I have two 2504 wireless LAN controller that are plugged into the LAN. One as primary and the other as backup.
When I disconnect the primary, the backup must take control of the WIFI access points but no one devices can connect to them.
I waited a few minutes but nothing changed.
Primary controller (before unplugging) :
Backup controller (after unplunning the primary):
When I reconnect the primary, it takes control of the WIFI access points and all devices can connect to them.
Both are connected in trunk, are on the same authorized VLAN and connected in gigabit ethernet.
Here are the configurations I made on the primary controller :
For the last screen I made the same for the secondary controller.
Also both are the same software version.
If you want more precision, i am listening.
2504 does not support HA SSO, so, dont matter the Redundanty config. What will be necessary is the High Availability on the WIRELESS page.
Can you try to add one AP to the secondary and see if at least the AP hits there? You can take one AP and add the Seconday IP address as the Primary and reload the AP.
Then, look at the Secondary WLC and see in Monitor> Statistics> AP join
On this page you shared, if you click over the AP name, you have the 'not join reason' but one important thing here is that the AP is able to hit the secondary WLC. With that, we can eliminate network issue and focus on the WLC.
On the secondary WLC chech a few thing please:
- Is the license activated?
Go to MANAGEMENT tab, Software Activation, at least one base-ap-cont license must be active. Dont matter if permanent or evaluation
-The Data and time is correct?
Go to COMMANDS tab and check.
- The Country Code is correct?
Go to WIRELESS tab and check.
Long story short, Open the Primary WLC GUI and the Secondary WLC GUI and put both on your screen and check each TAB comparing one with other and you are going to find what is missing on the Secondary.
This ? :
Last Error Summary
Last AP Message Decryption Failure -
Last AP Connection Failure Timed out while waiting for ECHO repsonse from the AP
Last AP Disconnect Reason Unknown failure reason
Last Error Occurred AP got or has been disconnected
Last Error Occurred Reason Timed out while waiting for ECHO repsonse from the AP
Last Join Error Timestamp May 03 08:46:51.762
Dont think so. This is related to AP priority. We can setup higher priority for some APs. In case we are running out of licensing for example, the WLC will prioritize some specific AP we choose. This feature just tell this WLC to respect that priority in case the AP migrates to this WLC.
About your problem, I am already out of idea. The critical points I mentioned seems to be OK. Wondering if you could by change reload the WLC, if did not yet.
As the AP hits the WLC and not join and the config seems ok, we can think in something related to faulty software.