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
