Hi there,

We have about 650 physical Fujitsu servers with iRMC s4. I would like to use a combination of SNMP and IPMI for monitoring of said servers.

Currently snmp is working as intended, but IPMI is giving me a imeout (5000 ms) every time i try to create the sensor.

The device is being created on the iRMC ip and i have made sure that .net is up to date in my test environment. Our firewall is not blocking traffic port 623.

I have no problems connecting to a server with IPMIVIEW64 from our PRTG test server.

Have anybody experienced something similar or is there some log that could perhaps help me on my way?

Best Regards

Simon Munk

Article Comments

Dear Simon

For further analysis, please open a command prompt and go to

C:\Program Files (x86)\PRTG Network Monitor\Sensor System

Please run the sensor manually. Please replace the -user, -pw and -IP content accordingly.

What happens when you run this command?

PRTG_IPMI_Sensor -user="xxx" -pw="xxx" -IP="xxx"


Nov, 2015 - Permalink

Hi Again,

If i run the commands, i get the result below.

C:\Program Files (x86)\PRTG Network Monitor\Sensor System>PRTG_IPMI_Sensor -user="admin" -pw="admin" -ip="10.x.x.x"
<prtg>
	<Item>Temperature</Item>
	<Item>Voltage</Item>
	<Item>Fan</Item>
</prtg>

Best Regards

Simon Munk


Nov, 2015 - Permalink

Hi Again,

When i choose a Group it seems lige i get some results.

C:\Program Files (x86)\PRTG Network Monitor\Sensor System>PRTG_IPMI_Sensor -user="admin" -pw="admin" -ip="10.x.x.x" -group="Fan"
<prtg><Result><Channel>FAN1 SYS</Channel><Value>1200</Value><CustomUnit>RPM</Cus
tomUnit><Float>1</Float></Result><Result><Channel>FAN2 SYS</Channel><Value>1140<
/Value><CustomUnit>RPM</CustomUnit><Float>1</Float></Result><Result><Channel>FAN
3 SYS</Channel><Value>1080</Value><CustomUnit>RPM</CustomUnit><Float>1</Float></
Result><Result><Channel>FAN4 SYS</Channel><Value>1080</Value><CustomUnit>RPM</Cu
stomUnit><Float>1</Float></Result><Result><Channel>FAN PSU</Channel><Value>0</Va
lue><CustomUnit>Cannot</CustomUnit><Float>1</Float></Result><Result><Channel>FAN
 PSU1</Channel><Value>0</Value><CustomUnit>Cannot</CustomUnit><Float>1</Float></
Result><Result><Channel>FAN PSU2</Channel><Value>2160</Value><CustomUnit>RPM</Cu
stomUnit><Float>1</Float></Result></prtg>

Best Regards

Simon Munk


Nov, 2015 - Permalink

Dear Simon

How long does it take the sensor (started from the console) to complete its action?


Nov, 2015 - Permalink

Hi,

It takes about 7-8 seconds before i get a timeout error in the PRTG Console, and it takes about 15-16 seconds to get the temperature results in CMD.

Best Regards

Simon Munk


Nov, 2015 - Permalink

Dear Simon

The metascan timeout is set to 5 seconds and cannot be increased, this is why the sensor creation fails.

You could copy the PRTG_IPMI_Senso.exe file into \Custom Sensors\EXEXML and create an Exe/Script Advanced sensor. With manually set parameters you can still use the sensor as it provides an output when you run it from the command prompt.


Nov, 2015 - Permalink

After three years, still no way to increase that 5 second initial scan timeout?

I don't think it would harm anybody to wait for 30 secs when adding the IPMI sensor. I think it's still better to wait a little than forcing to users to manually reconfigure a perfectly working sensor just because of a hardcoded timeout value.


Jun, 2018 - Permalink

Metacan timeouts (the timeout used on auto-discovery) is quite short in order to complete an auto-discovery in a foreseeable time. The rather aggressive timeout can result in some sensors not created, but delaying any device discovery which could have an IPMI sensor by additional 25 seconds does not scale well. For example if 150 devices are included, the additional auto-discovery duration would be some hour.


Jun, 2018 - Permalink