Wireless Access

Reply
Contributor I

AP was visible under default group but not anymore after Appy and Reboot under AP Installation

The default Master Discovery method under AP Installtion is using Host Controller Name of aruba-master.   If the AP is located in different VLAN from the controller, and aruba-master DNS entry does not exist in internal DNS or DHCP option 43 pointing to master controller IP is not configured in DHCP server, change the Master Dicovery method to Master Controller IP/DNS Name method, and enter controller IP in this field.  All these settings can be found under Configuration - AP Installation - pick an AP - Provision.

 

The AP will need to be factory defaulted, then show up under Configuration - AP Installation in GUI or show ap database in CLI under default AP group.  It is then ready to be provisioned to the correct AP group by following the first paragraph above.

Guru Elite

Re: AP was visible under default group but not anymore after Appy and Reboot under AP Installation

If you provision with all of the defaults, it will first:

 

1 - Check to find the controller via multicast on the same subnet

2 - Check to find the DHCP options 43 and 60

3 - Attempt to resolve aruba-master.<domain suffix from dhcp>.com

 

You do not have to edit anything for it to use those discovery methods above.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Contributor I

Re: AP was visible under default group but not anymore after Appy and Reboot under AP Installation

The original post is applicable if the AP does not reside in the same subnet as the controller and there is no aruba-master DNS entry and there is no DHCP option configured.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: