Wireless Access

Why doesn't my Aruba Access Point Find My Controller? - Part 1.  Covers the importance of the DNS a-record of "aruba-master" and the DHCP domain name in Aruba Controller Discovery.

 

Just a point of clarification, Colin.  AP master discovery uses the following methods, in order, to find its master.

 

1.  DHCP option

2.  ADP

3.  DNS

 

If you don't use the DHCP option but do use ADP, DNS doesn't even come in to play, does it?

If all of those methods were mentioned, there wouldn't be a part 2.

 

You forgot #1 Mike :smileytongue:

 

AP boot order

1)    “master” parameter set (manualy) on the AP

2)    dhcp option 43

3)    ADP multicast & broadcast

4)    DNS aruba-master

I'm wondering whether there is a way to validate remotely which method was used?

Also if the "master" parameter is manually set on the AP, is there a way to remotely remove this?

Unfortunately, there is no way to remotely validate or remove those parameters.  It must either connect to the controller, where you can provision it there, OR you can change those variables physically via the console.

 

Having worked with these parameters in a bit in the field the last few days in order to get some APs working which had DNS difficulties I noticed something interesting. When I wanted to re-provision an AP that was setup with a fixed Master IP locally I saw that within the Master Discovery part of provision menu it now had the 'Master controller IP address/DNS name' filled in rather than the "Host controller Name".

 

I'm wonder if these settings do not reflect whether it will:

1.) Look at the Master controller IP - which is the one that is manually configured IP on the console

2.) Find the controller through DNS looking for the 'aruba-master' if this is deleted and converted back to 'Host controller Name' filled in.

 

Unfortunately I don't have a lab setup at the moment where I can test this but it would sound logical to me.

 

Anyone who can confirm or would like to test this?

 

I'm sure this would be interesting for some of you as well in case you run in the same situation in the field :)

Dear ,

 

i can place aruba controller in different network ? , AP can find controller eventhough both are in different network ?

Using the DNS discovery method.. yes...

Hello

 

Below are my Aruba AP205 logs

Configuration is done under Vendor specific info, but cant connect to the controller.

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Uncompressing... done
[    0.000000]
[    0.000000] Aruba Networks
[    0.000000] ArubaOS Version 6.4.3.6 (build 52927 / label #52927)
[    0.000000] Built by p4build@lesbos on 2015-12-11 at 15:43:45 PST (gcc version 4.7.2)
[    0.000000]
[    0.000000] Flash variant: variant0
[    0.000000] MPCORE found at 19020000, SCTLR 0x10c53c7f ACTLR 0x00000040 CPSR 0x600001d3 SPSR 0x60000013 PRRR 0x000a81a8 NMRR 0x40e040e0
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 120676k/120676k available, 10396k reserved, 0K highmem
[    0.052000] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    3.468000] PMU: registered new PMU device of type 0
[    3.976000] pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
[    3.978000] pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
[    3.980000] pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]
[    4.484000] pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
[    4.486000] pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
[    4.488000] pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]
[    4.832000] i2c-springbank: using remapped base c9e54060
[    4.836000] mpcore_wdt mpcore_wdt: enabling watchdog.
[    4.840000] qspi_iproc qspi_iproc.1: 1-lane output, 3-byte address
[    4.842000] m25p80 spi1.0: mx25l25635e (32768 Kbytes)
[    4.846000] Creating 1 MTD partitions on "spi1.0":
[    4.848000] 0x000000000000-0x000002000000 : "qspi"
[    4.860000]
[    4.860000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[    4.864000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
[    4.926000] Starting Kernel DES KAT ...Completed Kernel DES KAT
[    4.930000] Starting Kernel AES KAT ...Completed Kernel AES KAT
[    4.932000]
AP-type has_ble_support: .
Domain Name: arubanetworks.com
No panic info available
[   13.746000] AP xml model 81, num_radios 2 (jiffies 6873)
[   13.748000] init_asap_mod: installation:0
[   13.750000] radio 0: band 1 ant 0 max_ssid 16
[   13.752000] radio 1: band 0 ant 0 max_ssid 16
USB is not supported on this model
Starting watchdog process...
Getting an IP address...
[   14.890000] ADDRCONF(NETDEV_UP): bond0: link is not ready
[   19.900000] bond0: link up (1000FD)
[   19.902000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
10.73.8.84 255.255.255.0 10.73.8.1
Running ADP...cat: /tmp/master: No such file or directory
Done. Master is
killall: nanny: no process killed
killall: sapd: no process killed
Sending SIGKILL to all processes.
Please stand by while rebooting the system.
[  120.132000] Restarting system.

 

Please anyone with idea please

yes

Please assists, confused here.

might be wiser to start a new topic. did you confirm the usual suspects, i.e. is the controller on the same L2 network (as DHCP seems to work). did you try reseting the AP?

Yes reset was done. AP seems to work fine from other site which are managed
by same controller but not at my site.

what is the difference between the sites? what method do you use for controller discovery?

Globally we are using DHCP,

have configured vendor specific.

Does it work anywhere?  Please show us your DHCP server configuration.

I have the same issue... 

 

My new ap 205 can't be viewer on my 3200 controller.

 

Checking image @ 0x1e100000
Copying image from 0x1e100000

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Uncompressing... done
[ 0.000000]
[ 0.000000] Aruba Networks
[ 0.000000] ArubaOS Version 6.4.2.6-4.1.1.13 (build 54918 / label #54918)
[ 0.000000] Built by p4build@rhodes on 2016-05-06 at 05:00:19 PDT (gcc version 4.7.2)
[ 0.000000]
[ 0.000000] Flash variant: variant0
[ 0.000000] MPCORE found at 19020000, SCTLR 0x10c53c7f ACTLR 0x00000040 CPSR 0x600001d3 SPSR 0xa7006200 PRRR 0x000a81a8 NMRR 0x40e040e0
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 117664k/117664k available, 13408k reserved, 0K highmem
[ 0.052000] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 5.358000] PMU: registered new PMU device of type 0
[ 5.864000] pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
[ 5.866000] pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
[ 5.868000] pci 0001:01:00.0: BAR 0: set to [mem 0x08000000-0x08007fff 64bit] (PCI address [0x8000000-0x8007fff]
[ 6.372000] pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
[ 6.374000] pci 0002:02:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
[ 6.376000] pci 0002:02:00.0: BAR 0: set to [mem 0x40000000-0x40007fff 64bit] (PCI address [0x40000000-0x40007fff]
[ 6.722000] i2c-springbank: using remapped base c8914060
[ 6.724000] mpcore_wdt mpcore_wdt: enabling watchdog.
[ 6.728000] qspi_iproc qspi_iproc.1: 1-lane output, 3-byte address
[ 6.730000] m25p80 spi1.0: mx25l25635e (32768 Kbytes)
[ 6.732000] Creating 1 MTD partitions on "spi1.0":
[ 6.734000] 0x000000000000-0x000002000000 : "qspi"
[ 6.736000]
[ 6.736000] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[ 6.740000] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
[ 6.754000] Starting Kernel DES KAT ...Completed Kernel DES KAT
[ 6.758000] Starting Kernel AES KAT ...Completed Kernel AES KAT
[ 6.760000]
Domain Name: instant.arubanetworks.com
No panic info available
apfcutil: sector CACHE: Cache uninitialized
apfcutil: sector RAP: Cache uninitialized
apfcutil: sector FAT: Cache uninitialized
apfcutil: sector SCRATCH: Cache uninitialized
Check backup ENV.
apfcutil: sector MESH Prov: Cache uninitialized
Cfg len is 0
Configuration file is empty, turning on default services...
extended ssid activate due to no AP config ...
[ 14.534000] ADDRCONF(NETDEV_UP): bond0: link is not ready
[ 16.538000] bond0: link up (100FD)
[ 16.540000] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Mesh is DISABLED on this device.
Disabling wpa_supplicant for this paltform
[ 17.606000] AP xml model 81, num_radios 2 (jiffies 8803)
[ 17.608000] init_asap_mod: installation:0
[ 17.610000] radio 0: band 1 ant 0 max_ssid 16
[ 17.612000] radio 1: band 0 ant 0 max_ssid 16
[ 17.614000] election init: rand=16 HZ=500
[ 17.616000] IAP client match init
notify asap_mod 3g no present...
Starting watchdog process...
Getting an IP address...
Dec 31 16:00:19 udhcpc[1361]: udhcpc (v0.9.9-pre) started
Dec 31 16:00:19 udhcpc[1361]: send_discover: pkt num 0, secs 0
Dec 31 16:00:19 udhcpc[1361]: Sending discover...
Dec 31 16:00:19 udhcpc[1361]: send_selecting: pkt num 0, secs 0
Dec 31 16:00:19 udhcpc[1361]: Sending select for 172.16.6.57...
Dec 31 16:00:19 udhcpc[1361]: Lease of 172.16.6.57 obtained, lease time 691200
Dec 31 16:00:19 udhcpc[1361]: DHCP OPT 43 deleted airwave config

172.16.6.57 255.255.0.0 172.16.0.1
Compressing all files in the /etc/httpd directory...
[ 22.624000] ip_time_handler: Got ip and packets on bond0 Started master election 89-0, rand 24
Done.
Starting Webserver
bind: Transport endpoint is not connected
bind: Transport endpoint is not connected
bind: Transport endpoint is not connected
Launching NTP Client on pool.ntp.org
[ 24.622000] wifi0: AP type AP-205, radio 0, max_bssids 16
[ 24.666000] wifi1: AP type AP-205, radio 1, max_bssids 16
shutting down watchdog process (nanny will restart it)...
Completed SW FIPS KAT test

<<<<< Welcome to the Access Point >>>>>

User: [ 43.856000] process `snmpd_sap' is using obsolete setsockopt SO_BSDCOMPAT
[ 46.656000] i am master now
[ 46.658000] (00:00:48) !!! Init ---> Master
[ 46.660000] asap_send_elected_master: sent successfully.

 

That is an instant AP.

 

ArubaOS Version 6.4.2.6-4.1.1.13 (build 54918 / label #54918)

 

 It must be converted to a campus AP before it can be used with a controller.  http://community.arubanetworks.com/t5/Controller-less-WLANs/How-do-I-convert-an-Aruba-Instant-AP-to-a-campus-AP/ta-p/178988

 

 

 

Could I please have access to view this video. Thanks!

good point, ozwifi / cjospeh the video now says it is private.

Fixed.

perfect, thanks.