Troubleshooting guide of roaming

Contents

Objective

Requirements

Introduction

Troubleshooting

Troubleshoot for Network Configuration

Troubleshoot for AP Deployment

Troubleshoot for Client-side Behavior

Conclusion

Objective

Roaming is a typical feature for wireless network scenarios. Factors such as network configuration, AP deployment and client-side behavior can all affect the effectiveness of roaming. This article describes how to troubleshoot problems encountered during roaming.

Requirements

• Omada AP
• Omada Controller (Software Controller/Hardware Controller/CBC, v5.9 and above)
• Omada App

Introduction

Roaming is a typical feature for wireless network scenarios. Factors such as network configuration, AP deployment and client-side behavior can all affect the effectiveness of roaming. This article describes how to troubleshoot problems encountered during roaming.

Troubleshooting

Troubleshoot for Network Configuration

Check if the issue is caused by network configuration.

Step 1. Verify if the target AP's SSID matches the SSID the client is currently connected to. In a roaming scenario, all APs must use the same SSID (including SSID name, security method, etc.). Roaming will fail if the target AP's SSID differs in name or security method from the one the client is connected to.

Step 2. Check if all APs are within the same site. Roaming policies can only take effect when the APs are within the same site.

Step 3. Ensure that Fast Roaming is enabled (enabled by default on Omada Controller version 5.14 and above).

Step 4. Check if the client has enabled Lock to AP, which keeps it connected to the current associated AP.

Step 5. Check if 802.11r is enabled. Some clients does not support 802.11r protocol. Please disable 802.11r and try again.

Step 6. Check if the target AP has a high load or is already overloaded. When the target AP has a high load or is overloaded, it may reject new client connections, leading to roaming failure.

Step 7. Check for the presence of same SSID from other vendors' networks in the wireless environment, which may cause wireless clients to stop associating with Omada AP, leading to a roaming failure.

Troubleshoot for AP Deployment

Check if the APs are reasonably deployed. Use the Network Tools function in the Omada App to check the signal coverage of APs.

Step 1. If adjacent APs are placed too far apart, it will result in a large overlap of weak signal areas. In such cases, clients may roam back and forth between the two APs. Increasing the number of APs or adjusting the AP's transmit power can reduce the overlap of weak signal areas.

Step 2. If adjacent APs are placed too close together, clients may not be able to reach the roaming threshold when moving between the two APs, resulting in unsuccessful roaming. In such cases, it is recommended to lower the AP transmit power to reduce overlap of signal coverage areas or enable AI Roaming.

Troubleshoot for Client-side Behavior

Check if the roaming issues are caused by client-side behavior.

Step 1. Check if only the specific client experiences delays in roaming. Confirm whether the client supports the 802.11k/v protocol. If supported, update the client's driver software to the latest version and try again.

Step 2. Check if only the specific client cannot access the internet after roaming. Confirm whether the client supports the 802.11r protocol. If not, disable 802.11r and try again.

Conclusion

This article analyzes roaming troubleshooting from three aspects: network configuration, AP deployment, and the client-side behavior. If the client is experiencing problems while roaming, you can troubleshoot by following the steps above.

Get to know more details of each function and configuration please go to Download Center to download the manual of your product.