08-04-2010 03:23 AM
I have trouble configuring an AP since it connects to the wrong controller. We have an A2400 (aruba-master, 10.9.0.200) and an A200 (aruba-test, 10.9.0.202) running OS 126.96.36.199. The AP61 has been used before.
Now I purged the configuration of the AP61 and connected it to the network. Although the default configuration has aruba-master as servername, it always connects to the A200. Even setting the serverip to 10.9.0.200 doesn't change this.
We are not using any white lists so far. This is the first time I connect an AP to our WLAN after upgrading to OS 5. So if something has changed that leads to this behavior, please let me know.
08-04-2010 05:22 AM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
08-04-2010 08:40 AM
08-06-2010 03:14 AM
The AP doesn't have an initial IP address. It will get it by DHCP. However, the controller is not the DHCP server. This is done by another machine on the network.
08-07-2010 02:45 AM
set master 10.9.0.200
set serverip 10.9.0.200
it will take controller config statically...without looking into ADP,DNS,DHCP....
08-11-2010 05:59 AM
What is the order of steps that an AP goes through to discover a controller, and has the order always been the same?
An AP's master discovery order
1) “master” parameter set (manualy) on the AP
2) dhcp option 43
3) ADP multicast & broadcast
4) DNS lookup for aruba-master
And yes, always been the same.
-- Found something helpful, important, or cool? Click the Kudos Star in a post.
-- Problem Solved? Click "Accept as Solution" in a post.
09-14-2010 02:57 AM
The AP then tries to set up its PAPI tunnel but can't, obviously as the Firewall will neither allow it or want to create a PAPI with an AP.
Any Ideas? Does the Fortinet use a similar protocol to ADP? (Why would it???)
We have searched our DNS entries and there is nothing in there that points Aruba-master to the fortinet IP.
Weare also running SW v.5