How to Adopt Devices Remotely with Omada Controller

 

Take the following as an example. The HQ and branch office of a company need to be connected over the internet. The HQ office has the Omada Controller and a TL-ER7206 in subnet 192.168.1.0/24. In the branch office, there is an EAP660 HD, TL-SG3210 and TL-ER7206 in subnet 192.168.0.0/24. We need to configure the networks so that the devices in the branch office can be managed by the Controller in HQ.

 

 

 

Step 1. Configure Port Forwarding rules on the Gateway in HQ

 

Please go to Transmission > NAT > Virtual Server and configure a virtual server for TCP & UDP ports ranging from 29810 to 29813, as shown in the screenshot below.

 

 

 

Step 2. Select one of three methods to discover the Omada devices in branch office.

 

Method 1: Discovery Utility

 

Run the Omada Discovery Utility from a computer in the Branch Office, select the Omada devices and click Batch Setting. Fill in the Controller Hostname/IP with WAN IP address of the Gateway in HQ which is 172.30.30.199 and the Username/Password of the Omada devices. At last, click “Apply”. The default Username/Password of the devices are admin/admin. If the Username and Password of Omada devices are not the same, please add the devices one by one.

 

 

 

Method 2: Controller Inform URL

 

In Standalone mode, please go to System Tools/System-Controller settings of every Omada device. Fill in the Controller IP/Inform URL with the WAN IP address of the Gateway in HQ, then click Apply.

 

 

Configuration screenshot of TL-ER7206 Controller Settings in standalone mode.

 

 

 

Configuration screenshot of TL-SG3210 Controller Settings in standalone mode.

 

 

 

Configuration screenshot of EAP660 HD Controller Settings in standalone mode.

 

 

 

Method 3: DHCP Option 138

 

Use Omada Discovery Utility or set Controller Inform URL to adopt the TL-ER7206 in branch office. And then go to Settings > Wired Networks > LAN > Networks, click in the ACTION column of the LAN where the DHCP clients are located. Enable DHCP Server and configure common DHCP parameters. Then click Advanced DHCP Options and specify Option 138 as the controller’s IP address, which is the WAN IP of TL-ER7206 in HQ. Click Save.

 

To make DHCP Option 138 take effect, you need to renew DHCP parameters for the DHCP clients.

One possible way is to disconnect the switch and EAP and then reconnect them.

Note: If you do not use Omada Gateway, you also can use DHCP Server which supports option138 feature to finish the configuration.

 

 

Configuration screenshot of DHCP138 in Omada Controller.

 

 

Step 3. Adopt the Omada devices in Omada Controller.

 

After finishing the configuration above, the Omada devices in branch office will appear in “pending” list of Omada Controller. Click the tick button in red circle and manage these devices.

 

Note: If you have already adopted a gateway in the default site, please click “Add New Site” in the drop-down list of Sites and configure the parameters of the branch office. Only one gateway can be adopted per site.

 

 

Screenshot of Omada devices in Omada Controller.