Once an AP has successfully registered with a controller, it recalls that controller's IP address, and uses that address on subsequent reboots. The AP bypasses discovery and goes straight to registration. Use the IP address of the controller to which the AP last connected successfully.
If a known controller cannot be located, take the following steps:
For the DHCP server to respond to an Option 60 request from an AP, configure the DHCP server with the vendor class identifier (VCI) for each AP model. Also, configure the DHCP server with the IP addresses of the controllers.
The AP tries the DNS server if it is configured in parallel with SLP unicast and SLP multicast.
If you use this method for discovery, place an A record in the DNS server for Controller.<domain-name>. The <domain-name> is optional, but if used, ensure it is listed with the DHCP server.
The AP sends a multicast SLP request, looking for any SLP Service Agents providing the Extreme Networks service.
The AP tries SLP multicast in parallel with other discovery methods.
To use the DHCP and unicast SLP discovery method, ensure that the DHCP server on your network supports Option 78 (DHCP for SLP RFC2610). The APs use this method to discover the controller.
This solution takes advantage of two services that are present on most networks:
The controller contains an SLP SA that, when started, queries the DHCP server for Option 78 and if found, registers itself with the DA as service type Extreme Networks. The controller contains a DA (SLPD).
The AP queries DHCP servers for Option 78 to locate any DAs. The SLP User Agent for the AP then queries the DAs for a list of Extreme Networks SAs.
Option 78 must be set for the subnets connected to the ports of the controller and the subnets connected to the APs. These subnets must contain an identical list of DA IP addresses.