Asus ASMB4-SOL PLUS User Manual download pdf (Page 6)

DELL.COM/PowerSolutions

Reprinted from

Dell Power Solutions,

or as a cron job at five-minute intervals to update the LCD with the latest

load values. For example, if the load average is 0.09, then the server

would display “LoadAvg 0.09” on its LCD.

This script incorporates two raw commands based on the “Set System

Info Parameters” row in the “BMC Device and Messaging Commands”

section of Table G-1 of the IPMI 2.0 specification:

ipmitool raw 0x6 0x58 193 0 0 length

ASCII_hex_values

ipmitool raw 0x6 0x58 194 0

The first command sets the LCD text, and the second enables the BMC

to show this text instead of the default text. In these commands, 0x6 is

the network function for “Set System Info Parameters” and 0x58 is the

command value, 193 is the data header specifying the text assignment,

194 specifies which string to show on the LCD, the first 0 after 193 speci-

fies which chunk of 16 bytes of text is being edited, the second 0 after 193

specifies the type of text encoding (in this case, ASCII), length specifies

the number of characters shown on the LCD, and ASCII_hex_values

is the hexadecimal values of the ASCII characters to be shown on the LCD

(which is equal to the length value).

Generating platform event messages

Platform event message commands serve as requests for the BMC to

process the event data that a command contains. This data is typically

stored in the system event log. Depending on the implementation, the

data may also go to the event message buffer and be processed by a

Platform Event Filter.

Based on these events, administrators may want to write monitoring

scripts to help them counter system failures and take appropriate action.

To help test system monitoring scripts, they may also need to generate

test event messages, which they can do using raw commands.

The format for generating a platform event message is as follows:

ipmitool -I lan -H ipaddress -U username raw

netfn cmd evmrev sensortype sensorid

eventdir/eventtype eventdata

In this format, evmrev is the one-byte event message revision,

which for IPMI 2.0 would be 04h. The sensortype element is the

one-byte event class or type of sensor that generates the event mes-

sage, and the sensorid element is the one-byte unique number rep-

resenting the sensor within the management controller. The eventdir/

eventtype element combines one bit indicating the transition direc-

tion (0 for an assertion event, 1 for a de-assertion event) with seven

bits indicating the type of threshold crossing or state transition that

produced the event (encoded using the event/reading type code).

Finally, the eventdata element consists of one to three bytes

containing the sensor-specific offset from Table 42-3 of the IPMI 2.0

specification, which is based on the class of the event type for the

sensor (threshold, discrete, or OEM).

For example, the command to generate a “processor disabled” event

is as follows:

ipmitool -I lanplus -H ipaddress -U username raw

0x04 0x02 0x04 0x07 0x61 0x6F 0x08 00 00

Appendix G of the IPMI 2.0 specification lists the command number

assignments, which include “Platform Event (a.k.a. ‘Event Message’)”

listed in the “Event Commands” section. This table also denotes the

network function as “Sensor/Event.” The “processor disabled” raw com-

mand was generated as follows:

• 0x04 (netfn): Table 5-1 of the IPMI 2.0 specification lists 04h as

the command/request code for “Sensor/Event” (with 05h being a

response).

• 0x02 (cmd): Appendix G of the IPMI 2.0 specification lists the

command value for “Platform Event (a.k.a. ‘Event Message’)” in the

“Event Commands” section as 02h.

• 0x04 (evmrev): As noted, the event message revision in IPMI 2.0

is 04h.

• 0x07 (sensortype): Table 42-3 of the IPMI 2.0 specification lists

the sensor-type command for “Processor” as 07h.

• 0x61 (sensorid): The sensor ID value for the processor can be

obtained using the sensor command with the -v option and search-

ing for “Processor/CPU.”

• 0x6F (eventdir/eventtype): Table 29-5 of the IPMI 2.0 speci-

fication lists the event direction for an assertion event as 0, and Table

42-1 lists the event type for a sensor-specific event (such as “processor

disabled”) as 6Fh. Combining the event direction, 0h (0), with the

event type, 6Fh (1101111), produces a final binary value of 01101111,

which is equivalent to 0x6F.

• 0x08 00 00 (eventdata): Table 42-3 of the IPMI 2.0 specifica-

tion lists the sensor-specific offset for “processor disabled” as 08h.

The second two bytes are left blank.

“

When combined with the guidelines

in the IPMI 2.0 specification and the

BMCs of Dell PowerEdge servers,

IPMItool can become an indispensable

tool in enterprise data centers.

”

1 2 3 4 5 6 7

Comments to this Manuals

No comments

Asus ASMB4-SOL PLUS User Manual Page 6

Comments to this Manuals

Related products and manuals for Software Asus ASMB4-SOL PLUS