yum install perl-IPC-Run
check_ipmi_sensor
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&dlc=en&docname=c03098595
[root@eguvennagios man]# /usr/lib64/nagios/plugins/check_ipmi_sensor -H 192.168.170.187 -U tc -P xxxx -L USER /usr/local/sbin/ipmi-sensors: authentication type unavailable for attempted privilege level
-> Execution of ipmimonitoring failed with return code 1. -> ipmimonitoring was executed with the following parameters: /usr/local/sbin/ipmi-sensors -h 192.168.170.187 -u tc -p xxxx -l USER --quiet-cache --sdr-cache-recreate --interpret-oem-data --output-sensor-state --ignore-not-available-sensors
[root@eguvennagios man]# /usr/local/sbin/ipmi-sensors -h 192.168.170.187 -u tc -p xxxx -l USER --quiet-cache --sdr-cache-recreate --interpret-oem-data --output-sensor-state --ignore-not-available-sensors /usr/local/sbin/ipmi-sensors: authentication type unavailable for attempted privilege level
No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been found to not support IPMI 1.5. Those hitting this issue may see "ipmi 2.0 unavailable" or "connection timeout" errors. This issue can be worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying --driver-type=LAN_2_0. Issue observed on HP Proliant DL 145.
/usr/local/sbin/ipmi-sensors -h 192.168.170.187 -u tc -p xxxx -l USER --quiet-cache --sdr-cache-recreate --interpret-oem-data --output-sensor-state --ignore-not-available-sensors --driver-type=LAN_2_0
On several HP systems (observed on HP Proliant DL380 G7 and HP ProLiant ML310 G5), the SDR lists sensors using inconsistent information. Some analog sensors are listed as discrete sensors or vice versa. This inconsistency, and implementation differences between ipmi-sensors and other IPMI software lead to different outputs. For example, this is one such sensor that was seen in ipmi-sensors:
2 | Power Supply 1 | Power Supply | N/A | N/A | 'Presence detected'
but this same sensor was see in ipmitool as
Power Supply 1 | 120 Watts | nc
In this example, ipmi-sensors did not output a Watts reading but outputs the proper "Presence Detected" state. Ipmitool outputs the correct watts reading, but outputs the invalid non-critical "nc" state.
In FreeIPMI, this problem can be worked around using the ’discretereading’ workaround flag.
/usr/local/sbin/ipmi-sensors -h 192.168.170.187 -u tc -p xxxx -l USER --quiet-cache --sdr-cache-recreate --interpret-oem-data --output-sensor-state --ignore-not-available-sensors --driver-type=LAN_2_0 -W discretereading
/usr/lib64/nagios/plugins/check_ipmi_sensor -H 192.168.170.187 -U tc -P makarna-ye99 -L USER -O "--driver-type=LAN_2_0 -W discretereading"
define command{ command_name check_ipmi_sensor command_line $USER1$/check_ipmi_sensor -O "--driver-type=LAN_2_0 -W discretereading" -H $_HOSTIPMI_IP$ -f $ARG1$ }
????????????????????????????????????????? I set the following in /etc/freeipmi.conf: > > > --- > > > driver-type LAN_2_0> > > ---
smartstart cd sini kaldırmış.
HP Intelligent Provisioning, No More SmartStart https://www.youtube.com/watch?v=pvYuPr9WYXA&feature=youtu.be
https://www.youtube.com/watch?v=07D4e9RLFG4
2 comments:
Hi, really good article. Especially thank for --driver-type=LAN_2_0. This save me a lot of time.
Just one additional question. How do you accomplish that all sensors are in one graph? I have for every sensor separate graph.. I'm using OMD with check_mk and nagios
Hi, thank you. I just use nagiosgraph.
Post a Comment