Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Apr 2018 11:44:14 +0100
From:      Vincent Hoffman-Kazlauskas <vince@unsane.co.uk>
To:        freebsd-hackers@freebsd.org
Subject:   Re: Can we please finally solve Dell's racadm for FreeBSD? Advice needed
Message-ID:  <e4899760-633f-93cc-0e5c-29905d3fbfcb@unsane.co.uk>
In-Reply-To: <f691a7ee-f038-a1e2-cb45-dab9b35003b8@disroot.org>
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> <f691a7ee-f038-a1e2-cb45-dab9b35003b8@disroot.org>

next in thread | previous in thread | raw e-mail | index | archive | help
for a quick tl;dr
kldload ipmi
pkg install freeipmi ipmitool
dmidecode --string  system-product-name
PowerEdge R420
[root@brittlestar ~]# ipmi-sensors | head -4
ID  | Name             | Type                     | Reading    | Units |
Event
1   | SEL              | Event Logging Disabled   | N/A        | N/A   | N/A
2   | Intrusion        | Physical Security        | N/A        | N/A   |
'OK'
11  | Fan1A            | Fan                      | 6240.00    | RPM   |
'OK'


or for an r210
root@helios:~ # ipmi-sensors | grep -i intr
31 | Intrusion        | Physical Security        | N/A        | N/A   | 'OK'

see also the rest of the freeipmi utils and maybe ipmitool for a
different interface (I prefer it for some uses)

Vince

On 29/04/2018 15:28, Peter G. wrote:
> 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
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e4899760-633f-93cc-0e5c-29905d3fbfcb>