BLADE-MIB

type

TEXTUAL-CONVENTION

Represents 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

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Management module temperature in degrees centigrade(C). An octet string expressed as 'sddd.dd Centigrade' where: s is the sign ('-' for negative or blank space for positive) d is a decimal digit or blank space for leading zeroes. The string 'Not Readable!' indicates that the given monitor is not supported on this system.

OBJECT-IDENTITY

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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 only

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

+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.

OBJECT-TYPE

+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.

OBJECT-TYPE

+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.

OBJECT-TYPE

-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.

OBJECT-TYPE

+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.

OBJECT-TYPE

+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.

OBJECT-IDENTITY

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

The health state for blower 1. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

The health state for blower 2. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table of power module health information. Contains the power health information for each power module.

OBJECT-TYPE

Power Module health entry

OBJECT-TYPE

Power module sequence index.

OBJECT-TYPE

Indicates whether the power module specified exists or not.

OBJECT-TYPE

The health state for the power module.

OBJECT-TYPE

The details for this power module.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

MM BIST DRAM test result. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

MM BIST RS 485 legacy test result.

OBJECT-TYPE

MM BIST RS 485 local bus test result.

OBJECT-TYPE

MM BIST NVRAM test result. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

MM BIST Real Time Clock test result.

OBJECT-TYPE

MM BIST Local I2C bus test result.

OBJECT-TYPE

MM BIST Primary Main Application Firmware test result.

OBJECT-TYPE

MM BIST Secondary Main Application test result.

OBJECT-TYPE

MM BIST Boot Firmware test result.

OBJECT-TYPE

MM BIST external ethernet port test result.

OBJECT-TYPE

MM BIST internal ethernet port test result. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

MM BIST PCI bus test result. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

MM BIST external I2C devices test result.

OBJECT-TYPE

MM BIST USB controller test result. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

MM BIST Video Compressor Board test result. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

MM BIST Remote Video test result. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

MM BIST primary mid-plane bus test result.

OBJECT-TYPE

MM BIST internal external switch test result.

OBJECT-TYPE

MM BIST video capture test result.

OBJECT-TYPE

MM BIST USB keyboard and mouse test result.

OBJECT-TYPE

MM BIST mass storage emulation test result.

OBJECT-TYPE

MM BIST USB keyboard and mouse firmware test result.

OBJECT-TYPE

MM BIST USB keyboard mouse firmware test result.

OBJECT-TYPE

MM BIST primary core test result.

OBJECT-TYPE

MM BIST secondary core test result.

OBJECT-TYPE

MM BIST internal IO expander test result.

OBJECT-TYPE

MM BIST Remote Control firmware test result.

OBJECT-TYPE

MM BIST Physical Network Link test result.

OBJECT-TYPE

MM BIST Logical Network Link test result.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

Indicates whether a media tray is installed on the chassis.

OBJECT-TYPE

Indicates whether a media tray is communicating.

OBJECT-TYPE

Indicates whether a redundant MM is installed.

OBJECT-TYPE

Indicates whether a redundant MM is communicating.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

It is the time when the primary MM updated the last BIST results.

OBJECT-IDENTITY

OBJECT-TYPE

Standby MM BIST RS 485 legacy test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST RS 485 local bus test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST Real Time Clock test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST Local I2C bus test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST Primary Main Application Firmware test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST Secondary Main Application test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST Boot Firmware test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST external ethernet port test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby MM BIST internal external switch test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby MM BIST primary core test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST secondary core test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby MM BIST internal IO expander test result. The time of the last update can be obtained by querying rbistUpdateTime object.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

Standby 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.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

Indicates 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.

OBJECT-TYPE

Indicates 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.

OBJECT-TYPE

Indicates 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.

OBJECT-TYPE

Indicates 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'.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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'.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

It is the time when the standby MM updated the last BIST results.

OBJECT-TYPE

It is the time when the standby MM updated the last BIST results when it was still primary.

OBJECT-IDENTITY

OBJECT-TYPE

Table of fan pack information. Contains the information for each fan pack. NOTE: Fan packs are also referred to as Power Module Cooling Devices.

OBJECT-TYPE

Fan Pack entry

OBJECT-TYPE

Fan Pack sequence index.

OBJECT-TYPE

Indicates whether the fan pack specified exists or not.

OBJECT-TYPE

The health state for the fan pack. 0 = unknown, 1 = good, 2 = warning, 3 = bad.

OBJECT-TYPE

The number of fans in the fan pack.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The health state for the controller for the fan pack. 0 = operational, 1 = flashing in progress, 2 = not present, 3 = communication error, 255 = unknown

OBJECT-IDENTITY

OBJECT-TYPE

Indicates 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.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

System Health Summary entry NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

System health summary index. NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

System health summary severity. NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

System health summary description. NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

System health summary date time. NOTE: This MIB object is for BladeCenter only.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Indicates whether the front panel system error LED is on or off. NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

Indicates 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.

OBJECT-TYPE

Indicates whether the front panel temperature LED is on or off. NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

Indicates whether the front panel identity LED is on or off. NOTE: This MIB object is for BladeCenter only.

OBJECT-IDENTITY

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Blade system status entry

OBJECT-TYPE

Blade LED table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the server blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

Indicates whether the blade system error LED is on or off.

OBJECT-TYPE

Indicates whether the blade information LED is on or off. For Write access, the LED can be turned off only.

OBJECT-TYPE

Indicates whether the blade KVM LED is on, off, or blinking.

OBJECT-TYPE

Indicates whether the blade media tray LED is on, off, or blinking.

OBJECT-TYPE

Indicates whether the blade identify LED is on, off, or blinking.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Blade LEDs Details entry

OBJECT-TYPE

The LED index number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The 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.

OBJECT-TYPE

Type of the component/subcomponent grouping for this LED. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Text label for a LED. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Text description which denotes color or on/off/blink state for a LED. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Location of this LED. For consistent results, view as a table and not as individual entries.

OBJECT-IDENTITY

OBJECT-TYPE

Indicates whether the BladeCenter T Panel CRT (Critical) LED is on or off. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Indicates whether the BladeCenter T Panel MJR (Major) LED is on or off. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Indicates whether the BladeCenter T Panel MNR (Minor) LED is on or off. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Indicates whether the BladeCenter T Panel identity LED is on or off. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Indicates whether the BladeCenter T Critical and Major LEDs are displayed in amber or red color. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Indicates whether the BladeCenter T Criticality Assertion Mode is enabled or disabled. NOTE: This MIB object is for BladeCenter T only.

OBJECT-IDENTITY

OBJECT-TYPE

Table of switch module LEDs information.

OBJECT-TYPE

Switch module LEDs information entry

OBJECT-TYPE

Switch module LEDs table index.

OBJECT-TYPE

A 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table of blower LEDs information. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

Blower LEDs information entry

OBJECT-TYPE

Blower LEDs table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the blower specified exists or not.

OBJECT-TYPE

Indicates whether the blower error LED is on, off, or not available.

OBJECT-IDENTITY

OBJECT-TYPE

Table of fan pack LEDs information. NOTE: Fan packs are also referred to as Power Module Cooling Devices.

OBJECT-TYPE

Fan Pack LEDs information entry

OBJECT-TYPE

Fan Pack LEDs table index.

OBJECT-TYPE

The numeric fan pack ID.

OBJECT-TYPE

Indicates whether the fan pack specified exists or not.

OBJECT-TYPE

Indicates whether the fan pack error LED is on or off.

OBJECT-IDENTITY

OBJECT-TYPE

Table of Media Tray Status LEDs information. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Media Tray Status LEDs information entry. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Media Tray Status LEDs table index. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

The numeric Media Tray ID. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Media Tray exists or not. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Media Tray Fault LED is on or off. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-IDENTITY

OBJECT-TYPE

Indicates whether the Alarm Panel exists or not. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Alarm Panel Safe To Remove LED is on or off. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Alarm Panel Fault LED is on or off. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-IDENTITY

OBJECT-TYPE

Table of Network Clock Status LEDs information. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Network Clock Status LEDs information entry. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Network Clock Status LEDs table index. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

The numeric Network Clock ID. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Network Clock exists or not. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Network Clock Safe To Remove LED is on or off. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Network Clock Fault LED is on or off. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-IDENTITY

OBJECT-TYPE

Table of Multiplexer Expansion Module Status LEDs information. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Multiplexer Expansion Module Status LEDs information entry. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Multiplexer Expansion Module Status LEDs table index. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

The numeric Multiplexer Expansion Module ID. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Multiplexer Expansion Module exists or not. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Multiplexer Expansion Module Safe To Remove LED is on or off. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Indicates whether the Multiplexer Expansion Module Fault LED is on or off. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-IDENTITY

OBJECT-TYPE

Table of storage module LEDs information. NOTE: This MIB object is for BladeCenter S only.

OBJECT-TYPE

Storage Module LEDs information entry NOTE: This MIB object is for BladeCenter S only.

OBJECT-TYPE

Storage Module LEDs table index. NOTE: This MIB object is for BladeCenter S only.

OBJECT-TYPE

The numeric storage module ID. NOTE: This MIB object is for BladeCenter S only.

OBJECT-TYPE

Indicates whether the storage module specified exists or not. NOTE: This MIB object is for BladeCenter S only.

OBJECT-TYPE

Indicates the status of the storage module error LED. NOTE: This MIB object is for BladeCenter S only.

OBJECT-IDENTITY

OBJECT-TYPE

Indicates 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.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

BladeCenter T System Health Summary entry. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

BladeCenter T System Health Summary Index. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

BladeCenter 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'.

OBJECT-TYPE

BladeCenter 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'.

OBJECT-TYPE

BladeCenter T System Health Summary Event Name. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

BladeCenter 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'.

OBJECT-TYPE

BladeCenter T System Health Summary Acknowledge. Indicates whether the alarm event is acknowledged or unacknowledged. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

BladeCenter 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'.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of Fuel Gauge information.

OBJECT-TYPE

Fuel Gauge entry

OBJECT-TYPE

Fuel Gauge Table Index.

OBJECT-TYPE

Fuel Gauge Table Power Domain Number.

OBJECT-TYPE

Fuel 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.

OBJECT-TYPE

Fuel 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.

OBJECT-TYPE

Fuel 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.

OBJECT-TYPE

Fuel 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 Management

OBJECT-TYPE

This 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.

OBJECT-TYPE

This 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.

OBJECT-TYPE

This 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.

OBJECT-TYPE

This 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Fuel Gauge entry

OBJECT-TYPE

Power Domain 1 Table Index.

OBJECT-TYPE

Power 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)

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power Domain 1 Table Module Throttle Status.

OBJECT-TYPE

Power Domain 1 Table Module Name.

OBJECT-TYPE

Power Domain 1 Table Module State.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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 higher

OBJECT-TYPE

Power Domain 1 Table Module Measured Or Static.

OBJECT-IDENTITY

OBJECT-TYPE

Specify 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.

OBJECT-TYPE

Table of Power Domain 1 Power Trending Information.

OBJECT-TYPE

Power Domain 1 Power Trending Sample entry.

OBJECT-TYPE

Power Domain 1 Power Trending Sample Table Index.

OBJECT-TYPE

Power Domain 1 Power Trending Sample Table Timestamp.

OBJECT-TYPE

Power Domain 1 Power Trending Table Average Power.

OBJECT-IDENTITY

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Fuel Gauge entry

OBJECT-TYPE

Power Domain 2 Table Index.

OBJECT-TYPE

Power 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)

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power Domain 2 Table Module throttle status.

OBJECT-TYPE

Power Domain 2 Table Module Name.

OBJECT-TYPE

Power Domain 2 Table Power State.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power 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 higher

OBJECT-TYPE

Power Domain 2 Table Module Measured Or Static.

OBJECT-IDENTITY

OBJECT-TYPE

Specify 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.

OBJECT-TYPE

Table of Power Domain 2 Power Trending Sample Information.

OBJECT-TYPE

Power Domain 2 Power Trending Sample entry.

OBJECT-TYPE

Power Domain 2 Power Trending Sample Table Index.

OBJECT-TYPE

Power Domain 2 Power Trending Sample Table Timestamp.

OBJECT-TYPE

Power Domain 2 Power Trending Sample Table Average Power.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of Blade Module Details.

OBJECT-TYPE

Blade Module Details entry.

OBJECT-TYPE

Blade Module Details Table Index.

OBJECT-TYPE

Blade Module Details Table Blade Id.

OBJECT-TYPE

Blade 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 feature

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

When 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.

OBJECT-TYPE

When 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.

OBJECT-TYPE

When 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.

OBJECT-TYPE

This object is used to get or set the power control setting on a blade. If dynamic power mgmt is not supported on a blade, notApplicable(255) will be returned. This will set the power control setting on all slots of the multiwide blade. The same can be used if the blade is single wide.

OBJECT-IDENTITY

OBJECT-TYPE

Specify 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.

OBJECT-TYPE

Blade Module Power Trending Blade Id. NOTE: The Blade Id should be configured before displaying the bladePowerTrendingTable.

OBJECT-TYPE

Table of Blade Module Power Trending Information.

OBJECT-TYPE

Blade Module Power Trending Sample entry.

OBJECT-TYPE

Blade Module Power Trending Sample Table Index.

OBJECT-TYPE

Blade Module Power Trending Sample Table Blade Id.

OBJECT-TYPE

Blade Module Power Trending Sample Table Timestamp.

OBJECT-TYPE

Blade Module Power Trending Sample Table Maximum Power.

OBJECT-TYPE

Blade Module Power Trending Sample Table Minimum Power.

OBJECT-TYPE

Blade Module Power Trending Sample Table Average Power.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Specify 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.

OBJECT-TYPE

Switch Module Power Trending Switch Id. NOTE: The Switch Id should be configured before displaying the switchPowerTrendingTable.

OBJECT-TYPE

Table of Switch Module Power Trending Information.

OBJECT-TYPE

Switch Module Power Trending Sample entry.

OBJECT-TYPE

Switch Module Power Trending Sample Table Index.

OBJECT-TYPE

Switch Module Power Trending Sample Table Switch Id.

OBJECT-TYPE

Switch Module Power Trending Sample Table Timestamp.

OBJECT-TYPE

Switch Module Power Trending Sample Table Maximum Power.

OBJECT-TYPE

Switch Module Power Trending Sample Table Minimum Power.

OBJECT-TYPE

Switch Module Power Trending Sample Table Average Power.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Specify 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.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Table of Blower Module Power Trending Information. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

Blower Module Power Trending Sample entry.

OBJECT-TYPE

Blower Module Power Trending Sample Table Index.

OBJECT-TYPE

Blower Module Power Trending Sample Table Blower Id.

OBJECT-TYPE

Blower Module Power Trending Sample Table Timestamp.

OBJECT-TYPE

Blower Module Power Trending Sample Table Maximum Power.

OBJECT-TYPE

Blower Module Power Trending Sample Table Minimum Power.

OBJECT-TYPE

Blower Module Power Trending Sample Table Average Power.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Chassis total DC power available, which displays the total DC power available for the entire chassis. It is the sum of the two power domains.

OBJECT-TYPE

Chassis 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.

OBJECT-TYPE

Chassis 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).

OBJECT-TYPE

Chassis 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.

OBJECT-TYPE

The chassis power service mode. NOTE: This MIB object is for BCS only.

OBJECT-IDENTITY

OBJECT-TYPE

Specify time period of power trending information. NOTE: This time period should be configured before displaying the following Power Trending Information table for Chassis.

OBJECT-TYPE

Table of Chassis Power Trending Sample Information in specified time period.

OBJECT-TYPE

Chassis Power Trending Sample entry in specified time period.

OBJECT-TYPE

Chassis Power Trending Sample Index in specified time period.

OBJECT-TYPE

Chassis Power Trending Sample Timestamp in specified time period.

OBJECT-TYPE

Chassis Power Trending Sample Average Power in specified time period.

OBJECT-IDENTITY

OBJECT-TYPE

Specify time period of thermal trending information. NOTE: This time period should be configured before displaying the following Thermal Trending Information table for Chassis.

OBJECT-TYPE

Table of Media Tray 1 Thermal Trending Information.

OBJECT-TYPE

Media Tray 1 Thermal Trending entry.

OBJECT-TYPE

Media Tray 1 Thermal Trending Table Index.

OBJECT-TYPE

Media Tray 1 Thermal Trending Table Sample Timestamp.

OBJECT-TYPE

Media Tray 1 Thermal Trending Table Temperature.

OBJECT-TYPE

Table of Media Tray 2 Thermal Trending Information. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Media Tray 2 Thermal Trending entry. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Media Tray 2 Thermal Trending Table Index. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Media Tray 2 Thermal Trending Table Sample Timestamp. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Media Tray 2 Thermal Trending Table Temperature. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-TYPE

Table of Blower 1 Thermal Trending Information. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

Blower 1 Thermal Trending entry.

OBJECT-TYPE

Blower 1 Thermal Trending Table Index.

OBJECT-TYPE

Blower 1 Thermal Trending Table Sample Timestamp.

OBJECT-TYPE

Blower 1 Thermal Trending Table Temperature.

OBJECT-TYPE

Table of Blower 2 Thermal Trending Information. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

Blower Thermal 2 Trending entry.

OBJECT-TYPE

Blower 2 Thermal Trending Table Index.

OBJECT-TYPE

Blower 2 Thermal Trending Table Sample Timestamp.

OBJECT-TYPE

Blower 2 Thermal Trending Table Temperature.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Blower 3 Thermal Trending entry. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Blower 3 Thermal Trending Table Index. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Blower 3 Thermal Trending Table Sample Timestamp. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Blower 3 Thermal Trending Table Temperature. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Table of Blower 4 Thermal Trending Information. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Blower 4 Thermal Trending entry. NOTE: This MIB object is for BladeCenter T only. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

Blower 4 Thermal Trending Table Index. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Blower 4 Thermal Trending Table Sample Timestamp. NOTE: This MIB object is for BladeCenter T only.

OBJECT-TYPE

Blower 4 Thermal Trending Table Temperature. NOTE: This MIB object is for BladeCenter T only.

OBJECT-IDENTITY

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Power Policy Entry

OBJECT-TYPE

The unique idenitifier of a row in the powerPolicyTable.

OBJECT-TYPE

The power domain number which this row is associated with.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The maximum number of power supplies that can fail in a chassis while still providing redundancy.

OBJECT-TYPE

The maximum power available (in watts), based on the number of power modules and the Power Management Policy setting.

OBJECT-TYPE

The estimated utilization (as a percentage) based on current power usage.

OBJECT-TYPE

When 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.

OBJECT-IDENTITY

OBJECT-TYPE

Indicates whether the front bezel is installed or not. NOTE: This MIB object is for BladeCenter HT only.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of MM users currently logged in. NOTE: This MIB object is for AMM only.

OBJECT-TYPE

MM users currently logged in entries. NOTE: This MIB object is for AMM only.

OBJECT-TYPE

Index for MM users currently logged in.

OBJECT-TYPE

Name for MM users currently logged in. NOTE: 'Default SNMPv1 user' indicates an internal user used by SNMPv1 agent.

OBJECT-TYPE

Access method for MM users currently logged in.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of voltage threshold entries. NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

Voltage threshold entries. NOTE: This MIB object is for BladeCenter only.

OBJECT-TYPE

Index for voltage threshold entry.

OBJECT-TYPE

Voltage threshold entry null terminated string that contains the power supply's name, for example '+5V'.

OBJECT-TYPE

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.

OBJECT-TYPE

Voltage 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.

OBJECT-TYPE

Voltage 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.

OBJECT-TYPE

Voltage 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.

OBJECT-TYPE

Voltage 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.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Machine type VPD information (from System BIOS). This field must be four alpha numeric characters.

OBJECT-TYPE

Machine model VPD information (from System BIOS). This field must be three alpha numeric characters.

OBJECT-TYPE

Machine serial number VPD information (from System BIOS). This field must be seven alpha numeric characters.

OBJECT-TYPE

Machine UUID (Universal Unique ID information) (from System BIOS). This field must be 32 alpha numeric characters.

OBJECT-TYPE

Machine chassis manufacturing ID.

OBJECT-TYPE

Machine 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.

OBJECT-TYPE

Machine chassis FRU number.

OBJECT-TYPE

Machine chassis manufacture date.

OBJECT-TYPE

Machine chassis part number.

OBJECT-TYPE

Machine chassis FRU serial number.

OBJECT-TYPE

Machine chassis manufacturer ID Number.

OBJECT-TYPE

Machine chassis product ID.

OBJECT-TYPE

Machine chassis subsystem manufacturer.

OBJECT-TYPE

Machine chassis Common Language Equipment Identification (CLEI).

OBJECT-TYPE

Presence of the Direct Serial Attach Module. NOTE: This MIB object is for BCS only.

OBJECT-TYPE

Machine 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table of the management module hardware components. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management module hardware VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD manufacture date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD manufacturer ID Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD subsystem manufacturer. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module hardware VPD Common Language Equipment Identification (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management 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.

OBJECT-TYPE

Management module Interposer hardware VPD manufacturer ID Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module Interposer hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module Interposer hardware VPD subsystem manufacturer. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management module Interposer hardware VPD Common Language Equipment Identification (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Management 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table of MM Firmware VPD.

OBJECT-TYPE

MM Firmware VPD entry.

OBJECT-TYPE

Firmware VPD index.

OBJECT-TYPE

Firmware VPD name description. 'AMM firmware' indicates the running firmware of the MM. 'AMM firmware (pending restart)' indicates the flashed firmware of the MM which will become active after the next restart.

OBJECT-TYPE

Firmware VPD build identification.

OBJECT-TYPE

Firmware VPD revision number.

OBJECT-TYPE

Firmware VPD file name.

OBJECT-TYPE

Firmware VPD build date.

OBJECT-TYPE

Table of MM Firmware VPD. NOTE: This MIB object is for MM only. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

MM Firmware VPD entry. NOTE: This MIB object is for MM only. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD index. NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD name description. NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build identification. NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD revision number. NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD file name. NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build date. NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Table of MM Firmware VPD. NOTE: This MIB object is for MM only. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

MM Firmware VPD entry. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD index. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD name description. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build identification. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD revision number. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD file name. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build date. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Table of MM Firmware VPD. NOTE: This MIB object is for MM only. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

MM Firmware VPD entry. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD index. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD name description. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build identification. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD revision number. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD file name. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build date. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Table of MM Firmware VPD. NOTE: This MIB object is for MM only. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

MM Firmware VPD entry. NOTE: This table is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD index. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD name description. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build identification. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD revision number. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD file name. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-TYPE

Firmware VPD build date. NOTE: This Mib object is deprecated and no longer supported.

OBJECT-IDENTITY

OBJECT-TYPE

Table of VPD information for the blade hardware components. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade hardware VPD serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD machine type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD Manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD machine model. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD Manufacturer ID Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade expansion card (daughter card) VPD type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade expansion card (daughter card) VPD Serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD Machine type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD Manufacture date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD FRU Serial. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD manufacturer ID Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD subsystem manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Table of MAC addresses of the blade and its expansion cards (daughter cards). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 1 MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 2 MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 3 MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 4 MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card (daughter card) 5 MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 9. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 10. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 11. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 12. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 13. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 14. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 15. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade high speed expansion card (daughter card) 1 MAC address 16. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card MAC address 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Table of VPD information for the blade expansion board components. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade expansion board VPD serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD machine type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD Manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD machine model. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD Manufacturer ID Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD Product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade bay number of the blade expansion board. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion board VPD type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Table of VPD information for the blade side card components. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade side card VPD serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD machine type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD Manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD machine model. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD Manufacturer ID Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD Product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade side card VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade bay number of the blade side card. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Table of VPD information for the blade expansion card components. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade expansion card VPD serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD machine type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD Manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD machine model. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD Manufacturer ID Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD Product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade bay number of the blade expansion card. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Blade concurrent keyboard, video, and mouse (cKVM) card VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard mouse video (cKVM) card VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD machine type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD Manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD machine model. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD Product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade concurrent keyboard video mouse (cKVM) card VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Blade WWN/GUID entries. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card VPD bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The name of the blade or expansion card. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

For 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.

OBJECT-TYPE

Blade or expansion card WWN/GUID/SAS Type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 1. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 2. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 3. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 4. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 5. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 6. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 7. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade or expansion card WWN/GUID 8. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Table of VPD information for the blade management card component. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-TYPE

Blade management card VPD serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD machine type. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD Manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD Part number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD machine model. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD Product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade management card VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table of blade firmware vital product data (VPD) information.

OBJECT-TYPE

Blade firmware VPD table entry

OBJECT-TYPE

Blade firmware VPD table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the server blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

The build ID for the blade firmware.

OBJECT-TYPE

The revision of the blade firmware.

OBJECT-TYPE

The date of the blade firmware.

OBJECT-TYPE

The 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).

OBJECT-TYPE

Table of blade firmware vital product data (VPD) information.

OBJECT-TYPE

Blade firmware VPD table entry

OBJECT-TYPE

Blade firmware VPD table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the server blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

The build ID for the blade firmware.

OBJECT-TYPE

The revision of the blade firmware.

OBJECT-TYPE

The date of the blade firmware.

OBJECT-TYPE

The 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).

OBJECT-TYPE

Table of blade firmware vital product data (VPD) information.

OBJECT-TYPE

Blade firmware VPD table entry

OBJECT-TYPE

Blade firmware VPD table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the server blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

The build ID for the blade firmware.

OBJECT-TYPE

The revision of the blade firmware.

OBJECT-TYPE

The 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).

OBJECT-TYPE

Table of blade firmware vital product data (VPD) information.

OBJECT-TYPE

Blade firmware VPD table entry

OBJECT-TYPE

Blade firmware VPD table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

The revision of the blade firmware.

OBJECT-IDENTITY

OBJECT-TYPE

Table of Blade Firmware Build ID entries information.

OBJECT-TYPE

Blade Firmware Build ID table entry

OBJECT-TYPE

The index number of one Build ID entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The Manufacturer property of one Build ID entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The Machine Type property of one Build ID entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The Firmware Type property of one Build ID entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The Build ID property of one Build ID entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The Build Revision property of one Build ID entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Create one new Build ID List from current installed blades. NOTE: Value returned for the GET command is meaningless for this MIB object.

OBJECT-IDENTITY

OBJECT-TYPE

Add one Build ID entry into the Build ID List. This is to set Manufacturer property.

OBJECT-TYPE

Add one Build ID entry into the Build ID List. This is to set Machine Type property.

OBJECT-TYPE

Add one Build ID entry into the Build ID List. This is to set Firmware Type property.

OBJECT-TYPE

Add one Build ID entry into the Build ID List. This is to set Build ID property.

OBJECT-TYPE

Add one Build ID entry into the Build ID List. This is to set Build Revision property.

OBJECT-TYPE

Add 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.

OBJECT-TYPE

Remove 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.

OBJECT-TYPE

Remove all Build ID entries from the Build ID List. NOTE: Value returned for the GET command is meaningless for this MIB object.

OBJECT-TYPE

File name of the Build ID list that will be used in import function.

OBJECT-TYPE

Contains 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>.

OBJECT-TYPE

If 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).

OBJECT-TYPE

Import one Build ID List set by the buildIDFilename from a specific location set by buildIDServer.

OBJECT-TYPE

Export 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.

OBJECT-TYPE

Gives the status message from the last import or export operation.

OBJECT-IDENTITY

OBJECT-TYPE

Table of the switch module hardware components. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch module hardware VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD manufacture date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD Part Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD FRU Serial. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch module hardware VPD World Wide Name or Global Unique ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The width of the switch module hardware. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

Switch 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.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The width of the switch Interposer module hardware. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

The Switch Interposer Name. For consistent results, view as a table and not as individual entries. NOTE: This MIB object is for BladeCenter HS only.

OBJECT-TYPE

Switch 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.

OBJECT-IDENTITY

OBJECT-TYPE

Switch module main application VPD information table.

OBJECT-TYPE

Switch module main application VPD table entry

OBJECT-TYPE

Switch module main application VPD entry index.

OBJECT-TYPE

The switch module numeric identifier.

OBJECT-TYPE

Indicates whether the switch module specified exists or not.

OBJECT-TYPE

Indicates the type of switch module installed.

OBJECT-TYPE

Switch module firmware build id.

OBJECT-TYPE

Switch module firmware build date.

OBJECT-TYPE

Switch module firmware revision number.

OBJECT-TYPE

Switch module firmware build id.

OBJECT-TYPE

Switch module firmware build date.

OBJECT-TYPE

Switch module firmware revision number.

OBJECT-TYPE

I/O Module firmware build id.

OBJECT-TYPE

I/O Module firmware build date.

OBJECT-TYPE

I/O Module firmware revision number.

OBJECT-TYPE

Indicates the subtype of switch module installed.

OBJECT-TYPE

Switch module boot ROM VPD information table.

OBJECT-TYPE

Switch module boot ROM VPD table entry

OBJECT-TYPE

Switch module boot ROM VPD entry index.

OBJECT-TYPE

The switch module numeric identifier.

OBJECT-TYPE

Indicates whether the switch module specified exists or not.

OBJECT-TYPE

Indicates the type of switch module installed.

OBJECT-TYPE

Switch module firmware build ID.

OBJECT-TYPE

Switch module firmware build date.

OBJECT-TYPE

Switch module firmware revision number.

OBJECT-TYPE

Indicates the subtype of switch module installed.

OBJECT-IDENTITY

OBJECT-TYPE

Table of the power module hardware components. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power 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.

OBJECT-TYPE

Power module hardware VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD Manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD Part Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD FRU Serial. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power module hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Power 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.

OBJECT-IDENTITY

OBJECT-TYPE

Media tray 1 hardware VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 1 hardware VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media 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.

OBJECT-TYPE

Media tray 1 hardware VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 1 hardware VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 1 hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 1 hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 1 hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 1 hardware VPD CompactFlash card capacity. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 1 hardware VPD CompactFlash card capacity. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Indicates the presence of Battery Backup Unit 1. NOTE: This MIB object is for BCS only.

OBJECT-TYPE

Indicates the presence of Battery Backup Unit 2. NOTE: This MIB object is for BCS only.

OBJECT-TYPE

Media 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.

OBJECT-TYPE

Media tray 1 hardware VPD Manufacture Date.

OBJECT-TYPE

Media tray 1 hardware VPD Part Number.

OBJECT-TYPE

Media tray 1 hardware VPD FRU Serial.

OBJECT-IDENTITY

OBJECT-TYPE

Media tray 2 hardware VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 2 hardware VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media 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.

OBJECT-TYPE

Media tray 2 hardware VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 2 hardware VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 2 hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 2 hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 2 hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 2 hardware VPD CompactFlash card capacity. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media tray 2 hardware VPD CompactFlash card capacity. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Media 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.

OBJECT-TYPE

Media tray 2 hardware VPD Manufacture Date.

OBJECT-TYPE

Media tray 2 hardware VPD Part Number.

OBJECT-TYPE

Media tray 2 hardware VPD FRU Serial.

OBJECT-IDENTITY

OBJECT-TYPE

Table of blower controller firmware vital product data (VPD) information. NOTE: Blowers are also referred to as Chassis Cooling Devices.

OBJECT-TYPE

Blower controller firmware VPD table entry

OBJECT-TYPE

Blower controller firmware VPD table index.

OBJECT-TYPE

The numeric blower ID.

OBJECT-TYPE

Indicates whether the blower specified exists or not.

OBJECT-TYPE

The revision of the blower controller firmware.

OBJECT-IDENTITY

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Blower hardware VPD entry. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD index. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD Bay number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD manufacturing ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD FRU number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower 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.

OBJECT-TYPE

Blower hardware VPD UUID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD manufacture Date. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD Part Number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD FRU serial number. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blower 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table of fan pack controller firmware vital product data (VPD) information. NOTE: Fan packs are also referred to as Power Module Chassis Cooling Devices.

OBJECT-TYPE

Fan Pack controller firmware VPD table entry

OBJECT-TYPE

Fan Pack controller firmware VPD table index.

OBJECT-TYPE

The numeric fan pack ID.

OBJECT-TYPE

Indicates whether the fan pack specified exists or not.

OBJECT-TYPE

The revision of the fan pack controller firmware.

OBJECT-IDENTITY

OBJECT-TYPE

Telco 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.

OBJECT-TYPE

Telco 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.

OBJECT-TYPE

Telco 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.

OBJECT-TYPE

Telco 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.

OBJECT-TYPE

Telco 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.

OBJECT-TYPE

Telco 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.

OBJECT-TYPE

Telco 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.

OBJECT-TYPE

Telco Alarm Panel hardware VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Telco Alarm Panel hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Telco Alarm Panel hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Telco Alarm Panel hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Telco 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network 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.

OBJECT-TYPE

Network Clock hardware VPD manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Network Clock hardware VPD product ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Network Clock hardware VPD subsystem manufacturer ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Network Clock hardware VPD Common Language Equipment Identifier (CLEI). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Network 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.

OBJECT-IDENTITY

OBJECT-TYPE

Table 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.

OBJECT-TYPE

Multiplexer 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.

OBJECT-TYPE

Multiplexer 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.

OBJECT-TYPE

Multiplexer 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.

OBJECT-TYPE

Multiplexer 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.