X hits on this document

PDF document

February 10, 2006 - page 79 / 238

535 views

0 shares

0 downloads

0 comments

79 / 238

3.13. THE PEF TABLE AND SNMP TRAPS

67

0

1

2-n

Completion code. Standard codes, plus: 80h - parameter not supported Parameter revision. Format is: Bits 0-3 - Oldest revision parameter is backward compatible with Bits 4-7 - Current parameter revision Parameter data. This will not be present if bit 7 of byte 0 of the response is set to 1. The contents of this depends on the particular parameter being fetched, see table 3.36 for the parameters.

Table 3.34: Get PEF Configuration Parameters Command, NetFN S/E (04h), Cmd 13h

Table 3.35 shows the command used to send an acknowledge for a received trap. If the “Alert Ac- knowledge” bit is set in “Destination Type” entry of the LAN Configuration Table (Table 3.16) or in the “ “Destination Info” entry of the Serial Configuration Table (Table 3.17), then the receiver of the trap must send this message to stop the resends.

Request 0-1

2-5

6 7 8 9-11 Response 0

Sequence Number, from the field in the Platform Event Trap (PET) of the trap being acknowledged. Least significant byte first. Local Timestamp, from the field in the PET of the trap being acknowledged. Least significant byte first. Event Source Type, from the field in the PET of the trap being acknowledged Sensor Device, from the field in the PET of the trap being acknowledged Sensor Number, from the field in the PET of the trap being acknowledged Event Data 1-3, from the field in the PET of the trap being acknowledged

Completion Code Table 3.35: PET Acknowledge Command, NetFN S/E (04h), Cmd 17h

3.13.2

The PEF Postpone Timer

TBD - write this.

3.13.3

PEF Configuration

Parameters

The PEF Configuration table has an unusual locking mechanism (although it is usual for IPMI). Parameter zero is a lock. If you set the value to one, it will only succeed if the value is zero. Thus, to lock the table, you set the value to one until it succeeds. You then set it to zero when you are done. This locking mechanism leads to problem if the locker dies while it holds the lock, so you probably need some way to override the lock if this happens. The lock does not actually keep anyone from changing the data, it is simply a common mechanism to mutual exclusion. Note also that the lock has a “commit” mechanism, writing two to the lock will commit the contents if the system supports it. If the system supports rollback, setting the value to zero

Document info
Document views535
Page views535
Page last viewedSun Dec 04 02:31:32 UTC 2016
Pages238
Paragraphs8090
Words85809

Comments