From owner-freebsd-net@FreeBSD.ORG  Fri Dec 21 12:13:58 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 7F83616C
 for <freebsd-net@freebsd.org>; Fri, 21 Dec 2012 12:13:58 +0000 (UTC)
 (envelope-from telemat@extrim.it)
Received: from fatboy.mirasystem.net (unknown [IPv6:2a02:17d0:af:ff01:1:2::])
 by mx1.freebsd.org (Postfix) with ESMTP id E8D218FC12
 for <freebsd-net@freebsd.org>; Fri, 21 Dec 2012 12:13:57 +0000 (UTC)
Received: from tsar.itmh.local (unknown [172.16.64.37])
 by fatboy.mirasystem.net (Postfix) with ESMTP id E2423126B76B
 for <freebsd-net@freebsd.org>; Fri, 21 Dec 2012 18:13:54 +0600 (YEKT)
Message-ID: <50D45282.5080708@extrim.it>
Date: Fri, 21 Dec 2012 18:13:54 +0600
From: Tsaregorodtsev Denis <telemat@extrim.it>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: freebsd-net@freebsd.org
Subject: 'no buffer space available' after switch goes down on freeBSD 7.3
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 12:13:58 -0000

Hello,

I maintenance ISP's DNS server which works under FreeBSD 7.3 and BIND 9.9.1-P4. The network adapter is Intel(R) PRO/1000 Network Connection, driver - em. The server is connected to a Cisco 6500 switch. Sometimes the switch goes down (for maintenance) and is unavailable for 10 minutes. After the switch goes up the server is still unavailable through IP. When I open an IPMI console on the server and enter the ping command, I receive "no buffer space available" error message. And the network doesn't work until the server reboot.
I tried to google this and found that the problem can be solved by increasing nmbclusters parameter. But I want to understand why this problem appears when the switch is rebooting . May be you can suggest something?

Best regards, Tsaregorodtsev Denis