BLADE-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for BLADE-MIB.
2815
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
2815 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 |
planarTemp OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.1.1 |
mmTempManagement 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.ro 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 |
frontPanelTempThe front panel 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 |
frontPanel2TempThe front panel 2 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.
NOTE: This MIB object is for BladeCenter HT onlyro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.1.5.2 |
voltage OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.2 |
planarVolt OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.2.1 |
plus5Volt+5 Volt power supply voltage reading expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.2.1.1 |
plus3Pt3Volt+3.3 Volt power supply voltage reading expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.2.1.2 |
plus12Volt+12 Volt power supply voltage reading expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.2.1.3 |
minus5Volt-5 Volt power supply voltage reading expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.2.1.5 |
plus2Pt5Volt+2.5 Volt power supply voltage reading expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.2.1.6 |
plus1Pt8Volt+1.8 Volt power supply voltage reading expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.2.1.8 |
blowers OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.3 |
blower1speedBlower 1 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 blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.1 |
blower2speedBlower 2 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 blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.2 |
blower3speedBlower 3 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 blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: This MIB object is for BladeCenter T, BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.3 |
blower4speedBlower 4 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 blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: This MIB object is for BladeCenter T, BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.4 |
blower1StateThe health state for blower 1.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.10 |
blower2StateThe health state for blower 2.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.11 |
blower3StateThe health state for blower 3.
NOTE: This MIB object is for BladeCenter T and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.12 |
blower4StateThe health state for blower 4.
NOTE: This MIB object is for BladeCenter T and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.13 |
blower1speedRPMBlower 1 speed expressed in RPM.
If the blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: This MIB object is for AMM installed in BladeCenter H, BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.20 |
blower2speedRPMBlower 2 speed expressed in RPM.
If the blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: This MIB object is for AMM installed in BladeCenter H, BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.21 |
blower3speedRPMBlower 3 speed expressed in RPM.
If the blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: This MIB object is for AMM installed in BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.22 |
blower4speedRPMBlower 4 speed expressed in RPM.
If the blower is determined not to be running or
the blower speed cannot be determined, the string will
indicate 'Offline'.
The string 'Not Readable!' indicates that the given monitor
is not supported on this system.
NOTE: This MIB object is for AMM installed in BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.23 |
blower1ControllerStateThe health state for the controller for blower 1.
NOTE: This MIB object is for AMM installed in BladeCenter H, BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.30 |
blower2ControllerStateThe health state for the controller for blower 2.
NOTE: This MIB object is for AMM installed in BladeCenter H, BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.31 |
blower3ControllerStateThe health state for the controller for blower 3.
NOTE: This MIB object is for AMM installed in BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.32 |
blower4ControllerStateThe health state for the controller for blower 4.
NOTE: This MIB object is for AMM installed in BladeCenter HT and BladeCenter S only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.3.33 |
blower1ExhaustTempThe exhaust temperature in degrees Celsius for blower 1.
NOTE: This MIB object is for BCS only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.40 |
blower2ExhaustTempThe exhaust temperature in degrees Celsius for blower 2.
NOTE: This MIB object is for BCS only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.41 |
blower3ExhaustTempThe exhaust temperature in degrees Celsius for blower 3.
NOTE: This MIB object is for BCS only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.42 |
blower4ExhaustTempThe exhaust temperature in degrees Celsius for blower 4.
NOTE: This MIB object is for BCS only.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.3.43 |
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 sequence 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.ro 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 |
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 |
bistSdramMM BIST DRAM test result.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.1 |
bistRs485Port1MM BIST RS 485 legacy test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.2 |
bistRs485Port2MM BIST RS 485 local bus test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.3 |
bistNvramMM BIST NVRAM test result.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.4 |
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 ethernet port test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.11 |
bistEthernetPort2MM BIST internal ethernet port test result.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.12 |
bistInternalPCIBusMM BIST PCI bus test result.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.13 |
bistExternalI2CDevicesMM BIST external I2C devices test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.14 |
bistUSBControllerMM BIST USB controller test result.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.15 |
bistVideoCompressorBoardMM BIST Video Compressor Board test result.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.16 |
bistRemoteVideoMM BIST Remote Video test result.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.17 |
bistPrimaryBusMM BIST primary mid-plane bus test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.18 |
bistInternalEthernetSwitchMM BIST internal external switch test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.19 |
bistVideoCaptureMM BIST video capture test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.20 |
bistUSBKeyboardMouseEmulationMM BIST USB keyboard and mouse test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.21 |
bistUSBMassStorageEmulationMM BIST mass storage emulation test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.22 |
bistUSBKeyboardMouseFirmwareMM BIST USB keyboard and mouse firmware test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.23 |
bistUSBMassStorageFirmwareMM BIST USB keyboard mouse firmware test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.24 |
bistPrimaryCoreMM BIST primary core test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.25 |
bistSecondaryCoreMM BIST secondary core test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.26 |
bistInternalIOExpanderMM BIST internal IO expander test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.27 |
bistRemoteControlFirmwareMM BIST Remote Control firmware test result.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.28 |
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 |
bistBlowersInstalledThe blowers that are installed on the chassis.
The blowers 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 blowers supported. If a blower 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 a blower
is installed in bay 1, and 2 blowers are supported, the string
would look like '10'.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.65 |
bistBlowersFunctionalThe blowers installed on the chassis that are functional.
The blowers 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 blowers supported. If a blower 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 a blower is installed and functional only in bay 1, and 2 blowers
are supported, the string would look like '10'.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.73 |
bistMediaTrayInstalledIndicates whether a media tray is installed on the chassis.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.5.2.74 |
bistMediaTrayCommunicatingIndicates whether a media tray is communicating.ro 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' for BladeCenter and
BladeCenter T and '1011000000' for BladeCenter H and BladeCenter HT.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 for BladeCenter and BladeCenter T and '1011000000' for
BladeCenter H and BladeCenter HT.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.2.113 |
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 |
rbistRs485Port1Standby MM BIST RS 485 legacy 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.2 |
rbistRs485Port2Standby MM BIST RS 485 local 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.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 |
rbistPrimaryMainAppFlashImageStandby MM BIST Primary Main Application Firmware 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.8 |
rbistSecondaryMainAppFlashImageStandby MM BIST Secondary Main Application 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.9 |
rbistBootRomFlashImageStandby MM BIST Boot Firmware 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.10 |
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 |
rbistVideoCaptureStandby MM BIST video capture 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.20 |
rbistUSBKeyboardMouseEmulationStandby MM BIST USB keyboard and mouse 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.21 |
rbistUSBMassStorageEmulationStandby MM BIST mass storage emulation 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.22 |
rbistUSBKeyboardMouseFirmwareStandby MM BIST USB keyboard and mouse firmware 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.23 |
rbistUSBMassStorageFirmwareStandby MM BIST USB keyboard mouse firmware 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.24 |
rbistPrimaryCoreStandby MM BIST primary core 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.25 |
rbistSecondaryCoreStandby MM BIST secondary core 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.26 |
rbistInternalIOExpanderStandby MM BIST internal IO expander 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.27 |
rbistRemoteControlFirmwareStandby MM BIST Remote Control firmware 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.28 |
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 |
rbistBlowersInstalledThe blowers 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 blowers 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 blowers supported. If a blower 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 a blower
is installed in bay 1, and 2 blowers are supported, the string
would look like '10'.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.65 |
rbistBlowersFunctionalThe blowers 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.
The blowers 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 blowers supported. If a blower 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 a blower is installed and functional only in bay 1, and 2 blowers
are supported, the string would look like '10'.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.73 |
rbistMediaTrayInstalledIndicates whether a media tray was installed on the chassis 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.74 |
rbistMediaTrayCommunicatingIndicates whether a media tray was communicating 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.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' for BladeCenter and
BladeCenter T and '1011000000' for BladeCenter H and BladeCenter HT.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 for BladeCenter and BladeCenter T and '1011000000' for
BladeCenter H and BladeCenter HT.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.5.3.113 |
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.
0 = unknown, 1 = good, 2 = warning, 3 = bad.ro 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.
0 = operational, 1 = flashing in progress, 2 = not present, 3 = communication error,
255 = unknownro 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.
NOTE: This MIB object is for BladeCenter only. SEQUENCE OF SystemHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.2.7.2 |
systemHealthSummaryEntrySystem Health Summary entry
NOTE: This MIB object is for BladeCenter only. SystemHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.2.7.2.1 |
systemHealthSummaryIndexSystem health summary index.
NOTE: This MIB object is for BladeCenter only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.7.2.1.1 |
systemHealthSummarySeveritySystem health summary severity.
NOTE: This MIB object is for BladeCenter only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.2 |
systemHealthSummaryDescriptionSystem health summary description.
NOTE: This MIB object is for BladeCenter only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.3 |
systemHealthSummaryDateTimeSystem health summary date time.
NOTE: This MIB object is for BladeCenter only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.7.2.1.4 |
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 |
systemErrorLEDIndicates whether the front panel system error LED is on or off.
NOTE: This MIB object is for BladeCenter only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.1.1 |
informationLEDIndicates whether the front panel system information LED
is on or off. For Write access, the LED can be turned off
only.
NOTE: This MIB object is for BladeCenter only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.1.2 |
temperatureLEDIndicates whether the front panel temperature LED is on or off.
NOTE: This MIB object is for BladeCenter only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.1.3 |
identityLEDIndicates whether the front panel identity LED is on or off.
NOTE: This MIB object is for BladeCenter only.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 server 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 AMM is currently in the process of discovering this blade.
Communications Error: The AMM 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 |
ledBladeSystemErrorIndicates whether the blade system error LED is on or off.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.7 |
ledBladeInformationIndicates whether the blade 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 |
ledBladeKVMIndicates whether the blade KVM LED is on, off, or blinking.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.9 |
ledBladeMediaTrayIndicates whether the blade media tray LED is on, off, or blinking.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.1.1.10 |
ledBladeIdentityIndicates 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.
For consistent results, view as a table and not as individual entries.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.
For consistent results, view as a table and not as individual entries.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.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.3 |
ledBladeLabelText label for a LED.
For consistent results, view as a table and not as individual entries.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.
For consistent results, view as a table and not as individual entries.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.5 |
ledBladeLocationLocation of this LED.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.2.2.1.6 |
telcoPanelLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.3 |
criticalLEDIndicates whether the BladeCenter T Panel CRT (Critical) LED is on or off.
NOTE: This MIB object is for BladeCenter T only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.3.1 |
majorLEDIndicates whether the BladeCenter T Panel MJR (Major) LED is on or off.
NOTE: This MIB object is for BladeCenter T only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.3.2 |
minorLEDIndicates whether the BladeCenter T Panel MNR (Minor) LED is on or off.
NOTE: This MIB object is for BladeCenter T only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.3.3 |
telcoIdentityLEDIndicates whether the BladeCenter T Panel identity LED is on or off.
NOTE: This MIB object is for BladeCenter T only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.3.4 |
telcoColorSelIndicates whether the BladeCenter T Critical and Major LEDs are displayed in amber or red color.
NOTE: This MIB object is for BladeCenter T only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.3.5 |
criticalityAssertionModeIndicates whether the BladeCenter T Criticality Assertion Mode is enabled or disabled.
NOTE: This MIB object is for BladeCenter T only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.3.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.1 |
smLEDsEntrySwitch module LEDs information entry SMLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.4.1.1 |
ledSMIndexSwitch module LEDs table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.4.1.1.1 |
ledSMLEDsA bitmap of LEDs information on the selected switch module. The
bitmap is a string containing a list of 1's and 0's. Every 4 bytes
are used to represent a led state. The first 64 bytes represent the
status of the external LEDs while the last 64 bytes represent the
status of the internal port connections from the switch module to
blades. Each nibble of data is presented in the bitmap format (0000)
and is encoded as followed
- 0000: LED is not present
- 0001: LED is off
- 0010: LED is on
NOTE: The data is read from left to right, starting out with blade
server 1 and so on.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.8.4.1.1.2 |
blowerLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.5 |
blowerLEDsTableTable of blower LEDs information.
NOTE: Blowers are also referred to as Chassis Cooling Devices. SEQUENCE OF BlowerLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.5.1 |
blowerLEDsEntryBlower LEDs information entry BlowerLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1 |
ledBlowerIndexBlower LEDs table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1.1 |
ledBlowerIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1.2 |
ledBlowerExistsIndicates whether the blower specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.5.1.1.3 |
ledBlowerErrorIndicates whether the blower 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.
NOTE: Fan packs are also referred to as Power Module Cooling Devices. SEQUENCE OF FanPackLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.6.1 |
fanPackLEDsEntryFan Pack LEDs information entry FanPackLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1 |
ledFanPackIndexFan Pack LEDs table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1.1 |
ledFanPackIdThe numeric fan pack ID.ro 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.ro INTEGER .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.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.6.1.1.4 |
mtStatusLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.7 |
mtStatusLEDsTableTable of Media Tray Status LEDs information.
NOTE: This MIB object is for BladeCenter HT only. SEQUENCE OF MtStatusLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.7.1 |
mtStatusLEDsEntryMedia Tray Status LEDs information entry.
NOTE: This MIB object is for BladeCenter HT only. MtStatusLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.7.1.1 |
ledMediaTrayIndexMedia Tray Status LEDs table index.
NOTE: This MIB object is for BladeCenter HT only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.7.1.1.1 |
ledMediaTrayIdThe numeric Media Tray ID.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.7.1.1.2 |
ledMediaTrayExistsIndicates whether the Media Tray exists or not.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.7.1.1.3 |
ledMediaTrayFaultIndicates whether the Media Tray Fault LED is on or off.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.7.1.1.5 |
tapStatusLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.8 |
tapExistsIndicates whether the Alarm Panel exists or not.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.8.3 |
tapFRRLEDIndicates whether the Alarm Panel Safe To Remove LED is on or off.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.8.4 |
tapFaultLEDIndicates whether the Alarm Panel Fault LED is on or off.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.8.5 |
ncStatusLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.9 |
ncStatusLEDsTableTable of Network Clock Status LEDs information.
NOTE: This MIB object is for BladeCenter HT only.deprecated SEQUENCE OF NcStatusLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.9.1 |
ncStatusLEDsEntryNetwork Clock Status LEDs information entry.
NOTE: This MIB object is for BladeCenter HT only.deprecated NcStatusLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.9.1.1 |
ledNetworkClockIndexNetwork Clock Status LEDs table index.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.9.1.1.1 |
ledNetworkClockIdThe numeric Network Clock ID.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.9.1.1.2 |
ledNetworkClockExistsIndicates whether the Network Clock exists or not.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.9.1.1.3 |
ledNetworkClockFRRIndicates whether the Network Clock Safe To Remove LED is on or off.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.9.1.1.4 |
ledNetworkClockFaultIndicates whether the Network Clock Fault LED is on or off.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.9.1.1.5 |
mxStatusLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.10 |
mxStatusLEDsTableTable of Multiplexer Expansion Module Status LEDs information.
NOTE: This MIB object is for BladeCenter HT only. SEQUENCE OF MxStatusLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.10.1 |
mxStatusLEDsEntryMultiplexer Expansion Module Status LEDs information entry.
NOTE: This MIB object is for BladeCenter HT only. MxStatusLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.10.1.1 |
ledMuxIndexMultiplexer Expansion Module Status LEDs table index.
NOTE: This MIB object is for BladeCenter HT only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.10.1.1.1 |
ledMuxIdThe numeric Multiplexer Expansion Module ID.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.10.1.1.2 |
ledMuxExistsIndicates whether the Multiplexer Expansion Module exists or not.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.10.1.1.3 |
ledMuxFRRIndicates whether the Multiplexer Expansion Module Safe To Remove LED is on or off.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.10.1.1.4 |
ledMuxFaultIndicates whether the Multiplexer Expansion Module Fault LED is on or off.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.10.1.1.5 |
storageLEDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.8.11 |
storageLEDsTableTable of storage module LEDs information.
NOTE: This MIB object is for BladeCenter S only. SEQUENCE OF StorageLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.11.1 |
storageLEDsEntryStorage Module LEDs information entry
NOTE: This MIB object is for BladeCenter S only. StorageLEDsEntry .1.3.6.1.4.1.2.3.51.2.2.8.11.1.1 |
ledStorageIndexStorage Module LEDs table index.
NOTE: This MIB object is for BladeCenter S only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.8.11.1.1.1 |
ledStorageIdThe numeric storage module ID.
NOTE: This MIB object is for BladeCenter S only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.11.1.1.2 |
ledStorageExistsIndicates whether the storage module specified exists or not.
NOTE: This MIB object is for BladeCenter S only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.11.1.1.3 |
ledStorageErrorIndicates the status of the storage module error LED.
NOTE: This MIB object is for BladeCenter S only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.8.11.1.1.4 |
telcoSystemHealth OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.9 |
telcoSystemHealthStatIndicates status of system health for the system in which the
MM resides. Value of 'critical' indicates a non-recoverable
service affecting condition has occurred that requires an
immediate action. A value of 'major' indicates a critical
service affecting condition has occurred that requires an urgent
action. A value of 'minor' indicates a non-service affecting
condition has occurred. Corrective action should be taken in
order to prevent a more serious fault. A value of 'normal'
indicates that the system is operating normally. Severity level
with '-power' indicates the failure relates to the power resource.
NOTE: This MIB object is for BladeCenter T only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.9.1 |
telcoSystemHealthSummaryTableTable of System Health summary. Contains more detailed
information about the reasons for the overall system
health status.
NOTE: This MIB object is for BladeCenter T only.
NOTE: This table may contain one entry if no alarms are in progress. That one entry,
if present, contains no alarms but a message of 'Good' in the severity object. SEQUENCE OF TelcoSystemHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.2.9.2 |
telcoSystemHealthSummaryEntryBladeCenter T System Health Summary entry.
NOTE: This MIB object is for BladeCenter T only. TelcoSystemHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.2.9.2.1 |
telcoSystemHealthSummaryIndexBladeCenter T System Health Summary Index.
NOTE: This MIB object is for BladeCenter T only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.9.2.1.1 |
telcoSystemHealthSummarySeverityBladeCenter T System Health Summary Severity. The values
and meanings are as follows:
0x06 Critical-Power
0x05 Critical
0x04 Major-Power
0x03 Major
0x02 Minor-Power
0x01 Minor
0xFF Normal
NOTE: This MIB object is for BladeCenter T only.
NOTE: If no alarms are in progress, this object contains 'Good'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.9.2.1.2 |
telcoSystemHealthSummaryDescriptionBladeCenter T System Health Summary Description.
NOTE: This MIB object is for BladeCenter T only.
NOTE: If no alarms are in progress, this object contains 'No alarm events'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.9.2.1.3 |
telcoSystemHealthSummaryEventNameBladeCenter T System Health Summary Event Name.
NOTE: This MIB object is for BladeCenter T only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.9.2.1.4 |
telcoSystemHealthSummaryEventKeyIDBladeCenter T System Health Summary Event Key ID. An octet string
expressed as 'mmm:ggg:iii:aaa:sss' where:
m : Module ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
g : Gen ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
i : GenInfo ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
a : Alarm ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
s : Alarm severity value of decimal digits(1-255) or
blank space(s) for leading zero(s)
NOTE: This MIB object is for BladeCenter T only.
NOTE: If no alarms are in progress, this object contains 'No alarm events'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.9.2.1.5 |
telcoSystemHealthSummaryAcknowledgeBladeCenter T System Health Summary Acknowledge. Indicates whether the
alarm event is acknowledged or unacknowledged.
NOTE: This MIB object is for BladeCenter T only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.9.2.1.6 |
telcoSystemHealthSummaryAssertTimeBladeCenter T System Health Summary Assert Time.
NOTE: This MIB object is for BladeCenter T only.
NOTE: If no alarms are in progress, this object contains 'No alarm events'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.9.2.1.7 |
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 |
fuelGaugeFirstPowerModuleFuel Gauge Table First Power Module capacity in Watts in the power domain.
NOTE: First power module in power domain 1 and 2 is in bay 1
and 3 respectively.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.4 |
fuelGaugeSecondPowerModuleFuel Gauge Table Second Power Module capacity in Watts in the power domain.
NOTE: Second power module in power domain 1 and 2 is in bay 2
and 4 respectively.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.1.1.1.5 |
fuelGaugePowerManagementPolicySettingFuel Gauge Table for the Power Management Policy Setting for each power domain.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.
In addition, note that the first three enumerated choices above are
referred to with updated nomenclature, as follows:
redundantWithoutPerformanceImpact(0) equals Redundant Power Modules
redundantWithPerformanceImpact(1) equals Power Modules with Blade
Throttling Allowed
nonRedundant(2) equals Basic Power Managementro 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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.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.
NOTE: 1) Power is always reserved in domain 1 for two management modules and
two I/O modules. 2) Power is reserved for I/O modules installed in bay 3 and
4 (Powered on or standby). 3) Power is reserved for each installed Blade.
Blades in a standby state (not powered on) will reserve a certain amount power.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.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 Use
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.ro 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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.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.
NOTE: Blowers are also referred to as Chassis Cooling Devices.
NOTE: Fan packs are also referred to as Power Module Cooling Devices. 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 in the BladeCenter:
notApplicable(1),
notApplicable(2),
blowerBay1(3),
blowerBay2(4),
managementModuleBay1(5),
managementModuleBay2(6),
switchModuleBay1(7),
switchModuleBay2(8),
switchModuleBay3(9),
switchModuleBay4(10),
serverBladeBay1(11),
serverBladeBay2(12),
serverBladeBay3(13),
serverBladeBay4(14),
serverBladeBay5(15),
serverBladeBay6(16),
notApplicable(17)
The following Bay Number IDs are used in the BladeCenter H:
notApplicable(1),
notApplicable(2),
fanPackBay1(3),
fanPackBay2(4),
fanPackBay3(5),
fanPackBay4(6),
managementModuleBay1(7),
managementModuleBay2(8),
ioModuleBay1(9),
ioModuleBay2(10),
ioModuleBay3(11),
ioModuleBay4(12),
ioModuleBay7(13),
ioModuleBay8(14),
ioModuleBay9(15),
ioModuleBay10(16),
serverBladeBay1(17),
serverBladeBay2(18),
serverBladeBay3(19),
serverBladeBay4(20),
serverBladeBay5(21),
serverBladeBay6(22),
serverBladeBay7(23),
notApplicable(24)
The following Bay Number IDs are used in the BladeCenter T:
notApplicable(1),
notApplicable(2),
blowerBay1(3),
blowerBay2(4),
blowerBay3(5) (if Power Domain 2 is not available),
blowerBay4(6) (if Power Domain 2 is not available),
managementModuleBay1(7),
managementModuleBay2(8),
switchModuleBay1(9),
switchModuleBay2(10),
switchModuleBay3(11),
switchModuleBay4(12),
serverBladeBay1(13),
serverBladeBay2(14),
serverBladeBay3(15),
serverBladeBay4(16),
notApplicable(17)
The following Bay Number IDs are used in the BladeCenter HT:
notApplicable(1),
mediatrayBay1(2),
mediatrayBay2(3),
fanPackBay1(4),
fanPackBay2(5),
fanPackBay3(6),
fanPackBay4(7),
blowerBay1(8),
blowerBay2(9),
blowerBay3(10),
blowerBay4(11),
networkclockBay1(12),
networkclockBay2(13),
midplaneelectroBay1(14),
midplaneelectroBay2(15),
notApplicable(16),
managementModuleBay1(17),
managementModuleBay2(18),
ioModuleBay1(19),
ioModuleBay2(20),
ioModuleBay3(21),
ioModuleBay4(22),
serverBladeBay1(23),
serverBladeBay2(24),
serverBladeBay3(25),
serverBladeBay4(26),
serverBladeBay5(27),
serverBladeBay6(28),
notApplicable(29)
The following Bay Number IDs are used in the BladeCenter S:
notApplicable(1),
notApplicable(2),
fanPackBay1(3),
fanPackBay2(4),
fanPackBay3(5),
fanPackBay4(6),
blowerBay1(7),
blowerBay2(8),
blowerBay3(9),
blowerBay4(10),
storageModuleBay1(11),
storageModuleBay2(12),
managementModuleBay(13),
ioModuleBay1(14),
ioModuleBay2(15),
ioModuleBay3(16),
ioModuleBay4(17),
serverBladeBay1(18),
serverBladeBay2(19),
serverBladeBay3(20),
serverBladeBay4(21),
serverBladeBay5(22),
serverBladeBay6(23),
notApplicable(24)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. When a 1200W or 1400W power module is
installed in the domain the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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. When a 1200W or 1400W power module is installed
in the domain the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.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 |
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 |
powerDomain2 OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.3 |
powerDomain2TableTable of Power Domain 2.
NOTE: Blowers are also referred to as Chassis Cooling Devices.
NOTE: Fan packs are also referred to as Power Module Cooling Devices. SEQUENCE OF PowerDomain2Entry .1.3.6.1.4.1.2.3.51.2.2.10.3.1 |
powerDomain2EntryFuel Gauge entry PowerDomain2Entry .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1 |
pd2IndexPower Domain 2 Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.1 |
pd2BayNumberPower Domain 2 Table Bay Number.
The following Bay Number IDs are used in the BladeCenter:
serverBladeBay7(1),
serverBladeBay8(2),
serverBladeBay9(3),
serverBladeBay10(4),
serverBladeBay11(5),
serverBladeBay12(6),
serverBladeBay13(7),
serverBladeBay14(8),
notApplicable(9)
The following Bay Number IDs are used in the BladeCenter H:
notApplicable(1),
notApplicable(2),
fanPackBay1(3),
fanPackBay2(4),
fanPackBay3(5),
fanPackBay4(6),
managementModuleBay1(7),
managementModuleBay2(8),
ioModuleBay1(9),
ioModuleBay2(10),
ioModuleBay3(11),
ioModuleBay4(12),
ioModuleBay7(13),
ioModuleBay8(14),
ioModuleBay9(15),
ioModuleBay10(16),
serverBladeBay8(17),
serverBladeBay9(18),
serverBladeBay10(19),
serverBladeBay11(20),
serverBladeBay12(21),
serverBladeBay13(22),
serverBladeBay14(23),
notApplicable(24)
The following Bay Number IDs are used in the BladeCenter T:
blowerBay3(1),
blowerBay4(2),
serverBladeBay5(3),
serverBladeBay6(4),
serverBladeBay7(5),
serverBladeBay8(6),
notApplicable(7),
notApplicable(8),
notApplicable(9)
The following Bay Number IDs are used in the BladeCenter HT:
fanPackBay1(1),
fanPackBay2(2),
fanPackBay3(3),
fanPackBay4(4),
blowerBay1(5),
blowerBay2(6),
blowerBay3(7),
blowerBay4(8),
ioModuleBay7(9),
ioModuleBay8(10),
ioModuleBay9(11),
ioModuleBay10(12),
serverBladeBay7(13),
serverBladeBay8(14),
serverBladeBay9(15),
serverBladeBay10(16),
serverBladeBay11(17),
serverBladeBay12(18),
notApplicable(19)ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.2 |
pd2BladePrimarySlotPower Domain 2 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.3.1.1.3 |
pd2ModuleStatusPower Domain 2 Table Module throttle status.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.4 |
pd2ModuleNamePower Domain 2 Table Module Name.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.5 |
pd2ModuleStatePower Domain 2 Table Power State.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.6 |
pd2ModuleAllocatedPowerCurrentPower Domain 2 Table Allocated Power Current indicates the current power
allocation for the module. When a 1200W or 1400W power module is
installed in the domain the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.3.1.1.7 |
pd2ModuleAllocatedPowerMaxPower Domain 2 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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable. In addition
the power consumption in this domain will not be monitored.
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.3.1.1.8 |
pd2ModuleAllocatedPowerMinPower Domain 2 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. When a 1200W or 1400W power module is
installed in the domain the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.3.1.1.9 |
pd2ModuleCPUDutyCyclesPower Domain 2 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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.3.1.1.10 |
pd2ModuleThrottlePower Domain 2 Table Module Throttle indicates whether the
server blade may be allowed to throttle or not.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.11 |
pd2ModulePowerCapabilitiesPower Domain 2 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.3.1.1.12 |
pd2ModuleMeasuredOrStaticPower Domain 2 Table Module Measured Or Static.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.3.1.1.13 |
powerDomain2PowerTrending OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.3.3 |
pd2PowerTrendingPeriodSpecify time period for power domain 2 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.3.3.1 |
pd2PowerTrendingSampleTableTable of Power Domain 2 Power Trending Sample Information. SEQUENCE OF Pd2PowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.3.3.10 |
pd2PowerTrendingSampleEntryPower Domain 2 Power Trending Sample entry. Pd2PowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.3.3.10.1 |
pd2PowerTrendingSampleIndexPower Domain 2 Power Trending Sample Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.3.3.10.1.1 |
pd2PowerTrendingSampleTimeStampPower Domain 2 Power Trending Sample Table Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.3.3.10.1.2 |
pd2PowerTrendingSampleAvePower Domain 2 Power Trending Sample Table Average Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.3.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.
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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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.
When a 1200W or 1400W power module is installed in the domain
the power management policy will not be applicable.
In addition the power consumption in this domain will not be monitored.
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 |
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.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 |
bladePowerTrendingSampleTableTable of Blade Module Power Trending Information. SEQUENCE OF BladePowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10 |
bladePowerTrendingSampleEntryBlade Module Power Trending Sample entry. BladePowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10.1 |
bladePowerTrendingSampleIndexBlade Module Power Trending Sample Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10.1.1 |
bladePowerTrendingSampleIdBlade Module Power Trending Sample Table Blade Id.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10.1.2 |
bladePowerTrendingSampleTimeStampBlade Module Power Trending Sample Table Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10.1.3 |
bladePowerTrendingSampleMaxBlade Module Power Trending Sample Table Maximum Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10.1.4 |
bladePowerTrendingSampleMinBlade Module Power Trending Sample Table Minimum Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10.1.5 |
bladePowerTrendingSampleAveBlade Module Power Trending Sample Table Average Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.1.3.10.1.6 |
switchDetails OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.4.2 |
switchPowerTrending OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3 |
switchPowerTrendingPeriodSpecify time period for switch module power trending information table view.
NOTE: This time period should be configured before displaying the
following Power Trending Information table for Switch Module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.1 |
switchPowerTrendingSwitchIdSwitch Module Power Trending Switch Id.
NOTE: The Switch Id should be configured before displaying the
switchPowerTrendingTable.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.2 |
switchPowerTrendingSampleTableTable of Switch Module Power Trending Information. SEQUENCE OF SwitchPowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10 |
switchPowerTrendingSampleEntrySwitch Module Power Trending Sample entry. SwitchPowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10.1 |
switchPowerTrendingSampleIndexSwitch Module Power Trending Sample Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10.1.1 |
switchPowerTrendingSampleIdSwitch Module Power Trending Sample Table Switch Id.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10.1.2 |
switchPowerTrendingSampleTimeStampSwitch Module Power Trending Sample Table Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10.1.3 |
switchPowerTrendingSampleMaxSwitch Module Power Trending Sample Table Maximum Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10.1.4 |
switchPowerTrendingSampleMinSwitch Module Power Trending Sample Table Minimum Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10.1.5 |
switchPowerTrendingSampleAveSwitch Module Power Trending Sample Table Average Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.2.3.10.1.6 |
blowerDetails OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.4.3 |
blowerPowerTrending OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3 |
blowerPowerTrendingPeriodSpecify time period for blower module power trending information table view.
NOTE: This time period should be configured before displaying the
following Power Trending Information table for Blower Module.
NOTE: Blowers are also referred to as Chassis Cooling Devices.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.1 |
blowerPowerTrendingBlowerIdBlower Module Power Trending Blower Id.
NOTE: The Blower Id should be configured before displaying the blowerPowerTrendingTable.
NOTE: Blowers are also referred to as Chassis Cooling Devices.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.2 |
blowerPowerTrendingSampleTableTable of Blower Module Power Trending Information.
NOTE: Blowers are also referred to as Chassis Cooling Devices. SEQUENCE OF BlowerPowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10 |
blowerPowerTrendingSampleEntryBlower Module Power Trending Sample entry. BlowerPowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10.1 |
blowerPowerTrendingSampleIndexBlower Module Power Trending Sample Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10.1.1 |
blowerPowerTrendingSampleIdBlower Module Power Trending Sample Table Blower Id.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10.1.2 |
blowerPowerTrendingSampleTimeStampBlower Module Power Trending Sample Table Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10.1.3 |
blowerPowerTrendingSampleMaxBlower Module Power Trending Sample Table Maximum Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10.1.4 |
blowerPowerTrendingSampleMinBlower Module Power Trending Sample Table Minimum Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10.1.5 |
blowerPowerTrendingSampleAveBlower Module Power Trending Sample Table Average Power.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.4.3.3.10.1.6 |
chassisInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.5 |
chassisConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.5.1 |
chassisTotalDCPowerAvailableChassis total DC power available, which displays the total DC power available
for the entire chassis. It is the sum of the two power domains.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.1.1 |
chassisTotalACPowerInUsedChassis total AC power being used, which displays the total AC power
being consumed by all modules in the chassis. It also includes power
consumed by the blowers (chassis oooling devices) for the chassis.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.1.2 |
chassisTotalThermalOutputChassis total thermal output, which displays the thermal output
(load) in BTUs per hour. It is calculated based on the total AC
power in use. (1 Watt = 3.412 BTU/hour).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.1.3 |
chassisTrendingSampleIntervalChassis Power and Thermal Trending Sample Interval.
0 means no trending. the minimum interval is 10 minutes and the maximum
is 60 minutes, in 5 minute increments.rw INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.1.4 |
chassisPowerServiceThe chassis power service mode.
NOTE: This MIB object is for BCS only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.5.1.5 |
chassisPowerTrending OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.5.3 |
chassisPowerTrendingPeriodSpecify time period of power trending information.
NOTE: This time period should be configured before displaying the
following Power Trending Information table for Chassis.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.5.3.1 |
chassisPowerTrendingSampleTableTable of Chassis Power Trending Sample Information in specified time period. SEQUENCE OF ChassisPowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.3.10 |
chassisPowerTrendingSampleEntryChassis Power Trending Sample entry in specified time period. ChassisPowerTrendingSampleEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.3.10.1 |
chassisPowerTrendingSampleIndexChassis Power Trending Sample Index in specified time period.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.3.10.1.1 |
chassisPowerTrendingSampleTimeStampChassis Power Trending Sample Timestamp in specified time period.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.3.10.1.2 |
chassisPowerTrendingSampleAveChassis Power Trending Sample Average Power in specified time period.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.3.10.1.3 |
chassisThermalTrending OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.5.5 |
chassisThermalTrendingPeriodSpecify time period of thermal trending information.
NOTE: This time period should be configured before displaying the
following Thermal Trending Information table for Chassis.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.5.5.1 |
mt1ThermalTrendingTableTable of Media Tray 1 Thermal Trending Information. SEQUENCE OF Mt1ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.10 |
mt1ThermalTrendingEntryMedia Tray 1 Thermal Trending entry. Mt1ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.10.1 |
mt1ThermalTrendingIndexMedia Tray 1 Thermal Trending Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.5.10.1.1 |
mt1ThermalTrendingTimeStampMedia Tray 1 Thermal Trending Table Sample Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.10.1.2 |
mt1ThermalTrendingTemperatureMedia Tray 1 Thermal Trending Table Temperature.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.10.1.3 |
mt2ThermalTrendingTableTable of Media Tray 2 Thermal Trending Information.
NOTE: This MIB object is for BladeCenter HT only. SEQUENCE OF Mt2ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.15 |
mt2ThermalTrendingEntryMedia Tray 2 Thermal Trending entry.
NOTE: This MIB object is for BladeCenter HT only. Mt2ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.15.1 |
mt2ThermalTrendingIndexMedia Tray 2 Thermal Trending Table Index.
NOTE: This MIB object is for BladeCenter HT only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.5.15.1.1 |
mt2ThermalTrendingTimeStampMedia Tray 2 Thermal Trending Table Sample Timestamp.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.15.1.2 |
mt2ThermalTrendingTemperatureMedia Tray 2 Thermal Trending Table Temperature.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.15.1.3 |
blower1ThermalTrendingTableTable of Blower 1 Thermal Trending Information.
NOTE: Blowers are also referred to as Chassis Cooling Devices. SEQUENCE OF Blower1ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.20 |
blower1ThermalTrendingEntryBlower 1 Thermal Trending entry. Blower1ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.20.1 |
blower1ThermalTrendingIndexBlower 1 Thermal Trending Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.5.20.1.1 |
blower1ThermalTrendingTimeStampBlower 1 Thermal Trending Table Sample Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.20.1.2 |
blower1ThermalTrendingTemperatureBlower 1 Thermal Trending Table Temperature.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.20.1.3 |
blower2ThermalTrendingTableTable of Blower 2 Thermal Trending Information.
NOTE: Blowers are also referred to as Chassis Cooling Devices. SEQUENCE OF Blower2ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.30 |
blower2ThermalTrendingEntryBlower Thermal 2 Trending entry. Blower2ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.30.1 |
blower2ThermalTrendingIndexBlower 2 Thermal Trending Table Index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.5.30.1.1 |
blower2ThermalTrendingTimeStampBlower 2 Thermal Trending Table Sample Timestamp.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.30.1.2 |
blower2ThermalTrendingTemperatureBlower 2 Thermal Trending Table Temperature.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.30.1.3 |
blower3ThermalTrendingTableTable of Blower 3 Thermal Trending Information.
NOTE: This MIB object is for BladeCenter T only.
NOTE: Blowers are also referred to as Chassis Cooling Devices. SEQUENCE OF Blower3ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.40 |
blower3ThermalTrendingEntryBlower 3 Thermal Trending entry.
NOTE: This MIB object is for BladeCenter T only. Blower3ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.40.1 |
blower3ThermalTrendingIndexBlower 3 Thermal Trending Table Index.
NOTE: This MIB object is for BladeCenter T only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.5.40.1.1 |
blower3ThermalTrendingTimeStampBlower 3 Thermal Trending Table Sample Timestamp.
NOTE: This MIB object is for BladeCenter T only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.40.1.2 |
blower3ThermalTrendingTemperatureBlower 3 Thermal Trending Table Temperature.
NOTE: This MIB object is for BladeCenter T only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.40.1.3 |
blower4ThermalTrendingTableTable of Blower 4 Thermal Trending Information.
NOTE: This MIB object is for BladeCenter T only. SEQUENCE OF Blower4ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.50 |
blower4ThermalTrendingEntryBlower 4 Thermal Trending entry.
NOTE: This MIB object is for BladeCenter T only.
NOTE: Blowers are also referred to as Chassis Cooling Devices. Blower4ThermalTrendingEntry .1.3.6.1.4.1.2.3.51.2.2.10.5.5.50.1 |
blower4ThermalTrendingIndexBlower 4 Thermal Trending Table Index.
NOTE: This MIB object is for BladeCenter T only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.5.5.50.1.1 |
blower4ThermalTrendingTimeStampBlower 4 Thermal Trending Table Sample Timestamp.
NOTE: This MIB object is for BladeCenter T only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.50.1.2 |
blower4ThermalTrendingTemperatureBlower 4 Thermal Trending Table Temperature.
NOTE: This MIB object is for BladeCenter T only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.5.5.50.1.3 |
powerPolicyInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.10.6 |
powerPolicyTableTable of Power Policy information for all power domains. Reading this
table can tell you about the available power policies that can be
configured for a domain and also which is currently selected. The
powerPolicyActivate object can also be SET to select which policy
should be active for a given power domain. SEQUENCE OF PowerPolicyEntry .1.3.6.1.4.1.2.3.51.2.2.10.6.1 |
powerPolicyEntryPower Policy Entry PowerPolicyEntry .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1 |
powerPolicyIndexThe unique idenitifier of a row in the powerPolicyTable.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1.1 |
powerPolicyPowerDomainNumberThe power domain number which this row is associated with.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1.2 |
powerPolicyNameThe short name of the power policy. The following are the possible
names and their detailed description:
Power Module Redundancy
Intended for a single AC power source into the chassis
where each Power Module is on its own dedicated circuit.
Total allowed power draw 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 blade
operation. Multiple Power Module failures can cause
the chassis to power off. Note that some blades may not be
allowed to power on if doing so would exceed the policy power
limit.
Power Module Redundancy with Blade Throttling Allowed
Very similar to the Power Module Redundancy policy. This
policy allows you to draw more total power; however, capable
blades may be allowed to throttle down if one Power Module fails.
Basic Power Management
Total allowed power is higher than other policies and is limited only
by the total power capacity of all the Power Modules up to the maximum
of chassis power rating. This is the least conservative approach, since
it does not provide any protection for AC power source or Power Module
failure. If any single power supply fails, blade and/or chassis
operation may be affected.
AC Power Source Redundancy
Intended for dual AC power sources into the chassis. Total
allowed power draw is limited to the capacity of two Power
Modules. This is the most conservative approach and is
recommended when all four Power Modules are installed.
When the chassis is correctly wired with dual AC power
sources, one AC power source can fail without affecting
blade operation. Note that some blades may not be
allowed to power on if doing so would exceed the policy
power limit.
AC Power Source Redundancy with Blade Throttling Allowed
Very similar to the AC Power Source Redundancy policy. This policy
allows you to draw more total power; however, capable blades
may be allowed to throttle down if one AC power source fails.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1.3 |
powerPolicyPwrSupplyFailureLimitThe maximum number of power supplies that can fail in a chassis
while still providing redundancy.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1.4 |
powerPolicyMaxPowerLimitThe maximum power available (in watts), based on the number of power modules and
the Power Management Policy setting.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1.5 |
powerPolicyEstimatedUtilizationThe estimated utilization (as a percentage) based on current power usage.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1.6 |
powerPolicyActivateWhen read, this object provides the status of this power policy. If the
value is enabled(1), it means this is the active power policy for the
associated domain. When set to a value of enabled(1), the power policy
will be made the active one for the associated domain. A set of disabled(0)
is not allowed.
The SET may fail when the user goes from a less restrictive policy
to a more restrictive policy, e.g. no power management to redundant power
modules.
This happens because the AMM might have allocated more power for components
in the less restrictive policy. Then if a user wants to go to a more restrictive
policy, the power available may be lower than what was already allocated.
The SET should always succeed if a user goes from a more restrictive to
a less restrictive policy.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.10.6.1.1.7 |
frontbezel OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.12 |
frontbezelExistsIndicates whether the front bezel is installed or not.
NOTE: This MIB object is for BladeCenter HT only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.12.1 |
users OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.17 |
mmUsers OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.17.1 |
currentlyLoggedInTableTable of MM users currently logged in.
NOTE: This MIB object is for AMM only. SEQUENCE OF CurrentlyLoggedInEntry .1.3.6.1.4.1.2.3.51.2.2.17.1.1 |
currentlyLoggedInEntryMM users currently logged in entries.
NOTE: This MIB object is for AMM only. CurrentlyLoggedInEntry .1.3.6.1.4.1.2.3.51.2.2.17.1.1.1 |
currentlyLoggedInEntryIndexIndex for MM users currently logged in.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.17.1.1.1.1 |
currentlyLoggedInEntryUserIdName for MM users currently logged in.
NOTE: 'Default SNMPv1 user' indicates an internal user used by SNMPv1 agent.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.17.1.1.1.2 |
currentlyLoggedInEntryAccMethodAccess method for MM users currently logged in.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.17.1.1.1.3 |
monitorThresholds OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.20 |
voltageThresholds OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.20.2 |
voltageThresholdsTableTable of voltage threshold entries.
NOTE: This MIB object is for BladeCenter only. SEQUENCE OF VoltageThresholdsEntry .1.3.6.1.4.1.2.3.51.2.2.20.2.1 |
voltageThresholdsEntryVoltage threshold entries.
NOTE: This MIB object is for BladeCenter only. VoltageThresholdsEntry .1.3.6.1.4.1.2.3.51.2.2.20.2.1.1 |
voltageThresholdEntryIndexIndex for voltage threshold entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.20.2.1.1.1 |
voltageThresholdEntryNameVoltage threshold entry null terminated string that
contains the power supply's name, for example '+5V'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.20.2.1.1.2 |
voltageThresholdEntryCurrentValueVoltage reading expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.20.2.1.1.3 |
voltageThresholdEntryWarningHighValueVoltage threshold reading expressed in Volts(V).
If the voltage rises above this value, a warning
alert/event, if enabled, will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.20.2.1.1.6 |
voltageThresholdEntryWarningResetHighValueVoltage threshold reading expressed in Volts(V).
If the voltage rises above this value and
if a warning alert/event had previously been
created, then the alert/event will be reset.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.20.2.1.1.7 |
voltageThresholdEntryWarningLowValueVoltage threshold reading expressed in Volts(V).
If the voltage drops below this value, a warning
alert/event, if enabled, will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.20.2.1.1.10 |
voltageThresholdEntryWarningResetLowValueVoltage threshold reading expressed in Volts(V).
If the voltage drops below this value and
if a warning alert/event had previously been
created, then the alert/event will be reset.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.20.2.1.1.11 |
vpdInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21 |
chassisVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.1 |
bladeCenterVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.1.1 |
bladeCenterVpdMachineTypeMachine type VPD information (from System BIOS). This field must be four
alpha numeric characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.1 |
bladeCenterVpdMachineModelMachine model VPD information (from System BIOS). This field must be three
alpha numeric characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.2 |
bladeCenterSerialNumberMachine serial number VPD information (from System BIOS). This field must be
seven alpha numeric characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.3 |
bladeCenterUUIDMachine UUID (Universal Unique ID information) (from System BIOS). This field
must be 32 alpha numeric characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.4 |
bladeCenterManufacturingIdMachine chassis manufacturing ID.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.5 |
bladeCenterHardwareRevisionMachine chassis hardware revision.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.1.1.6 |
bladeCenterFruNumberMachine chassis FRU number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.7 |
bladeCenterManufDateMachine chassis manufacture date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.8 |
bladeCenterPartNumberMachine chassis part number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.9 |
bladeCenterFruSerialMachine chassis FRU serial number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.10 |
bladeCenterManufacturingIDNumberMachine chassis manufacturer ID Number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.11 |
bladeCenterProductIdMachine chassis product ID.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.12 |
bladeCenterSubManufacturerIdMachine chassis subsystem manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.13 |
bladeCenterCleiMachine chassis Common Language Equipment Identification (CLEI).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.14 |
bladeCenterDirectSerialAttachPresence of the Direct Serial Attach Module.
NOTE: This MIB object is for BCS only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.1.1.15 |
bladeCenterHardwareRevisionStringMachine chassis hardware revision in string format.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.1.1.16 |
mmHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.2 |
mmHardwareVpdTableTable of the management module hardware components.
For consistent results, view as a table and not as individual entries. SEQUENCE OF MmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.2.1 |
mmHardwareVpdEntryManagement module hardware VPD entry.
For consistent results, view as a table and not as individual entries. MmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1 |
mmHardwareVpdIndexManagement module hardware VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.1 |
mmHardwareVpdBayNumberManagement module hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.2 |
mmHardwareVpdManufacturingIdManagement module hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.3 |
mmHardwareVpdFruNumberManagement module hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.4 |
mmHardwareVpdHardwareRevisionManagement module hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.5 |
mmHardwareVpdUuidManagement module hardware VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.6 |
mmHardwareVpdManufDateManagement module hardware VPD manufacture date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.7 |
mmHardwareVpdPartNumberManagement module hardware VPD Part number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.8 |
mmHardwareVpdFruSerialManagement module hardware VPD FRU serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.9 |
mmHardwareVpdManufacturingIDNumberManagement module hardware VPD manufacturer ID Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.10 |
mmHardwareVpdProductIdManagement module hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.11 |
mmHardwareVpdSubManufacturerIdManagement module hardware VPD subsystem manufacturer.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.12 |
mmHardwareVpdCleiManagement module hardware VPD Common
Language Equipment Identification (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.13 |
mmHardwareVpdHardwareRevisionStringManagement module hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.1.1.14 |
mmInpHardwareVpdTableTable of the management module interposer hardware components.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only. SEQUENCE OF MmInpHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.2.2 |
mmInpHardwareVpdEntryManagement module Interposer hardware VPD entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only. MmInpHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1 |
mmInpHardwareVpdIndexManagement module Interposer hardware VPD index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.1 |
mmInpHardwareVpdBayNumberManagement module Interposer hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.2 |
mmInpHardwareVpdManufacturingIdManagement module Interposer hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.3 |
mmInpHardwareVpdFruNumberManagement module Interposer hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.4 |
mmInpHardwareVpdHardwareRevisionManagement module Interposer hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.5 |
mmInpHardwareVpdUuidManagement module Interposer hardware VPD UUID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.6 |
mmInpHardwareVpdManufDateManagement module Interposer hardware VPD manufacture date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.7 |
mmInpHardwareVpdPartNumberManagement module Interposer hardware VPD Part number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.8 |
mmInpHardwareVpdFruSerialManagement module Interposer hardware VPD FRU serial number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.9 |
mmInpHardwareVpdManufacturingIDNumberManagement module Interposer hardware VPD manufacturer ID Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.10 |
mmInpHardwareVpdProductIdManagement module Interposer hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.11 |
mmInpHardwareVpdSubManufacturerIdManagement module Interposer hardware VPD subsystem manufacturer.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.12 |
mmInpHardwareVpdCleiManagement module Interposer hardware VPD Common
Language Equipment Identification (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.13 |
mmInpHardwareVpdHardwareRevisionStringManagement module Interposer hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then this version of this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.2.2.1.14 |
mmFirmwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.3 |
mmMainApplVpdTableTable of MM Firmware VPD. SEQUENCE OF MmMainApplVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.1 |
mmMainApplVpdEntryMM Firmware VPD entry. MmMainApplVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.1.1 |
mmMainApplVpdIndexFirmware VPD index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.3.1.1.1 |
mmMainApplVpdNameFirmware VPD name description.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.1.1.2 |
mmMainApplVpdBuildIdFirmware VPD build identification.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.1.1.3 |
mmMainApplVpdRevisonNumberFirmware VPD revision number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.1.1.4 |
mmMainApplVpdFilenameFirmware VPD file name.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.1.1.5 |
mmMainApplVpdBuildDateFirmware VPD build date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.1.1.6 |
mmBootROMVpdTableTable of MM Firmware VPD.
NOTE: This MIB object is for MM only.
NOTE: This table is deprecated and no longer supported.deprecated SEQUENCE OF MmBootROMVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.2 |
mmBootROMVpdEntryMM Firmware VPD entry.
NOTE: This MIB object is for MM only.
NOTE: This table is deprecated and no longer supported.deprecated MmBootROMVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.2.1 |
mmBootROMVpdIndexFirmware VPD index.
NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.3.2.1.1 |
mmBootROMVpdNameFirmware VPD name description.
NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.2.1.2 |
mmBootROMVpdBuildIdFirmware VPD build identification.
NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.2.1.3 |
mmBootROMVpdRevisonNumberFirmware VPD revision number.
NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.2.1.4 |
mmBootROMVpdFilenameFirmware VPD file name.
NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.2.1.5 |
mmBootROMVpdBuildDateFirmware VPD build date.
NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.2.1.6 |
mmRemoteControlVpdTableTable of MM Firmware VPD.
NOTE: This MIB object is for MM only.
NOTE: This table is deprecated and no longer supported.deprecated SEQUENCE OF MmRemoteControlVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.3 |
mmRemoteControlVpdEntryMM Firmware VPD entry.
NOTE: This table is deprecated and no longer supported.deprecated MmRemoteControlVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.3.1 |
mmRemoteControlVpdIndexFirmware VPD index.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.3.3.1.1 |
mmRemoteControlVpdNameFirmware VPD name description.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.3.1.2 |
mmRemoteControlVpdBuildIdFirmware VPD build identification.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.3.1.3 |
mmRemoteControlVpdRevisonNumberFirmware VPD revision number.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.3.1.4 |
mmRemoteControlVpdFilenameFirmware VPD file name.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.3.1.5 |
mmRemoteControlVpdBuildDateFirmware VPD build date.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.3.1.6 |
mmPS2toUSBConvVpdTableTable of MM Firmware VPD.
NOTE: This MIB object is for MM only.
NOTE: This table is deprecated and no longer supported.deprecated SEQUENCE OF MmPS2toUSBConvVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.4 |
mmPS2toUSBConvVpdEntryMM Firmware VPD entry.
NOTE: This table is deprecated and no longer supported.deprecated MmPS2toUSBConvVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.4.1 |
mmPS2toUSBConvVpdIndexFirmware VPD index.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.3.4.1.1 |
mmPS2toUSBConvVpdNameFirmware VPD name description.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.4.1.2 |
mmPS2toUSBConvVpdBuildIdFirmware VPD build identification.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.4.1.3 |
mmPS2toUSBConvVpdRevisonNumberFirmware VPD revision number.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.4.1.4 |
mmPS2toUSBConvVpdFilenameFirmware VPD file name.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.4.1.5 |
mmPS2toUSBConvVpdBuildDateFirmware VPD build date.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.4.1.6 |
mmToUSBIntfVpdTableTable of MM Firmware VPD.
NOTE: This MIB object is for MM only.
NOTE: This table is deprecated and no longer supported.deprecated SEQUENCE OF MmToUSBIntfVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.5 |
mmToUSBIntfVpdEntryMM Firmware VPD entry.
NOTE: This table is deprecated and no longer supported.deprecated MmToUSBIntfVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.3.5.1 |
mmToUSBIntfVpdIndexFirmware VPD index.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.3.5.1.1 |
mmToUSBIntfVpdNameFirmware VPD name description.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.5.1.2 |
mmToUSBIntfVpdBuildIdFirmware VPD build identification.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.5.1.3 |
mmToUSBIntfVpdRevisonNumberFirmware VPD revision number.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.5.1.4 |
mmToUSBIntfVpdFilenameFirmware VPD file name.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.5.1.5 |
mmToUSBIntfVpdBuildDateFirmware VPD build date.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.3.5.1.6 |
bladeHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.4 |
bladeHardwareVpdTableTable of VPD information for the blade hardware components.
For consistent results, view as a table and not as individual entries. SEQUENCE OF BladeHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.1 |
bladeHardwareVpdEntryBlade hardware VPD entry.
For consistent results, view as a table and not as individual entries. BladeHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1 |
bladeHardwareVpdIndexBlade hardware VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.1 |
bladeHardwareVpdBayNumberBlade hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.2 |
bladeHardwareVpdManufacturingIdBlade hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.3 |
bladeHardwareVpdFruNumberBlade hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.4 |
bladeHardwareVpdHardwareRevisionBlade hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.5 |
bladeHardwareVpdSerialNumberBlade hardware VPD serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.6 |
bladeHardwareVpdMachineTypeBlade hardware VPD machine type.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.7 |
bladeHardwareVpdUuidBlade hardware VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.8 |
bladeHardwareVpdManufDateBlade hardware VPD Manufacture Date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.9 |
bladeHardwareVpdPartNumberBlade hardware VPD Part number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.10 |
bladeHardwareVpdFruSerialBlade hardware VPD FRU serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.11 |
bladeHardwareVpdMachineModelBlade hardware VPD machine model.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.12 |
bladeHardwareVpdManufacturingIDNumberBlade hardware VPD Manufacturer ID Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.13 |
bladeHardwareVpdProductIdBlade hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.14 |
bladeHardwareVpdSubManufacturerIdBlade hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.15 |
bladeHardwareVpdCleiBlade hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.16 |
bladeHardwareVpdHardwareRevisionStringBlade hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.17 |
bladeDaughterVpdCardTypeBlade expansion card (daughter card) VPD type.
For consistent results, view as a table and not as individual entries.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.20 |
bladeDaughterVpdManufacturingIdBlade expansion card (daughter card) VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.21 |
bladeDaughterVpdFruNumberBlade expansion card (daughter card) VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.22 |
bladeDaughterVpdHardwareRevisionBlade expansion card (daughter card) VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.23 |
bladeDaughterVpdSerialNumberBlade expansion card (daughter card) VPD Serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.24 |
bladeDaughterVpdMachineTypeBlade expansion card (daughter card) VPD Machine type.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.25 |
bladeDaughterVpdUuidBlade expansion card (daughter card) VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.26 |
bladeDaughterVpdManufDateBlade expansion card (daughter card) VPD Manufacture date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.27 |
bladeDaughterVpdPartNumberBlade expansion card (daughter card) VPD Part number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.28 |
bladeDaughterVpdFruSerialBlade expansion card (daughter card) VPD FRU Serial.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.29 |
bladeDaughterVpdManufacturingIDNumberBlade expansion card (daughter card) VPD manufacturer ID Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.30 |
bladeDaughterVpdProductIdBlade expansion card (daughter card) VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.31 |
bladeDaughterVpdSubManufacturerIdBlade expansion card (daughter card) VPD subsystem manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.32 |
bladeDaughterVpdCleiBlade expansion card (daughter card) VPD
Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.33 |
bladeDaughterVpdHardwareRevisionStringBlade expansion card (daughter card) VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.1.1.34 |
bladeMACAddressVpdTableTable of MAC addresses of the blade and its expansion cards (daughter cards).
For consistent results, view as a table and not as individual entries. SEQUENCE OF BladeMACAddressVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.2 |
bladeMACAddressVpdEntryBlade MAC address entry.
For consistent results, view as a table and not as individual entries. BladeMACAddressVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1 |
bladeMACAddressVpdIndexBlade index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.1 |
bladeMACAddress1VpdBlade MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.2 |
bladeMACAddress2VpdBlade MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.3 |
bladeMACAddress3VpdBlade MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.4 |
bladeMACAddress4VpdBlade MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.5 |
bladeMACAddress5VpdBlade MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.6 |
bladeMACAddress6VpdBlade MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.7 |
bladeMACAddress7VpdBlade MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.8 |
bladeMACAddress8VpdBlade MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.9 |
bladeDaughterCard1MACAddress1VpdBlade expansion card (daughter card) 1 MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.10 |
bladeDaughterCard1MACAddress2VpdBlade expansion card (daughter card) 1 MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.11 |
bladeDaughterCard1MACAddress3VpdBlade expansion card (daughter card) 1 MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.12 |
bladeDaughterCard1MACAddress4VpdBlade expansion card (daughter card) 1 MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.13 |
bladeDaughterCard1MACAddress5VpdBlade expansion card (daughter card) 1 MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.14 |
bladeDaughterCard1MACAddress6VpdBlade expansion card (daughter card) 1 MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.15 |
bladeDaughterCard1MACAddress7VpdBlade expansion card (daughter card) 1 MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.16 |
bladeDaughterCard1MACAddress8VpdBlade expansion card (daughter card) 1 MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.17 |
bladeDaughterCard2MACAddress1VpdBlade expansion card (daughter card) 2 MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.18 |
bladeDaughterCard2MACAddress2VpdBlade expansion card (daughter card) 2 MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.19 |
bladeDaughterCard2MACAddress3VpdBlade expansion card (daughter card) 2 MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.20 |
bladeDaughterCard2MACAddress4VpdBlade expansion card (daughter card) 2 MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.21 |
bladeDaughterCard2MACAddress5VpdBlade expansion card (daughter card) 2 MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.22 |
bladeDaughterCard2MACAddress6VpdBlade expansion card (daughter card) 2 MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.23 |
bladeDaughterCard2MACAddress7VpdBlade expansion card (daughter card) 2 MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.24 |
bladeDaughterCard2MACAddress8VpdBlade expansion card (daughter card) 2 MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.25 |
bladeDaughterCard3MACAddress1VpdBlade expansion card (daughter card) 3 MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.26 |
bladeDaughterCard3MACAddress2VpdBlade expansion card (daughter card) 3 MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.27 |
bladeDaughterCard3MACAddress3VpdBlade expansion card (daughter card) 3 MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.28 |
bladeDaughterCard3MACAddress4VpdBlade expansion card (daughter card) 3 MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.29 |
bladeDaughterCard3MACAddress5VpdBlade expansion card (daughter card) 3 MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.30 |
bladeDaughterCard3MACAddress6VpdBlade expansion card (daughter card) 3 MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.31 |
bladeDaughterCard3MACAddress7VpdBlade expansion card (daughter card) 3 MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.32 |
bladeDaughterCard3MACAddress8VpdBlade expansion card (daughter card) 3 MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.33 |
bladeDaughterCard4MACAddress1VpdBlade expansion card (daughter card) 4 MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.34 |
bladeDaughterCard4MACAddress2VpdBlade expansion card (daughter card) 4 MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.35 |
bladeDaughterCard4MACAddress3VpdBlade expansion card (daughter card) 4 MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.36 |
bladeDaughterCard4MACAddress4VpdBlade expansion card (daughter card) 4 MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.37 |
bladeDaughterCard4MACAddress5VpdBlade expansion card (daughter card) 4 MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.38 |
bladeDaughterCard4MACAddress6VpdBlade expansion card (daughter card) 4 MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.39 |
bladeDaughterCard4MACAddress7VpdBlade expansion card (daughter card) 4 MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.40 |
bladeDaughterCard4MACAddress8VpdBlade expansion card (daughter card) 4 MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.41 |
bladeDaughterCard5MACAddress1VpdBlade expansion card (daughter card) 5 MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.42 |
bladeDaughterCard5MACAddress2VpdBlade expansion card (daughter card) 5 MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.43 |
bladeDaughterCard5MACAddress3VpdBlade expansion card (daughter card) 5 MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.44 |
bladeDaughterCard5MACAddress4VpdBlade expansion card (daughter card) 5 MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.45 |
bladeDaughterCard5MACAddress5VpdBlade expansion card (daughter card) 5 MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.46 |
bladeDaughterCard5MACAddress6VpdBlade expansion card (daughter card) 5 MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.47 |
bladeDaughterCard5MACAddress7VpdBlade expansion card (daughter card) 5 MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.48 |
bladeDaughterCard5MACAddress8VpdBlade expansion card (daughter card) 5 MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.49 |
bladeHSDaughterCard1MACAddress1VpdBlade high speed expansion card (daughter card) 1 MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.100 |
bladeHSDaughterCard1MACAddress2VpdBlade high speed expansion card (daughter card) 1 MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.101 |
bladeHSDaughterCard1MACAddress3VpdBlade high speed expansion card (daughter card) 1 MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.102 |
bladeHSDaughterCard1MACAddress4VpdBlade high speed expansion card (daughter card) 1 MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.103 |
bladeHSDaughterCard1MACAddress5VpdBlade high speed expansion card (daughter card) 1 MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.104 |
bladeHSDaughterCard1MACAddress6VpdBlade high speed expansion card (daughter card) 1 MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.105 |
bladeHSDaughterCard1MACAddress7VpdBlade high speed expansion card (daughter card) 1 MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.106 |
bladeHSDaughterCard1MACAddress8VpdBlade high speed expansion card (daughter card) 1 MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.107 |
bladeSideCardMACAddress1VpdBlade side card MAC address 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.164 |
bladeSideCardMACAddress2VpdBlade side card MAC address 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.165 |
bladeSideCardMACAddress3VpdBlade side card MAC address 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.166 |
bladeSideCardMACAddress4VpdBlade side card MAC address 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.167 |
bladeSideCardMACAddress5VpdBlade side card MAC address 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.168 |
bladeSideCardMACAddress6VpdBlade side card MAC address 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.169 |
bladeSideCardMACAddress7VpdBlade side card MAC address 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.170 |
bladeSideCardMACAddress8VpdBlade side card MAC address 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.2.1.171 |
bladeExpBoardVpdTableTable of VPD information for the blade expansion board components.
For consistent results, view as a table and not as individual entries. SEQUENCE OF BladeExpBoardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.3 |
bladeExpBoardVpdEntryBlade expansion board VPD entry.
For consistent results, view as a table and not as individual entries. BladeExpBoardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1 |
bladeExpBoardVpdIndexBlade expansion board VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.1 |
bladeExpBoardVpdBayNumberBlade expansion board VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.2 |
bladeExpBoardVpdManufacturingIdBlade expansion board VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.3 |
bladeExpBoardVpdFruNumberBlade expansion board VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.4 |
bladeExpBoardVpdHardwareRevisionBlade expansion board VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.5 |
bladeExpBoardVpdSerialNumberBlade expansion board VPD serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.6 |
bladeExpBoardVpdMachineTypeBlade expansion board VPD machine type.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.7 |
bladeExpBoardVpdUuidBlade expansion board VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.8 |
bladeExpBoardVpdManufDateBlade expansion board VPD Manufacture Date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.9 |
bladeExpBoardVpdPartNumberBlade expansion board VPD Part number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.10 |
bladeExpBoardVpdFruSerialBlade expansion board VPD FRU serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.11 |
bladeExpBoardVpdMachineModelBlade expansion board VPD machine model.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.12 |
bladeExpBoardVpdManufacturingIDNumberBlade expansion board VPD Manufacturer ID Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.13 |
bladeExpBoardVpdProductIdBlade expansion board VPD Product ID.
For consistent results, view as a table and
not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.14 |
bladeExpBoardVpdSubManufacturerIdBlade expansion board VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.15 |
bladeExpBoardVpdCleiBlade expansion board VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.16 |
bladeExpBoardVpdBladeBayNumberBlade bay number of the blade expansion board.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.19 |
bladeExpBoardVpdCardTypeBlade expansion board VPD type.
For consistent results, view as a table and not as individual entries.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.20 |
bladeExpBoardVpdCardSubTypeBlade expansion board VPD subtype.
Describes the expansion board type with more granularity.
bse1,bse2,bse3 = Blade Storage Expansion (1st, 2nd, and 3rd Generations),
peu1 = PCI Expansion (1st Generation),
peu2 = PCI Expansion Unit II,
peu3 = bpe3 = PCI Express Expansion Unit,
bie= Blade I/O Expansion
For consistent results, view as a table and not as individual entries.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.21 |
bladeExpBoardVpdHardwareRevisionStringBlade expansion board VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.3.1.22 |
bladeSideCardVpdTableTable of VPD information for the blade side card components.
For consistent results, view as a table and not as individual entries. SEQUENCE OF BladeSideCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.4 |
bladeSideCardVpdEntryBlade side card VPD entry.
For consistent results, view as a table and not as individual entries. BladeSideCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1 |
bladeSideCardVpdIndexBlade side card VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.1 |
bladeSideCardVpdBayNumberBlade side card VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.2 |
bladeSideCardVpdManufacturingIdBlade side card VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.3 |
bladeSideCardVpdFruNumberBlade side card VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.4 |
bladeSideCardVpdHardwareRevisionBlade side card VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.5 |
bladeSideCardVpdSerialNumberBlade side card VPD serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.6 |
bladeSideCardVpdMachineTypeBlade side card VPD machine type.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.7 |
bladeSideCardVpdUuidBlade side card VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.8 |
bladeSideCardVpdManufDateBlade side card VPD Manufacture Date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.9 |
bladeSideCardVpdPartNumberBlade side card VPD Part number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.10 |
bladeSideCardVpdFruSerialBlade side card VPD FRU serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.11 |
bladeSideCardVpdMachineModelBlade side card VPD machine model.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.12 |
bladeSideCardVpdManufacturingIDNumberBlade side card VPD Manufacturer ID Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.13 |
bladeSideCardVpdProductIdBlade side card VPD Product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.14 |
bladeSideCardVpdSubManufacturerIdBlade side card VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.15 |
bladeSideCardVpdCleiBlade side card VPD Common Language
Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.16 |
bladeSideCardVpdBladeBayNumberBlade bay number of the blade side card.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.19 |
bladeSideCardVpdHardwareRevisionStringBlade side card VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.4.1.20 |
bladeExpCardVpdTableTable of VPD information for the blade expansion card components.
For consistent results, view as a table and not as individual entries. SEQUENCE OF BladeExpCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.5 |
bladeExpCardVpdEntryBlade expansion card VPD entry.
For consistent results, view as a table and not as individual entries. BladeExpCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1 |
bladeExpCardVpdIndexBlade expansion card VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.1 |
bladeExpCardVpdBayNumberBlade expansion card VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.2 |
bladeExpCardVpdManufacturingIdBlade expansion card VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.3 |
bladeExpCardVpdFruNumberBlade expansion card VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.4 |
bladeExpCardVpdHardwareRevisionBlade expansion card VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.5 |
bladeExpCardVpdSerialNumberBlade expansion card VPD serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.6 |
bladeExpCardVpdMachineTypeBlade expansion card VPD machine type.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.7 |
bladeExpCardVpdUuidBlade expansion card VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.8 |
bladeExpCardVpdManufDateBlade expansion card VPD Manufacture Date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.9 |
bladeExpCardVpdPartNumberBlade expansion card VPD Part number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.10 |
bladeExpCardVpdFruSerialBlade expansion card VPD FRU serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.11 |
bladeExpCardVpdMachineModelBlade expansion card VPD machine model.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.12 |
bladeExpCardVpdManufacturingIDNumberBlade expansion card VPD Manufacturer ID Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.13 |
bladeExpCardVpdProductIdBlade expansion card VPD Product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.14 |
bladeExpCardVpdSubManufacturerIdBlade expansion card VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.15 |
bladeExpCardVpdCleiBlade expansion card VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.16 |
bladeExpCardVpdBladeBayNumberBlade bay number of the blade expansion card.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.19 |
bladeExpCardVpdCardTypeInfoBlade expansion card (daughter card) VPD type code that describes the expansion
card. For consistent results, view as a table and not as individual entries.
NOTE: The CFFe expansion card is also referred to as a CFFh expansion card.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.21 |
bladeExpCardVpdHighSpeedBlade expansion card (daughter card) VPD high speed that indicates whether the
expansion card is high speed or not. For consistent results, view as a table and
not as individual entries.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.22 |
bladeExpCardVpdHardwareRevisionStringBlade expansion card VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.5.1.23 |
bladecKVMCardVpdTableTable of VPD information for the blade
concurrent keyboard, video, and mouse (cKVM) card components.
For consistent results, view as a table and not as individual entries. SEQUENCE OF BladecKVMCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.6 |
bladecKVMCardVpdEntryBlade concurrent keyboard, video, and mouse (cKVM) card VPD entry.
For consistent results, view as a table and not as individual entries. BladecKVMCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1 |
bladecKVMCardVpdIndexBlade concurrent keyboard mouse video (cKVM) card VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.1 |
bladecKVMCardVpdBayNumberBlade concurrent keyboard video mouse (cKVM) card VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.2 |
bladecKVMCardVpdManufacturingIdBlade concurrent keyboard video mouse (cKVM) card VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.3 |
bladecKVMCardVpdFruNumberBlade concurrent keyboard video mouse (cKVM) card VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.4 |
bladecKVMCardVpdHardwareRevisionBlade concurrent keyboard video mouse (cKVM) card VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.5 |
bladecKVMCardVpdSerialNumberBlade concurrent keyboard video mouse (cKVM) card VPD serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.6 |
bladecKVMCardVpdMachineTypeBlade concurrent keyboard video mouse (cKVM) card VPD machine type.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.7 |
bladecKVMCardVpdUuidBlade concurrent keyboard video mouse (cKVM) card VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.8 |
bladecKVMCardVpdManufDateBlade concurrent keyboard video mouse (cKVM) card VPD Manufacture Date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.9 |
bladecKVMCardVpdPartNumberBlade concurrent keyboard video mouse (cKVM) card VPD Part number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.10 |
bladecKVMCardVpdFruSerialBlade concurrent keyboard video mouse (cKVM) card VPD FRU serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.11 |
bladecKVMCardVpdMachineModelBlade concurrent keyboard video mouse (cKVM) card VPD machine model.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.12 |
bladecKVMCardVpdManufacturingIDNumberBlade concurrent keyboard video mouse (cKVM) card VPD
manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.13 |
bladecKVMCardVpdProductIdBlade concurrent keyboard video mouse (cKVM) card VPD
Product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.14 |
bladecKVMCardVpdSubManufacturerIdBlade concurrent keyboard video mouse (cKVM) card VPD
subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.15 |
bladecKVMCardVpdCleiBlade concurrent keyboard video mouse (cKVM) card VPD
Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.16 |
bladecKVMCardVpdHardwareRevisionStringBlade concurrent keyboard video mouse (cKVM) card VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.6.1.17 |
bladeAndExpCardWwnGuidVpdTableTable of World Wide Names (WWN), Global Unique IDs (GUID) and
Serial Attach SCSI IDs (SAS) of the blade server and its expansion
cards (daughter cards).
For consistent results, view as a table and not as individual entries. SEQUENCE OF BladeAndExpCardWwnGuidVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.7 |
bladeAndExpCardWwnGuidVpdEntryBlade WWN/GUID entries.
For consistent results, view as a table and not as individual entries. BladeAndExpCardWwnGuidVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1 |
bladeAndExpCardWwnGuidVpdIndexBlade or expansion card index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.1 |
bladeAndExpCardWwnGuidVpdBayNumberBlade or expansion card VPD bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.2 |
bladeAndExpCardWwnGuidVpdNameThe name of the blade or expansion card.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.3 |
bladeAndExpCardWwnGuidVpdBladeBayNumberFor expansion cards, it's the blade bay number of the blade
expansion card. For blades, it's the bay number of the blade.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.4 |
bladeAndExpCardWwnGuidVpdTypeBlade or expansion card WWN/GUID/SAS Type.
For consistent results, view as a table and not as individual entries.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.5 |
bladeAndExpCardWwnGuidVpd1Blade or expansion card WWN/GUID 1.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.6 |
bladeAndExpCardWwnGuidVpd2Blade or expansion card WWN/GUID 2.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.7 |
bladeAndExpCardWwnGuidVpd3Blade or expansion card WWN/GUID 3.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.8 |
bladeAndExpCardWwnGuidVpd4Blade or expansion card WWN/GUID 4.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.9 |
bladeAndExpCardWwnGuidVpd5Blade or expansion card WWN/GUID 5.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.10 |
bladeAndExpCardWwnGuidVpd6Blade or expansion card WWN/GUID 6.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.11 |
bladeAndExpCardWwnGuidVpd7Blade or expansion card WWN/GUID 7.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.12 |
bladeAndExpCardWwnGuidVpd8Blade or expansion card WWN/GUID 8.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.7.1.13 |
bladeManagementCardVpdTableTable of VPD information for the blade
management card component.
For consistent results, view as a table
and not as individual entries. SEQUENCE OF BladeManagementCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.8 |
bladeManagementCardVpdEntryBlade management card VPD entry.
For consistent results, view as a table
and not as individual entries. BladeManagementCardVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1 |
bladeManagementCardVpdIndexBlade management card VPD index.
For consistent results, view as a table
and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.1 |
bladeManagementCardVpdBayNumberBlade management card VPD Bay number.
For consistent results, view as a table and
not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.2 |
bladeManagementCardVpdManufacturingIdBlade management card VPD manufacturing ID.
For consistent results, view as a table and not as
individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.3 |
bladeManagementCardVpdFruNumberBlade management card VPD FRU number.
For consistent results, view as a table and not
as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.4 |
bladeManagementCardVpdHardwareRevisionBlade management card VPD hardware revision.
For consistent results, view as a table and not as
individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.5 |
bladeManagementCardVpdSerialNumberBlade management card VPD serial number.
For consistent results, view as a table and not
as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.6 |
bladeManagementCardVpdMachineTypeBlade management card VPD machine type.
For consistent results, view as a table and not
as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.7 |
bladeManagementCardVpdUuidBlade management card VPD UUID.
For consistent results, view as a table
and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.8 |
bladeManagementCardVpdManufDateBlade management card VPD Manufacture Date.
For consistent results, view as a table and not as
individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.9 |
bladeManagementCardVpdPartNumberBlade management card VPD Part number.
For consistent results, view as a table and not
as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.10 |
bladeManagementCardVpdFruSerialBlade management card VPD FRU serial number.
For consistent results, view as a table and not as
individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.11 |
bladeManagementCardVpdMachineModelBlade management card VPD machine model.
For consistent results, view as a table and not
as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.12 |
bladeManagementCardVpdManufacturingIDNumberBlade management card VPD manufacturer ID.
For consistent results, view as a table and not as
individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.13 |
bladeManagementCardVpdProductIdBlade management card VPD Product ID.
For consistent results, view as a table and not
as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.14 |
bladeManagementCardVpdSubManufacturerIdBlade management card VPD subsystem manufacturer ID.
For consistent results, view as a table and not as
individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.15 |
bladeManagementCardVpdCleiBlade management card VPD Common Language Equipment
Identifier (CLEI).
For consistent results, view as a table and not as
individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.16 |
bladeManagementCardVpdHardwareRevisionStringBlade management card VPD hardware revision in string format.
For consistent results, view as a table and not as
individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.4.8.1.17 |
bladeFirmwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.5 |
bladeBiosVPDTableTable of blade firmware vital product data (VPD) information. SEQUENCE OF BladeBiosVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.1 |
bladeBiosVPDEntryBlade firmware VPD table entry BladeBiosVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1 |
bladeBiosVpdIndexBlade firmware VPD table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.1 |
bladeBiosVpdIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.2 |
bladeBiosVpdExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.3 |
bladeBiosVpdPowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.4 |
bladeBiosVpdNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.5 |
bladeBiosVpdBuildIdThe build ID for the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.6 |
bladeBiosVpdRevisionThe revision of the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.7 |
bladeBiosVpdDateThe date of the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.8 |
bladeBiosVpdLevelStatusThe level status of the blade bios firmware build ID.
It has three possible values as Different (mismatch firmware build ID), Match (the
same firmware build ID), Unique (only one such firmware build ID).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.1.1.9 |
bladeDiagsVPDTableTable of blade firmware vital product data (VPD) information. SEQUENCE OF BladeDiagsVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.2 |
bladeDiagsVPDEntryBlade firmware VPD table entry BladeDiagsVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1 |
bladeDiagsVpdIndexBlade firmware VPD table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.1 |
bladeDiagsVpdIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.2 |
bladeDiagsVpdExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.3 |
bladeDiagsVpdPowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.4 |
bladeDiagsVpdNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.5 |
bladeDiagsVpdBuildIdThe build ID for the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.6 |
bladeDiagsVpdRevisionThe revision of the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.7 |
bladeDiagsVpdDateThe date of the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.8 |
bladeDiagsVpdLevelStatusThe level status of the blade diagnostics firmware build ID.
It has three possible values as Different (mismatch firmware build ID), Match (the
same firmware build ID), Unique (only one such firmware build ID).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.2.1.9 |
bladeSysMgmtProcVPDTableTable of blade firmware vital product data (VPD) information. SEQUENCE OF BladeSysMgmtProcVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.3 |
bladeSysMgmtProcVPDEntryBlade firmware VPD table entry BladeSysMgmtProcVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1 |
bladeSysMgmtProcVpdIndexBlade firmware VPD table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.1 |
bladeSysMgmtProcVpdIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.2 |
bladeSysMgmtProcVpdExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.3 |
bladeSysMgmtProcVpdPowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.4 |
bladeSysMgmtProcVpdNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.5 |
bladeSysMgmtProcVpdBuildIdThe build ID for the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.6 |
bladeSysMgmtProcVpdRevisionThe revision of the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.7 |
bladeSysMgmtProcVpdLevelStatusThe level status of the blade system management processor firmware build ID.
It has three possible values as Different (mismatch firmware build ID), Match (the
same firmware build ID), Unique (only one such firmware build ID).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.3.1.8 |
bladecKVMVPDTableTable of blade firmware vital product data (VPD) information. SEQUENCE OF BladecKVMVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.4 |
bladecKVMVPDEntryBlade firmware VPD table entry BladecKVMVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.4.1 |
bladecKVMVpdIndexBlade firmware VPD table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.5.4.1.1 |
bladecKVMVpdIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.4.1.2 |
bladecKVMVpdExistsIndicates whether the blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.4.1.3 |
bladecKVMVpdPowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.4.1.4 |
bladecKVMVpdNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.4.1.5 |
bladecKVMVpdRevisionThe revision of the blade firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.4.1.7 |
bladeFWBuildIDs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.5.5 |
bladeFWBuildIDTableTable of Blade Firmware Build ID entries information. SEQUENCE OF BladeFWBuildIDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1 |
bladeFWBuildIDEntryBlade Firmware Build ID table entry BladeFWBuildIDEntry .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1.1 |
bladeFWBuildIDIndexThe index number of one Build ID entry.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1.1.1 |
bladeFWBuildMfgThe Manufacturer property of one Build ID entry.
For consistent results, view as a table and not as individual entries.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1.1.2 |
bladeFWBuildMTThe Machine Type property of one Build ID entry.
For consistent results, view as a table and not as individual entries.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1.1.3 |
bladeFWBuildFWTypeThe Firmware Type property of one Build ID entry.
For consistent results, view as a table and not as individual entries.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1.1.4 |
bladeFWBuildIDThe Build ID property of one Build ID entry.
For consistent results, view as a table and not as individual entries.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1.1.5 |
bladeFWBuildRevThe Build Revision property of one Build ID entry.
For consistent results, view as a table and not as individual entries.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.1.1.6 |
createBladeFWBuildIDsCreate one new Build ID List from current installed blades.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.5.2 |
addBladeFWBuildID OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.5.5.3 |
addBladeMfgAdd one Build ID entry into the Build ID List.
This is to set Manufacturer property.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.3.1 |
addBladeMtAdd one Build ID entry into the Build ID List.
This is to set Machine Type property.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.3.2 |
addBladeFtAdd one Build ID entry into the Build ID List.
This is to set Firmware Type property.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.3.3 |
addBladeBuildIDAdd one Build ID entry into the Build ID List.
This is to set Build ID property.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.3.4 |
addBladeBuildRevAdd one Build ID entry into the Build ID List.
This is to set Build Revision property.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.3.5 |
exeBladeAddingAdd one Build ID entry into the Build ID List.
This is to perform the adding action.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.5.3.6 |
rmBladeFWBuildIDRemove one Build ID entry from the Build ID List.
The index of the Build ID entry in the list is required.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.5.5.4 |
rmAllBladeFWBuildIDsRemove all Build ID entries from the Build ID List.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.5.5 |
buildIDFileNameFile name of the Build ID list that will be used in import function.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.6 |
buildIDURINameContains the fully qualified remote location of the build ID list. Use
buildIDFileName to specify the filename. A fully qualified remote location
contains a supported protocol followed by a colon and two slashes (//),
userid and password separated by a colon for login authentication, an
@ sign, followed by the hostname or IP address of the server where the
build ID list resides, followed by an optional port number to the hostname,
and the full pathname to the file. Note that if the port number is specified,
it must be separated with the hostname (or IP address) by a colon.
The AMM currently supports the following protocols:
TFTP, FTP, FTPS, HTTP and HTTPS.
The complete format of a fully qualified remote location is:
<protocol>://<userid:password>@<hostname:port>/<pathname>
An example of a fully qualified remote location can be:
ftp://USERID:PASSW0RD@192.168.0.2:30045/tmp
where the ftp protocol will be used for transferring the file in
this location, username is USERID, password is PASSW0RD, host IP address
is 192.168.0.2, port number is 30045, and the full pathname for the build ID
list is /tmp.
Some protocols do not need the username, password, and the port number, so the
minimum requirement for a fully qualified location can be:
<protocol>://<hostname>/<pathname>.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.7 |
buildIDtftpIPIf importing/exporting via the legacy method using a tftp server, then
set the IP address or host name of the TFTP server where
the firmware file resides. The address must be entered in a
dotted decimal IP string (e.g. 9.37.44.2).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.8 |
importBladeFWBuildIDsImport one Build ID List set by the buildIDFilename from a specific location
set by buildIDServer.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.5.9 |
exportBladeFWBuildIDsExport the current Build ID List from the active AMM to a specific location
set by buildIDServer.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.5.5.10 |
statusBladeFWBuildIDsGives the status message from the last import or export operation.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.5.5.11 |
smHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.6 |
smHardwareVpdTableTable of the switch module hardware components.
For consistent results, view as a table and not as
individual entries. SEQUENCE OF SmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.6.1 |
smHardwareVpdEntrySwitch module hardware VPD entry.
For consistent results, view as a table and
not as individual entries. SmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1 |
smHardwareVpdIndexSwitch module hardware VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.1 |
smHardwareVpdBayNumberSwitch module hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.2 |
smHardwareVpdManufacturingIdSwitch module hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.3 |
smHardwareVpdFruNumberSwitch module hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.4 |
smHardwareVpdHardwareRevisionSwitch module hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.5 |
smHardwareVpdUuidSwitch module hardware VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.8 |
smHardwareVpdManufDateSwitch module hardware VPD manufacture date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.9 |
smHardwareVpdPartNumberSwitch module hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.10 |
smHardwareVpdFruSerialSwitch module hardware VPD FRU Serial.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.11 |
smHardwareVpdManufacturingIDNumberSwitch module hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.12 |
smHardwareVpdProductIdSwitch module hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.13 |
smHardwareVpdSubManufacturerIdSwitch module hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.14 |
smHardwareVpdCleiSwitch module hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.15 |
smHardwareVpdWwnGuidSwitch module hardware VPD World Wide Name or Global Unique ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.16 |
smHardwareVpdWwnGuidTypeThe WWN/GUID/SAS entry is actually World Wide Name, Global Unique ID
or Serial Attach SCSI ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.17 |
smHardwareVpdWidthThe width of the switch module hardware.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.18 |
smHardwareVpdHardwareRevisionStringSwitch module hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.1.1.20 |
smInpHardwareVpdTableTable of the switch interposer hardware components.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only. SEQUENCE OF SmInpHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.6.2 |
smInpHardwareVpdEntrySwitch Interposer hardware VPD entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only. SmInpHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1 |
smInpHardwareVpdIndexSwitch Interposer hardware VPD index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.1 |
smInpHardwareVpdBayNumberSwitch Interposer hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.2 |
smInpHardwareVpdManufacturingIdSwitch Interposer hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.3 |
smInpHardwareVpdFruNumberSwitch Interposer hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.4 |
smInpHardwareVpdHardwareRevisionSwitch Interposer hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.5 |
smInpHardwareVpdUuidSwitch Interposer hardware VPD UUID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.8 |
smInpHardwareVpdManufDateSwitch Interposer hardware VPD manufacture Date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.9 |
smInpHardwareVpdPartNumberSwitch Interposer hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.10 |
smInpHardwareVpdFruSerialSwitch Interposer module hardware VPD FRU Serial.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.11 |
smInpHardwareVpdManufacturingIDNumberSwitch Interposer module hardware VPD manufacturer ID Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.12 |
smInpHardwareVpdProductIdSwitch Interposer module hardware VPD product ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.13 |
smInpHardwareVpdSubManufacturerIdSwitch Interposer module hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.14 |
smInpHardwareVpdCleiSwitch Interposer module hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.15 |
smInpHardwareVpdWwnGuidSwitch Interposer module hardware VPD World Wide Name or Global Unique ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.16 |
smInpHardwareVpdWwnGuidTypeThe Switch Interposer WWN/GUID/SAS entry is actually World Wide
Name, Global Unique ID or Serial Attach SCSI ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.17 |
smInpHardwareVpdWidthThe width of the switch Interposer module hardware.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.18 |
smInpHardwareVpdNameThe Switch Interposer Name.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.19 |
smInpHardwareVpdHardwareRevisionStringSwitch Interposer hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HS only.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.6.2.1.20 |
smFirmwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.7 |
smMainAppVpdTableSwitch module main application VPD information table. SEQUENCE OF SmMainAppVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.7.1 |
smMainAppVpdEntrySwitch module main application VPD table entry SmMainAppVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1 |
smMainAppVpdIndexSwitch module main application VPD entry index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.1 |
smMainAppVpdIdThe switch module numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.2 |
smMainAppVpdExistsIndicates whether the switch module specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.3 |
smMainAppVpdSwitchTypeIndicates the type of switch module installed.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.4 |
smMainApp1VpdBuildIdSwitch module firmware build id.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.5 |
smMainApp1VpdBuildDateSwitch module firmware build date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.6 |
smMainApp1VpdRevisionNumberSwitch module firmware revision number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.7 |
smMainApp2VpdBuildIdSwitch module firmware build id.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.8 |
smMainApp2VpdBuildDateSwitch module firmware build date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.9 |
smMainApp2VpdRevisionNumberSwitch module firmware revision number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.10 |
smMainApp3VpdBuildIdI/O Module firmware build id.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.11 |
smMainApp3VpdBuildDateI/O Module firmware build date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.12 |
smMainApp3VpdRevisionNumberI/O Module firmware revision number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.13 |
smMainAppVpdSwitchSubTypeIndicates the subtype of switch module installed.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.1.1.20 |
smBootRomVpdTableSwitch module boot ROM VPD information table. SEQUENCE OF SmBootRomVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.7.2 |
smBootRomVpdEntrySwitch module boot ROM VPD table entry SmBootRomVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1 |
smBootRomVpdIndexSwitch module boot ROM VPD entry index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.1 |
smBootRomVpdIdThe switch module numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.2 |
smBootRomVpdExistsIndicates whether the switch module specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.3 |
smBootRomVpdSwitchTypeIndicates the type of switch module installed.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.4 |
smBootRomVpdBuildIdSwitch module firmware build ID.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.5 |
smBootRomVpdBuildDateSwitch module firmware build date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.6 |
smBootRomVpdRevisionNumberSwitch module firmware revision number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.7 |
smBootRomVpdSwitchSubTypeIndicates the subtype of switch module installed.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.7.2.1.8 |
pmHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.8 |
pmHardwareVpdTableTable of the power module hardware components.
For consistent results, view as a table and not as individual entries. SEQUENCE OF PmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.8.1 |
pmHardwareVpdEntryPower module hardware VPD entry.
For consistent results, view as a table and not as individual entries. PmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1 |
pmHardwareVpdIndexPower module hardware VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.1 |
pmHardwareVpdBayNumberPower module hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.2 |
pmHardwareVpdManufacturingIdPower module hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.3 |
pmHardwareVpdFruNumberPower module hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.4 |
pmHardwareVpdHardwareRevisionPower module hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.5 |
pmHardwareVpdUuidPower module hardware VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.8 |
pmHardwareVpdManufDatePower module hardware VPD Manufacture Date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.9 |
pmHardwareVpdPartNumberPower module hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.10 |
pmHardwareVpdFruSerialPower module hardware VPD FRU Serial.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.11 |
pmHardwareVpdManufacturingIDNumberPower module hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.12 |
pmHardwareVpdProductIdPower module hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.13 |
pmHardwareVpdSubManufacturerIdPower module hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.14 |
pmHardwareVpdCleiPower module hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.15 |
pmHardwareVpdHardwareRevisionStringPower module hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.8.1.1.16 |
mtHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.9 |
mtHardwareVpdManufacturingIdMedia tray 1 hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.3 |
mtHardwareVpdFruNumberMedia tray 1 hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.4 |
mtHardwareVpdHardwareRevisionMedia tray 1 hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.9.5 |
mtHardwareVpdUuidMedia tray 1 hardware VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.8 |
mtHardwareVpdManufacturingIDNumberMedia tray 1 hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.9 |
mtHardwareVpdProductIdMedia tray 1 hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.10 |
mtHardwareVpdSubManufacturerIdMedia tray 1 hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.11 |
mtHardwareVpdCleiMedia tray 1 hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.12 |
mtHardwareVpdCF1CapacityMedia tray 1 hardware VPD CompactFlash card capacity.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.13 |
mtHardwareVpdCF2CapacityMedia tray 1 hardware VPD CompactFlash card capacity.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.14 |
mtHardwareVpdBBU1Indicates the presence of Battery Backup Unit 1.
NOTE: This MIB object is for BCS only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.9.15 |
mtHardwareVpdBBU2Indicates the presence of Battery Backup Unit 2.
NOTE: This MIB object is for BCS only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.9.16 |
mtHardwareVpdHardwareRevisionStringMedia tray 1 hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.17 |
mtHardwareVpdManufDateMedia tray 1 hardware VPD Manufacture Date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.18 |
mtHardwareVpdPartNumberMedia tray 1 hardware VPD Part Number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.19 |
mtHardwareVpdFruSerialMedia tray 1 hardware VPD FRU Serial.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.9.20 |
mt2HardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.10 |
mt2HardwareVpdManufacturingIdMedia tray 2 hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.3 |
mt2HardwareVpdFruNumberMedia tray 2 hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.4 |
mt2HardwareVpdHardwareRevisionMedia tray 2 hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.10.5 |
mt2HardwareVpdUuidMedia tray 2 hardware VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.8 |
mt2HardwareVpdManufacturingIDNumberMedia tray 2 hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.9 |
mt2HardwareVpdProductIdMedia tray 2 hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.10 |
mt2HardwareVpdSubManufacturerIdMedia tray 2 hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.11 |
mt2HardwareVpdCleiMedia tray 2 hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.12 |
mt2HardwareVpdCF1CapacityMedia tray 2 hardware VPD CompactFlash card capacity.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.13 |
mt2HardwareVpdCF2CapacityMedia tray 2 hardware VPD CompactFlash card capacity.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.14 |
mt2HardwareVpdHardwareRevisionStringMedia tray 2 hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.17 |
mt2HardwareVpdManufDateMedia tray 2 hardware VPD Manufacture Date.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.18 |
mt2HardwareVpdPartNumberMedia tray 2 hardware VPD Part Number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.19 |
mt2HardwareVpdFruSerialMedia tray 2 hardware VPD FRU Serial.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.10.20 |
blowerFirmwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.12 |
blowerControllerVPDTableTable of blower controller firmware vital product data (VPD) information.
NOTE: Blowers are also referred to as Chassis Cooling Devices. SEQUENCE OF BlowerControllerVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.12.1 |
blowerControllerVPDEntryBlower controller firmware VPD table entry BlowerControllerVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.12.1.1 |
blowerControllerVpdIndexBlower controller firmware VPD table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.12.1.1.1 |
blowerControllerVpdIdThe numeric blower ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.12.1.1.2 |
blowerControllerVpdExistsIndicates whether the blower specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.12.1.1.3 |
blowerControllerVpdRevisionThe revision of the blower controller firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.12.1.1.7 |
blowerHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.13 |
blowerHardwareVpdTableTable of the blower hardware components.
For consistent results, view as a table and not as individual entries.
NOTE: Blowers are also referred to as Chassis Cooling Devices. SEQUENCE OF BlowerHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.13.1 |
blowerHardwareVpdEntryBlower hardware VPD entry.
For consistent results, view as a table and not as individual entries. BlowerHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1 |
blowerHardwareVpdIndexBlower hardware VPD index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.1 |
blowerHardwareVpdBayNumberBlower hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.2 |
blowerHardwareVpdManufacturingIdBlower hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.3 |
blowerHardwareVpdFruNumberBlower hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.4 |
blowerHardwareVpdHardwareRevisionBlower hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.5 |
blowerHardwareVpdUuidBlower hardware VPD UUID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.8 |
blowerHardwareVpdManufDateBlower hardware VPD manufacture Date.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.9 |
blowerHardwareVpdPartNumberBlower hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.10 |
blowerHardwareVpdFruSerialBlower hardware VPD FRU serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.11 |
blowerHardwareVpdManufacturingIDNumberBlower hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.12 |
blowerHardwareVpdProductIdBlower hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.13 |
blowerHardwareVpdSubManufacturerIdBlower hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.14 |
blowerHardwareVpdCleiBlower hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.15 |
blowerHardwareVpdHardwareRevisionStringBlower hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.13.1.1.16 |
fanPackFirmwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.14 |
fanPackControllerVPDTableTable of fan pack controller firmware vital product data (VPD) information.
NOTE: Fan packs are also referred to as Power Module Chassis Cooling Devices. SEQUENCE OF FanPackControllerVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.14.1 |
fanPackControllerVPDEntryFan Pack controller firmware VPD table entry FanPackControllerVPDEntry .1.3.6.1.4.1.2.3.51.2.2.21.14.1.1 |
fanPackControllerVpdIndexFan Pack controller firmware VPD table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.14.1.1.1 |
fanPackControllerVpdIdThe numeric fan pack ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.14.1.1.2 |
fanPackControllerVpdExistsIndicates whether the fan pack specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.14.1.1.3 |
fanPackControllerVpdRevisionThe revision of the fan pack controller firmware.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.14.1.1.7 |
tapHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.15 |
tapHardwareVpdManufacturingIdTelco Alarm Panel hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.3 |
tapHardwareVpdFruNumberTelco Alarm Panel hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.4 |
tapHardwareVpdHardwareRevisionTelco Alarm Panel hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.15.5 |
tapHardwareVpdUuidTelco Alarm Panel hardware VPD UUID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.8 |
tapHardwareVpdManufDateTelco Alarm Panel hardware VPD manufacture Date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.9 |
tapHardwareVpdPartNumberTelco Alarm Panel hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.10 |
tapHardwareVpdFruSerialTelco Alarm Panel hardware VPD FRU Serial.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.11 |
tapHardwareVpdManufacturingIDNumberTelco Alarm Panel hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.12 |
tapHardwareVpdProductIdTelco Alarm Panel hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.13 |
tapHardwareVpdSubManufacturerIdTelco Alarm Panel hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.14 |
tapHardwareVpdCleiTelco Alarm Panel hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.15 |
tapHardwareVpdHardwareRevisionStringTelco Alarm Panel hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.15.16 |
ncHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.16 |
ncHardwareVpdTableTable of the Network Clock hardware components.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.deprecated SEQUENCE OF NcHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.16.1 |
ncHardwareVpdEntryNetwork Clock hardware VPD entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.deprecated NcHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1 |
ncHardwareVpdIndexNetwork Clock hardware VPD index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.1 |
ncHardwareVpdBayNumberNetwork Clock hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.2 |
ncHardwareVpdManufacturingIdNetwork Clock hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.3 |
ncHardwareVpdFruNumberNetwork Clock hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.4 |
ncHardwareVpdHardwareRevisionNetwork Clock hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.5 |
ncHardwareVpdUuidNetwork Clock hardware VPD UUID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.8 |
ncHardwareVpdManufDateNetwork Clock hardware VPD manufacture Date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.9 |
ncHardwareVpdPartNumberNetwork Clock hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.10 |
ncHardwareVpdFruSerialNetwork Clock hardware VPD FRU serial number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.11 |
ncHardwareVpdManufacturingIDNumberNetwork Clock hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.12 |
ncHardwareVpdProductIdNetwork Clock hardware VPD product ID.
For consistent results, view as a table and not as individual entries.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.13 |
ncHardwareVpdSubManufacturerIdNetwork Clock hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.14 |
ncHardwareVpdCleiNetwork Clock hardware VPD Common Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.15 |
ncHardwareVpdHardwareRevisionStringNetwork Clock hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.16.1.1.16 |
mxHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.17 |
mxHardwareVpdTableTable of the Multiplexer Expansion Module hardware components.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only. SEQUENCE OF MxHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.17.1 |
mxHardwareVpdEntryMultiplexer Expansion Module hardware VPD entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only. MxHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1 |
mxHardwareVpdIndexMultiplexer Expansion Module hardware VPD index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.1 |
mxHardwareVpdBayNumberMultiplexer Expansion Module hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.2 |
mxHardwareVpdManufacturingIdMultiplexer Expansion Module hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.3 |
mxHardwareVpdFruNumberMultiplexer Expansion Module hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.4 |
mxHardwareVpdHardwareRevisionMultiplexer Expansion Module hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.5 |
mxHardwareVpdUuidMultiplexer Expansion Module hardware VPD UUID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.8 |
mxHardwareVpdManufDateMultiplexer Expansion Module hardware VPD manufacture Date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.9 |
mxHardwareVpdPartNumberMultiplexer Expansion Module hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.10 |
mxHardwareVpdFruSerialMultiplexer Expansion Module hardware VPD FRU Serial Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.11 |
mxHardwareVpdManufacturingIDNumberMultiplexer Expansion Module hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.12 |
mxHardwareVpdProductIdMultiplexer Expansion Module hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.13 |
mxHardwareVpdSubManufacturerIdMultiplexer Expansion Module hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.14 |
mxHardwareVpdCleiMultiplexer Expansion Module hardware VPD Common
Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.15 |
mxHardwareVpdHardwareRevisionStringMultiplexer Expansion Module hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.17.1.1.16 |
stmHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.18 |
stmHardwareVpdTableTable of the Storage Module hardware components.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only. SEQUENCE OF StmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.18.1 |
stmHardwareVpdEntryStorage Module hardware VPD entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only. StmHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1 |
stmHardwareVpdIndexStorage Module hardware VPD index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.1 |
stmHardwareVpdBayNumberStorage Module hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.2 |
stmHardwareVpdManufacturingIdStorage Module hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.3 |
stmHardwareVpdFruNumberStorage Module hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.4 |
stmHardwareVpdHardwareRevisionStorage Module hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.
If a hardware revision is programmed in the OEM VPD area for this component,
then the HardwareRevisionString version of this MIB object should be used.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.5 |
stmHardwareVpdUuidStorage Module hardware VPD UUID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.8 |
stmHardwareVpdManufDateStorage Module hardware VPD manufacture Date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.9 |
stmHardwareVpdPartNumberStorage Module hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.10 |
stmHardwareVpdFruSerialStorage Module hardware VPD FRU Serial Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.11 |
stmHardwareVpdManufacturingIDNumberStorage Module hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.12 |
stmHardwareVpdProductIdStorage Module hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.13 |
stmHardwareVpdSubManufacturerIdStorage Module hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.14 |
stmHardwareVpdCleiStorage Module hardware VPD Common
Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.15 |
stmHardwareVpdHardwareRevisionStringStorage Module hardware VPD hardware revision in string format.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.
If a hardware revision is programmed in the OEM VPD area for this component,
then this MIB object should be used.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.18.1.1.16 |
stmFirmwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.19 |
stmFirmwareVpdTableTable of the Storage Module firmware components.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only. SEQUENCE OF StmFirmwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.19.1 |
stmFirmwareVpdEntryStorage Module firmware VPD entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only. StmFirmwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.19.1.1 |
stmFirmwareVpdIndexStorage Module firmware VPD index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.19.1.1.1 |
stmFirmwareVpdTypeStorage Module firmware VPD type.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.19.1.1.2 |
stmFirmwareVpdBuildIdStorage Module firmware VPD build ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.19.1.1.3 |
stmFirmwareVpdReleaseDateStorage Module firmware VPD release date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.19.1.1.4 |
stmFirmwareVpdRevisionStorage Module firmware VPD revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.19.1.1.5 |
bbuHardwareVpd OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.21 |
bbuHardwareVpdTableTable of the Battery Backup Unit hardware components.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only. SEQUENCE OF BbuHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.21.1 |
bbuHardwareVpdEntryBattery Backup Unit hardware VPD entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only. BbuHardwareVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1 |
bbuHardwareVpdIndexBattery Backup Unit hardware VPD index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.1 |
bbuHardwareVpdBayNumberBattery Backup Unit hardware VPD Bay number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.2 |
bbuHardwareVpdManufacturingIdBattery Backup Unit hardware VPD manufacturing ID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.3 |
bbuHardwareVpdFruNumberBattery Backup Unit hardware VPD FRU number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.4 |
bbuHardwareVpdHardwareRevisionBattery Backup Unit hardware VPD hardware revision.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.5 |
bbuHardwareVpdUuidBattery Backup Unit hardware VPD UUID.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.8 |
bbuHardwareVpdManufDateBattery Backup Unit hardware VPD manufacture Date.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.9 |
bbuHardwareVpdPartNumberBattery Backup Unit hardware VPD Part Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.10 |
bbuHardwareVpdFruSerialBattery Backup Unit hardware VPD FRU Serial Number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.11 |
bbuHardwareVpdManufacturingIDNumberBattery Backup Unit hardware VPD manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.12 |
bbuHardwareVpdProductIdBattery Backup Unit hardware VPD product ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.13 |
bbuHardwareVpdSubManufacturerIdBattery Backup Unit hardware VPD subsystem manufacturer ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.14 |
bbuHardwareVpdCleiBattery Backup Unit hardware VPD Common
Language Equipment Identifier (CLEI).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.21.1.1.15 |
inventoryManagementActivityVpdTableTable of system component hardware VPD activity log.
For consistent results, view as a table and not as individual entries. SEQUENCE OF InventoryManagementActivityVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.22 |
inventoryManagementActivityVpdEntrySystem component hardware VPD activity log entry.
For consistent results, view as a table and not as individual entries. InventoryManagementActivityVpdEntry .1.3.6.1.4.1.2.3.51.2.2.21.22.1 |
componentLevelActivityVpdIndexSystem component level VPD activity log index.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.21.22.1.1 |
componentLevelActivityVpdFruNumberSystem component level VPD activity log FRU number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.22.1.2 |
componentLevelActivityVpdSerialNumberSystem component level VPD activity log serial number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.22.1.3 |
componentLevelActivityVpdManufacturingIdSystem component level VPD activity log manufacturing ID.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.22.1.4 |
componentLevelActivityVpdBayNumberSystem component level VPD activity log Bay number.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.22.1.5 |
componentLevelActivityVpdActionSystem component level VPD activity log action (added/removed).
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.22.1.9 |
componentLevelActivityVpdTimestampSystem component level VPD activity log timestamp.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.22.1.10 |
componentLevelActivityVpdModuleNameThe module name which this row is associated with.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.21.22.1.12 |
reloadVpdData OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.21.23 |
reloadAllVpdDataReload all VPD data (firmware, hardware, MAC address, WWN/GUID and other Unique ID).
NOTE: The value returned for the GET command is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.23.1 |
reloadFwVpdDataReload firmware VPD data.
NOTE: The value returned for the GET command is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.23.2 |
reloadHwVpdDataReload hardware VPD data.
NOTE: The value returned for the GET command is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.23.3 |
reloadMACAddressReload blade MAC addresses.
NOTE: The value returned for the GET command is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.23.4 |
reloadWwnGuidVpdDataReload blade and I/O module WWN/GUID and other VPD data.
NOTE: The value returned for the GET command is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.21.23.5 |
airFilter OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.22 |
passiveAirFilter OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.22.1 |
passiveAirFilterStatusDisable/Enable/Reset the passive air filter. When enabled, sending an enable or reset will reset the replace date.
The reset command is only applicable in BladeCenter Telco Refresh and it will restart the Fouled Filter Detection settings.
NOTE: This MIB object is only applicable for BladeCenter S, BladeCenter E Refresh, and BladeCenter Telco Refresh.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.22.1.1 |
passiveAirFilterMonthFreqThe chassis environment. 1 month indicates high dust, 3 months indicates moderate dust and, 6 months indicates low dust.
NOTE: This MIB object is for BladeCenter S and BladeCenter E Refresh only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.2.22.1.2 |
passiveAirFilterReplaceDateThe scheduled replacement date of the air filter.
NOTE: This MIB object is for BladeCenter S and BladeCenter E Refresh only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.22.1.3 |
componentInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.23 |
componentInventory OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.23.1 |
componentInventoryTableTable of component inventory information. Not all components will
provide every object defined in the ComponentInventoryEntry. SEQUENCE OF ComponentInventoryEntry .1.3.6.1.4.1.2.3.51.2.2.23.1.1 |
componentInventoryEntryComponent inventory information. ComponentInventoryEntry .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1 |
componentInventoryTopologyPathThe unique identifier for a row 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.
This component inventory 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
MEDIA_MODULE, 0x19 Container of one or more media devices
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 cardro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.1 |
componentInventoryInstanceThe slot number or instance of a particular component. Typically,
if the component plugs into the chassis, this represents the slot
number. However, some components are connected to another component,
and this represents the instance. For example, a blade may have
several expansion cards that connect to the blade system planar,
and in this case, this value identifies which expansion card
instance the row represents.
Note that this slot/instance value can be determined from the
componentInventoryTopologyPath object, but this
componentInventoryInstance object is provided as a convenience
to the user.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.2 |
componentInventoryDescriptionA short text string describing the particular component. For the
AMM and blades, this name will be the configured name or its
serial number if no user configured name is available. For all
other components, this object will provide text to identify the
component. If a text string is not available, a value of
'Not available' is presented.
For more detail, also refer to the componentInventoryProductName
object.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.3 |
componentInventoryMachineTypeModelThe machine type and model number of this component. Typically,
the format is XXXXYYY, where XXXX reprsents the machine type
and YYY represents the model number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.4 |
componentInventoryMachineSerialThe machine serial number of this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.5 |
componentInventoryAssetIDThe asset identifier of this component, typically set by some
other authority than the
manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.6 |
componentInventoryPartNumberThe part number of this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.7 |
componentInventoryFRUNumberThe Field Replaceable Unit (FRU) number of this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.8 |
componentInventoryFRUSerialNumberThe Field Replaceable Unit (FRU) serial number of this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.9 |
componentInventoryManufactureIDThe text description of the manufacturer of this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.10 |
componentInventoryHardwareRevisionThe hardware revision number of the this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.11 |
componentInventoryManufactureDateThe date when the manufacturer created this component. The format
is XXYY, where XX is the week number of the year 20YY.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.12 |
componentInventoryUUIDThe Universally Unique IDentifier (UUID) of this component, represented
as a 16 byte hex number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.13 |
componentInventoryProductIDThe product identifier of the component assigned by the
manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.14 |
componentInventorySubManufactureIDThe text sub-description of the manufacturer of this component, often
used to identify a supplier for a component which has multiple
suppliers.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.15 |
componentInventoryCLEIThe Common Language Equipment Identifier (CLEI) of this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.16 |
componentInventoryAssetTagThe asset tag of this component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.17 |
componentInventorySpeedA speed designation for the component, for example, processor
speed.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.18 |
componentInventoryIdentifierA unique identifier assigned by the manufacturer to the
component, for example,
a processor ID.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.19 |
componentInventorySizeA size designation for the component, for example, a memory
DIMM size
or hard drive capacity.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.20 |
componentInventoryMemoryTypeThe architecture specification of a memory device.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.21 |
componentInventoryProductNameThe product name assigned by the manufacturer for this component.
For more detail, also refer to the componentInventoryDescription
object.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.22 |
componentInventoryProductVersionThe product version assigned by the manufacturer for this
component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.23 |
componentInventoryProcessorTypeThe type designation for processor components.ro Enumeration .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.24 |
componentInventoryProcessorFamilyThe family designation for processor components.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.25 |
componentInventoryProcessorCoresThe number of cores present on a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.26 |
componentInventoryProcessorThreadsThe number of threads present on a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.27 |
componentInventoryProcessorL1DCacheThe level 1 data cache size of a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.28 |
componentInventoryProcessorL1ICacheThe level 1 instruction cache size of a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.29 |
componentInventoryProcessorL2CacheThe level 2 cache size of a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.30 |
componentInventoryProcessorL3CacheThe level 3 cache size of a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.31 |
componentInventoryProcessorVoltageThe voltage rating for a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.32 |
componentInventoryProcessorExtClockThe external clock speed of a processor component.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.33 |
componentInventoryProcessorDataWidthThe maximum data bus width capability of a processor component,
expressed typically in bits.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.34 |
componentInventoryManufactureIDNumThe identification number assigned for the component by the manufacturer.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.23.1.1.1.35 |
componentFirmware OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.2.23.2 |
componentFirmwareTableTable of component firmware information. Not all components will
provide every object defined in the ComponentFirmwareEntry. SEQUENCE OF ComponentFirmwareEntry .1.3.6.1.4.1.2.3.51.2.2.23.2.1 |
componentFirmwareEntryComponent firmware information. ComponentFirmwareEntry .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1 |
componentFirmwareTopologyPathThe 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
MEDIA_MODULE, 0x19 Container of one or more media devices
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 cardro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.1 |
componentFirmwareIndexEach component may have one or more types of firmware associated with it, and this index object
identifies the particular instance.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.2 |
componentFirmwareComponentInstanceThe slot number or instance of a particular component. Typically,
if the component plugs into the chassis, this represents the slot
number. However, some components are connected to another component,
and this represents the instance. For example, a blade may have
several expansion cards that connect to the blade system planar,
and in this case, this value identifies which expansion card
instance the row represents.
Note that this slot/instance value can be determined from the
componentFirmwareTopologyPath object, but this
componentFirmwareComponentInstance object is provided as a convenience
to the user.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.3 |
componentFirmwareComponentDescriptionA short text string describing the particular component. For the
AMM and blades, this name will be the configured name or its
serial number if no user configured name is available. For all
other components, this object will provide text to identify the
component. If a text string is not available, a value of
'Not available' is presented.
For more detail, also refer to the componentInventoryProductName
object.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.4 |
componentFirmwareTypeA text description of the type of firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.5 |
componentFirmwareBuildIDA text description of the build identifier for this firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.6 |
componentFirmwareReleaseDateA text description of the release date for this firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.7 |
componentFirmwareFilenameA text description of the filename of this firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.8 |
componentFirmwareRevisionA text description of the revision level of this firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.9 |
componentFirmwareRevisionMajorA numeric identifier of the revision major number for this firmware load.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.10 |
componentFirmwareRevisionMinorA numeric identifier of the revision minor number for this firmware load.ro INTEGER .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.11 |
componentFirmwareLevelStatusThe level status of the firmware build ID.
It has three possible values as Different (mismatch firmware build ID), Match (the
same firmware build ID), Unique (only one such firmware build ID).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.12 |
componentFirmwarePendingBuildIDA text description of the build identifier for this pending firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.13 |
componentFirmwarePendingReleaseDateA text description of the release date for this pending firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.14 |
componentFirmwarePendingRevisionA text description of the revision level of this pending firmware load.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.2.23.2.1.1.15 |
componentInventoryReadyWhen a blade management controller or the AMM is reset, the
blade inventory data is refreshed in the AMM database. This includes
items like IBM VPD (e.g. - serial number, UUID) and MAC address information.
Applications need to know when this information has been populated on the AMM
before they begin to query it using SNMP or other means. This simple flag
object will return a ready or notReady indication when all blades have completed
initialization and the inventory information has been provided to the AMM.
Note that due to blades that may be experiencing a 'communication failure' or
'initialization failure' condition, this object may continue to show notReady.
Therefore, any application that polls this object should also incorporate a timeout
period. As of AMM release v5.3, a 10 minute timeout seems to be a minimum suggested
polling period.
A more granular, per-blade status is available via the bladeSystemStatusTablero Enumeration .1.3.6.1.4.1.2.3.51.2.2.23.3 |
errorLogs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.3 |
eventLog OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.3.4 |
readEventLogTableTable of event log entry information. SEQUENCE OF ReadEventLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.2 |
readEventLogEntryEvent log table entry ReadEventLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.2.1 |
readEventLogIndexThe event log index number.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.3.4.2.1.1 |
readEventLogStringA string of data detailing an event.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.3.4.2.1.2 |
clearEventLogClear the event log.
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.3.4.3 |
monitorLogStateEventsIf disabled, it means the info LED will not turn on when the log gets full
and no alerts will be sent out. If enabled, the LED will turn on when the log
gets full and alerts will be sent out.rw Enumeration .1.3.6.1.4.1.2.3.51.2.3.4.4 |
readEnhancedEventLogTableTable of enhanced event log entry information. SEQUENCE OF ReadEnhancedEventLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.6 |
readEnhancedEventLogEntryEnhaced Event log table entry, new entries could be added for new items. ReadEnhancedEventLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.6.1 |
readEnhancedEventLogNumberThe event log number for the enhanced event log.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.3.4.6.1.1 |
readEnhancedEventLogAttributeA string of data detailing an event log's attribute, such as the
Event ID and Call Home Flag. The Event ID is a hexadecimal number representing an specific or class of events.
The call home flag indicates that the corresponding problem may result in a call home.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.3.4.6.1.2 |
readEnhancedEventLogMessageA string of data detailing an event log message.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.3.4.6.1.3 |
readAuditLogTableTable of audit log entry information. Audit log includes the logs whose source is 'Audit' SEQUENCE OF ReadAuditLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.10 |
readAuditLogEntryAudit log table entry, new entries could be added for new items. ReadAuditLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.10.1 |
readAuditLogNumberThe audit log number.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.3.4.10.1.1 |
readAuditLogAttributeA string of data detailing an audit eventlog's attribute.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.3.4.10.1.2 |
readAuditLogMessageA string of data detailing an audit event log message.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.3.4.10.1.3 |
clearAuditLogClear the audit log.
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.3.4.11 |
readSystemLogTableTable of system log entry information. System log includes the logs whose source is other than 'Audit' SEQUENCE OF ReadSystemLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.12 |
readSystemLogEntrySystem log table entry, new entries could be added for new items. ReadSystemLogEntry .1.3.6.1.4.1.2.3.51.2.3.4.12.1 |
readSystemLogNumberThe system log index number.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.3.4.12.1.1 |
readSystemLogAttributeA string of data detailing an system event log's attribute.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.3.4.12.1.2 |
readSystemLogMessageA string of data detailing an system event log message.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.3.4.12.1.3 |
clearSystemLogClear the system log.
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.3.4.13 |
configureSP OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4 |
remoteAccessConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1 |
generalRemoteCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.1 |
remoteAlertRetryDelayNumber in seconds to delay between retries if sending a
remote alert is unsuccessful.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.3 |
remoteAlertRetryCountNumber of additional times a remote alert will be
retried if not successfully sent. A value of zero indicates
no retries will be attempted.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.4 |
remoteAlertEntryDelayNumber in seconds to delay between entries if sending a
remote alert is unsuccessful.
NOTE: This object is no longer supported. However, for
compatibilities sake, a value of (255) is returned when
read. Also, write access has been removed.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.5 |
remoteAccessTamperDelayThis value is no longer supported and has been replaced by
'lockoutPeriod'.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.6 |
userAuthenticationMethodUse this field to specify how users attempting to login should be authenticated.
There are two methods:
Local authentication. Userid and password are verified by searching the list
of users locally configured under Local Login Profiles.
LDAP based authentication. Users are authenticated via a remote LDAP server.
One or both authentication methods can be selected. If both methods should be
used, the order must be specified.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.7 |
maxSessionsPerLDAPUserThe maximum number of simultaneous active sessions allowed for
each LDAP user. If the value is 0, this option is disabled. The
minimum value is 1 and the maximum value is 20.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.1.9 |
authenticationLoggingTimeoutUse this option to set how long, in seconds, AMM will not log the authentication
events for the same user. The default setting is 5 minutes. 0 indicates log all
authentication events, 255 indicates don't log any new authentication events.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.10 |
trackingIPThis option indicates tracking different IP addresses for the same user is
enabled or not. If it is enabled then an access every second from
alternating IP addresses will result in multiple log entries,
regardless of the time duration set in the 'authenticaionLoggingTimeout'field.
If this flag is disabled, multiple accesses by varying IP addresses
will only be logged as 'new' accesses if they are out of the
'authenticationLoggingTimeout'.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.11 |
accountSecurityManagement OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.1.20 |
accountSecurityLevelThe level of security needed for local user login passwords.
The legacy level:
- no password required
- no password expiration
- no password re-use restrictions
- no frequency of password change restrictions
- account is locked for 2 minutes after 5 login failures
- simple password rules
- no account inactivity monitoring
The high level:
- password required
- factory default 'USERID' account password must be changed on next login
- force user to change password on first login
- password expires in 90 days
- password re-use checking enabled (last 5 passwords kept in history)
- minimum 24 hours interval between password changes
- account is locked for 60 minutes after 5 login failures
- complex password rules with 2 degrees of difference from previous password
- alert on account inactivity after 120 days
- accounts disabled after 180 days of inactivity
The custom level:
- set the password settings individually under customSecuritySettings
The default value is legacy.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.1 |
customSecuritySettings OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2 |
loginPasswordRequiredIf enabled, all users require a login password to access the AMM.
If disabled, empty password is allowed and complex password rules
will be disabled automatically.
The default value is disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.1 |
passwordExpirationPeriodThe number of days before login passwords expire. The minimum
value is 1 day and the maximum value is 365 days. The default
value is 90 days. A value of 0 disables this option.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.2 |
defaultAdminPasswordExpiredIf enabled, the factory default 'USERID' account password must
be changed on next login. The default value is disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.3 |
minimumPasswordReuseCycleThe number of unique passwords a user must choose before
reusing a password. The default value is none.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.4 |
complexPasswordRulesIf enabled, the minimum complexity rules will be enforced for all
local login passwords and 'User login password required' rule will be enabled.
The rules are as follows:
Passwords must be a minimum of eight characters.
Passwords must not be a repeat or reverse of the associated login id.
Passwords must be no more than three of the same characters used consecutively.
Passwords must contain at least three of the following combinations:
At least one lower case alphanumeric character.
At least one upper case alphanumeric character.
At least one numeric character.
At least one special character.
The default value is disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.5 |
minimumDiffCharsPasswordThe required minimum number of characters in the new password
different from the previous password. The default value is 2.
A SET of this object is ignored until the complexPasswordRules option is enabled
and the minimumPasswordReuseCycle is not none(0)rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.6 |
changePasswordFirstAccessIf enabled, the login user will be forced to change their password on
the first access after the account has been established or on
the first access after an administrator has changed the password
for the user, except for the administrator password for USERID.
The default value is disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.7 |
inactivityAlertPeriodThe period of time in days before generating an alert for a dormant
account. This value applies to all login accounts, including the
administrator account. The minimum value is 1 day and the maximum
value is 365 days. The default value is 0 which disables this option.
NOTE: This value must be less than the inactivityAlertDisablePeriod.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.8 |
inactivityAlertDisablePeriodThe period of time in days before generating an alert and disabling
a dormant account. This value applies to all login accounts, excluding
the administrator account. The minimum value is 1 day and the maximum
value is 365 days. The default value is 0 which disables this option.
NOTE: This value must be greater than the inactivityAlertPeriod.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.9 |
lockoutPeriodThe period of time in minutes that a user is locked out after the
maximum number of login failures was reached. The minimum value is
is 1 minute and the maximum value is 2880 minutes. The default value
is 2 minutes for the Legacy security level and 60 minutes for the
High security level. A value of 0 disables this option.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.10 |
maxLoginFailuresThe maximum number of login failures before a user account is locked.
A value of 0 disables this option. The default value is 5.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.11 |
passwordChangeIntervalA minimum period of time that user is not able to change
their own password. The range of acceptable values will be
from 0 to 1440 (or 60 days). A value of 0 disables this
option. If the password expiration period is set, it must be
greater than the minimum password change interval.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.1.20.2.12 |
serialPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.2 |
portBaudBaud rate for the serial port.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.2.1 |
portParityParity setting for the serial port.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.2.2 |
portStopBitsNumber of stop bits for the serial port.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.2.3 |
remoteAlertIds OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.3 |
remoteAlertIdsTableTable of remote alert entries.
This table lets you configure remote alert recipients.
You can define up to 12 unique recipients.
NOTE: All selected alert events will be sent to all
enabled alert recipients. SEQUENCE OF RemoteAlertIdsEntry .1.3.6.1.4.1.2.3.51.2.4.1.3.1 |
remoteAlertIdsEntryRemote alert entries. RemoteAlertIdsEntry .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1 |
remoteAlertIdEntryIndexIndex for remote alert entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1.1 |
remoteAlertIdEntryStatusRemote alert entry status, invalid means entry
not defined yet, disabledAndValid means entry defined
but not enabled to send an alert, enabledAndValid means
entry defined and enabled to send an alert.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1.2 |
remoteAlertIdEntryIpOrHostAddressA null terminated string that either
contains an IP address of the form '1.2.3.4'
or a host name (if DNS is enabled) for the
alert entry.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1.3 |
remoteAlertIdEntryTextDescriptionA null terminated string that contains
a text description of this entry.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1.4 |
remoteAlertIdEntryNotificationTypeRemote alert entry notification method. Types include
unknown when the type can't be determined (read-only),
ibmDirectorOverLAN for a LAN alert sent over ethernet to
IBM director, snmpOverLan for an SNMP alert over ethernet,
and emailOverLan for a E-Mail alert over ethernet.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1.5 |
remoteAlertIdEmailAddrA null terminated string that contains an
E-Mail Address. For example, 'jeb@us.ibm.com'.
Used only for an E-mail over LAN or E-Mail over PPP
notification type.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1.9 |
remoteAlertIdEntrySelectiveAlertRemote alert entry selective alert setting. A value of
critOnlyAlerts will only send critical alerts to this
remote alert recipient, a value of allAlerts will send
all alerts to this remote alert recipient.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.3.1.1.13 |
generateTestAlertGenerate a Test Alert. This will send a test alert to all configured
and enabled remote alert recipients. The text portion of the alert
will contain 'Application Posted Alert to MM'.
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.3.30 |
remoteAccessIds OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.4 |
remoteAccessIdsTableTable of remote access profiles.
This table lets you to configure all login profiles.
You can define up to 12 unique profiles.
NOTE: By default, the management module
comes configured with one login profile that allows remote
access using a login ID of 'USERID' and a password of 'PASSW0RD'
(the 0 is a zero). To avoid a potential security exposure,
we strongly recommend that you change this default Login
Profile to values of your choice. SEQUENCE OF RemoteAccessIdsEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.1 |
remoteAccessIdsEntryRemote access entries. RemoteAccessIdsEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1 |
remoteAccessIdEntryIndexIndex for Remote access entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.1 |
remoteAccessIdEntryUserIdRemote access entry null terminated string that
contains the user-id. It must not be a duplicate of
any previously configured ones.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.2 |
remoteAccessIdEntryPasswordRemote access password. The password must
contain at least one alphabetic and one
non-alphabetic character and be at least 5
characters long, or you can leave the password
field blank to set an empty password.
NOTE: Value returned by the GET command is meaningless
for this MIB object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.3 |
remoteAccessIdEntryEncodedLoginPwUsed only for configuration save/restore.
A null terminated string containing an encoded
concatenation of the login ID and password
separated by an ':'.
This object is no longer supported and will return
a string of asterisksrwdeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.7 |
remoteAccessIdEntryRoleIndicates if user has supervisor, operator, or custom access.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.10 |
remoteAccessIdEntryLoggedInIndicates if user is currently logged in or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.11 |
remoteAccessIdEntryLastLoginTimestamp for the last successful login by the user.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.12 |
remoteAccessIdEntryPwdCompliantIndicates if user complies with all of the password
rules currently in effect.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.13 |
remoteAccessIdEntryPwdExpThe number of days until the user's current password expires.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.14 |
remoteAccessIdEntryDormantIndicates if the user account has been inactive for a
specified amount of time based on inactivityAlertDisablePeriod
in the customSecuritySettings section.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.15 |
remoteAccessIdEntryStateIndicates the state of the user:
Active - normal state
Disabled - user cannot use account until enabled by a
supervisor or chassis user account manager. An account
can get disabled after being dormant for a specified
amount of time OR as a result of a supervisor or chassis
user account manager disabling it.
Locked - account is temporarily locked due to repeated
unsuccessful login attempts as specified by lockoutPeriod
in the customSecuritySettings section. Account can be
unlocked by a supervisor or chassis user account manager
OR can be automatically unlocked after the lockoutPeriod expires.
NOTE: The disable action does not apply to supervisor or chassis
user account manager accounts.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.16 |
remoteAccessIdEntryActionActions that only a supervisor or chassis user account manager
can perform for each user id:
Enable - enables an account in the Disabled state
Disable - disables an account in the Active or Locked state
Unlock - unlock an account in the Locked state
NOTE: The disable action does not apply to supervisor or chassis
user account manager accounts.
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.17 |
remoteAccessIdEntrySessionCountThe number of sessions the user is currently logged in to.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.18 |
remoteAccessIdEntryMaxSessionsThe maximum number of simultaneous active sessions allowed for
the user. If the value is 0, this option is disabled. The
minimum value is 1 and the maximum value is 20.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.4.1.1.19 |
remoteAccessUserAuthorityLevelTableTable of user authority level profiles. SEQUENCE OF RemoteAccessUserAuthorityLevelEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.2 |
remoteAccessUserAuthorityLevelEntryUser authority level entries. RemoteAccessUserAuthorityLevelEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1 |
ualIndexIndex for User Authority Level entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.1 |
ualIdUser IDro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.2 |
ualSupervisorUser has no restrictions.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.3 |
ualReadOnlyUser has only read-only access, and cannot perform any save, modify,
clear, or state affecting operations (e.g. restart MM, restore defaults,
upgrade the firmware, etc.).rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.4 |
ualAccountManagementUser can add/modify/delete users and change the global login settings in
the Login Profiles panel.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.5 |
ualConsoleAccessUser can access the remote console.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.6 |
ualConsoleAndVirtualMediaAccessUser can access both the remote console and the virtual media feature.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.7 |
ualServerPowerAccessUser can access the power on and restart functions for the remote server.
These functions are available via the Power/Restart panel.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.8 |
ualAllowClearLogUser can clear the event logs. Everyone can look at the
event logs, but this particular permission is required to clear the logs.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.9 |
ualAdapterBasicConfigUser can modify configuration parameters in the System Settings and Alerts
panels.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.10 |
ualAdapterNetworkAndSecurityConfigUser can modify configuration parameters in the Security, Network Protocols,
Network Interface, Port Assignments, and Serial Port panels.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.11 |
ualAdapterAdvancedConfigUser has no restrictions when configuring the adapter. In addition, the
user is said to have administrative access to the RSA, meaning that the
user can also perform the following advanced functions: firmware upgrades,
PXE network boot, restore adapter factory defaults, modify and restore
adapter configuration from a configuration file, and restart/reset the
adapter.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.2.1.12 |
remoteAccessRBSroleTableTable of RBS User Role profiles. SEQUENCE OF RemoteAccessRBSroleEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.3 |
remoteAccessRBSroleEntryUser Role entries. RemoteAccessRBSroleEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1 |
roleIndexIndex for RBS User Role entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.1 |
roleIdUser IDro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.2 |
rbsSupervisorUser has no restrictions.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.3 |
rbsOperatorUser has read-only access, and cannot perform
any save, modify, clear, or state affecting operations
(e.g. restart MM, restore defaults, upgrade the firmware, etc.).rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.4 |
rbsChassisOperatorUser has ability to browse status and properties of
chassis components (MM, blowers (chassis cooling devices), midplane, power modules,
media tray. Ability to backup MM configuration to a file.
Saving MM configuration to chassis requires supervisor access.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.5 |
rbsChassisAccountManagementUser can add/modify/delete user login profiles. Ability
to backup MM configuration to a file. Changing global login
settings require chassis configuration authority.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.6 |
rbsChassisLogManagementUser has ability to clear the MM event log, change log
policy settings, and backup MM configuration to a file.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.7 |
rbsChassisConfigurationUser can modify and save any chassis configuration
parameter (except user profiles and event log settings).
Ability to restore MM factory defaults if the user also has
chassis administration permissions. Ability to change the
global login settings, SOL configuration, and backup MM
configuration to a file.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.8 |
rbsChassisAdministrationUser has ability to do MM firmware updates, modify chassis
LEDs, restore MM factory defaults if the user also has
chassis configuration permissions. Ability to restart MM
and backup MM configuration to a file.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.9 |
rbsBladeOperatorUser has ability to browse status and properties of
blades.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.10 |
rbsBladeRemotePresenceUser has ability to access the Remote Control web panel
and the functions provided on the panel: remote console
(KVM) and remote disk. The ability to issue the CLI
console command to start an SOL session to a blade will
also require this authority.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.11 |
rbsBladeConfigurationUser can modify and save any blade configuration parameter.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.12 |
rbsBladeAdministrationUser can power on/off and restart blades, activate
standby blades, do firmware updates, and modify blade LEDs.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.13 |
rbsSwitchModuleOperatorUser has ability to browse status and properties of
I/O Modules, and to ping I/O Modules.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.14 |
rbsSwitchModuleConfigurationUser can modify the I/O Module IP address, configure
I/O Module Advanced Management parameters, and restore
factory defaults on an I/O Module. Note that a user
requires both I/O Module configuration and I/O Module
administration roles in order to be able to launch a telnet
or web UI session to an I/O Module, or to restore factory
defaults on an I/O Module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.15 |
rbsSwitchModuleAdministrationUser can power on/off and restart the I/O Modules,
update I/O Module firmware, enable/disable the Fast POST
and External Ports of an I/O Module. Note that a user
requires both I/O Module configuration and I/O Module
administration roles in order to be able to launch a telnet
or web UI session to an I/O Module, or to restore factory
defaults on an I/O Module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.16 |
rbsBladeRemotePresenseVideoUser can browser Remote Control web panel and remote blade video.
NOTE: This mib object is deprecated. This level of granularity is available
via the LDAP snap-in tool.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.17 |
rbsBladeRemotePresenseKVMUser has ability to access the Remote Control web panel
and the functions provided on the panel: remote console
(KVM) and remote disk.
NOTE: This mib object is deprecated. This level of granularity is available
via the LDAP snap-in tool.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.18 |
rbsBladeRemotePresenseRdriveRUser can mount remote blade driver, and have read access only.
NOTE: This mib object is deprecated. This level of granularity is available
via the LDAP snap-in tool.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.19 |
rbsBladeRemotePresenseRdriveRWUser can mount remote blade driver and have read/write access.
NOTE: This mib object is deprecated. This level of granularity is available
via the LDAP snap-in tool.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.20 |
rbsChassisRemotePresenseRdocUser has ability to upload/delete own image to RDOC and also
can start remote control web panel.
NOTE: This mib object is deprecated. This level of granularity is available
via the LDAP snap-in tool.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.21 |
rbsRemotePresenceSupervisorUser has ability to access the Remote Control web panel
and the functions provided on the panel: remote console
(KVM) and remote driver read/write, upload/delete himself
and other's image to RDOC.
NOTE: This mib object is deprecated. This level of granularity is available
via the LDAP snap-in tool.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.3.1.22 |
remoteAccessRBSscopeTableTable of RBS User Scope profiles. SEQUENCE OF RemoteAccessRBSscopeEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.4 |
remoteAccessRBSscopeEntryUser Scope entries. RemoteAccessRBSscopeEntry .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1 |
scopeIndexIndex for RBS User Scope Entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.1 |
scopeIdUser IDro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.2 |
rbsChassisUser has access to the MM and chassis functions.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.3 |
rbsBlade1User has access to the blade in slot 1.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.4 |
rbsBlade2User has access to the blade in slot 2.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.5 |
rbsBlade3User has access to the blade in slot 3.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.6 |
rbsBlade4User has access to the blade in slot 4.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.7 |
rbsBlade5User has access to the blade in slot 5.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.8 |
rbsBlade6User has access to the blade in slot 6.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.9 |
rbsBlade7User has access to the blade in slot 7.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.10 |
rbsBlade8User has access to the blade in slot 8.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.11 |
rbsBlade9User has access to the blade in slot 9.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.12 |
rbsBlade10User has access to the blade in slot 10.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.13 |
rbsBlade11User has access to the blade in slot 11.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.14 |
rbsBlade12User has access to the blade in slot 12.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.15 |
rbsBlade13User has access to the blade in slot 13.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.16 |
rbsBlade14User has access to the blade in slot 14.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.17 |
rbsSwitch1User has access to I/O module 1.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.18 |
rbsSwitch2User has access to I/O module 2.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.19 |
rbsSwitch3User has access to I/O module 3.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.20 |
rbsSwitch4User has access to I/O module 4.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.21 |
rbsSwitch5User has access to I/O module 5.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.22 |
rbsSwitch6User has access to I/O module 6.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.23 |
rbsSwitch7User has access to I/O module 7.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.24 |
rbsSwitch8User has access to I/O module 8.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.25 |
rbsSwitch9User has access to I/O module 9.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.26 |
rbsSwitch10User has access to I/O module 10.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.4.4.1.27 |
userInterfaces OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.5 |
cliEnable/Disable CLI access to the MM (telnet and SSH).
The value enabled(3) means both telnet and ssh are enabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.5.1 |
snmpEnable/Disable SNMP v1 and v3 access to the MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.5.2 |
tcmEnable/Disable TCM access to the MM.
A value of 0 means disabled, any value from 1 to 20 means enabled.
NOTE: AMM will provide a max of 20 connections for both
Secure TCP Command Mode and TCP Command Mode.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.5.3 |
webEnable/Disable Web access (HTTP/HTTPS) to the MM.
NOTE: Disabling web access to the MM will cause all
currently active web sessions to disconnect,
and you will no longer be able to access the
MM management functions using a web browser.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.5.4 |
stcmEnable/Disable STCM access to the MM.
A value of 0 means disabled, any value from 1 to 20 means enabled.
NOTE: AMM will provide a max of 20 connections for both
Secure TCP Command Mode and TCP Command Mode.
If no valid server certificate is in place,
Secure TCP Command Mode will not be allowed to set to enable.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.5.5 |
mmSshClientAuth OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.6 |
mmSshClientAuthPubKeyTableA table that contains client authentication
public key information. SEQUENCE OF MmSshClientAuthPubKeyEntry .1.3.6.1.4.1.2.3.51.2.4.1.6.1 |
mmSshClientAuthPubKeyEntryA information list about a particular SSH
public key used for client authentication.
The primary table index is the same value as
the associated remoteAccessIdEntryIndex.
The secondary table index allows selection
of the Nth public key for that
remoteAccessIdEntryIndex. MmSshClientAuthPubKeyEntry .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1 |
mmSshClientAuthRemoteAccessIdIndexThe primary table index is the same value as
the associated remoteAccessIdEntryIndex used
as an index into the remoteAccessIdsTable. INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.1 |
mmSshClientAuthPubKeyIndexThe secondary table index used to select
one of the client authentication public
keys for a particular remote access Id.
The index is an integer value from 1 to N
where N is the number of keys associated
with a particular remote access Id.
An addition always causes the value of N to increase
by one, effectively adding an entry after the
existing keys for that remote access Id.
If an entry is deleted from the table by
setting mmSshClientAuthPubKeyEntryStatus = invalid,
the key associated with that entry is deleted.
If the deleted key was not the last key for
a remote access Id (mmSshClientAuthPubKeyIndex is
not the 'last' or Nth entry), the subsequent entries
are renumbered after the deletion. A deletion
always causes the value of N to decrease by one.
The underlying SSH server implementation searches
the keys in order from 1 to N when attempting public
key authentication.
NOTE:A maximum of 4 public keys can be installed
for one remote access Id. INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.2 |
mmSshClientAuthPubKeyTypeThe type of the SSH public key represented by
this entry.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.3 |
mmSshClientAuthPubKeySizeThe size of the SSH public key represented by
this entry.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.4 |
mmSshClientAuthPubKeyFingerprintThe RSA fingerprint of the SSH public key represented
by this entry.
This value can be used with the SSH client to
verify, on the initial connection, that the Secure Shell
server responding to the request is the server running
on the managed entity. This is the fingerprint of the
operational host key pair. If the key pair represented
by this entry is not operational then sixteen null octets
must be returned.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.5 |
mmSshClientAuthPubKeyAcceptFromThis is a filter that describes the set of SSH client
IP addresses and host names that can establish
SSH connections to the AMM authenticated by the public key
represented by this entry of the table. The filter is a
comma-separated list of IP addresses and/or hostnames.
A question mark may be used to match any single character.
An asterisk may be used to match multiple characters.
An exclamation point may preceed an IP address or hostname
to deny acccess from that IP address or hostname.
The format of the Accept From specification is:
from=PATTERN-LIST
PATTERN-LIST is the filter, which must be enclosed in
double quotation marks.
NOTE:This MIB object can be manipulated after the
corresponding SSH public key is installed.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.6 |
mmSshClientAuthPubKeyCommentThis is a descriptive string that the administrator may
use to help identify the public key represented by this entry.
It serves no function in the operation of the SSH server.
NOTE:This MIB object can be manipulated after the
corresponding SSH public key is installed.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.7 |
mmSshClientAuthPubKeyActionimport(1) starts the TFTP file transfer of an SSH
client authentication public key from the TFTP
server to the AMM. The import operation is only
accepted if the associated RemoteAccessIdsEntry row
is configured and the current value of
mmSshClientAuthPubKeyEntryStatus is underCreation(3)
or valid(1), if the current value of mmSshClientAuthPubKeyEntryStatus
is valid(1), it will replace the key with a new key,
If the import is successful the value of
mmSshClientAuthPubKeyRowStatus changes to valid(1).
export(2) starts the TFTP file transfer of an SSH
client authentication public key from the AMM to the TFTP
server. The export operation is only accepted if
the current value of mmSshClientAuthPubKeyEntryStatus
is valid(1).
NOTE: Users should compare the fingerprint value
mmSshClientAuthPubKeyFingerprint to the
fingerprint of client authentication key files
imported or exported using the TFTP file transfer
protocol to guard against possible file corruption.
Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.8 |
mmSshClientAuthPubKeyEntryStatusThis object manages the creation and deletion of this entry.
The steps recommended to install and to activate a new client
authorization public key are:
1. Set values for mmSshClientAuthPubKeyTftpServer,
mmSshClientAuthPubKeyFileName, mmSshClientAuthPubKeyFileFormat
2. Create a new entry in this table
mmSshClientAuthPubKeyEntryStatus = createRequest
3. Import a new key mmSshClientAuthPubKeyAction = import
This entry will be valid after mmSshClientAuthPubKeyAction
is successfully imported.
4. Set mmSshClientAuthPubKeyAcceptFrom and
mmSshClientAuthPubKeyComment as required.
valid(1) - Indicates that the public key pair represented
by this entry is available for use by the Secure
Shell Server for client authentication.
createRequest(2) - A new entry will be created in this table
for the specified host key pair and the new
entry will transition to the underCreation(3)
state. The operation is only accepted if the
associated RemoteAccessIdsEntry row defining
a local user account is configured.
underCreation(3) - Indicates that this entry exists in the
agent but is unavailable for use. After completing the
create operation, the agent will set this object to
underCreation(3).
invalid(4) - Deletes this entry and any client authentication
public key that may be associated with it.rw EntryStatus .1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.9 |
mmSshClientAuthPubKeyUnusedThe number of available storage locations that may be
used to install additional Client Authentication
Public Keys. This number decreases by one when a new
key is added to the configuration.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.6.2 |
mmSshClientAuthPubKeyTftpServerIP address or host name of the TFTP server where an SSH client
authentication public key is to be installed from or exported
to. The address must be entered in a dotted decimal
IP string (e.g. 9.37.44.2).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.6.3 |
mmSshClientAuthPubKeyFileNameFile name on the TFTP server of an SSH client
authentication public key.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.6.4 |
mmSshClientAuthPubKeyFileFormatFile format of SSH client authentication public key files
imported from or exported to the TFTP file server.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.6.5 |
groupProfiles OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.1.7 |
groupIdsTableTable of Group profiles.
This table lets you to configure all group profiles.
You can define up to 16 unique profiles. SEQUENCE OF GroupIdsEntry .1.3.6.1.4.1.2.3.51.2.4.1.7.1 |
groupIdsEntryGroup ID entries. GroupIdsEntry .1.3.6.1.4.1.2.3.51.2.4.1.7.1.1 |
groupIndexIndex for Group IDs entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.7.1.1.1 |
groupIdGroup ID. It is a null terminated string that contains the group-id.
It must not be a duplicate of any previously configured ones.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.7.1.1.2 |
groupRoleGroup Role. It indicates if the group has supervisor, operator,
or custom access.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.7.1.1.3 |
groupEntryStatusThis object manages the creation and deletion of this entry.
The steps recommended to add a new group are:
1. Create a new entry in this table
groupEntryStatus = createRequest
2. Set groupId as required.
Then the entry will be valid.
valid(1) - Indicates that the group represented
by this entry is available for use.
createRequest(2) - A new entry will be created in this table
for the specified group and the new entry
will transition to the underCreation(3).
underCreation(3) - Indicates that this entry exists in the
agent but is unavailable for use. After completing the
create operation, the agent will set this object to
underCreation(3).
invalid(4) - Deletes this entry.rw EntryStatus .1.3.6.1.4.1.2.3.51.2.4.1.7.1.1.9 |
groupRBSroleTableTable of Group Role profiles. SEQUENCE OF GroupRBSroleEntry .1.3.6.1.4.1.2.3.51.2.4.1.7.2 |
groupRBSroleEntryGroup Role entries. GroupRBSroleEntry .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1 |
groupRBSroleIndexIndex for Group Role entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.1 |
groupRBSroleIdGroup IDro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.2 |
groupRBSSupervisorGroup has no restrictions.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.3 |
groupRBSOperatorGroup has read-only access, and cannot perform
any save, modify, clear, or state affecting operations
(e.g. restart MM, restore defaults, upgrade the firmware, etc.).rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.4 |
groupRBSChassisOperatorGroup has ability to browse status and properties of
chassis components (MM, blowers (chassis cooling devices), midplane, power modules,
media tray. Ability to backup MM configuration to a file.
Saving MM configuration to chassis requires supervisor access.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.5 |
groupRBSChassisAccountManagementGroup can add/modify/delete user login profiles. Ability
to backup MM configuration to a file. Changing global login
settings require chassis configuration authority.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.6 |
groupRBSChassisLogManagementGroup has ability to clear the MM event log, change log
policy settings, and backup MM configuration to a file.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.7 |
groupRBSChassisConfigurationGroup can modify and save any chassis configuration
parameter (except user profiles and event log settings).
Ability to restore MM factory defaults if the group also has
chassis administration permissions. Ability to change the
global login settings, SOL configuration, and backup MM
configuration to a file.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.8 |
groupRBSChassisAdministrationGroup has ability to do MM firmware updates, modify chassis
LEDs, restore MM factory defaults if the group also has
chassis configuration permissions. Ability to restart MM
and backup MM configuration to a file.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.9 |
groupRBSBladeOperatorGroup has ability to browse status and properties of
blades.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.10 |
groupRBSBladeRemotePresenceGroup has ability to access the Remote Control web panel
and the functions provided on the panel: remote console
(KVM) and remote disk. The ability to issue the CLI
console command to start an SOL session to a blade will
also require this authority.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.11 |
groupRBSBladeConfigurationGroup can modify and save any blade configuration parameter.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.12 |
groupRBSBladeAdministrationGroup can power on/off and restart blades, activate
standby blades, do firmware updates, and modify blade LEDs.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.13 |
groupRBSSwitchModuleOperatorGroup has ability to browse status and properties of
I/O Modules, and to ping I/O Modules.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.14 |
groupRBSSwitchModuleConfigurationGroup can modify the I/O Module IP address, configure
I/O Module Advanced Management parameters, and restore
factory defaults on an I/O Module. Note that a group
requires both I/O Module configuration and I/O Module
administration roles in order to be able to launch a telnet
or web UI session to an I/O Module, or to restore factory
defaults on an I/O Module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.15 |
groupRBSSwitchModuleAdministrationGroup can power on/off and restart the I/O Modules,
update I/O Module firmware, enable/disable the Fast POST
and External Ports of an I/O Module. Note that a group
requires both I/O Module configuration and I/O Module
administration roles in order to be able to launch a telnet
or web UI session to an I/O Module, or to restore factory
defaults on an I/O Module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.2.1.16 |
groupRBSscopeTableTable of Group Scope profiles. SEQUENCE OF GroupRBSscopeEntry .1.3.6.1.4.1.2.3.51.2.4.1.7.3 |
groupRBSscopeEntryGroup Scope entries. GroupRBSscopeEntry .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1 |
groupRBSscopeIndexIndex for Group Scope Entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.1 |
groupRBSscopeIdGroup IDro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.2 |
groupRBSChassisGroup has access to the MM and chassis functions.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.3 |
groupRBSBlade1Group has access to the blade in slot 1.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.4 |
groupRBSBlade2Group has access to the blade in slot 2.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.5 |
groupRBSBlade3Group has access to the blade in slot 3.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.6 |
groupRBSBlade4Group has access to the blade in slot 4.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.7 |
groupRBSBlade5Group has access to the blade in slot 5.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.8 |
groupRBSBlade6Group has access to the blade in slot 6.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.9 |
groupRBSBlade7Group has access to the blade in slot 7.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.10 |
groupRBSBlade8Group has access to the blade in slot 8.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.11 |
groupRBSBlade9Group has access to the blade in slot 9.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.12 |
groupRBSBlade10Group has access to the blade in slot 10.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.13 |
groupRBSBlade11Group has access to the blade in slot 11.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.14 |
groupRBSBlade12Group has access to the blade in slot 12.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.15 |
groupRBSBlade13Group has access to the blade in slot 13.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.16 |
groupRBSBlade14Group has access to the blade in slot 14.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.17 |
groupRBSSwitch1Group has access to I/O module 1.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.18 |
groupRBSSwitch2Group has access to I/O module 2.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.19 |
groupRBSSwitch3Group has access to I/O module 3.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.20 |
groupRBSSwitch4Group has access to I/O module 4.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.21 |
groupRBSSwitch5Group has access to I/O module 5.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.22 |
groupRBSSwitch6Group has access to I/O module 6.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.23 |
groupRBSSwitch7Group has access to I/O module 7.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.24 |
groupRBSSwitch8Group has access to I/O module 8.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.25 |
groupRBSSwitch9Group has access to I/O module 9.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.26 |
groupRBSSwitch10Group has access to I/O module 10.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.1.7.3.1.27 |
remoteAlerts OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.2 |
remoteAlertsCrit OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.2.1 |
critTempGenerate an alert if any of the monitored temperature sensors
in the system exceed their critical threshold.
NOTE: If a critical Temperature condition is detected,
the server will automatically be shut down and powered off
whether this object is enabled or not.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.1 |
critVoltGenerate a alert if any of the monitored power supply sensors
in the system fall outside their specified critical
operational range.
NOTE: If a critical voltage condition is detected,
the server will automatically be shut down and powered off
whether this object is enabled or not.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.2 |
critMultiBlowerGenerate an alert if multiple blowers used for cooling the system fail.
NOTE: Blowers are also referred to as Chassis Cooling Devices.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.4 |
critPowerGenerate an alert if any of the system power supplies fail.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.5 |
critHardDriveGenerate an alert if any of hard disk drives fail.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.6 |
critVRMGenerate an alert if any of VRM (voltage regulator modules) fail.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.7 |
critMultipleSwitchModuleGenerate an alert if all switch modules fail or are removed.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.8 |
critInvalidConfigGenerate an alert if the hardware configuration is incompatible.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.9 |
critBladeGenerate an alert for any critical error condition on a blade.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.10 |
critIOGenerate an alert for any critical error condition on I/O module.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.11 |
critStorageGenerate an alert for any critical error condition on a Storage module.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.
NOTE: This MIB object is for BCS only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.12 |
critChassisGenerate an alert for any critical error condition on chassis.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.13 |
critFanGenerate an alert for any critical error condition on cooling devices.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.1.14 |
remoteAlertsNonCrit OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.2.2 |
warnSingleBlowerGenerate an alert if one blower used for cooling the system fails.
NOTE: Blowers are also referred to as Chassis Cooling Devices.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.2 |
warnTempGenerate an alert if any of the monitored temperature sensors
in the system exceed their warning threshold.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.3 |
warnVoltageGenerate an alert if any of the monitored power supply sensors
in the system fall outside their specified warning operational range.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.4 |
warnRedundantModuleGenerate an alert if any of the switch modules or management
modules is failing or removed.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.6 |
warnMediaTrayKVMSwitchGenerate an alert if the system detects a Media Tray or KVM
switching failure.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.7 |
warnLogFullGenerate an alert if the system log reaches 100% full.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.10 |
warnBladeGenerate an alert for any warning condition on a blade.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.15 |
warnIOGenerate an alert for any warning condition on I/O module.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.16 |
warnStorageGenerate an alert for any warning condition on a Storage module.
NOTE: This MIB object is for BCS only.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.17 |
warnPowerGenerate an alert for any warning condition on power module.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.18 |
warnChassisGenerate an alert for any warning condition on chassis.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.19 |
warnFanGenerate an alert for any warning condition on cooling devices.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.2.20 |
remoteAlertsSystem OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.2.3 |
systemPowerOffGenerate an alert if the system is powered off.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.4 |
systemPowerOnGenerate a alert if the system is powered on.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.5 |
systemPFAGenerate a alert if the system hardware detects a Predictive
Failure Analysis(PFA) on PFA enabled hardware.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.8 |
systemInventoryGenerate an alert if the a processor blade or media tray is
added or removed.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.10 |
systemLog75PctFullGenerate an alert if the system log reaches 75% full.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.11 |
networkChangeNotificationGenerate an alert if the SP has restarted and the internal
network has initialized successfully, or if an IP address
change via a source other than the management module.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.12 |
systemBladeThrottlingGenerate an alert if any of the server blades are throttling.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.13 |
systemPowerManagementGenerate an alert if the system detects a power oversubscription
condition or power supply mismatch in a power domain.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.14 |
systemRemoteLoginGenerate an alert if the system detects a new user logged in from
a remote site.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.15 |
systemBladeGenerate an alert for any informational condition on a blade.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.16 |
systemIOGenerate an alert for any informational condition on I/O module.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.17 |
systemStorageGenerate an alert for any informational condition on a Storage module.
NOTE: This MIB object is for BCS only.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.18 |
systemPowerGenerate an alert for any informational condition on power module.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.19 |
systemChassisGenerate an alert for any informational condition on chassis.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.20 |
systemFanGenerate an alert for any informational condition on cooling device.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.21 |
systemPWRDOGenerate an alert for any informational condition on power on and power off.
NOTE: This object is valid when the alertMode object is
set enhanced(1) and should be used for all alert
category configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.3.22 |
alertModeSelects which alert categories will be displayed on the
web interface, which alert category objects are accessible
through SNMP, and which SNMP trap type an alert is associated with.
The enhanced option provides a component based category
category scheme and is the only one that is now supported.
NOTE: The legacy(0) mode alerts should no longer be used
and have been deprecated for several releases. They are
now also changed to be read-only and any future modifications
to the alert category settings must be done only with the
enahanced(1) mode alerts. Therefore, this setting should
have a value of enhanced(1).rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.2.4 |
securitySettings OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.3 |
dataEncryptionIf enabled, all confidential data will be encrypted. The default value is disabled.
NOTE: Once the data is encrypted, the only way to reverse this process is to
reset to default values.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.3.1 |
trespassWarningIf enabled, a customizable trespass warning message is displayed via the Web
and CLI interfaces.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.3.2 |
trespassWarningDefaultReset the trespass warning to default value.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.3.3 |
trespassMessageThe value of the trespass warning message.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.3.4 |
spClock OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.4 |
spClockDateAndTimeSettingMM clock date and time setting.
A date-time specification for the local time of day.
For example to set the date and time to
March 4, 2001 at 06:00:00AM, set the value to:'03/04/2001,06:00:00'.
field contents range
_____ ________ _____
1 month 01..12
2 separator '/'
3 day 01..31
4 separator '/'
5 year 2000..2089
6 separator ','
7 hour 00..23
8 separator ':'
9 minutes 00..59
10 separator ':'
11 seconds 00..59rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.4.1 |
spClockTimezoneSettingMM clock Greenwich Mean Time(GMT) offset and Daylight Saving Time(DST)
settings.
The following table lists GMT offsets and associated DST
information. DST is not observed in time zones where
the 'Observe DST' value does not contain 'yes' in the table.
Also, note that in some cases additional information
is required to determine the clock adjustment when DST is
observed. The additional information is required when the
GMT offset being written is +2:00 or +10:00.
Examples
-to set the GMT offset to +3:30,
set the value to:'+3:30,no'
-for Eastern Standard Time and observing DST,
set the value to:'-5:00,yes'
-for Egypt and observing DST,
set the value to:'+2:00,yes,6'
GMT Observe Additional
Offset DST? DST value
______ _______ __________
+0:00 yes|no
+1:00 yes|no
+2:00 yes|no When 'Observe DST?' value is 'yes':
5 (for E.Europe)
4 (for GTB)
6 (for Egypt)
7 (for FLE)
+3:00 yes|no
+3:30 yes|no
+4:00 no
+4:30 no
+5:00 yes|no
+5:30 no
+6:00 no
+7:00 no
+8:00 yes|no
+9:00 yes|no
+9:30 yes|no When 'Observe DST?' value is 'yes':
10 (for South AUS)
9 (for other locations)
+10:00 yes|no When 'Observe DST?' value is 'yes':
9 (for AUS Eastern)
10 (for TAS,ACT,NSW,VIC)
4 (for Vladivostok)
+11:00 no
+12:00 yes|no
-12:00 no
-11:00 no
-10:00 no
-9:00 yes|no When 'Observe DST?' value is 'yes':
12 (for USA and Canada)
1 (for other locations)
-8:00 yes|no When 'Observe DST?' value is 'yes':
12 (for USA and Canada)
1 (for other locations)
-7:00 yes|no When 'Observe DST?' value is 'yes':
12 (for USA and Canada)
1 (for other locations)
-6:00 yes|no When 'Observe DST?' value is 'yes':
12 (for USA and Canada)
1 (for other locations)
-5:00 yes|no When 'Observe DST?' value is 'yes':
12 (for USA and Canada)
1 (for other locations)
-4:00 yes|no When 'Observe DST' value is 'yes':
12 (for Canada)
1 (for other locations)
-3:30 yes|no
-3:00 yes|no
-2:00 yes|no
-1:00 yes|norw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.4.2 |
spIdentification OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.5 |
spTxtIdMM text ID.
NOTE: Do not put any 'space characters' at end of the ID.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.5.1 |
networkConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9 |
networkInterfaces OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1 |
extEthernetInterface OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.1 |
extEthernetInterfaceTypeThe type of interface. Indicates 'Ethernet-1'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.1.1 |
extEthernetInterfaceHostNameContains the 64 byte null terminated DNS host name for this
interface.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.1.3 |
extEthernetInterfaceIPAddressContains the IP address for the ethernet interface.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.4 |
extEthernetInterfaceDataRateSpecifies the data transfer rate to be used over the ethernet
interface: 10Mb, 100Mb, 1G Auto or Auto.
Note that not all AMM hardware supports the 1G Auto speed. If it does not
and a SET of this value is attempted, it will be rejected with a
badValue return code.
When a user selects the 1G Auto setting, the duplex setting will be forced to
fullDuplex.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.1.5 |
extEthernetInterfaceDuplexSettingSpecifies the duplex settings for the data transfer rate to be used over
the ethernet interface: Half, Full, or Auto.
When a user selects the 1G Auto speed setting, the duplex setting will be forced to
fullDuplex.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.1.6 |
extEthernetInterfaceLAASpecifies the locally administered MAC address. The locally administered
address must be a hexadecimal value between 000000000000 - FFFFFFFFFFFF. This
value must be in the form XX:XX:XX:XX:XX:XX where 'X' is a number between 0 - 9 and
A - F. This MM subsystem does not allow use of a multicast address. A multicast
address has the least significant bit of the first byte set to a 1. The first
byte must, therefore, be an even number.
NOTE: Although the locally administered MAC address can be assigned the same value
for the primary and backup AMM, it is not recommended.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.1.7 |
extEthernetInterfaceDhcpEnabledDisable or enable DHCP on this interface.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.1.8 |
extEthernetInterfaceGatewayIPAddressContains the IP address of the gateway/router for the ethernet
interface.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.9 |
extEthernetInterfaceBIASpecifies the burned-in MAC (BIA) address.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.1.10 |
extEthernetInterfaceMTUContains the Maximum Transmission Unit(MTU) for the ethernet
interfacerw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.1.13 |
extEthernetInterfaceSubnetMaskContains the subnet mask for the ethernet interfacerw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.14 |
dhcpEthernetInterface OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16 |
dhcpHostNameContains the 64 byte null terminated DNS host name for this
interface, assigned by the DHCP server.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.1 |
dhcpIPAddressContains the IP address for the ethernet interface,
assigned by the DHCP server.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.2 |
dhcpGatewayIPAddressContains the IP address of the gateway/router for the ethernet
interface, assigned by the DHCP server.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.3 |
dhcpSubnetMaskContains the Subnet Mask for the ethernet
interface, assigned by the DHCP server.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.4 |
dhcpDomainNameContains the 64 byte null terminated Domain Name for this
interface, assigned by the DHCP server.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.5 |
dhcpDHCPServerContains the DHCP server IP address used to acquire the
DHCP settings.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.6 |
dhcpPrimaryDNSServerContains the Primary DNS server, assigned by the DHCP server.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.7 |
dhcpSecondaryDNSServerContains the Secondary DNS server, assigned by the DHCP server.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.8 |
dhcpTertiaryDNSServerContains the tertiary DNS server, assigned by the DHCP server.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.1.16.9 |
intEthernetInterface OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.2 |
intEthernetInterfaceTypeThe type of interface. Indicates 'PPP-1'.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.2.1 |
intEthernetInterfaceEnabledDisable or enable the internal ethernet interface.
NOTE: To alter any of the configuration settings for the
ethernet interface, the following procedure should be used:
(1) This object should be set to 'interfaceDisabled'
(2) Make the modifications to other settings
(3) This object should be set to 'interfaceEnabled'
(4) Restart the management module
Also note that when attempting to enable this interface, the
remote IP address is verified to be nonzero. If this verification
fails, an error response will be returned and the internal ethernet
interface will be left disabled.
NOTE: This Mib object is deprecated and no longer supported.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.2.2 |
intEthernetInterfaceLocalIPAddressContains the IP address for the MM side of the internal ethernet link.
NOTE: This Mib object is deprecated and no longer supported.rwdeprecated IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.2.4 |
intEthernetInterfaceDataRateSpecifies the data transfer rate to be used over the ethernet
interface: 10Mb, 100Mb, or Auto.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.2.5 |
intEthernetInterfaceDuplexSettingSpecifies the duplex settings for the data transfer rate to be used over
the ethernet interface: Half, Full, or Auto.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.2.6 |
intEthernetInterfaceLAASpecifies the locally administered MAC address. The locally administered
address must be a hexadecimal value between 000000000000 - FFFFFFFFFFFF. This
value must be in the form XX:XX:XX:XX:XX:XX where 'X' is a number between 0 - 9 and
A - F. This MM subsystem does not allow use of a multicast address. A multicast
address has the least significant bit of the first byte set to a 1. The first
byte must, therefore, be an even number.
NOTE: This Mib object is deprecated and no longer supported.rwdeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.2.7 |
intEthernetInterfaceGatewayIPAddressContains the IP address of the gateway/router for the ethernet
interface.
NOTE: This Mib object is deprecated and no longer supported.rwdeprecated IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.2.9 |
intEthernetInterfaceBIASpecifies the burned-in MAC (BIA) address.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.2.10 |
intEthernetInterfaceMTUContains the Maximum Transmission Unit (MTU) for the ethernet
interface
NOTE: This Mib object is deprecated and no longer supported.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.2.13 |
intEthernetInterfaceSubnetMaskContains the subnet mask for the ethernet interface.
NOTE: This Mib object is deprecated and no longer supported.rwdeprecated IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.2.14 |
standbyExtEthernetInterface OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.3 |
standbyExtEthernetInterfaceTypeThe type of interface. Indicates 'Ethernet-1'.
NOTE: This MIB object is only applicable to systems with a standby MM.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.3.1 |
standbyExtEthernetInterfaceHostNameContains the 64 byte null terminated DNS host name for this
interface.
NOTE: This MIB object is only applicable to systems with a standby MM.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.3.3 |
standbyExtEthernetInterfaceIPAddressContains the IP address for the ethernet interface.
NOTE: This MIB object is only applicable to systems with a standby MM.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.4 |
standbyExtEthernetInterfaceDataRateSpecifies the data transfer rate to be used over the ethernet
interface: 10Mb, 100Mb, 1G Auto or Auto.
NOTE: This MIB object is only applicable to systems with a standby MM.
Note that not all AMM hardware supports the 1G Auto speed. If it does not
and a SET of this value is attempted, it will be rejected with a
badValue return code.
When a user selects the 1G Auto setting, the duplex setting will be forced to
fullDuplex.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.3.5 |
standbyExtEthernetInterfaceDuplexSettingSpecifies the duplex settings for the data transfer rate to be used over
the ethernet interface: Half, Full, or Auto.
NOTE: This MIB object is only applicable to systems with a standby MM.
When a user selects the 1G Auto speed setting, the duplex setting will be forced to
fullDuplex.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.3.6 |
standbyExtEthernetInterfaceLAASpecifies the locally administered MAC address. The locally administered
address must be a hexadecimal value between 000000000000 - FFFFFFFFFFFF.
This value must be in the form XX:XX:XX:XX:XX:XX where 'X' is a number between 0 - 9 and A - F.
This MM subsystem does not allow use of a multicast address.
A multicast address has the least significant bit of the first byte set to a 1. The first
byte must, therefore, be an even number.
NOTE: This MIB object is only applicable to systems with a standby MM.
NOTE: Although the locally administered MAC address can be assigned the same value
for the primary and backup AMM, it is not recommended.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.3.7 |
standbyExtEthernetInterfaceDhcpEnabledDisable or enable DHCP on this interface.
NOTE: This MIB object is only applicable to systems with a standby MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.3.8 |
standbyExtEthernetInterfaceGatewayIPAddressContains the IP address of the gateway/router for the ethernet
interface.
NOTE: This MIB object is only applicable to systems with a standby MM.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.9 |
standbyExtEthernetInterfaceBIASpecifies the burned-in MAC (BIA) address.
NOTE: This MIB object is only applicable to systems with a standby MM.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.3.10 |
standbyExtEthernetInterfaceMTUContains the Maximum Transmission Unit (MTU) for the ethernet
interface.
NOTE: This MIB object is only applicable to systems with a standby MM.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.3.13 |
standbyExtEthernetInterfaceSubnetMaskContains the subnet mask for the ethernet interface.
NOTE: This MIB object is only applicable to systems with a standby MM.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.14 |
advancedFailoverUser can enable advanced failover.
off : no standby network interface
ipswap: Standby network interface, swap IPs during failover
ipnoswap: Standby network interface, no swap IPs during failover.
NOTE: This MIB object is only applicable to systems with a standby MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.3.15 |
standbyDhcpEthernetInterface OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16 |
standbyDhcpHostNameContains the 64 byte null terminated DNS host name for this
interface, assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.1 |
standbyDhcpIPAddressContains the IP address for the ethernet interface,
assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.2 |
standbyDhcpGatewayIPAddressContains the IP address of the gateway/router for the ethernet
interface, assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.3 |
standbyDhcpSubnetMaskContains the Subnet Mask for the ethernet
interface, assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.4 |
standbyDhcpDomainNameContains the 64 byte null terminated Domain Name for this
interface, assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.5 |
standbyDhcpDHCPServerContains the DHCP server IP address used to acquire the
DHCP settings.
NOTE: This MIB object is only applicable to systems with a standby MM.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.6 |
standbyDhcpPrimaryDNSServerContains the Primary DNS server, assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.7 |
standbyDhcpSecondaryDNSServerContains the Secondary DNS server, assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.8 |
standbyDhcpTertiaryDNSServerContains the tertiary DNS server, assigned by the DHCP server.
NOTE: This MIB object is only applicable to systems with a standby MM.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.1.3.16.9 |
extEthernetInterfaceIPv6 OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.4 |
extEthernetInterfaceIPv6TypeThe type of interface. Indicates 'Ethernet-1'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.4.1 |
extEthernetInterfaceIPv6EnabledThe current IPv6 enabled or disabled state of this AMM.
NOTE: If IPv6 address(es) have been configured for one or more
interfaces/protocols/services on this AMM, when you update
the firmware to a level which does not support IPv6, all IPv6
connectivity will be lost, and services/interfaces for which an IPv6
address was configured may not function properly. You will be required
to reconfigure these services/interfaces.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.4.2 |
extEthernetInterfaceIPv6Config OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5 |
extEthernetInterfaceIPv6LocalAddress OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.1 |
extEthernetInterfaceIPv6LinkLocalAddressThe IPv6 link local IP address for the ethernet interface.
NOTE: If extEthernetInterfaceIPv6Enabled is currently disabled, this
object has the value '0:0:0:0:0:0:0:0'.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.1.1 |
extEthernetInterfaceIPv6StaticIPConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.2 |
extEthernetInterfaceIPv6StaticIPConfigEnabledThe IPv6 static IP address enabled or disabled state for the ethernet interface.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.2.1 |
extEthernetInterfaceIPv6StaticIPAddressThe IPv6 static IP address for the ethernet interface.
NOTE: If extEthernetInterfaceIPv6Enabled is currently disabled, this
object has the value '0:0:0:0:0:0:0:0'.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.2.2 |
extEthernetInterfaceIPv6StaticIPAddressPrefixLenThe IPv6 static IP address prefix length for the ethernet interface.
NOTE: If extEthernetInterfaceIPv6Enabled is currently disabled, this
object has the value 0.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.2.3 |
extEthernetInterfaceIPv6StaticIPDefaultRouteThe IPv6 static IP address default route for the ethernet interface.
NOTE: If extEthernetInterfaceIPv6Enabled is currently disabled, this
object has the value '0:0:0:0:0:0:0:0'.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.2.4 |
extEthernetInterfaceIPv6AutoIPConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3 |
extEthernetInterfaceIPv6AutoIPConfigEnabledThe IPv6 automatic IP configuration enabled or disabled state for the ethernet interface.
NOTE: extEthernetInterfaceIPv6AutoIPConfigEnabled is the logical OR of extEthernetInterfaceDHCPv6Enabled
and extEthernetInterfaceIPv6StatelessAutoConfigEnabled settings.
NOTE: Enabling/Disabling extEthernetInterfaceIPv6AutoIPConfigEnabled will cause both
extEthernetInterfaceDHCPv6Enabled and extEthernetInterfaceIPv6StatelessAutoConfigEnabled to be enabled/disabled.
NOTE: extEthernetInterfaceIPv6StaticIPConfigEnabled and extEthernetInterfaceIPv6AutoIPConfigEnabled
cannot be disabled at the same time.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.1 |
extEthernetInterfaceDHCPv6Config OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2 |
extEthernetInterfaceDHCPv6EnabledThe DHCPv6 enabled or disabled state for the ethernet interface.
NOTE: If extEthernetInterfaceIPv6StatelessAutoConfigEnabled is currently disabled, Disabling
extEthernetInterfaceDHCPv6Enabled will cause extEthernetInterfaceIPv6AutoIPConfigEnabled to be disabled.
NOTE: If extEthernetInterfaceIPv6StaticIPConfigEnabled and
extEthernetInterfaceIPv6StatelessAutoConfigEnabled are currently disabled, Disabling
extEthernetInterfaceDHCPv6Enabled will not be allowed.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2.1 |
extEthernetInterfaceDHCPv6IPAddressThe IPv6 address for the ethernet interface, assigned by DHCPv6 server.
NOTE: If extEthernetInterfaceIPv6Enabled or extEthernetInterfaceDHCPv6Enabled
is disabled or if DHCPv6 server is not available, this object has the value
'0:0:0:0:0:0:0:0'.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2.2 |
extEthernetInterfaceDHCPv6DomainNameThe 64 byte Domain Name for the ethernet interface,
assigned by the DHCPv6 server.
NOTE: If extEthernetInterfaceIPv6Enabled or extEthernetInterfaceDHCPv6Enabled
is disabled or if DHCPv6 server is not available, this object has the
value '(Not available)'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2.4 |
extEthernetInterfaceDHCPv6PrimaryDNSServerThe primary DNS server, assigned by the DHCPv6 server.
NOTE: If extEthernetInterfaceIPv6Enabled or extEthernetInterfaceDHCPv6Enabled
is disabled or if DHCPv6 server is not available, this object has the
value '0:0:0:0:0:0:0:0'.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2.5 |
extEthernetInterfaceDHCPv6SecondaryDNSServerThe secondary DNS server, assigned by the DHCPv6 server.
NOTE: If extEthernetInterfaceIPv6Enabled or extEthernetInterfaceDHCPv6Enabled
is disabled or if DHCPv6 server is not available, this object has the
value '0:0:0:0:0:0:0:0'.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2.6 |
extEthernetInterfaceDHCPv6TertiaryDNSServerThe tertiary DNS server, assigned by the DHCPv6 server.
NOTE: If extEthernetInterfaceIPv6Enabled or extEthernetInterfaceDHCPv6Enabled
is disabled or if DHCPv6 server is not available, this object has the
value '0:0:0:0:0:0:0:0'.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2.7 |
extEthernetInterfaceDHCPv6ServerThe DHCPv6 server IPv6 address used to acquire the DHCP settings.
NOTE: If extEthernetInterfaceIPv6Enabled or extEthernetInterfaceDHCPv6Enabled
is disabled or if DHCPv6 server is not available, this object has the
value '0:0:0:0:0:0:0:0'.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.2.8 |
extEthernetInterfaceIPv6StatelessAutoConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.3 |
extEthernetInterfaceIPv6StatelessAutoConfigEnabledThe IPv6 stateless auto-configuration enabled or disabled state for the ethernet interface.
NOTE: If extEthernetfInterfaceDHCPv6Enabled is currently disabled, Disabling
extEthernetInterfaceIPv6StatelessAutoConfigEnabled will cause extEthernetInterfaceIPv6AutoIPConfigEnabled
to be disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.3.1 |
extEthernetInterfaceStatelessAutoConfigAddressesTableTable of stateless Auto-Config addresses entries SEQUENCE OF ExtEthernetInterfaceStatelessAutoConfigAddressesEntry .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.3.2 |
extEthernetInterfaceStatelessAutoConfigAddressesEntryStateless Auto-Config address entries ExtEthernetInterfaceStatelessAutoConfigAddressesEntry .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.3.2.1 |
extEthernetInterfaceStatelessAutoConfigAddressesIndexIndex for stateless Auto-Config addresses.
NOTE: If extEthernetInterfaceIPv6StatelessAutoConfigEnabled or
extEthernetInterfaceIPv6Enabled is currently disabled, this
object will show nothing.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.3.2.1.1 |
extEthernetInterfaceStatelessAutoConfigAddressesThe stateless Auto-Configuration IPv6 address.
NOTE: If extEthernetInterfaceIPv6StatelessAutoConfigEnabled or
extEthernetInterfaceIPv6Enabled is currently disabled, this
object will show nothing.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.3.2.1.2 |
extEthernetInterfaceStatelessAutoConfigAddressesPrefixLenThe stateless Auto-Configration address prefix length.
NOTE: If extEthernetInterfaceIPv6StatelessAutoConfigEnabled or
extEthernetInterfaceIPv6Enabled is currently disabled, this
object will show nothing.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.4.5.3.3.2.1.3 |
standbyExtEthernetInterfaceIPv6 OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.5 |
standbyEthernetInterfaceIPv6LocalAddress OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.5.1 |
standbyEthernetInterfaceIPv6LinkLocalAddressThe IPv6 link local IP address for the standby AMM.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.5.1.1 |
standbyEthernetInterfaceIPv6StaticIPConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.5.2 |
standbyEthernetInterfaceIPv6StaticIPConfigEnabledThe IPv6 static IP address state for the AMM.
NOTE: This value may be altered through the
extEthernetInterfaceIPv6StaticIPConfigEnabled object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.5.2.1 |
standbyEthernetInterfaceIPv6StaticIPAddressThe IPv6 static IP address for the standby AMM
NOTE: If extEthernetInterfaceIPv6Enabled is currently disabled, this
object has the value '0:0:0:0:0:0:0:0'.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.5.2.2 |
standbyEthernetInterfaceIPv6StaticIPAddressPrefixLenThe IPv6 static IP address prefix length for the standyby AMM.
NOTE: This value may be altered through the
extEthernetInterfaceIPv6StaticIPAddressPrefixLen object.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.5.2.3 |
standbyEthernetInterfaceIPv6StaticIPDefaultRouteThe IPv6 static IP address default route for the standby AMM.
NOTE: This value may be altered through the
extEthernetInterfaceIPv6StaticIPDefaultRoute object.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.5.2.4 |
standbyEthernetInterfaceDHCPv6Config OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.1.5.3 |
standbyEthernetInterfaceDHCPv6EnabledThe DHCPv6 enabled or disabled state for the standby AMM.
NOTE: This field may be altered through the
extEthernetInterfaceDHCPv6Enabled object.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.5.3.1 |
standbyEthernetInterfaceDHCPv6IPAddressThe IPv6 address for the standby AMM assigned by DHCPv6 server.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.5.3.2 |
standbyEthernetInterfaceDHCPv6DomainNameThe 64 byte Domain Name for the standby AMM
assigned by the DHCPv6 server.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.5.3.4 |
standbyEthernetInterfaceStatelessAutoConfigAddressesTableTable of stateless Auto-Config addresses entries.
NOTE: If extEthernetInterfaceIPv6StatelessAutoConfigEnabled or
extEthernetInterfaceIPv6Enabled is currently disabled, this
table will show nothing. SEQUENCE OF StandbyEthernetInterfaceStatelessAutoConfigAddressesEntry .1.3.6.1.4.1.2.3.51.2.4.9.1.5.4 |
standbyEthernetInterfaceStatelessAutoConfigAddressesEntryStateless Auto-Config address entries StandbyEthernetInterfaceStatelessAutoConfigAddressesEntry .1.3.6.1.4.1.2.3.51.2.4.9.1.5.4.1 |
standbyEthernetInterfaceStatelessAutoConfigAddressesIndexIndex for stateless Auto-Config addresses.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.5.4.1.1 |
standbyEthernetInterfaceStatelessAutoConfigAddressesThe stateless Auto-Configuration IPv6 address.ro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.1.5.4.1.2 |
standbyEthernetInterfaceStatelessAutoConfigAddressesPrefixLenThe stateless Auto-Configration address prefix length.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.1.5.4.1.3 |
ddnsStatusDynamic DNS provides the capability for a networked device
to notify a domain name server to change, in real time, the
active DNS configuration of its configured hostnames, addresses
or other information stored in DNS. With Dynamic DNS, host
computers gain the capability to notify their respective DNS
server of the IP address they have received from a DHCP server
or through self-configuration.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.1.10 |
hostNameContains the DNS host name for this system. This object
provides the exact same function as extEthernetInterfaceHostNamerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.11 |
standbyHostNameContains the DNS host name for the standby. This object
provides the exact same function as standbyExtEthernetInterfaceHostName
and is only applicable to systems with a standby MM.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.12 |
domainNameThe user assigned DNS domain name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.13 |
standbyDomainNameThe user assigned DNS domain name of the standby. This is only
applicable to systems with a standby MM.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.1.14 |
tcpProtocols OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3 |
snmpAgentConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.1 |
snmpSystemContactA NULL terminated 48 byte string that contains the
SNMP agent contact name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.1 |
snmpSystemLocationA NULL terminated 48 byte string that contains the
SNMP agent location name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.2 |
snmpSystemAgentTrapsDisableDisable or enable SNMP traps.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.1.3 |
snmpAgentCommunityConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4 |
snmpCommunityTableTable of SNMP Community entries SEQUENCE OF SnmpCommunityEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1 |
snmpCommunityEntrySNMP community entries SnmpCommunityEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1.1 |
snmpCommunityEntryIndexIndex for SNMP Agent Community entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1.1.1 |
snmpCommunityEntryCommunityNameSNMP Community entry name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1.1.2 |
snmpCommunityEntryCommunityIpAddress1SNMP Community IP address or host name.
Can either be a dotted decimal IP string (e.g. 9.37.44.2)
or if DNS is enabled a host name. This field also allows two
wildard values for read-Traps and write-Read-Traps communities:
0.0.0.0 - allow any IPv4 address
0::0 - allow any IPv6 addressrw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1.1.3 |
snmpCommunityEntryCommunityIpAddress2SNMP Community IP address or host name.
Can either be a dotted decimal IP string (e.g. 9.37.44.2)
or if DNS is enabled a host name. This field also allows two
wildard values for read-Traps and write-Read-Traps communities:
0.0.0.0 - allow any IPv4 address
0::0 - allow any IPv6 addressrw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1.1.4 |
snmpCommunityEntryCommunityIpAddress3SNMP Community IP address or host name.
Can either be a dotted decimal IP string (e.g. 9.37.44.2)
or if DNS is enabled a host name. This field also allows two
wildard values for read-Traps and write-Read-Traps communities:
0.0.0.0 - allow any IPv4 address
0::0 - allow any IPv6 addressrw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1.1.5 |
snmpCommunityEntryCommunityViewTypeAccess Level of the SNMPv1 managers. Note this parameter
is set for each community. Therefore all three managers
in the same community have the same access level.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.1.4.1.1.6 |
snmpv1SystemAgentEnableDisable or enable the SNMPv1 agent.
NOTE: Restart the management module if this MIB object is changed
with respect to the value at system bootup time. For example the
SNMPv1 agent was set to disabled at system bootup time and now
it is enabled. Then restarting the remote supervisor adaptor is
required.
Also note that when attempting to enable this agent,
the following are verified:
(1) Is there a valid system contact
(2) Is there a valid system name
(3) Is there at least one valid community name and for that
community name is there one valid IP address or hostname
(4) Are all defined community names unique
If this verification fails an error response will be returned
and the SNMPv1 agent will be left disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.1.5 |
snmpv3SystemAgentEnableDisable or enable the SNMPv3 agent.
NOTE: Restart the management module if this MIB object is changed
with respect to the value at system bootup time. For example the
SNMPv3 agent was set to disabled at system bootup time and now
it is enabled. Then restarting the remote supervisor adaptor is
required.
Also note that when attempting to enable this agent,
the following are verified:
(1) Is there a valid system contact?
(2) Is there a valid system name?
If this verification fails an error response will be returned
and the SNMPv3 agent will be left disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.1.6 |
snmpAgentUserProfileConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9 |
snmpUserProfileTableTable of SNMPv3 User Profile entries SEQUENCE OF SnmpUserProfileEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1 |
snmpUserProfileEntrySNMP User Profile entries SnmpUserProfileEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1 |
snmpUserProfileEntryIndexIndex for SNMPv3 Agent User Profile entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1.1 |
snmpUserProfileEntryContextNameSNMPv3 User Profile entry - Context name
for users to access MIB objects. Note that context names can be duplicates
and can be shared among users. Empty context names are allowed. The
default context name is the empty string.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1.3 |
snmpUserProfileEntryAuthProtSNMPv3 User Profile entry - Authentication Protocol
supported by the user.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1.4 |
snmpUserProfileEntryPrivProtSNMPv3 User Profile entry - Privacy Protocol
supported by the user. The Privacy Password must be set
and the Authentication Protocol must be md5 or sha
before this field may be set to des or aes.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1.6 |
snmpUserProfileEntryPrivPasswordSNMPv3 User Profile entry - Privacy password
for the user.
NOTE: Value returned for the GET command is
meaningless for this MIB object for security reasons.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1.7 |
snmpUserProfileEntryViewTypeSNMPv3 User Profile entry - Access level (Get, Set, and
Traps) of the user.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1.8 |
snmpUserProfileEntryIpAddressSNMPv3 User Profile entry - IP address or host name.
Can either be a dotted decimal IP string (e.g. 9.37.44.2)
or if DNS is enabled a host name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.1.9.1.1.9 |
dnsConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.2 |
dnsEnabledDisable or enable the DNS agent.
NOTE: To alter any of the configuration settings for the DNS agent,
the following procedure should be used:
(1) This object should be set to 'disabled'
(2) Make the modifications to other settings
(3) This object should be set to 'enabled'
(4) Restart the management module
Also note that when attempting to enable this agent, it is verified
that there is at least one valid DNS server IP address. If this
verification fails, an error response will be returned and the DNS
agent will be left disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.2.1 |
dnsServerIPAddress1Contains the primary DNS server IP address.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.3.2.2 |
dnsServerIPAddress2Contains the secondary DNS server IP address.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.3.2.3 |
dnsServerIPAddress3Contains the tertiary DNS server IP address.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.3.2.4 |
dnsServerIPv6Address1Contains the primary IPv6 DNS server address.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.3.2.12 |
dnsServerIPv6Address2Contains the secondary IPv6 DNS server address.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.3.2.13 |
dnsServerIPv6Address3Contains the tertiary IPv6 DNS server address.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.3.2.14 |
dnsPriorityTells the order host names are resolved. The options are
to either first resolve with an IPv6 DNS server or to first
resolve with an IPv6 DNS server.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.2.20 |
smtpConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.3 |
smtpServerNameOrIPAddressA NULL terminated 64 byte string that contains the
SMTP server host name or IP address (a.b.c.d).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.3.1 |
attachmentsToEmailAlertsIndicates if the service information should be attached to
an email alert.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.3.2 |
smtpEmailDomainA NULL terminated string that contains the
SMTP email domain. If this field is empty, the AMM IP
address is used as the domain. However, some SMTP
servers (e.g. - MS Exchange 2007) do not accept an IP address and
instead require a domain name. This object can be used to set that
email domain name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.3.3 |
tcpApplicationConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.4 |
telnetInactivityTimeoutDefault is 120 seconds. Value of zero is no timeout.
Max value is any positive 4 bytes value. Note that SSH also uses this
timeout value to wait before disconnecting inactive SSH connections.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.4.1 |
commandModeInactivityTimeoutThe amount of time in seconds before the (Secure)TCP Command Mode times out.
Default value of 0 means no timeout. Max value is any positive 4 byte value.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.4.2 |
secureCommandModeEnableSet Secure TCP Command Mode number of connections.
AMM will provide a max of 20 connections for both Secure TCP Command Mode and TCP Command Mode.
A value of 0 means disabled.
If no valid server certificate is in place, Secure TCP Command Mode will not be allowed to set to enable.
NOTE: System Management Software requires this to be enabled for secure communication to the AMM.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.4.3 |
commandModeEnableSet TCP Command Mode number of connections.
AMM will provide a max of 20 connections for both Secure TCP Command Mode and TCP Command Mode.
A value of 0 means disabled.
NOTE: System Management Software requires this to be enabled for non-secure communication to the AMM.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.4.4 |
slpAddrTypeSet SLP address type to 0 (multicast) or 1 (broadcast). Note that when
slpAddrType is set to broadcast value then the multicast address set in
slpMulticastAddr will be ignored.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.5 |
slpMulticastAddrService Locator Protocol Multicast addressrw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.3.4.6 |
slpEnableDisable/Enable Service Location Protocol.
NOTE: Change to Service Location Protocol will take
effect after the next restart of the MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.7 |
telnetEnableDisable/Enable telnet.
NOTE: Change to telnet enable/disable will take effect immediately.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.9 |
sshEnableDisable/Enable SSH.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.10 |
sshVersionWhen SSH is enabled, this object allows the user to
configure whether the SSH server accepts all versions
of client connections or whether it restricts the
connectivity to the more secure version 2 only.
NOTE: Only SSH version 2 is supported now.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.11 |
sslServerEnableDisable/Enable SSL Server.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.15 |
sslClientEnableDisable/Enable SSL Client. If no valid client or server certificate is in place,
SSL client will not be allowed to set to enable.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.16 |
ftpEnableDisable/Enable FTP.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.17 |
tftpEnableDisable/Enable TFTP.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.19 |
smashTelnetEnableDisable/Enable SMASH CLP (System Management Architecture for
Server Hardware Command Line Protocol) over Telnet.
This option is not available on all systems.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.20 |
smashSshEnableDisable/Enable SMASH CLP (System Management Architecture for
Server Hardware Command Line Protocol) over SSH. A valid SSH
server key must be installed before enabling secure SMASH.
This option is not available on all systems.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.21 |
tftpCreateEmptyFileThis MIB object is no longer a requirement for TFTP and has been deprecated.rwdeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.4.22 |
ftpTimeoutThe amount of time before FTP times out. Default is 300 seconds.
Value of zero is no timeout. Max value is any positive 4 byte value.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.4.23 |
rdEnableDisable/Enable Remote Disk.
NOTE: Change to Remote Disk will take effect after the
next restart of the MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.24 |
rdocEnableDisable/Enable Remote Disk on Card.
NOTE: Change to Remote Disk on Card will take effect
after the next restart of the MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.25 |
kvmEnableDisable/Enable KVM.
NOTE: Change to KVM will take effect after the next
restart of the MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.26 |
mmSshServerConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27 |
mmSshServerHostKeyTableA table that contains per public/private host key
pair information. SEQUENCE OF MmSshServerHostKeyEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.1 |
mmSshServerHostKeyEntryA list of information about a particular public/private
host key pair. MmSshServerHostKeyEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.1.1 |
mmSshServerHostKeyIndexThe index of the public/private host key pair.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.1.1.1 |
mmSshServerHostKeyTypeThe type of the public/private host key pair.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.1.1.2 |
mmSshServerHostKeySizeThe size of the public/private host key pair.
NOTE: The AMM supports only the bits2048 value.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.1.1.3 |
mmSshServerHostKeyFingerprintThe RSA fingerprint of the public part of the host key
pair. This value can be used with the SSH client to
verify, on the initial connection, that the Secure Shell
server responding to the request is the server running
on the AMM.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.1.1.4 |
mmSshServerHostKeyGenerateInitiate the new Host Keys generation process for the
AMM SSH Server.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.2 |
mmSshServerHostKeyGenerateProgressIndicate the progress of the key generation process.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.4.27.3 |
rpEnableDisable/Enable Remote Presence.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.4.28 |
tcpPortAssignmentCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.5 |
tcpPortsRestoreDefaultReset all ports to default value.
http: 80
https: 443
telnet: 23
ssh: 22
SNMP agent: 161
SNMP trap: 162
TCP Command Mode: 6090
Secure TCP Command Mode: 6091
Remote Disk: 1044
Remote Disk-on-Card: 1045
Remote KVM: 3900
FTP: 21
FTP Data: 20
TFTP: 69
SMASH telnet: 50023
SMASH ssh: 50022
SLP: 427
Storage Description Service: 1046
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.5.1 |
httpPortAssignmentHTTP port number. Default value is 80. Once changed, the URL's have to
include :port at the end.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.2 |
httpsPortAssignmentSSL port number. Default value is 443. Once changed, the URL's have to
include :port at the end.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.3 |
telnetPortAssignmentTelnet port number. Default value is 23. Port change will take effect immediately.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.4 |
sshPortAssignmentSSH port number. Default value is 22.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.5 |
snmpAgentPortAssignmentSNMP Agent port number. Default value is 161.
Changes take effect after several seconds.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.6 |
snmpTrapsPortAssignmentSNMP Traps port number. Default value is 162.
Changes take effect after several seconds.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.7 |
commandModePortAssignmentTCP Command Mode port number. Default value is 6090. Change will take effect immediately.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.8 |
secureCommandModePortAssignmentSecure TCP Command Mode port number. Default value is 6091. Change will take effect immediately.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.9 |
rdPortAssignmentRemote Disk port number. Default value is 1044. MM has to be reset for change
to take effect.
NOTE: This mib object is deprecated and has been replaced by the rpPortAssignment object.
Attempts to set the port value for this SNMP object are no longer supported and any
read of the value associated with this object will return the rpPortAssignment
(Remote Presence) port information.rwdeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.10 |
rdocPortAssignmentRemote Disk-on-Card port number. Default value is 1045. MM has to be reset for
change to take effect.
NOTE: This mib object is deprecated and has been replaced by the rpPortAssignment object.
Attempts to set the port value for this SNMP object are no longer supported and any
read of the value associated with this object will return the rpPortAssignment
(Remote Presence) port information.rwdeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.11 |
kvmPortAssignmentRemote KVM port number. Default value is 3900. MM has to be reset for
change to take effect.
NOTE: This mib object is deprecated and has been replaced by the rpPortAssignment object.
Attempts to set the port value for this SNMP object are no longer supported and any
read of the value associated with this object will return the rpPortAssignment
(Remote Presence) port information.rwdeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.12 |
ftpPortAssignmentFTP port number. Default value is 21. Port change will take effect immediately.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.13 |
ftpDataPortAssignmentFTP Data port number. Default value is 20. Port change will take effect immediately.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.14 |
tftpPortAssignmentTFTP port number. Default value is 69.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.15 |
smashTelnetPortAssignmentThe port number for SMASH CLP (System Management Architecture for Server
Hardware Command Line Protocol) over telnet. Default value is 50023.
Change will take effect immediately.
This option is not available on all systems.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.17 |
smashSshPortAssignmentThe port number for SMASH CLP (System Management Architecture for Server
Hardware Command Line Protocol) over SSH. Default value is 50022.
This option is not available on all systems.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.18 |
slpPortAssignmentService Location Protocol port number. Default value is 427.
NOTE: This value is normally required to be 427 to interoperate properly
with other SLP enabled applications.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.19 |
sdsPortAssignmentStorage description service port number. Default value is 1046. MM has to be reset for
change to take effect.
NOTE: This mib object is deprecated and has been replaced by the rpPortAssignment object.
Attempts to set the port value for this SNMP object are no longer supported and any
read of the value associated with this object will return the rpPortAssignment
(Remote Presence) port information.rwdeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.20 |
rpPortAssignmentRemote Presence port. Default value is 3900. This port cannot be disabled since it is
the single service entry point for all the services provided by AMM RPServ to clients.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.5.21 |
ldapClientCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.6 |
ldapServer1NameOrIPAddressA NULL terminated 64 byte string that contains the
LDAP server host name or IP address (a.b.c.d).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.1 |
ldapServer1PortNumberLDAP server port number.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.6.2 |
ldapServer2NameOrIPAddressA NULL terminated 64 byte string that contains the
LDAP server host name or IP address (a.b.c.d).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.3 |
ldapServer2PortNumberLDAP server port number.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.6.4 |
ldapServer3NameOrIPAddressA NULL terminated 64 byte string that contains the
LDAP server host name or IP address (a.b.c.d).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.5 |
ldapServer3PortNumberLDAP server port number.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.6.6 |
ldapRootDNDistinguished Name for root entry of directory tree.
An example might look like dn=foobar,dn=com.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.7 |
ldapUserSearchBaseDNAs part of the user authentication process, it is necessary to search
the LDAP server for one or more attributes associated with a particular
user. Any search request must specify the base DN for the actual search.
This field specifies the base DN which should be used to search the User
directory. An example might look like cn=users,dn=foobar,dn=com. If this
field is left blank, the Root DN will be used as the search base instead.
As mentioned, user searches are part of the authentication process. They
are carried out to retrieve information about the user such as login
permissions, callback number, and group memberships. For Version 2.0 LDAP
clients, it is strongly encouraged that this parameter be configured,
otherwise a search using the root DN may not succeed (as seen on Active
Directory servers).
NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported.rwdeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.8 |
ldapGroupFilterThis filter is used for group authentication. It specifies what group or
groups that this MM belongs to. If left blank, group authentication is
disabled. Otherwise, group authentication will be performed against the
filter. The filter can be a specific group name (e.g. RSAWest), a wildcard (*)
which matches everything, or a wildcard with a prefix (e.g. RSA*). The default
filter is RSA*.
After user authentication, group authentication will take place, whereby an
attempt will be made to match the group or groups (that the user belongs to)
to the group filter defined here. If there is no match, the user will not pass
authentication and will be blocked. If there is a match, the login permissions
for the user will be retrieved from the matched group(s), unless the user
already has login permissions assigned directly from the user record retrieved
from the LDAP server.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.9 |
ldapBindingMethodOn initial binds to the LDAP server during user authentication, there are
three options:
Anonymous authentication: Bind attempt is made without a client DN or password.
If the bind is successful, a search will be requested in order to find an entry
on the LDAP server for the user attempting to login. If an entry is found, a
second attempt to bind will be attempted, this time with the user's DN and
password. If this succeeds, the user is deemed to have passed the user
authentication phase. Group authentication is then attempted if it is enabled.
Client authentication: Bind attempt is made with client DN and password
specified by this configuration parameter. If the bind is successful, we
proceed as above.
User Principal Name (UPN): Bind attempt is made directly with the credentials
used during the login process. If this succeeds, the user is deemed to have
passed the user authentication phase. Note that for Active Directory servers,
the userid can have the form someuser@somedomain or simply someuser.
Strict UPN: This is the same as UPN above, except that the userid must have
the form someuser@somedomain. The string entered by the user will be parsed
for the @ symbol.
NOTE: strictUserPrincipalName(3) option is available on MM only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.6.10 |
ldapClientAuthenticationDNThe initial bind to the LDAP server during user authentication can be
performed with anonymous authentication, client based authentication, or UPN.
The client based option requires a client DN and password as parameters to
the bind request. These parameters are configured here. Note that the password
can be left blank.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.11 |
ldapClientAuthenticationPasswordThe client authentication passwordrw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.12 |
ldapUIDsearchAttributeWhen the binding method selected is Anonymous authentication or Client
authentication, the initial bind to the LDAP server is followed by a search
request aimed at retrieving specific information about the user, including the
user's DN, login permissions, and group ownerships. In order to retrieve this
information, the search request must specify the attribute name used to
represent userids on that server. Specifically, this name is used as a search
filter against the login id entered by the user. This attribute name is
configured here. If this field is left blank, a default of uid is used during
user authentication.
For example, on Active Directory servers, the attribute name used for userids
is often sAMAccoutName.
When the binding method selected is UPN or Strict UPN, this field defaults
automatically to userPrincipalName during user authentication if the userid
entered has the form userid@somedomain.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.13 |
ldapGroupSearchAttributeWhen the MM Group Filter name is configured, it is necessary to retrieve
from the LDAP server the list of groups that a particular user belongs to.
This is required to do group authentication. In order to retrieve this list,
the search filter sent to the server must specify the attribute name associated
with groups. This field specifies this attribute name.
If this field is left blank, the attribute name in the filter will default
to memberOf.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.14 |
ldapLoginPermissionAttributeWhen a user successfully authenticates via a LDAP server, it is necessary
to retrieve the login permissions for this user. In order to retrieve these
permissions, the search filter sent to the server must specify the attribute
name associated with login permissions. This field specifies this attribute
name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.15 |
ldapUseDNSOrPreConfiguredServersThe MM contains a Version 2.0 LDAP Client that may be configured to provide
user authentication through one or more LDAP servers. The LDAP server(s) to be
used for authentication can be discovered dynamically or manually pre-configured.
If the usePreConfiguredLDAPServers option is selected, up to 4 LDAP servers can
be configured. Simply enter the server's IP address or hostname (assuming DNS
is enabled). The port number for each server is optional. If left blank,
the default value of 389 is used for non-secured LDAP connections. For secured
connections, the default is 636. At least one server must be configured.
If the useDNSToFindLDAPServers is selected, the domain name need to be provided.
For LDAP Authentication Only mode, additional information such as the forest name
also need to be provided.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.6.16 |
ldapDomainSourceThe DNS SRV request sent to the DNS server must specify a domain name.
The LDAP client will determine where to get this domain name based on one
of the following three options:
- extractSearchDomainFromLoginID: With this option, the LDAP client will
use the domain name in the login id. For example, if the login id is
joesmith@mycompany.com, the domain name equals mycompany.com. If the domain
name cannot be extracted, the DNS SRV will fail, causing the user
authentication to fail automatically.
- useOnlyConfiguredSearchDomainBelow: With this option, the LDAP client
will use the domain name configured in the Search Domain parameter.
- tryLoginFirstThenConfiguredValue: With this option, the LDAP client will
first attempt to extract the domain name from the login id. If this succeeds,
this domain name will be used in the DNS SRV request. If there is no domain
name present in the login id, the LDAP client will instead use the configured
Search Domain parameter as the domain name in the DNS SRV request.
If nothing is configured, user authentication will fail immediately.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.6.17 |
ldapSearchDomainThis parameter may be used as the domain name in the DNS SRV request,
depending on how the Domain Source parameter is configured.rwdeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.18 |
ldapServiceNameThe DNS SRV request sent to the DNS server must also specify a service name.
The configured value will be used for this purpose. If left blank, the default
value used is 'ldap'. Note that the DNS SRV request must also specify a protocol
name. This defaults to 'tcp' and is not configurable.rwdeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.19 |
ldapRBSModelCfgThere are two mechanisms to authenticate and authorize users on the AMM when
using an LDAP-enabled server. The first mechanism (oldPermissionString), also
known as version 1, uses bitstrings to associate permissions to users and groups.
Version1 supports Active Directory, Novell eDirectory, and OPenLDAP based
servers. The second mechanism (newRBSModel), also known as version 2,
uses a new Role-Based-Security (RBS) model. This mechanism is only available
for Active Directory servers, and requires the use of a snap-in that runs on any
windows platform. This snap-in tool allows you to configure roles on an Active
Directory server of your choice, and to associate users/groups and AMMs to those
roles. A role identifies the permissions given to users and groups associated with
that role, and also identifies the targets (e.g. AMM) to which this role is attached.
The use of bitstrings in version 2 disappears, making the configuration much more
manageable and user-friendly. Note that if you are not using Active Directory, then
you should not enable version 2. Also note that before enabling version 2, you should
already have your roles configured on your Active Directory server. The old version 1
bitstring model cannot be automatically converted to the new version 2 model. This is
why you must configure your users and groups before enabling version 2. Once
enabled, the change takes effect immediately. The default value for this field is
oldPermissionString.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.6.20 |
ldapTargetNameWhen administrator chooses Enhanced Role Based Security authentication model,
he can associate one AMM with one managed target object in Snap-in (one tool
to configure LDAP users permission) via one target name. The AMM target name can
be looked as alias of AMM, administrator can change it according to his
configuration requirements. This is a string of up to 63 characters (plus the
null character)rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.21 |
ldapAuthCfgIf ldapAuthCfg is set to 0, LDAP server is used to authenticate and authorize
users. If it is set to 1, LDAP server is only used to authenticate users.
Note:LDAP Authentication Only mode is currently supported only in an Active
Directory environment.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.6.22 |
ldapForestNameLDAP Forest Name.
Note: LDAP Forest Name is only for Active Directory environment.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.23 |
ldapDomainNameLDAP Domain Name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.24 |
ldapServer4NameOrIPAddressA NULL terminated 64 byte string that contains the
LDAP server host name or IP address (a.b.c.d).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.6.25 |
ldapServer4PortNumberLDAP server port number.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.6.26 |
uplinkCheckConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.7 |
uplinkCheckEnabledDisable or enable network uplink checking for physical detection.
NOTE: This MIB object is only applicable to systems with a standby MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.7.1 |
uplinkCheckDelayDelay, in minutes (1-2880), between discovery of a failed network uplink and
the subsequent MM failover for physical detection.
NOTE: This MIB object is only applicable to systems with a standby MM.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.7.2 |
logicalUplinkDestinationDestination IP for MM to check its logical link.
Specify a non-zero IP Address in order to enable logical uplink checking.
NOTE: This MIB object is only applicable to systems with a standby MM.rw IpAddress .1.3.6.1.4.1.2.3.51.2.4.9.3.7.3 |
logicalUplinkCheckEnabledDisable or enable network uplink checking for logical detection.
logicalUplinkDestination must be set to a non-zero IP Address before enable
logical uplink checking.
NOTE: This MIB object is only applicable to systems with a standby MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.7.4 |
logicalUplinkCheckDelayDelay, in minutes(1-2880), between discovery of a failed network uplink and
the subsequent MM failover for logical detection.
NOTE: This MIB object is only applicable to systems with a standby MM.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.7.5 |
physicalUplinkCheckDelayInSecsDelay, in seconds(10-172800), between discovery of a failed network uplink and
the subsequent MM failover for physical detection.
NOTE: This MIB object is only applicable to systems with a standby MM.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.7.6 |
logicalUplinkCheckDelayInSecsDelay, in seconds(60-172800), between discovery of a failed network uplink and
the subsequent MM failover for logical detection.
NOTE: This MIB object is only applicable to systems with a standby MM.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.7.7 |
logicalUplinkIPv6DestinationDestination IP for MM to check its logical link using IPv6.
Specify a non-zero IP Address in order to enable logical uplink checking.
NOTE: This MIB object is only applicable to systems with a standby MM.
NOTE: This MIB object is only applicable if IPv6 is enabled on the MM.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.9.3.7.8 |
logicalUplinkFailoverPolicyDetermines when to failover if both an IPv4 and IPv6 destination
have been configured.
If set to 'either' the system will failover if either of the
destination's link check fails. If set to 'both' then the IPv4
and IPv6 link checks must fail before a failover will happen.
NOTE: This MIB object is only applicable to systems with a standby MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.7.9 |
ntpConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.8 |
ntpEnableDisable/Enable the NTP client. The client will update
the AMM system clock at the frequency specified.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.8.1 |
ntpIpAddressHostnameNTP server's IP address or hostname if DNS is enabled
and configured.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.8.2 |
ntpUpdateFrequencyThe frequency in minutes that the NTP service runs.
The value range is 0 to 45000. If the NTP update frequency
is set to 0, the AMM clock can only be synchronized with the
NTP server manually.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.8.3 |
ntpLastUpdateThe date and time that the NTP server last updated
the system clock.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.8.4 |
ntpUpdateClockUpdate the AMM system clock with the specified NTP server.
A valid NTP server must be configured first.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.8.5 |
ntpAuthEntryThe NTP v3 authentication entry to be used for time sync
with a secure NTP server. The format of an authentication
entry is <key index> <key type> <key>. <key index> must
be an integer between 1 and 65535. <key type> must be
M. <key> is the actual value of the authentication
key as configured on the NTP server.
The GET command returns back data in the format:
<key index> <key type>
It does not return the actual key.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.8.6 |
ntpAuthEnableEnables/Disables NTP v3 authenticationrw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.8.7 |
syslogConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.9 |
syslogSevFilterLevelsyslogSevFilterLevel error/warning/information .rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.9.1 |
syslogCollectorConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.9.3.9.2 |
syslogCollectorTableTable of Syslog Collector entries SEQUENCE OF SyslogCollectorEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.9.2.1 |
syslogCollectorEntrySyslog Collector entries SyslogCollectorEntry .1.3.6.1.4.1.2.3.51.2.4.9.3.9.2.1.1 |
syslogCollectorIndexIndex for Syslog Collector entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.9.2.1.1.1 |
syslogCollectorHostnameOrIpAddressSyslog Collector IP address or host name.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.9.3.9.2.1.1.2 |
syslogCollectorPortSyslog Collector port number.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.9.3.9.2.1.1.3 |
syslogCollectorEnableSyslog Collector enable/disable.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.9.2.1.1.4 |
syslogTestPacketGenerate a test syslog packet. This will send a test syslog to all configured
and enabled syslog collectors to assist in validating the configuration.
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.9.3.9.3 |
solConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.10 |
solGlobalConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.10.1 |
solEnableDisable/Enable SOL dynamically.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.10.1.1 |
solVlanIdThis is the virtual LAN ID for the internal management network between the MM and
the Blade System Management Processors (BSMPs). The range of valid VLAN ID's
is 3 to 4095.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.10.1.2 |
solAccumulateTimeoutThis value specifies how much time in millisecond SOL to buffer data before
sending the next SOL packet since the last SOL packet was transmitted.
Valid value from 5 ms to 1275 ms. The value is in 5 ms increment. Value
is not in 5 ms increment will be truncated to a nearest 5s. Default value
is 5 ms.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.10.1.3 |
solCharSendThresholdThis value specifies how many characters SOL to buffer before
sending the next SOL packet since the last SOL packet was transmitted.
Valid value is from 1 to 255rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.10.1.4 |
solRetryRetry count. Valid value from 0-7. 0 means no retries after packet is transmitted.
Packet will be dropped if no ACK/NACK received by the time retries expired.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.10.1.5 |
solRetryIntervalRetry Interval in 10 ms increment. Sets the time that the SOL will
wait before the first retry and the time between retries when sending SOL
packets to the remote blade. Value range is from 0 to 2550 ms in 10 ms
increment. 0 means retries will be sent back-to-back.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.10.1.6 |
solExitToCliKeySeqThis is the keystroke sequence used to escape out of SOL session and back to CLI
console. This sequence must have at least one character. The caret symbol (^)
has a special meaning in this sequence. It denotes 'Ctrl' for keystrokes that
map to Ctrl sequences (for example, ^[ for the escape key and ^M for carriage
return). All occurrences of ^ will be interpreted as part of a Ctrl sequence.
Refer to an ASCII-to-key conversion table for a complete list of Ctrl sequences.
The default value for this field is '^[(' i.e. ESC followed by (.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.10.1.7 |
solResetBladeKeySeqThis is the keystroke sequence used to reset the blade while in SOL session
console. This sequence must have at least one character. The caret symbol (^)
has a special meaning in this sequence. It denotes 'Ctrl' for keystrokes that
map to Ctrl sequences (for example, ^[ for the escape key and ^M for carriage
return). All occurrences of ^ will be interpreted as part of a Ctrl sequence.
Refer to an ASCII-to-key conversion table for a complete list of Ctrl sequences.
The default value for this field is '^[R^[r^[R' i.e. ESC R ESC r ESC R.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.10.1.8 |
solBladeConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.10.2 |
solBladeTableSOL Blade configuration table. SEQUENCE OF SolBladeEntry .1.3.6.1.4.1.2.3.51.2.4.10.2.1 |
solBladeEntrySOL Blade table entry SolBladeEntry .1.3.6.1.4.1.2.3.51.2.4.10.2.1.1 |
solBladeIndexSOL Blade table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.10.2.1.1.1 |
solBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.10.2.1.1.2 |
solBladeEnableDisable or enable a SOL on a blade.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.10.2.1.1.3 |
solBladeIpAddrIP address of the blade derived from the IP address range for the blade
system management processors on the blades.
NOTE: The IPv6 address for a blade can be view with the
bladeIPv6AddressTable.ro IpAddress .1.3.6.1.4.1.2.3.51.2.4.10.2.1.1.4 |
solBladeSessionStatusStatus of a blade SOL session:
solSessionNotReady: no SOL session connected to the blade.
solSessionReady: there is an SOL session to the blade.
solSessionActive: there is an SOL session to the blade and there is a
client using the SOL session.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.10.2.1.1.5 |
solBladeCapabilityDisplay whether or not the blade support SOL feature.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.10.2.1.1.6 |
chassisInternalNetwork OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.11 |
cinsSupportedNumber of Chassis Internal Network (CIN) definitions supported.
Currently a maximum of 14 CIN definitions can be supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.1 |
cinGlobalEnableDisable/Enable Chassis Internal Network (CIN) function dynamically.
Enabled:
AMM reads the CIN entries. For each enabled entry,
- If the CIN VLAN ID is new and does not have a CIN interface
created yet then create a new CIN interface based on that
CIN VLAN ID. Use the CIN IP address from the entry to create
a host route.
- If the CIN IP address is 0.0.0.0 then start ARP monitoring.
Disabled:
- Stop all ARP monitoring.
- Delete all host routes.
- Delete all CIN interfaces.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.11.2 |
cinTableChassis Internal Network (CIN) configuration table. SEQUENCE OF CinEntry .1.3.6.1.4.1.2.3.51.2.4.11.3 |
cinEntryChassis Internal Network (CIN) table entry. CinEntry .1.3.6.1.4.1.2.3.51.2.4.11.3.1 |
cinIndexChassis Internal Network (CIN) table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.3.1.1 |
cinDefExistsIndicates if a Chassis Internal Network (CIN) definition exists for
this index or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.4.11.3.1.2 |
cinDeleteDelete Chassis Internal Network (CIN) definition.
Works like CIN entry disabled. However, the entry is also deleted.
NOTE: Value returned for the GET command is meaningless for this
MIB object. Deleting a non-defined entry does nothing.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.11.3.1.3 |
cinEnableDisable or enable a Chassis Internal Network (CIN) definition.
Enabled:
AMM reads the entry and creates a new CIN interface if the CIN VLAN
ID is new and does not have a CIN interface created yet, adds host
route, and monitors communication path. Start ARP monitoring if
IP is 0.0.0.0.
Disabled:
Delete host route. If this is the last IP address that uses the CIN
interface,
- Stop ARP monitoring if IP is 0.0.0.0.
- Delete the CIN interface if there is no other entry depends on it.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.11.3.1.4 |
cinIdThis is the Chassis Internal Network (CIN) Virtual LAN (VLAN) ID for
the internal management network between the Management Module,
I/O Module, and the blade OS. The range of valid CIN VLAN IDs is
3 to 4094 (inclusive). This value cannot be the same as the
Serial Over LAN (SOL) or Concurrent KVM (cKVM) VLAN ID.
NOTE: If creating a new CIN definition, you must define cinId
before you define cinIpAddress.
NOTE: Before changing this value on an existing CIN definition,
you must first disable the definition.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.3.1.5 |
cinIpAddressChassis Internal Network (CIN) IP address.
Restrictions:
- CIN entries cannot have matching IP addresses, with the exception of 0.0.0.0.
- Multiple IP addresses of 0.0.0.0 with different VLAN IDs are allowed.
- The IP address cannot be multi-cast.
- The IP address cannot match the AMM IP address.
- If the CIN IP address is 0.0.0.0, the blade IP address for CIN which is configured
in the blade's OS can not be in the same subnet as that of AMM.
NOTE: If creating a new CIN definition, you must define cinId
before you define cinIpAddress.
NOTE: Before changing this value on an existing CIN definition,
you must first disable the definition.
NOTE: When ipv6 is enable on one interface, this column will
display all zero IPv4 addressrw IpAddress .1.3.6.1.4.1.2.3.51.2.4.11.3.1.6 |
cinIpv6AddressChassis Internal Network (CIN) IPv6 address
NOTE: When ipv4 is enable on one interface,this column will display
all zero IPv6 address.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.4.11.3.1.7 |
cinStatus OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.11.4 |
cinStatusTableTable of Chassis Internal Network (CIN) status entry information. SEQUENCE OF CinStatusEntry .1.3.6.1.4.1.2.3.51.2.4.11.4.1 |
cinStatusEntryChassis Internal Network (CIN) status table entry. CinStatusEntry .1.3.6.1.4.1.2.3.51.2.4.11.4.1.1 |
cinStatusIndexThe Chassis Internal Network (CIN) status log index number.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.4.1.1.1 |
cinStatusStringStatus of a Chassis Internal Network (CIN) connection. For example:
Index:1 VLANID:4094 IPADDR:192.168.70.100 MAC:01:0A:0B:00:01:01 Type:Learned Status:Operational
Index is the status entry number in the status table. Followed by the
VLAN ID, IP address, and MAC address that the Management Module is
communicating with on the CIN connection.
Type is either 'Configured' or 'Learned'. Learned implies that the
Management Module dynamically discovered the IP address.
Configured means that the address was explicitly configured in
the Management Module.
Status can be 'Operational', 'Not Operational', or 'Disabled'.
'Operational' means the Management Module can ping the CIN IP address.
'Not Operational' means that the Management Module cannot ping the CIN
IP address. Verify that the blade and I/O Module are configured properly
and that their configurations are compatible with the Management Module.
The blade OS also needs to have an IP host route defined
(e.g. route add -host 192.168.70.100 eth0.4094).
I/O Modules need to have a VLAN defined containing the blade's and the
AMM's port. Blade and I/O Modules need to be powered up and operational.
'Disabled' means that the CIN configuration has been disabled by a
Management Module administrator.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.4.11.4.1.1.2 |
cinPortConfigTableChassis Internal Network (CIN) configuration table for viewing
and configuring the protocol port information for a particular CIN entry. SEQUENCE OF CinPortConfigEntry .1.3.6.1.4.1.2.3.51.2.4.11.5 |
cinPortConfigEntryChassis Internal Network (CIN) entry for viewing and configuring
the protocol port information for a particular CIN entry. CinPortConfigEntry .1.3.6.1.4.1.2.3.51.2.4.11.5.1 |
cinPortConfigCINIndexThe identifier for the particular CIN configuration that
these protocol port definitions are associated with. This object
is the same as the cinIndex value in the cinTable.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.5.1.1 |
cinPortConfigIndexThe identifier of a particular CIN protocol port configuration
for a given CIN configuration as specified by cinPortConfigCINIndex.
There can be up to 8 unique protocol port definitions per CIN
configuration.ro INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.5.1.2 |
cinPortConfigProtocolIDIndicates whether the port protocol definition is for a TCP or UDP port.
If the value of notDefined(3) is returned, the entry has yet to be configured.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.11.5.1.3 |
cinPortConfigExternalPortThe external port number specified for this port protocol
definition, ranging from 1 to 65,534.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.5.1.4 |
cinPortConfigInternalPortThe internal port number specified for this port protocol
definition, ranging from 1 to 65,534.rw INTEGER .1.3.6.1.4.1.2.3.51.2.4.11.5.1.5 |
cinPortConfigEnableThe status of this port protocol definition.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.11.5.1.6 |
cinPortConfigDirectionThe traffic direction specified for this port protocol definition.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.11.5.1.7 |
configurationManagement OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.4.15 |
saveConfigurationToChassisSave the configuration settings from the AMM to the chassis.
This operation may take several seconds.
The input values for the SET command when AMM is installed in BladeCenter and
BladeCenter T are:
1: Save the configuration settings in compressed(AMM) format.
2: Save the configuration settings in legacy(MM) format. This option has
been deprecated.
other: Invalid.
The input values for the SET command when AMM is installed in BladeCenter H and
BladeCenter HT are:
1: Save the configuration settings in compressed(AMM) format.
other: Invalid.
NOTE: This MIB object is for AMM only and the value returned for the GET command is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.15.1 |
restoreConfigurationFromChassisRestore the configuration settings to the AMM from the BladeCenter chassis.
NOTE: This MIB object is for AMM only and the value returned for the GET command is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.15.2 |
autoReadConfigInNewChassisThe AMM will automatically read configuration settings
from the midplane every time the AMM is inserted into a
new chassis.
NOTE: This MIB object is for AMM only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.4.15.3 |
telcoManagement OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.5 |
telcoAlarmReq OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.5.1 |
telcoAlarmSetCreate a software alarm. An input octet string consists of the
alarm severity level and the alarm description (40 bytes max).
The following severity levels are valid :
CRT Critical
MJR Major
MNR Minor
NOTE 1: The level (e.g. MJR) and alarm description string must
be separated by a blank, otherwise, a badValue error will be returned.
NOTE 2: Value returned for the GET command is meaningless for
this MIB object.
NOTE 3: This MIB object is for BladeCenter T only.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.5.1.1 |
telcoAlarmAckAcknowledge an alarm. An input octet string consists of the
alarm key ID expressed as 'mmm:ggg:iii:aaa:sss' where:
m : Module ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
g : Gen ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
i : GenInfo ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
a : Alarm ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
s : Alarm severity value of decimal digits(1-255) or
blank space(s) for leading zero(s)
NOTE 1: Value returned for the GET command is meaningless for
this MIB object.
NOTE 2: This MIB object is for BladeCenter T only.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.5.1.2 |
telcoAlarmClearClear an active alarm. An input octet string consists of the
alarm key ID expressed as 'mmm:ggg:iii:aaa:sss' where:
m : Module ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
g : Gen ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
i : GenInfo ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
a : Alarm ID value of decimal digits(1-255) or
blank space(s) for leading zero(s)
s : Alarm severity value of decimal digits(1-255) or
blank space(s) for leading zero(s)
NOTE1 : Value returned for the GET command is meaningless for
this MIB object.
NOTE 2: This MIB object is for BladeCenter T only.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.5.1.3 |
telcoHWManagement OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.5.3 |
tappowerReq OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.5.3.1 |
tappoweronoffTelco Alarm Panel power on or power off. If powering off a currently
powered on Telco Alarm Panel, then all LEDs of this request card will
be reset to OFF and the Safely Remove LED will be turned ON to indicate
the card is safe for removal.
NOTE: This MIB object is for BladeCenter HT only.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.5.3.1.1 |
ncReq OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.5.3.2 |
ncReqTableTable of the Network Clock Module Operations.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.deprecated SEQUENCE OF NcReqEntry .1.3.6.1.4.1.2.3.51.2.5.3.2.1 |
ncReqEntryNetwork Clock Module Power ON/OFF entry.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.deprecated NcReqEntry .1.3.6.1.4.1.2.3.51.2.5.3.2.1.1 |
ncReqIndexNetwork Clock Module Request index.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.5.3.2.1.1.1 |
ncReqBayNumberNetwork Clock Module Request Bay number.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.5.3.2.1.1.2 |
ncReqPoweronoffRequest to power on/off for the specified Network Clock Module.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BladeCenter HT only.
NOTE: Value returned for the GET command is meaningless for this MIB object.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.5.3.2.1.1.3 |
telcoOEM OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.5.127 |
telcoOEMsA bitmap of information about the contents of this subtree. The
bitmap is a variable length string containing a list of 1's and 0's.
Every bit that is set to 1 has a corresponding subtree entry that
is supported in firmware, while a 0 means that the subtree entry
is unavailable.
NOTE: This MIB object is for BladeCenter T only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.5.127.1 |
restartReset OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.7 |
restartSPImmediatelyRestart the MM immediately.
NOTE: Value returned for the GET command is meaningless for
this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.7.4 |
restartStandbyMMRestarts the Standby MM from the Primary MM.
NOTE: Value returned for the GET command is meaningless for
this MIB object.
NOTE: This mib object is only applicable to systems with a standby MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.7.5 |
switchOverRedundantMMSwitch over to the redundant Management Module.
The failover will not occur if the standby or primary MM is in flashing mode.
NOTE: Value returned for the GET command is meaningless for
this MIB object.
NOTE: This mib object is only applicable to systems with a redundant MM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.7.7 |
resetSPConfigAndRestartWill cause all the MM information to be reset to it's
initial factory defaults (all previous configuration
information is lost) and the MM will be re-started.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.7.20 |
resetSPConfigAndRestartSaveLogsWill cause all the MM information to be reset to it's
initial factory defaults (all previous configuration
information is lost) and the MM will be re-started. The
logs will be saved.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.7.21 |
blades OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22 |
processorBlade OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1 |
bladeMediaTrayBladeIdAllocate the media tray to a blade of a BladeCenter system.
On a get command, a blade ID of 0x00 means that no blade is
currently using the device. A set command cannot allocate
the media tray to the management module.
NOTE: A blade cannot be allocated to the media tray if the
value of OID remoteMediaTraySwitchEnable of the blade is disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.1 |
bladeKVMBladeIdAllocate the keyboard, video, and mouse ports (KVM) to a blade
of a blade runner system. On a get command, a blade ID of 0x00
means that no blade is currently using the devices. A set
command cannot allocate the KVM to the management module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.2 |
bladeBootSequenceTableTable of blade boot sequence information. Contains
the boot sequence information for each blade. SEQUENCE OF BladeBootSequenceEntry .1.3.6.1.4.1.2.3.51.2.22.1.3 |
bladeBootSequenceEntryBoot sequence entry BladeBootSequenceEntry .1.3.6.1.4.1.2.3.51.2.22.1.3.1 |
bootSequenceIndexBlade boot sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.3.1.1 |
bootSequenceBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.3.1.2 |
bootSequenceBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.3.1.3 |
bootSequenceBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.3.1.4 |
bootSequenceBladeHealthStateThe 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 AMM is currently in the process of discovering this blade.
Communications Error: The AMM 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.22.1.3.1.5 |
bootSequenceBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.3.1.6 |
bootSequence1The boot device for this blade boot sequence. Note that some types
of blades don't support floppy disk drive. It is recommended that all
boot sequence 1,2 3, and 4 be configured starting from boot sequence 1.
If there is any duplication of the configured boot sequence and the
current configuration, the two boot sequence will be swapped.
For an example: the current boot sequence is
1=HD0, 2=CD, 3=FD, 4=HD1
If the user wants to configure 1=FD which is a duplication of 3 then the
new boot sequence will be:
1=FD, 2=CD, 3=HD0, 4=HD1 (1 and 3 swapped)
Not all hard drives are available on all blade configurations.
The 'Iscsi critical' option has a special meaning: the blade tries to
find an iscsi boot device and if it does not it keeps trying forever.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.3.1.7 |
bootSequence2The boot device for this blade boot sequence. Note that some types
of blades don't support floppy disk drive. It is recommended that all
boot sequence 1,2 3, and 4 be configured starting from boot sequence 1.
If there is any duplication of the configured boot sequence and the
current configuration, the two boot sequence will be swapped.
For an example: the current boot sequence is
1=HD0, 2=CD, 3=FD, 4=HD1
If the user wants to configure 1=FD which is a duplication of 3 then the
new boot sequence will be:
1=FD, 2=CD, 3=HD0, 4=HD1 (1 and 3 swapped)
Not all hard drives are available on all blade configurations.
The 'Iscsi critical' option has a special meaning: the blade tries to
find an iscsi boot device and if it does not it keeps trying forever.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.3.1.8 |
bootSequence3The boot device for this blade boot sequence. Note that some types
of blades don't support floppy disk drive. It is recommended that all
boot sequence 1,2 3, and 4 be configured starting from boot sequence 1.
If there is any duplication of the configured boot sequence and the
current configuration, the two boot sequence will be swapped.
For an example: the current boot sequence is
1=HD0, 2=CD, 3=FD, 4=HD1
If the user wants to configure 1=FD which is a duplication of 3 then the
new boot sequence will be:
1=FD, 2=CD, 3=HD0, 4=HD1 (1 and 3 swapped)
Not all hard drives are available on all blade configurations.
The 'Iscsi critical' option has a special meaning: the blade tries to
find an iscsi boot device and if it does not it keeps trying forever.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.3.1.9 |
bootSequence4The boot device for this blade boot sequence. Note that some types
of blades don't support floppy disk drive. It is recommended that all
boot sequence 1,2 3, and 4 be configured starting from boot sequence 1.
If there is any duplication of the configured boot sequence and the
current configuration, the two boot sequence will be swapped.
For an example: the current boot sequence is
1=HD0, 2=CD, 3=FD, 4=HD1
If the user wants to configure 1=FD which is a duplication of 3 then the
new boot sequence will be:
1=FD, 2=CD, 3=HD0, 4=HD1 (1 and 3 swapped)
Not all hard drives are available on all blade configurations.
The 'Iscsi critical' option has a special meaning: the blade tries to
find an iscsi boot device and if it does not it keeps trying forever.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.3.1.10 |
bladeRemoteControl OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.4 |
bladeRemoteControlTableTable of blade remote power control information.
Contains power on/off enablement status for each blade. SEQUENCE OF BladeRemoteControlEntry .1.3.6.1.4.1.2.3.51.2.22.1.4.1 |
bladeRemoteControlEntryRemote power control entry BladeRemoteControlEntry .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1 |
remoteControlIndexBlade remote power control index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.1 |
remoteControlBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.2 |
remoteControlBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.3 |
remoteControlBladePowerStateThe power state for blade.
0 = off, 1 = on, 3 = standby, 4 = hibernate, 255 = unknown.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.4 |
remoteControlBladeHealthStateThe 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 AMM is currently in the process of discovering this blade.
Communications Error: The AMM 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.22.1.4.1.1.5 |
remoteControlBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.6 |
remotePowerControlEnableBlade remote power control enablement status.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.7 |
remoteMediaTrayControlEnableBlade media tray enablement status.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.8 |
remoteKVMControlEnableBlade KVM enablement status. Note that some types of blades
don't support KVMrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.9 |
remoteWakeOnLanControlEnableBlade Wake On LAN enablement status.
If WOL is not supported by the blade, it displays 'notApplicable'
and WOL can not be enabled or disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.10 |
remoteMediaTraySwitchEnableBlade Remote Media Tray Switch enablement status.
If the remote disk feature is disabled, this OID cannot be set.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.1.1.11 |
bladePolicy OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.4.2 |
bladePolicyPowerControlEnableBlade remote power control enablement status policy.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.2.1 |
bladePolicyMediaTrayControlEnableBlade media tray enablement status policy.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.2.2 |
bladePolicyKVMControlEnableBlade KVM enablement status policy. Note that some types of blades
don't support KVM.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.2.3 |
bladePolicyWakeOnLanControlEnableBlade Wake On LAN enablement status policy. The
notApplicable(255) enumeration is not valid for SET
operations.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.2.4 |
bladePolicyMediaTraySwitchEnableBlade Remote Media Tray Switch enablement status policy.
If the remote disk feature is disabled, this OID cannot be set.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.2.5 |
bladePolicyMultipleRemoteVideoEnableBlade multiple remote video sessions enablement status policy.
A maximum users can access the video of the same blade from remote
console when set to enabled. If it is disabled, only one user can
access the video from remote control.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.2.6 |
bladePolicyAutoPowerOnBlade auto-power on policy.
- restore: all blades will be powered on which were previously on.
- auto: all blades will automatically be powered on when power is applied to the chassis.
- manual: all blades will be left off until manually powered on by the user.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.4.2.7 |
bladeMonitors OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.5 |
bladeSystemStatusTableTable of blade status information. SEQUENCE OF BladeSystemStatusEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.1 |
bladeSystemStatusEntryBlade system status entry BladeSystemStatusEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1 |
bladeStatusIndexBlade system status index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.1 |
bladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.2 |
bladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.3 |
bladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.4 |
bladeHealthStateThe 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 AMM is currently in the process of discovering this blade.
Communications Error: The AMM 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.22.1.5.1.1.5 |
bladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.6 |
bladeRemotePowerEnableRemote power state for the blade.
0x01 indicates enabled.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.7 |
bladeRemoteMediaTrayEnableRemote Media Tray state for the blade.
0x01 indicates enabled.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.8 |
bladeRemoteKVMEnableRemote keyboard/video/monitor state for the blade.
0x01 indicates enabled. Note that some types of blades
don't support KVMro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.9 |
bladeConnectionTypeConnection type of the expansion card number one.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.10 |
bladeOwnsKVMIndicates whether the MM owns the KVM.
0 = false, 1 = true. Note that some types of blades
don't support KVMro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.11 |
bladeOwnsMediaTrayIndicates whether the blade owns the Media Tray.
0 = false, 1 = true.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.12 |
bladeRemoteWakeOnLanEnableRemote wake on LAN state for the blade.
0x01 indicates enabled.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.13 |
bladeServerExpansionThis shows whether this blade has an expansion board attached.
A yes column indicates that an expansion board is installed for this
blade.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.14 |
bladeWidthThe width of the blade including any supplement blade attached to itro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.15 |
bladeSupportCapacityOnDemandThis shows whether this blade support Capacity On Demand.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.16 |
bladeServerExpansion2This shows whether this blade has an expansion board attached.
A yes column indicates that an expansion board is installed for this
blade.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.17 |
bladecKVMStatusThis shows whether this blade has a concurrent keyboard, video, and
mouse (cKVM) card installed and the status of cKVM on the blade.
Not present: A cKVM card is not installed.
Not ready: A cKVM card is installed but is not functional.
Ready: A cKVM card is installed and is functional, with no cKVM session in progress.
Active: A cKVM card is installed and is functional, with a cKVM session currently in progress.
Disabled: A cKVM card is not enabled on this blade.
Not available: A cKVM card is installed but the status is not available.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.21 |
bladeConnectionType2Connection type of the expansion card number 2.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.22 |
bladeConnectionType3Connection type of the expansion card number 3.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.23 |
bladeConnectionType4Connection type of the expansion card number 4.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.24 |
bladeConnectionType5Connection type of the expansion card number 5.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.25 |
bladeHighSpeedConnectionTypeConnection type of the high speed expansion card number 1.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.41 |
bladeIOCompatibilityI/O compatibility status for the blade.
The possible values and their meanings are as follows:
unknown: This indicates a communication error for the blade.
ok: This is the normal (good) case where the blade and the
corresponding I/O modules it is internally wired to have no
compatibility issues.
noIOMs: This means there are no I/O modules in any of the
corresponding I/O module bays this blade is internally wired to.
attention: This indicates that one or more of the corresponding
I/O modules are in communication error.
mismatch: This indicates one of the following cases:
Fabric types are incompatible
An unknown I/O module type
An unknown fabric type on the bladero OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.51 |
bladeInventoryReadyWhen a blade management controller or the AMM is reset, the
blade inventory data is refreshed in the AMM database. This includes
items like IBM VPD (e.g. - serial number, UUID) and MAC address information.
Applications need to know when this information has been populated on the AMM
before they begin to query it using SNMP or other means. This simple flag
object will return a ready or notReady indication for each blade regarding the
status of this information.
Notes:
For blades that are experiencing a 'communication failure' or
'initialization failure' condition, this object will continue to indicate
notReady until the condition is resolved. Therefore, any application that
polls this object should also incorporate a timeout period. As of AMM
release v5.3, a 10 minute timeout seems to be a minimum suggested polling period.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.1.1.52 |
bladeHealthSummaryTableTable of blade health summary information.
Contains information about the overall blade health status. SEQUENCE OF BladeHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.2 |
bladeHealthSummaryEntryBlade health summary entry BladeHealthSummaryEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.2.1 |
bladeHealthSummaryIndexBlade health summary index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.2.1.1 |
bladeHealthSummaryBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.2.1.2 |
bladeHealthSummarySeveritySystem health summary severity.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.2.1.3 |
bladeHealthSummaryDescriptionSystem health summary description.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.2.1.4 |
bladeHealthSummaryDateTimeSystem health summary date time.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.2.1.5 |
bladeTemperaturesTableTable of blade temperatures information. SEQUENCE OF BladeTemperaturesEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.3 |
bladeTemperaturesEntryBlade temperatures table entry BladeTemperaturesEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1 |
temperatureIndexBlade temperatures table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.1 |
temperatureBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.2 |
temperatureBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.3 |
temperatureBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.4 |
temperatureBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.5 |
temperatureCPU1The blade CPU 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.6 |
temperatureCPU2The blade CPU 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.7 |
temperatureCPU3The blade CPU 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.8 |
temperatureCPU4The blade CPU 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.9 |
temperatureDASD1The blade DASD 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.10 |
bladeSensorTempCapabilityIndicates whether the server blade is IPMI capable or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.11 |
bladeSensor1TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.12 |
bladeSensor2TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.13 |
bladeSensor3TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.14 |
bladeSensor4TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.15 |
bladeSensor5TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.16 |
bladeSensor6TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.17 |
bladeSensor7TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.18 |
bladeSensor8TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.19 |
bladeSensor9TempTemperature reading for an IPMI blade expressed 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.3.1.20 |
bladeTemperatureThresholdsTableTable of blade temperature thresholds information. SEQUENCE OF BladeTemperatureThresholdsEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.4 |
bladeTemperatureThresholdsEntryBlade temperature thresholds table entry BladeTemperatureThresholdsEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1 |
temperatureThresholdIndexBlade temperature threshold table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.1 |
temperatureThresholdBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.2 |
temperatureThresholdBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.3 |
temperatureThresholdBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.4 |
temperatureThresholdBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.5 |
temperatureCPU1HardShutdownThe blade CPU hard shutdown temperature in degrees
centigrade(C). If the component's temperature rises above
this value the system will be powered off immediately.
If enabled, a critical alert/event will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.6 |
temperatureCPU1WarningThe blade CPU warning temperature in degrees centigrade(C).
If the temperature rises above this value a warning alert/event
if enabled will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.7 |
temperatureCPU1WarningResetThe blade CPU warning reset temperature in degrees
centigrade(C). If the temperature rises above this value and
if a warning alert/event had previously been created then the
alert/event will be reset.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.8 |
temperatureCPU2HardShutdownThe blade CPU hard shutdown temperature in degrees
centigrade(C). If the component's temperature rises above
this value the system will be powered off immediately.
If enabled, a critical alert/event will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.9 |
temperatureCPU2WarningThe blade CPU warning temperature in degrees centigrade(C).
If the temperature rises above this value a warning alert/event
if enabled will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.10 |
temperatureCPU2WarningResetThe blade CPU warning reset temperature in degrees
centigrade(C). If the temperature rises above this value and
if a warning alert/event had previously been created then the
alert/event will be reset.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.11 |
temperatureCPU3HardShutdownThe blade CPU hard shutdown temperature in degrees
centigrade(C). If the component's temperature rises above
this value the system will be powered off immediately.
If enabled, a critical alert/event will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.12 |
temperatureCPU3WarningThe blade CPU warning temperature in degrees centigrade(C).
If the temperature rises above this value a warning alert/event
if enabled will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.13 |
temperatureCPU3WarningResetThe blade CPU warning reset temperature in degrees
centigrade(C). If the temperature rises above this value and
if a warning alert/event had previously been created then the
alert/event will be reset.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.14 |
temperatureCPU4HardShutdownThe blade CPU hard shutdown temperature in degrees
centigrade(C). If the component's temperature rises above
this value the system will be powered off immediately.
If enabled, a critical alert/event will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.15 |
temperatureCPU4WarningThe blade CPU warning temperature in degrees centigrade(C).
If the temperature rises above this value a warning alert/event
if enabled will be generated.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.16 |
temperatureCPU4WarningResetThe blade CPU warning reset temperature in degrees
centigrade(C). If the temperature rises above this value and
if a warning alert/event had previously been created then the
alert/event will be reset.
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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.17 |
temperatureDASD1HardShutdownThe blade DASD hard shutdown 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.18 |
temperatureDASD1WarningThe blade DASD warning 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.19 |
temperatureDASD1WarningResetThe blade DASD warning reset 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.20 |
bladeTempThresholdSensorCapabilityIndicates whether the server blade is IPMI capable or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.21 |
temperatureSensor1HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.22 |
temperatureSensor1WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.23 |
temperatureSensor1WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.24 |
temperatureSensor2HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.25 |
temperatureSensor2WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.26 |
temperatureSensor2WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.27 |
temperatureSensor3HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.28 |
temperatureSensor3WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.29 |
temperatureSensor3WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.30 |
temperatureSensor4HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.31 |
temperatureSensor4WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.32 |
temperatureSensor4WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.33 |
temperatureSensor5HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.34 |
temperatureSensor5WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.35 |
temperatureSensor5WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.36 |
temperatureSensor6HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.37 |
temperatureSensor6WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.38 |
temperatureSensor6WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.39 |
temperatureSensor7HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.40 |
temperatureSensor7WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.41 |
temperatureSensor7WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.42 |
temperatureSensor8HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.43 |
temperatureSensor8WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.44 |
temperatureSensor8WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.45 |
temperatureSensor9HardShutdownThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.46 |
temperatureSensor9WarningThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.47 |
temperatureSensor9WarningResetThe blade hard shutdown temperature for IPMI blades 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.
The string 'No Temperature' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.4.1.48 |
bladeVoltagesTableTable of blade voltages information. SEQUENCE OF BladeVoltagesEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.5 |
bladeVoltagesEntryBlade voltages table entry BladeVoltagesEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1 |
voltageIndexBlade voltages table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.1 |
voltageBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.2 |
voltageBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.3 |
voltageBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.4 |
voltageBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.5 |
bladePlus5Volt+5 Volt power supply voltage reading for the blade
expressed in Volts(V). An octet string expressed as
'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.6 |
bladePlus3pt3Volt+3.3 Volt power supply voltage reading for the blade
expressed in Volts(V). An octet string expressed as
'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.7 |
bladePlus12Volt+12 Volt power supply voltage reading for the blade
expressed in Volts(V). An octet string expressed as
'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.8 |
bladePlus2pt5Volt+2.5 Volt power supply voltage reading for the blade
expressed in Volts(V). An octet string expressed as
'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.10 |
bladePlus1pt5Volt+1.5 Volt power supply voltage reading for the blade
expressed in Volts(V). An octet string expressed as
'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.11 |
bladePlus1pt25Volt+1.25 Volt power supply voltage reading for the blade
expressed in Volts(V). An octet string expressed as
'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.12 |
bladeVRM1VoltVRM 1 voltage reading for the blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.13 |
bladeSensorVoltCapabilityIndicates whether the server blade is IPMI capable or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.14 |
bladeSensor1VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.15 |
bladeSensor2VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.16 |
bladeSensor3VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.17 |
bladeSensor4VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.18 |
bladeSensor5VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.19 |
bladeSensor6VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.20 |
bladeSensor7VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.21 |
bladeSensor8VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.22 |
bladeSensor9VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.23 |
bladeSensor10VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.24 |
bladeSensor11VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.25 |
bladeSensor12VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.26 |
bladeSensor13VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.27 |
bladeSensor14VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.28 |
bladeSensor15VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.29 |
bladeSensor16VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.30 |
bladeSensor17VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.31 |
bladeSensor18VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.32 |
bladeSensor19VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.33 |
bladeSensor20VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.34 |
bladeSensor21VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.35 |
bladeSensor22VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.36 |
bladeSensor23VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.37 |
bladeSensor24VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.38 |
bladeSensor25VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.39 |
bladeSensor26VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.40 |
bladeSensor27VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.41 |
bladeSensor28VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.42 |
bladeSensor29VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.43 |
bladeSensor30VoltVoltage reading for an IPMI blade expressed in Volts(V).
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.5.1.44 |
bladeVoltageThresholdsTableTable of blade VoltageThresholds information. SEQUENCE OF BladeVoltageThresholdsEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.6 |
bladeVoltageThresholdsEntryBlade voltage thresholds table entry BladeVoltageThresholdsEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1 |
voltageThresholdIndexBlade voltage thresholds table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.1 |
voltageThresholdBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.2 |
voltageThresholdBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.3 |
voltageThresholdBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.4 |
voltageThresholdBladeNameThe name of the blade as a null terminated string.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.5 |
bladePlus5VoltHighWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage rises above this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.6 |
bladePlus5VoltLowWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage drops below this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.7 |
bladePlus3pt3VoltHighWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage rises above this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.8 |
bladePlus3pt3VoltLowWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage drops below this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.9 |
bladePlus12VoltHighWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage rises above this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.10 |
bladePlus12VoltLowWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage drops below this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.11 |
bladePlus2pt5VoltHighWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage rises above this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.14 |
bladePlus2pt5VoltLowWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage drops below this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.15 |
bladePlus1pt5VoltHighWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage rises above this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.16 |
bladePlus1pt5VoltLowWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage drops below this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.17 |
bladePlus1pt25VoltHighWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage rises above this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.18 |
bladePlus1pt25VoltLowWarningVoltage warning threshold reading expressed in Volts(V).
If the voltage drops below this value a warning alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.19 |
bladeVoltThresholdSensorCapabilityIndicates whether the server blade is IPMI capable or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.22 |
bladeSensor1VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.23 |
bladeSensor1VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.24 |
bladeSensor2VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.25 |
bladeSensor2VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.26 |
bladeSensor3VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.27 |
bladeSensor3VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.28 |
bladeSensor4VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.29 |
bladeSensor4VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.30 |
bladeSensor5VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.31 |
bladeSensor5VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.32 |
bladeSensor6VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.33 |
bladeSensor6VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.34 |
bladeSensor7VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.35 |
bladeSensor7VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.36 |
bladeSensor8VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.37 |
bladeSensor8VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.38 |
bladeSensor9VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.39 |
bladeSensor9VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.40 |
bladeSensor10VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.41 |
bladeSensor10VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.42 |
bladeSensor11VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.43 |
bladeSensor11VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.44 |
bladeSensor12VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.45 |
bladeSensor12VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.46 |
bladeSensor13VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.47 |
bladeSensor13VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.48 |
bladeSensor14VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.49 |
bladeSensor14VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.50 |
bladeSensor15VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.51 |
bladeSensor15VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.52 |
bladeSensor16VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.53 |
bladeSensor16VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.54 |
bladeSensor17VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.55 |
bladeSensor17VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.56 |
bladeSensor18VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.57 |
bladeSensor18VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.58 |
bladeSensor19VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.59 |
bladeSensor19VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.60 |
bladeSensor20VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.61 |
bladeSensor20VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.62 |
bladeSensor21VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.63 |
bladeSensor21VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.64 |
bladeSensor22VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.65 |
bladeSensor22VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.66 |
bladeSensor23VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.67 |
bladeSensor23VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.68 |
bladeSensor24VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.69 |
bladeSensor24VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.70 |
bladeSensor25VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.71 |
bladeSensor25VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.72 |
bladeSensor26VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.73 |
bladeSensor26VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.74 |
bladeSensor27VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.75 |
bladeSensor27VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.76 |
bladeSensor28VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.77 |
bladeSensor28VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.78 |
bladeSensor29VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.79 |
bladeSensor29VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.80 |
bladeSensor30VoltHighWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage rises above this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.81 |
bladeSensor30VoltLowWarningVoltage warning threshold reading for IPMI blades expressed in Volts(V).
If the voltage drops below this value, a critical alert/event
if enabled will be generated.
An octet string expressed as 'sdd.dd Volts' where:
s is the sign ('-' for negative or '+' 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.
The string 'No Voltage' indicates that the given monitor
does not exist on this system or is powered off.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.6.1.82 |
bladeIOCompatibilityTableTable of IO Compatibility status for the blade. SEQUENCE OF BladeIOCompatibilityEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.7 |
bladeIOCompatibilityEntryBlade IO Compatibility Status entry BladeIOCompatibilityEntry .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1 |
bladeIOCompatibilityIndexThe blade I/O compatibility table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.1 |
bladeIOCompatibilityBladeIdThe blade numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.2 |
bladeIOCompatibilityBayNumberThe Bay number of the blade or expension card.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.3 |
bladeIOCompatibilityModuleBayThe modules (each one specified by module type and bay number)
that the blade can communicate with over the midplane networking fabric
(i.e. a physical path exists between the blade and this module, and
hardware exists on the blade to communicate with this module).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.4 |
bladeIOCompatibilityModulePowerThe power state of the module specified in bladeIOCompatibilityModuleBay.
n/a if module not installed.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.5 |
bladeIOCompatibilityModuleFabricTypeThe fabric type of the module specified in bladeIOCompatibilityModuleBay.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.6 |
bladeIOCompatibilityFabricOnBladeThe fabric type for this channel on the blade (may be onboard fabric or
an expansion card).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.7 |
bladeIOCompatibilityStatusThe compatibility status between the blade and the module specified
in bladeIOCompatibilityModuleBay.
The possible values are:
OK: No compatibility issues
No IOM: There is no module on the other side of the wire for this channel on the blade.
n/a: (Not applicable) The module specified in bladeIOCompatibilityModuleBay is a bridge,
so the blade port cannot connect to it.
Attention: The module specified in bladeIOCompatibilityModuleBay has a communication error.
Mismatch: Indicates one of the following cases:
Fabric types are incompatible
Module specified in bladeIOCompatibilityModuleBay is of unknown type
Unknown fabric type on the bladero OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.5.7.1.8 |
bladePowerRestart OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.6 |
bladePowerRestartTableTable of blade remote power control information.
Contains power on/off enablement status for each blade. SEQUENCE OF BladePowerRestartEntry .1.3.6.1.4.1.2.3.51.2.22.1.6.1 |
bladePowerRestartEntryBlade power restart table entry BladePowerRestartEntry .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1 |
powerRestartIndexBlade power restart table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.1 |
powerRestartBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.2 |
powerRestartBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.3 |
powerRestartBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.4 |
powerRestartBladeHealthStateThe 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 AMM is currently in the process of discovering this blade.
Communications Error: The AMM 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.22.1.6.1.1.5 |
powerRestartBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.6 |
powerOnOffBladeControl the power state of a specific blade.
Off: Power Off Blade.
On: Power On Blade.
Softoff: Shut Down OS and Power Off Blade. This operation is not
supported on all blades.
NOTE: Value returned for the GET command is meaningless
for this MIB object. The powerRestartBladePowerState MIB object should be
used to check the power state of the blade(s)rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.7 |
restartBladeRestart a blade.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.8 |
restartBladeSMPRestart a blade's system management processor.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.9 |
restartBladeNMIIssue an NMI to the blade. This option is not supported
on all blades.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.10 |
restartBladeClearNVRAMRestart a blade and set NVRAM to default values. This option is not
supported on all blades.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.11 |
restartBladeInvokeDiagsRestart a blade and boot into diagnostic mode. This option is not
supported on all blades.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.12 |
restartBladeInvokeDiagsFromDefaultBootListRestart a blade and boot into diagnostic mode from Default Boot List
as defined on the blade. This option is not supported on all blades.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.13 |
restartBladeToSMSBootMenuRestart a blade to SMS boot menu. This option is not supported on
all blades.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.6.1.1.14 |
bladeConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.7 |
bladeConfigurationTableTable of blade remote power control information.
Contains power on/off enablement status for each blade. SEQUENCE OF BladeConfigurationEntry .1.3.6.1.4.1.2.3.51.2.22.1.7.1 |
bladeConfigurationEntryBlade configuration table entry BladeConfigurationEntry .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1 |
configurationIndexBlade configuration table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.1 |
configurationBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.2 |
configurationBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.3 |
configurationBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.4 |
configurationBladeNameThe name of the blade as a null terminated string.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.5 |
configurationBladecKVMEnable or disable the concurrent KVM function on specified blade.
If concurrent KVM is not supported by the blade, it displays 'notPresent'
and the concurrent KVM functionality can not be enabled or disabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.6 |
configurationBladeActiveBootModeIndicates the active copy of the firmware from which the blade is booting.
NOTE: Some blades do not support the automatic boot recovery. It displays
'notApplicable' for such blades.
Booting from the temporary copy is recommended since it typically contains the
latest enhancements and fixes. Switching to the permanent copy should be reserved
for when booting from the temporary copy is no longer possible.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.7 |
configurationBladePendingBootModeIndicates the copy of the firmware from which the blade will boot
after the next reboot.
NOTE: Some blades do not support the automatic boot recovery. It displays
'notApplicable' for such blades and the value can not be set.
Booting from the temporary copy is recommended since it typically contains the
latest enhancements and fixes. Switching to the permanent copy should be reserved
for when booting from the temporary copy is no longer possible.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.1.1.8 |
bladePowerManagementPolicy OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.7.2 |
powerdomain1OversubscriptionPower Management Policy settings for power domain 1.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.2.1 |
powerdomain2OversubscriptionPower Management Policy settings for power domain 2.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.2.2 |
acousticModeAcoustic mode setting for thermal conditionsrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.2.3 |
nebsModeNEBS (Network Equipment-Building System) mode setting for thermal conditions.
NOTE: This MIB object is for BladeCenter T, HT and TR only.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.2.4 |
bladecKVMEnableDisableEnable or disable cKVM function on all server blades.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.7.3 |
bladeIPAddrRangeStartThis field is used to configure the start of the IP address range for the blade
system management processors on the blades. These addresses are used on the
internal management network between the MM and the blade BSMPs. For example the
value of 10.10.10.1 means the BSMP on the blade in bay 1 will have IP address
10.10.10.1, the BSMP on the blade in bay 2 will have IP address 10.10.10.2 and so on.
This field is deprecated and no longer supported. An attempt to SET this
object will be rejected, and any query will always return 0.0.0.0.
Refer to the bladeManagementNetworkInfoTable for the new objects providing
this information.rodeprecated IpAddress .1.3.6.1.4.1.2.3.51.2.22.1.8 |
bladeCapacityOnDemand OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.9 |
bladeCapacityOnDemandTableTable of COD blade.
NOTE: This table is deprecated and no longer supported.deprecated SEQUENCE OF BladeCapacityOnDemandEntry .1.3.6.1.4.1.2.3.51.2.22.1.9.1 |
bladeCapacityOnDemandEntryBlade COD table entry
NOTE: This table is deprecated and no longer supported.deprecated BladeCapacityOnDemandEntry .1.3.6.1.4.1.2.3.51.2.22.1.9.1.1 |
bladeCapacityOnDemandIndexBlade configuration table index.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.9.1.1.1 |
bladeCapacityOnDemandBladeNameThe name of the blade as a null terminated string.
NOTE: This Mib object is deprecated and no longer supported.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.9.1.1.2 |
bladeCapacityOnDemandStateThe state of Capacity On Demand.
NOTE: This Mib object is deprecated and no longer supported.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.9.1.1.3 |
bladeBootCountPowerOnTime OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.10 |
bladeBootCountPowerOnTimeTableTable per blade of the number of boots for the blade and
the number of seconds the blade has been powered on. SEQUENCE OF BladeBootCountPowerOnTimeEntry .1.3.6.1.4.1.2.3.51.2.22.1.10.1 |
bladeBootCountPowerOnTimeEntryThe number of boots for the blade and
the number of seconds the blade has been powered on. BladeBootCountPowerOnTimeEntry .1.3.6.1.4.1.2.3.51.2.22.1.10.1.1 |
bootCountPowerOnTimeBladeIndexBlade boot count/Power On Time table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.10.1.1.1 |
bootCountPowerOnTimeBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.10.1.1.2 |
bootCountPowerOnTimeBootsBlade Boot Count. If there is no blade in the
given slot then this value is undefined. Writing this
value resets the Boot Count to zero.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.10.1.1.3 |
bootCountPowerOnTimeSecsBlade Power On Time in seconds. If there is no blade in
the given slot then this value is undefined. Writing this
value resets the Power On Time to zero.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.10.1.1.4 |
bladeVlanIdThis is the virtual LAN ID for the internal management network between the MM and
the blade system management processors (BSMPs). The range of valid VLAN ID's
is 3 to 4095.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.11 |
bladeNetworkConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.12 |
bladeNetworkInterfaceTableTable of all blades' network interfaces. SEQUENCE OF BladeNetworkInterfaceEntry .1.3.6.1.4.1.2.3.51.2.22.1.12.2 |
bladeNetworkInterfaceEntryBlade configuration table entry BladeNetworkInterfaceEntry .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1 |
bladeNetworkInterfaceIndexBlade Network Interface Table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.1 |
bladeNetworkInterfaceBayNumberThe bay number of the main server blade that supports network interface managementro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.2 |
bladeNetworkInterfaceNumberIndicates which network interface on the blade System Management Processor is be read or writenro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.3 |
bladeNetworkInterfaceTypeIndicates blade network interface type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.4 |
bladeNetworkInterfaceLabelShow string label that identifies the interface.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.5 |
bladeNetworkInterfaceIPAddrShow/modify current IP address of the blade network interface.
Note that only if the bladeNetworkInterfaceEnable is 'enabled(1)' and the bladeNetworkInterfaceDHCPEnable is not 'dhcpEnabled(1)', should the IP address be
pushed down to blade System Management Processorrw IpAddress .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.6 |
bladeNetworkInterfaceSubnetMaskShow or modifie current subnet mask of the blade network interface.
Note that only if the bladeNetworkInterfaceEnable is 'enabled(1)' and the bladeNetworkInterfaceDHCPEnable is not 'dhcpEnabled(1)', should the SunnetMask be
pushed down to blade System Management Processorrw IpAddress .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.7 |
bladeNetworkInterfaceGatewayAddrShow or modify current IP gateway of the blade network interface.
Note that only if the bladeNetworkInterfaceEnable is 'enabled(1)' and the bladeNetworkInterfaceDHCPEnable is not 'dhcpEnabled(1)', should the Gateway address be
pushed down to blade System Management Processorrw IpAddress .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.8 |
bladeNetworkInterfaceVlanIdThis is the Virtual LAN ID for supported network interface cards (NICs).
The range of valid VLAN ID's is 0 to 4095.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.9 |
bladeNetworkInterfaceVlanEnableThis object is no longer supported and will always be 0rodeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.10 |
bladeNetworkInterfaceEnableDisabled or enabled the blade network interface. If the network interface is disabled, then ignore other configurations.
If this network interface doesn't support enabled/disabled, show 'notApplicable(255)'rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.11 |
bladeNetworkInterfaceDHCPEnableIP config method on the blade network interface to modify mode to static IP, dhcp and dhcpthenstatic.
If this network interface doesn't support DHCP, show 'notApplicable(255)'rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.12 |
bladeNetworkInterfaceMACAddrShow the blade network interface MAC address. If this network interface doesn't support MAC, show 'notApplicable'ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.13 |
bladeNetworkInterfaceAssignedSwitchThis field allows you to select an I/O Module to use for
management traffic to the blade.
NOTE: This field is only supported for eth1 of blade.
NOTE: You may only specify ethernet switches to this field.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.2.1.14 |
bladeIPv6Config OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.12.10 |
bladeIPv6ConfigTableA table of IPv6 configuration options for blades.
NOTE: This MIB object is not applicable to blades that
do not support IPv6. SEQUENCE OF BladeIPv6ConfigEntry .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1 |
bladeIPv6ConfigEntryIPv6 configuration options for a blade.
NOTE: This MIB object is not applicable to blades that
do not support IPv6. BladeIPv6ConfigEntry .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1.1 |
bladeIPv6ConfigIndexThe blade's slot numberro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1.1.1 |
bladeIPv6ConfigPortIndexThe physical port number of the given entryro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1.1.2 |
bladeIPv6ConfigEnabledEnables/Disables IPv6 support on the blade.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1.1.3 |
bladeIPv6ConfigStaticEnables/Disables IPv6 static configuration support on the blade.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1.1.4 |
bladeDHCPv6ConfigEnabledEnables/Disables DHCPv6 address configuration support on the blade.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1.1.5 |
bladeIPv6ConfigStatelessEnabledEnables/Disables IPv6 stateless auto-configuration support on the blade.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.10.1.1.6 |
bladeIPv6AddressTableA table of assigned IPv6 addresses for blades.
NOTE: This MIB object is not applicable to blades that
do not support IPv6. SEQUENCE OF BladeIPv6AddressEntry .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2 |
bladeIPv6AddressEntryThe assigned IPv6 address for a given blade.
NOTE: This MIB object is not applicable to blades that
do not support IPv6. BladeIPv6AddressEntry .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1 |
bladeIPv6AddressIndexThe blade's slot number.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1.1 |
bladeIPv6AddressPortIndexThe blade's physical port number for the given entry.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1.2 |
bladeIPv6AddressEntryIndexThe blade's address entry index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1.3 |
bladeIPv6AddressTypeThe address type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1.4 |
bladeIPv6AddressThe assigned IPv6 address.
Note: 'write' is for static ipv6 only.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1.5 |
bladeIPv6AddressPrefixLenThe prefix length for the given address.
Note: 'write' is for static ipv6 only.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1.6 |
bladeIPv6AddressDefaultRouteThe default route used for the given address.
Note: 'write' is for static ipv6 only.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.22.1.12.10.2.1.7 |
bladeBayDataTableTable of blade bay data (BBD) information. SEQUENCE OF BladeBayDataEntry .1.3.6.1.4.1.2.3.51.2.22.1.13 |
bladeBayDataEntryBlade bay data (BBD) table entry. BladeBayDataEntry .1.3.6.1.4.1.2.3.51.2.22.1.13.1 |
bayDataIndexBlade bay data (BBD) table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.13.1.1 |
bayDataBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.13.1.2 |
bayDataBladeExistsIndicates whether the server blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.13.1.3 |
bayDataBladePowerStateIndicates the power state of the blade specified.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.13.1.4 |
bayDataBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.13.1.5 |
bayDataA null terminated string that defines the Blade Bay Data (BBD). This data
is pushed to the blade's BSMP and SMBIOS structures, where it can used
by the blade's OS. Up to 60 characters can be defined plus a Null
terminator.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.13.1.6 |
bayDataBladeStatusThis shows Blade Bay Data (BBD) status. 0 means the blade fully
supports BBD; 1 means that the blade's BIOS does not support BBD;
2 means that there is no blade in the bay; 3 means that the blade is
being discovered. 255 means that the blade does not support BBD.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.13.1.7 |
bladeSPEthOverUSBInterface OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.14 |
spEthOverUSBInterfaceTableTable of blade Service Processor's Ethernet over USB interface. SEQUENCE OF SPEthOverUSBInterfaceEntry .1.3.6.1.4.1.2.3.51.2.22.1.14.1 |
spEthOverUSBInterfaceEntryBlade Service Processor's Ethernet over USB interface entry. SPEthOverUSBInterfaceEntry .1.3.6.1.4.1.2.3.51.2.22.1.14.1.1 |
spEthOverUSBInterfaceIndexService Processor's Ethernet over USB interface table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.14.1.1.1 |
spEthOverUSBInterfaceBladeIdThe numeric blade ID.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.14.1.1.2 |
spEthOverUSBInterfaceBladeExistsIndicates whether the blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.14.1.1.3 |
spEthOverUSBInterfaceBladeNameThe name of the blade as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.14.1.1.6 |
spEthOverUSBInterfaceEnableThis object allows the user to view the status of, and enable
or disable, a blade Service Processor's command interface on
Ethernet-over-USB.
NOTE: If the blade either does not exist or does not support
Ethernet-over-USB command interface. It displays 'notApplicable'.
NOTE: It will take about 10 or more seconds for the disable/enable
setting to take effect.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.14.1.1.9 |
bladeManagementNetwork OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.1.15 |
bladeManagementNetworkControlEnableGlobally disable/enable blade management network auto discovery support.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.15.1 |
bladeManagementNetworkInfoTableTable of blade management network information. SEQUENCE OF BladeManagementNetworkInfoEntry .1.3.6.1.4.1.2.3.51.2.22.1.15.2 |
bladeManagementNetworkInfoEntryBlade management network information entry. BladeManagementNetworkInfoEntry .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1 |
bladeManagementNetworkInfoIndexBlade management network information table indexro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.1 |
bladeManagementNetworkInfoBladeIdThe Blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.2 |
bladeManagementNetworkInfoBladeExistIndicates whether the blade specified exists or not in the chassis.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.3 |
bladeManagementNetworkInfoBladeSupportIndicates whether the blade supports the management network auto discovery capability or not.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.4 |
bladeManagementNetworkInfoPathStatusIndicates the status of the management network for this blade.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.5 |
bladeManagementNetworkInfoBladeIPAddrIndicates the blade system management processor IPv4 address.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.6 |
bladeManagementNetworkInfoBladeMACAddrIndicates the blade system management processor MAC address.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.7 |
bladeManagementNetworkInfoSwitchIdIndicates which switch is selected for the blade management network.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.1.15.2.1.8 |
switchModule OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3 |
switchModuleControl OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.1 |
smControlTableSwitch module control table. SEQUENCE OF SmControlEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.1 |
smControlEntrySwitch module control table entry SmControlEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1 |
smControlIndexSwitch module control table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.1 |
switchModuleControlIdThe switch module numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.2 |
smPostResultsAvailableDescribes whether the switch module POST diagnostic result
value contained in the smPostResultsValue is valid.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.3 |
smPostResultsValueThe range of values and meanings are as follows:
0x00 - 0x7F ( 0 - 127) Base internal functions
0x80 - 0x9F (128 - 159) Internal interface failures
0xA0 - 0xAF (160 - 175) External interface failures
0xB0 - 0xFE (176 - 254) Reserved
0xFF (255) Switch completed POST successfullyro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.4 |
switchModuleMemDiagEnableDisableSwitch module memory diagnostics enabled or disabled.
NOTE: The numeric values for the enumerations for enabled and disabled are non-traditional
(i.e. - 0 and 1 are swapped), however, they cannot be changed since this MIB is already
published.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.5 |
smCfgCtrlEnableDisableSwitch module configuration control. When set to enabled, only the MM can manage
the module.
This MIB object can not be set, if AMM grants switch module the Protected Mode permission.
This MIB object can not be set, if the switch module is participating in the Stacking Mode
and external management is protected.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode. A value of disabled(0) will be returned.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.6 |
smExtEthPortsEnableDisableSwitch module external ethernet ports enabled or disabled.
This MIB object can not be set, if AMM grants switch module the
Protected Mode permission.
This MIB object can not be set, if the switch module is participating
in the Stacking Mode and External Port Access is protected.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.7 |
switchPingRequestSends a ping to a switch module's current IPv4 address.
This MIB object can not be set, if AMM grants switch module the Protected Mode
permission and switch module goes into Protected Mode.
This MIB object can not be set, if the switch module is participating
in the Stacking Mode and IP Configuration is protected.
NOTE: Value returned for the GET command is meaningless
for this MIB object.
NOTE: This object has been deprecated in favor of the new
table smPingTable which supports IPv6 and IPv4 addresses.rwdeprecated Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.8 |
smCfgCtrlOnResetEnableDisableSwitch module configuration control on resets (default and unsolicited).
When set to enabled, the factory default IP configuration will become
active when the I/O module is reset to factory defaults by either the
management module or the I/O module. If an I/O module reset is initiated
by a source other than the management module then the previous IP configuration
will be in affect. In both these cases the MM will lose IP communications with
the IOM.
This MIB object can not be set, if AMM grants switch module the Protected Mode
permission and switch module goes into Protected Mode.
NOTE: The numeric values for the enumerations for enabled and disabled are non-traditional
(i.e. - 0 and 1 are swapped), however, they cannot be changed since this MIB is already
published.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode. A value of disabled(1) will be returned.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.9 |
smHealthStateThe health state for the switch module.
0 = unknown, 1 = good, 2 = warning, 3 = bad.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.15 |
smPMStateThe Protected Mode Status for the switch module.
standby- Protected Mode capability exists on the IOM but has not
been activated on the switch module or the AMM.
pending - Protected Mode has been activated on the AMM but not yet on the switch module.
active - Protected Mode is active on both the switch module and the AMM.
attention - Protected Mode is enabled on the switch module but not on the AMM.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.16 |
smPMCtrlEnableDisableAMM Protected Mode permission for the switch module.
disabled - allow AMM to disable Protected Mode Permission for the switch module.
enabled - allow AMM to grant Protected Mode Permission for the switch module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.17 |
smIOCompatibilityThe compatibility status for the I/O module.
The possible values and their meanings are as follows:
Unknown: This indicates a communication error for the I/O module.
OK: This is the normal (good) case where there are no compatibility
issues between the I/O module and the modules it is internally wired to.
No Fabric: This means the other end is not populated on any of the
modules this I/O module is internally wired to (e.g. this is an
Infiniband switch but none of the blades it is internally wired to
has an expansion card attached in the corresponding expansion slot).
Attention: Indicates one of the following cases:
One or more of the modules this I/O module is internally wired to is in communication error
The I/O module is powered off and at least one module it is internally wired to is powered on
Mismatch: Indicates one of the following cases:
Fabric types are incompatible
An unknown I/O module type
An unknown fabric type on a module the I/O module is internally wired to.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.1.1.18 |
smPingTableAllows pinging one of the active assigned addresses of an I/O module.
NOTE: This table is not applicable to modules that are running in
Stacking Mode and IP configuration is protected. SEQUENCE OF SmPingEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.2 |
smPingEntryRepresents a single address that can be pinged SmPingEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.2.1 |
smPingIndexThe switch module's slot numberro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.1.2.1.1 |
smPingAddressEntryIndexThe switch module's address entry indexro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.1.2.1.2 |
smPingAddressThe switch module's IPv4 or IPv6 addressro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.2.1.3 |
smPingAddressExecutePings the given IP address.
NOTE: The GET operation for this object is meaningless.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.2.1.4 |
smPowerRestartTableSwitch module power restart table. SEQUENCE OF SmPowerRestartEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.7 |
smPowerRestartEntrySwitch module power restart table entry SmPowerRestartEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1 |
smPowerRestartIndexSwitch module power restart index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.1 |
smPowerRestartIdThe switch module numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.2 |
smSwitchExistsIndicates whether the switch module specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.3 |
smSwitchTypeSwitch module type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.4 |
smMACAddressSwitch module MAC address.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.5 |
smIPAddressThe switch module current IP address.
If the switch module is participating in the Stacking Mode
and IP Configuration is protected, then the stack management
IP address is displayed.
NOTE: IPv6 addresses for the switch can be view with the
smIPv6AddressTable.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.6 |
switchModulePowerOnOffI/O Module power on or power off. If powering on a currently
powered off I/O Module, then the I/O Module will execute a POST.
The results of this POST will need to be retrieved using the 'Post Results'
command.
NOTE:
When powering off a currently powered on I/O Module, a minimum of 1 second
is needed to allow the module to power off before powering back on.
The value 'shutdownInProgress' is for I/O Modules that may take some time to
transition from 'poweron' to 'poweroff'. For example, SAS Controller Modules must
flush pending I/O before powering off in order to maintain data integrity.
The value'shutdownInProgress' can not be used to set.
If both SAS Controller Module and SAS Connectivity Module are installed in slot 3
and 4 of BCS chassis, AMM must prevent one of them from powering on otherwise
there would be conflict with the Storage Module access and possibly corruption of data.
This MIB object can not be set, if AMM grants the I/O Module the Protected Mode
permission and module goes into Protected Mode.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.7 |
smResetFor the case where the switch module is currently powered on, this command
will effectively power off and then power on the switch module indicated and
cause it to run its POST test. For the case where the switch module is
currently powered off, the command will just power on the switch module.
This MIB object can not be set, if AMM grants switch module the Protected Mode
permission and switch module goes into Protected Mode.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.8 |
smResetToDefaultFor the case where the switch module is currently powered on, this command
will effectively power off and then power on the switch module indicated and
cause it to run its POST test. For the case where the switch module is
currently powered off, the command will just power on the switch module.
In both cases, the switch module will reset the configuration to the default
values.
This MIB object can not be set, if AMM grants switch module the Protected Mode
permission and switch module goes into Protected Mode.
This MIB object can not be set, if the switch module is participating in the
Stacking Mode and reset to default is protected.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.9 |
smRestartAndRunStdDiagTo power cycle the selected module(s) and then run the standard diagnostic
test package.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.10 |
smRestartAndRunExtDiagTo power cycle the selected module(s) and then run the extended diagnostic
test package. This option is not supported on all I/O modules.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.11 |
smRestartAndRunFullDiagTo power cycle the selected module(s) and then run the full diagnostic test
package. The full diagnostic test package may take over 5 minutes to run.
This option is not supported on all I/O modules.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.12 |
smSwitchSubTypeSwitch module subtype.
NOTE: Some Legacy modules do not support a subtype and will be displayed as unknown.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.20 |
smSwitchWidthSwitch module width.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.21 |
smManufacturingIDSwitch module hardware VPD manufacturing ID.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.22 |
smStackingModeStateThe Stacking Mode Status for the switch module.
standby - I/O module has stacking capability but is not part of a stack.
member - I/O module has stacking capability and is part of a stack in the
member role.
master - I/O module has stacking capability and is part of a stack in the
master role.
NOTE: The term disabled was changed to the term standby to be more descriptive.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.23 |
smStackingModeInfoA string containing a text description about the details of which functions are
protected for a switch module when it is in Stacking Mode as Master or Member.
The possible functions protected by switch modules are IP configuration,
External Port Access, External Management all over ports and Restore to defaults.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.7.1.24 |
smIOCompatibilityTableSwitch module control table. SEQUENCE OF SmIOCompatibilityEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.10 |
smIOCompatibilityEntrySwitch module IO compatibility table entry SmIOCompatibilityEntry .1.3.6.1.4.1.2.3.51.2.22.3.1.10.1 |
smIOCompatibilityIndexSwitch module IO compatibility index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.1.10.1.1 |
smIOCompatibilityIdThe switch module numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.1.10.1.2 |
smIOCompatibilityModuleBayThe modules (each one specified by module type and bay number) that
this I/O module can communicate with over the midplane networking fabric
(i.e. a physical path exists between the I/O module and this module).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.10.1.3 |
smIOCompatibilityModulePowerThe power state of the module specified in smIOCompatibilityModuleBay.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.10.1.4 |
smIOCompatibilityModuleFabricTypeThe I/O fabric type on the module side for the module.
'n/a' will be displayed if the corresponding channel is not populated
on the module side (e.g. we are looking at the details for an Infiniband
switch but the blade does not have an Infiniband expansion card attached
in the corresponding expansion slot).ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.10.1.5 |
smIOCompatibilityStatusThe compatibility status for this I/O module and the module specified
in smIOCompatibilityModuleBay.
The possible values are:
OK: No compatibility issues
n/a: Indicates the corresponding channel is not populated on the module
side even though the module is present (e.g. we are looking at the details
for an Infiniband switch but the blade specified in smIOCompatibilityModuleBay
does not have an Infiniband expansion card attached in the corresponding expansion slot).
Attention: Indicates one of the following:
The module specified in smIOCompatibilityModuleBay has a communication error.
The I/O module is powered off but the module specified in smIOCompatibilityModuleBay is powered on.
Mismatch: Indicates one of the following cases::
Fabric types are incompatible
Unknown fabric type on the module side
Unknown I/O module typero OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.1.10.1.6 |
switchModuleConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2 |
switchMgmtNetworkCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1 |
switchCurrentNwCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1 |
smCurrentIPInfoTableSwitch module current IP information.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected. SEQUENCE OF SmCurrentIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1 |
smCurrentIPInfoEntrySwitch module current IP table entry.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected. SmCurrentIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1 |
smCurrentIPInfoIndexSwitch module current IP info index.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.1 |
smCurrentIPInfoIdThe switch module numeric identifier.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.2 |
smCurrentIPInfoExistsIndicates whether the switch module specified exists or not.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.3 |
smCurrentIPInfoPowerStateIndicates whether the I/O Module specified is powered on or not.
The value 'shutdownInProgress' is for the I/O Module that may take some time to
transition from 'poweron' to 'poweroff'. Such as SAS Controller Modules, that must
flush pending I/O before powering off in order to maintain data integrity.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.4 |
smCurrentIPAddrThe switch module current IP address.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.6 |
smCurrentSubnetMaskThe switch module current subnet mask.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.7 |
smCurrentGatewayThe switch module current IP gateway.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.8 |
smCurrentIPConfigMethodThe switch module current IP configuration method.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.1.1.1.9 |
switchNewNwCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2 |
smNewIPInfoTableSwitch module new IP information.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode or Stacking Mode and IP configuration is protected. SEQUENCE OF SmNewIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1 |
smNewIPInfoEntrySwitch module new IP configuration information table entry.
NOTE: This MIB table is not applicable to modules that are running in Network Address
Translation (NAT) Mode or Stacking Mode and IP configuration is protected. SmNewIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1 |
smNewIPInfoIndexSwitch module new IP info index.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode or Stacking Mode and IP configuration is protected.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.1 |
smNewIPInfoIdThe switch module numeric identifier.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode or Stacking Mode and IP configuration is protected.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.2 |
smNewIPInfoExistsIndicates whether the switch module specified exists or not.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode or Stacking Mode and IP configuration is protected.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.3 |
smNewIPInfoPowerStateIndicates whether the switch module specified is powered on or not.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode or Stacking Mode and IP configuration is protected..ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.4 |
smNewIPAddrThe switch module new IP address. Before setting this object to a new value,
smNewIpconfigEnableDisable object must first be set to disabled.
NOTE: This MIB object can not be set if the AMM grants the switch module Protected Mode
permission and the switch module goes into Protected Mode.
NOTE: This MIB object can not be set if the switch module is in Stacking Mode
and IP Configuration is protected.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.6 |
smNewSubnetMaskThe switch module new subnet mask. Before setting this object to a new value,
smNewIpconfigEnableDisable object must first be set to disabled.
NOTE: This MIB object can not be set if the AMM grants the switch module Protected Mode
permission and the switch module goes into Protected Mode.
NOTE: This MIB object can not be set if the switch module is in Stacking Mode,
and IP Configuration is protected.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.7 |
smNewGatewayThe switch module new IP gateway. Before setting this object to a new value,
smNewIpconfigEnableDisable object must first be set to disabled.
NOTE: This MIB object can not be set if the AMM grants the switch module Protected Mode
permission and the switch module goes into Protected Mode.
NOTE: This MIB object can not be set if the switch module is in Stacking Mode,
and IP Configuration is protected.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.8 |
smNewIPConfigMethodThe switch module new IP configuration method. Before setting this object to a new value,
smNewIpconfigEnableDisable object must first be set to disabled.
NOTE: This MIB object can not be set if the AMM grants the switch module Protected Mode
permission and the switch module goes into Protected Mode.
NOTE: This MIB object can not be set if the switch module is in Stacking Mode,
and IP Configuration is protected.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.9 |
smNewIPConfigEnableDisableA set command enables a new IP configuration that has been
previously defined. A get command indicates whether the new
IP configuration information has been enabled.
NOTE: This MIB object can not be set if the AMM grants the switch module Protected Mode
permission and the switch module goes into Protected Mode.
NOTE: This MIB object can not be set if the switch module is in Stacking Mode,
and IP Configuration is protected.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.2.1.1.10 |
switchNwProtCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3 |
switchNwProtCfgModOne OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1 |
smNwProtInfoModOneTableSwitch module 1 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModOneEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1 |
smNwProtInfoModOneEntrySwitch module 1 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModOneEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1 |
smNwProtInfoModOneIndexSwitch module 1 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.1 |
smNwProtInfoModOneIdThe switch module 1 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.2 |
smNwProtInfoModOneExistsIndicates whether the switch module 1 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.3 |
smNwProtInfoModOnePowerStateIndicates whether the switch module 1 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.4 |
smNwProtInfoModOneProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.5 |
smNwProtInfoModOneProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.6 |
smNwProtInfoModOneExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.7 |
smNwProtInfoModOneIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.8 |
smNwProtInfoModOneEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.1.1.9 |
smNwProtInfoModOneActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.2 |
smNwProtInfoModOneResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.1.3 |
switchNwProtCfgModTwo OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2 |
smNwProtInfoModTwoTableSwitch module 2 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModTwoEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1 |
smNwProtInfoModTwoEntrySwitch module 2 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModTwoEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1 |
smNwProtInfoModTwoIndexSwitch module 2 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.1 |
smNwProtInfoModTwoIdThe switch module 2 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.2 |
smNwProtInfoModTwoExistsIndicates whether the switch module 2 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.3 |
smNwProtInfoModTwoPowerStateIndicates whether the switch module 2 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.4 |
smNwProtInfoModTwoProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.5 |
smNwProtInfoModTwoProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.6 |
smNwProtInfoModTwoExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.7 |
smNwProtInfoModTwoIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.8 |
smNwProtInfoModTwoEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.1.1.9 |
smNwProtInfoModTwoActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.2 |
smNwProtInfoModTwoResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.2.3 |
switchNwProtCfgModThree OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3 |
smNwProtInfoModThreeTableSwitch module 3 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModThreeEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1 |
smNwProtInfoModThreeEntrySwitch module 3 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModThreeEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1 |
smNwProtInfoModThreeIndexSwitch module 3 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.1 |
smNwProtInfoModThreeIdThe switch module 3 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.2 |
smNwProtInfoModThreeExistsIndicates whether the switch module 3 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.3 |
smNwProtInfoModThreePowerStateIndicates whether the switch module 3 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.4 |
smNwProtInfoModThreeProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.5 |
smNwProtInfoModThreeProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.6 |
smNwProtInfoModThreeExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.7 |
smNwProtInfoModThreeIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.8 |
smNwProtInfoModThreeEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.1.1.9 |
smNwProtInfoModThreeActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.2 |
smNwProtInfoModThreeResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.3.3 |
switchNwProtCfgModFour OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4 |
smNwProtInfoModFourTableSwitch module 4 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModFourEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1 |
smNwProtInfoModFourEntrySwitch module 3 network protocol (Network Address Translation) configuration
information table entry. SmNwProtInfoModFourEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1 |
smNwProtInfoModFourIndexSwitch module 4 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.1 |
smNwProtInfoModFourIdThe switch module 4 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.2 |
smNwProtInfoModFourExistsIndicates whether the switch module 4 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.3 |
smNwProtInfoModFourPowerStateIndicates whether the switch module 4 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.4 |
smNwProtInfoModFourProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.5 |
smNwProtInfoModFourProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.6 |
smNwProtInfoModFourExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.7 |
smNwProtInfoModFourIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.8 |
smNwProtInfoModFourEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.1.1.9 |
smNwProtInfoModFourActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.2 |
smNwProtInfoModFourResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.4.3 |
switchNwProtCfgModFive OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5 |
smNwProtInfoModFiveTableSwitch module 5 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModFiveEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1 |
smNwProtInfoModFiveEntrySwitch module 5 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModFiveEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1 |
smNwProtInfoModFiveIndexSwitch module 5 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.1 |
smNwProtInfoModFiveIdThe switch module 5 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.2 |
smNwProtInfoModFiveExistsIndicates whether the switch module 5 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.3 |
smNwProtInfoModFivePowerStateIndicates whether the switch module 5 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.4 |
smNwProtInfoModFiveProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.5 |
smNwProtInfoModFiveProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.6 |
smNwProtInfoModFiveExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.7 |
smNwProtInfoModFiveIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.8 |
smNwProtInfoModFiveEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.1.1.9 |
smNwProtInfoModFiveActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.2 |
smNwProtInfoModFiveResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.5.3 |
switchNwProtCfgModSix OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6 |
smNwProtInfoModSixTableSwitch module 6 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModSixEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1 |
smNwProtInfoModSixEntrySwitch module 6 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModSixEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1 |
smNwProtInfoModSixIndexSwitch module 6 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.1 |
smNwProtInfoModSixIdThe switch module 6 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.2 |
smNwProtInfoModSixExistsIndicates whether the switch module 6 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.3 |
smNwProtInfoModSixPowerStateIndicates whether the switch module 6 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.4 |
smNwProtInfoModSixProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.5 |
smNwProtInfoModSixProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.6 |
smNwProtInfoModSixExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.7 |
smNwProtInfoModSixIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.8 |
smNwProtInfoModSixEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.1.1.9 |
smNwProtInfoModSixActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.2 |
smNwProtInfoModSixResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.6.3 |
switchNwProtCfgModSeven OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7 |
smNwProtInfoModSevenTableSwitch module 7 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModSevenEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1 |
smNwProtInfoModSevenEntrySwitch module 7 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModSevenEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1 |
smNwProtInfoModSevenIndexSwitch module 7 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.1 |
smNwProtInfoModSevenIdThe switch module 7 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.2 |
smNwProtInfoModSevenExistsIndicates whether the switch module 7 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.3 |
smNwProtInfoModSevenPowerStateIndicates whether the switch module 7 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.4 |
smNwProtInfoModSevenProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.5 |
smNwProtInfoModSevenProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.6 |
smNwProtInfoModSevenExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.7 |
smNwProtInfoModSevenIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.8 |
smNwProtInfoModSevenEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.1.1.9 |
smNwProtInfoModSevenActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.2 |
smNwProtInfoModSevenResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.7.3 |
switchNwProtCfgModEight OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8 |
smNwProtInfoModEightTableSwitch module 8 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModEightEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1 |
smNwProtInfoModEightEntrySwitch module 8 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModEightEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1 |
smNwProtInfoModEightIndexSwitch module 8 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.1 |
smNwProtInfoModEightIdThe switch module 8 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.2 |
smNwProtInfoModEightExistsIndicates whether the switch module 8 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.3 |
smNwProtInfoModEightPowerStateIndicates whether the switch module 8 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.4 |
smNwProtInfoModEightProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.5 |
smNwProtInfoModEightProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.6 |
smNwProtInfoModEightExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.7 |
smNwProtInfoModEightIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.8 |
smNwProtInfoModEightEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.1.1.9 |
smNwProtInfoModEightActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.2 |
smNwProtInfoModEightResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.8.3 |
switchNwProtCfgModNine OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9 |
smNwProtInfoModNineTableSwitch module 9 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModNineEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1 |
smNwProtInfoModNineEntrySwitch module 9 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModNineEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1 |
smNwProtInfoModNineIndexSwitch module 9 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.1 |
smNwProtInfoModNineIdThe switch module 9 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.2 |
smNwProtInfoModNineExistsIndicates whether the switch module 9 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.3 |
smNwProtInfoModNinePowerStateIndicates whether the switch module 9 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.4 |
smNwProtInfoModNineProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.5 |
smNwProtInfoModNineProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.6 |
smNwProtInfoModNineExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.7 |
smNwProtInfoModNineIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.8 |
smNwProtInfoModNineEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.1.1.9 |
smNwProtInfoModNineActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.2 |
smNwProtInfoModNineResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.9.3 |
switchNwProtCfgModTen OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10 |
smNwProtInfoModTenTableSwitch module 10 network protocol (Network Address Translation) information. SEQUENCE OF SmNwProtInfoModTenEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1 |
smNwProtInfoModTenEntrySwitch module 10 network protocol (Network Address Translation) configuration
information table entry SmNwProtInfoModTenEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1 |
smNwProtInfoModTenIndexSwitch module 10 network protocol (Network Address Translation) information index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.1 |
smNwProtInfoModTenIdThe switch module 10 numeric identifier.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.2 |
smNwProtInfoModTenExistsIndicates whether the switch module 10 exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.3 |
smNwProtInfoModTenPowerStateIndicates whether the switch module 10 is powered on or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.4 |
smNwProtInfoModTenProtNameProtocol namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.5 |
smNwProtInfoModTenProtIDProtocol IDrw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.6 |
smNwProtInfoModTenExtPortExternal portrw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.7 |
smNwProtInfoModTenIntPortInternal port.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.8 |
smNwProtInfoModTenEnableEnable or disable the protocol entry.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.1.1.9 |
smNwProtInfoModTenActivateActivate all network protocol settings for the switch module.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.2 |
smNwProtInfoModTenResetReset all network protocol settings for the switch module to default.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.3.10.3 |
switchIPv6Config OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4 |
smIPv6ConfigTableA table of IPv6 configuration options for switch modules.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.
NOTE: This MIB object is not applicable to modules that
do not support IPv6. SEQUENCE OF SmIPv6ConfigEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.1 |
smIPv6ConfigEntryIPv6 configuration options for a switch module..
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.
NOTE: This MIB object is not applicable to modules that
do not support IPv6. SmIPv6ConfigEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.1.1 |
smIPv6ConfigIndexThe switch module's slot numberro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.1.1.1 |
smIPv6ConfigEnabledEnables/Disables IPv6 support on the switch module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.1.1.2 |
smIPv6ConfigStaticEnables/Disables IPv6 static configuration support on the switch module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.1.1.3 |
smDHCPv6ConfigEnabledEnables/Disables DHCPv6 address configuration support on the switch module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.1.1.4 |
smIPv6ConfigStatelessEnabledEnables/Disables IPv6 stateless auto-configuration support on the switch module.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.1.1.5 |
smIPv6AddressTableA table of assigned IPv6 addresses for switch modules.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.
NOTE: This MIB object is not applicable to modules that
do not support IPv6. SEQUENCE OF SmIPv6AddressEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2 |
smIPv6AddressEntryThe assigned IPv6 address for a given switch module
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.
NOTE: This MIB object is not applicable to modules that
do not support IPv6. SmIPv6AddressEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2.1 |
smIPv6AddressIndexThe switch module's slot numberro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2.1.1 |
smIPv6AddressEntryIndexThe switch module's address entry indexro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2.1.2 |
smIPv6AddressTypeThe address type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2.1.3 |
smIPv6AddressThe assigned IPv6 addressro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2.1.4 |
smIPv6AddressPrefixLenThe prefix length for the given address.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2.1.5 |
smIPv6AddressDefaultRouteThe default route used for the given addressro InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.2.1.6 |
smIPv6StaticConfigTableAllows configuration of static IPv6 information for supported
IO modules.
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.
NOTE: This MIB object is not applicable to modules that
do not support IPv6. SEQUENCE OF SmIPv6StaticConfigEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.3 |
smIPv6StaticConfigEntryThe static IP address assignment information for an
IO module. Once the assignement has taken place the address
will show up as a row in the smIPv6AddressTable
NOTE: This MIB object is not applicable to modules that are running in
Stacking Mode and IP configuration is protected.
NOTE: This MIB object is not applicable to modules that
do not support IPv6. SmIPv6StaticConfigEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.3.1 |
smIPv6StaticIndexThe switch module's slot numberro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.3.1.1 |
smIPv6StaticAddressThe assigned IPv6 address.
NOTE: If changing with smIPv6StaticAddressPrefixLen and/or
smIPv6StaticAddressDefaultRoute sending the update as a
single SET command(in one PDU) will minimize the potential
downtime of the target switch.
NOTE: Sets on this object can take a few seconds. You may
need to update your SNMP timeout when modifying this setting.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.3.1.2 |
smIPv6StaticAddressPrefixLenThe prefix length for the given address.
NOTE: If changing with smIPv6StaticAddress and/or
smIPv6StaticAddressDefaultRoute sending the update as a
single SET command(in one PDU) will minimize the potential
downtime of the target switch.
NOTE: Sets on this object can take a few seconds. You may
need to update your SNMP timeout when modifying this setting.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.3.1.3 |
smIPv6StaticAddressDefaultRouteThe default route used for the given address
NOTE: If changing with smIPv6StaticAddressPrefixLen and/or
smIPv6StaticAddress sending the update as a
single SET command(in one PDU) will minimize the potential
downtime of the target switch.
NOTE: Sets on this object can take a few seconds. You may
need to update your SNMP timeout when modifying this setting.rw InetAddressIPv6 .1.3.6.1.4.1.2.3.51.2.22.3.2.1.4.3.1.4 |
switchPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2 |
switchModOnePortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1 |
smOnePortCfgTableSwitch Module 1 port configuration information.
NOTE: This option is not supported on all I/O modules. SEQUENCE OF SmOnePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1 |
smOnePortCfgEntrySwitch Module 1 port configuration information table entry SmOnePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1 |
smOnePortCfgIndexSwitch Module 1 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.1 |
smOnePortCfgLabelSwitch Module 1 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.2 |
smOnePortCfgTypeSwitch Module 1 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.3 |
smOnePortCfgLinkSettingCurrent port link setting for Switch Module 1.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.4 |
smOnePortCfgLinkStateCurrent port link state of Switch Module 1.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.5 |
smOnePortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100 Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smOnePortCfgAvailSpeeds object are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.6 |
smOnePortCfgSpeedStatusCurrent port speed of Switch Module 1.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.7 |
smOnePortCfgAvailSpeedsAvailable speed setting per port for Switch Module 1.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.8 |
smOnePortCfgMediaPort media type of Switch Module 1.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.9 |
smOnePortCfgProtocolPort protocol of Switch Module 1.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.10 |
smOnePortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 1.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.11 |
smOnePortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 1.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.12 |
smOnePortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.13 |
smOnePortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.14 |
smOnePortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.15 |
smOnePortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.1.1.1.16 |
switchModTwoPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2 |
smTwoPortCfgTableSwitch Module 2 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmTwoPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1 |
smTwoPortCfgEntrySwitch Module 2 port configuration information table entry SmTwoPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1 |
smTwoPortCfgIndexSwitch Module 2 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.1 |
smTwoPortCfgLabelSwitch Module 2 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.2 |
smTwoPortCfgTypeSwitch Module 2 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.3 |
smTwoPortCfgLinkSettingCurrent port link setting for Switch Module 2.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.4 |
smTwoPortCfgLinkStateCurrent port link state of Switch Module 2.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.5 |
smTwoPortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smTwoPortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.6 |
smTwoPortCfgSpeedStatusCurrent port speed of Switch Module 2.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.7 |
smTwoPortCfgAvailSpeedsAvailable speed setting per port for Switch Module 2.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.8 |
smTwoPortCfgMediaPort media type of Switch Module 2.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.9 |
smTwoPortCfgProtocolPort protocol of Switch Module 2.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.10 |
smTwoPortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 2.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.11 |
smTwoPortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 2.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.12 |
smTwoPortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.13 |
smTwoPortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.14 |
smTwoPortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.15 |
smTwoPortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.2.1.1.16 |
switchModThreePortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3 |
smThreePortCfgTableSwitch Module 3 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmThreePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1 |
smThreePortCfgEntrySwitch Module 3 port configuration information table entry SmThreePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1 |
smThreePortCfgIndexSwitch Module 3 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.1 |
smThreePortCfgLabelSwitch Module 3 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.2 |
smThreePortCfgTypeSwitch Module 3 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.3 |
smThreePortCfgLinkSettingCurrent port link setting for Switch Module 3.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.4 |
smThreePortCfgLinkStateCurrent port link state of Switch Module 3.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.5 |
smThreePortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smThreePortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.6 |
smThreePortCfgSpeedStatusCurrent port speed of Switch Module 3.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.7 |
smThreePortCfgAvailSpeedsAvailable speed setting per port for Switch Module 3.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.8 |
smThreePortCfgMediaPort media type of Switch Module 3.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.9 |
smThreePortCfgProtocolPort protocol of Switch Module 3.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.10 |
smThreePortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 3.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.11 |
smThreePortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 3.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.12 |
smThreePortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.13 |
smThreePortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.14 |
smThreePortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.15 |
smThreePortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.3.1.1.16 |
switchModFourPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4 |
smFourPortCfgTableSwitch Module 4 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmFourPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1 |
smFourPortCfgEntrySwitch Module 4 port configuration information table entry SmFourPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1 |
smFourPortCfgIndexSwitch Module 4 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.1 |
smFourPortCfgLabelSwitch Module 4 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.2 |
smFourPortCfgTypeSwitch Module 4 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.3 |
smFourPortCfgLinkSettingCurrent port link setting for Switch Module 4.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.4 |
smFourPortCfgLinkStateCurrent port link state of Switch Module 4.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.5 |
smFourPortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smFourPortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.6 |
smFourPortCfgSpeedStatusCurrent port speed of Switch Module 4.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.7 |
smFourPortCfgAvailSpeedsAvailable speed setting per port for Switch Module 4.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.8 |
smFourPortCfgMediaPort media type of Switch Module 4.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.9 |
smFourPortCfgProtocolPort protocol of Switch Module 4.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.10 |
smFourPortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 4.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.11 |
smFourPortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 4.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.12 |
smFourPortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.13 |
smFourPortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.14 |
smFourPortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.15 |
smFourPortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.4.1.1.16 |
switchModFivePortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5 |
smFivePortCfgTableSwitch Module 5 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmFivePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1 |
smFivePortCfgEntrySwitch Module 5 port configuration information table entry SmFivePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1 |
smFivePortCfgIndexSwitch Module 5 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.1 |
smFivePortCfgLabelSwitch Module 5 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.2 |
smFivePortCfgTypeSwitch Module 5 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.3 |
smFivePortCfgLinkSettingCurrent port link setting for Switch Module 5.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.4 |
smFivePortCfgLinkStateCurrent port link state of Switch Module 5.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.5 |
smFivePortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smFivePortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.6 |
smFivePortCfgSpeedStatusCurrent port speed of Switch Module 5.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.7 |
smFivePortCfgAvailSpeedsAvailable speed setting per port for Switch Module 5.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.8 |
smFivePortCfgMediaPort media type of Switch Module 5.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.9 |
smFivePortCfgProtocolPort protocol of Switch Module 5.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.10 |
smFivePortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 5.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.11 |
smFivePortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 5.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.12 |
smFivePortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.13 |
smFivePortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.14 |
smFivePortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.15 |
smFivePortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.5.1.1.16 |
switchModSixPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6 |
smSixPortCfgTableSwitch Module 6 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmSixPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1 |
smSixPortCfgEntrySwitch Module 6 port configuration information table entry SmSixPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1 |
smSixPortCfgIndexSwitch Module 6 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.1 |
smSixPortCfgLabelSwitch Module 6 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.2 |
smSixPortCfgTypeSwitch Module 6 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.3 |
smSixPortCfgLinkSettingCurrent port link setting for Switch Module 6.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.4 |
smSixPortCfgLinkStateCurrent port link state of Switch Module 6.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.5 |
smSixPortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smSixPortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.6 |
smSixPortCfgSpeedStatusCurrent port speed of Switch Module 6.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.7 |
smSixPortCfgAvailSpeedsAvailable speed setting per port for Switch Module 6.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.8 |
smSixPortCfgMediaPort media type of Switch Module 6.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.9 |
smSixPortCfgProtocolPort protocol of Switch Module 6.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.10 |
smSixPortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 6.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.11 |
smSixPortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 6.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.12 |
smSixPortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.13 |
smSixPortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.14 |
smSixPortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.15 |
smSixPortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.6.1.1.16 |
switchModSevenPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7 |
smSevenPortCfgTableSwitch Module 7 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmSevenPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1 |
smSevenPortCfgEntrySwitch Module 7 port configuration information table entry SmSevenPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1 |
smSevenPortCfgIndexSwitch Module 7 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.1 |
smSevenPortCfgLabelSwitch Module 7 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.2 |
smSevenPortCfgTypeSwitch Module 7 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.3 |
smSevenPortCfgLinkSettingCurrent port link setting for Switch Module 7.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.4 |
smSevenPortCfgLinkStateCurrent port link state of Switch Module 7.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.5 |
smSevenPortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smSevenPortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.6 |
smSevenPortCfgSpeedStatusCurrent port speed of Switch Module 7.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.7 |
smSevenPortCfgAvailSpeedsAvailable speed setting per port for Switch Module 7.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.8 |
smSevenPortCfgMediaPort media type of Switch Module 7.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.9 |
smSevenPortCfgProtocolPort protocol of Switch Module 7.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.10 |
smSevenPortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 7.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.11 |
smSevenPortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 7.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.12 |
smSevenPortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.13 |
smSevenPortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.14 |
smSevenPortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.15 |
smSevenPortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.7.1.1.16 |
switchModEightPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8 |
smEightPortCfgTableSwitch Module 8 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmEightPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1 |
smEightPortCfgEntrySwitch Module 8 port configuration information table entry SmEightPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1 |
smEightPortCfgIndexSwitch Module 8 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.1 |
smEightPortCfgLabelSwitch Module 8 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.2 |
smEightPortCfgTypeSwitch Module 8 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.3 |
smEightPortCfgLinkSettingCurrent port link setting for Switch Module 8.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.4 |
smEightPortCfgLinkStateCurrent port link state of Switch Module 8.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.5 |
smEightPortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smEightPortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.6 |
smEightPortCfgSpeedStatusCurrent port speed of Switch Module 8.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.7 |
smEightPortCfgAvailSpeedsAvailable speed setting per port for Switch Module 8.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.8 |
smEightPortCfgMediaPort media type of Switch Module 8.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.9 |
smEightPortCfgProtocolPort protocol of Switch Module 8.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.10 |
smEightPortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 8.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.11 |
smEightPortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 8.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.12 |
smEightPortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.13 |
smEightPortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.14 |
smEightPortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.15 |
smEightPortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.8.1.1.16 |
switchModNinePortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9 |
smNinePortCfgTableSwitch Module 9 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmNinePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1 |
smNinePortCfgEntrySwitch Module 9 port configuration information table entry SmNinePortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1 |
smNinePortCfgIndexSwitch Module 9 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.1 |
smNinePortCfgLabelSwitch Module 9 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.2 |
smNinePortCfgTypeSwitch Module 9 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.3 |
smNinePortCfgLinkSettingCurrent port link setting for Switch Module 9.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.4 |
smNinePortCfgLinkStateCurrent port link state of Switch Module 9.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.5 |
smNinePortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smNinePortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.6 |
smNinePortCfgSpeedStatusCurrent port speed of Switch Module 9.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.7 |
smNinePortCfgAvailSpeedsAvailable speed setting per port for Switch Module 9.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.8 |
smNinePortCfgMediaPort media type of Switch Module 9.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.9 |
smNinePortCfgProtocolPort protocol of Switch Module 9.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.10 |
smNinePortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 9.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.11 |
smNinePortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 9.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.12 |
smNinePortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.13 |
smNinePortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.14 |
smNinePortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.15 |
smNinePortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.9.1.1.16 |
switchModTenPortCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10 |
smTenPortCfgTableSwitch Module 10 port configuration information.
Note: This option is not supported on all I/O modules. SEQUENCE OF SmTenPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1 |
smTenPortCfgEntrySwitch Module 10 port configuration information table entry SmTenPortCfgEntry .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1 |
smTenPortCfgIndexSwitch Module 10 port sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.1 |
smTenPortCfgLabelSwitch Module 10 port labelro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.2 |
smTenPortCfgTypeSwitch Module 10 port type:
External port: This port is connected to external device and is for data traffic.
External management port: This port is solely for external management connection.
This port is not used for data traffic from remote to blades.
External dual port: This external port is used for both data traffic to blades as well as for management.
Blade port: This port is connected to the blade.
Management Module Management port: This port is connected to the Management Module.
Uplink port: This port is configured for up link functionality.
Inter-Module port: This port is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.
Inter-Module Management port: This port is connected to another I/O Module for management purpose.
The port type is either by design connected to another I/O Module, by user configured,
or by AMM setting the port type.
Inter-Module Dual port: The port is connected to another I/O Module and can be used for both data
and management purposes. The port type is either by design connected to another I/O Module,
by user configured, or by AMM setting the port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.3 |
smTenPortCfgLinkSettingCurrent port link setting for Switch Module 10.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.4 |
smTenPortCfgLinkStateCurrent port link state of Switch Module 10.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.5 |
smTenPortCfgSpeedSettingSet the port speed using the data rate and duplex value. For examples:
100mf: 100Mbps in Half Duplex;
10gf: 10 Gbps in Full Duplex;
auto: The working speed of the physical port can be tuned automatically.
NOTE: Only the speeds from smTenPortCfgAvailSpeeds are applicable to setting
this mib object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.6 |
smTenPortCfgSpeedStatusCurrent port speed of Switch Module 10.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.7 |
smTenPortCfgAvailSpeedsAvailable speed setting per port for Switch Module 10.
If there is more than one setting, the speeds are separated by a comma and then a space.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.8 |
smTenPortCfgMediaPort media type of Switch Module 10.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.9 |
smTenPortCfgProtocolPort protocol of Switch Module 10.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.10 |
smTenPortCfgWidthThe width of the port in terms of how many combined cables are present for Switch Module 10.
A value of 0 indicates this field is not applicable to the switch ports.
This data is also known as the lane count.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.11 |
smTenPortCfgCableLengthThe length (in meters) of the cable supported by this port for Switch Module 10.
A value of 0 indicates this field is not applicable to the switch ports.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.12 |
smTenPortCfgCableTypeExternal cable type for this port, for example, active copper or passive fiber.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.13 |
smTenPortCfgVendorNameThe cable manufacturer.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.14 |
smTenPortCfgCompatibilityCompatibility of the external cable that is plugged into the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.15 |
smTenPortCfgDataRateData rate supported for this port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.2.2.10.1.1.16 |
raidControllerConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.3 |
raidControllerTableRAID Controller control table. SEQUENCE OF RaidControllerEntry .1.3.6.1.4.1.2.3.51.2.22.3.3.1 |
raidControllerEntryRAID Controller control table entry. RaidControllerEntry .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1 |
raidControllerIndexRAID Controller control table index.
This MIB object is for SAS Controller Modules only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1.1 |
raidControllerIdThe I/O Module numeric identifier for the SAS Controller Module.
This MIB object is for SAS Controller Modules only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1.2 |
raidControllerExistsIndicates whether the I/O Module specified for the RAID Controller
exists or not.
This MIB object is for SAS Controller Modules only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1.3 |
raidControllerPowerStateIndicates whether the I/O Module is powered on or not.
This MIB object is for SAS Controller Modules only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1.4 |
raidControllerMACAddressThe MAC address for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1.5 |
raidControllerSasIDThe hardware VPD SAS ID for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1.6 |
raidControllerPingRequestSends a ping to the current IP address of the RAID Controller network interface.
This MIB object can not be set, if AMM grants I/O Module the Protected Mode
permission and the module goes into Protected Mode.
NOTE: Value returned for the GET command is meaningless for this MIB object
This MIB object is for SAS Controller Modules only.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.3.1.1.7 |
raidControllerNetworkCfg OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.3.3.2 |
rcCurrentIPInfoTableRAID Controller current IP table.
This MIB object is for SAS Controller Modules only. SEQUENCE OF RcCurrentIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1 |
rcCurrentIPInfoEntryRAID Controller current IP table entry.
This MIB object is for SAS Controller Modules only. RcCurrentIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1 |
rcCurrentIPInfoIndexRAID Controller current IP table index.
This MIB object is for SAS Controller Modules only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.1 |
rcCurrentIPInfoIdThe I/O Module numeric identifier for the RAID Controller.
This MIB object is for SAS Controller Modules only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.2 |
rcCurrentIPInfoExistsIndicates whether the I/O Module exists or not.
This MIB object is for SAS Controller Modules only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.3 |
rcCurrentIPInfoPowerStateIndicates whether the I/O Module is powered on or not.
This MIB object is for SAS Controller Modules only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.4 |
rcCurrentIPAddrThe current IP address for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.5 |
rcCurrentSubnetMaskThe current subnet mask for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.6 |
rcCurrentGatewayThe current subnet mask for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only.ro IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.7 |
rcCurrentIPConfigMethodThe current IP gateway for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.8 |
rcCurrentRaidedVlanIdThe current virtual LAN ID for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.3.2.1.1.9 |
rcNewIPInfoTableRAID Controller new IP configuration table.
This MIB object is for SAS Controller Modules only.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode. SEQUENCE OF RcNewIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2 |
rcNewIPInfoEntryRAID Controller new IP configuration information table entry.
This MIB object is for SAS Controller Modules only.
NOTE: This MIB table is not applicable to modules that are running in Network Address
Translation (NAT) Mode. RcNewIPInfoEntry .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1 |
rcNewIPInfoIndexRAID Controller new IP configuration information index.
This MIB object is for SAS Controller Modules only.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.1 |
rcNewIPInfoIdThe I/O Module numeric identifier for the RAID Controller.
This MIB object is for SAS Controller Modules only.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.2 |
rcNewIPInfoExistsIndicates whether the I/O Module exists or not.
This MIB object is for SAS Controller Modules only.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.3 |
rcNewIPInfoPowerStateIndicates whether the I/O Module is powered on or not.
This MIB object is for SAS Controller Modules only.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.4 |
rcNewIPAddrThe new IP address for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only. Before setting this object to a new value,
rcNewIpconfigEnableDisable object must first be set to disabled.
NOTE: This MIB object can not be set if the AMM grants the I/O Module Protected Mode
permission and the module goes into Protected Mode.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.5 |
rcNewSubnetMaskThe new subnet mask for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only. Before setting this object to a new value,
rcNewIpconfigEnableDisable object must first be set to disabled.
NOTE: This MIB object can not be set if the AMM grants the I/O Module Protected Mode
permission and the module goes into Protected Mode.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.6 |
rcNewGatewayThe new IP gateway for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only. Before setting this object to a new value,
rcNewIpconfigEnableDisable object must first be set to disabled.
NOTE: This MIB object can not be set if the AMM grants the I/O Module Protected Mode
permission and the module goes into Protected Mode.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw IpAddress .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.7 |
rcNewIPConfigMethodThe new IP configuration method for the RAID Controller network interface.
This MIB object is for SAS Controller Modules only. Before setting this object to a new value,
rcNewIpconfigEnableDisable object must first be set to disabled.
NOTE: The value 'DHCP' can not be used to set.
NOTE: This MIB object can not be set if the AMM grants the I/O Module Protected Mode
permission and the module goes into Protected Mode.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.8 |
rcNewIPConfigEnableDisableA set command enables new IP configurations that have been defined.
A get command indicates whether new IP configurations that have been enabled.
NOTE: This MIB object can not be set if the AMM grants the I/O Module Protected Mode
permission and the module goes into Protected Mode.
NOTE: This MIB object is not applicable to modules that are running in Network Address
Translation (NAT) Mode.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.3.3.2.2.1.11 |
chassisTopology OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.4 |
chassisResponseVersionChassis response version.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.1 |
chassisFlagsChassis flags.
1 = a server blade chassis, 0 = a rack or standalone chassis.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.4.2 |
chassisNameThe name of the active MM as a null terminated string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.3 |
chassisNoOfFPsSupportedNumber of fan packs (FPs) supported.
NOTE: Fan packs are also referred to as Power Module Cooling Devices.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.18 |
chassisNoOfPBsSupportedNumber of processor blades (PBs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.19 |
chassisNoOfSMsSupportedNumber of switch modules (SMs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.20 |
chassisNoOfMMsSupportedNumber of management modules (MMs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.21 |
chassisNoOfPMsSupportedNumber of power modules (PMs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.22 |
chassisNoOfMTsSupportedNumber of media trays (MTs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.23 |
chassisNoOfBlowersSupportedNumber of blowers supported.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.24 |
chassisPBsInstalledThe 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.22.4.25 |
chassisSMsInstalledThe 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' for BladeCenter and
BladeCenter T and '1011000000' for BladeCenter H and BladeCenter HT.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.29 |
chassisMMsInstalledThe management modules that are installed on the chassis.
The management 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 management modules supported. If a management 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 a management module
is installed in bay 1, and 2 management modules are supported, the
string would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.30 |
chassisPMsInstalledThe 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.22.4.31 |
chassisMTInstalledIndicates whether at least one media tray (MT) is installed.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.4.32 |
chassisBlowersInstalledThe blowers that are installed on the chassis.
The blowers 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 blowers supported. If a blower 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 a blower
is installed in bay 1, and 2 blowers are supported, the string
would look like '10'.
NOTE: Blowers are also referred to as Chassis Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.33 |
chassisActiveMMThe active management module (MM).ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.34 |
chassisKVMOwnerThe blade that currently owns the keyboard/video/monitor (KVM).
0 = the KVM devices are owned by the management module.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.35 |
chassisMediaTrayOwnerThe blade that currently owns the media tray.
0 = the media tray is owned by the management module.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.36 |
chassisFPsInstalledThe fan packs that are installed on the chassis.
The fan packs 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 fan packs supported. If a fan pack 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 fan packs are installed in bays 1 and 3, and 4 fan packs
are supported, the string would look like '1010'.
NOTE: Fan packs are also referred to as Power Module Cooling Devices.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.37 |
chassisTypeThe type of the chassis. The BladeCenterS chassis and BladeCenterE are part of the
bladeCenterOrBladeCenterH type. This MIB object should be used in conjunction
with chassisSubType MIB object to determine the characteristic of the chassis.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.4.38 |
chassisSubtypeThe subtype of the chassis. This MIB object should be used in conjunction with
chassisType MIB object to determine the characteristic of the chassis.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.4.39 |
chassisNoOfFBsSupportedNumber of Front Bezel (FBs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.40 |
chassisNoOfAPsSupportedNumber of Alarm Panel (APs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.41 |
chassisNoOfNCsSupportedNumber of Network Clocks (NCs) supported.rodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.42 |
chassisNoOfMXsSupportedNumber of Multiplexer Expansion modules (MXs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.43 |
chassisNoOfMMIsSupportedNumber of management module interposers (MMIs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.44 |
chassisNoOfSMIsSupportedNumber of switch module interposers (SMIs) supported.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.4.45 |
chassisNoOfFBsInstalledThe return value of '1'indicates the front bezel is installed on the chassis.
The value of '0' indicates the front bezel is not installed.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.46 |
chassisNoOfAPsInstalledThe return value of '1'indicates the alarm panel is installed on the chassis.
The value of '0' indicates the alarm panel is not installed.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.47 |
chassisNoOfNCsInstalledThe network clock cards that are installed on the chassis.
The network clock cards 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 network clock cards supported. If a network clock
card 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 a network clock card is installed in bays 1, and 2 network clock cards
are supported, the string would look like '10'.rodeprecated OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.48 |
chassisNoOfMXsInstalledThe Multiplexer Expansion Modules that are installed on the chassis.
The Multiplexer Expansion 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
Multiplexer Expansion Modules supported. If a Multiplexer Expansion 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 Multiplexer Expansion Module is installed in bays 1, and 2 Multiplexer
Expansion Modules are supported, the string would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.49 |
chassisNoOfMMIsInstalledThe flex cables that are installed on the chassis.
The flex cables 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 flex cables supported. If a flex cable
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 flex cable is installed in bays 1, and 2 flex cables are
supported, the string would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.50 |
chassisNoOfSMIsInstalledThe interposers that are installed on the chassis.
The interposers 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 interposers supported. If an interposer
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 interposer is installed in bays 1, and 10 interposers are
supported, the string would look like '1000000000'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.51 |
chassisNoOfMTsInstalledThe media trays that are installed on the chassis.
The media trays 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 media trays supported. If a media tray 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 media trays are installed in bays 1, and 2 media trays are,
the string would look like '10'.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.4.52 |
managementModule OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.5 |
mmStatusTableTable of the management module status.
For consistent results, view as a table and not as individual entries. SEQUENCE OF MmStatusEntry .1.3.6.1.4.1.2.3.51.2.22.5.1 |
mmStatusEntryManagement module status entry.
For consistent results, view as a table and not as individual entries. MmStatusEntry .1.3.6.1.4.1.2.3.51.2.22.5.1.1 |
mmStatusIndexManagement module status index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.5.1.1.1 |
mmPresentManagement module current status.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.5.1.1.2 |
mmExtIpAddressManagement module external IP address.
NOTE: The IPv6 addresses assigned to the AMM may be viewed
with the extEthernetInterfaceIPv6 objectsro IpAddress .1.3.6.1.4.1.2.3.51.2.22.5.1.1.3 |
mmPrimaryIndicates if this Management module is a primary or not.
NOTE: If there is no standby MM, this value defaults to primary.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.5.1.1.4 |
mmHealthStateThe health state for the management module.
0 = unknown, 1 = good, 2 = warning, 3 = bad.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.5.1.1.5 |
storage OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.6 |
storageStatus OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.6.1 |
storageStatusTableTable of the storage module status.
For consistent results, view as a table and not as individual entries.
NOTE: This MIB object is for BCS only. SEQUENCE OF StorageStatusEntry .1.3.6.1.4.1.2.3.51.2.22.6.1.1 |
storageStatusEntryStorage Module Status Table Entry. StorageStatusEntry .1.3.6.1.4.1.2.3.51.2.22.6.1.1.1 |
storageStatusIndexStorage device status table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.1.1.1.1 |
storageBayNumberBay number of the Storage device.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.6.1.1.1.2 |
storageStateStorage device state.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.6.1.1.1.3 |
storageNameThe name of the storage device.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.6.1.1.1.4 |
storageConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.6.2 |
storageSwitchConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.6.2.1 |
storageSwitchZoneCfgTableTable of all the zone configurations stored on switch
modules. For consistent results, view as a table and
not as individual entries.
Before activating a new zone configuration via the switchActiveZoneCfg
object, a user must consider the following:
1) Changing the zone configuration may cause disruption in the storage
access of blades connected to this SAS Module. It is highly recommended
that you first ensure that the blades have completed all storage accesses.
You may want to shutdown the blade OS prior to changing your zone configuration.
2) When selecting a zone configuration, ensure that it is appropriate
for the number of SAS switches installed in your chassis. This can
be determined from the switchZoneCfgDescription text.
3) When selecting a zone configuration, ensure that it exists first on
all SAS switches. This can be determined by querying the
storageSwitchZoneCfgTable. In addition, for user-defined zone
configurations, even if the number is the same, ensure that the
actual zone configurations are identical or compatible. You will need
to use an application, such as the Switch Configuration Manager (SCM)
to verify this.
4) All SAS switches must be in operational state prior to activating a
new zone configuration. This can be determined by querying the
activeZoneCfgNumberBySwitch object and ensuring that none of the
2xx codes are returned. SEQUENCE OF StorageSwitchZoneCfgEntry .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1 |
storageSwitchZoneCfgEntrySwitch Module Zone Configuration Management Entry. StorageSwitchZoneCfgEntry .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1 |
switchZoneCfgIndexSwitch module zone configuration table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.1 |
switchZoneCfgBayNumberThe numeric switch bay number.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.2 |
switchZoneCfgNumberThe zone configuration number, also referred to as the
configuration store number.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.3 |
switchZoneCfgStatusThe status of the zone configuration.
Only one configuration is 'Active', others are in 'nonActive'
status.
When a zone configuration is active on a switch, the status
may temporarily indicate pending(2) as it transitions from
nonActive(0) to active (1).ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.4 |
switchZoneCfgTypeThe type of the zone configuration. Predefined are read-only
static configurations, and userdefined are read-write
configurations that can be created and modified using the
Switch Configuration Manager application.ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.5 |
switchZoneCfgNameA short descriptive name for the zone configuration.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.6 |
switchZoneCfgDescriptionA detailed description for the zone configuration.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.7 |
switchZoneCfgDateThe date the zone configuration was created.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.8 |
switchActiveZoneCfgAn object used to activate a particular zone configuration.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.6.2.1.1.1.9 |
storageSwitchActiveZoneCfgTableTable showing the zone configuration that is currently
active on a given switch module. For consistent results,
view as a table and not as individual entries. SEQUENCE OF StorageSwitchActiveZoneCfgEntry .1.3.6.1.4.1.2.3.51.2.22.6.2.1.2 |
storageSwitchActiveZoneCfgEntryActive zone configurations Entry. StorageSwitchActiveZoneCfgEntry .1.3.6.1.4.1.2.3.51.2.22.6.2.1.2.1 |
activeZoneCfgIndexActive zone configurations table index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.2.1.2.1.1 |
activeZoneCfgBayNumberBay number of the switch module where active zone configurations exist.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.6.2.1.2.1.2 |
activeZoneCfgNumberBySwitchThe zone configuration number active on this SAS switch module
as reported by the switch module. If this number differs from the
value of the activeZoneCfgNumberByMM object for the same
switch, this may indicate a configuration problem.
The zone configuration number is also referred to as the zone
configuration store.
NOTE:
0 = No zone configuration is active on this I/O Module.
253 = I/O module is discovering zone information.
254 = I/O Module is not powered on or in a fault state.
255 = notApplicable.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.2.1.2.1.3 |
activeZoneCfgNumberByMMThe zone configuration number active on this SAS switch module
as known by the management module. If this number differs from the
value of the activeZoneCfgNumberBySwitch object for the same
switch, this may indicate a configuration problem.
The zone configuration number is also referred to as the zone
configuration store.
NOTE:
0 = No zone configuration is active on this I/O Module.
255 = notApplicable.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.2.1.2.1.4 |
switchZoneCfgActivationThis object provides a quick means of activating a valid zone
configuration on all active SAS switches. The zone configuration
to be activated is specified as the value of the SET and can be
obtained from the switchZoneCfgNumber object.
The zone configuration number is also referred to as the zone
configuration store.
Before activating a new zone configuration, a user must consider
the following:
1) Changing the zone configuration may cause disruption in the storage
access of blades connected to this SAS Module. It is highly recommended
that you first ensure that the blades have completed all storage accesses.
You may want to shutdown the blade OS prior to changing your zone configuration.
2) When selecting a zone configuration, ensure that it is appropriate
for the number of SAS switches installed in your chassis. This can
be determined from the switchZoneCfgDescription text.
3) When selecting a zone configuration, ensure that it exists first on
all SAS switches. This can be determined by querying the
storageSwitchZoneCfgTable. In addition, for user-defined zone
configurations, even if the number is the same, ensure that the
actual zone configurations are identical or compatible. You will need
to use an application, such as the Switch Configuration Manager (SCM)
to verify this.
4) All SAS switches must be in operational state prior to activating a
new zone configuration. This can be determined by querying the
activeZoneCfgNumberBySwitch object and ensuring that none of the
2xx codes are returned.
NOTE: Value returned for the GET command is meaningless
for this MIB object.
If any of the switches are not activated, an error response
will be returned.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.6.2.1.3 |
firmwareInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.8 |
smFirmwareInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.8.1 |
smFirmwareInfoTableSwitch Module firmware image information.
This table is only applicable to modules that support multiple images SEQUENCE OF SmFirmwareInfoEntry .1.3.6.1.4.1.2.3.51.2.22.8.1.1 |
smFirmwareInfoEntrySwitch Module firmware image information table entry SmFirmwareInfoEntry .1.3.6.1.4.1.2.3.51.2.22.8.1.1.1 |
smFirmwareInfoIndexSequence index in the firmware table.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.8.1.1.1.1 |
smFirmwareInfoModIndexSwitch Module number.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.8.1.1.1.2 |
smFirmwareInfoImageIndexSwitch Module firmware image index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.8.1.1.1.3 |
smFirmwareInfoImageNameSwitch Module firmware image namerw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.8.1.1.1.4 |
firmwareUpdate OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.9 |
firmwareUpdateTargetTarget module whose firmware will be updated.
NOTE: Some switch modules do not allow firmware update.
When firmware update is attempted on those switch modules,
the agent will report an error.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.9.1 |
firmwareUpdateTftpServerIf flashing via the legacy method using a tftp server, then
set the IP address or host name of the TFTP server where
the firmware file resides. The address must be entered in a
dotted decimal IP string (e.g. 9.37.44.2).
NOTE: IPv6 numeric addresses must be enclosed with brackets
(e.g. [fe80::5652:ff:fe50:53b6]).rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.9.2 |
firmwareUpdateFileNameFile name of the firmware file.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.9.3 |
firmwareUpdateStartStart updating the firmware of the specified target module.
Using execute or execute-with-reboot will cause the SNMP client to
wait for the firmware update to complete.
Using execute-nowait or execute-with-reboot-nowait will not cause
the SNMP client to wait for the update to complete. Instead it will
flash the firmware in the background.
Note 1: If the execute-with-reboot or execute-with-reboot-nowait
option is selected, the target will reset after a successful flash.
This option is only valid if the firmwareUpdateTarget object is
set to managementModule.
Note 2: If flashing from a remote file, then both
firmwareUpdateServer and firmwareUpdateFileName must be
set. Otherwise if flashing via the legacy method using a tftp
server, then both firmwareUpdateTftpServer and
firmwareUpdateFileName must be set.
Note 3: Depending on the target, it might take up to several
minutes for the flash update to complete. Do not reset the
target until the control has been returned. At this point,
the results will be displayed.
Note 4: Use firmwareUpdateStatus to confirm the status of
the last firmware update initiated by SNMP method. The
Management Module must be restarted for the new firmware to
take affect.
Note 5: If data encryption is currently enabled on this MM,
and you update the MM firmware to a level which does not
support data encryption, you will lose all your configuration
settings as a result.
Note 6: Since some I/O Module types use the AMM TFTP server for
firmware file transfer during the firmware update process, the
tftpEnable MIB object must be set to enable prior to updating
the firmware for these modules.
Note 7: If IPv6 address(es) have been configured for one or more
interfaces/protocols/services on this AMM, when you update
the firmware to a level which does not support IPv6, all IPv6
connectivity will be lost, and services/interfaces for which an IPv6
address was configured may not function properly. You will be required
to reconfigure these services/interfaces.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.9.4 |
firmwareUpdateStatusGet the status of the last firmware update which was
initiated through SNMP method.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.9.5 |
standbyFirmwareUpdateStatusGet the current status of the firmware update for the standby AMM.
NOTE: This only applies to systems with a standby AMM.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.9.6 |
firmwareImageNumberIf the module can upload more than one image, an image
number must be specified after setting the firmware target.
Please refer to the firmwareInformation section.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.9.7 |
firmwareActiveImageIf the module can upload more than one image, an active image
number must be specified. Please refer to the firmwareInformation section.
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw INTEGER .1.3.6.1.4.1.2.3.51.2.22.9.8 |
firmwareUpdateServerContains the fully qualified remote location of the firmware
packet file. Use firmwareUpdateFileName to specify the filename.
A fully qualified remote location contains a supported
protocol followed by a colon and two slashes (//), userid and
password separated by a colon for login authentication, an
@ sign, followed by the hostname or IP address of the
server where the packet file resides, followed by an optional
port number to the hostname, and the full pathname to the file.
Note that if the port number is specified, it must be
separated with the hostname (or IP address) by a colon.
The AMM currently supports the following protocols:
TFTP, FTP, FTPS, HTTP and HTTPS.
The complete format of a fully qualified remote location is:
<protocol>://<userid:password>@<hostname:port>/<pathname>
An example of a fully qualified remote location can be:
ftp://USERID:PASSW0RD@192.168.0.2:30045/tmp
where the ftp protocol will be used for transferring the file in
this location, username is USERID, password is
PASSW0RD, host IP address is 192.168.0.2, port number is
30045, and the full pathname for the packet file is /tmp.
and firmwareUpdateFileName is set to: CNETCMUS.pkt
Some protocols do not need the username, password, and
the port number, so the minimum requirement for a fully
qualified location can be: <protocol>://<hostname>/<pathname>.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.9.9 |
remoteChassis OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.10 |
remoteChassisTableTable of remote chassis information. SEQUENCE OF RemoteChassisEntry .1.3.6.1.4.1.2.3.51.2.22.10.1 |
remoteChassisEntryRemote chassis entry RemoteChassisEntry .1.3.6.1.4.1.2.3.51.2.22.10.1.1 |
remoteChassisIndexRemote chassis discovery sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.10.1.1.1 |
systemNameSystem name for this discovery management module.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.2 |
systemStatusSystem status summary (chassis).ro Enumeration .1.3.6.1.4.1.2.3.51.2.22.10.1.1.3 |
mmTypeService processor type.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.4 |
mmSerialManagement module serial number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.5 |
mmFruManagement module Field-Replaceable number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.6 |
mmIpThe IPv4 compliant address of the management module.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.7 |
chassisSerialChassis serial number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.8 |
chassisFruChassis Field-Replaceable number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.9 |
chassisMachineTypeModeChassis machine type and model number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.10 |
chassisUuidChassis unique identifier.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.11 |
firmwareVersionFirmware version of the discovery management module.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.12 |
ipStatusA flag to state if IPv4 and IPv6 are enabledro Enumeration .1.3.6.1.4.1.2.3.51.2.22.10.1.1.13 |
ipv6AddressesThe IPv6 addresses configured for the chassis.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.10.1.1.14 |
chassisDiscoveryDiscovery of remote Chassis.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.22.10.2 |
fileManagement OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.11 |
fileTopology OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.22.11.1 |
currentDirectorySpecifies the directory name for listing the requested files.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.11.1.1 |
fileDetailsTableA table of all the files in the specified directory.
For consistent results, view as a table and not as individual entries. SEQUENCE OF FileDetailsEntry .1.3.6.1.4.1.2.3.51.2.22.11.1.2 |
fileDetailsEntryFile details entry.
For consistent results, view as a table and not as individual entries. FileDetailsEntry .1.3.6.1.4.1.2.3.51.2.22.11.1.2.1 |
fileIndexFile sequence index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.22.11.1.2.1.1 |
fileNameFile name.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.11.1.2.1.2 |
fileLastUpdateDate of the latest file update.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.11.1.2.1.3 |
fileSizeFile size in bytes.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.11.1.2.1.4 |
fileManagementCmdThis field will execute the selected operations on the files.
The following operation is supported:
DEL name - delete a file
Examples:
- to delete the file named switch.config in tftproot directory
set the value to 'DEL tftproot/switch.config'
NOTE: Value returned for the GET command is meaningless for this
MIB object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.11.3 |
fileSystemSpaceAvailableThis field displays the available space of the AMM file system.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.22.11.6 |
service OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23 |
serviceConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.1 |
debugEnableDisable/Enable AMM debugging with USB key by service personnel.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.1.3 |
bladeServiceData OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.3 |
bladeServiceDataTableTable of blade service data information. SEQUENCE OF BladeServiceDataEntry .1.3.6.1.4.1.2.3.51.2.23.3.1 |
bladeServiceDataEntryBlade service data entry BladeServiceDataEntry .1.3.6.1.4.1.2.3.51.2.23.3.1.1 |
serviceDataIndexBlade service date index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.23.3.1.1.1 |
serviceDataBladeIdThe numeric blade ID.ro Enumeration .1.3.6.1.4.1.2.3.51.2.23.3.1.1.2 |
serviceDataBladeExistsIndicates whether the blade specified exists or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.23.3.1.1.3 |
serviceDataBladePowerStateIndicates whether the blade specified is powered on or not.
If the AMM is experiencing a communication problem with the blade,
the state may be returned as unknown(255)ro Enumeration .1.3.6.1.4.1.2.3.51.2.23.3.1.1.4 |
serviceDataBladeNameThe name of the blade as a string.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.1.1.5 |
serviceDataBladeCapabilityIndicates whether the blade has the capability to trigger service data.
NOTE: This Mib object is deprecated and no longer supported.
Please see serviceDataBladeCapabilityMask OIDrodeprecated INTEGER .1.3.6.1.4.1.2.3.51.2.23.3.1.1.6 |
serviceDataDumpInitiateInitiates a type of dump collection to be initiated for the blade.
NOTE: Not all blades support this, please check serviceDataDumpCapabilityMask
OID to see if the action is supported on this blade. Only one file can be moved
to the'/service' directory at a time, please look over fileManagement OID
to check if the file has been compeleted.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.3.1.1.7 |
serviceDataDumpRetrieveRetrieve a type of service data file from blade to AMM.
NOTE: This OID only is valid for the last four bit mask designations listed
in the serviceDataDumpCapabilityMask OID. Only one file can be moved to
the '/service' directory at a time, please look over fileManagement OID
to check if the file has been compeleted.
NOTE: Value returned for the GET command is meaningless
for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.3.1.1.8 |
serviceDataDumpCapabilityMaskIndicates whether the blade has the capability to trigger service data and if so,
which operations are supported and whether the file can be transferred to the AMM
from the blade.
The values and meanings are as follows:
0000 0000 means this blade does not support any at all.
0000 0001 means this blade supports 'processor' type and the file remains on the blade.
0000 0010 means this blade supports 'platform' type and the file remains on the blade
0000 0100 means this blade supports 'partition' type and the file remians on the blade
0000 1000 means this blade supports 'processor' type and the file can be transferred to the AMM.
0001 0000 means this blade supports 'platform' type and the file can be transferred to the AMM.
0010 0000 means this blade supports 'partition' type and the file can be transferred to the AMM
0100 0000 means this blade supports 'serviceData' type and the file can be transferred to the AMM
For example, the returned value of 01111000 means this blade supports 'processor','platform',
'partition' and 'serviceData' types, and the file can be transferred to the AMMro OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.1.1.9 |
serviceDataDumpInProgressAn indicator as to whether a blade dump is in progress for the specified blade.
This object ONLY applies to dumps that can be triggered by the AMM and where the
dump file is transferred to the AMM filesystem upon completion. See the
serviceDataDumpCapabilityMask object for support levels. The flag that this MIB object
represents will be set on when the IPMI command is sent to the blade indicating 'init dump'
and will be cleared upon receiving the valid dump file from the blade or the
creation of the text file indicating the problem encountered.ro Enumeration .1.3.6.1.4.1.2.3.51.2.23.3.1.1.10 |
bladeSystemReferenceCodes OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.3.3 |
bladeSysRefCodesTableTable of blade system reference codes. SEQUENCE OF BladeSysRefCodesEntry .1.3.6.1.4.1.2.3.51.2.23.3.3.1 |
bladeSysRefCodesEntryBoot sequence entry BladeSysRefCodesEntry .1.3.6.1.4.1.2.3.51.2.23.3.3.1.1 |
sysRefCodeIndexSystem reference codes index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.23.3.3.1.1.1 |
sysRefCodeBayNumberThe bay number of the blade which has the system reference code.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.3.1.1.2 |
sysRefCodeSequenceIndicates whether the blade specified exists or not.ro INTEGER .1.3.6.1.4.1.2.3.51.2.23.3.3.1.1.3 |
sysRefCodeUnique ID and system reference code for the blade.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.3.1.1.4 |
sysRefCodeTimestampTimestamp of system reference code for the blade.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.3.1.1.5 |
bladeSysRefCodesDetailsTableTable of details of blade system reference codes. SEQUENCE OF BladeSysRefCodesDetailsEntry .1.3.6.1.4.1.2.3.51.2.23.3.3.2 |
bladeSysRefCodesDetailsEntryBoot sequence entry BladeSysRefCodesDetailsEntry .1.3.6.1.4.1.2.3.51.2.23.3.3.2.1 |
sysRefCodeDetailIndexSystem reference codes index.ro INTEGER .1.3.6.1.4.1.2.3.51.2.23.3.3.2.1.1 |
sysRefCodeDetailBayNumberThe bay number of the blade which has the details
of system reference code.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.3.2.1.2 |
sysRefCodeDetailSRCSequenceA sequence of the system reference codes for the blade.ro INTEGER .1.3.6.1.4.1.2.3.51.2.23.3.3.2.1.3 |
sysRefCodeDetailSequenceA sequence of the detailed information of the system reference
codes for the blade.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.3.2.1.4 |
sysRefCodeDetailDataStringDetailed information of the system reference codes for the blade.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.3.3.2.1.5 |
serviceAdvisor OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.4 |
autoCallHomeSetup OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.4.1 |
acceptLicenseAgreementAccept Terms and Conditions of AMM Service Advisor. The user will have to accept the terms and conditions
before Service Advisor can send diagnostic data to IBM support personnel. If AMM configuration
is reset to defaults, the user will have to accept the terms and conditions again before they can
enable Service Advisor. For more information, please refer to the IBM BladeCenter User's Guide.
A GET of this object may return disabled(0) or enabled(1), depending upon the current state. However,
only enabled(1) is accepted on a SET in order to accept the license agreement. A SET of disabled(0)
will return noSuchValue and is not allowed.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.4.1.1 |
serviceAdvisorEnableDisable/Enable IBM Support. The User Agreement must be accepted and the contact information
must be set before the IBM Support function of Service Advisor can be enabled.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.4.1.2 |
serviceSupportCenter OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.4.2 |
ibmSupportCenterThe country code for the IBM Support Center. 2 character ISO country code.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.2.1 |
contactInformation OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.4.3 |
companyNameThe organization/company name of the contact person. 1-30 characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.1 |
contactNameThe name of the contact person.1-30 characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.2 |
phoneNumberThe phone of the contact person. 5-30 characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.3 |
emailAddressThe email of the contact person. It must contain '@' and dot '.' in form userid@hostname (30 characters maximum).
The userid can be alphanumeric characters, '.', '-', or '_' but must begin and end with alphanumeric characters.
The hostname can be alphanumeric characters, '.', '-', or '_'. It must contain at least two domain items.
Every domain item should begin and end with alphanumeric character, and the last domain item should be 2-20 alphabetic characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.4 |
addressThe address of the machine location. The information in this field should be of sufficient detail to allow someone to
quickly find the chassis when necessary. 1-30 characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.5 |
cityThe city of the machine location. 1-30 characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.6 |
stateThe state of the machine location. 2-3 characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.7 |
postalCodeThe postal code of the location for this system. 1-9 characters, only alphanumeric characters are valid.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.3.8 |
httpProxyConfig OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.4.4 |
httpProxyEnableDisable/Enable of the HTTP Proxy. Select Enable to use the proxy for call home
connections from the AMM to IBM. HTTP Proxy is used by the AMM when it is not connected to the internet directly.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.4.4.1 |
httpProxyLocationFully qualified host name or IP address of the HTTP Proxy. Maximum of 63 characters.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.4.2 |
httpProxyPortThe port number of the HTTP Proxy. An integer value from 1 to 65535.rw INTEGER .1.3.6.1.4.1.2.3.51.2.23.4.4.3 |
httpProxyUserNameUser Name of the HTTP Proxy. A maximum of 30 characters string without spaces.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.4.4 |
httpProxyPasswordPassword of the HTTP Proxy. A maximum of 15 characters string without spaces.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.4.5 |
activityLogs OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.4.5 |
activityLogTableTable of Service Advisor Activity Log entries information. This table displays the last five
events that were generated by the system or user that are called home. The entries are displayed in
reverse chronological order (most recent call home entry first). For any events that happen with same
Date/Time, only one event will be called home. If a call home event that is already in the activity
log is triggered again on the same event source, it will not be called home again unless the prior entry has
been acknowledged as corrected or 120 hours (5 days) have passed since it initially occurred and was called home. SEQUENCE OF ActivityLogEntry .1.3.6.1.4.1.2.3.51.2.23.4.5.1 |
activityLogEntryActivity Log table entry. Each entry has the result of the call-home attempt,
the service number assigned for the issue by IBM support, the event ID, event source, date and
time that event occured, and a text message. ActivityLogEntry .1.3.6.1.4.1.2.3.51.2.23.4.5.1.1 |
activityLogIndexThe Activity Log index number.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.1 |
activityLogStringA string of data detailing one Activity Log entry. The text message is from the original entry in the event log.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.2 |
activityLogAcknowledgeThe acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to
certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed
from the log or close the ticket at IBM support. This log is not cleared, so the acknowledge flag can be used to indicate a problem
can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via IBM Support or FTP/TFTP Server
of Service Data.
For consistent results, view as a table and not as individual entries.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.3 |
activityLogAttributeA string of data detailing one Activity Log entry's attribute. It contains states of both calling IBM support and FTP/TFTP Server.
A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state
indicates that the problem was successfully transmitted to IBM support or FTP/TFTP Server. A DISABLED state indicates that Service Advisor
has disabled calling IBM Support or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable
event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt
to transmit the event information was not successful. Additional information may be found in the Event Log.
The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine
when contacting IBM support. The event ID, event source, date and time are all information from the original entry in the event log.
The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.4 |
autoFTPSetup OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.5 |
autoFTPCallModeThis field specifies the automated problem reporting mode. Automated problem reporting mode allows the AMM to automatically put
service data to a specified server when a call home event is detected. For any call home events that happen with same Date/Time,
only one event will be reported. The system will also wait for an interval of 120 hours (5 days) before another identical event
can be sent for the same failed component.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.5.1 |
autoFTPCallAddrThis field specifies the remote server address of FTP and TFTP. It should be fully qualified hostname or IP address.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.5.2 |
autoFTPCallPortThis field specifies the port on remote FTP/TFTP server for data transmission.rw INTEGER .1.3.6.1.4.1.2.3.51.2.23.5.3 |
autoFTPCallUserIDThis field specifies the user account to login remote FTP server.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.5.4 |
autoFTPCallPasswordThis field specifies the password to login remote FTP server.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.5.5 |
callHomeExclusionEvents OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.23.6 |
readCallHomeExclusionEventTableTable of Call Home Exclusion Event entries information. SEQUENCE OF ReadCallHomeExclusionEventEntry .1.3.6.1.4.1.2.3.51.2.23.6.1 |
readCallHomeExclusionEventEntryCall Home Exclusion Event table entry ReadCallHomeExclusionEventEntry .1.3.6.1.4.1.2.3.51.2.23.6.1.1 |
readCallHomeExclusionEventIndexThe index number of one Call Home Exclusion Event.
For consistent results, view as a table and not as individual entries.ro INTEGER .1.3.6.1.4.1.2.3.51.2.23.6.1.1.1 |
readCallHomeExclusionEventIDThe Event ID of one Call Home Exclusion Event entry.
For consistent results, view as a table and not as individual entries.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.6.1.1.2 |
addCallHomeExclusionEventAdd one call home Event ID into the Call Home Exclusion List.
The Event ID is an 8-digit hexadecimal number (0-F) with an optional prefix of '0x' or '0X'.
If Service Advisor Terms and Conditions are accepted, an event can be added into the exclusion list.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.6.2 |
rmCallHomeExclusionEventRemove one call home Event ID from the Call Home Exclusion List.
The Event ID is an 8-digit hexadecimal number (0-F) with an optional prefix of '0x' or '0X'.
If Service Advisor Terms and Conditions are accepted, an event on the exclusion list can be removed.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw OCTET STRING .1.3.6.1.4.1.2.3.51.2.23.6.3 |
rmAllCallHomeExclusionEventRemove all Event IDs from the Call Home Exclusion List.
If Service Advisor Terms and Conditions are accepted, events on the exclusion list can be removed.
NOTE: Value returned for the GET command is meaningless for this MIB object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.23.6.4 |
scaling OBJECT IDENTIFIER .1.3.6.1.4.1.2.3.51.2.24 |
scalableComplexTableTable of scalable complex information. This table provides information
and control actions related to the scalable complexes installed in the
chassis. Partition, node and port information and control are defined
in their own tables. SEQUENCE OF ScalableComplexEntry .1.3.6.1.4.1.2.3.51.2.24.1 |
scalableComplexEntryScalable complex information. ScalableComplexEntry .1.3.6.1.4.1.2.3.51.2.24.1.1 |
scalableComplexIdentifierThe unique numeric identifier for a complex installed in the chassis.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.1.1.1 |
scalableComplexNumPartitionsThe number of partitions currently defined for this complex.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.1.1.2 |
scalableComplexNumNodesThe number of nodes existing in this complex, regardless
of their assignment to any given partition. The physical
slot location of the nodes can be determined from the
scalableComplexNodeTable.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.1.1.3 |
scalableComplexPartStartSlotThe lowest slot number occupied by the nodes in the new partition that
is being created via the scalableComplexAction=create(3) action. This
object must be set prior to triggering the partition creation.rw INTEGER .1.3.6.1.4.1.2.3.51.2.24.1.1.4 |
scalableComplexPartNumNodesThe number of nodes to be included in the new partition that is being
created via the scalableComplexAction=create(3) action. This object must
be set prior to triggering the partition creation.rw INTEGER .1.3.6.1.4.1.2.3.51.2.24.1.1.5 |
scalableComplexActionThis object allows various actions to be taken in relation to a particular complex.
clear(1) - This clears all partition information related to the complex. Any nodes
associated with the complex are no longer assigned to any partitions.
All nodes in the complex must be powered off prior to attempting this
operation, otherwise, the action will fail.
autocreate(2) - This creates a single partition which includes all nodes associated
with the complex. Any other prior partition definitions must be
deleted prior to issuing this action, otherwise, the action will fail.
create(3) - This allows the creation of a partition within the complex. Prior to
triggering this action, the scalableComplexPartStartSlot and
scalableComplexPartNumNodes objects must be set first to identify the starting
slot number and number of nodes to be included in this new partition.
The nodes chosen for inclusion in this new partition must not be part of
another existing partition, otherwise, the action will fail.rw Enumeration .1.3.6.1.4.1.2.3.51.2.24.1.1.6 |
scalableComplexPartitionTableTable of scalable complex partition information. This table provides information
and control actions related to the partitions defined across all of the
complexes installed in the chassis. Complex, node and port information
and control are defined in their own tables. SEQUENCE OF ScalableComplexPartitionEntry .1.3.6.1.4.1.2.3.51.2.24.2 |
scalableComplexPartitionEntryScalable complex partition information. ScalableComplexPartitionEntry .1.3.6.1.4.1.2.3.51.2.24.2.1 |
scalableComplexIdThe unique numeric identifier for a complex installed in the chassis.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.2.1.1 |
scalableComplexPartitionIdentifierThe unique numeric identifier for a partition defined within a complex
installed in the chassis.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.2.1.2 |
scalableComplexPartitionModeThe currently configured mode of this partition. It is recommended that
a partition be powered off prior to modification of the mode. In addition,
switching a partition mode to stand-alone will cause subsequent partition
actions to be ignored until the partition mode is restored.rw Enumeration .1.3.6.1.4.1.2.3.51.2.24.2.1.3 |
scalableComplexPartitionNumNodesThe number of nodes currently defined for this partition.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.2.1.4 |
scalableComplexPartitionStatusThe current power status of this partition when the partition has a
valid partition configuration. However, in the event the partition
reports a partition consitency check problem, the invalid state is provided.ro Enumeration .1.3.6.1.4.1.2.3.51.2.24.2.1.5 |
scalableComplexPartitionActionThis object allows various actions to be taken in relation to a particular partition
in a given complex.
delete(1) - Deletes the partition from the complex. All nodes in the partition must
be powered off prior to attempting this operation, otherwise, the action
will fail.
poweron(2) - Powers up a powered off partition
poweroff(3) - Powers off an already powered on partition
powercycle(4) - Power cycles a partitionrw Enumeration .1.3.6.1.4.1.2.3.51.2.24.2.1.6 |
scalableComplexNodeTableTable of scalable complex node information. This table provides information
and control actions related to the nodes installed in the chassis.
Complex, partition and port information and control are defined
in their own tables. SEQUENCE OF ScalableComplexNodeEntry .1.3.6.1.4.1.2.3.51.2.24.3 |
scalableComplexNodeEntryScalable complex node information. ScalableComplexNodeEntry .1.3.6.1.4.1.2.3.51.2.24.3.1 |
scalableComplexNodeSlotThe base slot number where the node exists in the chassis.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.3.1.1 |
scalableComplexNodeNameThe description string which uniquely identifies the blade.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.24.3.1.2 |
scalableComplexNodeTypeThe general categorization of the node.ro Enumeration .1.3.6.1.4.1.2.3.51.2.24.3.1.3 |
scalableComplexNodeResourcesA string providing a summary overview of the resources provided by this node.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.24.3.1.4 |
scalableComplexNodeRoleIndicates if the node is assigned to a partition, and if so, provides an
indication of whether the node is the primary node of the partition or not.ro Enumeration .1.3.6.1.4.1.2.3.51.2.24.3.1.5 |
scalableComplexNodeStateThe physical power state of this node.ro Enumeration .1.3.6.1.4.1.2.3.51.2.24.3.1.6 |
scalableComplexNodeUUIDThe Universally Unique IDentifier (UUID) of this node, represented
as a 16 byte hex number.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.24.3.1.7 |
scalableComplexNodeSerialNumThe serial number of this node.ro OCTET STRING .1.3.6.1.4.1.2.3.51.2.24.3.1.8 |
scalableComplexNodeNumPortsThe number of remote nodes that this node has links to.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.3.1.9 |
scalableComplexNodeComplexIDFor an assigned node, the identifier of the complex this node is related to.
For an unassigned node, this object has no meaning.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.3.1.10 |
scalableComplexNodePartitionIDFor an assigned node, the identifier of the partition this node is related to.
For an unassigned node, this object has no meaning.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.3.1.11 |
scalableComplexNodeLogicalIDThe unique numeric identifier for this node, unique within the partition.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.3.1.12 |
scalableComplexNodeActionThe actions that can be applied to an unassigned node. The current state is
provided by the scalableComplexNodeState object.rw Enumeration .1.3.6.1.4.1.2.3.51.2.24.3.1.14 |
scalableComplexNodePortTableTable of scalable complex node port information which provides details
related to the port connectivity. Complex, partition and node information
and control are defined in their own tables. SEQUENCE OF ScalableComplexNodePortEntry .1.3.6.1.4.1.2.3.51.2.24.4 |
scalableComplexNodePortEntryScalable complex node port information. ScalableComplexNodePortEntry .1.3.6.1.4.1.2.3.51.2.24.4.1 |
scalableComplexNodePortSlotThe base slot number where the node exists in the chassis.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.4.1.1 |
scalableComplexNodePortNumThe port number of a port on this node. Note that this port
number is 0-based, but since it is used as the table index
(0 is not allowed), it will be presented as one more than the
actual port number.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.4.1.2 |
scalableComplexNodePortRemChkSumThe checksum of the remote port, used as a port identifier.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.4.1.3 |
scalableComplexNodePortRemNumThe zero-based port number of the remote port.ro INTEGER .1.3.6.1.4.1.2.3.51.2.24.4.1.4 |
scalableComplexNodePortStatusThe current status of the port.ro Enumeration .1.3.6.1.4.1.2.3.51.2.24.4.1.5 |
scalableComplexNodePortTypeThe port type.ro Enumeration .1.3.6.1.4.1.2.3.51.2.24.4.1.6 |