02-15-2012 12:24 PM - last edited on 05-14-2014 06:02 PM by Jamie E
We are running M3 controllers running 188.8.131.52.
So, we installed several dozen new AP 105s at a new location. We created the aruba-master DNS entry and they all come up and show up in AP Installation. We are provisioning them from the master and putting them into a group that points them at a new local controller at the same location as the APs. When we provision them, however, they do not come back up. We were able to provision most of the APs. But, the last 5 or 6 won't come back up. Besides provisioning them, I noticed a few of them were on switch ports with the wrong VLAN and thus got an IP address in a different scope. So, usually what I do in this situation is provision them and just a few seconds after I tell it to provision and reboot, I switch the vlan number on the switch port.
What I see in the Cisco arp table are repeated changes of the IP address (and the IP addresses are in the correct VLAN/DHCP scope). So, I know they are getting an IP. When I turn debugging on for the APs, I get:
Feb 3 03:34:24 KERNEL(00:0b:86:cf:bc:firstname.lastname@example.org): vap aruba005 vlan is 0. discovering tunnel vlan
Feb 3 03:34:24 KERNEL(00:0b:86:cf:bc:email@example.com): vap aruba105 vlan is 0. discovering tunnel vlan
When I do a show log system 50, I get:
Feb 13 03:19:01 :311002: <WARN> |AP 00:0b:86:cf:bc:firstname.lastname@example.org sapd| Rebooting: SAPD: Reboot requested by controller
Feb 13 03:22:02 :311002: <WARN> |AP 00:0b:86:cf:bc:email@example.com sapd| Rebooting: SAPD: Reboot requested by controller
Notice that 184.108.40.206 would be the IP address of the old VLAN.
I tried doing a 'clear gap-db ap-name 00:0b:86:cf:bc:a5' on the master and then trying to switch the VLAN again. That didn't work. The arp table shows it is in the right IP scope now. But, the AP will not come up. Any ideas?
Solved! Go to Solution.
02-21-2012 10:28 AM
We figured out the issue on this. Whoever configured the DHCP scope, configured it with two search domains. The aruba-master DNS record existed in one but not the other. I don't know why this worked previously and then stopped working - unless someone just added the other search domain.
Thanks for the help!
05-08-2014 03:57 AM
I know this is an old thread, but wanted to include what our cause/fix was.
The AP's at our site were rebooting, even though the controller could ping them.
The issue turned out to be that DNS at the remote site was broken, so the AP's could not resolve aruba-master, hence the reboots.