Wireless Access

Hi all,

only 1 of my 40 AP93 reboot periodically and sometime stay down for long period. For example today I found this AP down in the "show ap database", but the HP switch interace is UP with speed of only 10M! I replaced the AP with another, that works properly.

In the Aruba3200 log message I see this:

Jan 27 13:45:23  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x10000 miictrl
Jan 27 13:45:23  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 13:45:23  KERNEL(AP42-Pal01@192.168.150.219): RGMii 100Mbps full duplex
Jan 27 14:28:51  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x10000 miictrl
Jan 27 14:28:51  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 14:28:51  KERNEL(AP42-Pal01@192.168.150.219): RGMii 100Mbps full duplex
Jan 27 14:30:47  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x0 miictrl
Jan 27 14:30:47  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 14:30:47  KERNEL(AP42-Pal01@192.168.150.219): RGMii 10Mbps full duplex
Jan 27 14:33:24  nanny[1543]: <303086> <ERRS> |AP AP42-Pal01@192.168.150.219 nanny| Process Manager (nanny) shutting down - AP will reboot!
Jan 27 14:33:24  nanny[1543]: <303086> <ERRS> |AP AP42-Pal01@192.168.150.219 nanny| Process Manager (nanny) shutting down - AP will reboot!
Jan 27 14:33:24  sapd[1604]: <311002> <WARN> |AP AP42-Pal01@192.168.150.219 sapd|  Rebooting: SAPD: Unable to contact switch. Called by sapd_hello_cb:4.  HBT miss seq_gen=22110 seq_snt=22103 seq_rcv=22102 233 sec bef: Last Ctrl message: HELLO len=1004 dest=192.168.0.72 tries=10 seq=0
Jan 27 14:34:34  nanny[880]: <303022> <WARN> |AP AP42-Pal01@192.168.150.219 nanny|  Reboot Reason: AP rebooted Mon Jan 27 14:33:24 GMT 2014; SAPD: Unable to contact switch. Called by sapd_hello_cb:4. HBT miss seq_gen=22110 seq_snt=22103 seq_rcv=22102 233 sec bef: Last Ctrl message: HELLO len=1004 dest=192.168.0.72 tries=10 seq=0
Jan 27 14:36:38  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x10000 miictrl
Jan 27 14:36:38  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 14:36:38  KERNEL(AP42-Pal01@192.168.150.219): RGMii 100Mbps full duplex
Jan 27 14:42:06  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x10000 miictrl
Jan 27 14:42:06  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 14:42:06  KERNEL(AP42-Pal01@192.168.150.219): RGMii 100Mbps full duplex
Jan 27 14:43:00  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x10000 miictrl
Jan 27 14:43:00  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 14:43:00  KERNEL(AP42-Pal01@192.168.150.219): RGMii 100Mbps full duplex
Jan 27 15:03:39  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x10000 miictrl
Jan 27 15:03:39  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 15:03:39  KERNEL(AP42-Pal01@192.168.150.219): RGMii 100Mbps full duplex
Jan 27 15:14:32  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x10000 miictrl
Jan 27 15:14:32  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 27 15:14:32  KERNEL(AP42-Pal01@192.168.150.219): RGMii 100Mbps full duplex
Jan 28 08:26:09  KERNEL(AP42-Pal01@192.168.150.219): AG7240: done cfg2 0x7115 ifctl 0x0 miictrl
Jan 28 08:26:09  KERNEL(AP42-Pal01@192.168.150.219): AG7240: enet unit:0 is up...
Jan 28 08:26:09  KERNEL(AP42-Pal01@192.168.150.219): RGMii 10Mbps full duplex

The version of my controller is  6.1.3.10.

What could it be? I have already checked the VLAN configuration and it's ok, the same of the other APs on the same switch; in fact all the other APs on the same switch work fine.

Thanks,

Massimo

Hello

It seems that the problem is that the ap is unable to see the controller...

Something is happening which makes him unable to see it.

It could be maybe a port of the switch issue, or cabling issue... or the ap itself..

An easy way to troubleshoot it, is to swap 2 AP 93

take one working AP 93 and plug it to the same port in which the AP is not working

And take the non working AP to the port in which the working AP is working.

This way you will be able to test the switch port and the cabling and everything...

Ifyou see that the AP which had NO issue start happening the same issue then you know its NOT The AP

IF you see that the non working AP start having issue even if he is connected to the port of the switch which had no issue then is most likely the AP.

If you see the problem isthe AP then you will need to open  a support case for the RMA.

Cheers

Carlos

Thanks Carlos!
In fact I have already replaced the problematic AP with another and the new AP is working from 5 hours; I keep the situation under observation in the next days. I will also test the problematic AP in the our lab.