Re: IPMI and Dell ERA/O
On Saturday 30 August 2008 11:56:01 am Jonathan Bond-Caron wrote: On Fri Aug 29 11:24 AM, John Baldwin wrote: If your BIOS doesn't tell us about the IPMI BMC via ACPI or SMBIOS, you can try using hints (I've seen machines thave a BMC, but the BIOS doesn't bother to tell you about it). Dell boxes I've seen have KCS at the default address, so you can just do: hint.ipmi.0.at=isa0 hint.ipmi.0.mode=KCS Either add that to /boot/device.hints or for a test just explicitly set those variables at the loader prompt before booting. Thanks, that works! Although I don't really understand why? After some digging, I found this: (man 4 ipmi) BUGS Not all features of the MontaVista driver are supported. Currently, IPMB and BT modes are not implemented. But the interface for the Dell 1750 with ERA/O seems to be BT. Luckily it works enough for me with KCS (hint.ipmi.0.mode=KCS) http://linux.dell.com/ipmi.shtml Not the same BT. BT is a different transport for the host OS to talk to the BMC that allows for a more asynchronous model. I've not seen any hardware that supports BT yet. I'm saying 'works enough' because some readings show as 'disabled', I'm not sure if that's because the interface is not BT or the supported IPMI version is 1.0 (on the BMC): [EMAIL PROTECTED] /home/jbondc]# ipmitool -I open sdr CPU 1| disabled | ns CPU 2| disabled | ns CPU 3| disabled | ns CPU 4| disabled | ns CPU Planar | 35 degrees C | ok Ambient | 27 degrees C | ok CPU | 1.48 Volts| ok CPU 2| disabled | ns CPU 3| disabled | ns CPU 4| disabled | ns +5 | 5.05 Volts| ok +12 | 11.97 Volts | ok +3.3 | 3.29 Volts| ok Battery | 3.06 Volts| ok +2.5 | 2.55 Volts| ok NIC +2.5 | disabled | ns NIC +1.8 | disabled | ns MemCard A +2.5 | disabled | ns MemCard B +2.5 | disabled | ns MemCard A +1.25 | disabled | ns MemCard B +1.25 | disabled | ns Cover Intrusion | 0x00 | ok Fan Control | 0x17 | ok Fan 1| 6240 RPM | ok Fan 2| 6120 RPM | ok ... This is a property of your BMC. The fact that you can talk to it at all means communication with the BMC is working, and that is all the ipmi(4) driver provides (communication with the BMC). -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: IPMI and Dell ERA/O
On Fri Aug 29 11:24 AM, John Baldwin wrote: If your BIOS doesn't tell us about the IPMI BMC via ACPI or SMBIOS, you can try using hints (I've seen machines thave a BMC, but the BIOS doesn't bother to tell you about it). Dell boxes I've seen have KCS at the default address, so you can just do: hint.ipmi.0.at=isa0 hint.ipmi.0.mode=KCS Either add that to /boot/device.hints or for a test just explicitly set those variables at the loader prompt before booting. Thanks, that works! Although I don't really understand why? After some digging, I found this: (man 4 ipmi) BUGS Not all features of the MontaVista driver are supported. Currently, IPMB and BT modes are not implemented. But the interface for the Dell 1750 with ERA/O seems to be BT. Luckily it works enough for me with KCS (hint.ipmi.0.mode=KCS) http://linux.dell.com/ipmi.shtml I'm saying 'works enough' because some readings show as 'disabled', I'm not sure if that's because the interface is not BT or the supported IPMI version is 1.0 (on the BMC): [EMAIL PROTECTED] /home/jbondc]# ipmitool -I open sdr CPU 1| disabled | ns CPU 2| disabled | ns CPU 3| disabled | ns CPU 4| disabled | ns CPU Planar | 35 degrees C | ok Ambient | 27 degrees C | ok CPU | 1.48 Volts| ok CPU 2| disabled | ns CPU 3| disabled | ns CPU 4| disabled | ns +5 | 5.05 Volts| ok +12 | 11.97 Volts | ok +3.3 | 3.29 Volts| ok Battery | 3.06 Volts| ok +2.5 | 2.55 Volts| ok NIC +2.5 | disabled | ns NIC +1.8 | disabled | ns MemCard A +2.5 | disabled | ns MemCard B +2.5 | disabled | ns MemCard A +1.25 | disabled | ns MemCard B +1.25 | disabled | ns Cover Intrusion | 0x00 | ok Fan Control | 0x17 | ok Fan 1| 6240 RPM | ok Fan 2| 6120 RPM | ok ... I've created a wiki entry for IPMI at: http://www.freebsdwiki.net/index.php/IPMI I will maintain that page as I learn more about IMPI and FreeBSD. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: IPMI and Dell ERA/O
On Fri Aug 29 03:44 AM, Jeremy Chadwick wrote: On Fri, Aug 29, 2008 at 02:17:17AM -0400, Zaphod Beeblebrox wrote: Curiously, IPMI shares the ethernet ports with the onboard ethernet controllers without FreeBSD's knowledge. It does use a different MAC address. It is also apparently capable of using vlans (haven't tested this yet). I'm most nervous about how this might behave if the port was being nailed with traffic --- but I can't easily test this to my satisfaction. What controls the contention for the port between whatever IPMI magic is going on and the OS use of the port? That said, the feature you're referring to (IPMI piggybacking on top of an existing NIC on the mainboard) is called ASF from a NIC driver perspective. The NIC driver for the OS *must* have full awareness of said piggybacking, and if it doesn't, a couple different things can happen: Thanks for the info, the ASF functionality seems to be what Dell uses with the ERA/O, DRAC etc.. cards, http://www.dmtf.org/standards/documents/ASF/DSP0114.pdf (picture on page 6 says it all) Although I fixed my problem with: vi /boot/device.hints hint.ipmi.0.at=isa0 hint.ipmi.0.mode=KCS I'm curious about hw.bge.allow_asf=1 hw.bge.allow_asf=0 It doesn't seem to have any effect on a Dell 1750, any details on how it can affect IPMI, or point me to the discussions I'd like to keep http://www.freebsdwiki.net/index.php/IPMI with as much accurate information as possible ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
I have a 1950-III 1U on the floor here that I'm loading. After configuring IPMI in the BIOS, I can: [2:6:[EMAIL PROTECTED]:~ ipmitool -I lanplus -U root -H 192.168.221.160 shell Password: ipmitool power on Chassis Power Control: Up/On Now. strike is not the 1U in question... and does not, in fact, have IPMI of it's own, but it can talk to the 1950-III, but... [1:1:[EMAIL PROTECTED]:~ dmesg | grep ipmi ipmi0: KCS mode found at io 0xca8 on acpi ipmi0: KCS error: ff ipmi1: IPMI System Interface on isa0 device_attach: ipmi1 attach returned 16 ipmi0: IPMI device rev. 0, firmware rev. 2.2, version 2.0 ipmi0: Number of channels 4 ipmi0: Attached watchdog ... and it will respond to local use of the ipmi tool. Serial console works --- although it seems like it has a finite buffer and too much output overflows the buffer (flow control doesn't seem to fix this). You also have to custom compile the kernel and boot blocks to use COM2 (sio1) as the console. The BIOS seems to have settings to make the external serial port COM2 and use COM1 for IPMI, but the settings don't work. You need to use COM2. While you're at it, the default speed is 57600 (might as well compile in that default, too). The R200's that I have also seem to work fine. I haven't tested serial consoles with them --- but it's on the list. Curiously, IPMI shares the ethernet ports with the onboard ethernet controllers without FreeBSD's knowledge. It does use a different MAC address. It is also apparently capable of using vlans (haven't tested this yet). I'm most nervous about how this might behave if the port was being nailed with traffic --- but I can't easily test this to my satisfaction. What controls the contention for the port between whatever IPMI magic is going on and the OS use of the port? Anyways... the really cool thing about IPMI is that it's cheap enough to be included. The original poster spoke of a PCI card (likely one of the management cards) --- these are expensive options --- especially if you don't need graphics or remote media. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
On Fri, Aug 29, 2008 at 02:17:17AM -0400, Zaphod Beeblebrox wrote: Curiously, IPMI shares the ethernet ports with the onboard ethernet controllers without FreeBSD's knowledge. It does use a different MAC address. It is also apparently capable of using vlans (haven't tested this yet). I'm most nervous about how this might behave if the port was being nailed with traffic --- but I can't easily test this to my satisfaction. What controls the contention for the port between whatever IPMI magic is going on and the OS use of the port? My general opinion is to avoid IPMI at all costs. The concept itself is great, and the design idea is okay, but the implementation is an atrocity. If you *must* use IPMI, get an implementation that uses its own, dedicated NIC. That said, the feature you're referring to (IPMI piggybacking on top of an existing NIC on the mainboard) is called ASF from a NIC driver perspective. The NIC driver for the OS *must* have full awareness of said piggybacking, and if it doesn't, a couple different things can happen: a) NIC simply does not work b) NIC works, but behaves oddly -- usually this is tracked down to the local network seeing the MAC address continually change for the IP address associated with the machine c) NIC works, but IPMI and other features do not work There are a couple different drivers for FreeBSD which have ASF knowledge; bge(4) does, and I believe em(4) does (I could be wrong here). bge(4) has a loader.conf tunable that tells the driver to understand ASF or not. In general, it's horrible, and I feel sorry for driver authors having to deal with it. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
Hi, On 29 Aug 2008, at 08:44, Jeremy Chadwick wrote: [...]That said, the feature you're referring to (IPMI piggybacking on top of an existing NIC on the mainboard) is called ASF from a NIC driver perspective. In implementations I've looked at, the interfaces really are distinct hardware but they use a common phy. It's just about transparent to software. The NIC driver for the OS *must* have full awareness of said piggybacking, and if it doesn't, a couple different things can happen: a) NIC simply does not work b) NIC works, but behaves oddly -- usually this is tracked down to the local network seeing the MAC address continually change for the IP address associated with the machine That might just be be misconfiguration: the IPMI interface should have an IP address distinct from (any address of) the 'proper' interface. c) NIC works, but IPMI and other features do not work There are a couple different drivers for FreeBSD which have ASF knowledge; bge(4) does, and I believe em(4) does (I could be wrong here). em(4) does indeed work, we are using it on a couple of dozen boxes. bge(4) has a loader.conf tunable that tells the driver to understand ASF or not. In general, it's horrible, and I feel sorry for driver authors having to deal with it. The only problem I have seen on em is that by default the driver resets the phy during boot which confuses IPMI; if a SOL console session is active, the driver is signalled not to do the reset. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bob Bishop [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
On Fri, Aug 29, 2008 at 4:48 AM, Bob Bishop [EMAIL PROTECTED] wrote: The only problem I have seen on em is that by default the driver resets the phy during boot which confuses IPMI; if a SOL console session is active, the driver is signalled not to do the reset. Same here. The 1950-III that I have has bce cards (2) on the motherboard. When the kernel probes them, the IPMI interface dissapears for a second or so. The IPMI documentation seems to imply that either port will talk IPMI --- but I havn't tested this. I havn't noticed any problems with the port otherwise. I'm even bridging the two motherboard ports right now. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI and Dell ERA/O
On Friday 29 August 2008 01:33:36 am Jonathan Bond-Caron wrote: Hi Everyone, I have a dell 1750 server with ERA/O card running on FreeBSD 7.0-STABLE According to Dell, the ERA card supports ipmi 1.0: http://linux.dell.com/ipmi.shtml But so far no luck with freebsd :/ If your BIOS doesn't tell us about the IPMI BMC via ACPI or SMBIOS, you can try using hints (I've seen machines thave a BMC, but the BIOS doesn't bother to tell you about it). Dell boxes I've seen have KCS at the default address, so you can just do: hint.ipmi.0.at=isa0 hint.ipmi.0.mode=KCS Either add that to /boot/device.hints or for a test just explicitly set those variables at the loader prompt before booting. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
IPMI and Dell ERA/O
Hi Everyone, I have a dell 1750 server with ERA/O card running on FreeBSD 7.0-STABLE According to Dell, the ERA card supports ipmi 1.0: http://linux.dell.com/ipmi.shtml But so far no luck with freebsd :/ [EMAIL PROTECTED] /usr/src/sys/i386/conf]# ipmitool -I open channel info 1 Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory [EMAIL PROTECTED] /usr/src/sys/i386/conf]# kldstat Id Refs AddressSize Name 15 0xc040 4eed90 kernel 32 0xc08fb000 1bd0 smbus.ko 42 0xc08fd000 6a594acpi.ko 71 0xc69b7000 a000 ipmi.ko [EMAIL PROTECTED] /usr/src/sys/i386/conf]# pciconf -lv (.) [EMAIL PROTECTED]:0:8:0: class=0xff card=0x000c1028 chip=0x000c1028 rev=0x00 hdr=0x00 vendor = 'Dell Computer Corporation' device = 'Embedded Systems Management Device 4' Any hacks or wisdom that can make this work? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
