From owner-freebsd-net@FreeBSD.ORG Wed Mar 15 22:02:06 2006 Return-Path: X-Original-To: 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 6B57616A401 for ; Wed, 15 Mar 2006 22:02:06 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail2.ambrisko.com (mail2.ambrisko.com [64.174.51.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id A037B43D9F for ; Wed, 15 Mar 2006 21:59:58 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail2.ambrisko.com with ESMTP; 15 Mar 2006 13:59:23 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.11) with ESMTP id k2FLxlJV023119; Wed, 15 Mar 2006 13:59:47 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id k2FLxlPA023118; Wed, 15 Mar 2006 13:59:47 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200603152159.k2FLxlPA023118@ambrisko.com> In-Reply-To: <4417CE70.5070301@elischer.org> To: Julian Elischer Date: Wed, 15 Mar 2006 13:59:47 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: Matt , Jack Vogel , freebsd-net@freebsd.org Subject: Re: IPMI During Boot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 22:02:06 -0000 Julian Elischer writes: | Working with intel (TM) motherboards using the Intel Gb chips, | and talking to the intel reps last year (for my previous employer) I was | led to believe that | these chips supported IPMI by giving the BMC a back door into the same | NIC that the | OS was using. | (using an I2c (SMB) interface) | On the machines I used, I am pretty sure the bios gave the same MAC | address to the BMC | side of things as the OS side of theings by default, and we had is set | up so that we used the | same IP address also. ... and at your current employer that is not required nor setup that way, albeit, with different HW (Intel chip on Dell server). ambrisko 5] ipmitool lan print 1 Set in Progress : 0x00 Auth Type : 0x17 Auth Type Enable : callback=0x06 user=0x06 operator=0x06 admin=0x06 oem=0x06 IP Address Source : 0x01 IP Address : 1.1.1.1 Subnet Mask : 255.255.255.0 MAC Address : 00:11:43:31:56:61 SNMP Community String : public IP Header : TTL=0x40 flags=0x40 precedence=0x00 TOS=0x10 Default Gateway IP : 1.1.1.254 Default Gateway MAC : 00:00:00:00:00:00 Backup Gateway IP : 0.0.0.0 Backup Gateway MAC : 00:00:00:00:00:00 ambrisko 6] ifconfig -a | grep 00:11:43:31:56 ether 00:11:43:31:56:5f ether 00:11:43:31:56:60 ambrisko 7] ifconfig em0 em0: flags=8843 mtu 1500 options=3 inet 192.168.98.87 netmask 0xffffff00 broadcast 192.168.98.255 ether 00:11:43:31:56:5f media: Ethernet autoselect (1000baseTX ) status: active ambrisko 11] pciconf -l | grep em0 em0@pci6:7:0: class=0x020000 card=0x016d1028 chip=0x10768086 rev=0x05 hdr=0x00 ambrisko 12] Which can make it interesting since we can query itself over the network via a router to itself: ambrisko 17] ipmitool -I lan -H 1.1.1.1 sel SEL Information Version : 51 Entries : 64 Free Space : 7168 Last Add Time : 03/02/2006 19:15:25 Last Del Time : 10/07/2005 16:18:14 Overflow : false Delete cmd : unsupported Parial add cmd : unsupported Reserve cmd : supported Get Alloc Info : unsupported ambrisko 18] Note that we have a hacked up/down. You might try to "ifconfig down" the interface and see if that breaks things and it "up" brings it back to life. With the Broadcom NIC we have to be careful to keep the window short when the NIC's IPMI/ASF stack is not up. Doug A.