Date: Sun, 29 Apr 2018 16:28:06 +0200 From: "Peter G." <freebsd@disroot.org> To: xxjack12xx@gmail.com Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed Message-ID: <f691a7ee-f038-a1e2-cb45-dab9b35003b8@disroot.org> In-Reply-To: <CALeGphypQv7_4%2BD%2BrNZOG8t%2B3yrBsxMJBUuwV6jkDCkqMWq=%2BA@mail.gmail.com> References: <5eca3020-4b9c-dd43-8cf0-066d63a92521@disroot.org> <CAGuJ=CmvZbVG5U%2B_OuU-hwTWjoww3rt%2BFwOjW=9jfKLyotOHdw@mail.gmail.com> <CALeGphypQv7_4%2BD%2BrNZOG8t%2B3yrBsxMJBUuwV6jkDCkqMWq=%2BA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/04/2018 05:08, Jack L. wrote: > I manage a variety of Dell servers running FreeBSD, only 610 and 1950s > work with racadm but everything that can be done with racadm can also > be done with ipmitool. I just use ipmitool to get around instead of > their proprietary racadm stuff. What functionality do you need from > racadm and maybe I can give you an ipmitool equivalent? It seems I may missed the ipmi angle altogether assuming it was only remote. Only now following Dan's comments I am realizing how racadm works talking to local hardware. You mean using this impi(4) as a local device and talking to it via local tool allowing coms with the device? Oh, that would do nicely. I need this for scripting mostly, e.g. monitoring what the intrusion sensor shows. Can you please describe your setup? What other kernel modules and 3rd party software do you employ? Any tricks with device.hints are needed? I have a small R220 at hand for testing, but it's lacking impi(4) altogether. Will have to rebuild. -- PG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f691a7ee-f038-a1e2-cb45-dab9b35003b8>