From owner-freebsd-net@FreeBSD.ORG Thu Mar 16 12:29:04 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 B813B16A420 for ; Thu, 16 Mar 2006 12:29:04 +0000 (UTC) (envelope-from matt@successfulhosting.com) Received: from mail.successfulhosting.com (web.successfulhosting.com [147.202.46.199]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E40E43D72 for ; Thu, 16 Mar 2006 12:29:00 +0000 (GMT) (envelope-from matt@successfulhosting.com) Received: (qmail 30931 invoked by uid 0); 16 Mar 2006 12:31:07 -0000 Received: from unknown (HELO BLADESNITZ) (mhouston@successfulhosting.com@68.205.195.64) by mail.successfulhosting.com with SMTP; 16 Mar 2006 12:31:07 -0000 From: "Matt" To: Date: Thu, 16 Mar 2006 07:29:01 -0500 Organization: Successful Hosting Message-ID: <007c01c648f5$34cff870$75a31f9b@BLADESNITZ> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 Thread-Index: AcZIZBQ7XJPB1k09QkC0wZXfx10mUgAhwTawAAJ0OQA= In-Reply-To: <007b01c648f4$75eb41d0$75a31f9b@BLADESNITZ> 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: Thu, 16 Mar 2006 12:29:04 -0000 Just to emphasize the fact, I'd actually remove the ifconfig_ lines from my rc.conf, so when the OS came up, it did not assign an IP to the interface. IPMI refused to work until I assigned an IP. Once assigned, I can remove the IP and do ifconfig em0 down, etc. and the IPMI continues to work (until I reboot). Matt Houston Systems Administrator Successful Hosting matt@successfulhosting.com http://www.SuccessfulHosting.com Toll-Free: +1.866.494.5096 ================================= The Success behind your web site! ================================= -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Matt Sent: Thursday, March 16, 2006 7:24 AM To: 'Jack Vogel'; freebsd-net@freebsd.org Subject: RE: IPMI During Boot Hello, The help is much appreciate. Just to test thoroughly, I recompiled my kernel without the em driver, and I didn't load the module in loader.conf. Upon rebooting, it flew through just fine, and I was even able to drop to single-user mode with no issues. I then enabled the em module in the loader.conf, and got the results as before, I'm dead in the water until the network is configured. Below is the information you requested. The IPMI Card is currently configured as: IP: 192.168.2.110 MAC: 00:30:48:2F:A0:80 Here's the ifconfig: em0: flags=8843 mtu 1500 options=b inet 192.168.2.105 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:30:48:2f:a0:80 media: Ethernet autoselect (100baseTX ) status: active And pciconf -v -l output: hostb0@pci0:0:0: class=0x060000 card=0x688015d9 chip=0x35908086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = 'E752x Server Memory Controller Hub' class = bridge subclass = HOST-PCI none0@pci0:0:1: class=0xff0000 card=0x688015d9 chip=0x35918086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub Error Reporting Registers' none1@pci0:1:0: class=0x088000 card=0x688015d9 chip=0x35948086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub DMA Controller' class = base peripheral pcib1@pci0:2:0: class=0x060400 card=0x00000050 chip=0x35958086 rev=0x0c hdr=0x01 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub PCI Express Port A0' class = bridge subclass = PCI-PCI pcib4@pci0:4:0: class=0x060400 card=0x00000050 chip=0x35978086 rev=0x0c hdr=0x01 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub PCI Express Port B0' class = bridge subclass = PCI-PCI pcib5@pci0:6:0: class=0x060400 card=0x00000050 chip=0x35998086 rev=0x0c hdr=0x01 vendor = 'Intel Corporation' device = 'E752x Memory Controller Hub PCI Express Port C0' class = bridge subclass = PCI-PCI pcib6@pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0xc2 hdr=0x01 vendor = 'Intel Corporation' device = '82801BA/CA/DB/DBL/EB/ER/FB (ICH2/3/4/4/5/5/6), 6300ESB Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x24d08086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) LPC Interface Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:31:1: class=0x01018a card=0x688015d9 chip=0x24db8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) EIDE Controller' class = mass storage subclass = ATA none2@pci0:31:3: class=0x0c0500 card=0x688015d9 chip=0x24d38086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) SMBus Controller' class = serial bus subclass = SMBus pcib2@pci1:0:0: class=0x060400 card=0x00000044 chip=0x03298086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge A' class = bridge subclass = PCI-PCI none3@pci1:0:1: class=0x080020 card=0x688015d9 chip=0x03268086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'PCI Bridge Hub I/OxAPIC Interrupt Controller A' class = base peripheral subclass = interrupt controller pcib3@pci1:0:2: class=0x060400 card=0x00000044 chip=0x032a8086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge B' class = bridge subclass = PCI-PCI none4@pci1:0:3: class=0x080020 card=0x688015d9 chip=0x03278086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'PCI Bridge Hub I/OxAPIC Interrupt Controller B' class = base peripheral subclass = interrupt controller em0@pci2:3:0: class=0x020000 card=0x117a15d9 chip=0x10798086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82546EB Dual Port Gigabit Ethernet Controller' class = network subclass = ethernet em1@pci2:3:1: class=0x020000 card=0x117a15d9 chip=0x10798086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82546EB Dual Port Gigabit Ethernet Controller' class = network subclass = ethernet ahd0@pci3:4:0: class=0x010000 card=0x688015d9 chip=0x801d9005 rev=0x10 hdr=0x00 vendor = 'Adaptec Inc' device = 'AIC-7902B Ultra320 SCSI Controller' class = mass storage subclass = SCSI ahd1@pci3:4:1: class=0x010000 card=0x688015d9 chip=0x801d9005 rev=0x10 hdr=0x00 vendor = 'Adaptec Inc' device = 'AIC-7902B Ultra320 SCSI Controller' class = mass storage subclass = SCSI none5@pci6:1:0: class=0x030000 card=0x80081002 chip=0x47521002 rev=0x27 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'Rage XL PCI' class = display subclass = VGA Matt Houston Systems Administrator Successful Hosting matt@successfulhosting.com http://www.SuccessfulHosting.com Toll-Free: +1.866.494.5096 ================================= The Success behind your web site! ================================= -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Jack Vogel Sent: Wednesday, March 15, 2006 2:01 PM To: Julian Elischer Cc: Matt; freebsd-net@freebsd.org Subject: Re: IPMI During Boot On 3/15/06, Jack Vogel wrote: > On 3/15/06, Julian Elischer wrote: > > > > 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. > > well, i'm not positive about the MAC thing, but I am quite sure that on > IBM xSeries systems you assigned a different IP address to the BMC, > this was done in the BIOS. And, when I think about that, if it did have > a seperate IP address then it musta had a seperate MAC too... > > Course, that was IBM hardware. I'll have to check up on this more > at work tomorrow. > > So Julian, are you saying that you have seen this kind of functionality > work on FreeBSD?? Hmm, well I've been told that using the same IP address or not should both work :) Matt, can you do a pciconf listing for me, I'd like to see exactly what MAC you have. The most recent systems that are AMT capable need some special code in the driver that FreeBSD doesnt yet have. I'm wondering if that might be whats happening here. Jack _______________________________________________ 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" _______________________________________________ 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"