Date: Tue, 14 Mar 2006 23:07:32 -0800 From: "Jack Vogel" <jfvogel@gmail.com> To: Matt <matt@successfulhosting.com> Cc: freebsd-net@freebsd.org Subject: Re: IPMI During Boot Message-ID: <2a41acea0603142307v78f41d86n7523574e26cd7f5f@mail.gmail.com> In-Reply-To: <002f01c6479a$696d1510$c802a8c0@BLADESNITZ> References: <002f01c6479a$696d1510$c802a8c0@BLADESNITZ>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/14/06, Matt <matt@successfulhosting.com> wrote: > Hello, > > I've tried to be fairly thorough in researching the problem before postin= g > to the list, however, there doesn't seem to be a great multitude of > information out there regarding IPMI configuration on FreeBSD. > > Here's the setup: I have a SuperMicro 6014H-82 Chassis with the > AOC-IPMI20-E > (http://supermicro.com/products/accessories/addon/AOC-IPMI20-E.cfm). The > motherboard has an Intel adapter that uses the em(4) driver (so it isn't > suppose to suffer the same issues as the bge adapter). I have ensured th= e > MAC address configured for the IPMI matches the MAC address of the networ= k > card itself. I'm using a private network IP (192.168.2.41) on the IPMI c= ard > itself, and I've tried various settings for the adapter in the OS (I've > tried it using the same private IP, and a different private IP). The IPM= I > function itself works great, I can connect and perform the needed tasks, = I > can even use Serial-On-Lan to get into the BIOS, the RAID card setup, as > well as log into the Operating system. I've also configured the boot > settings so that I do get the menu of boot options, and I can see the boo= t > happening. > > However, here's the issue: During booting, when the "em" driver loads, t= he > IPMI function effectively ceases. From the time the em driver is loaded, > until the OS actually configures the network adapter, I do not receive > output to the serial console. If I disconnect the IPMI session, I cannot > reconnect during the time either (IPMI is suppose to connect at all times= , > even when the box is powered off!). If I don't disconnect, eventually, a= ll > the backlog will spew to the screen and I'll be at the login prompt. > However, this poses a problem if I need to use single-user mode or if FSC= K > requires some intervention. Since single-user mode never configures the > network adapter, then it just never comes back. Regarding FSCK, if a box > crashes and goes to FSCK, even if its set to automatically fsck (too scre= wed > up for background fsck or something), I have no way of seeing that, since= it > occurs before the network adapter is configured as well. This kinda defe= ats > the purpose of the IPMI card. > > I'm using the SuperMicro IPMIView program. I have tried both the regular > IPMI firmware that uses a non-standard RMCP protocol, as well as their > "beta" firmware that uses the standard RMCP+ protocol. Using the RMCP+ > firmware enables me to use ipmitool or such from command line, but the sa= me > problem exists. > > I have tried a multitude of things. I've upgraded to the latest stable > version (6-STABLE). Built the latest boot blocks (cd /usr/src/sys/boot &= & > make && make install), installed them (fdisk -B && disklabel -B > /dev/aacd0s1). Below are the various configs and messages I can think of= to > post. The kernel is pretty much GENERIC with maxusers, smp, and quota. > > /boot.config: > -Dh -S19200 > > /boot/loader.conf: > boot_serial=3D"YES" > boot_multicons=3D"YES" > console=3D"comconsole,vidconsole" > comconsole_speed=3D"19200" > > I'm pretty sure the above is overkill. I've tried using just one or the > other or both, and while the console redirection still works, it still > freezes when the em driver loads. > > > One thing to note when look at the dmesg. I do see the dmesg load fast o= n > the SOL up until the em loads, and then it shows this: > > em0: Ethernet address: 00:30:48:2f:51:d2 > > Until the network interface is brought up in the later boot stages, at wh= ich > point it flies through what it missed to the login prompt. Hi Matt, I have zero experience with IPMI on FreeBSD, however I worked on it a fair amount on Linux while at IBM. Off the top of my head I'm wondering if you really should assign the same MAC address to the BMC as the NIC, does something tell you to do this? I was not sure from your description, are you saying that IPMI stops working during boot, but eventually it does work again, or does it only work with the em driver is not loaded? Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0603142307v78f41d86n7523574e26cd7f5f>