Cisco Wireless LAN Controllers: Seamless Roaming Configuration

Seamless Roaming Configuration

Question

A company has an existing Cisco 5520 HA cluster using SSO.

An engineer deploys a new single Cisco Catalyst 9800 WLC to test new features.

The engineer successfully configures a mobility tunnel between the 5520 cluster and 9800 WLC.

Clients connected to the corporate WLAN roam seamlessly between access points on the 5520 and 9800 WLC.

After a failure on the primary 5520 WLC, all WLAN services remain functional; however, clients cannot roam between the 5520 and 9800 controllers without dropping their connection.

Which feature must be configured to remedy the issue?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B.

The issue described in this scenario is that after the primary 5520 WLC fails, clients cannot roam between the 5520 and 9800 WLCs without dropping their connection. This indicates that there is a problem with the mobility configuration between the two WLCs.

When clients roam between WLCs, the mobility feature enables a seamless handoff by allowing the client's MAC address to move from one controller to the other. To facilitate this, each WLC is assigned a unique mobility group name, and a common mobility domain is created between the WLCs. In this scenario, it appears that the mobility configuration between the 5520 and 9800 WLCs was working correctly before the 5520 WLC failure, but it is not functioning properly after the failure.

To remedy this issue, it is necessary to identify and correct the mobility configuration on one or both of the WLCs. The answer to the question asks which feature must be configured to remedy the issue, and the options are:

A. mobility MAC on the 5520 cluster B. mobility MAC on the 9800 WLC C. new mobility on the 5520 cluster D. new mobility on the 9800 WLC.

Option A and B both refer to the mobility MAC address, which is a unique MAC address assigned to each WLC in a mobility group. This address is used to identify the WLCs to each other and is used in the mobility messages exchanged between the WLCs. However, simply configuring or changing the mobility MAC address on one or both of the WLCs is unlikely to solve the issue described in the scenario.

Option C and D refer to creating a new mobility configuration on one or both of the WLCs. This could potentially solve the problem, but it is not a recommended approach as it would require a complete reconfiguration of the mobility feature. Instead, it is recommended to troubleshoot and identify the root cause of the issue, which could be related to any number of factors, such as a misconfiguration of the mobility group, a problem with the mobility tunnel, or an issue with the failover behavior of the WLCs.

In summary, to remedy the issue described in the scenario, it is recommended to troubleshoot and identify the root cause of the problem with the mobility configuration between the 5520 and 9800 WLCs, rather than simply configuring a new mobility configuration or changing the mobility MAC address.