Intel MPCMM0001 manual HealthEvents Queries for All Sensors on a Location, No Active Events

Health Events

11.3.2HealthEvents Queries for All Sensors on a Location

Executing a healthevents query on the “cmm” location in the CLI without a target specified

(cmmget -l cmm -d healthevents) returns all the healthevents for all CMM sensors in a concatenated string. This includes all BIST, LAN, Telco Alarm, Voltage, and Temp sensors on the CMM. This ability to retrieve all healthevents on a location also applies to the chassis, bladeN, FantrayN and PemN* locations.

11.3.3No Active Events

When a healthevents query is executed in the CLI on a target that doesn’t have active events a string will be returned that is a single line string with no timestamp or severity. Only this string will be returned and won’t be concatenated with any other strings. For example, doing a healthevents query from the CLI of a location or target that doesn’t have any active healthevents will return the following string:

“[Target] has no problems.” - i.e., “cmm has no problems” or “Brd Temp has no problems”

Executing a healthevents query through SNMP on a target with no active events returns different values than the CLI does. When a healthevents query is executed in SNMP on a location or a target (i.e., in SNMP, the cmmHealthEvents object or cmmSensorHealthEvents object) that has no active events, the value returned is a zero length string.

Note: Attempting to execute a healthevents query on the “FRU” target will return a “CLI Invalid Data Item Error.” string since “FRU” is not a sensor. This also applies to LED targets and FeedN targets.

11.3.4Not Present or Non-IPMI Locations

Doing a healthevents query of a blade or powersupply, or a target on a blade or powersupply, that is not present or non-IPMI compliant will return one of the following:

“BPM Blade Not Present.” - if querying an empty blade slot.

“BPM Non IPMI Blade.” - if querying a blade that is present but doesn’t support IPMI.

11.4List of Possible Health Event Strings

The following tables list strings, codes, and severities for sensor events generated on cmm1 (cmm in left slot), cmm2 (cmm in right slot), chassis, fantrays, PEM1 (PEM on left when looking from front of chassis) and PEM2 (PEM on right when looking from front of chassis). All listed healthevents are logged in a SEL entry, sent out as an SNMP Trap, and show up in a healthevents query while the event is active. OK Health Events are displayed in healthevents queries for a limited time when they are asserted.

For each event, the event code that is returned with each event in SNMP is listed. SNMP traps sent from CMM include the event code with each trap. Users can search for and customize their SNMP applications to use the event code to search for and perform actions on an event instead of needing to use the entire event string.

The event codes below can also be used with the eventaction dataitem to trigger scripts based on when individual events occur. Eventaction uses the base-10 version of the below hexadecimal codes. For more information on eventaction scripting refer to Section 18, “CMM Scripting” on page 164.

108MPCMM0001 Chassis Management Module Software Technical Product Specification