From owner-freebsd-net@FreeBSD.ORG  Tue Mar 15 00:24:56 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D36D416A4CE
	for <freebsd-net@freebsd.org>; Tue, 15 Mar 2005 00:24:56 +0000 (GMT)
Received: from sb.santaba.com (sb.santaba.com [207.154.84.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B3B7343D48
	for <freebsd-net@freebsd.org>; Tue, 15 Mar 2005 00:24:56 +0000 (GMT)
	(envelope-from anon1@santaba.com)
Received: from [192.168.3.100] (unknown [205.180.85.193])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by sb.santaba.com (Postfix) with ESMTP id 91D6128483;
	Mon, 14 Mar 2005 16:24:56 -0800 (PST)
Message-ID: <42362BA8.5000502@santaba.com>
Date: Mon, 14 Mar 2005 16:26:16 -0800
From: Jeff <anon1@santaba.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <4235E6CC.7040909@santaba.com> <42360DB2.5000500@elischer.org>
In-Reply-To: <42360DB2.5000500@elischer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-net@freebsd.org
Subject: Re: IPMI doesn't work...
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Tue, 15 Mar 2005 00:24:56 -0000

Julian Elischer wrote:

> I use IPMI with intel boards using the fxp driver.
> it seems to work ok..
> The only problem I have seen its that is IS possible for the OS to 
> turn off the
> NIC so that IPMI can't be reached..
> Usually during a  'suspend' or similar.
> On a server you wouldn't do that however.

I don't think it's the case of the OS turning off the NIC.  We can 
access/monitor/control the chassis via the BMC fine through the bios 
assigned IP address when the computer is off, and when it is booting, 
but lose control when the kernel loads (the bios assigned ip address is, 
of course, different from what OS assigns).  It seems odd to me how the 
BMC shares the NIC, but maybe this is normal...I'm new to IPMI.