[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Error
- To: rmikisa at one2net.co.ug
- Subject: Re: Error
- From: Brian Candler <B.Candler at pobox.com>
- Date: Thu, 19 Jun 2003 13:51:17 +0100
- Cc: "afnog at afnog.org" <afnog at afnog.org>
- Content-Disposition: inline
- Content-Type: text/plain; charset=us-ascii
- Delivered-To: afnog-archive at lists.eahd.or.ug
- Delivered-To: afnog-outgoing at afnog.org
- Delivered-To: afnog at afnog.org
- In-Reply-To: <200306190948.54588.Richard Mikisa <rmikisa>; from rmikisa at mail.one2netmail.co.ug on Thu, Jun 19, 2003 at 09:48:54AM +0300
- References: <200306190948.54588.Richard Mikisa <rmikisa>
- Sender: owner-afnog at afnog.org
- User-Agent: Mutt/1.2.5i
On Thu, Jun 19, 2003 at 09:48:54AM +0300, Richard Mikisa wrote:
> Hi all,
> This is an output I get off my 2611 router when I do a show log. Does anybody
> Know what this means. The eth0/0 interface is plugged into a catalyst 2950
> switch.
My guess is that there is a full-duplex / half-duplex mismatch. Try
configuring both the router ethernet port and the switch port into which it
is connected to full-duplex.
(Strange though, I guess this is a 10Mbps port on the router? In which case
normally both ends would default to half-duplex which would be fine)
When one end of an ethernet link has chosen full-duplex and the other has
chosen half-duplex then these sorts of errors can occur - typically
resulting in a 1-3% packet loss on a 100Mbps network. This problem can be
difficult to spot: your network gives poor performance but not so bad that
it's easy to spot.
Sending a few hundred large ping packets can usually detect it though:
# ping -s1472 -c300 x.x.x.x
-s = size of packet (adding 28 bytes of IP/ICMP header makes 1500)
-c = count of packets to send
Try x.x.x.x as different devices in your own network. You should get 0%
packet loss if everything is working properly. Packet loss at the 2% level
will cause noticeable slowdown in TCP sessions, and 5% gives severe
degradation, so it's quite important to find and fix.
Regards,
Brian.
>
> *Mar 30 23:37:15.174 UTC: %AMDP2_FE-5-LATECOLL: Ethernet0/0 transmit error
> *Mar 30 23:37:15.294 UTC: %AMDP2_FE-5-LATECOLL: Ethernet0/0 transmit error
> *Mar 30 23:37:15.366 UTC: %AMDP2_FE-5-LATECOLL: Ethernet0/0 transmit error
> *Mar 30 23:37:15.386 UTC: %AMDP2_FE-5-LATECOLL: Ethernet0/0 transmit error
> *Mar 30 23:37:15.422 UTC: %AMDP2_FE-5-LATECOLL: Ethernet0/0 transmit error
>
> --
> cheers
> Richard
>
>
>
> -----
> This is the afnog mailing list, managed by Majordomo 1.94.5
>
> To send a message to this list, e-mail afnog at afnog.org
> To send a request to majordomo, e-mail majordomo at afnog.org and put
> your request in the body of the message (i.e use "help" for help)
>
> This list is maintained by owner-afnog at afnog.org
>
>
-----
This is the afnog mailing list, managed by Majordomo 1.94.5
To send a message to this list, e-mail afnog at afnog.org
To send a request to majordomo, e-mail majordomo at afnog.org and put
your request in the body of the message (i.e use "help" for help)
This list is maintained by owner-afnog at afnog.org