Re: FreeBSD4.4, fxp, no net after ifconfig for ~50 seconds (fwd)
As Cisco switches have STP enabled by default on all ports, maybe a reboot of an 4.4 system is seen as a change in link state, so Catalyst holds the port STP-blocked for a couple of seconds before putting it to forwarding state. Did you try disabling STP on Catalyst eth ports? Marko David Kirchner wrote: > Hi, > > This problem is still ongoing; unfortunately I haven't seen a reply about > it from questions. Maybe someone here knows what's up? > > -- Forwarded message -- > Date: Thu, 15 Nov 2001 13:08:38 -0800 (PST) > From: David Kirchner <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: FreeBSD4.4, fxp, no net after ifconfig for ~50 seconds > > We've recently started using FreeBSD 4.4 for production servers, in an > environment where servers between 3.2 and 4.3 have had no trouble. > Starting with 4.4, the servers have been booting up without being able to > see the network for around 50 seconds. > > tcpdump indicates that the gateway isn't responding to the ARP request for > x.x.x.1 right away. However, the gateway responds immediately to ARP > requests from 3.2 through 4.3 machines. All other ARP requests are > responded to immediately (ie, other FreeBSD 3.2-4.4 servers, even before > the gateway responds) > > I was wondering if a) anyone else has been experiencing similar trouble, > and b) if anything non-obvious has changed in the way FreeBSD ARP request > packets are sent that would cause this? > > Our network runs on primarily Cisco hardware, and the servers are > connected to Catalyst (29xx I believe) switches. The gateway is a Cisco > somethingorother router. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: FreeBSD4.4, fxp, no net after ifconfig for ~50 seconds (fwd)
Seeing the tcpdump would be informative. D-man > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of David Kirchner > Sent: Tuesday, November 27, 2001 10:45 AM > To: [EMAIL PROTECTED] > Subject: FreeBSD4.4, fxp, no net after ifconfig for ~50 seconds (fwd) > > > Hi, > > This problem is still ongoing; unfortunately I haven't seen a reply about > it from questions. Maybe someone here knows what's up? > > -- Forwarded message -- > Date: Thu, 15 Nov 2001 13:08:38 -0800 (PST) > From: David Kirchner <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: FreeBSD4.4, fxp, no net after ifconfig for ~50 seconds > > We've recently started using FreeBSD 4.4 for production servers, in an > environment where servers between 3.2 and 4.3 have had no trouble. > Starting with 4.4, the servers have been booting up without being able to > see the network for around 50 seconds. > > tcpdump indicates that the gateway isn't responding to the ARP request for > x.x.x.1 right away. However, the gateway responds immediately to ARP > requests from 3.2 through 4.3 machines. All other ARP requests are > responded to immediately (ie, other FreeBSD 3.2-4.4 servers, even before > the gateway responds) > > I was wondering if a) anyone else has been experiencing similar trouble, > and b) if anything non-obvious has changed in the way FreeBSD ARP request > packets are sent that would cause this? > > Our network runs on primarily Cisco hardware, and the servers are > connected to Catalyst (29xx I believe) switches. The gateway is a Cisco > somethingorother router. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
FreeBSD4.4, fxp, no net after ifconfig for ~50 seconds (fwd)
Hi, This problem is still ongoing; unfortunately I haven't seen a reply about it from questions. Maybe someone here knows what's up? -- Forwarded message -- Date: Thu, 15 Nov 2001 13:08:38 -0800 (PST) From: David Kirchner <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: FreeBSD4.4, fxp, no net after ifconfig for ~50 seconds We've recently started using FreeBSD 4.4 for production servers, in an environment where servers between 3.2 and 4.3 have had no trouble. Starting with 4.4, the servers have been booting up without being able to see the network for around 50 seconds. tcpdump indicates that the gateway isn't responding to the ARP request for x.x.x.1 right away. However, the gateway responds immediately to ARP requests from 3.2 through 4.3 machines. All other ARP requests are responded to immediately (ie, other FreeBSD 3.2-4.4 servers, even before the gateway responds) I was wondering if a) anyone else has been experiencing similar trouble, and b) if anything non-obvious has changed in the way FreeBSD ARP request packets are sent that would cause this? Our network runs on primarily Cisco hardware, and the servers are connected to Catalyst (29xx I believe) switches. The gateway is a Cisco somethingorother router. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
