Scott,
This really depends on the platform and where the image is store. Below is a walk though command by command. This is an example for a ASR920, but will work on any IOS device. Let me know if you have any questions. Type dir or dir /all (Shows directories from all file systems) Router#dir Directory of bootflash:/ <<<<<<<<<<< This is the local filesystem. I have seen this call (Flash, Flash0, Disk0, Disk1, Bootflash, Bootdisk, and a couple more. It really depends on the router platform) 12 -rw- 404372822 Jun 30 2017 21:35:15 -05:00 asr920-universalk9_npe.16.05.01.SPA.bin 23 -rw- 311139324 Aug 9 2017 04:01:41 -05:00 asr920-universalk9_npe.03.16.04.S.155-3.S4-ext.bin 25 -rw- 311274492 Dec 21 2017 10:39:19 -06:00 asr920-universalk9_npe.03.16.06b.S.155-3.S6b-ext.bin <<< Let boot this file Router (config)#boot ? bootstrap Bootstrap image file config Configuration file host Router-specific config file network Network-wide config file system System image file <<<<<<<< boot the System image files Router(config)#boot system ? WORD TFTP filename or URL flash Boot from flash memory <<<<<<< source will be from flash memory on ftp Boot from a server via ftp mop Boot from a Decnet MOP server rcp Boot from a server via rcp rom Boot from rom tftp Boot from a tftp server Router(config)#boot system flash ? WORD System image filename <<<<<<<< This should be the <filesystem>:/<imagefile.bin> <cr> Router (config)#boot system flash bootflash:/asr920-universalk9_npe.03.16.06b.S.155-3.S6b-ext.bin Save the config How to Verify. Make sure it's the only image confiugred Router#sh run | i boot boot system flash bootflash:/asr920-universalk9_npe.03.16.06b.S.155-3.S6b-ext.bin Router#sh bootvar Not all Cisco Devices have this command BOOT variable = bootflash:/asr920-universalk9_npe.03.16.06b.S.155-3.S6b-ext.bin,1; <<<<<<<This is what the system is going to try and boot CONFIG_FILE variable does not exist BOOTLDR variable does not exist Configuration register is 0x2102 Verify the that files exist and the router can get to it. Type dir and copy and path the BOOT Variable from above or from the sh run | i boot. Remove the ,1; from the end of the line. This will check to make sure you have not typo'd the filesystem or file name Router#dir bootflash:/asr920-universalk9_npe.03.16.06b.S.155-3.S6b-ext.bin Directory of bootflash:/asr920-universalk9_npe.03.16.06b.S.155-3.S6b-ext.bin 25 -rw- 311274492 Dec 21 2017 10:39:19 -06:00 asr920-universalk9_npe.03.16.06b.S.155-3.S6b-ext.bin 1339412480 bytes total (200482816 bytes free) -----Original Message----- From: cisco-nsp <cisco-nsp-boun...@puck.nether.net> On Behalf Of Hagen Amen Sent: Thursday, February 28, 2019 12:16 PM To: Scott Voll <svoll.v...@gmail.com> Cc: cisco-nsp <cisco-nsp@puck.nether.net> Subject: Re: [c-nsp] Correct syntax for Boot system I've found, same as Tyler, that the "flash:" alias doesn't work at boot (on my 4Ks), so the stanza: boot-start-marker > boot system bootflash:isr4300-universalk9.16.06.03.SPA.bin > boot-end-marker works just fine. I do see systems out of the box with the extra "flash" keyword. I haven't found one yet that doesn't work by pointing directly to the file system name. Does seem like a newer bit of added clutter. sincerely, Hagen On Thu, Feb 28, 2019 at 10:06 AM Scott Voll <svoll.v...@gmail.com<mailto:svoll.v...@gmail.com>> wrote: > External Sender - Be Suspicious of Attachments, Links, and Requests > for Payment or Login Information. > > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > > my question is the extra flash in the command: > > boot system *flash* bootflash:filename.bin > > is that something new? > > Scott > > > > > On Thu, Feb 28, 2019 at 9:53 AM Tyler Applebaum > <appleba...@ochin.org<mailto:appleba...@ochin.org>> > wrote: > > > On the 4k series I use bootflash:<filename> > > > > -----Original Message----- > > From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf > > Of Scott Voll > > Sent: Thursday, February 28, 2019 9:40 AM > > To: cisco-nsp <cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net>> > > Subject: [c-nsp] Correct syntax for Boot system > > > > I have always used > > > > boot system flash:xxxxxx.bin or boot system bootflash:xxxx.bin > > > > did the syntax change to boot system flash flash0:xxxxx.bin??? > > > > I have a new 4331 that without the extra flash it failed to boot. Is > this > > new? did I miss the memo? > > > > does this carry over to ASRs and the older 29xx/39xx platforms? > > > > I'm booting a bunch of remote routers and don't want to be driving > > to recover them from a simple mistake I missed. > > > > TIA > > > > Scott > > _______________________________________________ > > cisco-nsp mailing list > > cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > Attention: Information contained in this message and or attachments > > is intended only for the recipient(s) named above and may contain > confidential > > and or privileged material that is protected under State or Federal law. > If > > you are not the intended recipient, any disclosure, copying, > > distribution or action taken on it is prohibited. If you believe you > > have received > this > > email in error, please contact the sender with a copy to > > complia...@ochin.org<mailto:complia...@ochin.org>, delete this email and > > destroy all copies. > > > _______________________________________________ > cisco-nsp mailing list > cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net<mailto:cisco-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ________________________________ CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you. _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
