Reset Search
 

 

Article

Access points failing the IdentiFi Controller discovery process

« Go Back

Information

 
TitleAccess points failing the IdentiFi Controller discovery process
Symptoms
  • Access points are not able to locate an IdentiFi Controller via DNS lookup (controller.<domain name>)
  • Access points are not using option 78 provided by the DHCP offer
Environment
  • ExtremeWireless appliances
  • DNS
  • DHCP Inform
  • All ExtremeWireless appliance Firmware
  • Access Point Boot Up Process
  • SonicWall
Cause
DHCP server not replying to DHCP informs 
Resolution
Use a DHCP server that will reply to DHCP informs.  The access point will not use the options supplied in the DHCP offer which is provided by the DHCP server. The ap will send periodic DHCP informs looking for the DHCP server to ACK the inform and provide the necessary options (78, 43, DNS server, etc...)

Another option would be to manually set the controllers IP on the access point: 
How to assign a static IP address to an IdentiFi Access Point via the ap shell
Additional notes
The Access Point (AP) does not use the DNS information from the initial DHCP offer supplied from the DHCP server. After the IP setup stage, the AP decides whether to use the static controller IP or start it's discovery methods. If SLP/DNS/VCI discovery is started, the AP sends periodic DHCP informs to get more data in order to complete it's boot discovery methods. If the DHCP server does not reply to the inform, the process to contact the controller will fail and start over.

How To Configure an AP to Find the IdentiFi Wireless Controller with DHCP Option 78 on a Linux Server

How To Configure an AP to find the IdentiFi Wireless Controller from a DNS server entry.

How To Configure an AP to Find the IdentiFi Wireless Controller with DHCP Option 78 on a Windows Server

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255