cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1166
Views
0
Helpful
3
Replies

2924 switch error message

Tejeshwar Saini
Level 1
Level 1

Hi,

We have 2924 switch which is showing below error messages in logs.Please help what could have caused this messages and how we can get rid of it.

Bristol_IDF.6.1#sh logg
Syslog logging: enabled (0 messages dropped, 22 flushes, 0 overruns)
    Console logging: level debugging, 2524 messages logged
    Monitor logging: level debugging, 0 messages logged
    Buffer logging: level debugging, 1259 messages logged
    File logging: disabled
    Trap logging: level warnings, 956 message lines logged
        Logging to 10.138.215.96, 956 message lines logged
Log Buffer (4096 bytes):
:00:25: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 25 17:25:14: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 25 18:06:02: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 25 23:57:55: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 05:54:39: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 06:00:09: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 26 06:00:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 26 06:00:11: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 26 06:00:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 26 06:00:14: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 26 06:00:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 26 06:00:15: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 26 06:00:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 26 07:42:46: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 26 08:52:06: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 09:31:48: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 09:37:43: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 09:39:42: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 10:46:45: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 11:44:06: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 11:57:05: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 13:45:26: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 26 13:48:06: %RTD-1-ADDR_FLAP: FastEthernet0/24 relearning 5 addrs per min
Nov 26 15:56:16: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 16:00:26: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 16:02:26: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 27 06:00:39: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 27 06:00:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 27 06:00:41: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 27 06:00:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 27 06:00:44: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 27 06:00:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 27 06:00:45: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 27 06:00:46: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 27 06:04:59: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 13:43:26: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 13:44:52: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 13:51:14: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 16:10:50: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 16:18:24: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 05:51:49: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 05:54:30: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 08:13:48: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 28 09:31:18: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 28 09:35:49: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 09:36:55: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 10:10:45: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 10:57:08: %RTD-1-ADDR_FLAP: FastEthernet0/24 relearning 5 addrs per min
Nov 28 11:12:44: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 11:15:38: %RTD-1-ADDR_FLAP: FastEthernet0/24 relearning 5 addrs per min
Nov 28 11:18:38: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Bristol_IDF.6.1#


Bristol_IDF.6.1#sh logg
Syslog logging: enabled (0 messages dropped, 22 flushes, 0 overruns)
    Console logging: level debugging, 2524 messages logged
    Monitor logging: level debugging, 0 messages logged
    Buffer logging: level debugging, 1259 messages logged
    File logging: disabled
    Trap logging: level warnings, 956 message lines logged
        Logging to 10.138.215.96, 956 message lines logged
Log Buffer (4096 bytes):
:00:25: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 25 17:25:14: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 25 18:06:02: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 25 23:57:55: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 05:54:39: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 06:00:09: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 26 06:00:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 26 06:00:11: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 26 06:00:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 26 06:00:14: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 26 06:00:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 26 06:00:15: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 26 06:00:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 26 07:42:46: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 26 08:52:06: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 09:31:48: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 09:37:43: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 09:39:42: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 10:46:45: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 11:44:06: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 11:57:05: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 26 13:45:26: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 26 13:48:06: %RTD-1-ADDR_FLAP: FastEthernet0/24 relearning 5 addrs per min
Nov 26 15:56:16: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 16:00:26: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 26 16:02:26: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Nov 27 06:00:39: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 27 06:00:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 27 06:00:41: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 27 06:00:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 27 06:00:44: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to do
wn
Nov 27 06:00:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to down
Nov 27 06:00:45: %LINK-3-UPDOWN: Interface FastEthernet0/20, changed state to up
Nov 27 06:00:46: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2
0, changed state to up
Nov 27 06:04:59: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 13:43:26: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 13:44:52: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 13:51:14: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 16:10:50: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 27 16:18:24: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 05:51:49: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 05:54:30: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 08:13:48: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 28 09:31:18: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min
Nov 28 09:35:49: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 09:36:55: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 10:10:45: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 10:57:08: %RTD-1-ADDR_FLAP: FastEthernet0/24 relearning 5 addrs per min
Nov 28 11:12:44: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors
Nov 28 11:15:38: %RTD-1-ADDR_FLAP: FastEthernet0/24 relearning 5 addrs per min
Nov 28 11:18:38: %RTD-1-ADDR_FLAP: FastEthernet0/17 relearning 5 addrs per min
Bristol_IDF.6.1#

Bristol_IDF.6.1# sh vers
Cisco Internetwork Operating System Software
IOS (tm) C2900XL Software (C2900XL-C3H2S-M), Version 12.0(5)WC17, RELEASE SOFTW
RE (fc1)
Copyright (c) 1986-2007 by cisco Systems, Inc.
Compiled Tue 13-Feb-07 15:27 by antonino
Image text-base: 0x00003000, data-base: 0x00352924
ROM: Bootstrap program is C2900XL boot loader
Bristol_IDF.6.1 uptime is 1 week, 4 days, 21 hours, 41 minutes
System returned to ROM by power-on
System restarted at 15:06:15 est Wed Nov 16 2011
System image file is "flash:c2900xl-c3h2s-mz.120-5.WC17.bin"

cisco WS-C2924C-XL (PowerPC403GA) processor (revision 0x11) with 8192K/1024K by
es of memory.
Processor board ID FAB0410V0BC, with hardware revision 0x01
Last reset from power-on
Processor is running Enterprise Edition Software
Cluster command switch capable
Cluster member switch capable
24 FastEthernet/IEEE 802.3 interface(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:01:42:E7:CD:C0
Motherboard assembly number: 73-3381-08
Power supply part number: 34-0834-01
Motherboard serial number: FAB041040TN
Power supply serial number: PHI035204NM
Model revision number: A0
Motherboard revision number: A0
Model number: WS-C2924C-XL-EN
System serial number: FAB0410V0BC
Configuration register is 0xF

Rgds,

Tejeshwar Saini

3 Replies 3

Latchum Naidu
VIP Alumni
VIP Alumni

Hi Tejeshwar,


There are several factors you need to look in and check...

I had this same kind of issue before and it was the problem with the switch port configuration.

As per configuration , each switch port is 100mbs speed/full duplex and on the other end the NIC of computers are in auto configuration.


1. I might like to know what's connected to the other end, because the interfaces could be receiving malformed frames or something..

2. Try swapping cables between one of the problem ports into a port that you know has no errors. If the problem follows the cable, you may have a problem either on the patch cable, your internal cabling or teh NIC on the host. If the problem doesn't follow, you could have faulty ports on your switch(es).

3. For such a widespread problem, if the problem isn't with the physical ports, look for common factors between the end points of the problem ports. Like a certain area of the building, or the "run" of internal cables from the comms room to the end points (where your PC NIC plugs into the wall/floor).

Please rate the helpfull posts.
Regards,
Naidu.

Nov 25 17:25:14: %LINK-4-ERROR: FastEthernet0/22 is experiencing errors

This means that line errors are incrementing.  Verify by using the command "sh contr e f0/22".  Collisions (left-hand side) should be 0.  Symbols, FCS and CRC (right-hand side) should be 0.

Nov 25 23:57:55: %RTD-1-ADDR_FLAP: FastEthernet0/18 relearning 5 addrs per min

Sound like cable is faulty or the NIC of the client is faulty.

Your switch is 11 years old.

I notice your hostname has a "." in it.  Are you using Switch Clustering?

glen.grant
VIP Alumni
VIP Alumni

  This looks like you have a spanning tree loop somewhere.   Do  a show cdp neighbor and see if the switch sees "itlself on any of the ports . If so then shutdown that port and find the physical loop in the network.

Review Cisco Networking for a $25 gift card