11-06-2023 12:50 AM
BSTC-DAT-31-LAN6_SEC#sh int gi1/0/22
GigabitEthernet1/0/22 is down, line protocol is down (err-disabled)
Hardware is Gigabit Ethernet, address is a84f.b13e.8d96 (bia a84f.b13e.8d96)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 10/100/1000BaseTX
input flow-control is on, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 12:03:54, output 12:03:54, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/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 0 bits/sec, 0 packets/sec
126824036 packets input, 149324241416 bytes, 0 no buffer
Received 4762240 broadcasts (1405795 multicasts)
0 runts, 0 giants, 0 throttles
1 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1405795 multicast, 0 pause input
0 input packets with dribble condition detected
35280501 packets output, 2306718583 bytes, 0 underruns
Output 204272 broadcasts (0 multicasts)
0 output errors, 0 collisions, 4 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
11-06-2023 02:03 AM
Hello @csasrinivasan,
could you please more elaborate ? Many reasons.... do you have another logs (sh logging) ?
This feature was first implemented in order to handle special collision situations in which the switch detected excessive or late collisions on a port. Excessive collisions occur when a frame is dropped because the switch encounters 16 collisions in a row. Late collisions occur because every device on the wire did not recognize that the wire was in use. Possible causes of these types of errors include:
A cable that is out of specification (either too long, the wrong type, or defective)
A bad network interface card (NIC) card (with physical problems or driver problems)
A port duplex misconfiguration
A port duplex misconfiguration is a common cause of the errors because of failures to negotiate the speed and duplex properly between two directly connected devices (for example, a NIC that connects to a switch). Only half-duplex connections can ever have collisions in a LAN. Because of the carrier sense multiple access (CSMA) nature of Ethernet, collisions are normal for half duplex, as long as the collisions do not exceed a small percentage of traffic.
There are various reasons for the interface to go into errdisable. The reason can be:
Duplex mismatch
Port channel misconfiguration
BPDU guard violation
UniDirectional Link Detection (UDLD) condition
Late-collision detection
Link-flap detection
Security violation
Port Aggregation Protocol (PAgP) flap
Layer 2 Tunneling Protocol (L2TP) guard
DHCP snooping rate-limit
Incorrect GBIC / Small Form-Factor Pluggable (SFP) module or cable
Address Resolution Protocol (ARP) inspection
Inline power
11-06-2023 07:37 PM
yesterday I did a shutdown and no shutdown for that port, so I was unable to check the reason
today I have taken the error reason kindly advise further
BSTC-DAT-31-LAN6_SEC#sh int gi1/0/47 status err-disabled
Port Name Status Reason Err-disabled Vlans
Gi1/0/47 err-disabled loopback
11-06-2023 02:08 AM
Post the complete output to the command "sh interface Gi1/0/22 status err".
11-06-2023 07:38 PM
yesterday I did a shutdown and no shutdown for that port, so I was unable to check the reason
today I have taken the error reason kindly advise further
BSTC-DAT-31-LAN6_SEC#sh int gi1/0/47 status err-disabled
Port Name Status Reason Err-disabled Vlans
Gi1/0/47 err-disabled loopback
11-06-2023 08:10 PM
Loopback error could, potentially, be a cable issue.
Is this a PoE switch?
Please post the complete output to the command "sh version". I want to know what firmware the switch is on and the uptime before recommending a TDR on the port.
If the switch is a classic IOS, then fine. But if the switch is on IOS-XE, I want to make sure it will not hit CSCwd97177 or CSCvw97924.
11-06-2023 08:19 PM
BSTC-DAT-31-LAN6_SEC#sh version
Cisco IOS XE Software, Version 17.03.04b
Cisco IOS Software [Amsterdam], Catalyst L3 Switch Software (CAT9K_LITE_IOSXE), Version 17.3.4b, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2021 by Cisco Systems, Inc.
Compiled Tue 19-Oct-21 03:16 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2021 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: IOS-XE ROMMON
BOOTLDR: System Bootstrap, Version 17.9.1r [FC4], RELEASE SOFTWARE (P)
BSTC-DAT-31-LAN6_SEC uptime is 1 week, 1 day, 14 hours, 59 minutes
Uptime for this control processor is 1 week, 1 day, 15 hours, 2 minutes
System returned to ROM by Power Failure or Unknown at 17:22:23 GST Thu Feb 16 2023
System restarted at 17:02:18 GST Sun Oct 29 2023
System image file is "flash:packages.conf"
Last reload reason: Power Failure or Unknown
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Technology Package License Information:
------------------------------------------------------------------------------
Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------------------
network-essentials Smart License network-essentials
dna-essentials Subscription Smart License dna-essentials
Smart Licensing Status: Registration Not Applicable/Not Applicable
cisco C9200L-48P-4G (ARM64) processor with 523451K/3071K bytes of memory.
Processor board ID JAE26170AZ6
3 Virtual Ethernet interfaces
52 Gigabit Ethernet interfaces
2048K bytes of non-volatile configuration memory.
1984308K bytes of physical memory.
819200K bytes of Crash Files at crashinfo:.
1941504K bytes of Flash at flash:.
Base Ethernet MAC Address : a8:4f:b1:3e:8d:80
Motherboard Assembly Number : 73-102108-04
Motherboard Serial Number : JAE26170AZ6
Model Revision Number : C0
Motherboard Revision Number : A0
Model Number : C9200L-48P-4G
System Serial Number : JAE26170AZ6
CLEI Code Number : INM6B00ARB
Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 52 C9200L-48P-4G 17.03.04b CAT9K_LITE_IOSXE INSTALL
Configuration register is 0x102
BSTC-DAT-31-LAN6_SEC#
11-06-2023 08:41 PM
Ok, 1 week uptime. It might work.
conf t
interface Gi 1/0/22
power inline never
end
test cable tdr interface Gi 1/0/22
Wait for about 15 seconds and then post the complete output to the command below:
sh cable tdr interface Gi 1/0/22
After everything is sorted, enable PoE on the port:
conf t
interface Gi 1/0/22
no power inline never
end
11-06-2023 08:47 PM
Loopback there is l2 loop in your network.
It STP issue
11-06-2023 02:16 AM - edited 11-06-2023 02:19 AM
as mentioned above, we need more info; Also I noticed "1 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored"
CRC - cyclic redundancy checks - CRC are typically caused by noise on the line or duplex mismatch. Bandwidth constraints can also cause CRC errors sometimes. Try hardcoding the duplex and in the event that doesn't help physical layer troubleshooting is needed.
from https://community.cisco.com/t5/other-network-architecture-subjects/crc-errors/td-p/538665
Regards, ML
11-06-2023 02:30 AM - edited 11-06-2023 02:42 AM
Show interface status dont give us the reason why port go to errdisable.
You need to check log to see correct reason.
There is other way I dont recommend but I will mention it' use err recovery and then check which protocol make port go to errdisable (show errdisable recovery) and then disable recovery.
Thanks A Lot
MHM
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