Configure ExtremeCloud IQ Controller for Local DHCP Management

For Bridged@AC configurations, the appliance can be configured as a Local DHCP (Dynamic Host Configuration Protocol) server for the VLAN segment. This is useful for deployments that do not have access to an infrastructure provided DHCP server. Configure ExtremeCloud IQ Controller as a Local DHCP from the Layer 3 settings of a Bridged@AC topology.

When the appliances are configured as a High Availability pair, the configuration sync to the peer appliance results in two DHCP servers being configured for one appliance pair. ExtremeCloud IQ Controller automatically syncs the configuration for redundancy. Therefore, if one appliance (and its corresponding DHCP server instance) is removed, the remaining appliance (and DHCP server) have full visibility of the allocated DHCP set, and support the subnet without interruption or conflict.

When configuring ExtremeCloud IQ Controller for providing IP addresses to APs, take the following steps on both appliances in a High Availability Pair:

  1. Define a physical topology on each ExtremeCloud IQ Controller.
    Configure a shared subnet and a unique IP address for each controller.
  2. From ExtremeCloud IQ Controller, enable Local DHCP server on the physical topology for both controllers.
  3. Specify the same L2 subnet on both physical topologies. The following settings should match on both controllers:
    Ensure that the following Physical Interface Settings match on both appliances in the High Availability Pair:
    • Mode
    • VLAN ID
    • Tagged
    • Port
    • Device Registration
    • Traffic Management
    Endure that the following Local DHCP settings match on both appliances in the High Availability Pair:
    • Gateway IP address
    • IP Address Range
9038115-00 Rev. AA