@fjulianom wrote:
Hi guys,
I have just left the customer site, I was doing troubleshooting. In fact the problem was very easy, just customer doesn't have a DHCP server and then the APs didn't obtain an IP address and couldn't join to the controller.
After setting a static IP address to the AP and doing the conversion from IAP to CAP the AP joined to the controller, and appeared as up ready to provision.
Just one more thing, when doing the conversion I tried with the master controller IP address and with the local controller IP address. In the first case the AP appeared as up and ready to provision in the master controller dashboard, but in the second case it also appeared in the master controller dashboard and not in the local controller dashboard.
In this second case, when I used the local controller IP address when converting the IAP, shouldn't the AP appear as up in the local controller dashboard?
And in any case, is it recommended to use the master controller or the local controller IP address when converting the AP? Because as said previously, in both cases the AP appeared as up in the master controller dashboard, so it seems in both cases the AP joined to the master controller.
Regards,
Julián
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.