Date: Mon, 14 Mar 2005 18:54:45 -0800 From: Julian Elischer <julian@elischer.org> To: Jeff <anon1@santaba.com> Cc: Jung-uk Kim <jkim@niksun.com> Subject: Re: IPMI doesn't work... Message-ID: <42364E75.8030205@elischer.org> In-Reply-To: <42362D37.6010202@santaba.com> References: <4235E6CC.7040909@santaba.com> <200503141747.57487.jkim@niksun.com> <42362D37.6010202@santaba.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff wrote: > >> >> >> >> > I'm not sure what you mean by in band. The IP address of the BMC is > assigned via the bios and is different from what the OS later > assigns. With imiptool we can turn on/powercycle/monitor via the BMC > assigned address up until the point where the kernel loads. Once it > does, the BMC no longer responds. This doesn't happen with the two > linux distros we've tried it on. Wtih both, including SuSE, we can > still query/control via the BMC using ipmitool. It seems to be some > sort of driver issue to me. I find it confusing that the NIC is > shared between the BMC and the OS, but I guess that's just how it's > done. Perhaps the bsd broadcomm driver is simply blocking this > somehow... you have to assign it the same address! > > jeff > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42364E75.8030205>