cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
437
Views
0
Helpful
1
Replies
helenio
Beginner

Cat 6807 6500 Dual SUP 6T ISSU (eFSU) upgrade in SSO mode not working

Hello,

I'm trying to upgrade a 6807-XL with 2x SUP 6T (sso redundancy mode) with ISSU procedure.

The running version is s6t64-adventerprisek9-mz.SPA.153-1.SY2.bin and I'd like to upgrade to 155-1.SY1.

 

I issued the command 

"issu loadversion 4 bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY1.bin 3 slavebootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY1.bin"

 

and the module 3 (that was the standby) come back online with new version loaded but not in sso mode but in rpr mode (Reason: Software mismatch).

 

for detail see commeand below. 

 

reading the configuration guide I don't see way this should happen, I'm expecting to see standby module in sso mode even if they are runnig different IOS version.

 

Enhanced Fast Software Upgrade (eFSU)

 

Thank you in advance ..

 

###### 

switch# show redundancy states

       my state = 13 -ACTIVE

     peer state = 4  -STANDBY COLD

           Mode = Duplex

           Unit = Secondary

        Unit ID = 4

 

Redundancy Mode (Operational) = rpr    Reason: Software mismat

Redundancy Mode (Configured)  = sso

Redundancy State              = rpr

     Maintenance Mode = Disabled

    Manual Swact = enabled

 Communications = Up

 

   client count = 136

 client_notification_TMR = 30000 milliseconds

          keep_alive TMR = 9000 milliseconds

        keep_alive count = 0

    keep_alive threshold = 19

           RF debug mask = 0x0

 

switch# show issu state detail

                          Slot = 4

                      RP State = Active

                    ISSU State = Load Version

                 Boot Variable = bootdisk:s6t64-adventerprisek9-mz.SPA.153-1.SY2.bin,12

                Operating Mode = rpr

               Primary Version = bootdisk:s6t64-adventerprisek9-mz.SPA.153-1.SY2.bin

             Secondary Version = bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY1.bin

               Current Version = bootdisk:s6t64-adventerprisek9-mz.SPA.153-1.SY2.bin

                Variable Store = PrstVbl

 

                          Slot = 3

                      RP State = Standby

                    ISSU State = Load Version

                 Boot Variable = bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY1.bin,12;bootdisk:s6t64-adventerprisek9-mz.SPA.153-1.SY2.bin,12

                Operating Mode = rpr 

               Primary Version = bootdisk:s6t64-adventerprisek9-mz.SPA.153-1.SY2.bin

             Secondary Version = bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY1.bin

               Current Version = bootdisk:s6t64-adventerprisek9-mz.SPA.155-1.SY1.bin

1 REPLY 1
Leo Laohoo
VIP Community Legend

Try this alternative method:
1. Copy the IOS into the primary supervisor card;
2. Copy the IOS into the secondary supervisor card;
3. Change the boot variable string to point to the new IOS and another line to point to the old IOS (in case the new IOS fails to boot);
4. Check to ensure the config-registry value is 0x2102;
5. Save the config.
6. Reboot.