From owner-freebsd-stable@FreeBSD.ORG Mon Aug 22 14:58:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4D7616A41F for ; Mon, 22 Aug 2005 14:58:38 +0000 (GMT) (envelope-from dpk@dpk.net) Received: from shared10.hosting.flyingcroc.net (shared10.hosting.flyingcroc.net [207.246.149.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4331B43D53 for ; Mon, 22 Aug 2005 14:58:38 +0000 (GMT) (envelope-from dpk@dpk.net) Received: from shared10.hosting.flyingcroc.net (localhost [127.0.0.1]) by shared10.hosting.flyingcroc.net (8.12.9p2/8.12.10) with ESMTP id j7MEwbrR044386; Mon, 22 Aug 2005 07:58:37 -0700 (PDT) Received: from localhost (dpk@localhost) by shared10.hosting.flyingcroc.net (8.12.9p2/8.12.10/Submit) with ESMTP id j7MEwbYD044382; Mon, 22 Aug 2005 07:58:37 -0700 (PDT) X-Authentication-Warning: shared10.hosting.flyingcroc.net: dpk owned process doing -bs Date: Mon, 22 Aug 2005 07:58:37 -0700 (PDT) From: dpk X-X-Sender: dpk@shared10.hosting.flyingcroc.net To: "Marc G. Fournier" In-Reply-To: <20050822115056.M1002@ganymede.hub.org> Message-ID: <20050822075409.T71377@shared10.hosting.flyingcroc.net> References: <20050822013402.B1002@ganymede.hub.org> <20050822073642.B71377@shared10.hosting.flyingcroc.net> <20050822115056.M1002@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: broken fxp driver in 4.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 14:58:38 -0000 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).