NAT-MCH Users Manual Version 1.16

NAT-MCH – Users Manual
� /usr/local/sbin/openhpid –c /usr/local/etc/openhpi/openhpi.conf
Using the provided configuration file openhpi_nat.conf you will find daemon logging
information on your system in /tmp/openhpi00.log.
As mentioned above the OpenHPI daemon will silently terminate on error conditions. If you
are not able to establish a RMCP connection between the OpenHPI daemon and the MCH
please note following:
• startup time can last up to 1 minute (depending on the number of found resources, i.e.
sensors and FRU data
• check that MCH can be reached over the network:
� ping
• if there is no ping reply please check the MCH’s network configuration or the IP
address and port settings in openhpi.conf
• check that the openhpi daemon is running:
� ps aux | grep openhpi
Once the daemon was started successfully you may start an application to communicate with
the MCH. The OpenHPI package provides some applications, e.g.:
� hpitree
displays found esources,
� hpitop
displays esource information about found esources and
� hpisensors
displays information about found sensors.
You also may use the N.A.T. JAVA GUI to communicate to the MCH and to display the
found esources.
To stop the OpenHPI daemon please enter:
� killall openhpid
Please note that when stopping the OpenHPI daemon in that way open sessions will not be
closed by the daemon. However, the MCH implements a 60 seconds inactivity timeout
condition in its firmware that closes open sessions after this timeout.
Version 1.16 © N.A.T. GmbH 49