Specifications

DHCP setups for relayed WM-ADs and AP deployment networks
Summit WM Series WLAN Switch and Altitude Access Point Software Version 4.1 Technical Reference Guide
17
DHCP setups for relayed WM-ADs and AP deployment
networks
Sometimes it is necessary to use a DHCP server external from the Summit WM to give offer DHCP
addresses. Popular reasons for this are:
● Support for DHCP options that are not exposed through Summit WM GUI,
● To leverage existing DHCP infrastructures, and
● To consolidate the DHCP requirements for wireless client, APs, and the Summit WM in one place.
The one downfall of using DHCP relay comes in the logging of DHCP messages on the Summit WM.
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 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-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 Access Domain Service (WM-AD) to
use DHCP relay to the example DHCP server of 10.0.0.9.