CME-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
234
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
234 total| Object Name |
|---|
ibm OBJECT IDENTIFIER .1.3.6.1.4.1.2 |
IMPORTSRepresents an IPv6 network address. Since MIB browsers
may require different formats, the address is
expected to be the 16 byte address in network-byte order,
and shortened formats such as 0::0 are not accepted in SET
operations. Two common examples are:
The NetSNMP command line will accept SET requests like:
snmpset -v1 -cprivate <host> s 2001:00:00:00:FFFF:CCC4:BBB2:AAA6
Other MIB browsers may require the SET request value to be formatted as:
# 0x20 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0xFF 0xFF 0xCC 0xC4 0xBB 0xB2 0xAA 0xA6 OCTET STRING .1.3.6.1.4.1.2 |
ibmAgents OBJECT IDENTIFIER .1.3.6.1.4.1.2.3 |
netfinitySupportProcessorAgent OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51 |
bladeCenterSnmpMIB OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2 |
monitors OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2 |
temperature OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.1 |
internalTemp OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.1.1 |
cmmTempThis field is deprecated. The return value of this field is the same as rearLEDCardTemp.
Chassis management module temperature in degrees centigrade(C).
An octet string expressed as 'sddd.dd Centigrade' where:
s is the sign ('-' for negative or blank space for positive)
d is a decimal digit or blank space for leading zeroes.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.1.2 |
ambientTemp OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.1.5 |
rearLEDCardTempAvgThe average rear LED card temperature in degrees centigrade(C).
This is surrounding temperature where the system is installed.
An octet string expressed as 'sddd.dd Centigrade' where:
s is the sign ('-' for negative or blank space for positive)
d is a decimal digit or blank space for a leading zero.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.5.1 |
rearLEDCardTempMinThe minimum rear LED card temperature in degrees centigrade(C).
This is surrounding temperature where the system is installed.
An octet string expressed as 'sddd.dd Centigrade' where:
s is the sign ('-' for negative or blank space for positive)
d is a decimal digit or blank space for a leading zero.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.5.2 |
rearLEDCardTempMaxThe maximum rear LED card temperature in degrees centigrade(C).
This is surrounding temperature where the system is installed.
An octet string expressed as 'sddd.dd Centigrade' where:
s is the sign ('-' for negative or blank space for positive)
d is a decimal digit or blank space for a leading zero.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.5.3 |
monitorTemp OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.1.9 |
hotAirRecircMonitoringIf this is enabled, the management module will monitor for Hot Air
Recirculation by detecting non-uniform air temperature(s) that may
be entering the front of the chassis.
This could be due to either localized hot or cold air reaching at
least one of the node's or chassis temperature sensors and it
exceeding the acceptable range. When enabled, this monitor will
generate an event and be transmitted to any configured remote
alert recipient.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.1.9.3 |
hotAirRecircTempDeltaThreshThis object is used to read or change the temperature delta threshold for
Hot Air Recirculation detection. Values are enforced to be in the inclusive
range between 5.00C and 9.00C and are specified as hundreths of a degree. For
example, a value of 659 would equate to a threshold of 6.59 degrees C.rw INTEGER .1.3.6.1.4.1.2.3.51.2.2.1.9.5 |
hotAirRecircStatusTableTable of hot air recirculation status information. SEQUENCE OF HotAirRecircStatusEntry .1.3.6.1.4.1.2.3.51.2.2.1.9.7 |
hotAirRecircStatusEntryHot air recirculation status entry HotAirRecircStatusEntry .1.3.6.1.4.1.2.3.51.2.2.1.9.7.1 |
hotAirRecircStatusTopologyPathThe unique identifier for a component in this table. The chassis and each
installed component is represented by a hardware topology tree, where
each node in the tree represents a component. The path to a particular
component consists of one or more <component>,<instance> pairs, where
each successive pair is a child of the previous parent pair.
As an example, the root of the tree is the chassis and is represented
by the pair 'CHASSIS, 1'. This pair indicates the first instance of
the chassis. If a blade is inserted in slot 4 of the chassis, its
topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the
components in the chassis can be determined along with their relative
hierarchy to each other.
Note that this TP is preceded by a single octet that specifies the TP length.
This is required since this table is indexed with two indices and, therefore,
the TP length must be explicitly provided.
This component firmware table is indexed by this unique topology
path and the numeric designations for the components are:
CHASSIS, 0x01 Chassis
MM, 0x02 Management Module
BLADE, 0x03 Main system board of a blade
POWER, 0x04 Power Supply, Power Module, etc
COOLING, 0x05 Fan, blower, or other cooling device
IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge
MEDIA, 0x07 Media device
PROCESSOR, 0x08 Any processor, processor module, etc
STORAGE, 0x09 Any type of storage device
EXPANSION, 0x0A Expansion Card (not covered by more specific type)
MEMORY, 0x0B Any memory device, module, etc
MFRU, 0x0C Managed FRU Device
PANEL, 0x0D Any sort of panel device, such as a front panel
BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc
CARD_EXPANSION, 0x0F Expansion card, ie. daughter card
CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card
INTERPOSER, 0x11 Interposer device
CLOCK, 0x12 Clock card
MUX, 0x13 Mulitplexer card
ADDIN, 0x14 cKVM card & other addin cards
STORAGE_MODULE, 0x15 Container of one or more Storage Devices
SYS_EXPANSION_CARD, 0x16 Management card
BATTERY, 0x17 A single battery
BATTERY_MODULE, 0x18 Container of one or more batteries
REAR_LED, 0x19 Rear LED card
MEMORY_BANK, 0x1A Memory banks
AIR_FILTER, 0x1B Filter mechanism (bezel)
SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports
PARENT, 0x1D Reference to parent for multi-parent support
PHY_PORT, 0x1E Physical port
IO_EXPANDER, 0x1F RAID card
CABLE, 0x20 Cable/Interconnect
FAN_MUX 0x29 Fan multiplexer card
PCI_EXPRESS, 0x32 PCI express card on (PEN)
FLASH_DIMM, 0x33 Used for SPD devices that matches the silkscreen of the DIMM slot
RACK, 0x50 Rack
PLATFORM, 0x51 Generic Platform like rack mounted server/appliance
DATAPLEX, 0x52 DataPlex
OTHER, 0x53 Other unknown etc.
PERIPHERAL_MODULE, 0x54
SYSTEM_BOARD, 0x55 System board
PROCESSOR_MODULE, 0x56
BACK_PANEL, 0x57
POWER_SYSTEM_BOARD, 0x58
STORAGE_BACKPLANE, 0x59 Drive back plane
PROC_BOARD, 0x5A Holds 1 or more processors
POWER_DI, 0x5B Power mgt / power distribution board
CHASSIS_BACK_PANEL, 0x5C
SUB_CHASSIS, 0x5D
OTHER_CHASSIS_BOARD, 0x5E
DEVICE_MODULE, 0x5F
REMOTE_DEVICE, 0x60 Remote mgt communication device
EXTERNAL_ENVIRONMENT, 0x61 Such as external temp sensor for outside box temps
PROC_MEMORY_MODULE, 0x62 Processors and memory on same modulero OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.9.7.1.2 |
hotAirRecircStatusIndexEach component may have one or more sensor associated with it, this index object
identifies the particular instance.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.1.9.7.1.3 |
hotAirRecircStatusNameThe name of the component as a null terminated stringro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.9.7.1.4 |
hotAirRecircStatusSensorLabelThe text label of the sensor as a null terminated stringro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.9.7.1.5 |
hotAirRecircStatusSensorReadingAmbient temperature reading for this component in degrees centigrade(C).
The string is formatted as 'dd.dd Centigrade'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.9.7.1.6 |
hotAirRecircStatusExceededIndicates whether this component has exceeded the threshold
of the acceptable temperature being monitored for hot air recirculation.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.1.9.7.1.7 |
chassisFans OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.3 |
chassisFansTableTable of chassis Fan information. SEQUENCE OF ChassisFansEntry .1.3.6.1.4.1.2.3.51.2.2.3.50 |
chassisFansEntryChassis Fan information entry ChassisFansEntry .1.3.6.1.4.1.2.3.51.2.2.3.50.1 |
chassisFanIndexChassis Fans table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.3.50.1.1 |
chassisFanIdThe numeric chassis fan ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.50.1.2 |
chassisFanSpeedChassis fan speed expressed in percent(%) of maximum RPM.
An octet string expressed as 'ddd% of maximum' where:
d is a decimal digit or blank space for a leading zero.
If the chassis fan is determined not to be running or
the chassis fan speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.50.1.3 |
chassisFanStateThe health state for the chassis fan.
Note that the other UIs may use slightly different terminology for the
three health state values, as such:
WEB - Normal, Attention, Critical
CLI - OK, Non-critical, Criticalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.50.1.4 |
chassisFanSpeedRPMChassis fan speed expressed in RPM.
If the chassis fan is determined not to be running or
the chassis fan speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.50.1.5 |
chassisFanControllerStateThe controller health state for the chassis fan.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.50.1.6 |
chassisFanCoolingZoneThe cooling zone for the chassis fan.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.50.1.7 |
chassisCoolingZoneTableTable of chassis cooling zone information. SEQUENCE OF ChassisCoolingZoneEntry .1.3.6.1.4.1.2.3.51.2.2.3.51 |
chassisCoolingZoneEntryChassis cooling zone information entry ChassisCoolingZoneEntry .1.3.6.1.4.1.2.3.51.2.2.3.51.1 |
chassisCoolingIndexChassis Cooling Zones table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.3.51.1.1 |
chassisCoolingZoneThe cooling zone for the chassis component.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.51.1.2 |
chassisCoolingZoneStatusThe health state of the chassis cooling zone.
Note: This is the health of the cooling zone, not the health
status of the component in chassisCoolingZoneComponent.
Note that the other UIs may use slightly different terminology for the
three health state values, as such:
WEB - Normal, Attention, Critical
CLI - OK, Non-critical, Criticalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.51.1.3 |
chassisCoolingZoneComponentA component within a cooling zone.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.51.1.4 |
powerModuleHealth OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.4 |
powerModuleHealthTableTable of power module health information. Contains
the power health information for each power module. SEQUENCE OF PowerModuleHealthEntry .1.3.6.1.4.1.2.3.51.2.2.4.1 |
powerModuleHealthEntryPower Module health entry PowerModuleHealthEntry .1.3.6.1.4.1.2.3.51.2.2.4.1.1 |
powerModuleIndexPower module index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.4.1.1.1 |
powerModuleExistsIndicates whether the power module specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.4.1.1.2 |
powerModuleStateThe health state for the power module.
Note that the other UIs may use slightly different terminology for the
three health state values, as such:
WEB - Normal, Attention, Critical
CLI - OK, Non-critical, Criticalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.4.1.1.3 |
powerModuleDetailsThe details for this power module.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.4.1.1.4 |
powerModuleDescriptionThe description for this power module.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.4.1.1.9 |
spStatus OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.5 |
mmBistAndChassisStatus OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.5.2 |
bistRtcMM BIST Real Time Clock test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.5 |
bistLocalI2CBusMM BIST Local I2C bus test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.7 |
bistPrimaryMainAppFlashImageMM BIST Primary Main Application Firmware test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.8 |
bistSecondaryMainAppFlashImageMM BIST Secondary Main Application test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.9 |
bistBootRomFlashImageMM BIST Boot Firmware test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.10 |
bistEthernetPort1MM BIST external eth0 ethernet port test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.11 |
bistExternalI2CDevicesMM BIST external I2C devices test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.14 |
bistInternalEthernetSwitchMM BIST internal external switch test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.19 |
bistPrimaryKernelMM BIST primary kernel test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.25 |
bistSecondaryKernelMM BIST secondary kernel test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.26 |
bistPhysicalNetworkLinkMM BIST Physical Network Link test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.29 |
bistLogicalNetworkLinkMM BIST Logical Network Link test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.30 |
bistBladesInstalledThe blades that are installed on the chassis.
The blades are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of blades supported. If a blade is installed in a
bay, a 1 is present in the string in the position representing
the bay ID as read from left to right. For example, if blades
are installed in bays 1, 5, and 13, and 14 blades are supported,
the string would look like '10001000000010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.33 |
bistBladesCommunicatingThe blades that are communicating on the chassis.
The blades are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of blades supported. If a blade installed in a
bay is communicating, a 1 is present in the string in the position
representing the bay ID as read from left to right. For example,
if blades are communicating in bays 1, 5, and 13, and 14 blades
are supported, the string would look like '10001000000010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.49 |
bistChassisFansInstalledThe chassis fans that are installed on the chassis.
They are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number supported. If one is installed in a
bay, a 1 is present in the string in the position representing
the bay ID as read from left to right. For example, if it
is installed in bay 1, and 2 are supported, the string
would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.65 |
bistChassisFansFunctionalThe chassis fans installed on the chassis that are functional.
They are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number supported. If one is installed in a
bay, a 1 is present in the string in the position representing
the bay ID as read from left to right. For example, if it
is installed in bay 1, and 2 are supported, the string
would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.73 |
bistRearLEDCardInstalledIndicates whether a rear LED card is installedro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.74 |
bistRearLEDCardCommunicatingIndicates whether a rear LED card is communicatingro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.75 |
bistOtherMMInstalledIndicates whether a redundant MM is installed.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.76 |
bistOtherMMCommunicatingIndicates whether a redundant MM is communicating.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.77 |
bistPowerModulesInstalledThe power modules that are installed on the chassis.
The power modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of power modules supported. If a power module is
installed in a bay, a 1 is present in the string in the position
representing the bay ID as read from left to right. For example,
if power modules are installed in bays 1 and 3, and 4 power modules
are supported, the string would look like '1010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.81 |
bistPowerModulesFunctionalThe power modules that are functional on the chassis.
The power modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of power modules supported. If a power module is
installed and functioning in a bay, a 1 is present in the string
in the position representing the bay ID as read from left to right.
For example, if power modules are installed and functioning in bays
1 and 3, and 4 power modules are supported, the string would look
like '1010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.89 |
bistSwitchModulesInstalledThe switch modules that are installed on the chassis.
The switch modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of switch modules supported. If a switch module is
installed in a bay, a 1 is present in the string in the position
representing the bay ID as read from left to right. For example,
if switch modules are installed in bays 1 and 3, and 4 switch modules
are supported, the string would look like '1011'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.97 |
bistSwitchModulesCommunicatingThe switch modules that are communicating on the chassis.
The switch modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of switch modules supported. If a switch module is
installed and functioning in a bay, a 1 is present in the string
in the position representing the bay ID as read from left to right.
For example, if switch modules are installed and functioning in bays
1 and 3, and 4 switch modules are supported, the string would look
like '1011'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.113 |
bistChassisFansMUXAInstalledIndicates whether chassis fan MUX A is installedro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.120 |
bistChassisFansMUXAFunctionalIndicates whether chassis fan MUX A is functionalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.121 |
bistChassisFansMUXBInstalledIndicates whether chassis fan MUX B is installedro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.122 |
bistChassisFansMUXBFunctionalIndicates whether chassis fan MUX B is functionalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.123 |
bistLastUpdateIt is the time when the primary MM updated the last BIST results.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.200 |
rmmBistAndChassisStatus OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.5.3 |
rbistRtcStandby MM BIST Real Time Clock test result. The time of the last update
can be obtained by querying rbistUpdateTime object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.5 |
rbistLocalI2CBusStandby MM BIST Local I2C bus test result. The time of the last update
can be obtained by querying rbistUpdateTime object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.7 |
rbistEthernetPort1Standby MM BIST external ethernet port test result. The time of the last update
can be obtained by querying rbistUpdateTime object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.11 |
rbistExternalI2CDevicesStandby MM BIST external I2C devices test result collected
when the standby MM was primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.14 |
rbistInternalEthernetSwitchStandby MM BIST internal external switch test result.
The time of the last update can be obtained by querying rbistUpdateTime object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.19 |
rbistPhysicalNetworkLinkStandby MM BIST Physical Network Link test result collected
when the standby MM was primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.29 |
rbistLogicalNetworkLinkStandby MM BIST Logical Network Link test result collected
when the standby MM was primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.30 |
rbistBladesInstalledThe blades that were installed on the chassis when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
The blades are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of blades supported. If a blade is installed in a
bay, a 1 is present in the string in the position representing
the bay ID as read from left to right. For example, if blades
are installed in bays 1, 5, and 13, and 14 blades are supported,
the string would look like '10001000000010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.33 |
rbistBladesCommunicatingThe blades that were communicating on the chassis when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
The blades are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of blades supported. If a blade installed in a
bay is communicating, a 1 is present in the string in the position
representing the bay ID as read from left to right. For example,
if blades are communicating in bays 1, 5, and 13, and 14 blades
are supported, the string would look like '10001000000010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.49 |
rbistChassisFansInstalledThe chassis fans that were installed on the chassis when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
They are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of chassis fans supported. If it is installed in a
bay, a 1 is present in the string in the position representing
the bay ID as read from left to right. For example, if it
is installed in bay 1, and 2 are supported, the string
would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.65 |
rbistChassisFansFunctionalThe chassis fans installed on the chassis that were functional when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
They are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number supported. If it is installed and
functional in a bay, a 1 is present in the string in the position
representing the bay ID as read from left to right. For example,
if one is installed and functional only in bay 1, and 2
are supported, the string would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.73 |
rbistRearLEDCardInstalledIndicates whether a rear LED card is installedro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.74 |
rbistRearLEDCardCommunicatingIndicates whether a rear LED card is communicatingro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.75 |
rbistOtherMMInstalledIndicates whether a standby MM was installed when the
standby MM was once primary.The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.76 |
rbistOtherMMCommunicatingIndicates whether a standby MM was communicating when the
standby MM was once primary. The time of the last update can be
gotten from the object 'rbistUpdateTimePrimary'.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.77 |
rbistPowerModulesInstalledThe power modules that were installed on the chassis when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
The power modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of power modules supported. If a power module was
installed in a bay, a 1 is present in the string in the position
representing the bay ID as read from left to right. For example,
if power modules were installed in bays 1 and 3, and 4 power modules
were supported, the string would look like '1010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.81 |
rbistPowerModulesFunctionalThe power modules that were functional on the chassis when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
The power modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of power modules supported. If a power module was
installed and functioning in a bay, a 1 is present in the string
in the position representing the bay ID as read from left to right.
For example, if power modules were installed and functioning in bays
1 and 3, and 4 power modules were supported, the string would look
like '1010'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.89 |
rbistSwitchModulesInstalledThe switch modules that were installed on the chassis when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
The switch modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of switch modules supported. If a switch module was
installed in a bay, a 1 is present in the string in the position
representing the bay ID as read from left to right. For example,
if switch modules were installed in bays 1 and 3, and 4 switch modules
were supported, the string would look like '1011'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.97 |
rbistSwitchModulesCommunicatingThe switch modules that are communicating on the chassis when the
standby MM was once primary. The time of the last update
can be obtained by querying rbistUpdateTimePrimary object.
The switch modules are listed as a bitmap. The bitmap is a
string containing a list of 1's and 0's that is as long as
the number of switch modules supported. If a switch module was
installed and functioning in a bay, a 1 is present in the string
in the position representing the bay ID as read from left to right.
For example, if switch modules were installed and functioning in bays
1 and 3, and 4 switch modules were supported, the string would look
like '1011'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.113 |
rbistChassisFansMUXAInstalledIndicates whether chassis fan MUX A is installedro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.120 |
rbistChassisFansMUXAFunctionalIndicates whether chassis fan MUX A is functionalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.121 |
rbistChassisFansMUXBInstalledIndicates whether chassis fan MUX B is installedro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.122 |
rbistChassisFansMUXBFunctionalIndicates whether chassis fan MUX B is functionalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.3.123 |
rbistUpdateTimeIt is the time when the standby MM updated the last BIST results.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.200 |
rbistLastUpdatePrimaryIt is the time when the standby MM updated the last BIST results
when it was still primary.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.201 |
fanPack OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.6 |
fanPackTableTable of fan pack information. Contains
the information for each fan pack.
NOTE: Fan packs are also referred to as Power Module Cooling Devices. SEQUENCE OF FanPackEntry .1.3.6.1.4.1.2.3.51.2.2.6.1 |
fanPackEntryFan Pack entry FanPackEntry .1.3.6.1.4.1.2.3.51.2.2.6.1.1 |
fanPackIndexFan Pack sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.6.1.1.1 |
fanPackExistsIndicates whether the fan pack specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.6.1.1.2 |
fanPackStateThe health state for the fan pack.
Note that the other UIs may use slightly different terminology for the
three health state values, as such:
WEB - Normal, Attention, Critical
CLI - OK, Non-critical, Criticalro Enumeration .1.3.6.1.4.1.2.3.51.2.2.6.1.1.3 |
fanPackFanCountThe number of fans in the fan pack.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.6.1.1.4 |
fanPackAverageSpeedThe average speed of all fans in the fan pack expressed in percent(%)
of maximum RPM. If the fan pack is determined not to be running or
the fan pack speed cannot be determined, the string will
indicate 'Offline'. The string 'Not Readable!' indicates that the
given monitor is not supported on this system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.6.1.1.5 |
fanPackAverageSpeedRPMThe average speed of all fans in the fan pack expressed in RPM.
If the fan pack is determined not to be running or the fan pack speed
cannot be determined, the string will indicate 'Offline'. The string
'Not Readable!' indicates that the given monitor is not supported on
this system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.6.1.1.6 |
fanPackControllerStateThe health state for the controller for the fan pack.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.6.1.1.7 |
systemHealth OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.7 |
systemHealthStatIndicates status of system health for the
system in which the MM resides.
Value of 'critical' indicates a severe error has occurred
and the system may not be functioning. A value of
'nonCritical' indicates that a error has occurred but
the system is currently functioning properly. A value of
'systemLevel' indicates that a condition has occurred
that may change the state of the system in the future but currently
the system is working properly. A value of
'normal' indicates that the system is operating normally.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.7.1 |
systemHealthSummaryTableTable of System Health summary. Contains more detailed
information about the reasons for the overall system
health status. SEQUENCE OF SystemHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.2.7.2 |
systemHealthSummaryEntrySystem Health Summary entry SystemHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.2.7.2.1 |
systemHealthSummaryIndexSystem health summary index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.7.2.1.1 |
systemHealthSummarySeveritySystem health summary severity.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.2 |
systemHealthSummaryDescriptionSystem health summary description.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.3 |
systemHealthSummaryDateTimeSystem health summary date time.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.4 |
systemHealthSummaryAuxDataSystem health summary auxilliary event data. If auxilliary
event data is available, it is device-specific event data
provided to the CMM by the device.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.11 |
systemHealthSummaryEventIDSystem health summary event ID.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.12 |
leds OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8 |
frontPanelLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.1 |
faultLEDIndicates whether the front panel system error LED is on or off.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.1.1 |
checkLogLEDIndicates whether the front panel system information LED
is on or off. For Write access, the LED can be turned off
only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.1.2 |
identifyLEDIndicates whether the front panel identity LED is on or off.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.1.4 |
bladeLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.2 |
bladeLEDsTableTable of blade status information.
NOTE: Querying objects in this table may take significantly longer
than normal, so it is recommended that the query timeout be set to
a large value. On a fully populated chassis, the timeout should be set
to 120 seconds or more. SEQUENCE OF BladeLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.2.1 |
bladeLEDsEntryBlade system status entry BladeLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1 |
ledBladeIndexBlade LED table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.1 |
ledBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.2 |
ledBladeExistsIndicates whether the blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.3 |
ledBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.4 |
ledBladeHealthStateThe system health state for the blade.
Unknown: Blade is in an undefined state.
Good: Blade is operating normally.
Warning: One or more outstanding warnings exist for this blade.
Critical: One or more outstanding critical events for this blade.
Kernel Mode: Blade is in kernel mode.
Discovering: The MM is currently in the process of discovering this blade.
Communications Error: The MM failed to communicate with this blade.
No Power: No power to the blade's domain.
Flashing: Flashing in progress.
Initialization Failure: Blade failed to initialized.
Insufficient Power: Not enough power is left in the blade's domain to power the blade.
Power Denied: Power was denied to the blade.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.5 |
ledBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.6 |
ledBladeFaultIndicates whether the blade fault LED is on or off.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.7 |
ledBladeCheckLogIndicates whether the blade check log information LED is on or off.
For Write access, the LED can be turned off only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.8 |
ledBladeIdentifyIndicates whether the blade identify LED is on, off, or blinking.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.11 |
bladeLEDsDetailsTableTable of blade LEDs detailed information.
NOTE: Querying objects in this table may take significantly longer
than normal, so it is recommended that the query timeout be set to
a large value. On a fully populated chassis, the timeout should be set
to 120 seconds or more. SEQUENCE OF BladeLEDsDetailsEntry .1.3.6.1.4.1.2.3.51.2.2.8.2.2 |
bladeLEDsDetailsEntryBlade LEDs Details entry BladeLEDsDetailsEntry .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1 |
ledIndexThe LED index number.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.1 |
ledBladeBayNumberThe bay number of the main server blade that the LED is grouped into.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.2 |
ledBladeComponentTypeType of the component/subcomponent grouping for this LED.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.3 |
ledBladeLabelText label for a LED.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.4 |
ledBladeStateText description which denotes color or on/off/blink state for a LED.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.5 |
ledBladeLocationLocation of this LED.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.6 |
smLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.4 |
smLEDsTableTable of switch module LEDs information. SEQUENCE OF SMLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.4.2 |
smLEDsEntrySwitch module LEDs information entry SMLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.4.2.1 |
ledSMIndexSwitch module LEDs table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.4.2.1.1 |
ledSMSlotThe bay number of the switch.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.4.2.1.2 |
ledSMLabelThe name associated with the LED.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.4.2.1.3 |
ledSMStateNOTE: This table entry is read-write ONLY when Label = 'Enclosure Identity'.
All other Label values have read-only access.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.4.2.1.4 |
ledSMLocationThe physical location where the LED can be found on the Switch.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.4.2.1.5 |
chassisFanLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.5 |
chassisFanLEDsTableTable of chassis fan LEDs information. SEQUENCE OF ChassisFanLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.5.1 |
chassisFanLEDsEntryChassis fan LEDs information entry ChassisFanLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1 |
ledChassisFanIndexChassis fan LEDs table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1.1 |
ledChassisFanIdThe numeric chassis fan ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1.2 |
ledChassisFanExistsIndicates whether the chassis fan specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1.3 |
ledChassisFanErrorIndicates whether the chassis fan error LED is on, off, or not available.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1.4 |
fanPackLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.6 |
fanPackLEDsTableTable of fan pack LEDs information. This table is
deprecated because the LEDs for the power modules' fans
are no longer on the fan packs, the LEDs are on the
power modules.
See the MIB tables, componentLEDsTable and
componentLEDsDetailsTable, for the power modules' LEDs.
NOTE: Fan packs are also referred to as Power Module Cooling Devices.deprecated SEQUENCE OF FanPackLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.6.1 |
fanPackLEDsEntryFan Pack LEDs information entrydeprecated FanPackLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1 |
ledFanPackIndexFan Pack LEDs table index.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1.1 |
ledFanPackIdThe numeric fan pack ID.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1.2 |
ledFanPackExistsIndicates whether the fan pack specified exists or not.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1.3 |
ledFanPackErrorIndicates whether the fan pack error LED is on or off.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1.4 |
fuelGauge OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10 |
fuelGaugeInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.1 |
fuelGaugeTableTable of Fuel Gauge information. SEQUENCE OF FuelGaugeEntry .1.3.6.1.4.1.2.3.51.2.2.10.1.1 |
fuelGaugeEntryFuel Gauge entry FuelGaugeEntry .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1 |
fuelGaugeIndexFuel Gauge Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.1 |
fuelGaugePowerDomainNumberFuel Gauge Table Power Domain Number.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.2 |
fuelGaugeStatusFuel Gauge Table Status for the power domain.
The response will start out with a numeric value (0 = unknown,
1 = good, 2 = warning, and 3: bad), followed by a text message.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.3 |
fuelGaugePowerModulesFuel Gauge Table Power Module capacity in Watts in the power domain.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.4 |
fuelGaugePowerManagementPolicySettingPower Management Policy Setting for each power domain.
A new powerPolicyTable has been added which provides more detailed
information regarding a domains power policy information. This table
also has the capability to SET the power policy for a given domain.
Power Module Redundancy
Intended for a single power source into the chassis where each
Power Module is on its own dedicated circuit. Maximum power is
limited to one less than the number of Power Modules when more
than one Power Module is present. One Power Module can fail
without affecting compute node operation. Multiple Power Module
failures can cause the chassis to power off. Note that some compute
nodes may not be allowed to power on if doing so would exceed the
policy power limit.
Power Module Redundancy with Compute Nodes Throttling Allowed
Very similar to Power Module Redundancy. This policy allows for a
higher power limit; however, capable compute nodes may be allowed
to throttle down if one Power Module fails.
Basic Power Management
Maximum power limit is higher than other policies and is limited
only by the nameplate power of all the Power Modules combined.
This is the least conservative approach, since it does not provide
any protection for power source or Power Module failure. If any
single power supply fails, compute node and/or chassis operation
may be affected.
Power Source Redundancy
Intended for dual power sources into the chassis. Maximum power is
limited to the capacity of half the number of installed power modules.
This is the most conservative approach and is recommended when all power
modules are installed. When the chassis is correctly wired with dual
power sources, one power source can fail without affecting compute
node server operation. Note that some compute nodes may not be allowed
to power on if doing so would exceed the policy power limit.
Power Source Redundancy with Compute Node Throttling Allowed
Very similar to the Power Source Redundancy. This policy allows
for a higher power limit, however capable compute nodes may be allowed
to throttle down if one power source fails.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.6 |
fuelGaugeTotalPowerThis field displays the total available power for each power domain based on
installed power modules and the current Power Management Policy Setting.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.7 |
fuelGaugeAllocatedPowerThis field displays the power that has been reserved in each power domain.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.8 |
fuelGaugeRemainingPowerThis field displays the remaining power available in each domain.
Remaining Power = Total Power minus Power In Usero OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.9 |
fuelGaugePowerInUsedThis field displays the total power being used in each power domain.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.10 |
powerDomain1 OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.2 |
powerDomain1TableTable of Power Domain 1. SEQUENCE OF PowerDomain1Entry .1.3.6.1.4.1.2.3.51.2.2.10.2.1 |
powerDomain1EntryFuel Gauge entry PowerDomain1Entry .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1 |
pd1IndexPower Domain 1 Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.1 |
pd1BayNumberPower Domain 1 Table Bay Number.
The following Bay Number IDs are used:
notApplicable(1),
notApplicable(2),
fanPackBay1(3),
fanPackBay2(4),
fanPackBay3(5),
fanPackBay4(6),
fanPackBay5(7),
fanPackBay6(8),
chassisfanBay1(9),
chassisfanBay2(10),
chassisfanBay3(11),
chassisfanBay4(12),
chassisfanBay5(13),
chassisfanBay6(14),
chassisfanBay7(15),
chassisfanBay8(16),
chassisfanBay9(17),
chassisfanBay10(18),
managementModuleBay1(19),
managementModuleBay2(20),
ioModuleBay1(21),
ioModuleBay2(22),
ioModuleBay3(23),
ioModuleBay4(24),
serverBladeBay1(25),
serverBladeBay2(26),
serverBladeBay3(27),
serverBladeBay4(28),
serverBladeBay5(29),
serverBladeBay6(30),
serverBladeBay7(31),
serverBladeBay8(32),
serverBladeBay9(33),
serverBladeBay10(34),
serverBladeBay11(35),
serverBladeBay12(36),
serverBladeBay13(37),
serverBladeBay14(38),
notApplicable(39)ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.2 |
pd1BladePrimarySlotPower Domain 1 Table Blade Primary Slot can be useful
when a server blade spans multiple slots (e.g. double wide or
triple wide). For example if the blade is double wide and
is installed in slot 3 and 4. 3 is primary slot while 4 is not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.3 |
pd1ModuleStatusPower Domain 1 Table Module Throttle Status.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.4 |
pd1ModuleNamePower Domain 1 Table Module Name.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.5 |
pd1ModuleStatePower Domain 1 Table Module State.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.6 |
pd1ModuleAllocatedPowerCurrentPower Domain 1 Table Allocated Power Current indicates the current power
allocation for the module in Watts.
NOTE: When a server blade spans multiple slots (e.g. double wide or
triple wide), the current power allocation for the module is equally
divided among the slots.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.7 |
pd1ModuleAllocatedPowerMaxPower Domain 1 Table Allocated Power Max indicates the maximum power
allocation for the module in Watts. It is indicative of the maximum
amount of power the module will consume in the domain when it is
fully populated with memory chips, expansion cards, etc.
NOTE: When a server blade spans multiple slots (e.g. double wide or
triple wide), the maximum power allocation for the module is equally
divided among the slots.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.8 |
pd1ModuleAllocatedPowerMinPower Domain 1 Table Allocated Power Min indicates the minumum power
allocation for the module in Watts. It is indicative of the minumum
power consumption of the component in the domain based on its
maximum throttle limit.
NOTE: When a server blade spans multiple slots (e.g. double wide or
triple wide), the minimum power allocation for the module is equally
divided among the slots.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.9 |
pd1ModuleCPUDutyCyclesPower Domain 1 Table Module CPUs Duty Cycles applies to blade
servers only. It displays the duty cycle for each CPU on the blade
as a percentage. Note that some blades do not report the CPU
duty cycles. In this case, 'notApplicable' will be displayed.
NOTE: The CPU duty cycles are reported only on a primary slot when
a server blade spans multiple slots (e.g. double wide or
triple wide). For example if the blade is double wide and
is installed in slot 3 and 4. 3 is primary slot while 4 is not.
The CPU duty cycles are reported on slot 3 while 'notApplicable'
is displayed for slot 4.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.10 |
pd1ModuleThrottlePower Domain 1 Table Module Throttle indicates whether the
server blade may be allowed to throttle or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.11 |
pd1ModulePowerCapabilitiesPower Domain 1 Table Module Power Capabilities.
staticPowerManagement: the module with the static worst
case power values.
fixedPowermanagement: the module with the static power values but
ability to throttle.
dynamicPowerManagement: the module with power meter capability,
measurement enabled, but capping disabled.
dynamicPowerMeasurement1: the module with power meter capability,
measurement enabled, phase 1 only
dynamicPowerMeasurement2: the module with power meter capability,
measurement enabled, phase 2 or higher
dynamicPowerMeasurementWithPowerCapping: the module with power
meter capability, both measurement and capping enabled,
phase 2 or higherro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.12 |
pd1ModuleMeasuredOrStaticPower Domain 1 Table Module Measured Or Static.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.13 |
pd1TopologyPathThe topology path for the component in this table. The chassis and each
installed component is represented by a hardware topology tree, where
each node in the tree represents a component. The path to a particular
component consists of one or more <component>,<instance> pairs, where
each successive pair is a child of the previous parent pair.
As an example, the root of the tree is the chassis and is represented
by the pair 'CHASSIS, 1'. This pair indicates the first instance of
the chassis. If a blade is inserted in slot 4 of the chassis, its
topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the
components in the chassis can be determined along with their relative
hierarchy to each other.
CHASSIS, 0x01 Chassis
MM, 0x02 Management Module
BLADE, 0x03 Main system board of a blade
POWER, 0x04 Power Supply, Power Module, etc
COOLING, 0x05 Fan, blower, or other cooling device
IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge
MEDIA, 0x07 Media device
PROCESSOR, 0x08 Any processor, processor module, etc
STORAGE, 0x09 Any type of storage device
EXPANSION, 0x0A Expansion Card (not covered by more specific type)
MEMORY, 0x0B Any memory device, module, etc
MFRU, 0x0C Managed FRU Device
PANEL, 0x0D Any sort of panel device, such as a front panel
BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc
CARD_EXPANSION, 0x0F Expansion card, ie. daughter card
CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card
INTERPOSER, 0x11 Interposer device
CLOCK, 0x12 Clock card
MUX, 0x13 Mulitplexer card
ADDIN, 0x14 cKVM card & other addin cards
STORAGE_MODULE, 0x15 Container of one or more Storage Devices
SYS_EXPANSION_CARD, 0x16 Management card
BATTERY, 0x17 A single battery
BATTERY_MODULE, 0x18 Container of one or more batteries
REAR_LED, 0x19 Rear LED card
MEMORY_BANK, 0x1A Memory banks
AIR_FILTER, 0x1B Filter mechanism (bezel)
SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports
PARENT, 0x1D Reference to parent for multi-parent support
PHY_PORT, 0x1E Physical port
IO_EXPANDER, 0x1F RAID card
CABLE, 0x20 Cable/Interconnect
FAN_MUX 0x29 Fan multiplexer card
PCI_EXPRESS, 0x32 PCI express card on (PEN)
FLASH_DIMM, 0x33 Used for SPD devices that matches the silkscreen of the DIMM slot
RACK, 0x50 Rack
PLATFORM, 0x51 Generic Platform like rack mounted server/appliance
DATAPLEX, 0x52 DataPlex
OTHER, 0x53 Other unknown etc.
PERIPHERAL_MODULE, 0x54
SYSTEM_BOARD, 0x55 System board
PROCESSOR_MODULE, 0x56
BACK_PANEL, 0x57
POWER_SYSTEM_BOARD, 0x58
STORAGE_BACKPLANE, 0x59 Drive back plane
PROC_BOARD, 0x5A Holds 1 or more processors
POWER_DI, 0x5B Power mgt / power distribution board
CHASSIS_BACK_PANEL, 0x5C
SUB_CHASSIS, 0x5D
OTHER_CHASSIS_BOARD, 0x5E
DEVICE_MODULE, 0x5F
REMOTE_DEVICE, 0x60 Remote mgt communication device
EXTERNAL_ENVIRONMENT, 0x61 Such as external temp sensor for outside box temps
PROC_MEMORY_MODULE, 0x62 Processors and memory on same modulero OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.1.1.14 |
powerDomain1PowerTrending OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.2.3 |
pd1PowerTrendingPeriodSpecify time period for power domain 1 power trending information
table view.
NOTE: This time period should be configured before displaying the
following Power Trending Information table for Power Domain.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.2.3.1 |
pd1PowerTrendingSampleTableTable of Power Domain 1 Power Trending Information. SEQUENCE OF Pd1PowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.2.3.10 |
pd1PowerTrendingSampleEntryPower Domain 1 Power Trending Sample entry. Pd1PowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.2.3.10.1 |
pd1PowerTrendingSampleIndexPower Domain 1 Power Trending Sample Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.2.3.10.1.1 |
pd1PowerTrendingSampleTimeStampPower Domain 1 Power Trending Sample Table Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.3.10.1.2 |
pd1PowerTrendingSampleAvePower Domain 1 Power Trending Table Average Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.2.3.10.1.3 |
moduleInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.4 |
bladeDetails OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.4.1 |
bladeDetailsTableTable of Blade Module Details. SEQUENCE OF BladeDetailsEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1 |
bladeDetailsEntryBlade Module Details entry. BladeDetailsEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1 |
bladeDetailsIndexBlade Module Details Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.1 |
bladeDetailsIdBlade Module Details Table Blade Id.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.2 |
bladeDetailsMaxPowerConfigBlade Module Details Table Maximum Power Configuration.
Allow the user to set the maximum power that can be used by the blade. This
function is also known as power capping.
Blade must be powered on to set this value.
If the value of maximum power config is zero, it means the blade doesn't
support the power capping featurerw INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.3 |
bladeDetailsEffectiveClockRateBlade Module Details Table Effective CPU Clock Rate applies to DPM
blades only. It displays processor's effective clock rate based
on sample interval. Note that some blades do not effective
clock rate. In this case, 'notApplicable' will be displayed.
NOTE: The effective clock rate are reported only on a primary slot when
a server blade spans multiple slots (e.g. double wide or
triple wide). For example if the blade is double wide and
is installed in slot 3 and 4. 3 is primary slot while 4 is not.
The effective clock rate are reported on slot 3 while 'notApplicable'
is displayed for slot 4.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.4 |
bladeDetailsMaximumClockRateBlade Module Details Table Maximum CPU Clock Rate applies to DPM
blades only. It displays processor's maximum clock rate based
on sample interval. Note that some blades do not maximum
clock rate. In this case, 'notApplicable' will be displayed.
NOTE: The maximum clock rate are reported only on a primary slot when
a server blade spans multiple slots (e.g. double wide or
triple wide). For example if the blade is double wide and
is installed in slot 3 and 4. 3 is primary slot while 4 is not.
The maximum clock rate are reported on slot 3 while 'notApplicable'
is displayed for slot 4.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.5 |
bladeDetailsPowerSaverModeWhen enabled, the static low power saver mode allows the blade to selectively
alter its operating voltage and frequency to reduce power consumption.
This feature is not available on all blade types. Please refer to the blade documentation for details.
If a blade does not support the static low power saver mode, this object will return notApplicable (255).
Under certain rare circumstances, the enabling of the static low power saver mode
may not complete successfully due to interactions with other
blade functions, such as BIOS. Therefore, it is highly recommended that
the user perform a GET of this object after performing a SET, in order
to verify the completion of the intended operation.
NOTE: enabling this object will disable bladeDetailsDynamicPowerSaver if its not already disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.6 |
bladeDetailsDynamicPowerSaverWhen enabled, Dynamic Power Saver allows the voltage and frequency of the CPUs on the blade
to be controlled based on how busy the CPU is. This feature is not available on all blade types.
Please refer to the blade documentation for details. If a blade does not support the dynamic power
saver, this object will return notApplicable (255).
Under certain rare circumstances, the enabling of the dynamic power saver may not complete
successfully due to interactions with other blade functions, such as BIOS. Therefore, it is
highly recommended that the user perform a GET of this object after performing a SET, in order
to verify the completion of the intended operation.
NOTE: enabling this object will disable bladeDetailsPowerSaverMode if its not already disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.7 |
bladeDetailsDynamicPowerFavorPerformanceOverPowerWhen enabled, Dynamic Power Favor Performance Over Power supports a max performance mode that pushes the
system past its nominal CPU frequency when CPU and memory utilization implies it would help and the
system allows it. Dynamic Power Performance Over Power can be active on the blade only after Dynamic
Power Saver is enabled. This feature is not available on all blade types. Please refer to the
blade documentation for details. If a blade does not support the dynamic power saver, this object
will return notApplicable (255).
Under certain rare circumstances, the enabling of the dynamic power favor performance over power
may not complete successfully due to interactions with other blade functions, such as BIOS.
Therefore, it is highly recommended that the user perform a GET of this object after performing a SET,
in order to verify the completion of the intended operation.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.8 |
bladeDetailsPowerControlThis object is used to get or set the power control setting on a blade.
If dynamic power mgmt is not supported on a blade, notApplicable(255) will be returned.
This will set the power control setting on all slots of the multiwide blade. The
same can be used if the blade is single wide.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.9 |
bladeDetailsPcapMinBlade Module Details Table power capping Minimum value in watts.
The blade must support the advanced power management feature.
If the value of Pcap Min is 'notApplicable', it means the blade doesn't
support the power capping feature.
If the value of Pcap Min is 'notAvailable', it means the data
could not be obtained.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.10 |
bladeDetailsPcapGuaranteedMinBlade Module Details Table power capping Guaranteed Minimum value in watts.
The blade must support the advanced power management feature.
If the value of Pcap Guaranteed Min is 'notApplicable', it means the blade doesn't
support the power capping feature.
If the value of Pcap GuaranteedMin is 'notAvailable', it means the data
could not be obtained.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.11 |
bladeDetailsPcapMaxBlade Module Details Table power capping Maximum value in watts.
The blade must support the advanced power management feature.
If the value is '<max1> Watts,<max2> Watts', which means,
- if bladeDetailsDynamicPowerSaver is enabled, it is <max2>
- otherwise it is <max1>
If the value of Pcap Max is 'notApplicable', it means the blade doesn't
support the power capping feature.
If the value of Pcap Min is 'notAvailable', it means the data
could not be obtained.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.1.1.12 |
bladePowerTrending OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3 |
bladePowerTrendingPeriodSpecify time period for blade module power trending information table view.
NOTE: This time period should be configured before displaying the
following Power Trending Information table for Blade Module.
Since the power trending data is constantly being computed and saved in the
management application database, some queries of the bladePowerTrendingSampleTable
may not provide information for a very short window of time.
If the table returns empty, please wait a short period and retry the query.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.1 |
bladePowerTrendingBladeIdBlade Module Power Trending Blade Id.
NOTE: The Blade Id should be configured before displaying the
bladePowerTrendingTable.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.2 |
errorLogs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.3 |
configureSP OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4 |
restartReset OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.7 |
components OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22 |
service OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23 |
bladePowerTrendingTopologyPathThe topology Path is a location identifier for a blade. The chassis and each
installed blade is represented by a hardware topology tree, where
each node in the tree represents a blade. The path to a particular
blade consists of one or more <blade>,<instance> pairs, where
each successive pair is a child of the previous parent pair.
This topology path is used to identify blades such as blade storage devices.
Some examples. A storage blade with a controller card plugged into slot 1
topology location would be represented as :
010103010301
A storage blade with a controller card plugged into slot 2
topology location would be represented as :
010103010302
::= { bladePowerTrending 3 }
bladePowerTrendingSampleTable OBJECT-TYPE
SYNTAX SEQUENCE OF BladePowerTrendingSampleEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTIONrw OCTET STRING .1.3.6.1.4.1.2.3.51.2.24.1.1.6 |