11-20-2013 07:04 AM - edited 07-04-2021 01:18 AM
Hi,
We have two 5508 controllers which were actually working fine in ap sso mode when it was initially configured. Due to a recent network move, both 5508 were removed from current location & installed at another location.
When we re-installed & connected all the connections, the ap sso is not forming and it says Unknown-Communication down & goes into maintenance mode.
(Cisco Controller-1) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = ACTIVE
Peer State = UNKNOWN - Communication Down
Unit = Primary
Unit ID = 6C:41:6A:5E:E7:00
Redundancy State = Non Redundant
Mobility MAC = 6C:41:6A:5E:E7:00
Redundancy Management IP Address................. 10.20.15.17
Peer Redundancy Management IP Address............ 10.20.15.18
Redundancy Port IP Address....................... 169.254.15.17
Peer Redundancy Port IP Address.................. 169.254.15.18
Cisco Controller-2) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = MAINTENANCE
Peer State = UNKNOWN - Communication Down
Unit = Secondary - HA SKU
Unit ID = 10:F3:11:9A:04:20
Redundancy State = Non Redundant
Mobility MAC = 6C:41:6A:5E:E7:00
Maintenance Mode = Enabled
Maintenance cause= Negotiation Timeout
Redundancy Management IP Address................. 10.20.15.18
Peer Redundancy Management IP Address............ 10.20.15.17
Redundancy Port IP Address....................... 169.254.15.18
Peer Redundancy Port IP Address.................. 169.254.15.17
We tried disabling sso on secondary , followed by reboot but it didn't work
Some of the messages as seen during the process are :
WARNING: If peer unit's management and/or redundancy management entries are present as mobility
members please remove them before enabling redundancy.
Management Gateway and Peer Redundancy Management interface are not reachable.
Entering maintenance mode...
Please help with suggestions. Thanks
Message was edited by: sunny thomas
Solved! Go to Solution.
11-20-2013 04:22 PM
Maintenance cause= Negotiation Timeout
This means the two WLC can't see each other to establish a redundancy.
Can you describe the VLAN and subnet of the Management IP address?
11-20-2013 07:17 AM
it doesn't appear that your management addresses are in the same subnet. on is .15 the other is .5, but the redundancy port is showing both should be .15
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
11-20-2013 07:30 AM
My apologies, it is corrected now. Those are the changed values as provided to me by the subsidary where these wlc's reside.
11-20-2013 12:07 PM
Stupid question: Both WLC are running the same firmware?
11-20-2013 03:58 PM
yes both are running the same firmware versions.
11-20-2013 04:22 PM
Maintenance cause= Negotiation Timeout
This means the two WLC can't see each other to establish a redundancy.
Can you describe the VLAN and subnet of the Management IP address?
11-20-2013 05:00 PM
Management VLAN : Vlan 15 - 10.20.15.0 /24
10.20.15.15 is the management interface ip for primary wlc.
Do i need to configure secondary management ip or will it attach itself to the primary?
11-20-2013 05:30 PM
Are the Redundancy Ports of both WLC directly connected to each other?
11-21-2013 07:33 AM
Thank you everyone for the inputs.
This was resolved, as pointed by Leo, we ended up tracing the patch cords & the ones connected on the second controller was found to be wrongly linked to a different port than what was configured for it.
Appreciate all inputs.
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: