Check the device that is connected to the port for speed setting and duplex. If possible fix it to one particular setting at both ends. Start low and then build up to 100 full. The errors are usually caused by a mismatch or cabling that cannot handle it.
Steve Wilson Network Engineer -----Original Message----- From: Ken Diliberto [mailto:[EMAIL PROTECTED] Sent: 25 February 2003 15:52 To: [EMAIL PROTECTED] Subject: Re: Strange problem with a 2924XL. [7:63680] Here's more information I should have included in the first message: #sh int f0/13 FastEthernet0/13 is up, line protocol is up Hardware is Fast Ethernet, address is 00d0.bbd2.260d (bia 00d0.bbd2.260d) 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 Auto-duplex (Full), Auto Speed (100), 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 12:58:47 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 6000 bits/sec, 5 packets/sec 218510 packets input, 78936683 bytes Received 1073 broadcasts, 0 runts, 0 giants, 0 throttles 147 input errors, 147 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 538 multicast 0 input packets with dribble condition detected 467270 packets output, 258862433 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out I did a clear count f0/13 last night. Input and CRC errors were rising at a moderate rate. interface FastEthernet0/13 no logging event link-status port storm-control broadcast trap switchport access vlan 8 no snmp trap link-status spanning-tree portfast ! Feb 24 16:02:31.046: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:06:08.951: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:07:29.785: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:12:01.748: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:20:46.733: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:21:51.812: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:25:11.507: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:27:54.890: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:28:55.370: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:30:30.011: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:40:03.346: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:41:24.389: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:42:57.809: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 16:48:08.352: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 17:47:18.451: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 17:48:45.262: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 17:59:49.059: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 18:35:33.480: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 18:37:06.128: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors Feb 24 18:38:06.935: %LINK-4-ERROR: FastEthernet0/13 is experiencing errors >>> "The Long and Winding Road" 02/24/03 11:20PM >>> ""Ken Diliberto"" wrote in message news:[EMAIL PROTECTED] > I had a strange problem this evening with a 2924XL. The server attached > to port f0/13 had been generating errors and finally the switch stopped > talking to it. A shut/no shut combination started everything back up > again. > > The configuration only says to send a trap when a broadcast storm > happens. There isn't anything about excessive errors. > > Any thoughts? I haven't checked CCO. I don't have a good idea what to > search for without getting 10,000,000,000 hits. what is the exact configuration line used? the documentation talks about default rising and falling thresholds. of course it does not indicate whether or not the default is to shutdown or not. http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/29_35wc3/cref/cl icmds.htm#xtocid51 > > Thanks. > > Ken Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=63743&t=63680 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]