10-28-2016 07:12 AM - edited 07-05-2021 06:03 AM
Hi,
what is the difference between "Joined" and "Connected" AP status on Cisco 5508 wireless controller in HA configuration?
I have two WLC 5508 in HA configuration. In 3 october the controller switchovered with reason "Active controller failed" (attached file 1). I tried to understand why the controller was failed, but I haven't find the reason.
Now, there are a lot of AP (not all) in the "Connected status" and not in "Joined status" (attached file 2).
What is meaning ? and why in the "AP join stats details" (attached file 3 and 4) tha AP are both in joined status ? It is a licence problem ? Can I resolve this problem with a manual switchover to main controller ?
Thank you for help
Solved! Go to Solution.
10-30-2016 06:13 AM
Due to the failure you are now running on the secondary WLC. There is no direct harm in doing so because the primary controller already joined the HA-SSO setup again. The only downside (depending on your wired network infrastructure and if you use central switching) might be that client traffic flows are less ideal because they are now bridged on the second distribution or core switch.
These different access-point statuses are just to inform you about when the access-point(s) joined the current active controller:
Synched | The access-point joined the controller before the SSO |
Connected | The access-point joined the controller after the SSO |
Joined | The access-point rejoined the controller, or a new AP has joined the controller after the SSO |
Please rate useful posts... :-)
11-01-2016 03:02 PM
You have a license for 250 AP on your primary controller and the secondary is a HA SKU or has at least 50 AP license to act like a HA.
As long as the primary unit is available for the (active) secondary unit it will not perform the countdown. That 90 days are only applicable if the primary unit is unavailable for more than 90 days in a row. If the (active) secondary looses power and the primary is not available when it boots again, it will go to maintenance mode.
Please rate useful posts... :-)
10-30-2016 06:13 AM
Due to the failure you are now running on the secondary WLC. There is no direct harm in doing so because the primary controller already joined the HA-SSO setup again. The only downside (depending on your wired network infrastructure and if you use central switching) might be that client traffic flows are less ideal because they are now bridged on the second distribution or core switch.
These different access-point statuses are just to inform you about when the access-point(s) joined the current active controller:
Synched | The access-point joined the controller before the SSO |
Connected | The access-point joined the controller after the SSO |
Joined | The access-point rejoined the controller, or a new AP has joined the controller after the SSO |
Please rate useful posts... :-)
10-31-2016 09:11 AM
Thank you Freerk.
The infrastructure it's ok to have the secondary like primary controller.
I'm a little confusing for licence: I have a permanent licence on both controllers (attached file 5) right? So I don't need to force a switchover, the 90-day counter will not start and all AP will work normally after 90 days, I'm right ?
Tanks
11-01-2016 03:02 PM
You have a license for 250 AP on your primary controller and the secondary is a HA SKU or has at least 50 AP license to act like a HA.
As long as the primary unit is available for the (active) secondary unit it will not perform the countdown. That 90 days are only applicable if the primary unit is unavailable for more than 90 days in a row. If the (active) secondary looses power and the primary is not available when it boots again, it will go to maintenance mode.
Please rate useful posts... :-)
11-02-2016 02:37 AM
Very clear reply Freerk, thank you very much.
Regards
11-02-2016 04:08 PM
Glad I could help! Could you please mark your question as answered? This helps fellow engineers which have the same question :-)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide