intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other
jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Full Dates.......................................................................................................................................48
1
Introduction
This reference guide provides information about Simple Network Management Protocol (SNMP)
Management Information Base (MIB) which are released with the current version of Dell iDRAC8.
Sections in this guide follow MIB groups and provide explanations and definitions for the terms used to
define MIB objects. All essential Simple Network Management Protocol (SNMP) terms are defined in this
guide. Some of the vocabulary may seem complex and unfamiliar to system administrators who are using
SNMP for the first time
What’s New in This Release
This release of Dell iDRAC8 SNMP introduces the following new features:
New enhancement in iDRAC8 with SNMP v3 traps supported.
•Added new trap objects under iDRAC8
– Changes in sub group are:
System Trap Group
*Added new Traps for
RAC Trap
and
System Performance Trap
Updated Trap Group
*Added new Trap for :
Update Trap
Audit Trap Group
*Added new Trap for :
User Tracking Traps
Supported SNMP Versions
iDRAC versionSNMP Alerts / TrapsSNMP Gets
iDRAC7SNMP v1 ,v2,v1,v2,v3
iDRAC8SNMP v1,v2,v3v1,v2,v3
5
Managed Object Used in This Document
The MIB is divided into several major groups. The following table provides information about the MIB
names, name of the agent that uses each MIB and the purpose:
MIB NameAgent / Hardware SupportedPurpose of the MIB
10892.mibServer AdministratorProvides the information about the systems
monitored by Server Administrator
instrumentation software. This is the primary
MIB for PowerEdge systems.
dcs3fru.mibServer AdministratorProvides the information about the system
Field Replaceable Unit (FRU) to SNMP
management applications.
dcstorag.mibServer Administrator Storage
Management
iDRAC-SMIv1.mibiDRAC7 and iDRAC 8Provides information about the SNMP data,
iDRAC-SMIv2.mibiDRAC7 and iDRAC 8Provides information about the SNMP data,
dcs3rmt.mibDell Remote Access controller 5
(DRAC 5)
rac_host.mibRemote access out-of-band
agent
DELL-RAC-MIB.txtChassis Management Controller
(CMC)
DcAsfSrv.mibBaseboard Management
Controller (BMC)
Provides the information about the storage
hardware components and RAID
configurations monitored by Server
Administrator.
and traps, supported by the iDRAC7. This is
for SMv1.
and traps, supported by the iDRAC7. This is
for SMv2.
Provides information about remote access
components monitored by the Server
Administrator Remote Access Service.
Provides information about the components
monitored by the remote access out-ofband software agent.
Provides information about components
monitored by the Chassis Management
Controller for modular chassis.
Provides information about Dell server
Platform Event Traps generated by the
Baseboard Management Controller.
For further details see Release Notes for Management Information Base readme_mibs.txt.
Server Administrator Remote Access MIB
NOTE: This section contains information that is applicable only if the Server Administrator is
installed in the system.
The Server Administrator Remote Access MIB ( filename dcs3rmt.mib ) provides in-band information
about remote access hardware that may be present in your system.
The Server Administrator Remote Access MIB structures its MIB objects into groups of scalar objects or
MIB tables that provide related information. Table below describes each Server Administrator Remote
6
Access MIB group and lists the MIB group number assigned to the MIB group. The Server Administrator
Remote Access MIB groups are identified by the SNMP OID 1.3.6.1.4.1.674.10892.1.<MIB group number>
where <MIB group number> is the MIB group number assigned to the MIB group. See the relevant section
for more information about the MIB objects defined in a MIB group.
Table 1. Server Administrator Remote Access MIB Sections in This Guide
SectionTopicMIB Group Numbers
19Remote Access Group — provides information about
remote access hardware that may be present in your
system and defines variables for administrative users,
SNMP trap destinations, modem configuration for dial-up
networking, dial-in configuration, and dial-out
destinations
1700
Dell Remote Access Controller Out-of-Band MIB
The Dell Remote Access Controller Out-of-Band MIB (filename dellRAC.mib) provides management data
that allows you to monitor the Chassis Management Controller. This MIB also contains information on
RAC legacy alerting. The following table describes each Dell RAC Out-of-Band group and lists the MIB
group number assigned to the MIB group. See the relevant section for more information about the MIB
objects defined in a MIB group.
Table 2. Dell RAC Out-of-Band MIB
SectionTopicsMIB Group Number
25 The Dell RAC Out-of-Band MIB consists of information
for the following groups:
•Product Information
•Chassis Status
•Chassis Power
•CMC Power Information
•CMC PSU Information
•Chassis Alerts
•Legacy Alerting
2
How This Guide Defines Technical Terms
The following table provides information about where to find definitions for technical terms in this
reference guide.
Table 3. Where to Find Definitions for Technical Terms
Type of DefinitionSee
Basic SNMP vocabulary.Introduction
MIB-group-specific variable values. MIB-group-specific MIB
variables contain links to the tables that define these values in the
last section of the section in which these variables are used.
Sections 3, 5, 7, 8, 9, and 11
through 18.
7
Type of DefinitionSee
Systems management terms, acronyms, and commonly managed
components referred to in this reference guide.
Server Administrator-standard data types that specify variable
values in this reference guide.
Glossary available on the Dell
Support web site at dell.com/support/manuals.
Appendix A, Standard Data Type
Definitions.
Basic Terminology
It is important to have a good understanding of the key technical terms used in this guide. This guide
provides definitions for all essential terms used in describing the Server Administrator MIBs. For definitions
on all essential terms and acronyms, see the Glossary available on the Dell Support website at dell.com/
support/manuals.
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. Hotpluggable 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 behaves 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.
Tables
This reference guide contains two types of tables: tables that are used to organize and define variable
values and tables that define MIB objects. Readers must understand the difference between these two
types of tables.
SNMP Tables
Most of the MIB objects defined in this reference guide are organized into SNMP tables. SNMP tables
organize data into two-dimensional structural arrays. In SNMP, objects that have a relationship to other
objects are called columnar objects. Columnar objects are objects used to form lists and tables. When a
MIB group is divided into one or more discrete tables, the word table has a technical meaning. An
8
example is the section of this reference guide entitled Universal Unique Identifier (UUID). The UUID object
has a type and a value that uniquely identifies an object such as a chassis. The table defines all of the
variables that comprise the managed object UUID.
The following table is an example of an SNMP table. The table contains variables that must occur in a
definite sequence. In the example table the defined variables are UUID Chassis Index, UUID Index, UUID
Type, and UUID Value.
These objects comprise the Server Administrator definitions for the UUID.
Table 4. UUID Table
Name
uUIDTable
Object ID 1.3.6.1.4.1.674.10892.1.300.20
Description Defines the UUID table.
Syntax SEQUENCE OF UUIDTableEntry
Access Not accessible
Table 5. UUID Table Entry
Name
uUIDTableEntry
Object ID 1.3.6.1.4.1.674.10892.1.300.20.1
Description Defines the UUID table entry.
Syntax UUIDTableEntry
Access Not accessible
Index
uUIDIndex
,
uUIDchassisIndex
Table 6. UUID Chassis Index
Name
uUIDchassisIndex
Object ID 1.3.6.1.4.1.674.10892.1.300.20.1.1
Description Defines the index (one-based) of this chassis.
Syntax DellObjectRange
Access Read-only
Table 7. UUID Index
Name
uUIDIndex
Object ID 1.3.6.1.4.1.674.10892.1.300.20.1.2
Description Defines the index of the UUID in a specified chassis.
Syntax DellObjectRange
9
Access Read-only
Table 8. UUID Type
Name
Object ID 1.3.6.1.4.1.674.10892.1.300.20.1.3
Description Defines the type of the UUID for this chassis.
Syntax DellUUIDType
Access Read-only
Table 9. UUID Value
Name
Object ID 1.3.6.1.4.1.674.10892.1.300.20.1.4
Description Defines the value of the UUID for this chassis.
Syntax Octet String (SIZE[16])
Access Read-onlyRead-only
uUIDType
uUIDValue
Other Documents You May Need
In addition to this guide, you can access the following guides available on the Dell Support website at
dell.com/support/manuals. On the Manuals page, click SoftwareSystems Management. Click the
appropriate product link on the right-side to access the documents.
•The Server Administrator Messages Reference Guide lists the messages that you can receive on your
systems management console or on your operating system’s event viewer. This guide explains the
text, severity, and cause of each message that the server administrator issues.
•The Server Administrator CIM Reference Guide documents the Common Information Model (CIM)
provider, an extension of the standard management object format (MOF) file. The ServerAdministrator CIM provider documents supported classes of management objects.
•The Glossary provides information on the terms used in this document.
10
2
SNMP Traps
SNMP is frequently used to monitor systems for fault conditions such as temperature violations, hard
drive failures, and so on. Management applications can monitor for these conditions by polling the
appropriate OIDs with the Get command and analyzing the returned data. This method has its drawbacks.
If it is done frequently, significant amounts of network bandwidth can be consumed. If it is done
infrequently, the response to the fault condition may not occur in a timely fashion. SNMP traps avoid
these limitations of the polling method.
An SNMP trap is an asynchronous event indicating that something significant has occurred. This is
analogous to a pager receiving an important message, except that the SNMP trap frequently contains all
the information needed to diagnose a fault.
Two drawbacks to SNMP traps are that they are sent using UDP, which is not a guaranteed delivery
mechanism, and that they are not acknowledged by the receiver.
An SNMP trap message contains the trap’s enterprise OID, the agent IP address, a generic trap ID, the
specific trap ID, a time stamp, and zero or more variable bindings (varbinds). The combination of an
enterprise OID and a specific trap ID uniquely identifies each Server Administrator-defined trap. A varbind
consists of an OID and its value and provides additional information about the trap.
In order for a management system to receive SNMP traps from a managed system, the node must be
configured to send traps to the management system. Trap destination configuration is dependent on the
operating system. When this configuration is done, a management application on the management
system can wait for traps and act on them when received.
For a list of traps supported by the Server Administrator Instrumentation Service, see Instrumentation
Traps. For information on Server Administrator Storage Management traps, see Storage Management
Alert Reference.
For a list of traps supported by the Remote Access Controller, see RAC Traps, BMC Traps and iDRAC7
Traps.
Trap Variables
This section describes the variables both on Traditional and Enhanced varbinds that are sent to the
management console to provide additional information about a trap or alert generated by some event on
your system. The trap variables presented here apply to all Instrumentation and RAC traps. Trap variables
are sent in the order listed and are reserved for use only in traps. When a varbind is created for a trap
variable, a zero is appended to the object ID (OID) to create the OID for the varbind.
The messages associated with each alertMessage varbind are available in the Message Reference Guide
and can be found by matching the alert ID in the MIB to the event ID in the Message Reference Guide.
11
Table 10. Trap Variables
Variable Name
alertSystem
Object ID 1.3.6.1.4.1.674.10892.1.5000.10.1
Description Identifies the system generating the alert.
Syntax DisplayString
Table 11. Table Index OID
Variable Name
alertTableIndexOID
Object ID 1.3.6.1.4.1.674.10892.1.5000.10.2
Description Specifies the object identifier for the index attribute in the table that
contains the object causing the alert. Uniquely identifies the object
causing the alert and can be used to correlate different alerts caused by
the same object.
Syntax
Table 12. Message
Variable Name
OBJECT IDENTIFIER
alertMessage
Object ID 1.3.6.1.4.1.674.10892.1.5000.10.3
Description Describes the alert.
Syntax DisplayString
Table 13. Current Status
Variable Name
alertCurrentStatus
Object ID 1.3.6.1.4.1.674.10892.1.5000.10.4
Description Specifies the current status of the object causing the alert.
Syntax DellStatus
Table 14. Previous Status
Variable Name
alertPreviousStatus
Object ID 1.3.6.1.4.1.674.10892.1.5000.10.5
Description Specifies the previous status of the object causing the alert.
Syntax DellStatus
Table 15. Data
Variable Name
alertData
Object ID 1.3.6.1.4.1.674.10892.1.5000.10.6
Description Provides Server Administrator-defined data related to the alert.
12
Syntax Octet String
The following variables show the Enhanced varbinds:
Table 16. Message ID
Variable Name
Object ID 1.3.6.1.4.1.674.10892.4.5000.10.7
Description Specifies the enhanced message ID for the object generating the alert.
Syntax DisplayString
Table 17. System FQDN
Variable Name
Object ID 1.3.6.1.4.1.674.10892.4.5000.10.8
Description Specifies fully qualified domain name of the system generating the alert.
Syntax DisplayString
Table 18. Service Tag
Variable Name
Object ID 1.3.6.1.4.1.674.10892.4.5000.10.9
Description Specifies the system service tag of the system generating the alert.
Syntax DisplayString
Table 19. Chassis Service Tag
alertMsgID
alertSystemFQDN
alertServiceTag
Variable Name
Object ID 1.3.6.1.4.1.674.10892.4.5000.10.10
Description Specifies the chassis service tag of the system generating the alert.
Syntax DisplayString
alertChassisServiceTag
Understanding The Trap Description
The below table lists in alphabetical order each line item that may appear in the trap description.
Table 20. Trap Description
Description Line ItemExplanation
Action performed was:
<Action>
Action requested was:
<Action>
Specifies the automatic server recovery action that was performed, for
example:
Action performed was: Power cycle
Specifies the user initiated host control action that was requested, for
example:
13
Description Line ItemExplanation
Action requested was: Reboot, shutdown OS first
Additional details:
<Additional details
for the events>
<Additional power
supply status
information>
Battery sensor status:
<status>
Chassis intrusion
state: <Intrusion
state>
Chassis location:
<Name of chassis>
Configuration error
type: <type of
configuration error>
Specifies possible additional details about the specified device, for
example:
Additional details:
Memory device: DIMM_1A Serial number: 11111111
Memory device: DIMM_1B Serial number: 22222222
Specifies any additional power supply information pertaining to the
event, for example:
Power supply input AC is off, Power supply POK (power
OK) signal is not normal, Power supply is turned off
Specifies the status reported by the battery sensor, for example:
Battery sensor status: Predictive failure
Specifies the chassis intrusion state (open or closed), for example:
Chassis intrusion state: Open
Specifies the name of the chassis that generated the message, for
example:
Chassis location: Main System Chassis
Specifies the type of configuration error that occurred, for example:
Configuration error type: Revision mismatch
Current sensor value
(in Amps): <Reading>
Date and time of
action: <Date and
time>
Description:
<Description of event>
Device location:
<Location in chassis>
Discrete current
state: <State>
Discrete temperature
state: <State>
14
Specifies the current sensor value in amps, for example:
Current sensor value: 7.853
Specifies the date and time that an automatic server recovery action was
performed, for example:
Date and time of action: Fri May 30 23:55:44 2003.
Specifies the description of the event that occurred, for example:
Description: Chipset Err: Critical Event sensor, front
panel NMI / diagnostic interrupt was asserted.
Specifies the location of the device in the specified chassis, for example:
Device location: Mem Card A
Specifies the state of the current sensor, for example:
Discrete current state: Good
Specifies the state of the temperature sensor, for example:
Discrete temperature state: Good
Description Line ItemExplanation
Discrete voltage
state: <State>
Fan sensor value:
<Reading>
Log type: <Log type>
Memory device bank
location: <Bank name
in chassis>
Memory device
location: <Device name
in chassis>
Number of devices
required for full
redundancy: <Number>
Specifies the state of the voltage sensor, for example:
Discrete voltage state: Good
Specifies the fan speed in revolutions per minute (RPMs) or On/Off, for
example:
Fan sensor value (in RPM): 2600
Fan sensor value: Off
Specifies the type of hardware log, for example:
Log type: Embedded Server Management (ESM)
Specifies the name of the memory bank in the system that generated
the message, for example:
Memory device bank location: Bank_1
Specifies the location of the memory module in the chassis, for
example:
Memory device location: DIMM_A
Specifies the number of power supply or cooling devices required to
achieve full redundancy, for example:
Number of devices required for full redundancy: 4
Peak value (in Watts):
<Reading>
Possible memory module
event cause: <list of
causes>
Power Supply type:
<type of power supply>
Pre-failure state was:
<State>
Previous redundancy
state was: <State>
Previous state was:
<State>
Processor sensor
status: <status>
Specifies the peak value in Watts, for example:
Peak value (in Watts): 125
Specifies a list of possible causes for the memory module event, for
example:
Possible memory module event cause: Single bit warning
error rate exceeded
Single bit error logging disabled
Specifies the type of power supply, for example:
Power Supply type: VRM
Specifies the status of the previous memory message, for example:
Pre-failure state was: Failed
Specifies the status of the previous redundancy message, for example:
Previous redundancy state was: Lost
Specifies the previous state of the sensor, for example:
Previous state was: OK (Normal)
Specifies the status of the processor sensor, for example:
15
Loading...
+ 33 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.