Date: Mon, 22 Aug 2005 07:58:37 -0700 (PDT) From: dpk <dpk@dpk.net> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-stable@freebsd.org Subject: Re: broken fxp driver in 4.x ... Message-ID: <20050822075409.T71377@shared10.hosting.flyingcroc.net> In-Reply-To: <20050822115056.M1002@ganymede.hub.org> References: <20050822013402.B1002@ganymede.hub.org> <20050822073642.B71377@shared10.hosting.flyingcroc.net> <20050822115056.M1002@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Aug 2005, Marc G. Fournier wrote: > > Can you try having your network guys enable 'portfast' on your server > > port, and then see if adding an IP alias still causes the hang? > > I'd love to, but I know nothing about the Cisco switches other then the > very bare minimal ... if you can give me some instructions, I can look at > getting it done though ... > > Thanks ... > This only applies if they're using the Spanning Tree Protocol option (otherwise there's no reason I'm aware of that making a switch change would cause the problem to disappear, unfortunately). set spantree portfast M/P enable where M is the module and P is the port. http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/rel_5_2/config/stp_enha.htm#32976 The switch will display a significant caution statement when the command is issued, but it should only apply if you're attaching a switch or some device that talks to the network like it's a switch (I think we have some hosts like that, 802.1q aware load balancers).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050822075409.T71377>