02-16-2006 09:39 PM - edited 03-03-2019 01:52 AM
I noticed on one of our 6509's with MSFC that it had the following boot statements:
boot system flash bootflash:c6msfc2-dsv-mz.121-13.E5.bin
boot system bootflash:c6msfc2-psv-mz.121-13.E14.bin
boot bootldr bootflash:c6msfc2-boot-mz.121-13.E14.bin
What is the difference between the first 2 statements?
also, I noticed that the first image name is not even in bootflash.
Directory of bootflash:/
1 -rw- 1787412 May 21 2004 07:58:18 c6msfc2-boot-mz.121-13.E14.bin
2 -rw- 13097736 May 21 2004 07:58:33 c6msfc2-psv-mz.121-13.E14.bin
3 -rw- 2071 Jul 31 2004 13:53:48 satrt
31981568 bytes total (17093964 bytes free)
Just wanted to get some clarification on how these boot variables work. Thanks.
Solved! Go to Solution.
02-16-2006 10:30 PM
Hello,
There is essentially no difference in the first 2 boot system statements, with the exception of the image name. The system will try to boot from bootflash: c6msfc2-dsv-mz.121-13.E5.bin first. If the file is not present it will move to the next sequential boot system command configured - boot system bootflash:c6msfc2-psv-mz.121-13.E14.bin. The 3rd command is for the boot image - this is a limited version of software if previous attempts to load the specified images fails and there isn't a valid image in flash. You will see router(boot) prompt if this image is loaded.
To verify boot variables from the MSFC you can issue the show boot command.
Hope this helps.
Regards,
James
02-16-2006 10:30 PM
boot system flash bootflash:c6msfc2-dsv-mz.121-13.E5.bin is a valid boot variable.
boot system bootflash:c6msfc2-psv-mz.121-13.E14.bin is not a valid boot statement for MSFC, you need the "flash" keyword. However, if the config-register is set to 2102, this will boot into boot mode if reloaded, because the image "c6msfc2-dsv-mz.121-13.E5.bin" is not in the bootflash:. so it will boot the first available image in the bootflash which happens to be the boot loader.
To correct the boot variable remove the first and second boot statements:
config t
no boot system flash bootflash:c6msfc2-dsv-mz.121-13.E5.bin
no boot system bootflash:c6msfc2-psv-mz.121-13.E14.bin
then add the second boot statement:
boot system flash bootflash:c6msfc2-psv-mz.121-13.E14.bin
wr mem
show boot to confirm.
02-16-2006 10:30 PM
Hello,
There is essentially no difference in the first 2 boot system statements, with the exception of the image name. The system will try to boot from bootflash: c6msfc2-dsv-mz.121-13.E5.bin first. If the file is not present it will move to the next sequential boot system command configured - boot system bootflash:c6msfc2-psv-mz.121-13.E14.bin. The 3rd command is for the boot image - this is a limited version of software if previous attempts to load the specified images fails and there isn't a valid image in flash. You will see router(boot) prompt if this image is loaded.
To verify boot variables from the MSFC you can issue the show boot command.
Hope this helps.
Regards,
James
02-16-2006 10:30 PM
boot system flash bootflash:c6msfc2-dsv-mz.121-13.E5.bin is a valid boot variable.
boot system bootflash:c6msfc2-psv-mz.121-13.E14.bin is not a valid boot statement for MSFC, you need the "flash" keyword. However, if the config-register is set to 2102, this will boot into boot mode if reloaded, because the image "c6msfc2-dsv-mz.121-13.E5.bin" is not in the bootflash:. so it will boot the first available image in the bootflash which happens to be the boot loader.
To correct the boot variable remove the first and second boot statements:
config t
no boot system flash bootflash:c6msfc2-dsv-mz.121-13.E5.bin
no boot system bootflash:c6msfc2-psv-mz.121-13.E14.bin
then add the second boot statement:
boot system flash bootflash:c6msfc2-psv-mz.121-13.E14.bin
wr mem
show boot to confirm.
02-16-2006 11:26 PM
sounds good. Thanks for the clarification.
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