Wireless Access

Reply

Re: IAP fails when connecting to Aruba controller

Hi Phillip,

 

Many thanks, valuable information!

 

Regards,

Julián

Re: IAP fails when connecting to Aruba controller


wrote:

 

Access Points that connect to the local will appear on the master.  Access points that appear on the master will also show up on the master.  In any event, anything you provision should show up on the master, so you can look there to see any access points that either terminate on the master or the local.

You should ensure that the customer has dhcp and has a discovery method configured (DNS, DHCP option, etc), because doing anything with static ip addressing is error-prone and painful.  Having dhcp also allows your access points to recover if the underlying network changes for whatever reason.

If you deploy the new UAPs in the customer's environment, and the customer has a discovery method configured (DNS, dhcp option), the access points will convert themselves and work, as long as they can find a controller.

If you have Instant APs, you should probably deploy and convert them in the customer's environment, provided that they already have dhcp; you can bring up all the Instant APs you would need at the customer's site in a cluster and convert them all at the same time, onsite at the customer.  (you would need to know the Virtual Controller's ip address so that you can Web into the VC and convert them, using the  The access points will come up and join the controller.  This will save you hours in a lab, just to pack up the access points and ship them to the customer.

Ideally, you would just purchase campus APs, the customer would have DNS (aruba-master) pointed to the master controller and they would just come up, saving you tons of time.

The key here is dhcp and a discovery method, so that things work automatically and access points will recover.  Using static ip addressing involves too much risk due to duplicate ip addressing, wrong subnet masks and default gateways, etc.  Static ip addressing also forces you to keep track of all of your access point to ip address mapping, which is an administrative nightmare...

I hope that helps.


Hi Colin,

 

I completely agree with all your points you have already explained and the advantages of using DNS or DHCP option 43, and the disadvantages of using static IP addressing. The point is the customer is new and it already has a deployed network and many controllers, and we can't change its network.

 

I also aggree about is better to deploy and convert the entire cluster of IAPs in the customer's environment, since it will convert all the IAPs at the same time, and this will save many hours in a lab, just to pack up the access points and ship them to the customer. Here the point is we need to do this in our office firstly because customer doesn't use DHCP and secondly because some of sites are hundreds of kilometers away and I can't go to all the sites.

 

Very well explanation Colin and now I have more clear all this. Thanks again for your help!

 

Regards,

Julián

Re: IAP fails when connecting to Aruba controller

Hi guys,

 

Last question about this. In the case of setting the IP address of the master controller, there are two fields for this within Configuration> Wireless> AP Installation:

master_ip.png

Is there any difference of setting the IP address in the left one, in the right one, or in both at the same time?

 

Regards,

Julián

Guru Elite

Re: IAP fails when connecting to Aruba controller

You should use the field on the left to statically set the ip address of the master.  The same field on the right is a legacy parameter when you want to specifically define what controller an access point uses to get its firmware.  It is very rarely used today.  Again, both fields are rarely used today because most Aruba Networks are defined with discovery in mind, and those parameters are obtained automatically instead of entered manually.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars

Re: IAP fails when connecting to Aruba controller

OK, very clear. Thanks again!

Regards,
Julián
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: