In a certain enterprise office WLAN network, network engineers found that many APs were offline for a long time after being disconnected, or were offline again after being online. Which of the…

Question

Options

• AThe AP's peer device has SIP enabled, but the AP has not.
• BThe AP is not assigned an IP address
• CInsufficient license resources
• DWAC does not support this AP type

• A
  72% (31)
• B
  9% (4)
• C
  2% (1)
• D
  16% (7)

Explanation

Option A is correct because when the switch (peer device) connected to an AP has a link-state or loop-prevention protocol like STP/SIP enabled-but the AP's port isn't configured as an edge/fast port-every reconnection triggers a port convergence delay (up to 30 seconds for classic STP). During this window the AP cannot re-establish its CAPWAP tunnel to the WAC, which perfectly explains both the prolonged offline periods and the repeated drop-reconnect cycles. Option B is wrong because a missing IP address would prevent the AP from coming online at all, not cause intermittent drops. Option C is wrong because a license shortage would block AP registration consistently from the start, not produce the on-again/off-again pattern described. Option D is wrong because an unsupported AP type would result in a permanent failure during the initial handshake, not repeated cycling between online and offline states.

Memory tip: Think "convergence delay = lingering offline." Whenever you see APs that take unusually long to recover after a link bounce, suspect a spanning-tree or similar protocol on the upstream switch port that is holding the port in a non-forwarding state-configure it as an edge port (PortFast) to fix it.

No community discussion yet for this question.