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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

cannot upgrade IOS on 4500X vss

hello

I tried to change image from cat4500e-universal.SPA.03.04.02.SG.151-2.SG2.bin to cat4500e-universalk9.SPA.03.04.02.SG.151-2.SG2.bin

try with ISSU or FSU but always have the same pb

standby reboot whith the new version but at the end of process choose to reset again because , propably, of version or licence-level mismatch ?

below logs from the standby and active console

any idea ?

thanks in advance

regards,

Marc

 

standby :

Initializing as Virtual Switch STANDBY processor

*Apr 28 09:03:56.601: %C4K_IOSMODPORTMAN-4-POWERSUPPLYBAD: Power supply 2 has failed
 or been turned off
*Apr 28 09:04:44.522: %C4K_TRANSCEIVERMAN-3-INCOMPATIBLE: Port 61: New transceiver (
speed 0Mbps) is incompatible with this module
*Apr 28 09:04:48.915: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot 1
port 2.
*Apr 28 09:04:48.928: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot 1
port 1.
*Apr 28 09:05:04.918: %VSLP-5-VSL_UP:  Ready for control traffic

*Apr 28 09:05:09.938: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP
*Apr 28 09:05:46.308: %C4K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL: STANDBY:IOS version
mismatch. Active supervisor version is 15.1(2)SG2 (cat4500e-UNIVERSAL-M). Standby su
pervisor version is 15.1(2)SG2 (cat4500e-UNIVERSALK9-M). Redundancy feature may not
work as expected.
*Apr 28 09:05:46.308: %C4K_REDUNDANCY-2-NON_SYMMETRICAL_REDUNDANT_SYSTEM: STANDBY:ST
ANDBY supervisor will operate in fallback redundancy mode rpr.
*Apr 28 09:05:49.351: %C4K_REDUNDANCY-3-COMMUNICATION: STANDBY:Communication with th
e peer Supervisor has been established
*Apr 28 09:05:50.238: %C4K_REDUNDANCY-2-VS_REBOOT_ON_RPR_FALLBACK: STANDBY:Superviso
r in virtual-switch configuration cannot operate in redundancy mode RPR, will be res
et
*Apr 28 09:05:50.434: %RF-5-RF_RELOAD: STANDBY:Self Reload. Reason: Virtual-switch f
allback to RPR
*Apr 28 09:05:50.446: %VSLP-3-VSLP_LMP_FAIL_REASON: STANDBY: 1/2 : Link down
*Apr 28 09:05:50.458: %VSLP-3-VSLP_LMP_FAIL_REASON: STANDBY: 1/1 : Link down
*Apr 28 09:05:50.458: %VSLP-2-VSL_DOWN: STANDBY:  All VSL links went down while swit
ch is in Standby role

*Apr 28 09:05:50.458: %C4K_REDUNDANCY-3-NOT_READY_FOR_SWITCHOVER: STANDBY:The active
 Supervisor failed but standby supervisor cannot initiate Switchover activity. Reset
ting standby Supervisor.
*Apr 28 09:05:50.498: %RF-5-RF_RELOAD: STANDBY:Self Reload. Reason: Standby not read
y for switchover
*Apr 28 09:05:50.650: %SYS-5-RELOAD: STANDBY:Reload requested by Platform redundancy
 manager. Reload Reason: Virtual-switch fallback to RPR.

Switchover activity can not be initiated. Resetting...

Please stand by while rebooting the system...
                                             Restarting system.


active :

Apr 28 09:04:48.918: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot
 11 port 2.
Apr 28 09:04:48.942: %C4K_IOSINTF-5-LMPHWSESSIONSTATE: Lmp HW session UP on slot
 11 port 1.
Apr 28 09:05:04.928: %VSLP-5-VSL_UP:  Ready for control traffic
Initializing as Virtual Switch ACTIVE processor

Apr 28 09:05:08.929: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE  by VSLP
Apr 28 09:05:08.929: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/1 joined port
-channel Port-channel20
Apr 28 09:05:08.942: %EC-5-BUNDLE: Interface TenGigabitEthernet2/1/2 joined port
-channel Port-channel20
Apr 28 09:05:09.906: %C4K_REDUNDANCY-6-DUPLEX_MODE: The peer Supervisor has been
 detected
Apr 28 09:05:31.337: %SW_LEVEL-6-RESULT: Operational redundancy mode is UNKNOWN,
 due to software license-level mismatch at ACTIVE and STANDBY. Software Level on
 Active: entservices; on Standby: entservices.
Apr 28 09:05:49.356: %C4K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL: IOS version misma
tch. Active supervisor version is 15.1(2)SG2 (cat4500e-UNIVERSAL-M). Standby sup
ervisor version is 15.1(2)SG2 (cat4500e-UNIVERSALK9-M). Redundancy feature may n
ot work as expected.
Apr 28 09:05:49.360: %C4K_REDUNDANCY-6-MODE: ACTIVE supervisor initializing for
rpr mode
Apr 28 09:05:49.922: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the pee
r Supervisor has been established
Apr 28 09:05:50.562: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/2 left the
port-channel Port-channel20
Apr 28 09:05:50.574: %VSLP-3-VSLP_LMP_FAIL_REASON: Te2/1/2: Link down
Apr 28 09:05:50.582: %EC-5-UNBUNDLE: Interface TenGigabitEthernet2/1/1 left the
port-channel Port-channel20
Apr 28 09:05:50.594: %VSLP-3-VSLP_LMP_FAIL_REASON: Te2/1/1: Link down
Apr 28 09:05:50.594: %VSLP-2-VSL_DOWN:   All VSL links went down while switch is
 in ACTIVE role

Apr 28 09:05:50.925: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the pee
r Supervisor has been lost
Apr 28 09:05:50.938: %C4K_REDUNDANCY-3-SIMPLEX_



 

12 REPLIES
VIP Super Bronze

Hi,Are you following this

Hi,

Are you following this document to use ISSU?

Also, can you make sure preemption is not enabled?

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/15-1-2/XE_340/configuration/guide/config/vss.html#wp1320146

HTH

 

New Member

HiYes I followed exactly this

Hi

Yes I followed exactly this document

I tried again :  issu changeversion bootflash:cat4500e-universalk9...

and got exactly the sames messages :

extracts :

active :

Apr 28 14:31:24.595: %SW_LEVEL-6-RESULT: Operational redundancy mode is UNKNOWN, due
 to software license-level mismatch at ACTIVE and STANDBY. Software Level on Active:
 entservices; on Standby: entservices.

 

standby :

*Apr 28 14:31:37.230: %C4K_REDUNDANCY-2-NON_SYMMETRICAL_REDUNDANT_SYSTEM: STANDB
Y:STANDBY supervisor will operate in fallback redundancy mode rpr.
*Apr 28 14:31:40.314: %C4K_REDUNDANCY-3-COMMUNICATION: STANDBY:Communication wit
h the peer Supervisor has been established
*Apr 28 14:31:41.027: %C4K_REDUNDANCY-2-VS_REBOOT_ON_RPR_FALLBACK: STANDBY:Super
visor in virtual-switch configuration cannot operate in redundancy mode RPR, wil
l be reset

I don't know what you mean by "premeption" but here is the result of "show switch VIrtual role"

Switch  Switch Status  Preempt       Priority  Role     Local   Remote
        Number         Oper(Conf)    Oper(Conf)         SID     SID
--------------------------------------------------------------------
LOCAL   1      UP      FALSE(N )     100(100)  ACTIVE   0       0   
REMOTE  2      UP      FALSE(N )     100(100)  STANDBY  3269    8564

thanks

 

marc

 

 

VIP Super Bronze

Hi,From the log messages, it

Hi,

From the log messages, it appears that each switch has a different license levels installed and not the same.

What is the output of

sh switch virtual

sh redun

sh lice image leve

HTH

New Member

HiWe found this in the Cisco

Hi

We found this in the Cisco VSS documentation

Prerequisites to Performing ISSU

The type of the pre- and post-upgrade images must match precisely. Identical. ISSU is not supported from a Universal_lite to a Universal image, or vice versa. ISSU is also not supported from a k9 image to a non-k9 image, or vice versa.

 

I suppose now I must "break" the VSS and process with interruption  !?

Here is the process I  suppose ::

1 - set register to 0x2102 and set the bootvar to new IOS on active and passive

2 - halt active (passive become active)

3 - reload new active on new IOS (cause service interruption during few minutes)

4 - boot now old active on new IOS

and I suppose VSS while operate in SSO mode now ?

 

thanks

 

Marc

New Member

ooopswhen I say "passive"" ,

ooops

when I say "passive"" , I mean "standby" of course, sorry

 

Hall of Fame Super Gold

Read my post above.  I have

Read my post above.  I have two options for you to choose from and none of them uses ISSU.  

New Member

thank you Leowhen you say

thank you Leo

when you say "reboot", you mean active AND standby at the same time (otherwise it will happen the same problem), so with an interruption ?

thanks

 

Marc

Hall of Fame Super Gold

when you say "reboot", you

when you say "reboot", you mean active AND standby at the same time (otherwise it will happen the same problem), so with an interruption ?

When you upgrade the IOS of a VSS pair, both units have to reboot otherwise, one of the two will go into ROMmon.  

 

So when you issue the "reload" command on an active VSS pair, both will reboot.

 

We can have a nice discussion about how ISSU will boot one-at-a-time but, in my opinion and experience, ISSU doesn't work well all the time and when ISSU doesn't work well, your VSS pairs still have to reboot.

New Member

This is actually incorrect.

This is actually incorrect. Issuing the command "reload" on the active chassis/sup will only reboot that switch. The standby will not. You will need to issue the command "redundancy reload shelf" in order to boot both switches.

You are both right. It

You are both right. It actually depends on the platform/IOS, for whatever reasons:

 

c6k Sup2T

c4500

 Link: Configure VSS (Sup2T)

 Link: Configure VSS (c4500)

User Actions

User Actions

If you enter the reload command from the command console, the entire VSS performs a reload.

If you enter the reload command from the command console, it performs a reload on the switch where reload is issued.

 

I agree on better using the "redundancy ..." commands, those are thankfully consistent. A drawback of the "redundancy ..." commands is, however, that they do not support the optional keywords "in" or "at" (known from the "reload" command) in order to schedule a reload. If you want to use one of this keywords, the only option is the "issu changeversion" command (if applicable).

HTH
Rolf

Hall of Fame Super Gold

Ok, I've got TWO options for

Ok, I've got TWO options for you to choose from:  

 

Option 1:  Config-Register 0x2102

Configuration Register value of 0x2101 is, by default, the setting when the appliance or supervisor is shipped out.  The last octet of "1" basically tells the appliance to IGNORE the boot variable string and boot the first valid IOS (from top to bottom) found in the bootflash.  

The easiest and fastest way to do an IOS upgrade on a VSS pair is very simple.  

 

1.  Copy the IOS from the TFTP server to the active unit using the command "copy tftp://<TFTP IP address>/IOS_filename.bin bootflash:";

2.  Copy the IOS from the TFTP server to the standby unit using the command "copy tftp://<TFTP IP address>/IOS_filename.bin slavebootflash:";

3.  Remove the old boot variable string:  no boot system flash

4.  Change to the new boot variable string:  boot system flash bootflash:IOS_filename.bin

5.  Change the config-registry value to 0x2102:  config-registry 0x2102

6.  Save the config.

7.  Reboot. 

 

Now be aware that, like any 4500 supervisor card and 6500 supervisor card, if you change the config-registry to 0x2102 and you DO NOT HAVE a boot variable string (or a valid one), the your switch will reboot into ROMmon.  So please take good care in entering the right boot variable string.

 

Option 2:  Config-Register 0x2101

Now, if you do not want to change the config-registry value to 0x2102, this means that you would like config-registry value of 0x2101, there's another option around this.  

 

And the process is almost similar.  

 

1.  Copy the IOS from the TFTP server to the active unit using the command "copy tftp://<TFTP IP address>/IOS_filename.bin bootflash:";

2.  Copy the IOS from the TFTP server to the standby unit using the command "copy tftp://<TFTP IP address>/IOS_filename.bin slavebootflash:";

3.  RENAME the old IOS in both units:  

Active:  rename bootflash:OLD_IOS_filename.bin bootflash:OLD_IOS_filename.bin.BAK

Standby:  rename slavebootflash:OLD_IOS_filename.bin slavebootflash:OLD_IOS_filename.bin.BAK

4.  Save the config.

5.  Reboot.

 

You need to rename the old IOS because if you don't then there's a chance that one of the VSS pairs will boot the OLD IOS if the file is found to be above the new IOS file.

 

Hope this helps. 

 

PS:  I've stopped attempting to upgrade via ISSU because it's never worked out for me.   Either one of the two options are "workarounds" when ISSU doesn't work.

New Member

Best way to use IOS upgrade

Best way to use IOS upgrade in 4500X without ISSU

(no downtime required but recommended to do it in maintenance window)

Method of Procedure

IOS Upgrade Cisco 4500x (VSS)

Pre-upgrade activity.

  • Config backup of both of device
  • IOS backup of current IOS (In case required, will put current IOS again for roll back purpose.)

Below Command output.

Show version - Register value should be  (config-register 0x2102)

Show inventory

Show environment

dir bootflash:

dir slavebootflash:

show bootvar

show switch virtual

show redundancy

show switch virtual slot-map

show module

show log

show run start

Upgrade IOS in 4500x (VSS configured)

1 IOS download in bootflash and slave bootflash:

  • Copy tftp: bootflash:

2 Check IOS in bootflash

  • dir bootflash:
  • dir slavebootflash:

3 Very with MD5 command

  • Show version - Register value should be (config-register 0x2102)
  • verify bootflash: cat4500e-universalk9.SPA.03.06.05.E.152-2.E5.bin
  • verify slavebootflash: cat4500e-universalk9.SPA.03.06.05.E.152-2.E5.bin
  • 71a13a0fa109fa731743c199e7a29479 MD5 value for this IOS

4 Set the boot path for current IOS and verify path is set

  • no boot system bootflash:cat4500e- universalk9.SPA.03.04.05.SG.151-2.SG5.bin
  • boot system bootflash: cat4500e-universalk9.SPA.03.06.05.E.152-2.E5.bin
  • write
  • show bootvar

6) Standby switch will be reloading for IOS upgrade in standby device.

  • redundancy reload peer
  • show module (after peer come up)

     we will verify current IOS in peer switch with show module command

7) Now master device will be reloaded for IOS upgrade.

  • redundancy force-switchover

This will reload the active unit and force switchover to standby[confirm]

Preparing for switchover...

8) After primary device come up will verify IOS in both of device.

  • Show inventory
  • Show version
  • Show environment
  • dir bootflash:
  • dir slavebootflash:
  • show bootvar
  • show switch virtual
  • show redundancy
  • show switch virtual slot-map
  • show module
  • show log

 

6763
Views
5
Helpful
12
Replies
CreatePlease login to create content