Frequent PoE Loss - SG300-52MP

[ksbolton1]

Hello all.

We currently have a couple SG300 SBS devices in our warehouse meant primarily for PoE access for Cisco APs and cameras (TVT brand).

I've seen on different occasions where these SG300 (inclusive of SG300-10 & SG350-10MP) just "freeze" and lose native vlan config (the 300-10) or stop providing PoE power (in case of the 300-52MPs and the 350-10MP).

52MPs are powering multiple cameras along with some wireless APs while that 350 is just keeping a mesh AP up in our wireless bridge. We're well below our 740W power budget  with the most utilized switch using just 77W. The strange thing is that switch doesn't seem to be throwing this log I see on the less utilized devices:

%HAL_config_poe-I-PSE-PORT-ON-OFF-TRAP: Pse Port gi29 is not delivering power to the PD

Could anyone shed some light on why this is happening? I'm currently running 1.4.8.6 on the 300-52MP (I haven't been able to secure downtime to reboot for upgrade) and 1.4.9.4 on 350-10MP. 

If it is the firmware version, is there any changelog that addresses this? I've yet to find it.

[balaji.bandi]

This required some one need to log and see what is wrong in the switch.

have you contacted cisco TAC small busines.

[mipopov]

Hello, 

Happy New 2019 Year!

Sx300 and Sx350 are different series switches. 

The latest firmware for Sx300 is 1.4.9.4 

https://software.cisco.com/download/home/284576363/type/282463181/release/1.4.9.4?i=!pp

The latest firmware for Sx350 is 2.4.5.71

https://software.cisco.com/download/home/286288221/type/282463181/release/2.4.5.71?i=!pp 

What shows the command? :

switchxxxxxx# show power inline

Try to disable EEE (Energy Efficient Ethernet):

switchxxxxxx(config)# no eee enable

What happens?

Cheers,

Mike

[ksbolton1]

I stand corrected. I'm running 2.4.0.94 on the SG350.

#sho power inline

Class based power-limit mode
Inrush Test: Enable
Legacy Mode: Enable

Unit Power Nominal Power Consumed Power Usage Threshold Traps Temp (C)
---- ------- ------------- ------------------ --------------- --------- --------
1 On 740 Watts 60 Watts (8%) 95 Enable 59


Port Powered Device State Status Priority Class
-------- -------------------- ---------------- ------------ -------- ---------
gi1 Auto On high class4
gi2 Auto On low class4
gi3 Auto On low class4
gi4 Auto On low class4
gi5 Auto Searching low class4
gi6 Auto Searching low class4
gi7 Auto Searching low class4
gi8 Auto Searching low class4
gi9 Auto Searching low class4
gi10 Auto Searching low class4
gi11 Auto Searching low class4
gi12 Auto Searching low class4
gi13 Auto Searching low class4
gi14 Auto Searching low class4
gi15 Auto Searching low class4
gi16 Auto Searching low class4
gi17 Auto Searching low class4
gi18 Auto Searching low class4
gi19 Auto Searching low class4
gi20 Auto Searching low class4
gi21 Auto Searching low class4
gi22 Auto Searching low class4
gi23 Auto Searching low class4
gi24 Auto Searching low class4
gi25 Auto On critical class3
gi26 Auto On critical class3
gi27 Auto On critical class3
gi28 Auto On critical class3
gi29 Auto On critical class3
gi30 Auto On critical class3
gi31 Auto Searching low class4
gi32 Auto Searching low class4
gi33 Auto Searching low class4
gi34 Auto Searching low class4
gi35 Auto Searching low class4
gi36 Auto Searching low class4
gi37 Auto Searching low class4
gi38 Auto Searching low class4
gi39 Auto Searching low class4
gi40 Auto Searching low class4
gi41 Auto Searching low class4
gi42 Auto Searching low class4
gi43 Auto Searching low class4
gi44 Auto Searching low class4
gi45 Auto Searching low class4
gi46 Auto Searching low class4
gi47 Auto Searching low class4
gi48 Auto Searching low class4

Disabled EEE. I wish I had known it'd have bounced the ports (haha). I will observe the switch and see if the ports still seem to be bouncing. 

[mipopov]

Hi again,

The output from show power inline looks good - no errors :)

If you suspect particular port - check also the cable - the command is (* bear in mind that it will disconnect the device briefly):

switchxxxxxx# test cable-diagnostics tdr interface gi29

Then you can test another port if you like.

After initial testing, you can show the testing results for all ports:

switchxxxxxx# show cable-diagnostics tdr

Cheers, 

Mike

[ksbolton1]

It seems this still happens even with EEE disabled. I haven't looked back at it in all this time because the SBS switches are really the bane of our collective L2 existence. I'm just looking at the switch ports randomly deciding to drop power.

Example config:
no eee enable
flowcontrol auto
negotiation preferred master
description "TR-71nw Temp. Logger"
spanning-tree portfast
spanning-tree link-type shared
power inline priority critical
switchport mode access
switchport access vlan 5
no macro auto smartport





no eee enable
description "TR-71nw Temp. Logger"
spanning-tree portfast
power inline priority critical
switchport mode access
switchport access vlan 5