Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

VSS IOS upgrade eFSU way - no luck

Hi,

Am not able to make it happen even though I've got same major release ..

6506-E chasis , SUP2T

SDC2-TP-SW01#sh ver | i IOS

Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.1(1)SY2, RELEASE SOFTWARE (fc4)

SDC2-TP-SW01#issu loadversion bootdisk:?

bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY2.bin

bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY.bin

SDC2-TP-SW01#issu loadversion bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY.bin

.......

.......

*Oct 18 15:55:18.595: %ISSU-SW1-3-FSM_MISMATCH_MTU: ISSU nego failed for client ISSU VS PROV Client(6047) entity_id 2 session 196878 due to mismatch of mtu size 104 & 152.

*Oct 18 15:55:18.595: %ISSU-SW1-4-FSM_INCOMP: Version of local ISSU client ISSU VS PROV Client(6047) in session 196878 is incompatible with remote side.

*Oct 18 15:55:19.783: %PFREDUN-SW1-6-ACTIVE: Standby initializing for RPR mode

*Oct 18 15:55:24.199: %ISSU_ERROR-SW1-3-MSG_MTU: ISSU VS HA Client(6052): Client failed to get mtu for message 11 (ISSU_RC_NEGO_INCOMP)

SDC2-TP-SW01#sh issu state detail

         The system is configured to be upgraded in staggered mode.

         2 nodes are found to be online.

         Summary: an in-tandem upgrade is in progress.

               Slot = 1/5

           RP State = Active

         ISSU State = Load Version

       Boot Variable = bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY2.bin,12;

     Operating Mode = rpr

     ISSU Sub-State = Load Version completed, waiting for system to settle

     Starting Image = bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY2.bin

       Target Image = bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY.bin

     Current Version = bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY2.bin

               Slot = 2/5

           RP State = Standby

         ISSU State = Load Version

       Boot Variable = bootdisk:s2t54-ipservicesk9-mz.SPA.151-2.SY.bin,12;bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY2.bin,12

     Operating Mode = rpr

SDC2-TP-SW01#sh issu comp-matrix stored

Number of Matrices in Table = 1

         (1) Matrix for s2t54-IPSERVICESK9-M(10) - s2t54-IPSERVICESK9-M(10)

        ==========================================

        Start Flag (0xDEADBABE)

                My Image ver:  15.1(2)SY

                Peer Version    Compatibility

                ------------    -------------

                15.0(1)SY               Incomp(1)

                15.0(1)SY1              Incomp(1)

                15.0(1)SY2              Incomp(1)

                15.0(1)SY3              Incomp(1)

                15.0(1)SY4              Incomp(1)

                15.1(1)SY               Incomp(1)

               15.1(1)SY1              Incomp(1)   why it says incompatinle ???????

                15.0(1)SY5              Incomp(1)

                15.1(2)SY               Comp(3)

I did check that version on Cisco feature navigation and was assured it does support eFSU ?

Any help appreciated....

Thanks

5 REPLIES
New Member

VSS IOS upgrade eFSU way - no luck

nsf not enables yet as I have no any uplink/downlink switches attached or any dynamic protocol running. Can it be a culprit ? But why it complains about MTU ?

VIP Super Bronze

Re: VSS IOS upgrade eFSU way - no luck

No you need NSF as you are not running any routing protocols
Is VSS functioning correct?
Do you have 1 sup 2t per chassis?

What is the output of show virtual switch details?

HTH

Sent from Cisco Technical Support iPhone App

New Member

VSS IOS upgrade eFSU way - no luck

xxxx#sh switch virtual

Switch mode                  : Virtual Switch

Virtual switch domain number : 2

Local switch number          : 1

Local switch operational role: Virtual Switch Active

Peer switch number           : 2

Peer switch operational role : Virtual Switch Standby

WAGRSW01#sh switch virtual redundancy

                  My Switch Id = 1

                Peer Switch Id = 2

    Configured Redundancy Mode = sso

     Operating Redundancy Mode = sso

Switch 1 Slot 5 Processor Information :

-----------------------------------------------

        Current Software state = ACTIVE

       Uptime in current state = 4 hours, 20 minutes

Image Version = Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.1(1)SY2, RELEASE SOFTWARE (fc4)

                          BOOT = bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY2.bin,12;

                   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)

       Uptime in current state = 4 hours, 16 minutes

Image Version = Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.1(1)SY2, RELEASE SOFTWARE (fc4)

                          BOOT = bootdisk:s2t54-ipservicesk9-mz.SPA.151-1.SY2.bin

                   CONFIG_FILE =

                       BOOTLDR =

                  Fabric State = ACTIVE

           Control Plane State = STANDBY

New Member

VSS IOS upgrade eFSU way - no luck

VSS works fine without any issues

And yes , it is 1 sup2t per chassis

Cisco Employee

VSS IOS upgrade eFSU way - no luck

Although you have the same major release, you are still jumping a maintenance release version. That is why the compatibility matrix says that the new version you are trying to use in incompatible.

Take a look at the version numbers:

15.1(1)SY2

15.1(2)SY

15.1 is the train. The number in the parenthesis is your maintenance release. In general, for eFSU to work, you cannot jump train numbers or maintenance release numbers.

You will have to manually upgrade your VSS pair without using eFSU/ISSU.

Reference:

http://www.cisco.com/web/about/security/intelligence/ios-ref.html

1469
Views
5
Helpful
5
Replies
CreatePlease to create content