topic Re: Cannot boot ISR 4321 in Switching

Cannot boot ISR 4321

Hulk8647 — Fri, 08 Mar 2019 22:08:45 GMT

I cannot boot this router for the life of me. I am stuck in rommon. The image is there:

rommon 1 > dir bootflash:

0   0         drw-     lost+found
0   0         drw-     .prst_sync
0   0         drw-     .installer
0   0         drw-     core
0   0         drw-     .rollback_timer
0   0         -rw-     tracelogs.548
0   0         drw-     tracelogs
0   30        -rw-     throughput_monitor_params
0   549586049 -rw-     isr4300-universalk9.16.06.02.SPA.bin

When I do

boot bootflash:isr4300-universalk9.16.06.02.SPA.bin

The router just boots to rommon again.

rommon 1 > boot usb1:isr4300-universalk9.16.06.02.SPA.bin
boot: unsupported boot device "usb1"
rommon 2 > boot bootflash:isr4300-universalk9.16.06.02.SPA.bin
File size is 0x20c20481
Located isr4300-universalk9.16.06.02.SPA.bin
Image size 549586049 inode num 15, bks cnt 134177 blk size 8*512
############################################################################################################
Boot image size = 549586049 (0x20c20481) bytes

Package header rev 1 structure detected
Calculating SHA-1 hash...done
validate_package: SHA-1 hash:
calculated ecc5b5b6:ebc75039:f88a7236:2b567f13:e45804bf
expected ecc5b5b6:ebc75039:f88a7236:2b567f13:e45804bf

RSA Signed RELEASE Image Signature Verification Successful.
Package Load Test Latency : 8324 msec
Image validated
Detected old ROMMON version 15.4(3r)S5, upgrade required
Upgrading to newer ROMMON version required by this version of IOS-XE, do not power cycle the system. A reboot will automatically occur for the new ROMMON to take effect.
Booted : 0
Selected : 0
Reset Reason: 0
Switching to ROM 1
Upgrading ROMMON image...
Verifying ROMMON image...
Switching back to ROM 0
ROMMON upgrade was successful...
Copying ROMMON environment...
Switching to ROM 1
Updating ROMMON environment...
Switching back to ROM 0
ROMMON upgrade complete.
To make the new ROMMON permanent, you must restart the RP.
ROMMON upgrade successful. Rebooting for upgrade to take effect.

Initializing Hardware ...

System integrity status: 00300610
Rom image verified correctly

Current image running: Boot ROM0

Last reset cause: LocalSoft
Cisco ISR4321/K9 platform with 4194304 Kbytes of main memory

Rommon upgrade requested
Flash upgrade reset 0 in progress
.......
Initializing Hardware ...

Checking for PCIe device presence...done
System integrity status: 0x300610
Rom image verified correctly

Current image running: *Upgrade in progress* Boot ROM1

Last reset cause: BootRomUpgrade
ISR4321/K9 platform with 4194304 Kbytes of main memory

Any ideas?

Re: Cannot boot ISR 4321

burleyman — Tue, 06 Mar 2018 14:36:39 GMT

Try this...

boot system flash bootflash:isr4300-universalk9.16.06.02.SPA.bin

I think the syntax is the issue.

Mike

Re: Cannot boot ISR 4321

burleyman — Tue, 06 Mar 2018 14:37:42 GMT

First of course you need to do this...

no boot bootflash:isr4300-universalk9.16.06.02.SPA.bin

mike

Re: Cannot boot ISR 4321

Hulk8647 — Tue, 06 Mar 2018 14:40:52 GMT

I dont know how to delete this question. Either way, I found a solution here:

https://www.cisco.com/c/en/us/support/docs/routers/4000-series-integrated-services-routers/200678-Troubleshoot-Cisco-4000-Series-ISR-Stuck.html#anc2

Re: Cannot boot ISR 4321

burleyman — Tue, 06 Mar 2018 14:51:39 GMT

Looks like the same solution, great. Glad you got it resolved.

Mike

Re: Cannot boot ISR 4321

Hulk8647 — Tue, 06 Mar 2018 15:03:19 GMT

Now I'm having a different issue, i cannot delete the tftp from bootvar

Router(config)#do sh bootvar
BOOT variable = tftp:\\\\\\\\\\\\\\\\\\\ 255.255.255.255,12;bootflash:/isr4300-universalk9.16.06.02.SPA.bin,12;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102

I tried replacing it with

boot system flash bootflash:isr4300-universalk9.16.06.02.SPA.bin

Can't do it

Re: Cannot boot ISR 4321

burleyman — Tue, 06 Mar 2018 15:16:35 GMT

You need to run the command...

clear configure boot

and then put the correct boot config in.

Mike