From owner-freebsd-net@FreeBSD.ORG  Mon Mar 14 22:18:27 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 E148F16A4CE
	for <freebsd-net@freebsd.org>; Mon, 14 Mar 2005 22:18:27 +0000 (GMT)
Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A0D8F43D41
	for <freebsd-net@freebsd.org>; Mon, 14 Mar 2005 22:18:27 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from [208.206.78.97] (julian.vicor-nb.com [208.206.78.97])
	by mail.vicor-nb.com (Postfix) with ESMTP
	id EC9487A403; Mon, 14 Mar 2005 14:18:26 -0800 (PST)
Message-ID: <42360DB2.5000500@elischer.org>
Date: Mon, 14 Mar 2005 14:18:26 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Jeff <anon1@santaba.com>
References: <4235E6CC.7040909@santaba.com>
In-Reply-To: <4235E6CC.7040909@santaba.com>
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: Mon, 14 Mar 2005 22:18:28 -0000

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.

Jeff wrote:

> <posted this to -questions too but thought the nic component made it 
> worth posting to -net>
>
> on a 5.3 amd64 system.  anyone have any luck or know anything about 
> this?  i can query variables right up until the point where the kernel 
> loads, then nothing.  ibm is saying this can be caused by the actual 
> nic driver (the Baseboard Management Controller (BMC) shares the 
> network interface); the system uses a Broadcom BCM5704C Dual gig adapter:
>
> bge0: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003> mem 
> 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 1.0 on pci2
>
> anyone have any idea why this may be the case?  unfortunately for me 
> and others here, the inability to remotely manage boxes (console/power 
> cycle/detect drive failures/etc) via ipmi will be a deal breaker in 
> our push for FBSD in our fleet (couple hundred) of dual proc amd64 IBM 
> e325 servers.  SuSE here we come (unwillingly)...
>
> thx
>
>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"