We want to setup IPMI sensor on a Windows server. Server Team informed me the user id and password for this sensor, but it shows "Could not create the sensor IPMI System Health BETA on device" after try to creating the sensor.

The .NET is already ver 4.7.2 on PRTG probe.

What should I further setup on PRTG or on the Winodws Server to be monitored? Thanks.

Daniel


Article Comments

Hi there,

You can test the connection manually by using the "ipmiutil.exe" on the Core Server (or Remote Probe) under "C:\Program Files (x86)\PRTG Network Monitor\Sensor System\":

Ipmiutil.exe health -n IP.AD.DR.ES - U USERNAME -P PASW0RD

Does this work?

Best regards.


Feb, 2019 - Permalink

Dear Dariusz,

Thanks for your reply. I try on the probe with message:

"ipmiutil ver 2.96" "ihealth ver 2.96" "Cannot open an IPMI driver: imbdrv.sys or ipmidrv.sys" "ipmiutil health, cannot open IPMI driver"

Does the probe some file/driver missing? Thanks.

Daniel


Feb, 2019 - Permalink

Dear Dariusz,

It is found if cmd use :

Ipmiutil.exe health -N IP.AD.DR.ES - U USERNAME -P PASW0RD

( i.e. "-n" is changed to "-N" )

It has another message :

ipmiutil ver 2.96

ihealth ver 2.96

Connecting to node IP.AD.DR.ES

ipmilan_open_session error, rv = -3

ipmilan receive from BMC failed

ipmi_open error = -3

ipmiutil health, receive from BMC failed

Thanks.


Feb, 2019 - Permalink

Hi there,

Sorry you are right, there was something with a capital N. Could you try the following command as well, this should output more debug information:

Ipmiutil.exe health -N IP.AD.DR.ES - U USERNAME -P PASW0RD -x

Best regards.


Feb, 2019 - Permalink

Hi,

I try

" Ipmiutil.exe health -N IP.AD.DR.ES - U USERNAME -P PASW0RD -x "

Message:

ipmiutil ver 2.96

ihealth ver 2.96

ipmi_open: driver type =

ipmi_open_lan: fdebug = 1

Opening lan connection to node IP.AD.DR.ES ...

atoip: IP AD DR ES

open_sockfd returned 0, fd=212

Connecting to node IP.AD.DR.ES

calling get_rand(1)

ipmilan_open_session(212,02,testing,02,29) called

GetChanAuth(sock d4, level 2) called

ipmilan_sendto(seq=0,clen=23)

ipmilan_cmd timeout, after request, seq=0 itry=0

ipmilan_cmd timeout, after request, seq=0 itry=1

ipmilan_cmd timeout, after request, seq=0 itry=2

ipmilan_cmd timeout, after request, seq=0 itry=3

_ipmilan_cmd[38]: rv = -3, cc=0 rs_len=205

ipmilan_sendto(seq=0,clen=23)

ipmilan_cmd timeout, after request, seq=0 itry=0

ipmilan_cmd timeout, after request, seq=0 itry=1

ipmilan_cmd timeout, after request, seq=0 itry=2

ipmilan_cmd timeout, after request, seq=0 itry=3

_ipmilan_cmd[38]: rv = -3, cc=0 rs_len=205

GetChanAuth rv = -3, cc=0 rbuf: bf 46 00 91 55 26 cb

ipmilan_open_session error, rv = -3

ipmilan receive from BMC failed

ipmi_open rc = -3 type = lan

Driver type lan, open rc = -3

ipmi_open error = -3

ipmi_close_lan(IP.AD.DR.ES) entry, sockfd=0

ipmi_close_lan(IP.AD.DR.ES) rv=0 sockfd=0

ipmiutil health, receive from BMC failed

Thanks.


Feb, 2019 - Permalink

Hi Daniel,

It seems that IPMI is either not reachable or not available at all:

ipmilan_sendto(seq=0,clen=23)

ipmilan_cmd timeout, after request, seq=0 itry=0

ipmilan_cmd timeout, after request, seq=0 itry=1

ipmilan_cmd timeout, after request, seq=0 itry=2

ipmilan_cmd timeout, after request, seq=0 itry=3

_ipmilan_cmd[38]: rv = -3, cc=0 rs_len=205

ipmilan_sendto(seq=0,clen=23)

ipmilan_cmd timeout, after request, seq=0 itry=0

ipmilan_cmd timeout, after request, seq=0 itry=1

ipmilan_cmd timeout, after request, seq=0 itry=2

ipmilan_cmd timeout, after request, seq=0 itry=3

Best regards.


Feb, 2019 - Permalink