cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
194
Views
0
Helpful
2
Replies

PoE Overload on Cisco 1300

VTH
Level 1
Level 1

Hello,

I've installed a new C1300-24P-4X with firmware 4.1.3.36. It should support PoE+ 802.3at with max 30watts.

I have a TP-Link EAP650 with 802.3.at PoE that should draw 15.4watts on one port but the port flaps and shuts itself of with overload condition.

Ive tried every configuration I know with no cdp, no lldp, no negotioation. but the problem persists.

I have another Catalyst1300 with a newer firmware with the same problem.

Does anybody know how to solve this, and does anybody know why the port type is reported incorrectly? 

 

Port Status:               Port is off. Overload condition
Port standard:             802.3BT Type 3
Admin power limit (for port power-limit mode): 30.0 watts
Time range:
Operational power limit:   30.0 watts
Negotiated power:          0.0 watts (None)
Allocated power:           0.0 watts
Current (mA):              0
Voltage(V):                0.0
Overload Counter:          1648
1 Accepted Solution

Accepted Solutions

So, the missclassification is on all ports. limiting the port to 16000 or disabling lldp and cdp had no effect.

I've noticed that the class was different than on other AP's so I've changed the power limit mode to port.

(power inline limit mode port) and now everything seems to work.

View solution in original post

2 Replies 2

wajidhassan
Level 4
Level 4

The issue you're seeing on the C1300 switch is likely caused by a misclassification during PoE negotiation. Although your TP-Link EAP650 is a PoE+ device (802.3at, up to ~15.4W), the switch incorrectly detects it as a 802.3bt Type 3 device, which expects a higher power profile. This mismatch can trigger an overload condition and cause the port to shut down. To fix this, manually set the PoE limit on the affected port to 16000 milliwatts using the command power inline static max 16000, and disable CDP and LLDP on that port to prevent negotiation interference. If the issue persists, make sure the switch firmware is up to date, as older versions have known PoE-related bugs. If you've done all this and the overload still occurs, it could be a hardware-level incompatibility, and using an external PoE injector might help confirm that.

So, the missclassification is on all ports. limiting the port to 16000 or disabling lldp and cdp had no effect.

I've noticed that the class was different than on other AP's so I've changed the power limit mode to port.

(power inline limit mode port) and now everything seems to work.