SNMP Reference Guide

Introduction 21
The following variable names illustrate these conventions:
temperatureProbeLowerCriticalThreshold
coolingUnitIndex
pCIDeviceSpeed
Object Identifier (OID) is the unique number assigned to an object defined in a MIB. An OID is
written as a sequence of subidentifiers in decimal notation. Each OID in this reference guide has a prefix
that identifies the managed objects as belonging to Dellâ„¢: 1.3.6.1.4.1.674. The additional numbers
identify the MIB group and subgroup as well as the table entry number of any variables.
For example, the OID for the temperature probe managed object table is 700.20 and the variable for the
location of the temperature probe (temperatureProbeLocationName) has an OID of 700.20.1.8. The full
OIDs for these items are 1.3.6.1.4.1.674.10892.1.700.20 for the temperatureProbeTable and
1.3.6.1.4.1.674.10892.1.700.20.1.8 for the temperatureProbeLocation. For more information about the
structure of OIDs, see "SNMP MIB OIDs."
Description is a brief explanation of what a particular managed object does.
Syntax defines the data type in which the values of the variable must be expressed. Most variables in this
reference guide use standard data types such as string or boolean. All data types that are unique to server
administrator variables are defined at the end of the section in which they occur. Standard data types are
defined in "Standard Data Type Definitions."
Access specifies whether persons with administrative privileges can read but not modify the value of a
variable (read only) or can both read and modify the value of a variable (read-write).
Frequently Used Terms in Variable Names
The following terms are frequently used in the name of a MIB variable:
Capability refers to the actions an object can perform, or to actions that can be taken by the object.
Hot-pluggable is an example of a capability. If a card is hot-pluggable, it can be replaced while a system is
running. Capability settings refer to the capabilities of the object that the user can select from and
activate if desired. Capability settings allow users of the server administrator to predetermine how an
object will behave under specific conditions.
Settings are the conditions of a manageable object that determine what happens when a certain value is
detected in a component. For example, a user can set the upper critical threshold of a temperature probe
to 75 degrees Celsius. If the probe reaches that temperature, the setting causes an alert to be sent to the
management console. Some settings, when reached, can trigger a system shutdown or other response to
prevent damage to the system.
State refers to the condition of an object that has more than one condition. For example, an object may
be in a "not ready" or in an "enabled" state.
Status refers to the health of an object or how the object is functioning. For example, the status of a
temperature probe that is measuring acceptable temperatures would be reported as normal. When the
probe begins reading temperatures that exceed limits set by the user, it reports a critical status.