06-29-2024 08:02 AM
Hi
We're running a Cisco 9800-CL (17.12.3), and we offer a guest Wi-Fi.
We're using the built-in "guest system" and captive portal.
This is working as expected.
During planned maintenance the WLC did a failover from active to standby unit.
After the failover, the captive portal no longer shows up for the guest user.
I had to do a "redundancy force-failover" to promote the standby unit to active to get it back online.
Any explanation why the captive portal doesn't kick in when we're running of the standby WLC?
Solved! Go to Solution.
07-01-2024 05:28 AM
Yes it is sounding buggy hence my suggestion to get TAC involved.
07-05-2024 05:06 AM
I wanted to provide an update on the recent captive portal issue.
I added the "wireless mobility MAC address" to the WLC cluster and performed a redundancy force-switchover. Following this, the user was able to access the captive portal, which suggested that the issue had been resolved.
To verify the solution, I removed the wireless mobility MAC address and repeated the entire procedure. Surprisingly, the captive portal continued to function correctly even without the "wireless mobility MAC address" configured.
While the exact cause of the issue remains unclear, I will keep the wireless mobility MAC address configured as a precautionary measure.
07-05-2024 05:23 AM
- It would then be interesting , if configured to check if Wireless Config Analyzer still gives this error :
High Availability: Redundancy mac address is not set. This is mandatory configuration value if using redundancy feature
=?
M.
07-05-2024 05:28 AM
I ran the Config Analyzer, and the error is not reported when the command/config is set.
/Kenneth
07-05-2024 06:33 AM
- So it is needed then , good to know,
M.
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