*Use Scenario: Router A, a Omada Gateway is connected to Router B in a separate office via the internet. This guide will show you how to use the HQ’s controller to mange the remote branch’s Omada resources
Set up Port Forwarding for Router A on Omada SDN Controller
Note: In this example we assume Router A is an Omada Gateway with the Controller feature active and configured. If your router is not an Omada Gateway you may need additional hardware to accomplish this task.
Go to Settings > Transmission > NAT > Port Forwarding and click on Create New Rule.
Set the parameters (Source Port, Destination IP, Destination Port) then click on Create. In this example we will use the following:
Source Port: 29810-29814
Destination IP: 192.168.0.101
Destination Port: 29810-29814
- Download the Omada Discovery Utility and run it on PC2 at the branch office.
- Router B, the Omada switch, and EAP Access Point will be discovered by Utility automatically. Click the "Select All" and "Batch Setting" buttons in the lower right corner.
- Fill out the fields, the Center IP is Router A's WAN IP, in this example: 192.168.1.200. Then click Apply.
*Note: The factory default username and password of TP-Link devices are admin/admin. If you have already configured these devices in standalone mode and changed their username and password, you can manage them by entering their username and password separately.
- The devices will appear in the devices list with "PENDING" status, then you can adopt and manage them.
For Router B:
- Go to System Tools > Controller Settings > Inform URL/IP Address, input the Router A WAN IP in the box and click Save. In this example 192.18.1.200. Then Router B can find the Controller.
For Switch:
- Go to System Tools > Controller Settings > Inform URL/IP Address, input the Router A WAN IP in the box and click Apply. In this example 192.18.1. 200.
For EAP:
- Go to System Tools > Controller Settings > Inform URL/IP Address, input the Router A WAN IP in the box and click Save.
- After informing the devices of the Controller IP, the devices will appear in the Controller Device list with the "PENDING" status, then you can adopt them.
Note: Currently, this method is only suitable for Omada Switches and EAPs.
For Switches:
- Access its management page, then go to SECURITY > Access Security > SSH Config > enabled SSH under Global Config on the switch management page, then click Apply,
- Enter the Switch’s IP in Putty and click on Open to access the CLI management of the switch.
- The commands for informing the Controller IP are as below.
enable
configure
controller inform-url 192.168.1.200
For EAP:
- Access EAP’s management page, then go to Management > SSH > SSH Server and check the box to enable SSH. Then Click Save.
- Enter EAP’s IP address into Putty and click on Open to access the CLI of the EAP.
- The commands for informing the Controller IP are as below.
xsetctrladdr “192.168.1.200:29810”
Note: This method is only suitable for Omada DHCP clients
Configure the DHCP Option 138:
- Configure the DHCP server, in this example, it is Router B. Access Router B’s management page and go to Network > LAN > LAN, click the Operation ICON to modify the DHCP configuration.
- Click on the "Advanced DHCP Options” and enter the WAN IP of Router A into the Option 138 entry. In this example, it is 192.168.1.200. Then click OK.
- Reconnect the Switch and EAP Access Point to obtain the IP address again, the Switch and EAP will get the Controller IP from DHCP Option 138 and find Controller properly.
