Specifications

Summit WM Getting Started Guide, Software Version 5.1 57
Parameters (including options) declared before a section enclosed in curly brackets {} are considered
global parameters. Global parameters apply to all the sections below it.
NOTE
If you change the configuration file, the changes will not take effect until you restart the DHCP daemon with the
command service dhcpd restart.
The following is the example of DHCP configuration on a Red Hat Linux Server.
For Wireless AP subnet
For WM-AD subnets (In Summit WM Controller it is configured as Use DHCP Relay)
if you are utilizing multiple WM-ADs you must configure the Red Hat Linux server for every WM-AD.
The following is the example of DHCP configuration in Red Hat Linux for two WM-ADs (For more
information, see Chapter 7, “WM-AD configuration”).
subnet 10.209.0.0 netmask 255.255.255.0 {
option routers 10.209.0.2; ### This is the network’s default gateway address.
option subnet-mask 255.255.255.0
option domain-name xyznetworks.ca
option domain-name servers 192.168.1.3, 207.236, 176.11
range 10.209.0.3 10.209.0.40;
default-lease-time 7200000 ###The figures are in seconds.
option slp-directory-agent true 10.209.0.1, 10.209.0.3; ####The Wireless APs
use the SLP DA to discover the Summit WM Controller, and the mobility agents
use it to discover the mobility manager.
authoritative;
}
subnet 172.29.31.0 netmask 255.255.255.224
option routers 172.29.31.1; #### This is the WM-AD 1 gateway.
option subnet-mask 255. 255. 255.0
option domain-name toronto.xyznetworks.com”;
option domain-name-servers 192.1.1.3;
range 172.29.31.2 172.29.31.30;
default-lease-time 36000;
max-lease-time 7200000;###The figures are in seconds.
authoritative;
}