hpbmc(8)

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.

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.

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 Trap: SNMP enterprise-specific trap (if any) Platform: All, Entry-level, Mid-range, High-end

An E0 event may occur on multiple platforms with slightly different fields (event ID 98 is a good example). A set of attributes will be printed for each platform that supports the event.

If the argument is LIST, all registered events for the running platform will be printed as described above. There will not be any multiple events printed in this list.

Finally, if the argument is TABLE, a full list is printed, one line per event, with the pipe symbol "|" as field delimiter. This output is suitable for import into a spreadsheet.

Adds a new event to the Forward Progress Log. The FPL is a circular log (unlike the SEL) so it does not fill up; the oldest entries will be overwritten as necessary. The argument order is given by running the directive without arguments.

Adds a new event to the Forward Progress Log. The arguments are the raw 14 bytes of an FPL body. One source of this is the bytes given by FPLprintraw.

See the SELdecode directive below.

Erase the entire Forward Progress Log.

Print a verbose list of all entries in the Forward Progress Log. All entries start with the logical entry number followed by one of two forms:

• Normal IPMI events list the sensor number in hex, whether it was asserted [+] or deasserted [-], its generic type, a description of the triggering event, and a timestamp.

• Proprietary HP events list the description, a physical location (cabinet, cell number, and CPU number where appropriate), and any additional data for the event. Usually it is followed by a line that seems identical but only contains a timestamp; that belongs with the previous entry.

Like FPLprint , along with the raw data bytes of the entry, starting at the Record Type.

Print capacity, last entry time, last deletion time, and current time.

Print FRU entries that were listed in the SDRR. If the FRU is not installed N/A is printed; otherwise all details provided in the FRU are listed.

The IPMI 2.0 spec allows information strings to be set with this command. Commonly used parameters and the strings they return:

1. System Firmware Revision

2. Operating system type

3. Primary operating system name and revision

4. Current operating system name and revision

Takes the hexadecimal bytes and sends them directly to the target device. Output is printed as a block of hexadecimal bytes, although no length information is explicitly given. The user must know how to interpret the bytes. For example, hpbmc IPMIraw 18 1 is the Get Device ID command.

Returns the apparent bus address of the Open IPMI device; cannot be used with the -b option. This may reflect a wake up value (typically hex 20) and might not be an actual assigned address (as with an ATCA chassis). See the next command.

Sets the apparent bus address of the Open IPMI device; cannot be used with the -b option. This value is persistent until changed or the system is rebooted. newaddr is an eight-bit IPMB address in hexadecimal (i.e., A2). If it is missing or set to FF, hpbmc will probe all addresses for the one that matches actually hardware assignment (as with an ATCA chassis).

hpbmc embodies full textual descriptions and SNMP trap information for many IPMI SEL events. This directive prints all that information in the form of a MIB. You can typically find this MIB in /usr/share/snmp/mibs/HPIPFTRAP-MIB.txt. It should be created by the hpmgmtbase install scripts so MIBprint is not normally used.

Print the name of the partition on which the command is run. It cannot be run remotely over RMCP. When given an optional argument, an attempt is made to rename the partition.

On entry-level boxes, print the "parts": installed CPUs, installed IO cards, and RAM population. On partitioned systems it adds partition names, cell assignments, and cell-to-chassis associations.

Without the optional modifier, display the current chassis power state. The modifier can change the current state. On HP Integrity servers this can only be used with -b 46run locally via IPMI, or directly to the MP card with RMCP.

The Management Processor (MP) card on HP Integrity Servers supports RMCP operation for current firmware revisions. On entry-level systems (non- cellular) RMCP must first be enabled via an interactive session to the MP. The default password is null (no password), and can only be changed via this directive. Mid-range and high-end servers (cellular) can set the password via this directive or the interactive MP session. See the ENVIRONMENT VARIABLES section for password usage.

Print a verbose list of all entries in the Sensor Data Record Repository. An entry is summarized on a single line, followed by a type description and pertinent details. Not all of the entries are useful to the casual observer. The following types may be seen:

C Sensor

Compact sensor that returns state information

F Sensor

Full sensor that can return analog readings

FRU

Field Replaceable Unit

Ent Assoc

Entity association, a logical grouping of lower-level entities

A Prop

Association property, an HP-proprietary type (cellular only)

D Prop

Data property, an HP-proprietary type (cellular only)

C Prop

Control property, an HP-proprietary type (cellular only)

Like SDRprint, along with the raw data bytes of the entry, starting at the Record Type.

Adds a new event to the System Event Log. The SEL has a finite length and when full will not accept any new events. This directive may cause generate SNMP or WBEM network activity if agents are running. The details of the arguments are beyond the scope of this document, however the results of SELprintraw may be "cut-and-pasted."

Adds a new event to the System Event Log. The arguments are the raw 14 bytes of an SEL body. One source of this is the bytes given by SELprintraw.

MP cards provide a login and command line interface to manage an Integrity server. One of those commands lists the SEL contents. Those events are sometimes listed (based on firmware revision or settings) as two large hexadecimal numbers which need to be decoded. Use those numbers as the two arguments to the SELdecode directive to get a better description of the event. It is best to run this command on the same platform as that which generated the event; sometimes additional SDRR data is needed for a full decode.

Erase the entire System Event Log.

Print a verbose list of all entries in the System Event Log. See the description under FPLprint for more details.

Like SELprint, along with the raw data bytes of the entry, starting at the Record Type.

Print capacity, last entry time, last deletion time, and current time. The SEL is not a circular log, and will not take more events when it is full. The HP IPMI daemon, hpipmid monitors this condition and will erase the SEL as needed.

Print the last entry in the SEL, then go into a two-second polling loop waiting for new entries. Most useful with SELappend or truly buggy hardware :-)

Lists all sensors and the current reading of each. If number is given, list only that sensor (which can be obtained from SDRprint). Note that sensor number may not be a truly unique reference if multiple LUNs are available.

The IPMI 2.0 spec allows information strings to be set with this command. Commonly used parameters are shown under the GetSystemInfoParameter directive.

The c-Class blade enclosure has a monitoring processor called the Onboard Administrator (OA). The OA presents a web interface that includes summary data about the OS running on each blade. This directive populates that information. It is typically run by startup scripts and does not need to be invoked by the user.

Print machine identification and firmware revisions. On cellular platforms, partition and cell configuration is added.

Given 16 hexadecimal bytes, this directive prints the synthesized text message for a SEL entry comprised of these bytes. This directive is useful only to developers and deep IPMI spec geeks.