C3650 PoE issues with Yealink phones

[0rsnaric]

We are having problems with Yealink phones and PoE. Our environment has some 60 C3650 switch stacks in place. Until recently, the only PoE we have drawn from them has been to Cisco APs, miscellaneous cameras, and door locks. No problems.

Now we are plugging Yealink phones in, and now we are seeing an alarming number of PoE failures. The phones simply do not power up, and once a port has acted this way, nothing else will work for PoE in that port. If we move the phone 8 or more ports in any either direction, we can get PoE.

There are no log entires

Has anybody had similar PoE issues with Yealink, or the C3650's? We are running 16.12.05b CAT3K_CAA-UNIVERSALK9.

Thank you!

Rick

[balaji.bandi]

what is the model of the phone, what kind of power is it needed?

what is the power available on the device, show power inline give you information before you plug in the phone.

what is the port config looks like show run will help.

[0rsnaric]

The phones are Yealink Sip-T53s. Once up and running they are drawing 7 Watts per port and show as a class 2 device.

Our switches have more than enough available power, here is from a switch that just had a failure:

Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- -------- ---------
1 775.0 98.8 676.2
Interface Admin Oper Power Device Class Max

676.2 watts remaining.  Roughly 8 ports that aren't giving power right now, no errors.

Port config:

interface GigabitEthernet1/0/1
description Available
switchport access vlan 60
switchport mode access
switchport voice vlan 5
switchport port-security maximum 11
switchport port-security violation restrict
switchport port-security aging time 2
switchport port-security aging type inactivity
switchport port-security
load-interval 30
authentication host-mode multi-domain
authentication open
authentication order mab dot1x
authentication priority dot1x mab
authentication port-control auto
authentication timer inactivity server
mab
dot1x pae authenticator
spanning-tree portfast
end

Thank you!

[Leo Laohoo · Accepted solution]

---

@0rsnaric wrote:

If we move the phone 8 or more ports in any either direction, we can get PoE.

---

Catalyst 9k, 3650/3850 loaded with 16.12.X have known PoE bugs attributed to SNMP.  CSCvv28324 is for 3650/3850 and CSCvi48988 is for Catalyst 9k. 

According to the Bug IDs, the "trigger" is DOM optics (and I have seen people who have never used optics hit this bug). 

There are several ways of verifying if this is the bug affecting the stack: 

1.  Firmware is 16.12.X, particularly 16.12.4 and later.  This means 16.12.4 (and whatever re-build there is) and 16.12.5 (and whatever rebuild, like 16.12.5b).

2.  Moving the PED to different ports (like what you've just done) or different switch members.  

3.  Reboot the switch member (not the switch stack) and PoE goes good. 

4.  Uptime of >4 weeks

There is an SMU update patch (filename:  cat3k_caa-universalk9.16.12.04.CSCvv28324.SPA.smu.bin) and I am 100% sure the SMU patch do not work and will just annoy operators.  

There is an SNMP workaround and this might work.

NOTE:  

The last-and-final IOS-XE release for the 3650/3850, 16.12.6, will be released by September 2021.  It is not certain if this bug will be fixed or not.  Caveat emptor.