01-19-2022 10:02 PM - edited 01-19-2022 10:04 PM
I have replaced my old SG300-10P with a new CBS350-8P-E-2G but having some problem with PoE and a IP phone. When I reboot the switch it works for few hours and then the phone is off, i.e. has no power. I have only two PoE devices connected, an access point and this ip phone. The access point works fine all the time. From the specs both devices are far from exceeding the possible poe limits of the switch. Both worked fine on the old switch.
While it's working, it all looks good:
sw2(config)#do show power inline Power-limit mode: Port based Usage threshold: 95% Trap: Disable Legacy Mode: Enable Inrush Test: Enable Guard-Band Value: Static (2W) Unit Module Nominal Consumed Temp SW PSE chipset Power (W) Power (W) (C) Version HW Revision ---- -------------- --------- ------------ -------- ------------- ----------------- 1 CBS350-8P-E-2G 60 17 (28%) 52 0.2.0.17 TPS2388 - 0x40C4 Interface Admin Oper Power (W) Class Device Priority ---------- ---------- ----------- ----------------- ----- -------------- -------- gi1 Auto On 6.839 (15.4) 4 low gi2 Never Searching 0.0 - low gi3 Never Searching 0.0 - low gi4 Never Searching 0.0 - low gi5 Never Searching 0.0 - low gi6 Never Searching 0.0 - low gi7 Auto On 2.35 0 low gi8 Never Searching 0.0 - low sw2(config)#do show power inline ge7 Interface Admin Oper Power (W) Class Device Priority ---------- ---------- ----------- ----------------- ----- -------------- -------- gi7 Auto On 2.35 0 low Port Status: Port is on. Valid resistor detected Port standard: 802.3AT Admin power limit: 30.0 watts Time range: Link partner standard: 802.3AT Max Power Allocation: 30.0 watts Spare pair: Disabled Negotiated power: 0.0 watts (None) Current (mA): 44 Voltage(V): 53.0 Overload Counter: 32 Short Counter: 0 Denied Counter: 415164 Absent Counter: 15 Invalid Signature Counter: 0
However, a few hours later the port goes down:
20-Jan-2022 00:26:36 :%LINK-W-Down: gi7 19-Jan-2022 20:27:50 :%STP-W-PORTSTATUS: gi7: STP status Forwarding 19-Jan-2022 20:27:45 :%LINK-I-Up: gi7
And the state is at fault:
sw2#show power inline Power-limit mode: Port based Usage threshold: 95% Trap: Disable Legacy Mode: Enable Inrush Test: Enable Guard-Band Value: Static (2W) Unit Module Nominal Consumed Temp SW PSE chipset Power (W) Power (W) (C) Version HW Revision ---- -------------- --------- ------------ -------- ------------- ----------------- 1 CBS350-8P-E-2G 60 15 (25%) 52 0.2.0.17 TPS2388 - 0x40C4 Interface Admin Oper Power (W) Class Device Priority ---------- ---------- ----------- ----------------- ----- -------------- -------- gi1 Auto On 6.84 (15.4) 4 low gi2 Never Fault 0.0 - low gi3 Never Fault 0.0 - low gi4 Never Fault 0.0 - low gi5 Never Fault 0.0 - low gi6 Never Fault 0.0 - low gi7 Auto Fault 0.0 - low gi8 Never Fault 0.0 - low sw2#show power inline gi7 Interface Admin Oper Power (W) Class Device Priority ---------- ---------- ----------- ----------------- ----- -------------- -------- gi7 Auto Fault 0.0 - low Port Status: Port is off. Power budget exceeded Port standard: 802.3AT Admin power limit: 30.0 watts Time range: Max Power Allocation: 30.0 watts Spare pair: Disabled Negotiated power: 0.0 watts (None) Current (mA): 0 Voltage(V): 0.0 Overload Counter: 36 Short Counter: 0 Denied Counter: 444802 Absent Counter: 17 Invalid Signature Counter: 0
Even the other ports which don't use PoE and where I have disabled PoE are at fault and report overload state
Port Status: Port is off. Overload state
According to the specs the IP phone is 802.3af class 0 with a max of 3.5W.
I wouldn't know how to exceed the power budget or overload the system with these two devices and all other ports with poe disabled. The SG300 didn't have a problem with those two devices.
Initially, I had class based power-limit and I have switched to port based for tests, but no change.
I also don't see how to reset the fault state on a port to get it working again, excepting for switching the power-limit mode which resets all poe ports or rebooting...
01-19-2022 11:44 PM
Looks something gone wrong as per the output, turn off the device and turn on and connect each device and test it.
still same issue suggest to raise SMB TAC case.
01-20-2022 02:07 AM
Hi,
We had similar issues with the CBS250-8P
Have over 60 of these switches installed, PoE was unreliable until I made the following change to each switch.
conf
power inline limit-mode port
(press y to restart PoE on switch)
copy ru st
(press y to save)
This fixed our PoE issues
01-20-2022 09:04 AM
As I have mentioned before, I have tried class based and port based power-limit mode, but I have the same problem with either one...
02-22-2022 06:43 PM - edited 02-22-2022 07:02 PM
Hi Gerald,
Did you ever find a solution? I am facing the same issue on a CBS350-24P-4G and CBS350-8P-E-2G running 3.1.1.7 and floored that the switch is trying to perform POE operations ports that are clearly disabled.
#show running-config | i eee|^power no eee enable power inline limit-mode port power inline inrush test disable
#show running-config interface GigabitEthernet 11 interface GigabitEthernet11 shutdown description [UNUSED] switchport access vlan none switchport trunk native vlan none switchport trunk allowed vlan none power inline limit 0 power inline never
#show running-config interface GigabitEthernet 24 interface GigabitEthernet24 shutdown description [UNUSED] switchport access vlan none switchport trunk native vlan none switchport trunk allowed vlan none power inline limit 0 power inline never
#show power inline GigabitEthernet 11 Interface Admin Oper Power (W) Class Device Priority ---------- ---------- ----------- ----------------- ----- -------------- -------- gi11 Never Searching 0.0 - low Port Status: Port is off. Detection is in process Port standard: 802.3AT Admin power limit: 0.0 watts Time range: Max Power Allocation: 0.0 watts Spare pair: Disabled Negotiated power: 0.0 watts (None) Current (mA): 0 Voltage(V): 0.0 Overload Counter: 0 Short Counter: 0 Denied Counter: 0 Absent Counter: 0 Invalid Signature Counter: 0
#show power inline GigabitEthernet 24 Interface Admin Oper Power (W) Class Device Priority ---------- ---------- ----------- ----------------- ----- -------------- -------- gi24 Never Fault 0.0 - low Port Status: Port is off. Overload state Port standard: 802.3AT Admin power limit: 0.0 watts Time range: Max Power Allocation: 0.0 watts Spare pair: Disabled Negotiated power: 0.0 watts (None) Current (mA): 0 Voltage(V): 0.0 Overload Counter: 1 Short Counter: 0 Denied Counter: 0 Absent Counter: 0 Invalid Signature Counter: 0
Thank you in advance for any suggestions that you may have!
02-23-2022 01:52 AM
@d0nni3q84 wrote:Did you ever find a solution? I am facing the same issue on a CBS350-24P-4G and CBS350-8P-E-2G running 3.1.1.7 and floored that the switch is trying to perform POE operations ports that are clearly disabled.
After a couple of more tests on my old switch as well as using the phone with a power injector on the new switch I have decided to open a tac case today. Still waiting for the outcome...
02-24-2022 03:07 PM - edited 02-24-2022 03:11 PM
Thanks, Gerald! I also opened a case today and asked for an escalation to the software development team.
@ciscosupport @balaji.bandi This is really unfortunate and putting me in production pain with limited options. The options that exist are forcing me into a financial burden to procure competitive equipment and also have no choice but to recommend against any and all CBS products. Please treat this as a grave issue that needs immediate attention.
#show power inline
Power-limit mode: Port based
Usage threshold: 95%
Trap: Disable
Legacy Mode: Enable
Inrush Test: Disable
Guard-Band Value: Static (2W)
Unit Module Nominal Consumed Temp SW PSE chipset
Power (W) Power (W) (C) Version HW Revision
---- -------------- --------- ------------ -------- ------------- -----------------
1 CBS350-24P-4G 195 4 (2%) 72 0.2.0.17 TPS2388 - 0x40C4
TPS2388 - 0x40C4
TPS2388 - 0x40C4
Interface Admin Oper Power (W) Class Device Priority
---------- ---------- ----------- ----------------- ----- -------------- --------
gi1 Never Off 0.0 - low
gi2 Never Off 0.0 - low
gi3 Never Off 0.0 - low
gi4 Never Off 0.0 - low
gi5 Never Off 0.0 - low
gi6 Never Searching 0.0 - low
gi7 Never Off 0.0 - low
gi8 Never Off 0.0 - low
gi9 Auto On 3.599 4 Access-Point low
gi10 Auto Fault 0.0 - Access-Point low
gi11 Never Fault 0.0 - low
gi12 Never Fault 0.0 - low
gi13 Never Fault 0.0 - low
gi14 Never Fault 0.0 - low
gi15 Never Fault 0.0 - low
gi16 Never Searching 0.0 - low
gi17 Never Fault 0.0 - low
gi18 Never Fault 0.0 - low
gi19 Never Fault 0.0 - low
gi20 Never Fault 0.0 - low
gi21 Never Fault 0.0 - low
gi22 Never Fault 0.0 - low
gi23 Never Fault 0.0 - low
gi24 Never Fault 0.0 - low
02-25-2022 01:40 AM
as per community concern, we are not cisco TAC, we are like you as user, based on experience we try to help each other to resolve the issue, and learn new things, anything related hardware fault and software bugs, Cisco TAC is your right contact, not an any individual is your contact of communication.
understand the situation, some time its hard with cisco TAC, depends where the call will be routed.
03-07-2022 07:29 AM
Cisco TAC thinks the problem is related to open bug CSCvz97713. A fix is currently in beta...
03-07-2022 08:16 AM
Thank you for the feedback, it help other users.
06-01-2022 01:57 AM
Do you know if there is any update on this Gerald? Is the Beta available for us to try?
06-03-2022 04:26 AM
Hi,
It seems that issue is one of mentioned in release notes of latest firmware release.
I recommend you to open a support case in Cisco Small Business TAC.
They should have a solution.
Contacts you can find in link below:
https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide