Specifications

Configuration of Dynamic Host Configuration Protocol (DHCP)
Summit WM Technical Reference Guide, Software Version 5.324
The limitation of using DHCP relay comes in the logging of DHCP messages on the Summit WM
Controller. When using DHCP relay the DHCP log under Logs & Traces Æ DHCP Messages is not
populated with DHCP requests. It is assumed that for DHCP relay that the target DHCP server has its
own logging mechanism.
DHCP configuration example: OSC dhcpd on Linux
Consider the following topology:
Figure 3: Topology for DHCP example
The Summit WM Controller is connected on network 10.0.0.0/24 as 10.0.0.10. Also on that network are a
DHCP server, a voice gateway for phones, and all Access Points. The phones have the special property
in that they require DHCP option 151 to find their voice gateway. Since the Summit WM Controller-
built-in DHCP server does not support custom options is was decided to use a Linux server at 10.0.09 to
host all DHCP requirements for this network. It is possible to configure each WM-AD to use DHCP
relay to the example DHCP server of 10.0.0.9.
10.0.0.10
DCHP
10.0.0.9
Voice gateway
10.0.0.11
AP assigned by
DHCP
Summit WM-AD
wireless network
172.16.2.0/24
Summit WM-AD
wireless network
172.16.1.0/24
Wireless laptop
Network 10.0.0.0/24