openhpi(7) [debian man page]
openhpi(7) OpenHPI openhpi(7) NAME
openhpi - an implementation of the SA Forum's Hardware Platform Interface DESCRIPTION
OpenHPI is an implementation of the SA Forum's Hardware Platform Interface, which provides a standard C library interface to manage, monitor, and control hardware (both local and remote). OpenHPI 2.x implements the HPI B.01.01 specification. The OpenHPI client library (libopenhpi) provides all the connection functionality needed by the client application to connect to the OpenHPI daemon running on the local or remote server. ENVIRONMENTAL VARIABLES
Some of OpenHPI's functioning can be changed by setting environment variables. This documents all client environmental settings. OPENHPI_DAEMON_HOST=URL URL for the host running the daemon. This can be "localhost" (default) if the daemon is running on the local host or an ip address. OPENHPI_DAEMON_PORT=PORT_NUMBER The port number the host is listening on for clent connections. Default port is 4743. HARDWARE SUPPORT
OpenHPI provides a number of plugins that talk to different hardware types. The following is a list of tested plugins in OpenHPI 2.x. ipmi An IPMI plugin that can talk locally (via smi interface and OpenIPMI device driver) or remotely (via IPMI over LAN). It supports IPMI 1.5 for standard rackmount servers, and some of IPMI 2.0 for support of ATCA chassis. IPMI plugin depends on libOpenIPMI version 1.4.x. ipmidirect An IPMI plugin designed specifically for ATCA chassis. It implements IPMI commands directly in the plugin. snmp_bc An SNMP based plugin that can communicate with IBM BladeCenter, as well as IBM xSeries servers with RSA 1 adapters. SNMP_BC plugin depends on net-snmp > 5.0.7. sysfs Current status?? watchdog Current status?? OTHER DOCUMENTATION
The definitive guide to HPI is the SA Forum specification at http://saforum.org. More info on OpenHPI can be found at our webpage (http://openhpi.org). SEE ALSO
The following man pages may also be of interest openhpid The openhpi daemon, providing OpenHPI data as a system service. AUTHORS
Authors of this man page: Sean Dague (http://dague.net/sean) Renier Morales (renier@openhpi.org) 2.14.1 2009-11-23 openhpi(7)
Check Out this Related Man Page
ohhandler(1) OpenHPI ohhandler(1) NAME
ohhandler - An openhpi sample application that uses the openhpi additional interfaces to control openhpi configuration. That is plugins can be loaded, plugin instances (handlers) created, unloaded or their configuration displayed. SYNOPSIS
ohhandler [-D nn] [-N host[:port]] [-C <cfgfile>] [-X] command <specific arguments> ohhandler [--domain nn] [--host=host[:port]] [--cfgfile=file] [--debug] command <specific arguments> ohhandler [-D nn] [-x] list ohhandler [-D nn] [-x] info <handler-id> ohhandler [-D nn] [-x] destroy <handler-id> ohhandler [-D nn] [-x] getnext <handler-id> ohhandler [-D nn] [-x] find <resource-id> ohhandler [-D nn] [-x] retry <handler-id> ohhandler [-D nn] [-x] create plugin <plugin-name> <configuration-parameters> DESCRIPTION
ohhandler list will display a list of all plugin instances (handlers) currently defined in the openhpi daemon for the specified domain. Part of the output is the handler-id that can be used in subsequent commands. ohhandler info will display specific info for the handler with the specified id. This information includes all configuration parameters of the handler as specified in the openhpi.conf file or as dynamically defined during a "ohhandler create" call. ohhandler destroy will unload the specified handler and delete all its configuration information. ohhandler getnext will allows to walk through all hanlers currently defined in the openhpi daemon for the specified domain. ohhandler find will find the handler that is managing the specified resource. ohhandler retry allows to try again to load and initialize the specified handler. ohhandler create allows to dynamically create a new handler with configuration parameters like they are specified in the openhpi.conf file. - The type of plugin is specified with the keyword plugin - Configuration parameters should follow as name value pairs - Complex strings like entity paths must be enclosed with "" Example: ohhandler create plugin libsimulator entity_root "{SYSTEM_CHASSIS,1}" name sim If no domain or host is selected, ohhandler uses the default domain as specified in the openhpiclient.conf file. OPTIONS
Help Options: -h, --help Show help options Application Options: -D nn, --domain=nn Select domain id nn -X, --debug Display debug messages -N "host[:port]", --host="host[:port]" Open session to the domain served by the daemon at the specified URL (host:port). This option overrides the OPENHPI_DAEMON_HOST and OPENHPI_DAEMON_PORT environment variables. If host contains ':' (for example IPv6 address) then enclose it in square brackets. For example: "[::1]" or "[::1]:4743". -C "file", --cfgfile="file" Use passed file as client configuration file. This option overrides the OPENHPICLIENT_CONf environment variable. SEE ALSO
hpi_shell hpialarms hpifan hpipower hpithres hpidomain hpigensimdata hpireset hpitop hpiel hpiiinv hpisensor hpitree hpievents hpionIBMblade hpisettime hpiwdt hpixml ohdomainlist ohparam AUTHORS
Authors of this man page: Ulrich Kleber (ulikleber@users.sourceforge.net) Anton Pak (avpak@users.sourceforge.net) 3.2.1 2011-09-20 ohhandler(1)