show redundancy states

Unanswered Question
Oct 20th, 2008
User Badges:


After configuring the SSO on dual cat 6500 chassis, I do not see the peer state as '-STANDBY HOT'.

Please advise why would this happen. SSO is configured by default, and a trunk has been defined between the chassis.


MYSWITCH#sh redundancy states

my state = 13 -ACTIVE

peer state = 1 -DISABLED

Mode = Simplex

Unit = Primary

Unit ID = 5

Redundancy Mode (Operational) = sso

Redundancy Mode (Configured) = sso

Redundancy State = Non Redundant

Maintenance Mode = Disabled

Communications = Down Reason: Simplex mode

client count = 91

client_notification_TMR = 30000 milliseconds

keep_alive TMR = 9000 milliseconds

keep_alive count = 0

keep_alive threshold = 18

RF debug mask = 0x0

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Giuseppe Larosa Mon, 10/20/2008 - 10:13
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello New,

there is no communication between the two supervisors:

Communications = Down Reason: Simplex mode

peer state = 1 -DISABLED

the state of the other supervisor is disabled (this is the point of view of the current supervisor)

if this is a VSS the following requirements apply:

A virtual switching system operates with stateful switchover (SSO) redundancy if it meets the following requirements:

•Both supervisor engines must be running the same software version.

•VSL-related configuration in the two chassis must match.

•PFC mode must match.

•SSO and nonstop forwarding (NSF) must be configured on each chassis.


I would suggest to use a console connection and check if the other supervisor is stucked in rommonitor or other possible issue

Hope to help



This Discussion