cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
7690
Views
5
Helpful
19
Replies

WAP571 PoE+ Issue with 2960-X Switch

reesejacobs
Level 1
Level 1

Site has multiple WAP571 access points (5 total) deployed each connected to a 2960X-24S-L switch. The WAP571 devices are the only devices connected to the 2960X. The WAP571 devices are all running the latest firmware -- 1.0.1.10. The 2960X is running 15.2(2) E6.

 

Every WAP571 device connects to the 2960X and boots properly but each AP is only obtaining 15W from the switch. The APs are unable to negotiate for 802.3at power from the switch which is preferable for the WAP571 devices. I have connected the WAP571 devices to an external PoE+ injector and they work fine with the injector obtaining 30W as expected but this is of course not the optimal solution.

 

There have been various posts about 802.3at negotiation issues between 2960X switches and various Cisco APs but there seems to be no solution. Recommendations in other threads have ranged from setting power inline static max 30000, setting power inline 2x-mode or disabling LLDP power management on the specific switch ports to which the APs are attached. None of these had any effect on the WAP571 devices with the 2960X switch with each AP still drawing only 15W confirmed by examining the switch using show power inline and also the Status page of each of the WAP571 devices. The switch reports each WAP571 as an IEEE PD class 4 device. Interestingly, when using power inline port max 30000, the switch reports 30W being delivered to the WAP571 but the AP still reports on its status page that is powered via 802.3af and not 802.3at.

 

Does anyone have any recommendations or know of a specific fix that will enable the WAP571 APs to work properly with the 2960X switch and obtain the maximum power on their respective ports? I have examined the release notes for the 2960X and found nothing that suggests this issue has been addressed in a subsequent release to 15.2(2) E6. The WAP571 devices are all current on the latest firmware release. The switch is rated for 370W and no other devices are using the switch so the switch has ample capacity to provide full power to the APs. Any help would be appreciated.

19 Replies 19

I did not solve this problem :(

 

Problem - poor testimony for Cisco

Honver Lam
Level 1
Level 1

I am happy to report that the power feature called "2-event classification" has finally resolved this issue on my 3850s. I had to upgrade the 3850s to the 16.3.6 train to get this feature to show up because it was not there in 3.6. I believe other switches such as the 2960x have this feature too.

 

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960x/software/15-2_4_e/configurationguide/b_1524e_consolidated_2960x_cg/b_1524e_consolidated_2960x_cg_chapter_0111111.pdf

Hi all,

This solved my issue.

I am the proud owner of a Cisco Catalyst WS-C2960X -48FPS-L and four WAP571's.
IOS version: Cisco IOS Software, C2960X Software (C2960X-UNIVERSALK9-M), Version 15.2(7)E4

I experienced the same problem. The Catalyst did not give more than 15,4 watts.

The solution for me was to enable "2-event" classification on the ports. (Don't forget to shutdown&enable the ports or pull en re-attach the cable, so the IEEE can re-initialize)

 

The WAP doesn't give the message anymore....SUCCES!

 

and the catalyst now shows on the interface:

 

Inline Power Mode: auto
Operational status: on
Device Detected: yes
Device Type: Ieee PD
IEEE Class: 4
Discovery mechanism used/configured: Unknown
Police: off

Power Allocated
Admin Value: 30.0
Power drawn from the source: 30.0
Power available to the device: 30.0

Actual consumption
Measured at the port: 8.5
Maximum Power drawn by the device since powered on: 10.3

Absent Counter: 0
Over Current Counter: 0
Short Current Counter: 0
Invalid Signature Counter: 0
Power Denied Counter: 0

Power Negotiation Used: None
LLDP Power Negotiation --Sent to PD-- --Rcvd from PD--
Power Type: - -
Power Source: - -
Power Priority: - -
Requested Power(W): - -
Allocated Power(W): - -

Four-Pair PoE Supported: No
Spare Pair Power Enabled: No
Four-Pair PD Architecture: N/A

vconn
Level 1
Level 1

hi, yes you have to enable lldp to the 2960. the wap is using lldp instead of the cdp protocol to negotiate the power settings.
by default lldp is not running on the 2960.
to enable go to config mode and issue the lldp run command to enable lldp on all ports

weberr
Level 1
Level 1

Same/similar problem here.

 

I have a WAP571 connected to a WS-C2960X-48FPD-L that fails to correctly negotiate PoE. The AP claims

"The power source of WAP device is using IEEE 802.3af PoE standard provides. The device will run in lower CPU frequency and turn off ETH1 Ethernet port, the wireless will also use 2 antennas to transmit & receive data. It is highly recommended using IEEE 802.3at Power Source Equipment (PSE) to get the best performance. If the required power by the WAP device exceeds the maximum power delivered by the PSE, then the WAP device may reboot."

And indeed eth1 is disabled.

This appears to be a known issue that was supposedly fixed (from the FW release notes):

"The following issues have been fixed in firmware version 1.0.2.6
CSCvi23179 PoE power fails to negotiate correctly with Catalyst switch"

AP was shipped with FW 1.0.1.12, so I upgraded to 1.1.0.3 - no luck. Also tried 1.0.2.6 - same.

 

AP's view:

PID VID: WAP571-E-K9 V02
Serial Number: PSZ2xxx
Host Name: wap9989e0
MAC Address: 70:F0:96:xx:xx:xx
IPv4 Address: 192.168.x.x/x(STATIC)
IPv6 Address:
(DHCP)
ETH0/PD Port: Up 1000Mbps Full
ETH1 Port: Down
Radio 1 (5 GHz): Down
Radio 2 (2.4 GHz): Down
Power Source: 802.3af PoE
System Uptime: 0 days, 0 hours, 42 minutes
System Time: Tuesday, 2021-Nov-16, 14:11:20 MEZ
Firmware Version (Active Image): V1.1.0.3
Firmware MD5 Checksum (Active Image):
fa5d1e676ce6f8c241c3b1bd4d2ac0d5
Firmware Version (Non-active): V1.0.1.12
Firmware MD5 Checksum (Non-active):
0f49bc0fd9a1d5ed31a9cc29e41a189b

The switch tells me this:

switch1#show power inline gigabitEthernet 3/0/47 detail
Interface: Gi3/0/47
Inline Power Mode: auto
Operational status: on
Device Detected: no
Device Type: Ieee PD
IEEE Class: 4
Discovery mechanism used/configured: Unknown
Police: off

 

Power Allocated
Admin Value: 30.0
Power drawn from the source: 22.4
Power available to the device: 22.4

 

Actual consumption
Measured at the port: 4.9
Maximum Power drawn by the device since powered on: 7.0

 

Absent Counter: 0
Over Current Counter: 0
Short Current Counter: 68655
Invalid Signature Counter: 0
Power Denied Counter: 0

 

Power Negotiation Used: IEEE 802.3at LLDP
LLDP Power Negotiation --Sent to PD-- --Rcvd from PD--


Power Type: Type 2 PSE Type 2 PD
Power Source: Primary unknown
Power Priority: low unknown
Requested Power(W): 19.0 19.0
Allocated Power(W): 19.0 0.0

 

From the switch's view everything appears OK - IEEE 802.3at LLDP, Type 2, Class 4, 19W.

Switch is way under its power limit.

 

Have not yet tried disabling green ethernet, will try this now.

Review Cisco Networking for a $25 gift card