Switch Error (ILP_POWER_POLICE_DISABLE_EV )

da.newman · ‎07-15-2012

We have a Cisco WS-C3560X-48P running 12.2(55) with multiple 7945 IP Phones connected to it. Several of these phones are randomly rebooting once or a couple of times a day at the moment. There's sufficent POE capacity on the switch and all the diagnoistics I have run haven't shown any issues. he logs do show a bunch "ILP_POWER_POLICE_DISABLE_EV" shortly after the issue started occuring. I haven't been able to find much information on this error/message?

Is anyone familar with this log message?

000491: Jul 14 10:18:57.758 AEST: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi0/11, port's configured trust state is now operational.

000492: Jul 14 10:19:01.776 AEST: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Gi0/11, port's configured trust state is now operational.

000493: Jul 14 15:40:45.775 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000494: Jul 14 15:40:46.966 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

000495: Jul 14 15:41:03.265 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000496: Jul 14 15:41:04.297 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

000497: Jul 14 17:00:22.630 AEST: %SYS-5-CONFIG_I: Configured from console by erose on vty0 (10.10.11.72)

000498: Jul 14 17:13:54.314 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000499: Jul 14 17:13:55.338 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

000500: Jul 14 17:14:30.158 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000501: Jul 14 17:14:31.206 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

000502: Jul 14 17:14:32.330 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000503: Jul 14 17:14:33.261 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

000504: Jul 14 17:14:34.310 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000505: Jul 14 17:14:35.333 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

000506: Jul 14 17:14:37.372 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000507: Jul 14 17:14:38.395 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

000508: Jul 14 17:15:34.370 AEST: ILP uses DC Disconnect(Gi0/28): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000509: Jul 14 17:15:34.370 AEST: ILP uses DC Disconnect(Gi0/28): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000510: Jul 14 17:15:38.623 AEST: ILP uses DC Disconnect(Gi0/12): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000511: Jul 14 17:15:38.623 AEST: ILP uses DC Disconnect(Gi0/12): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000512: Jul 14 17:15:41.131 AEST: ILP uses DC Disconnect(Gi0/37): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000513: Jul 14 17:15:41.140 AEST: ILP uses DC Disconnect(Gi0/37): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000514: Jul 14 17:15:41.450 AEST: ILP uses DC Disconnect(Gi0/47): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000515: Jul 14 17:15:41.450 AEST: ILP uses DC Disconnect(Gi0/47): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000516: Jul 14 17:15:42.020 AEST: ILP uses DC Disconnect(Gi0/43): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000517: Jul 14 17:15:42.020 AEST: ILP uses DC Disconnect(Gi0/43): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000518: Jul 14 17:15:49.738 AEST: ILP uses DC Disconnect(Gi0/34): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000519: Jul 14 17:15:49.738 AEST: ILP uses DC Disconnect(Gi0/34): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000520: Jul 14 17:15:54.687 AEST: ILP uses DC Disconnect(Gi0/27): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000521: Jul 14 17:15:54.687 AEST: ILP uses DC Disconnect(Gi0/27): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000522: Jul 14 17:15:56.121 AEST: ILP uses DC Disconnect(Gi0/45): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000523: Jul 14 17:15:56.121 AEST: ILP uses DC Disconnect(Gi0/45): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000524: Jul 14 17:16:01.481 AEST: ILP uses DC Disconnect(Gi0/26): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000525: Jul 14 17:16:01.481 AEST: ILP uses DC Disconnect(Gi0/26): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000526: Jul 14 17:16:01.590 AEST: ILP uses DC Disconnect(Gi0/17): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000527: Jul 14 17:16:01.590 AEST: ILP uses DC Disconnect(Gi0/17): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000528: Jul 14 17:16:03.058 AEST: ILP uses DC Disconnect(Gi0/11): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000529: Jul 14 17:16:03.058 AEST: ILP uses DC Disconnect(Gi0/11): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000530: Jul 14 17:16:09.492 AEST: ILP uses DC Disconnect(Gi0/16): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000531: Jul 14 17:16:09.492 AEST: ILP uses DC Disconnect(Gi0/16): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000532: Jul 14 17:16:09.878 AEST: ILP uses DC Disconnect(Gi0/25): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000533: Jul 14 17:16:09.878 AEST: ILP uses DC Disconnect(Gi0/25): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000534: Jul 14 17:16:12.118 AEST: ILP uses DC Disconnect(Gi0/8): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000535: Jul 14 17:16:12.118 AEST: ILP uses DC Disconnect(Gi0/8): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000536: Jul 14 17:16:14.047 AEST: ILP uses DC Disconnect(Gi0/33): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000537: Jul 14 17:16:14.047 AEST: ILP uses DC Disconnect(Gi0/33): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000538: Jul 14 17:16:15.750 AEST: ILP uses DC Disconnect(Gi0/23): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000539: Jul 14 17:16:15.750 AEST: ILP uses DC Disconnect(Gi0/23): state= ILP_LINK_UP_S, event= ILP_POWER_POLICE_DISABLE_EV

000540: Jul 14 17:16:15.976 AEST: ILP uses DC Disconnect(Gi0/35): state= ILP_DETECTING_S, event= IEEE_CLASS_DONE_EV

000541: Jul 14 17:16:15.976 AEST: %ILPOWER-7-DETECT: Interface Gi0/35: Power Device detected: IEEE PD

000542: Jul 14 17:16:16.823 AEST: ILP uses DC Disconnect(Gi0/35): state= ILP_PD_DETECTED_S, event= IEEE_PD_REMOVAL_EV

000543: Jul 14 17:16:16.823 AEST: %ILPOWER-5-IEEE_DISCONNECT: Interface Gi0/35: PD removed

Sandeep Choudhary · ‎07-16-2012

Hi,

May be the device does not support the 3560 PoE. I have seen this with alot of VoIP phones. Does this line happen all the time or just a few times?

Regards

Leo Laohoo · ‎07-16-2012

Try the following commands:

1. Command: test cable tdr int G0/35;

2. Wait for approximately 7 seconds;

3. Command: sh cable tdr int G0/35; and

4. Post the output

I await to see the result.

da.newman · ‎07-16-2012

Leolaohoo: I ran the cable TDR test prior to posting this thread but couldn;t get any results to display on the switch. I've rebooted the switch last night and rerun the test this morning on multiple ports on the switch however it doesn;t seem to matter what port I run the test on I cannot get any results to display. Makes me think the switch might be faulty.

SW1#sh clock

08:42:54.639 AEST Tue Jul 17 2012

SW1#test cabl tdr int gi0/28

TDR test started on interface Gi0/28

A TDR test can take a few seconds to run on an interface

Use 'show cable-diagnostics tdr' to read the TDR results.

SW1#test cabl tdr int gi0/26

TDR test started on interface Gi0/26

A TDR test can take a few seconds to run on an interface

Use 'show cable-diagnostics tdr' to read the TDR results.

SW1#test cabl tdr int gi0/22

TDR test started on interface Gi0/22

A TDR test can take a few seconds to run on an interface

Use 'show cable-diagnostics tdr' to read the TDR results.

SW1#test cabl tdr int gi0/16

TDR test started on interface Gi0/16

A TDR test can take a few seconds to run on an interface

Use 'show cable-diagnostics tdr' to read the TDR results.

SW1#sh clock

08:43:42.394 AEST Tue Jul 17 2012

SW1#sh clock

08:44:54.618 AEST Tue Jul 17 2012

SW1#sh cable tdr int gi0/28

TDR test last run on: July 17 08:43:22

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/28 1000M Pair A N/A N/A Not Completed

Pair B N/A N/A Not Completed

Pair C N/A N/A Not Completed

Pair D N/A N/A Not Completed

SW1#sh cable tdr int gi0/26

TDR test last run on: July 17 08:43:27

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/26 1000M Pair A N/A N/A Not Completed

Pair B N/A N/A Not Completed

Pair C N/A N/A Not Completed

Pair D N/A N/A Not Completed

SW1#sh cable tdr int gi0/22

TDR test last run on: July 17 08:43:31

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/22 1000M Pair A N/A N/A Not Completed

Pair B N/A N/A Not Completed

Pair C N/A N/A Not Completed

Pair D N/A N/A Not Completed

SW1#sh cable tdr int gi0/16

TDR test last run on: July 17 08:43:39

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/16 1000M Pair A N/A N/A Not Completed

Pair B N/A N/A Not Completed

Pair C N/A N/A Not Completed

Pair D N/A N/A Not Completed

SW1#sh clock

08:49:41.516 AEST Tue Jul 17 2012

SW1#sh cable tdr int gi0/26

TDR test last run on: July 17 08:43:27

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/26 1000M Pair A N/A N/A Not Completed

Pair B N/A N/A Not Completed

Pair C N/A N/A Not Completed

Pair D N/A N/A Not Completed

SW1#sh cable tdr int gi0/28

TDR test last run on: July 17 08:43:22

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/28 1000M Pair A N/A N/A Not Completed

Pair B N/A N/A Not Completed

Pair C N/A N/A Not Completed

Pair D N/A N/A Not Completed

SW1#

If I run the tdr cable test on switch 2 at the site it runs fine and displays results.

SW2#sh cable-diagnostics tdr int gi0/20

TDR test last run on: July 17 08:38:59

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/20 1000M Pair A 40 +/- 4 meters Pair A Normal

Pair B 40 +/- 4 meters Pair B Normal

Pair C 42 +/- 4 meters Pair C Normal

Pair D 41 +/- 4 meters Pair D Normal

SW2#

Leo Laohoo · ‎07-16-2012

Oh freak. A 3560.

Ok, there's a chance you need to wait for approximately 60 seconds to run the "sh cable tdr inter " command.

Another thing I've notice with your post on the thread ... "power police"???

What's the interface-level config?

da.newman · ‎07-16-2012

Leolaohoo: I tried waiting over 30 mins after the test again and still no results on the switch:

SW1#sh clock

09:22:09.507 AEST Tue Jul 17 2012

SW1#sh cable-diagnostics tdr int gi0/28

TDR test last run on: July 17 08:43:22

Interface Speed Local pair Pair length Remote pair Pair status

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

Gi0/28 1000M Pair A N/A N/A Not Completed

Pair B N/A N/A Not Completed

Pair C N/A N/A Not Completed

Pair D N/A N/A Not Completed

SW1#

Interface level config is the same for all client access switch-ports:

SW1#sh run int gi0/28

Building configuration...

Current configuration : 515 bytes

!

interface GigabitEthernet0/28

description DATA and PHONE

switchport access vlan 10

switchport mode access

switchport nonegotiate

switchport voice vlan 20

no logging event link-status

srr-queue bandwidth share 1 30 35 5

queue-set 2

priority-queue out

no snmp trap link-status

mls qos trust device cisco-phone

mls qos trust cos

auto qos voip cisco-phone

storm-control broadcast level 50.00

spanning-tree portfast

spanning-tree guard root

service-policy input AUTOQOS-SRND4-CISCOPHONE-POLICY

end

I have no idea what the "power police" is in the logs. There are no specific power commands configured on the switch and the only police commands are for a Qos map.

SW1#sh run | inc power

SW1#sh run | inc police

mls qos map policed-dscp 0 10 18 to 8

police 128000 8000 exceed-action policed-dscp-transmit

police 32000 8000 exceed-action policed-dscp-transmit

police 10000000 8000 exceed-action policed-dscp-transmit

SW1#

Leo Laohoo · ‎07-16-2012

Ok, you got me stump.

I'm suspecting it's cable but sometimes TDR on a 3560 can be a challenge.

Do you have a 3750G somewhere? Doesn't have to be PoE just a GigabitEthernet port will do just fine.