IPMI doesn't work...
on a 5.3 amd64 system. anyone have any luck or know anything about this? i can query variables right up until the point where the kernel loads, then nothing. ibm is saying this can be caused by the actual net driver (the Baseboard Management Controller (BMC) shares the network interface); we're using a Broadcom BCM5704C Dual gig adapter: bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfe00-0xfe00,0xfe01-0xfe01 irq 24 at device 1.0 on pci2 anyone have any idea why this may be the case? unfortunately for me and others, the inability to remotely manage boxes (console/power cycle/detect drive failures/etc) via will be a deal breaker in our push for FBSD in our fleet (couple hundred) of dual proc amd64 IBM e325 servers. SuSe here we come (unwillingly)... thx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI doesn't work...
How are you attempting to manage the server.. via a command line or terminal emulation software directly to the BMC? What amangement software ships with the IBM? Once the kernel loads, you need to perform SOL (serial redirection over LAN), or use management software the speaks directly with the BMC.. Just curious a little bit more about your setup T - Original Message - From: Jeff Behl [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Monday, March 14, 2005 11:25 AM Subject: IPMI doesn't work... on a 5.3 amd64 system. anyone have any luck or know anything about this? i can query variables right up until the point where the kernel loads, then nothing. ibm is saying this can be caused by the actual net driver (the Baseboard Management Controller (BMC) shares the network interface); we're using a Broadcom BCM5704C Dual gig adapter: bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfe00-0xfe00,0xfe01-0xfe01 irq 24 at device 1.0 on pci2 anyone have any idea why this may be the case? unfortunately for me and others, the inability to remotely manage boxes (console/power cycle/detect drive failures/etc) via will be a deal breaker in our push for FBSD in our fleet (couple hundred) of dual proc amd64 IBM e325 servers. SuSe here we come (unwillingly)... thx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI doesn't work...
Thomas Foster wrote: How are you attempting to manage the server.. via a command line or terminal emulation software directly to the BMC? What amangement software ships with the IBM? Once the kernel loads, you need to perform SOL (serial redirection over LAN), or use management software the speaks directly with the BMC.. Just curious a little bit more about your setup T We've only used command line tools which speak directly to the BMC. The strange thing with these boxes is the network card is also used by the BMC. You configure (via the bios) a BMC IP address which is different from what the NIC is assigned via the OS. Like I said earlier, we're able to query/control the chassis just fine when the box is powered off or when it's booting, but as soon as the kernel loads, we lose control and simply no longer get any response from the BMC. This is not he case with the linux distros we've tried, so I'm guessing it's somehow to do with the NIC driver that BSD is loading... jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
