Getting Switch Errors Need Help
Can anyone tell me what these errors mean?
Its on my 2924 switch?
03:36:28: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:40:13: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:42:21: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:44:08: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:45:38: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:47:39: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:48:46: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:50:43: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
Its on my 2924 switch?
03:36:28: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:40:13: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:42:21: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:44:08: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:45:38: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:47:39: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:48:46: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
03:50:43: %LINK-4-ERROR: FastEthernet0/9 is experiencing errors
CompTIA A+ Nov 25, 1997
CompTIA Network+ March 7, 2008
MCTS Vista 620 June 14, 2008
MCP Server 290 Nov 15, 2008
MCP Server 291 In Progress (Exam 12/28/09)
Cisco CCENT In Progress
MCP Server 291 In Progress
C|EH In Progress
CompTIA Network+ March 7, 2008
MCTS Vista 620 June 14, 2008
MCP Server 290 Nov 15, 2008
MCP Server 291 In Progress (Exam 12/28/09)
Cisco CCENT In Progress
MCP Server 291 In Progress
C|EH In Progress
Comments
It means FastEthernet0/9 is experiencing errors...
CompTIA Network+ March 7, 2008
MCTS Vista 620 June 14, 2008
MCP Server 290 Nov 15, 2008
MCP Server 291 In Progress (Exam 12/28/09)
Cisco CCENT In Progress
MCP Server 291 In Progress
C|EH In Progress
does the crc have anything to do with this.
FastEthernet0/9 is up, line protocol is up
Hardware is Fast Ethernet, address is 0006.53ac.3649 (bia 0006.53ac.3649)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
232942 packets input, 73391384 bytes
Received 3511 broadcasts, 0 runts, 0 giants, 0 throttles
1584 input errors, 802 CRC, 782 frame, 0 overrun, 0 ignored
0 watchdog, 2117 multicast
0 input packets with dribble condition detected
367467 packets output, 419670640 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
CompTIA Network+ March 7, 2008
MCTS Vista 620 June 14, 2008
MCP Server 290 Nov 15, 2008
MCP Server 291 In Progress (Exam 12/28/09)
Cisco CCENT In Progress
MCP Server 291 In Progress
C|EH In Progress
Try plugging that host device into another port on the switch. If the errors do not follow the device, then plug another device into fa0/9. If you again start receiving errors on fa0/9 then that port is likely bad. Trial and error. Change only one thing at a time until you can determine where the problem actually is. From there you can decide WHAT the problem is...
i concur .....
and this line seems interesting ???
1584 input errors, 802 CRC, 782 frame, 0 overrun, 0 ignored
crc's and framing errors
sounds like a physical line problem to me .....
CompTIA Network+ March 7, 2008
MCTS Vista 620 June 14, 2008
MCP Server 290 Nov 15, 2008
MCP Server 291 In Progress (Exam 12/28/09)
Cisco CCENT In Progress
MCP Server 291 In Progress
C|EH In Progress
Dont forget to try a different cable. As dark said, may only be a physical layer problem...
have you verified the device on the other side of the link? speed/duplex if so change switch port, then change cable to switch and to end station. Past that update code to last version available for the switch. once the reboot ( look at the post messages while its coming up) on the new code finishes check the port again if still the same shut it down and label it as bad
I would check for speed/duplex mismatch then quickly move onto replacing the cable as I suspect thats what it is.
did you get it figure out? my 2924 does the same thing or did
i did mess with the speeds and whether it was full duplex or half and
are you trunking it with a 2924?????
I think there are issues with 2950 and 2924 trunking
I think i just gave up (i knwo i am a wimp)_ when with my 2950s and no issues
trunkiing....
but ihad same error with teh 2924 trunking with my 2950 so i bought another 2950
and practice truking and etherchannels and vtp domain and stp stuff
Trunk mismatch can cause CRC and input errors? interesting........can you explain this?
00:04:46: %LINK-4-ERROR: FastEthernet0/24 is experiencing errors
SW3#
00:05:46: %LINK-4-ERROR: FastEthernet0/24 is experiencing errors
W3#show int fa0/24 switchport
Name: Fa0/24
Switchport: Enabled
Administrative mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: isl
Operational Trunking Encapsulation: isl
Negotiation of Trunking: Disabled
Access Mode VLAN: 0 ((Inactive))
Trunking Native Mode VLAN: 1 (default)
Trunking VLANs Enabled: ALL
Trunking VLANs Active: 1,10,20,30,44
Pruning VLANs Enabled: 2-1001
FastEthernet0/24 is up, line protocol is up
Hardware is Fast Ethernet, address is 0002.7d37.cbd8 (bia 0002.7d37.cbd
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 156/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:05:15, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 2000 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 5 packets/sec
153 packets input, 102851 bytes
Received 152 broadcasts, 0 runts, 0 giants, 0 throttles
1244 input errors, 1244 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 152 multicast
0 input packets with dribble condition detected
1688 packets output, 57377 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
PEER
SW2#show int fa0/24 switchport
Name: Fa0/24
Switchport: Enabled
Administrative mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Disabled
Access Mode VLAN: 0 ((Inactive))
Trunking Native Mode VLAN: 1 (default)
Trunking VLANs Enabled: ALL
Trunking VLANs Active: 1,2,4,10,20,30,44
Pruning VLANs Enabled: 2-1001
Could have something to do with trunking negotiation with dot1Q which isn't tagged natively versus ISL that encapsulates 30 bytes on all frames.