Cisco 3560 PoE Error

[paulhughes5]

Hello

I have a Cisco 3560v2 running 12.2-50.SE5 that has a Cisco Aironet 1130 wireless access point attached.  Late on Saturday evening the port has gone down and I now get the following message in the logs:

Apr 23 11:45:10.733: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/33: Power Controller reports power Tstart error detected

I have looked through some of the bug toolkits and most things refer to it functioning correctly when the right device is connected.  Until Saturday this was working and I have a second access point connected to a different port working normally still.

Does anyone have any ideas as to what this problem could be?

Thanks

Paul

[Leo Laohoo]

Can you please post this command:  sh post

[paulhughes5]

Hi

Here is the result of show post:

POST: CPU MIC register Tests : Begin
POST: CPU MIC register Tests : End, Status Passed

POST: PortASIC Memory Tests : Begin
POST: PortASIC Memory Tests : End, Status Passed

POST: CPU MIC interface Loopback Tests : Begin
POST: CPU MIC interface Loopback Tests : End, Status Passed

POST: PortASIC RingLoopback Tests : Begin
POST: PortASIC RingLoopback Tests : End, Status Passed

POST: Inline Power Controller Tests : Begin
POST: Inline Power Controller Tests : End, Status Passed

POST: PortASIC CAM Subsystem Tests : Begin
POST: PortASIC CAM Subsystem Tests : End, Status Passed

POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed

The switch has been up for 15 weeks and was working fine until the weekend so I'm not sure if the post would show the problem.  Ideally Id like to avoid reloading the switch as it has part of our call centre on it.

Thanks

[Leo Laohoo]

If you do a "sh power inline fa0/33" do you see the port giving out power?

I mean you have a 3560 non-gigabit model which means that I can't do a TDR.

[paulhughes5]

sh power inline f0/33

Interface Admin  Oper       Power   Device              Class Max

                            (Watts)                           

--------- ------ ---------- ------- ------------------- ----- ----

Fa0/33    auto   off        0.0     n/a                 n/a   15.4

Interface  AdminPowerMax   AdminConsumption   

             (Watts)           (Watts)          

---------- --------------- -------------------- 

Fa0/33                15.4                 15.4

The switch is a 3560V2 10/100 48 port (WS-C3560V2-48PS)

[Leo Laohoo]

This looks like the remote end is either not getting any power or the power-end-device has been removed from the network.

Do you have any 3560 or 3750 with a copper Gig port so you can do TDR?

[paulhughes5]

I have a 3750 with copper ports but its not PoE so I dont know if the port will come up on that either.

Do you know what a TStart error is?  When I checked back in syslog there was this error:

%ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/33: Power Controller reports power Imax error detected

Now all I have is the one in the original post:

%ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/33: Power Controller reports power Tstart error detected

The fact that the switch is logging something leads me to believe it knows the end device wants power but I cant find any information about TStart errors.  I doubt its the cabling thats at fault as its all static through the roof void.

[Leo Laohoo]

%ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/33: Power Controller reports power Imax error detected

The command "sh power inline" should tell you whether or not you have enough PoE power.

%ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/33: Power Controller reports power Tstart error detected

Not sure.  Could be a hardware failure or could be that you could have a faulty patch cable somewhere, hence, I'm asking of you have a GigabitEthernet 3560 or a 3750 to perform a TDR.  Doesn't matter if it's not PoE.

[paulhughes5]

pih-intasw05#sh power inline

Available:370.0(w)  Used:22.4(w)  Remaining:347.6(w)

Fa0/33    auto   faulty     0.0     n/a                 n/a   15.4

I have enough power on the switch.  I'll go and try a gig port but may take a day or 2 before I have time to visit site.

Thanks

[Leo Laohoo]

Ok, you have more then enough PoE power.

To do the TDR, here are the command combination:

1.  Command:  test cable tdr interface Gig ;

2.  Wait for about 5 to 7 seconds;

3.  Command:  sh cable tdr interface Gig ; and

4.  Post the output.

[paulhughes5]

Sorry for the delay, here is the results

Interface Speed Local pair Pair length        Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi2/0/6   auto  Pair A     26   +/- 10 meters N/A         Open                
                Pair B     31   +/- 10 meters N/A         Short/Crosstalk     
                Pair C     25   +/- 10 meters N/A         Short/Crosstalk     
                Pair D     25   +/- 10 meters N/A         Short/Crosstalk     

[Leo Laohoo]

No wonder.  You have cable problem.  The cable issue is approximately 25 to 31 metres away from the switch port.

If you want more information about TDR, have a read here.

[paulhughes5]

Bit odd how its happened over a weekend while no one was about.  I'll have to get the ladders out I suppose and try it on a local patch lead.

[Leo Laohoo]

I'll have to get the ladders out I suppose and try it on a local patch lead.

If you need a ladder, can I ask if you test the new patch cord FIRST?

[Chidojohnkingsley92]

Follow the link below to see how to solve this issue

https://youtu.be/X7n_gt4z3BA?si=xxub5m12--NHt1ye