From owner-freebsd-net@FreeBSD.ORG Tue Mar 15 17:34:15 2005 Return-Path: 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 DBAEF16A4CE for ; Tue, 15 Mar 2005 17:34:15 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8968F43D1D for ; Tue, 15 Mar 2005 17:34:15 +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 CA2CC28433; Tue, 15 Mar 2005 09:34:14 -0800 (PST) Message-ID: <42371CE7.5090003@santaba.com> Date: Tue, 15 Mar 2005 09:35:35 -0800 From: Jeff User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Vince References: <4235E6CC.7040909@santaba.com> <42360DB2.5000500@elischer.org> <42362BA8.5000502@santaba.com> <20050315013029.GA7949@empiric.icir.org> <42365FBB.2070404@roq.com> In-Reply-To: <42365FBB.2070404@roq.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Julian Elischer 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 17:34:16 -0000 so i poked through the broadcom driver code for linux (http://www.broadcom.com/drivers/downloaddrivers.php) and found quite a few mentions of ASF/IPMI in the code. a little research shows that the Alert Standard Forum (ASF) defines the Remote Management Control Packet (RMCP) used in IPMI-over-LAN. see the readme for ipmitool: http://cvs.sourceforge.net/viewcvs.py/ipmitool/ipmitool/README?rev=1.2&view=markup the readme also says the address of the bmc must be the same as that of the system (as someone mentioned earlier), but i've found this not to be the case on other platforms. it makes a lot of sense to not tie the two addresses together. a change in ip unfortunateley, i'm no driver coder or i'd attempt a patch... Michael Vince wrote: > Just out of interest has any one got serial console to work with this > IPMI stuff? > I was looking at regular 9pin serial alternatives since Dell machines > normally only have 1 serial port and I prefer 2. > > Regards, > Mike > > Bruce M Simpson wrote: > >> On Mon, Mar 14, 2005 at 04:26:16PM -0800, Jeff wrote: >> >> >>> 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. >>> >> >> >> I can only speak for looking at the Intel gigabit chip datasheets and >> our em(4) driver somewhat, but there are registers which control the >> 'pass through' which IPMI uses. It could be that the bge driver is >> unaware of the registers Broadcom added to support IPMI. >> >> In this case we'd need to find out what they are and teach the driver >> not to meddle with them. >> >> Regards, >> BMS >> _______________________________________________ >> 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" >> >> >