cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2905
Views
5
Helpful
6
Replies

Updating Cisco ISR4331 from Everest (16.06.04) to Fuji (16.09.04)

stingus
Level 1
Level 1

Hello.

Having trouble updating Cisco ISR4331 from Everest (16.06.04) to Fuji (16.09.04)

Simply copying the firmware to the router and changing "boot system" image isn't helping.

The image is verified.

Router just won't boot into the new firmware and I don't know why. Same thing is going on when I try to downgrade to 16.05.X, but little steps like 16.06.04 -> 16.06.05 or 16.06.06 -> 16.06.04 are working both ways.

I feel that I might be missing something, am I? Maybe there are some extra steps required to update/downgrade to a different major version?

 

Here's what I have in boot:

Router#sh run br | i booboot-start-marker
boot system flash:isr4300-universalk9.16.09.04.SPA.bin
boot system flash:isr4300-universalk9.16.06.04.SPA.bin
boot-end-marker

 

Here's what I get when I do the:

verify isr4300-universalk9.16.09.04.SPA.bin

Embedded Hash SHA1 : 87D928C49CBD8EFB40C0A06BF2EBFD57498F302B
Computed Hash SHA1 : 87D928C49CBD8EFB40C0A06BF2EBFD57498F302B
Starting image verification
Hash Computation: 100%Done!
Computed Hash SHA2: b026294539f32f3ea152a93347212005
931587215d531f954487823e29879c62
27cc9892a9e6507c5590222414bbff01
f1a2ad8ab2e0255bff7823c6ccffb863

Embedded Hash SHA2: b026294539f32f3ea152a93347212005
931587215d531f954487823e29879c62
27cc9892a9e6507c5590222414bbff01
f1a2ad8ab2e0255bff7823c6ccffb863

Digital signature successfully verified in file bootflash:isr4300-universalk9.16.09.04.SPA.bin

1 Accepted Solution

Accepted Solutions

Leo Laohoo
Hall of Fame
Hall of Fame
Please read the Release Notes very carefully.
It is not possible to upgrade from 16.6.X to 16.9.X without upgrading the ROMMON first.
WARNING: Upgrade ROMMON to version 16.12(2r) or else you'll brick the router due to CSCvr18589.

View solution in original post

6 Replies 6

joey.debra
Level 1
Level 1

Hey,

I haven't touched an ISR in a while but since it's running IOS XE I have to ask the question.
Is the router running install mode or bundle mode?

Because the bundle mode is where the bin file is still intact and can use the boot system command, but install mode is different.

If you do a dir in priv exec and you see a bunch of .pkg files and a packages.conf file you're in install mode and you'll need to do the install commands.  Please refer to the support page how to perform the upgrade.

Hi!

The router operates in the Bundle mode.

Selecting different boot flash works if I'm moving between the Minor versions (16.06.04->16.06.06->16.06.05 and backwards).

As far as I understand, Bundle mode is on if I have a "boot flash" stated. If it's not stated - router will be working in the Install mode, right?

 

Router#sh boot
BOOT variable = flash:isr4300-universalk9.16.09.04.SPA.bin,12;flash:isr4300-universalk9.16.06.04.SPA.bin,12;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102

Standby not ready to show bootvar

 

Router#dir
Directory of bootflash:/

73441 drwx 4096 Oct 16 2019 07:09:00 +03:00 .installer
179521 drwx 4096 Mar 26 2019 17:25:54 +03:00 sysboot
24482 -rw- 550119351 Sep 21 2019 01:19:24 +03:00 isr4300-universalk9.16.06.04.SPA.bin
12 -rw- 35 Mar 26 2019 15:14:41 +03:00 pnp-tech-time
13 -rw- 149504 Mar 26 2019 15:14:52 +03:00 pnp-tech-discovery-summary
130561 drwx 4096 Nov 28 2018 10:01:33 +03:00 core
57121 drwx 4096 Oct 16 2019 07:11:09 +03:00 .prst_sync
65281 drwx 4096 Nov 28 2018 10:00:10 +03:00 .rollback_timer
146881 drwx 36864 Nov 11 2019 16:24:58 +03:00 tracelogs
97921 drwx 4096 Nov 28 2018 10:00:33 +03:00 virtual-instance
81601 drwx 4096 Nov 28 2018 10:00:33 +03:00 vman_fdb
14 -rw- 30 Oct 16 2019 07:11:10 +03:00 throughput_monitor_params
89761 drwx 4096 Nov 28 2018 10:01:29 +03:00 onep
15 drwx 4096 Mar 19 2019 10:49:46 +03:00 lost+found
24481 -rw- 550218614 Mar 27 2019 09:39:30 +03:00 isr4300-universalk9.16.06.05.SPA.bin
24483 -rw- 527671528 Oct 3 2019 12:56:26 +03:00 isr4300-universalk9.16.05.01b.SPA.bin
24484 -rw- 585126403 Oct 8 2019 17:39:47 +03:00 isr4300-universalk9.16.09.04.SPA.bin

3174936576 bytes total (261361664 bytes free)

 

Router#dir bootflash:/sysboot
Directory of bootflash:/sysboot/

179522 -r-- 50124 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_dreamliner.16.08.01.SPA.pkg
179523 -r-- 6497232 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_dsp_analogbri.16.08.01.SPA.pkg
179524 -r-- 1704908 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_dsp_sp2700.16.08.01.SPA.pkg
179525 -r-- 17818572 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_dsp_tilegx.16.08.01.SPA.pkg
179526 -r-- 10699724 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_ngwic_t1e1.16.08.01.SPA.pkg
179527 -r-- 9241548 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_nim_async.16.08.01.SPA.pkg
179528 -r-- 4604880 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_nim_bri_st_fw.16.08.01.SPA.pkg
179529 -r-- 17490892 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_nim_cwan.16.08.01.SPA.pkg
179530 -r-- 2520008 Mar 26 2019 17:25:49 +03:00 isr4300-firmware_nim_ge.16.08.01.SPA.pkg
179531 -r-- 11518924 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_nim_shdsl.16.08.01.SPA.pkg
179532 -r-- 3740616 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_nim_ssd.16.08.01.SPA.pkg
179533 -r-- 6296524 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_nim_xdsl.16.08.01.SPA.pkg
179534 -r-- 10118088 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_prince.16.08.01.SPA.pkg
179535 -r-- 2192328 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_sm_10g.16.08.01.SPA.pkg
179536 -r-- 10953676 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_sm_1t3e3.16.08.01.SPA.pkg
179537 -r-- 10634188 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_sm_async.16.08.01.SPA.pkg
179538 -r-- 1823696 Mar 26 2019 17:25:50 +03:00 isr4300-firmware_sm_dsp_sp2700.16.08.01.SPA.pkg
179539 -r-- 407126996 Mar 26 2019 17:25:54 +03:00 isr4300-mono-universalk9_npe.16.08.01.SPA.pkg
179540 -r-- 8685 Mar 26 2019 17:25:54 +03:00 packages.conf

3174936576 bytes total (261361664 bytes free)

I have not heard of any problems like this. What is your:

config register setting

ROMMON version

 

also, I don't think it makes much of a difference, maybe it's just habit after all these years, but i typically define the boot statement as:

boot system flash bootflash:filename

 

 

again, not sure if any of this is overly relevant but since I've not heard of a problem like this I'm just suggesting the most basic things.

 

Leo Laohoo
Hall of Fame
Hall of Fame
Please read the Release Notes very carefully.
It is not possible to upgrade from 16.6.X to 16.9.X without upgrading the ROMMON first.
WARNING: Upgrade ROMMON to version 16.12(2r) or else you'll brick the router due to CSCvr18589.

OUCH!

 

guess I'll be re-doing rommons this weekend.

Hello!
Thank you for the information!
Special thanks for the warning! But doesn't seem to affect my 4331 model.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: