Configuration Issue Causing Network Connectivity Outage for Roaming Wireless Clients

Wireless Controllers Roaming Configuration Issue

Question

When a wireless client roams between two different wireless controllers, a network connectivity outage is experienced for a period of time.

Which configuration issue would cause this problem?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/107188-mobility-groups-faq.html

When a wireless client roams between two different wireless controllers, a network connectivity outage can occur for a period of time. This is because the client needs to disconnect from one controller and connect to another controller, which can take some time to complete.

The mobility group feature in Cisco wireless LAN controllers allows multiple controllers to work together as a single system, providing seamless wireless access and mobility for clients. The mobility group consists of a set of controllers that share information about wireless clients and coordinate their actions to provide seamless roaming.

Option A, "Not all of the controllers in the mobility group are using the same mobility group name," is unlikely to cause the problem because the mobility group name is used only to identify the group of controllers that are working together. It does not affect the roaming or connectivity of wireless clients.

Option B, "Not all of the controllers within the mobility group are using the same virtual interface IP address," is a possible cause of the problem. When a wireless client roams between controllers, it needs to obtain a new IP address from the new controller. If the new controller is using a different virtual interface IP address, the client may not be able to obtain a new IP address, which could result in a network connectivity outage.

Option C, "All of the controllers within the mobility group are using the same virtual interface IP address," is also a possible cause of the problem. If all controllers are using the same virtual interface IP address, the wireless client may not be able to determine which controller to connect to, which could result in a connectivity outage.

Option D, "All of the controllers in the mobility group are using the same mobility group name," is unlikely to cause the problem for the same reason as option A.

In summary, the most likely configuration issue that would cause a network connectivity outage when a wireless client roams between two different wireless controllers is that not all of the controllers within the mobility group are using the same virtual interface IP address.