Why were the APs unable to rejoin the Cisco WLC, and how can you prevent this from happening in the future?

After a scheduled downtime of your 5508 WLC, you notice that only a handful of the 100 APs are
rejoining the controller. All the APs are in the same subnet and use default settings. Cisco WLC
debugs indicate that the APs are sending discovery and join requests. Only after shutting down all
the switch ports that connect to the APs and turning five ports back on at a time can you rejoin all
the APs. Why were the APs unable to rejoin the Cisco WLC, and how can you prevent this from
happening in the future?

After a scheduled downtime of your 5508 WLC, you notice that only a handful of the 100 APs are
rejoining the controller. All the APs are in the same subnet and use default settings. Cisco WLC
debugs indicate that the APs are sending discovery and join requests. Only after shutting down all
the switch ports that connect to the APs and turning five ports back on at a time can you rejoin all
the APs. Why were the APs unable to rejoin the Cisco WLC, and how can you prevent this from
happening in the future?

A.
Having all the APs in the same VLAN created a Layer 2 broadcast storm, preventing the APs
from receiving discovery and join responses from the Cisco WLC. You can prevent this by
configuring the APs to send syslog messages to a multicast address, using the Cisco WLC CLI
only.

B.
Having all the APs in the same VLAN created a Layer 2 broadcast storm, preventing the APs
from receiving discovery and join responses from the Cisco WLC. You can prevent this by
configuring the APs to send syslog messages to a unicast address, using the Cisco WLC CLI only.

C.
Having all the APs in the same VLAN created a Layer 3 broadcast storm, preventing the APs
from receiving discovery and join responses from the Cisco WLC. You can prevent this by
configuring the APs to send syslog messages to a unicast address, using the Cisco WLC CLI only.

D.
Having all the APs in the same VLAN created a Layer 2 broadcast storm. You cannot
prevented this from happening again.



Leave a Reply 0

Your email address will not be published. Required fields are marked *