EAP670 PD Over Current indication
I have discovered at least one reason for my EAP670v1 reboot - they're being reset by the switch for drawing too much power. Now, I had seen this before and have tried multiple adjustments of the PoE settings. It should be noted that I have many, many of the PoE switched in question and they work fine for all other PoE devices other than these, including all of the other PoE devices on this current switch. I have allocated an eye-popping 25w of power for these 670s, and they still continue to generate the following error and get reset by the switch W 05/08/24 21:04:29 00562 ports: port 14 PD Over Current indication.
this feels like a fairly serious bug, but all of my data is anecdotal: switches of same type have no poe issues, all other poe devices on same device work fine, power availability is within spec.
I am still on 1.0.13, and have seen this issue on older versions as well. Upgrading to 1.0.14 is a non-starter because all EAP670s consistently disconnect from the controller (already a ticket open for that, it is very reproducable).
switch configuration:
interface 14
name "Core: wap-ax-1"
power-over-ethernet critical
poe-allocate-by value
poe-value 25
poe-lldp-detect enabled
tagged vlan 4,6-7,9
untagged vlan 809
exit
core# show power-over-ethernet brief
Status and Configuration Information
Available: 370 W Used: 101 W Remaining: 269 W
PoE Pwr Pwr Pre-std Alloc Alloc PSE Pwr PD Pwr PoE Port PLC PLC
Port Enab Priority Detect Cfg Actual Rsrvd Draw Status Cls Type
------ ---- -------- ------- ----- ------ ------- ------- ------------ --- ----
...
14 Yes critical on value value 29.3 W 8.5 W Delivering 4 2
Has anyone else seen this? I've got an older Juniper PoE switch I can test with as well, but I don't think that's really the issue and I'd rather not power that power hungry beast back on. I also have a spare Aruba switch I can try, but again, I don't see that as the issue.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I've basically had to do the same thing but am using a managed PDU for reboots with the injectors plugged into that. Do you have timeouts / heartbeats missed on 1.0.13? that's the only stable release I have found, even on injectors. It seems stable but comes with a ridiculous DNS bug that is mostly cosmetic but very irksome.
I would not consider these APs ready for any kind of profssional use at this point.
- Copy Link
- Report Inappropriate Content
I give up on these 670s.
They're precarious on a good day and downright unreliable on a bad day. I've ordered some Aruba to replace them.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1718
Replies: 22
Voters 0
No one has voted for it yet.