For small networks, you can configure and enable a DHCP server on a device to provide network settings dynamically to clients. After you configure one hive member as a DHCP server, the other hive members process the DHCPDISCOVERY and DHCPREQUEST messages that they receive from clients as usual, forwarding them to their neighbors through which they connect to the network. The only requirement about which device to use as the DHCP server is that it must be a portal.
When all hive members are in the same subnet and all devices in that subnet are on a single VLAN, you only need to configure the device that you want to be the DHCP server with a pool of IP addresses from which it can draw when responding to DHCP client requests.
When some hive members are in a different subnet from that of the DHCP server, you must also configure those devices to forward DHCP traffic to the IP address of the DHCP server. In this case, the other devices act as DHCP relay agents. You can configure both DHCP servers and relay agents here.
Use the following procedure to add a new DHCP Server and Relay object.
Note
The following numbers are reserved: 226, ExtremeCloud IQ domain name; 225, ExtremeCloud IQ IP address; 229, PPSK server IP address; 230, RADIUS server authentication IP address; 231, RADIUS server accounting IP address. The following DHCP option numbers are reserved for other information: 3, 6, 7, 15, 26, 42, 44, 51, 58, 59, 69, and 70.