CHAPTER 3. IPMI INTERFACES
Table 3.36: PEF Configuration Parameters
Parameter Alert Strings (some parts are volatile)
Description Some actions require alert strings for paging an operator. This table holds the actual alert strings. This table is indexed by the alert policy table (table 3.38) either directly if bit 7 of byte 3 of an alert policy table entry is set to 0, or indirectly through parameter 12 of this table if that bit is one. The meanings of the values in this table are dependent on the alert type and channel. For dial paging, this string will have a carraige return automatically appended to the string. For TAP paging, this string corresonds to ’Field 2’, the pager message. Note that TAP only supports 7-bit ASCII and the BMC will zero the high bit when doing TAP paging.
bits 0-6 - The set selector, the array index of which alert string to set. Entry 0h is volatile and used by the Alert Immediate command as described in section 3.13.5. Entries 1h-7h are non-volatile. All other entries are reserved. bit 7 - reserved byte 1 - Block selector. The strings may be much larger than can be set in a single message. This selects which block to write, in 16-byte increments. So, a 0 here is the first 16 bytes, a 1 is the second 16 bytes, and so on. byte 2-n - The bytes to write into the specific block If this is less byte 0
Parameters 96-127 are allowed for OEM use. All other parameters are reserved.
The PEF table is read and written as part of the PEF Configuration table, parameter 6, but the contents are documented separately in table 3.37. When an event comes in, it is compared against each filter in order. If a match occurs on multiple filters, then the highest priority action is done and the rest except for alerts are ignored. After the operation is completed, any alert operations are done by scanning the alert policy table in order. The order of the alert policy table defines the priority of the different alerts.