Contents
Configuration for Layer 2 Device Discovery
Configuration for Layer 3 Device Discovery
Objective
This article intends to help customers discover their Omada devices via the Software Controller and Hardware Controller.
Requirements
- Omada Devices
- Omada Controller (Software Controller/Hardware Controller)
Introduction
You can discover your Omada devices through simple configurations with the Omada Software and Hardware Controller. After device discovery, you can adopt and manage your devices according to your needs. Generally, the Software Controller and Hardware Controller support discovering your Omada Devices through Layer 2 and Layer 3 networks：
- Discovering devices at Layer 2: This scenario means that the Omada devices exist in the same network as the Controller’s. For example, a device's IP address is 192.168.0.x/24, and the Controller's is 192.168.0.y/24. This scenario mainly applies to small-scale networks and fewer easily managed devices.
- Discovering devices at Layer 3: This scenario means that the Omada devices exist in a different network from the Controller’s. For example, a device's IP address is 192.168.0.x/24, and the Controller's is 192.168.1.x/24. This scenario mainly applies to large-scale deployments with more devices and separated sites where the devices are physically far away from the Controller.
Configuration for Layer 2 Device Discovery
Step 1. Connect your Omada devices and your Controller to the same network.
Step 2. Confirm that your devices are accessible to the Controller.
- Hardware Controller:
1. Log in to your Controller through the IP address of your Controller via browser.
2. Go to Global View > Settings > Network Check. Input the IP address of your device into the Domain/IP Address field. Set the Packet Size and Count according to your needs.
3. Click Run. Find the test result in the following Device Output section.
- Software Controller:
1. On the PC where your Software Controller runs, press "win+R" to open the Run window, enter cmd, and then press OK to access the command line.
2. Use the ping command to check the accessibility between your Controller and your device.
Step 3. After confirming that your devices are accessible to the Controller, they will appear in the list of Unknown Devices within the Controller. Refer to the Verification section for more detailed instructions.
Configuration for Layer 3 Device Discovery
To discover your Omada devices on a Layer 3 network, you need to provide your controller's IP address to the devices. Typically, we achieve this using the following methods: DHCP Option, Discover Utility, and Inform URL.
This method is commonly used to adopt APs and Switches. We use the DHCP server to deliver the controller's IP address to Omada devices. DHCP Options 138 and 43 are commonly used for this purpose. You can select the appropriate option based on your requirements. Here, we use DHCP Option 138 as an example to introduce the configuration process:
Step 1. Log in to your Controller via web browser and adopt the Omada gateway as a DHCP Server for your Controller.
Step 2. Go to Site View > Settings > Wired Network > LAN > Networks. Click the Action button.
Step 3. Go to Advanced DHCP Options, input the Controller’s IP address into Option 138, then click Save.
Step 4. Connect your Switches or APs to your gateway. The IP address of your Controller will be delivered to your devices through DHCP Option 138.
Discovery Utility
Step 1. Install the Discovery Utility on your PC by referring to How to Install TP-Link Omada Discovery Utility on Windows and macOS PCs.
Step 2. Connect your PC to the same network as your Omada devices and run the Discovery Utility. Then select the Omada device you are going to adopt and click Manage.
Step 3. Input the following information to the pop-up window and click Apply.
Center IP/Inform URL: The IP address of your Controller.
Username: The username when you log in to the management page of your device.
Password: The password you use when you log in to the management page of your device.
Step 4. After clicking Apply, the Status of the Device Information window will change from Pending to Adopting, Configuring, and then to Setting Succeed. Once it shows Setting Succeed, the IP address of your Controller has been successfully delivered to your device.
Connect a PC to the same network as your Omada devices and log in to the management page of your device by accessing its IP address in the browser.
- AP: Go to System > Controller Settings > Controller Inform URL. Input the IP address of your Controller in Inform URL/IP Address and click Save.
- Switch: Go to SYSTEM > Controller Settings > Controller Inform URL. Input the IP address of your Controller in Inform URL/IP Address and click Save.
- Gateway: Go to System Tools > Controller Settings > Controller Inform URL. Input the IP address of your Controller in Inform URL/IP Address and click Save.
Log in to your Controller via web browser, go to Global View > Unknown Devices. If you have successfully configured your Omada devices via Layer 2 and Layer 3, your devices will appear in the Unknown Devices list.
Your Omada Software/Hardware Controller has successfully discovered your Omada devices.
FAQ
What Should I Do If I Fail to Discover the Devices via the Local Controller?
Re. Please refer to the following steps for troubleshooting:
Step 1. Ensure the network your device is connected to is functioning correctly. Verify that all switch ports between the device and the gateway/DHCP server are configured with the correct VLAN tags and that there are no issues, such as network loops, present in the network.
Step 2. Check the communication between the device and the Controller:
- If the device and the Controller are in the same network or VLAN, use the built-in ping tool on the Hardware/Software Controller or perform the ping command on the PC running the Software Controller to the device IP address to ensure the device is reachable.
- If the device and the Controller are in different networks or VLANs, check your Layer 3 network configurations and whether you have already enabled device adoption in a different network via DHCP Option 138/Discovery Utility/Inform URL.
Step 3. Check whether firewalls or antivirus software have blocked or turned off the following ports in the network. For Software Controller users, check the port's status connected to the PC that runs the Controller.
|
Port |
Hardware Controller |
Software Controller |
Note |
|
29810 |
√ |
√ |
Discover |
|
29814 |
√ |
√ |
Manage |
|
29815 |
√ |
√ |
Manage |
|
29816 |
√ |
√ |
Manage |
|
29811/29812 |
√ |
√ |
Manage |
|
19810 |
√ |
√ |
OLT devices |
What Should I Do If I Can’t Discover an AP Wirelessly？
Re. Please refer to the following steps for troubleshooting:
Step 1. Make sure your APs are powered on and functioning correctly.
Step 2. Appropriately shorten the linear distance between the wireless APs.
Step 3. Move obstacles away to reduce their impact on wireless signals and wireless channel utilization between your APs.
