Cisco 2960 -24PC- 12.2(58)SE2 --PoE bug or not

mahesh18 · ‎05-29-2012

Hi all,

On Cisco 2960 -24PC-L switch IOS version---

Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(58)SE2, RELEASE SOFTWARE (fc1)

I checked few ports got this error on logs

May 16 11:06:35.715 : %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/10: Power Controller reports power Imax error detected

May 16 11:06:46.511 : %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/10: Power Controller reports power Imax error detected

May 16 11:08:18.710 : %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/10: Power Controller reports power Imax error detected

May 29 13:36:54.691 MDT: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/8: Power Controller reports power Imax error detected

May 29 13:37:32.565 MDT: %ILPOWER-5-IEEE_DISCONNECT: Interface Fa0/2: PD removed

May 29 13:37:32.683 MDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2, changed state to down

May 29 13:37:33.689 MDT: %LINK-3-UPDOWN: Interface FastEthernet0/2, changed state to down

I check the avaliable power it was enough

sh power inline

Available:370.0(w) Used:54.0(w) Remaining:316.0(w)

Port is config as access and also in Voice vlan.

We verify that cable was good as this happens with 3 ports.

Verfied post test was good.

Did shut and no no shut on one of ports and it came back up.

FastEthernet0/10 is up, line protocol is up (connected)

Hardware is Fast Ethernet, address is 5c50.15ae.d78a (bia 5c50.15ae.d78a)

MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, media type is 10/100BaseTX

input flow-control is off, output flow-control is unsupported

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:48, output 00:00:48, output hang never

Last clearing of "show interface" counters never

--More-- Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 2000 bits/sec, 2 packets/sec

427960 packets input, 79550297 bytes, 0 no buffer

Received 37840 broadcasts (37820 multicasts)

1 runts, 0 giants, 0 throttles

1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 37820 multicast, 0 pause input

0 input packets with dribble condition detected

9627001 packets output, 2421701292 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 unknown protocol drops

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 pause output

Cisco phone is connected to this port.

Fa0/10 auto on 10.5 IP Phone 7937 3 15.4

Need to confirm if this is due to some cisco bug or not?

My understanding is that 3 ports can not go bad same time and they came back after shut and no shut.

Also they did do went to errdisable state.

Need to confirm if it is some IOS bug or not ??

Thanks

Mahesh

Leo Laohoo · ‎05-29-2012

Before you blame the IOS can you plug the 7937 DIRECTLY to the switch port?

If you are getting the same error message then change the patch cable three times.

If by the third time you are still getting an error message, test the cable using the TDR.

Most of the time I see error messages like this, it's due to faulty cable.

mahesh18 · ‎05-30-2012

Hi leolaohoo,

Phone is directly connected to switch and other cable from phone goes to PC.

Thanks

MAhesh

Leo Laohoo · ‎05-30-2012

Phone is directly connected to switch and other cable from phone goes to PC.

Ok. Let's do this then ...

1. TEMPORARILY plug the phone directly to either GigabitEthernet 1 or 2.

NOTE: I know the phone ain't going to power up but this is not my intention.

2. Enter the following command on the switch:

conf t

interface Gig0/<1 or 2>;

media rj

end

3. In enable mode, enter the following command: test cable tdr interface Gig 0/<1 or 2>;

4. Wait for approximately 5 to 7 seconds;

5. Command: sh cable tdr interface Gig 0/<1 or 2>;

6. Post the command.

7. Undo the command in #2:

conf t

interface Gig0/<1 or 2>;

media auto

end

That's it. I await to see the result of your tests.

Pranjal Bharadwaj · ‎01-16-2020

Hello Everyone,

I have a little query related to this loopback error issue causing SW port in err-disable state.

My SW version is as below which states keepalives are not sent by default on the fibre and uplink ports as per CISCO.

krse510
Switch Ports Model              SW Version            SW Image
------ ----- -----              ----------            ----------
*    1 28    WS-C3750G-24TS-1U 12.2(46)SE            C3750-IPBASE-M

PE------SW------(Carrier)----CE

Gi1/0/27 -- pointing towards PE

Gi1/0/23 -- pointing towards Carrier.

However, I got the below logs and made our Customer facing port to Err-Disable state.

Dec 16 19:15:42.885 UTC: %SW_MATM-4-MACFLAP_NOTIF: Host 7c0e.cec1.8b04 in vlan 326 is flapping between port Gi1/0/23 and port Gi1/0/27

Dec 16 19:15:45.100 UTC: %ETHCNTR-3-LOOP_BACK_DETECTED: Loop-back detected on GigabitEthernet1/0/23.

Dec 16 19:15:45.100 UTC: %PM-4-ERR_DISABLE: loopback error detected on Gi1/0/23, putting Gi1/0/23 in err-disable state

My questions are as below:

1. Could somebody please let me know is this possible getting ETHCNTR-3-LOOP_BACK_DETECTED on this port as we are on Version 12.2(46)SE ??

2. How can I overcome this situation as each time it went to err-disable mode once any logs come for mac-flap between Gi1/0/23 and port Gi1/0/27?

3. What are the possible causes that generated these logs?

krse510#sh run int Gi1/0/23
Building configuration...

Current configuration : 315 bytes
!
interface GigabitEthernet1/0/23
description ---To XXXX
switchport trunk encapsulation dot1q
switchport trunk native vlan 326
switchport trunk allowed vlan 326,3123
switchport mode trunk
switchport nonegotiate
speed 100
duplex full
mls qos trust cos
no mdix auto
spanning-tree bpdufilter enable
end