03.07.2013 Views

Technical Product Specification for Canoe Pass - Preminary - Intel

Technical Product Specification for Canoe Pass - Preminary - Intel

Technical Product Specification for Canoe Pass - Preminary - Intel

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix C: BMC Sensor Tables <strong>Intel</strong> ® Server Board S2600CP and Server System P4000CP TPS<br />

168<br />

Appendix C: BMC Sensor Tables<br />

This appendix lists the sensor identification numbers and in<strong>for</strong>mation about the sensor type,<br />

name, supported thresholds, assertion and de-assertion in<strong>for</strong>mation, and a brief description of<br />

the sensor purpose. See the <strong>Intel</strong>ligent Plat<strong>for</strong>m Management Interface <strong>Specification</strong>, Version<br />

2.0 <strong>for</strong> sensor and event/reading-type table in<strong>for</strong>mation.<br />

Sensor Type Codes<br />

Sensor table given below lists the sensor identification numbers and in<strong>for</strong>mation regarding the<br />

sensor type, name, supported thresholds, assertion and de-assertion in<strong>for</strong>mation, and a brief<br />

description of the sensor purpose. Refer to the <strong>Intel</strong>ligent Plat<strong>for</strong>m Management Interface<br />

<strong>Specification</strong>, Version 2.0 <strong>for</strong> sensor and event/reading-type table in<strong>for</strong>mation.<br />

7. Sensor Type<br />

The sensor type references the values in the Sensor Type Codes table in the <strong>Intel</strong>ligent<br />

Plat<strong>for</strong>m Management Interface <strong>Specification</strong> Second Generation v2.0. It provides a<br />

context to interpret the sensor.<br />

8. Event/Reading Type<br />

The event/reading type references values from the Event/Reading Type Code Ranges<br />

and the Generic Event/Reading Type Code tables in the <strong>Intel</strong>ligent Plat<strong>for</strong>m<br />

Management Interface <strong>Specification</strong> Second Generation v2.0. Digital sensors are<br />

specific type of discrete sensors that only have two states.<br />

9. Event Thresholds/Triggers<br />

The following event thresholds are supported <strong>for</strong> threshold type sensors:<br />

[u,l][nr,c,nc] upper non-recoverable, upper critical, upper non-critical, lower nonrecoverable,<br />

lower critical, lower non-critical uc, lc upper critical, lower critical<br />

Event triggers are supported event-generating offsets <strong>for</strong> discrete type sensors. The<br />

offsets can be found in the Generic Event/Reading Type Code or Sensor Type Code<br />

tables in the <strong>Intel</strong>ligent Plat<strong>for</strong>m Management Interface <strong>Specification</strong> Second Generation<br />

v2.0, depending on whether the sensor event/reading type is generic or a sensorspecific<br />

response.<br />

10. Assertion/Deassertion<br />

Assertion and de-assertion indicators reveal the type of events this sensor generates:<br />

As: Assertion<br />

De: De-assertion<br />

11. Readable Value/Offsets<br />

Readable value indicates the type of value returned <strong>for</strong> threshold and other non-discrete<br />

type sensors.<br />

Readable offsets indicate the offsets <strong>for</strong> discrete sensors that are readable by means of<br />

the Get Sensor Reading command. Unless otherwise indicated, event triggers are<br />

readable. Readable offsets consist of the reading type offsets that do not generate events.<br />

12. Event Data<br />

Event data is the data that is included in an event message generated by the associated<br />

sensor. For threshold-based sensors, these abbreviations are used:<br />

R: Reading value<br />

T: Threshold value<br />

<strong>Intel</strong> Confidential Revision 0.8<br />

<strong>Intel</strong> order number G26942-003

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!