Wireless Access

I was able to get version 6.5.4.2 installed on our 7030 because of the WPA2 issue and most APs came back up after a few minutes except for our 6 AP-215s.  They just keep power cycling after failing to find our controller via ADP.  The only quick solution that support has been able to offer is to program the WAPs to point to the controller manually.  I can do this easily with two of our WAPs, however, this is not a desirable solution.  I also have a packet capture if that is of interest.  Is anyone else having any trouble after this latest update?

Attachment(s)

ap-215.zip   17 KB 1 version

I'm in a similar situation.  I upgraded and lost 3 APs connected to my 7005 controller.  I've been on the phone with TAC and they couldn't get them back because I couldn't attach a console cable to them due to where they are mounted.  TAC issued RMAs for all of my APs (2xAP225 and 1xAP325).  

If anyone knows how to recover without a console cable then please let me know... TAC was unable to find a solution.

I just got off of the phone with Aruba support and they said that they know of the issue and are working on a fix.  I have sent them a packet capture of the WAPs trying to connect, the controller tech log and a log of the WAPs booting up.  I hope that they can find a fix soon as well, because I have four WAPs that are very hard to gain physical access to.  

UPDATE:  Just received a call from Aruba and the tech said that the 6.5.3.3 (this version fixes the WPA2 vulnerability too) version does not have the issue.  I'm going to upload it after hours and check it out.

I tried 6.5.3.3 this morning... and my APs still don't register... I see them attempt to create the GRE tunnel but they never complete.  Then they reboot and try again.  I don't know how they can be recovered at this point since they can't seem to find the controller any longer...

 Sorry to hear about that njaiswal.  Now you have me worried about my update at 4:30 pm CST.  Have you tried contacting Aruba support? 

UPDATE:  I just applied the 6.5.3.3 and, like you, I am running in to the same issue.  >:-(  I really don't want to get in the cherry picker to get these 215s.  

That's the boat I'm in... TAC's only response was to RMA the affected APs. I have 2 of the 3 arriving tomorrow and the third arriving on the 24th.. I'm scheduling my electricians to come and swap them out... there is no way I'm climbing up a ladder to change APs mounted 18 ft high... :-/

Have you tried manually configuring them to point to the controller?  That's what I'm doing, because I don't have time to wait for some replacement hardware (honestly, I feel that it's a software issue anyway).

Terminaled into the WAP via the console port:

setenv serverip <controller_IP>
setenv master <controller_IP>
saveenv
boot

Thanks Derick.  Unfortuantely, I'm in the same boat as you with respect to where the APs are mounted... I have no way of getting to them until I have our electricians go fetch them...

It looks like you have the ip address for your access points statically configured.  Are they on the same VLAN as the controller?

Yes.  My APs are on the same VLAN as the controller and I even went one step further by plugging them directly into the controller.  They still weren't able to connect to it...

Is there anything blocking  broadcast multicast on your switches or on the wired interface of your controller?  Again, if you enabled any of those, your access points will silently fail when they reboot.  Also, what is the output of "show adp counters"?

I don't believe so... I have left those settings to the default value... 

Below is the output of the command you asked me to run...

(Master) #show adp counters

ADP Counters

------------

key           value

---           -----

IGMP Join Tx  1

IGMP Drop Tx  0

ADP Tx        13413

ADP Rx        13413

Type "show switch ip".  Is it on the same VLAN as the access points?

The controller is on the same VLAN as the APs.

Below is the output of the command...

(Master) #show switch ip

Switch IP Address: 192.168.25.2

Switch IP is configured to be Vlan Interface: 1

Switch IPv6 address is not configured.

According to your console output, your access points are configured on a different VLAN:

Bonding mode set to
10.10.1.165 255.255.240.0 10.10.1.1
Running ADP...cat: /tmp/master: No such file or directory
Done. Master is

10.10.1.165 is the access point's ip address.  If it cannot route to 192.168.25.2 through 10.10.1.1, it will NOT find the controller.  If you are using ADP, the controller will respond with it's controller- ip address and send your access points to that.  You can change the controller ip address to something on the 10.10.1.x subnet with via a console cable (might require a reboot) and see if your access points find the controller.

EDIT:

You would do it like this:

(Aruba7660-US) #configure t
Enter Configuration commands, one per line. End with CNTL/Z

(Aruba7660-US) (config) #controller-ip <new ip address of controller>

Hi Colin,

I believe you're looking at the wrong case... my network doesn't have any 10.x.x.x IPs in it...

Niten 

Niten,

You need to get a console cable like the person who opened this thread to understand what is going on.  You can type "show log system 50" to also see if there is a clue about why the access points are not connecting.

Hey Colin,

 No doubt.  But even with the console cable, I wouldn't be able to do anything with it until the electricians show up to unmount the APs from the ceiling... they're 17 feet in the air... :-(

Niten 

Are your access points statically configured?  Type "show log system 50" to see if there is a clue why they are not coming up...

It appears that the access points can't create the GRE tunnel.  When I look at the datapath session table I see protocol 17 but not protocol 47...  

(Master) #show log system 50

Oct 17 07:19:18 :399899:  <4063> <INFO> |ipstm|  sapi_rsp, sapi.c:248: SAPI response service/level lookup failed

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:18 :399899:  <4063> <INFO> |ipstm|  sapi_rsp, sapi.c:248: SAPI response service/level lookup failed

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:18 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19  KERNEL: [  306.867000]   0:alloc_vis_map: Allocated 7340032 bytes for fw_visibility(3975)

Oct 17 07:19:19  KERNEL: [  306.867000]   0:apsd_porf_getdmamem: physical address 0xB7000000, virtual address 0xc0000000b7000000, size 7340032

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message, len=88

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  papi_rcv_cb, Recvd PAPI Message from IKE

Oct 17 07:19:19 :348306:  <4063> <DBUG> |ipstm|  procIkeMessage, Received Unknown IKE message

Here's the output from the datapath command...

Source IP       Destination IP  Prot SPort DPort  Cntr    Prio ToS Age Destination TAge Packets    Bytes      Flags           

--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- ---------  --------- ---------------

192.168.25.3    239.0.82.11     17   54532 8200   0/0     0    0   1   0/0/1       17   10         400        FC              

255.255.255.255 192.168.25.3    17   8200  54532  0/0     0    0   1   0/0/1       17   0          0          FY              

192.168.25.3    255.255.255.255 17   54532 8200   0/0     0    0   1   0/0/1       17   10         400        FC              

(Master) #show datapath session table 192.168.25.3

Datapath Session Table Entries

------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT

       D - deny, R - redirect, Y - no syn

       H - high prio, P - set prio, T - set ToS

       C - client, M - mirror, V - VOIP

       Q - Real-Time Quality analysis

       I - Deep inspect, U - Locally destined

       E - Media Deep Inspect, G - media signal

       r - Route Nexthop

       A - Application Firewall Inspect

       B - Permanent, O - Openflow

Source IP       Destination IP  Prot SPort DPort  Cntr    Prio ToS Age Destination TAge Packets    Bytes      Flags           

--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- ---------  --------- ---------------

255.255.255.255 192.168.25.3    17   8200  54532  0/0     0    0   1   0/0/1       18   0          0          FY              

192.168.25.3    255.255.255.255 17   54532 8200   0/0     0    0   1   0/0/1       18   10         400        FC              

(Master) #show datapath session table 192.168.25.3

Datapath Session Table Entries

------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT

       D - deny, R - redirect, Y - no syn

       H - high prio, P - set prio, T - set ToS

       C - client, M - mirror, V - VOIP

       Q - Real-Time Quality analysis

       I - Deep inspect, U - Locally destined

       E - Media Deep Inspect, G - media signal

       r - Route Nexthop

       A - Application Firewall Inspect

       B - Permanent, O - Openflow

Source IP       Destination IP  Prot SPort DPort  Cntr    Prio ToS Age Destination TAge Packets    Bytes      Flags           

--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- ---------  --------- ---------------

255.255.255.255 192.168.25.3    17   8200  54532  0/0     0    0   1   0/0/1       1a   0          0          FY              

192.168.25.3    255.255.255.255 17   54532 8200   0/0     0    0   1   0/0/1       1a   10         400        FC              

(Master) #show datapath session table 192.168.25.3

Datapath Session Table Entries

------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT

       D - deny, R - redirect, Y - no syn

       H - high prio, P - set prio, T - set ToS

       C - client, M - mirror, V - VOIP

       Q - Real-Time Quality analysis

       I - Deep inspect, U - Locally destined

       E - Media Deep Inspect, G - media signal

       r - Route Nexthop

       A - Application Firewall Inspect

       B - Permanent, O - Openflow

Source IP       Destination IP  Prot SPort DPort  Cntr    Prio ToS Age Destination TAge Packets    Bytes      Flags           

--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- ---------  --------- ---------------

255.255.255.255 192.168.25.3    17   8200  54532  0/0     0    0   1   0/0/1       1e   0          0          FY              

192.168.25.3    255.255.255.255 17   54532 8200   0/0     0    0   1   0/0/1       1e   10         400        FC              

It looks like the access points are not setting up CPSEC.  Again, are your access points statically configured?  Protocol 17 is just UDP.

You should type "show log security 50 to see if there is another issue.

Hi... sorry.. My APs are all statically configured.  192.168.25.3-.5.  My controller is 192.168.25.2.

Below is the output of the command.

(Master) #show log security 50

Oct 17 07:17:35 :103093:  <3596> <WARN> |ike|   Starting cryptoPOST

Oct 17 07:17:50 :136008:  <4151> <DBUG> |survival|  init_rdwrap(): Max Number of users in RAD-DB:4096.

I would be guessing without the AP console output.  When you get those access points down, the first thing you should do is make them DHCP.  It will make your life easier.  If you feel like it, paste the console output into here, when you get it so we can understand what might be going on.  I am assuming you opened a TAC case,

Will do and yes.  I already have cases open with TAC... they've RMA'd my APs and are sending new ones... 

Niten 

Niten,

Please post back and let us know how it turns out.

Hey Colin,

So I was able to get my APs down today and have my AP325 attached to a console cable... below is the output the AP is generating when booting....

APBoot 1.5.5.5 (build 55373)
Built: 2016-06-09 at 11:36:40

Model: AP-32x
DRAM: 235 MB
SF: Detected MX25U3235F with page size 64 kB, total 4 MB
Flash: 4 MB
NAND: 132 MiB
PCIE0: link up
PCIE1: link up
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
Power: 802.3at POE
In: serial
Out: serial
Err: serial
Net: eth0, eth1
Radio: qca9990#0, qca9990#1
Reset: cold
FIPS: passed

Hit <Enter> to stop autoboot: 0
Checking image @ 0x0
Copying image from 0x44000000

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
[ 0.000000]
[ 0.000000] Aruba Networks
[ 0.000000] ArubaOS Version 6.5.4.2 (build 61807 / label #61807)
[ 0.000000] Built by p4build@lesbos on 2017-10-07 at 01:34:34 PDT (gcc versio n 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) )
[ 0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine: IPQ806X wave-2 board
[ 0.000000] Flash variant: default
[ 0.000000] msm_reserve_memory: 0x44600000, 0x200000
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 58154
[ 0.075538] CPU1: Booted secondary processor
[ 0.102249] clk_tbl_nss - loaded
[ 0.212371] PCI: enabling device 0000:02:00.0 (0140 -> 0143)
[ 0.212558] PCI: enabling device 0000:00:00.0 (0140 -> 0143)
[ 4.954545] m25p80 spi5.0: found mx25u3235f, expected s25fl512s
[ 7.407935] Found AT97SC3203 on i2c-gpio0
[ 7.465104] no pmic restart interrupt specified
[ 8.104842]
[ 8.104842] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[ 8.184067] Starting Kernel HMAC-SHA1 KAT ...Starting Kernel DES KAT ...Compl eted Kernel DES KAT
[ 8.290378] Starting Kernel AES KAT ...Completed Kernel AES KAT
[ 8.334114]
[ 8.379912] Completed Kernel HMAC-SHA1 KAT
[ 8.429896] Starting Kernel AESGCM KAT ...Completed Kernel AESGCM KAT
AP-type has_ble_support: ONBOARD.
Domain Name: arubanetworks.com
The APBoot version: 55373
APBoot is up to date
Done.
No panic info available
Writing /dev/ttyHSL2 into /tmp/ble_port
Enabling ble_daemon via nanny
[ 12.407372] nss_driver - fw of size 391744 bytes copied to load addr: 400000 00, nss_id : 0
[ 12.516526] nss_driver - Turbo Support 1
[ 12.551046] Supported Frequencies - 110Mhz 550Mhz 733Mhz
[ 12.621055] nss_driver - fw of size 190016 bytes copied to load addr: 408000 00, nss_id : 1
Ethernet port 1 mode: tunnel
WARNING: eth0 is down; using eth1 for uplink
[ 33.411621] drvlog_mod: module license 'Proprietary' taints kernel.
[ 33.474195] Disabling lock debugging due to kernel taint
[ 33.567447] init_asap_mod: installation:0
[ 33.603061] ethernet_device_event: dev eth0 is up
[ 33.669447] firewall cpu: core-1
[ 34.274570] ethernet_device_event: dev eth0 is changed, carrier: 0
[ 35.492096] ethernet_device_event: dev eth0 is changed, carrier: 1
Starting watchdog process...
Starting update SBL2 ...
SBL2 was updated already
[ 36.566447] Settng Jumbo MRU 2000
Done.
Got all network params from APboot env. Skipping DHCP
Static IP detected. Checking if LACP needs to be configured
LACP setting not required. AP can ping default gateway
192.168.25.5 255.255.255.0 192.168.25.1
Running ADP...cat: /tmp/master: No such file or directory
Done. Master is
cat: /etc/syslog.conf: No such file or directory
killall: nanny: no process killed
killall: sapd: no process killed
Sending SIGKILL to all processes.
Unmounting UBIFS completed.
Please stand by while rebooting the system.
[ 137.327428] Restarting system.

APBoot 1.5.5.5 (build 55373)
Built: 2016-06-09 at 11:36:40

Model: AP-32x
DRAM: 235 MB
SF: Detected MX25U3235F with page size 64 kB, total 4 MB
Flash: 4 MB
NAND: 132 MiB
PCIE0: link up
PCIE1: link up
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
Power: 802.3at POE
In: serial
Out: serial
Err: serial
Net: eth0, eth1
Radio: qca9990#0, qca9990#1
Reset: warm
FIPS: passed

Hit <Enter> to stop autoboot: 0
Checking image @ 0x0
Copying image from 0x44000000

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
[ 0.000000]
[ 0.000000] Aruba Networks
[ 0.000000] ArubaOS Version 6.5.4.2 (build 61807 / label #61807)
[ 0.000000] Built by p4build@lesbos on 2017-10-07 at 01:34:34 PDT (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) )
[ 0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine: IPQ806X wave-2 board
[ 0.000000] Flash variant: default
[ 0.000000] msm_reserve_memory: 0x44600000, 0x200000
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 58154
[ 0.075538] CPU1: Booted secondary processor
[ 0.102624] clk_tbl_nss - loaded
[ 0.214276] PCI: enabling device 0000:02:00.0 (0140 -> 0143)
[ 0.214464] PCI: enabling device 0000:00:00.0 (0140 -> 0143)
[ 4.966135] m25p80 spi5.0: found mx25u3235f, expected s25fl512s
[ 7.484067] Found AT97SC3203 on i2c-gpio0
[ 7.542861] no pmic restart interrupt specified
[ 8.186379]
[ 8.186379] Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
[ 8.265573] Starting Kernel HMAC-SHA1 KAT ...Starting Kernel DES KAT ...Completed Kernel DES KAT
[ 8.371883] Starting Kernel AES KAT ...Completed Kernel AES KAT
[ 8.415620]
[ 8.461449] Starting Kernel AESGCM KAT ...Completed Kernel HMAC-SHA1 KAT
[ 8.583099] Completed Kernel AESGCM KAT
AP-type has_ble_support: ONBOARD.
Domain Name: arubanetworks.com
The APBoot version: 55373
APBoot is up to date
Done.
No panic info available
Writing /dev/ttyHSL2 into /tmp/ble_port
Enabling ble_daemon via nanny
[ 12.458825] nss_driver - fw of size 391744 bytes copied to load addr: 40000000, nss_id : 0
[ 12.568041] nss_driver - Turbo Support 1
[ 12.602561] Supported Frequencies - 110Mhz 550Mhz 733Mhz
[ 12.672571] nss_driver - fw of size 190016 bytes copied to load addr: 40800000, nss_id : 1
Ethernet port 1 mode: tunnel
WARNING: eth0 is down; using eth1 for uplink
[ 33.474539] drvlog_mod: module license 'Proprietary' taints kernel.
[ 33.537113] Disabling lock debugging due to kernel taint
[ 33.630865] init_asap_mod: installation:0
[ 33.666416] ethernet_device_event: dev eth0 is up
[ 33.732895] firewall cpu: core-1
[ 34.331896] ethernet_device_event: dev eth0 is changed, carrier: 0
[ 35.573445] ethernet_device_event: dev eth0 is changed, carrier: 1
Starting watchdog process...
Starting update SBL2 ...
SBL2 was updated already
Done.
[ 36.647797] Settng Jumbo MRU 2000
Got all network params from APboot env. Skipping DHCP
Static IP detected. Checking if LACP needs to be configured
LACP setting not required. AP can ping default gateway
192.168.25.5 255.255.255.0 192.168.25.1
Running ADP...cat: /tmp/master: No such file or directory
Done. Master is
cat: /etc/syslog.conf: No such file or directory
killall: nanny: no process killed
killall: sapd: no process killed
Sending SIGKILL to all processes.
Unmounting UBIFS completed.
Please stand by while rebooting the system.
[ 137.392814] Restarting system.

APBoot 1.5.5.5 (build 55373)
Built: 2016-06-09 at 11:36:40

Model: AP-32x
DRAM: 235 MB
SF: Detected MX25U3235F with page size 64 kB, total 4 MB
Flash: 4 MB
NAND: 132 MiB
PCIE0: link up
PCIE1: link up
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
Power: 802.3at POE
In: serial
Out: serial
Err: serial

I'm packing my old APs up and sending them back... I won't be able to look at the console on them any longer.

Hope my output helped.

Niten 

It might be too late to say this, but it is a best practice to use dhcp for your access points.  If you statically IP them, if you ever wanted to reconfigure your network and you somehow remove the discovery method you first configured, the access points will be dead in the water.  If they were dhcp, they would reboot and discover the controller using any available method like DNS, dhcp option, multicast, etc with minimal effort from you.

With that being said, what was your discovery method initially?

My initial discovery method was ALD... However, I thought I manually configured them to statically point to the controller IP... I set the LMS configuration paramenter to the IP of the controller, but I guess that wasn't suffiicient... 

---

@njaiswal wrote:

My initial discovery method was ALD... However, I thought I manually configured them to statically point to the controller IP... I set the LMS configuration paramenter to the IP of the controller, but I guess that wasn't suffiicient... 

---

So, the LMS-IP is only good if the AP can find the controller after a reboot.  The AP is then redirected to the LMS-IP AFTER it finds the controller.  The LMS-IP does not survive a reboot in most circumstances. 

---

@cjoseph wrote:

It looks like you have the ip address for your access points statically configured.  Are they on the same VLAN as the controller?

---

cjoseph, sorry for the delayed response.  Yes, my controller and WAPs are on the same VLAN.  I saw the recent patch for ArubaOS to 6.5.4.3 was supposed to fix this issue.  I applied it, but since our WAPs have the old firmware on it they are still succeptible to this problem, since they can't get a firmware update from the controller.  So, the only two options that I received from the techs is to factory reset the affected WAPs or to manually assign each one the controller's IP address like I posted before.  In the future I will be using DHCP assigned IP addresses for sure, which would have prevented this issue.