cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1040
Views
0
Helpful
1
Replies

Can't get VSS Chassis from Modular to Native IOS

Odd issue trying to upgrade a VSS chassis from SXH6 Modular to Native.

We  decided first to move from SXH6 Modular to SXH6 Native. Then we will  schedule in the SXH > SXI change. So, this was just a modular/native  switch of the same versions...

Didn't go as planned at all.

The  standby supervisor refuses to see the new image and switch to RPR mode.  it just comes back running the modular IOS and straight back to SSO.

TFTP'd software images to both SUPS ahead of schedule, and did the following.

       * No Boot System

        * Config-Register 0x2102
     
        * Boot System Flash sup-bootdisk:s72033-advipservicesk9-mz.122-33.SXH6.bin (The non-modular image installed)

         * Write mem (this should sync the bootvar across the two chassis,  telling both supervisors to boot the new image upon reload)

        * Redundancy reload shelf 2 (to reload the standby)

          Secondary reloads, and came back up, but when I do “show switch virtual  redundancy”, and The mode is SSO still, not RPR. And it’s still booting  the modular image!

VSS#show switch virtual redundancy
                   My Switch Id = 1
                 Peer Switch Id = 2
         Last switchover reason = active unit removed
     Configured Redundancy Mode = sso
      Operating Redundancy Mode = sso

Switch 1 Slot 5 Processor Information :
-----------------------------------------------
         Current Software state = ACTIVE
                          Image Version = Cisco IOS Software, s72033_rp Software  (s72033_rp-ADVIPSERVICESK9-VM), Version 12.2(33)SXH6, RELEASE SOFTWARE  (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Thu 15-Oct-09 03:31 by prod_rel_team
                           BOOT =
s72033-advipservicesk9-mz.122-33.SXH6.bin,1;
                    CONFIG_FILE =
                        BOOTLDR =
         Configuration register = 0x2102
                   Fabric State = ACTIVE
            Control Plane State = ACTIVE

Switch 2 Slot 5 Processor Information :
-----------------------------------------------
          Current Software state = STANDBY HOT (switchover  target)                  Image Version = Cisco IOS Software, s72033_rp  Software (s72033_rp-ADVIPSERVICESK9-VM), Version 12.2(33)SXH6, RELEASE  SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Thu 15-Oct-09 03:31 by prod_rel_team
                           BOOT =
s72033-advipservicesk9-mz.122-33.SXH6.bin,1;
                    CONFIG_FILE =
                        BOOTLDR =
         Configuration register = 0x2102
                   Fabric State = ACTIVE
            Control Plane State = STANDBY

Attempted  the same again, with a console connection to the secondary supervisor,  and you can actually see it start to boot the modular image! seemingly  ignoring the bootvar!

My  next step should be "Redundancy force-switchover" But what's the point  of forcing the switchover if it's just reloaded the same modular image!

Henceforth,  I'm stuck! I can't get the standby sup to boot off the new image and go  into RPR, and I don't want to reload both boxes at the same time with  no confidence it's going to work.

Anyone any idea what's going on?

Thanks

1 Reply 1

Yogesh Ramdoss
Cisco Employee
Cisco Employee

David,

If you provide the log reported on the standby console, it would be very helpful.

I assume the logs provided are not edited. In the BOOT variable reported, I do not see the filesystem mentioned.

BOOT = s72033-advipservicesk9-mz.122-33.SXH6.bin,1;

It should be something like: BOOT = sup-bootdisk:s72033-advipservicesk9-mz.122-33.SXH6.bin,1;

With the BOOT variable setting you mentioned, if the Cat6500 cannot find the image in the default filesystem, then it will boot the first valid file in the default filesystem. So, the logs reported would be very useful.

Also, please send "show running | include boot"

Logs from my lab VSS setup:

TAC_VSS#sh bootvar


BOOT variable = sup-bootdisk:s72033-ipbasek9-mz.122-33.SXI4a.bin,1;

Is the current modular IOS in "installed" status ? If you are not sure, please send the last line in "show version" results.

- Yogesh