10-20-2008 09:50 AM - edited 03-06-2019 02:02 AM
Hi,
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.
Output:
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
10-20-2008 10:13 AM
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.
see
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
Giuseppe
01-14-2011 07:18 PM
Giuseppe Larosa wrote:
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.
see
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
Giuseppe
It's quite useful, I got more deep understanding about this part, Thanks for your instruction!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: