From owner-freebsd-stable@FreeBSD.ORG Wed Feb 14 22:28:35 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DDA9216A407 for ; Wed, 14 Feb 2007 22:28:35 +0000 (UTC) (envelope-from gvanlehn@ccsf.edu) Received: from ns7.ccsf.cc.ca.us (ns7.ccsf.cc.ca.us [147.144.1.250]) by mx1.freebsd.org (Postfix) with ESMTP id CCC8F13C48D for ; Wed, 14 Feb 2007 22:28:35 +0000 (UTC) (envelope-from gvanlehn@ccsf.edu) Received: from bat-gwpo.ccsf.edu ([10.2.0.249]) by ns7.ccsf.cc.ca.us (8.13.1/8.13.1) with ESMTP id l1ELxGqw025271 for ; Wed, 14 Feb 2007 13:59:16 -0800 Received: from sfccd-MTA by bat-gwpo.ccsf.edu with Novell_GroupWise; Wed, 14 Feb 2007 14:00:57 -0800 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Wed, 14 Feb 2007 14:00:30 -0800 From: "Glen Van Lehn" To: , Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Re: Intermittent network issues with Freebsd 6.2 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: Wed, 14 Feb 2007 22:28:35 -0000 >>> "Dimuthu Parussalla" 02/11/07 3:54 PM = >>> Hi All, I am having intermittent network issues with our IBM X236 dual xeon = server. Server comes with two bge network cards. At random intervals internal lan drops out. And then few minutes later it comes back online. So far I can only find some interface errors on netstat -i. Can anyone = help me to resolve this issue. Please refer to attached files and below outputs for more information. /etc/sysctl.conf kern.ipc.maxsockbuf=3D8388608 kern.ipc.somaxconn=3D2048 net.inet.tcp.sendspace=3D3217968 net.inet.tcp.recvspace=3D3217968 net.inet.tcp.rfc1323=3D1 #net.inet.tcp.rfc3042=3D0 net.inet.ip.portrange.hilast=3D65535 net.inet.ip.portrange.hifirst=3D49152 net.inet.ip.portrange.last=3D65535 net.inet.ip.portrange.first=3D1024 net.inet.tcp.inflight.enable=3D0 /boot/loader.conf kern.ipc.nmbclusters=3D32768 vmstat -i interrupt total rate irq52: ips0 75446 17 irq30: ahd0 81 0 irq31: ahd1 15 0 irq1: atkbd0 69 0 irq3: sio1 74 0 irq4: sio0 67 0 irq6: fdc0 90 0 irq14: ata0 47 0 irq16: bge0 bge1+ 1395326 315 irq19: uhci1 15 0 irq23: ehci0 1 0 cpu0: timer 8845847 1998 cpu3: timer 1 0 cpu1: timer 2 0 cpu2: timer 8830658 1995 Total 19147739 4326 netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll bge0 1500 00:11:25:e9:7f:58 392325 880 449420 0 0 bge0 1500 192.168.1 lan 342652 - 4175 - - bge1 1500 00:11:25:e9:7f:59 369744 1648 363688 0 0 Regards Dimuthu Parussalla =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Do you have access to the network switch that your server connects to? = The stats on the port may show CRC errors or the log may show carrier = off/on transitions indicating that 'Auto-negotiation' isn't stable. I've = seen this a lot with 100FDx connections and a few times with GbE. = Sometimes it helps to change the port speed/duplex settings from 'Auto' to = [or vice versa ;]. My preference has been to use = 'Auto' if it works, and, if it doesn't, to nail down the server settings, = then see whether nailing the switch port setting or leaving the switch = port in 'Auto' is best. =20 ymmv, glen van lehn city college san francisco