300-365 · Question #14
By default, how long does a Mobility Services Engine wait for an echo response from a Wireless LAN Controller before declaring the neighbor dead?
The correct answer is D. 30 Seconds. The Cisco Mobility Services Engine uses a default 30-second echo timeout before declaring a WLC neighbor dead. This timer governs MSE-to-WLC heartbeat adjacency.
Question
By default, how long does a Mobility Services Engine wait for an echo response from a Wireless LAN Controller before declaring the neighbor dead?
Options
- A10 Seconds
- B60 Seconds
- C15 Seconds
- D30 Seconds
How the community answered
(19 responses)- C5% (1)
- D95% (18)
Why each option
The Cisco Mobility Services Engine uses a default 30-second echo timeout before declaring a WLC neighbor dead. This timer governs MSE-to-WLC heartbeat adjacency.
10 seconds is not the default MSE echo timeout; this value is too short and does not match the documented Cisco MSE neighbor dead-detection interval.
60 seconds exceeds the default timer and corresponds to different protocol keep-alive contexts, not the MSE-to-WLC dead detection window.
15 seconds is not the configured default for MSE neighbor dead detection and does not appear in Cisco MSE baseline configuration documentation.
By default, the Cisco MSE waits 30 seconds for an echo reply from a paired WLC before marking that controller as a dead neighbor. If the echo response is not received within this window, the MSE terminates services dependent on that WLC connection and logs the neighbor as unreachable. This value is configurable in the MSE administration interface but the factory default is 30 seconds.
Concept tested: MSE to WLC neighbor dead detection default timer
Source: https://www.cisco.com/c/en/us/td/docs/wireless/mse/3350/7-6/MSE_CAS_Configuration_Guide/MSE_CAS_Configuration_Guide_chapter_01.html
Topics
Community Discussion
No community discussion yet for this question.