Wireless Roaming Troubleshooting Guide

Contents

Objective

Requirements

Introduction

Troubleshooting

Troubleshoot for Network Configuration

Troubleshoot for AP Deployment

Troubleshoot for Client-side Behavior

Conclusion

Overview:

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.

Required Items:

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

Troubleshooting: 

Troubleshooting the 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 Lock to AP enabled. Lock to AP keeps the client connected to the current AP.

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

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

Step 7. Check if the SSID is being broadcasted from another vendor’s network. This may cause wireless clients to stop associating with the Omada network, leading to a roaming failure.

Troubleshooting AP Deployment:

Step 1. If adjacent APs are placed too far apart, it will result in poor overlap and weak signal areas. In such cases, clients may switch back and forth between the two APs.  Increasing the number of APs or adjusting the AP's transmit power can lead to improved network performance.

Step 2. If adjacent APs are placed too close together, clients may refuse to roam as the signal to the connected AP is still strong. In such cases, it is recommended to lower the AP transmit power to reduce overlap or increase the distance between APs.  You may also consider enabling AI Roaming.

Troubleshooting Client Behavior:

Step 1. Check if only the specific client is experiences roaming concerns. Confirm whether the client supports the 802.11k/v protocol. If supported, update the client's software to its 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.