HP Integrity Superdome SX1000 HP Management Base Installation and User's Guide - Page 21

hpbmc(8) NAME hpbmc -- Manage the IPMI BMC on HP Servers . Synopsis /sbin/hpbmc [-b busaddr ] [-d path] [directive] Description hpbmc is a utility for performing action(s) on a Baseboard Management Controller (BMC). hpbmc was originally designed for HP Integrity Servers using the Open IPMI driver. hpbmc may work against other platforms if a BMC is available via a network connection (RMCP). If the optional directive is missing, the Summary output is printed. -b busaddr If the target BMC supports the IPMI Send Message command, all requests will be directed to this IPMB bus address "behind" the BMC. It needs to be an eight-bit hex number (i.e., A2). This bridging also works over RMCP sessions. -d path Override the default device file path for the target BMC. All commands are directed to this device. See FILES and ENVIRONMENT for details. Directives AssetTag {new tag value} Change the Product Area Asset Tag recorded in the IPMI System FRU. This change is non-volatile and will survive a power cycle. This directive is unsupported on rx7620, rx8620, SD16A, SD32A, and SD64A platforms, and any HPVM guest. BMCtimesync Sets the BMC time (used for timestamping entries in the FPL and SEL) to the current system time. See FPLstatus or SELstatus for the current BMC time. EventLookup (Integrity only) Takes a single argument as an event index and prints out a textual description. These events may be found in both the FPL and SEL of Integrity servers. Event types come in two variants: classic IPMI events of type 0x02 and HP OEM events of type 0xE0. If the argument is a "triplet" of the form "XX:YY:ZZ" (including colons) it is treated as three hex bytes denoting the sensor type, event read type (with direction bit), and offset of a type 2 event. Type 2 events are found exclusively in the FPL and SEL of entry level (non-partitioned) Integrity servers. The "triplet" form is documented in the appendix of most entry-level "Operations and Maintenance" manuals. If the argument is a single number, it is treated as an event type E0 "Event ID". Type E0 events are typically found in the SEL of midrange and high-end (partitioned) Integrity servers, and less often in the SEL of entry level servers. The FPL of entry level servers may have many E0 events. One line per attribute is printed; some lines are much longer than 80 characters. Type XX Event Id YY: Summary Desc: Longer description of the event Cause: Another way to look at the event Action: Sometimes corrective step(s) are prescribed Severity: one of six levels 21