12-02-2014 09:41 AM - edited 03-07-2019 09:44 PM
I am about to replace my distribution switches supervisor engine with VS-S720 engines. The modules came with s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin image installed. I was wondering if there is a boot image compatible with this code or does the Universal Boot Loader Image that place of the boot image I am use to in the 12 code train? If it does take the place of the boot image where is it installed or is it already partitioned on the module hardware or something?
Router#sh mod
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
3 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC SAD04350FB7
4 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC SAD0510070K
5 5 Supervisor Engine 720 10GE (Active) VS-S720-10G SAL17162Z07
6 5 Supervisor Engine 720 10GE (Hot) VS-S720-10G SAL1751J5T8
8 6 Firewall Module WS-SVC-FWM-1 SAD081002NE
9 48 48 port 10/100 mb RJ45 WS-X6348-RJ-45 SAD0416060S
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
3 0001.6460.2ff8 to 0001.6460.3007 1.2 5.4(2) 15.1(1)SY1 Ok
4 0001.9725.9b8a to 0001.9725.9b99 1.2 5.4(2) 15.1(1)SY1 Ok
5 5057.a8e2.70f5 to 5057.a8e2.70fc 4.1 8.5(4) 15.1(1)SY1 Ok
6 4403.a70a.873c to 4403.a70a.8743 4.1 8.5(4) 15.1(1)SY1 Ok
8 0003.feae.7dac to 0003.feae.7db3 3.0 7.2(1) 2.3(4) Ok
9 00d0.c0cd.62c8 to 00d0.c0cd.62f7 1.1 5.3(1) 15.1(1)SY1 Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
5 Policy Feature Card 3 VS-F6K-PFC3CXL SAL1644R9BK 1.3 Ok
5 MSFC3 Daughterboard VS-F6K-MSFC3 SAL1702W9ES 5.1 Ok
6 Policy Feature Card 3 VS-F6K-PFC3CXL SAL1750HSSE 1.3 Ok
6 MSFC3 Daughterboard VS-F6K-MSFC3 SAL1750HSYQ 5.1 Ok
Mod Online Diag Status
---- -------------------
3 Pass
4 Pass
5 Pass
6 Pass
8 Pass
9 Pass
Router#sh boot
BOOT variable = bootflash:s72033-ipservicesk9-mz.151-1.SY1.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
Standby is up
Standby has 1048576K/65536K bytes of memory.
Standby BOOT variable = bootflash:s72033-ipservicesk9-mz.151-1.SY1.bin,1;
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable does not exist
Standby Configuration register is 0x2102
12-02-2014 05:21 PM
I am sorry to say I dont understand the question what you are requesting for?
Anyhow let me point my view:
1- Currently you have Sup running 15.1(SY1) Image and all working fine now.
2- Now you have recieved the new Sup module with image 15.2(SY2).
Question:
=======
1- R u going to replace both the sup on this chasis or only one?
2- If you are replacing both the Sup then you would not have any problem the Sup;s would comeup properly with the SSO mode and you would be good to go.
3- In case you are changing/replacing only one of the sup then the sup would come up but it would in RPR mode which means that the standby redundancy mode would not be sso bcz of IOS mismatch. Either you have downgrade the image to the one which is currently working or upgrade the ios to match the same.
4- Regarding the hardware modules on the chasis that would not be impacted either way bcz those all would be still supported.
HTH
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