Date: Mon, 11 Aug 1997 21:54:31 -0400 (EDT) From: Ben Black <black@zen.cypher.net> To: Tom Samplonius <tom@sdf.com> Cc: David Greenman <dg@root.com>, hackers@FreeBSD.ORG Subject: Re: fxp driver full duplex packet loss problem Message-ID: <Pine.LNX.3.91.970811215346.21695A-100000@zen.cypher.net> In-Reply-To: <Pine.BSF.3.95q.970811184359.8572D-100000@misery.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
assuming the 1900 has the same software config commands as the 5500 then you should just be able to say: set port duplex <port> full and it will automatically switch right then. On Mon, 11 Aug 1997, Tom Samplonius wrote: > > On Mon, 11 Aug 1997, Tom Samplonius wrote: > > > > > On Mon, 11 Aug 1997, Ben Black wrote: > > > > > a good indication of this duplex mismatch is a sudden appearance of FCS > > > errors and Runts on the cisco interface. > > > > When I switch full duplex on the FreeBSD server, the switch starts > > recording late collision errors on that port (a 10BT port on a Cat 1900). > > I'm not sure what this means. > > > > Tom > > Actually I do know (now) what that means. The switch (which is supposed > to auto-negotiate and has no manual setting) is set to half, and card is > set to full. > > I'm guessing the switch doesn't understand devices switching from half > to full on the fly, and only detects this on intial connect. I will try > turning full duplex on, and them plug it into a different port. > > Tom >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.91.970811215346.21695A-100000>