300-425 · Question #127
WLC SSO is set up between two WLCs in a service provider network serving public spaces. On WLC failover, it is noticed that only about half of the original client count is now showing on the…
The correct answer is B. The WLCs had not completed database sync before the primary failure. When a Wireless LAN Controller (WLC) SSO is set up between two WLCs in a service provider network, and there is a failover, the secondary WLC should ideally support the same client count as the primary. If only about half of the original client count is showing on the secondary…
Question
WLC SSO is set up between two WLCs in a service provider network serving public spaces. On WLC failover, it is noticed that only about half of the original client count is now showing on the secondary WLC, although it is currently showing the role as active. Which design side case explains the issue?
Options
- AThe secondary WLC platform does not support the required client count.
- BThe WLCs had not completed database sync before the primary failure.
- CSSO is not configured correctly.
- DSome client sessions were in WebAuth-Req state before failover.
How the community answered
(42 responses)- A21% (9)
- B60% (25)
- C5% (2)
- D14% (6)
Explanation
When a Wireless LAN Controller (WLC) SSO is set up between two WLCs in a service provider network, and there is a failover, the secondary WLC should ideally support the same client count as the primary. If only about half of the original client count is showing on the secondary WLC post- failover, it suggests that the WLCs had not completed the database synchronization before the primary WLC failed. This incomplete sync would result in a loss of client information, leading to a reduced client count on the secondary WLC.
Topics
Community Discussion
No community discussion yet for this question.