VSS between 4506/Sup7L-E puts Standby into bootloop

[tneumayer]

I'm trying to put two 4506-E with Sup7L-E together to build a VSS.

My main source of documentation is http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/15-1-2/XE_340/configuration/guide/config/vss.html

I set up sw1 as virtual switch quite a while ago, as it is a productive switch in the core layer that cant be rebooted quite easily. So i figured i'd better prepare it for eventual VSS configurations in advance.

Now that i got the second chassis and sup-card. I booted it up, made sure the IOS is the same, reloaded it and went on with the configuration in order to get it to join VSS as Standby...which leads to this:

on sw1:

%ISSU-3-PEER_IMAGE_INCOMPATIBLE: Peer image (cat4500e-UNIVERSALK9-M), version (03.06.04.E) on peer uid (11) is incompatible
%C4K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL: IOS version mismatch. Active supervisor version is 15.2(2)E4 (cat4500e-UNIVERSALK9-M). Standby supervisor version is 15.2(2)E4 (cat4500e-UNIVERSALK9-M). Redundancy feature may not work as expected.

on sw2:

%VSLP-5-VSL_UP: Ready for control traffic
%VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP
%C4K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL: STANDBY:IOS version mismatch. Active supervisor version is 15.2(2)E4 (cat4500e-UNIVERSALK9-M). Standby supervisor version is 15.2(2)E4 (cat4500e-UNIVERSALK9-M). Redundancy feature may not work as expected.
%C4K_REDUNDANCY-2-NON_SYMMETRICAL_REDUNDANT_SYSTEM: STANDBY:STANDBY supervisor will operate in fallback redundancy mode rpr.
%C4K_REDUNDANCY-3-COMMUNICATION: STANDBY:Communication with the peer Supervisor has been established
%C4K_REDUNDANCY-2-VS_REBOOT_ON_RPR_FALLBACK: STANDBY:Supervisor in virtual-switch configuration cannot operate in redundancy mode RPR, will be reset
%RF-5-RF_RELOAD: STANDBY:Self Reload. Reason: Virtual-switch fallback to RPR
%SYS-5-RELOAD: STANDBY:Reload requested by Platform redundancy manager. Reload Reason: Virtual-switch fallback to RPR.

And it just keeps on rebooting as long as the vsl-link is available at boot.

Another thing thats weird is, that sw1 already at some point learned the provisioned modules of sw2. Like, i can see Te2/1/1 of sw2 when i do a 'sh int status' or 'sh run mod 11' on sw1.

Any ideas? So far i tried to convert to standalone and completely reset sw2 to factory defaults, double checking ios versions and licensed features, then rejoining. Did i hit a bug? Why is there a logging line from ISSU anyways, if i'm on litterally the same binary that i copied from sw1 to sw2?

Thanks in advance

[acampbell]

Hi,

Can you share the output from

show redundancy states from the ACTIVE supy

Regards

Alex

[tneumayer]

Hi,

sorry, I pasted the redundancy states above.

I would image the disabled state is "okay", because i had to shutdown the VSL in order to be able to boot the secondary switch into an interactive state.

Cheers

[Reza Sharifi]

Can you post the VSS configs from both switches?

[tneumayer]

switch virtual domain 1
 switch mode virtual
 switch 1 priority 200
 switch 2 priority 50
 mac-address use-virtual
!
redundancy
 mode sso
!
interface Port-channel1
 description VSL-sw1
 switchport
 switchport mode trunk
 switchport nonegotiate
 shutdown
 switch virtual link 1
!
interface TenGigabitEthernet1/1/1
 switchport mode trunk
 switchport nonegotiate
 shutdown
 no lldp transmit
 no lldp receive
 no cdp enable
 channel-group 1 mode on
 service-policy output VSL-Queuing-Policy
!

the shutdown in the Te-Interfaces of sw1 is currently to prevent sw2 from rebooting but coming up as single active switch, so i can interact with it.

sw2 is identical, only that its Po2 instead of 1.

sw1#sh redundancy states
 my state = 13 -ACTIVE
 peer state = 1 -DISABLED
 Mode = Simplex
 Unit = Primary
 Unit ID = 1

 Redundancy Mode (Operational) = Stateful Switchover
 Redundancy Mode (Configured) = Stateful Switchover
 Redundancy State = Non Redundant
 Manual Swact = disabled (system is simplex (no peer unit))

 Communications = Down Reason: Simplex mode

 client count = 82
 client_notification_TMR = 240000 milliseconds
 keep_alive TMR = 9000 milliseconds
 keep_alive count = 0
 keep_alive threshold = 9
 RF debug mask = 0

again, the both are currently not connected by shutting Te1/1/1-2 down.

its the only chance i can boot sw2 into a state where i can interact with it. (except from plugging the two cables of course)

[paul driver]

Hello

dh bootvar
dir bootflash:
dir slavebootflash:

res
Paul

[tneumayer]

sw1#sh bootvar
BOOT variable = bootflash:cat4500e-universalk9.SPA.03.06.04.E.152-2.E4.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2101

Standby not ready to show bootvar

sw1#dir bootflash:
Directory of bootflash:/

15106 -rwx 178288484 May 9 2016 21:31:08 +02:00 cat4500e-universalk9.SPA.03.06.04.E.152-2.E4.bin
15107 -rw- 6815 May 18 2016 07:46:23 +02:00 startup-config.converted_vs-20160518-054623
15108 -rw- 39474 Jun 24 2016 13:21:45 +02:00 startup-config.saved_vs-20160624-112145

851353600 bytes total (672690176 bytes free)
sw-core-1#dir slav
sw-core-1#dir slaveb
sw-core-1#dir slavebootflash:
%Error opening slavebootflash:/ (Error Sending Request)
sw1#

sw2#sh bootvar
BOOT variable = bootflash:cat4500e-universalk9.SPA.03.06.04.E.152-2.E4.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2101

Standby not ready to show bootvar

sw2#sh bootflash:
-#- --length-- ---------date/time--------- path
 1 4939 Jun 24 2016 13:11:13.0000000000 +00:00 startup-config.converted_vs-20160624-131113
 2 178288484 Jun 24 2016 03:13:38.0000000000 +00:00 cat4500e-universalk9.SPA.03.06.04.E.152-2.E4.bin

629526528 bytes available (178581504 bytes used)

sw2#