Quad sup2T VSS redundancy

krun_shah · ‎11-05-2013

hi folks,

Question regarding VSS with Quad sup.

It looks like with one switch being down you do not get any redundacy for remaining switch even though it has two supervisors is it true?

I have following config and I cabled 4 tengig port of supevisor with 5 to 5 and swap6 rule.

GW6500-VSS#sh switch virtual redundancy mismatch

No Config Mismatch between Active and Standby switches

ONX-GW6500-VSS#sh switch virtual redundancy

My Switch Id = 1

Peer Switch Id = 2

Last switchover reason = none

Configured Redundancy Mode = sso

Operating Redundancy Mode = sso

Switch 1 Slot 5 Processor Information :

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

Current Software state = ACTIVE

Uptime in current state = 21 hours, 35 minutes

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

Technical Support: http://www.cisco.com/techsupport

Compiled Tue 01-Oct-13 12:54 by prod_rel_team

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

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

Fabric State = ACTIVE

Control Plane State = ACTIVE

Switch 1 Slot 6 Processor Information :

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

Current Software state = STANDBY HOT (CHASSIS)

Uptime in current state = 21 hours, 34 minutes

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

Technical Support: http://www.cisco.com/techsupport

Compiled Tue 01-Oct-13 12:54 by prod_rel_team

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

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

Fabric State = ACTIVE

Control Plane State = STANDBY

Switch 2 Slot 5 Processor Information :

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

Current Software state = STANDBY HOT (switchover target)

Uptime in current state = 21 hours, 32 minutes

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

Technical Support: http://www.cisco.com/techsupport

Compiled Tue 01-Oct-13 12:54 by prod_rel_team

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

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

Fabric State = ACTIVE

Control Plane State = STANDBY

Switch 2 Slot 6 Processor Information :

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

Current Software state = STANDBY HOT (CHASSIS)

Uptime in current state = 21 hours, 32 minutes

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

Technical Support: http://www.cisco.com/techsupport

Compiled Tue 01-Oct-13 12:54 by prod_rel_team

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

CONFIG_FILE =

BOOTLDR =

Configuration register = 0x2102

Fabric State = ACTIVE

Control Plane State = STANDBY

krun_shah · ‎11-05-2013

According to following default redundancy domain is always accross chassis.

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-729039.html

I would like to know if there is a command to transfer switchover target state to second supervisor available within chassis when second chassis is out of service for what ever reason. When second chassis is available we can issue some command taht will make default redundancy domain back to original accross two chassis when boot second chassis.

Jose Solano · ‎11-05-2013

Hi,

See this statement:

The default redundancy domain is the domain established for the overall VSS itself. The default redundancy domain's active and standby supervisor modules are designed to always exist across chassis. Alternatively, the new in-chassis redundancy domain exists only within a single chassis. Each VSS chassis establishes its own in-chassis redundancy domain, which is independent of the other chassis.

krun_shah · ‎11-06-2013

But with only in-chassis redundancy domain there is no SSO.