05-06-2011 12:21 AM - edited 03-06-2019 04:55 PM
Hi All,
I'm upgrading the IOS in 4506-E Supervisor 6L-E switch and not loading the new IOS from the bootflash. Please see the output below and let me know if we have play with any other config.
4506-E#dir bootflash:
Directory of bootflash:/
6 -rw- 25793234 Jul 25 2010 02:50:06 +00:00 cat4500e-entservicesk9-mz.122-54.SG.bin
7 -rw- 25936915 May 6 2011 04:06:06 +00:00 cat4500e-entservicesk9-mz.122-54.SG1.bin
128282624 bytes total (66969600 bytes free)
4506-E#show run | i boot
boot-start-marker
boot system flash bootflash:cat4500e-entservicesk9-mz.122-54.SG1.bin
boot system flash bootflash:cat4500e-entservicesk9-mz.122-54.SG.bin
boot-end-marker
4506-E#show bootva
BOOT variable = bootflash:cat4500e-entservicesk9-mz.122-54.SG1.bin,1;bootflash:cat4500e-entservicesk9-mz.122-54.SG.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2101
Thanks,
Kasi
Solved! Go to Solution.
05-06-2011 05:15 AM
0x2101 means it is going to load the first image it sees in bootflash no matter if a boot statement is used or not .which is the top image if you do dir bootflash: command . 0x2102 means it will use the image specified in the boot statement . With 0x2101 you don't need a boot statement it will just use the first image it sees in bootflash.
05-06-2011 05:23 AM
Hi,
I think that it ignores the boot system command and tries to boot from first available image in flash.
"When the boot field equals 0001, the switch loads the first valid system image found in onboard Flash memory" taken from here:
Regards.
Alain.
05-06-2011 05:25 AM
With 2101 the switch doesn't consult the 'boot system flash' variables, it instead consults the 'boot system rom' variable in the startup config. Since you didn't have a 'boot system rom' variable defined, the switch, by default, will load the first image that it finds in flash. That's why you were booting to the old image. It was techincally unaware of your boot priority due to your registry setting.
Please rate all helpful posts in this thread.
05-06-2011 01:36 AM
I had to change the confreg to 2102 to fix the issue. Its loaded the new IOS.
Can any one explain why it not loaded the new IOS when the confreg was 2101.
Thanks,
Kasi
05-06-2011 02:05 AM
Hi,
0x2101: boot from rom
0x2102: boot from flash
Regards.
Alain.
05-06-2011 04:29 AM
Hi Alain,
Thanks.
But how it was able to load the old IOS image from the bootflash when confreg was x2101 and why was not able to load the new IOS even though the boot priority was given to new IOS.
Thanks,
Kasi
05-06-2011 05:23 AM
Hi,
I think that it ignores the boot system command and tries to boot from first available image in flash.
"When the boot field equals 0001, the switch loads the first valid system image found in onboard Flash memory" taken from here:
Regards.
Alain.
05-06-2011 05:25 AM
With 2101 the switch doesn't consult the 'boot system flash' variables, it instead consults the 'boot system rom' variable in the startup config. Since you didn't have a 'boot system rom' variable defined, the switch, by default, will load the first image that it finds in flash. That's why you were booting to the old image. It was techincally unaware of your boot priority due to your registry setting.
Please rate all helpful posts in this thread.
05-06-2011 05:15 AM
0x2101 means it is going to load the first image it sees in bootflash no matter if a boot statement is used or not .which is the top image if you do dir bootflash: command . 0x2102 means it will use the image specified in the boot statement . With 0x2101 you don't need a boot statement it will just use the first image it sees in bootflash.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide