09-05-2014 11:21 AM - edited 09-05-2014 02:51 PM
I have identically configured AP-275's. On occassion, some of them throw an I flag (inactive) on the controller. As far as Airwave is concerned, they are up. The only thing that clears the I flag seems to be a POE power cycle. Doing a reboot does not do the trick.
These AP's and their network connections are in a zoo's animal areas, so they are very inconvenient to physically lay hands on.
Any suggestions? The 275's that I have connected to an Aruba POE switch have not yet experienced this problem. It's only the ones with POE injectors. But it's only some of those, and they are the same POE throughout.
One of the ones that is currently showing I is pingable with a 3 ms roundtrip. And if I look at the switch port, I see no ethernet errors. Everything looks normal, but no clients connect and I have an inactive flag showing.
09-05-2014 02:14 PM
another data point as I just reset the POE and cleared the 2 I flags. When it was in I status, the AP had a solid red light. Upon boot, it flashed amber and green alternately. Is the light status documented somewhere?
It definitely does seem POE related. To clear these, I just briefly unplugged and replugged the CAT 6 cable that provided power to the AP. The POE was lit amber until I did do, then it went green.
09-05-2014 09:50 PM
Not sure what your issue ultimately was caused by, but the LED status is described in the AP-270 installation guide and depicted below.
Systems Engineer, Northeast USA
ACCX | ACDX | ACMX
09-08-2014 05:35 AM
Thanks. It's definitely POE related. We had some power browns and, despite being on a surge protected UPS, the POE seemed to hang up. The AP was lit red. I unplugged the powered CAT6 and plugged it back in, and that brought the AP back.
I guess I consider it a bug that Airwave reports this AP as up while the controller has it in Inactive status. As it is, I need to check the controller flags and status manually if I suspect a problem or see a red light on the AP.
11-30-2014 08:38 PM - edited 11-30-2014 08:51 PM
Hi, I am now seeing similar problems on AP-275 and AP-274... did this problem reoccur for you?
Edit: more info, exact same symptoms, mine occured only after provisioning. Before provisioning all 5 APs were up in default group, after provisioning only 2 APs re-registered. The other 3 have the exact same config, same connected switch config, are pingable but will not register to master. There are mildly intelligible debug logs relating to POE and LACP. Version 184.108.40.206. Opened a TAC case, but thought I'd canvas here as well and record issue for others.
Edit2: I tried disabling the second AP port and LACP on the switch. Voila, the AP registered. But I then noticed it still thought LACP was active (show ap debug lacp). So rebooted and now same problem, AP won't register but is pingable.
12-01-2014 05:39 AM
For me, a pingable 275 that is seen by Airwave but shows an "I" flag in the controller has always been power related. There's enough power to boot the AP and its LAN interface, but not enough power to power up the radios. I have a few HP switches that have to be configured to provide 26W to each port. In other cases, a power outage or brownout puts the POE in a weird state, so I need to unplug and replug those.
12-01-2014 12:34 PM
There's a known issue with the 275 combined with certain switches not dealing well when LLDP takes too long to negotiate, and the workaround
is to mess with the LLDP settings on the switch ethernet ports.
12-01-2014 02:47 PM - edited 12-01-2014 02:56 PM
Thanks for the tip!
These are Avaya switches, so apparently not fixed in 220.127.116.11 for these..