Re: Network stalls with 4.5

[Aaron Baugher]

David Wolfskill [EMAIL PROTECTED] writes:

 You might try doing something as crude as

 while (1)
 netstat -ni  sleep 10
 end

 and use that to see of you're getting errors or collisions durng the
 stalls.

Thanks.  They've all been up for 20-30 days, and show zero errors or
collisions.  Also, we're not having this problem with the Linux or
OpenBSD boxes on the same LAN, so it doesn't seem to be a cabling or
hub problem.


Aaron


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message

Re: Network stalls with 4.5

[Aaron Baugher]

Mike Tancsa [EMAIL PROTECTED] writes:

 Do you have a separate simple non production box you can put on the
 LAN with totally different hardware that you can try the same tests
 with running FreeBSD?

No, unfortunately the servers are across the country from my location,
and they're all in production.  But they do have varying hardware --
some Intel network cards, some 3COM; more or less RAM; different
processor speeds; etc.  All worked fine at various 4.3 and 4.4
versions, and all developed these symptoms when we upgraded to 4.5-RC,
and then 4.5-STABLE.


Thanks,
Aaron


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message

Re: Network stalls with 4.5

[Kevin Oberman]

 From: Aaron Baugher [EMAIL PROTECTED]
 Date: 19 Mar 2002 14:32:11 -0600
 Sender: [EMAIL PROTECTED]
 
 David Wolfskill [EMAIL PROTECTED] writes:
 
  You might try doing something as crude as
 
  while (1)
  netstat -ni  sleep 10
  end
 
  and use that to see of you're getting errors or collisions durng the
  stalls.
 
 Thanks.  They've all been up for 20-30 days, and show zero errors or
 collisions.  Also, we're not having this problem with the Linux or
 OpenBSD boxes on the same LAN, so it doesn't seem to be a cabling or
 hub problem.

Aaron,

This may be simple confusion on terminology, but hub normally is
the term used for a multi-port Ethernet device that acts as a simple
repeater with all connections in a common collision domain and all
running half-duplex.

If this is the case, zero collisions is VERY hard to believe.
Collisions will always happen in a half-duplex LAN on a system that
does any significant amount of writing to the network. Simple matter
of statistics. Is the connecting box a hub (repeater) or a switch
(bridge)? If it's a bridge, you should probably be running full-duplex
and would ALWAYS have zero collisions as collision detection is
disabled in that case.

If it's a hub or if the interface is running half-duplex, it's
possible that the NIC is defective and that could be the source of the
problems.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message