01-10-2017 11:26 AM - edited 03-08-2019 08:51 AM
Hi,
Im trying to upgrade a 6509E with Sup2T from 15.1-2.SY7 to 15.1-2.SY9, and I can't get it to pull SY9 on boot?
Here is the boot disk, bootvar, and boot sys
WA-COR-DSW1A#sh bootdisk:
-#- --length-- -----date/time------ path
1 33554432 Jun 1 2016 16:50:02 -07:00 sea_console.dat
2 327680 Jun 1 2016 16:57:26 -07:00 sea_log.dat
3 120283112 Aug 1 2016 15:36:46 -07:00 s2t54-adventerprisek9-mz.SPA.151-2.SY7.bin
4 120873960 Jan 10 2017 09:55:02 -08:00 s2t54-adventerprisek9-mz.SPA.151-2.SY9.bin
6 120873960 Jan 10 2017 09:55:02 -08:00 s2t54-adventerprisek9-mz.SPA.151-2.SY9.bin
WA-COR-DSW1A#sh bootvar
BOOT variable = s2t54-adventerprisek9-mz.SPA.151-2.SY9.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
!
boot-start-marker
boot system flash s2t54-adventerprisek9-mz.SPA.151-2.SY9.bin
boot-end-marker
!
I really don't want to delete SY7 and "hope" that it boots to SY9.
Also I find it strange that the boot disk shows the SY9 image twice? if I delete SY9 then it will show SY7 twice?
Any ideas?
Thanks
Solved! Go to Solution.
01-10-2017 12:35 PM
I think the boot variable string is incorrect.
It should be: boot system flash bootdisk:s2t54-adventerprisek9-mz.SPA.151-2.SY9.bin
01-10-2017 12:35 PM
I think the boot variable string is incorrect.
It should be: boot system flash bootdisk:s2t54-adventerprisek9-mz.SPA.151-2.SY9.bin
01-10-2017 12:47 PM
You sir are correct! Careless error on my part.
Thank again.
01-10-2017 12:49 PM
Thank you for taking the time to rate our post(s). :)
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