This article covers how to set up DHCP on the Omada Environment. While it is possible to use Omada to manage your DHCP, in my case I have had a long standing DNS/DHCP environment set up using Windows Domain controllers. with this, My piholes, Linux servers, and Windows workstations all share the DNS address space, and DHCP is integrated with he DNS.

I could not find any articles or cook books for this, so this is my attempt to fill that gap. This was prepared with the help on TP-Link technical support.

Assumptions

  1. Multiple VLANs
  2. Multiple Omada Switches
  3. Omada Router
  4. Omada AP (not talked about in this)
  5. Omada Controller, Software or Hardware based
  6. Omada 5.0.30
  7. All Omada hardware will have its management IP on VLAN 1
  8. DHCP and DNS set up on server.  In this case, Windows 2016 Domain Controllers
    1. 192.168.100.131
    2. 192.168.100.132

VLANs

1Management192.168.1.0
10Office192.168.10.0
20Media192.168.20.0
100Servers192.168.100.0
  1. Set up VLANs in Omada
NameMedia
PurposeInterface
LAN InterfacesSelect All of them
VLAN10
Domain NameYourdomain.com
Gateway/Subnet192.168.10.1/24
IGMP SnoopingUnchecked
DHCP ServerUnchecked
Legal DHCP Servers192.168.100.131, 192.168.100.132
Configure IPV6None
  1. Do the same for the other VLANs.
  2. For VLAN 1, Configure DHCP
NameAdm_Vlan (Management)
PurposeInterface
LAN InterfacesSelect All of them
VLAN10
Domain NameYourdomain.com
Gateway/Subnet192.168.1.1/24
IGMP SnoopingUnchecked
DHCP ServerChecked
DHCP Range192.168.1.50 – 192.168.1.100
DNS ServerManual – 192.168.100.50/192.168.100.51
Lease time720
Default GatewayManual – 192.168.1.1
DHCP Omada ControllerBlank
Legal DHCP ServersUnchecked
Configure IPV6None
  1. Profiles are created automatically when VLANs are created
  1. Switch Config
    1. Each switch should have an uplink to the router.  Choose the same port on each switch.
    2. Each switch will have a management IP on VLAN 1
    3. Use the “ALL” profile for the Uplink port.
    4. Assign the Other VLAN profiles to the rest of the ports as needed to support attached devices
  1. Config–>VLAN Interface
    1. Turn on all interfaces

This function is what allows DHCP to flow from your DHCP servers down to the ports on your switches.

  1. Edit each VLAN Interface

ADM_LAN – Management Network

Management VLANChecked
IP Address ModeStatic
IP Address192.168.1.11
Subnet Mask255.255.255.0
Default GW192.168.1.1
Primary DNS192.168.100.50
Secondary DNS192.168.100.51
DHCP RelayChecked
Server Address192.168.100.131

Remaining VLANS

Management VLANUnchecked
IP Address ModeStatic
IP Address192.168.20.2
Subnet Mask255.255.255.0
DHCP RelayChecked
Server Address192.168.100.131

Note the IP Address.  This will be the IP for the appropriate VLAN.

Note the last octet.  This will be the same for each Interface on each switch

Each VLAN ends up with an IP on the switch for that VLAN.

Here is a sample for 3 switches:

SwitchVLANVLAN Interface IP
Office1192.168.1.10 – admin IP
Office10192.168.10.3
Office20192.168.20.3
Office100192.168.100.3
Media1192.168.1.11 – admin IP
Media10192.168.10.2
Media20192.168.20.2
Media100192.168.100.2
Servers1192.168.1.12 – admin IP
Servers10192.168.10.4
Servers20192.168.20.4
Servers100192.168.100.4

1 Comment

Leave a Reply

Your email address will not be published.