Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

5508 unable to form redundant pair

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

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

5508 unable to form redundant pair

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?

8 REPLIES

5508 unable to form redundant pair

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

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

5508 unable to form redundant pair

My apologies, it is corrected now. Those are the changed values as provided to me by the subsidary where these wlc's reside.

Hall of Fame Super Gold

5508 unable to form redundant pair

Stupid question:  Both WLC are running the same firmware?

New Member

5508 unable to form redundant pair

yes both are running the same firmware versions.

Hall of Fame Super Gold

5508 unable to form redundant pair

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?

New Member

5508 unable to form redundant pair

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?

Hall of Fame Super Gold

5508 unable to form redundant pair

Are the Redundancy Ports of both WLC directly connected to each other?

New Member

5508 unable to form redundant pair

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.

612
Views
4
Helpful
8
Replies
CreatePlease to create content