I have a problem with AP-275. I'm using HP procurve 2530 to connect three access points, two 225 and one 275. AP 225 are working fine but AP-275 doesn't get enough power. I have always same error:
Sep 22 12:37:41 KERNEL(Piscina_Principal@172.16.253.5): [ 87.699373] bonding: bond0: releasing backup interface eth1Sep 22 12:37:41 KERNEL(Piscina_Principal@172.16.253.5): [ 87.788414] Disable device eth1 due to insufficient POE voltage.
I have disconnected AP's 225, and i tried to boot with only one AP 275, but doesn't work.
If I take a look to AP 275 Power system status I have this message:
I have another HP procurve 2530 with two AP275 and no one is working. Same problem too.
I have an Aruba controller 7210 with firmware version 18.104.22.168
Any idea where is the problem?
Thank you in advance.
It looks like LLDP on the HP switch is overriding what the power draw is to the AP. Can you verify that there is an LLDP policy on the port?
I have tried with LLDP enabled in the swtich and LLDP disabled. Doesn't work. With LLDP disabled I have this view:
This sounds like an HP switch config issue. Please see this link as I am not an HP CLI expert :)
Could be, but.., shouldn't work same port configuration as for an AP225??. I have same PoE configuration in all HP procurve ports and works fine with AP-225
Yes but the 225 will work with af power (negotiated)
I take this all back. I was just informed that we have a fix for this in 22.214.171.124 which was released Friday. Can you please upgrade and re-test!
Sorry about the back and forth
I will try to upgrade in a few days..
Thank you for your help.
I had three AP275 with this problem with AOS version 126.96.36.199
After upgrade to 188.8.131.52 version one of those three AP-275 start working (All HP Procurve ports with same configuration).
What I finally did to have those two AP275 working was configure HP Procurve switch this way:
That configuraction works, so I finally have all my AP-275 working.
I tried those commands on a 2920 to no avail. I also noticed that even though you
invoke the "poe-lldp-detect disable" command the port still shows that as enabled.
So, I enabled it, then configured the other two parameters, then disabled it,
the did a power/no power and that did the trick. Sheesh.
That same thing worked on both WB.15.13.0005 and WB.15.11.0007
Thanxo mucho for finding that.
Hey - can you give me a little more detail on your steps? I am in the same situation - despite the disabling LLDP, my HP2530 shows it enabled. What's the power/no power mean?
despite what I do with lldp-detect, my interface looks like:
interface 1power-over-ethernet criticalpoe-allocate-by valuepoe-value 25exit
lldp admin-status X tx_rx
thanks, but it's still showing LLDP enabled on the gui, and the cli command file shows nothing in this area.
One thing I noticed in the gui is Dot3 LLDP TLV and Poe LLDP-MED. I am not able to disable the former. And I can't find where that might be in the cli.
thanks, great to be working with someone on this!
...but are the radios up after doing that and letting the AP reboot. That is the question.
Yes the GUI always show poe lldp detection enabled even though the default is disabled
and no matter what you do with the setting. Probably a bug in the GUI.
actually seems a step backwards. Now after rebooting the AP-275, the controller doesn't see it.
Status light on the AP is blinking green and the switch giu says it's current watts are 26.
I'll let it sit like this a bit and see if it connects.
Check to make sure you didn't knock your uplink port out?
They do take a while to register as up. You can see their real status with "show ap database"
I had provisioned the AP with a name and rebooted it.
sh ap-database now shows this with its MAC address and it shows it as down.
Maybe I'll go with a POE injector to get it fully recognized, and then see if I can make it work with just the switch.
pain in the neck!
No joy for me so far. In fact, the 275 I had been playing with is now not recognized by the controller, even with a POE injector or connection to an Aruba switch. I'll end up consoling in and do a reset.
It's possible that the poe "optimization" borked my 275. I rolled that change back and hadn't rebooted any other AP's.
So for now, I have an ugly pile of POE injectors. And at $65 per, it's an irritating additional expense. But I will return to the HP switch configuration as time allows.
From the description of the feature I would expect applying the PoE optimization to an AP-275 would do one of two things: refuse to apply, or render the AP useless until it is put back to normal.
Thanks bjulin, the HP commands worked for me. I can confirm that the poe optimization makes the 275 non-responsive. I'm glad I found that out on a lab AP, and not on my 30 installed outdoors. The only thing that brought the lab AP back to life was an apboot>factory_reset, and the only way to accomplish that was with the micro USB console connection. To have done that up a ladder and then have to reload each AP installation would have been a giant pain.
I suppose I need to read up on effective ways to roll-out changes. If I had poe-optimimzed and then rebooted the controller, I would have rolled this change out to all of my AP's!
The only other challenge on an 8 ports HP 2530 is that 2 275's and 1 134 were right at the 67W power budget. I had to make the 134 "critical", one of the 275's "High" and one "low" in order to bring all three up on a switch reboot. I am investigating if there's another way to stagger port booting on this switch, because I think the problem only arises at initial power on of all 3.
Thanks for your help!
But they are working with 802.3at:
Same switch, same port configuration, 225 are working but AP 275 are not working. I have tried with just one AP-275 connected to avoid lack of PoE power, but doesn't work.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.