Dhcp Setups For Relayed Wm-Ad's And Ap Deployment Networks; Dhcp Configuration Example: Osc Dhcpd On Linux - Extreme Networks Summit WM Technical Reference Manual

DHCP setups for relayed WM-AD's and AP deployment
networks
Sometimes it is necessary to use a DHCP server external from the Summit WM Controller to give offer
DHCP addresses. Popular reasons for this are:
Support for DHCP options that are not exposed through Summit WM Controller GUI (Summit WM
●
GUI),
To leverage existing DHCP infrastructures, and
●
To consolidate the DHCP requirements for wireless client, APs, and the Summit WM Controller in
●
one place.
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
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
10.0.0.10
Summit WM-AD
wireless network
172.16.2.0/24
Wireless laptop
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
Summit WM Technical Reference Guide, Software Version 5.1
Network 10.0.0.0/24
AP assigned by
DHCP
DHCP Messages is not
DCHP
10.0.0.9
Voice gateway
10.0.0.11
Summit WM-AD
wireless network
172.16.1.0/24
23