CME-MIB: View SNMP OID List / Download MIB

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

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

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

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

If this is enabled, the management module will monitor for Hot Air Recirculation by detecting non-uniform air temperature(s) that may be entering the front of the chassis. This could be due to either localized hot or cold air reaching at least one of the node's or chassis temperature sensors and it exceeding the acceptable range. When enabled, this monitor will generate an event and be transmitted to any configured remote alert recipient. Enumeration: 'enable': 1, 'disable': 0.

This object is used to read or change the temperature delta threshold for Hot Air Recirculation detection. Values are enforced to be in the inclusive range between 5.00C and 9.00C and are specified as hundreths of a degree. For example, a value of 659 would equate to a threshold of 6.59 degrees C.

Table of hot air recirculation status information.

Hot air recirculation status entry

The unique identifier for a component in this table. The chassis and each installed component is represented by a hardware topology tree, where each node in the tree represents a component. The path to a particular component consists of one or more , pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. Note that this TP is preceded by a single octet that specifies the TP length. This is required since this table is indexed with two indices and, therefore, the TP length must be explicitly provided. This component firmware table is indexed by this unique topology path and the numeric designations for the components are: CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade POWER, 0x04 Power Supply, Power Module, etc COOLING, 0x05 Fan, blower, or other cooling device IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge MEDIA, 0x07 Media device PROCESSOR, 0x08 Any processor, processor module, etc STORAGE, 0x09 Any type of storage device EXPANSION, 0x0A Expansion Card (not covered by more specific type) MEMORY, 0x0B Any memory device, module, etc MFRU, 0x0C Managed FRU Device PANEL, 0x0D Any sort of panel device, such as a front panel BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc CARD_EXPANSION, 0x0F Expansion card, ie. daughter card CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card INTERPOSER, 0x11 Interposer device CLOCK, 0x12 Clock card MUX, 0x13 Mulitplexer card ADDIN, 0x14 cKVM card & other addin cards STORAGE_MODULE, 0x15 Container of one or more Storage Devices SYS_EXPANSION_CARD, 0x16 Management card BATTERY, 0x17 A single battery BATTERY_MODULE, 0x18 Container of one or more batteries REAR_LED, 0x19 Rear LED card MEMORY_BANK, 0x1A Memory banks AIR_FILTER, 0x1B Filter mechanism (bezel) SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports PARENT, 0x1D Reference to parent for multi-parent support PHY_PORT, 0x1E Physical port IO_EXPANDER, 0x1F RAID card CABLE, 0x20 Cable/Interconnect FAN_MUX 0x29 Fan multiplexer card PCI_EXPRESS, 0x32 PCI express card on (PEN) FLASH_DIMM, 0x33 Used for SPD devices that matches the silkscreen of the DIMM slot RACK, 0x50 Rack PLATFORM, 0x51 Generic Platform like rack mounted server/appliance DATAPLEX, 0x52 DataPlex OTHER, 0x53 Other unknown etc. PERIPHERAL_MODULE, 0x54 SYSTEM_BOARD, 0x55 System board PROCESSOR_MODULE, 0x56 BACK_PANEL, 0x57 POWER_SYSTEM_BOARD, 0x58 STORAGE_BACKPLANE, 0x59 Drive back plane PROC_BOARD, 0x5A Holds 1 or more processors POWER_DI, 0x5B Power mgt / power distribution board CHASSIS_BACK_PANEL, 0x5C SUB_CHASSIS, 0x5D OTHER_CHASSIS_BOARD, 0x5E DEVICE_MODULE, 0x5F REMOTE_DEVICE, 0x60 Remote mgt communication device EXTERNAL_ENVIRONMENT, 0x61 Such as external temp sensor for outside box temps PROC_MEMORY_MODULE, 0x62 Processors and memory on same module

Each component may have one or more sensor associated with it, this index object identifies the particular instance.

The name of the component as a null terminated string

The text label of the sensor as a null terminated string

Ambient temperature reading for this component in degrees centigrade(C). The string is formatted as 'dd.dd Centigrade'.

Indicates whether this component has exceeded the threshold of the acceptable temperature being monitored for hot air recirculation. Enumeration: 'yes': 1, 'no': 0.

Table of chassis Fan information.

Chassis Fan information entry

Chassis Fans table index.

The numeric chassis fan ID. Enumeration: 'chassisfan2': 2, 'chassisfan3': 3, 'chassisfan1': 1, 'chassisfan6': 6, 'chassisfan7': 7, 'chassisfan4': 4, 'chassisfan5': 5, 'chassisfan10': 10, 'chassisfan8': 8, 'chassisfan9': 9.

Chassis fan speed expressed in percent(%) of maximum RPM. An octet string expressed as 'ddd% of maximum' where: d is a decimal digit or blank space for a leading zero. If the chassis fan is determined not to be running or the chassis fan speed cannot be determined, the string will indicate 'Offline'. The string 'Not Readable!' indicates that the given monitor is not supported on this system.

The health state for the chassis fan. Note that the other UIs may use slightly different terminology for the three health state values, as such: WEB - Normal, Attention, Critical CLI - OK, Non-critical, Critical Enumeration: 'unknown': 0, 'bad': 3, 'good': 1, 'warning': 2.

Chassis fan speed expressed in RPM. If the chassis fan is determined not to be running or the chassis fan speed cannot be determined, the string will indicate 'Offline'. The string 'Not Readable!' indicates that the given monitor is not supported on this system.

The controller health state for the chassis fan. Enumeration: 'unknown': 255, 'flashing': 1, 'communicationError': 3, 'notPresent': 2, 'operational': 0.

The cooling zone for the chassis fan. Enumeration: 'coolingZone1': 1, 'unknown': 0, 'coolingZone3': 3, 'coolingZone2': 2, 'coolingZone4': 4.

Table of chassis cooling zone information.

Chassis cooling zone information entry

Chassis Cooling Zones table index.

The cooling zone for the chassis component. Enumeration: 'coolingZone1': 1, 'coolingZone3': 3, 'coolingZone2': 2, 'coolingZone4': 4.

The health state of the chassis cooling zone. Note: This is the health of the cooling zone, not the health status of the component in chassisCoolingZoneComponent. Note that the other UIs may use slightly different terminology for the three health state values, as such: WEB - Normal, Attention, Critical CLI - OK, Non-critical, Critical Enumeration: 'unknown': 0, 'bad': 3, 'good': 1, 'warning': 2.

A component within a cooling zone. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'switchModule1': 41, 'fan5': 85, 'switchModule3': 43, 'switchModule2': 42, 'switchModule4': 44, 'fan4': 84, 'fan9': 89, 'fan8': 88, 'mgmtModule2': 62, 'fan10': 90, 'mgmtModule1': 61, 'fan1': 81, 'fan3': 83, 'fan2': 82, 'blade8': 8, 'blade9': 9, 'fan7': 87, 'fan6': 86, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

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

Power Module health entry

Power module index.

Indicates whether the power module specified exists or not. Enumeration: 'true': 1, 'false': 0.

The health state for the power module. Note that the other UIs may use slightly different terminology for the three health state values, as such: WEB - Normal, Attention, Critical CLI - OK, Non-critical, Critical Enumeration: 'notAvailable': 3, 'unknown': 0, 'good': 1, 'warning': 2, 'critical': 4.

The details for this power module.

The description for this power module.

MM BIST Real Time Clock test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST Local I2C bus test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST Primary Main Application Firmware test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST Secondary Main Application test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST Boot Firmware test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST external eth0 ethernet port test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST external I2C devices test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST internal external switch test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST primary kernel test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST secondary kernel test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST Physical Network Link test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

MM BIST Logical Network Link test result. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

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

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

The chassis fans that are installed on the chassis. They are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number supported. If one is installed in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if it is installed in bay 1, and 2 are supported, the string would look like '10'.

The chassis fans installed on the chassis that are functional. They are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number supported. If one is installed in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if it is installed in bay 1, and 2 are supported, the string would look like '10'.

Indicates whether a rear LED card is installed Enumeration: 'yes': 1, 'no': 0.

Indicates whether a rear LED card is communicating Enumeration: 'yes': 1, 'no': 0.

Indicates whether a redundant MM is installed. Enumeration: 'yes': 1, 'no': 0.

Indicates whether a redundant MM is communicating. Enumeration: 'yes': 1, 'no': 0.

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

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

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

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

Indicates whether chassis fan MUX A is installed Enumeration: 'yes': 1, 'no': 0.

Indicates whether chassis fan MUX A is functional Enumeration: 'yes': 1, 'no': 0.

Indicates whether chassis fan MUX B is installed Enumeration: 'yes': 1, 'no': 0.

Indicates whether chassis fan MUX B is functional Enumeration: 'yes': 1, 'no': 0.

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

Standby MM BIST Real Time Clock test result. The time of the last update can be obtained by querying rbistUpdateTime object. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

Standby MM BIST Local I2C bus test result. The time of the last update can be obtained by querying rbistUpdateTime object. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

Standby MM BIST external ethernet port test result. The time of the last update can be obtained by querying rbistUpdateTime object. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

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. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

Standby MM BIST internal external switch test result. The time of the last update can be obtained by querying rbistUpdateTime object. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

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. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

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. Enumeration: 'testFailed': 1, 'testSucceeded': 0.

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

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

The chassis fans that were installed on the chassis when the standby MM was once primary. The time of the last update can be obtained by querying rbistUpdateTimePrimary object. They are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number of chassis fans supported. If it is installed in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if it is installed in bay 1, and 2 are supported, the string would look like '10'.

The chassis fans installed on the chassis that were functional when the standby MM was once primary. The time of the last update can be obtained by querying rbistUpdateTimePrimary object. They are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number supported. If it is installed and functional in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if one is installed and functional only in bay 1, and 2 are supported, the string would look like '10'.

Indicates whether a rear LED card is installed Enumeration: 'yes': 1, 'no': 0.

Indicates whether a rear LED card is communicating Enumeration: 'yes': 1, 'no': 0.

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. Enumeration: 'yes': 1, 'no': 0.

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'. Enumeration: 'yes': 1, 'no': 0.

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

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

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

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

Indicates whether chassis fan MUX A is installed Enumeration: 'yes': 1, 'no': 0.

Indicates whether chassis fan MUX A is functional Enumeration: 'yes': 1, 'no': 0.

Indicates whether chassis fan MUX B is installed Enumeration: 'yes': 1, 'no': 0.

Indicates whether chassis fan MUX B is functional Enumeration: 'yes': 1, 'no': 0.

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

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

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

Fan Pack entry

Fan Pack sequence index.

Indicates whether the fan pack specified exists or not. Enumeration: 'true': 1, 'false': 0.

The health state for the fan pack. Note that the other UIs may use slightly different terminology for the three health state values, as such: WEB - Normal, Attention, Critical CLI - OK, Non-critical, Critical Enumeration: 'unknown': 0, 'bad': 3, 'good': 1, 'warning': 2.

The number of fans in the fan pack. Enumeration: 'unknown': 255.

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.

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.

The health state for the controller for the fan pack. Enumeration: 'unknown': 255, 'flashing': 1, 'communicationError': 3, 'notPresent': 2, 'operational': 0.

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. Enumeration: 'systemLevel': 4, 'critical': 0, 'nonCritical': 2, 'normal': 255.

Table of System Health summary. Contains more detailed information about the reasons for the overall system health status.

System Health Summary entry

System health summary index.

System health summary severity.

System health summary description.

System health summary date time.

System health summary auxilliary event data. If auxilliary event data is available, it is device-specific event data provided to the CMM by the device.

System health summary event ID.

Indicates whether the front panel system error LED is on or off. Enumeration: 'on': 1, 'off': 0.

Indicates whether the front panel system information LED is on or off. For Write access, the LED can be turned off only. Enumeration: 'on': 1, 'off': 0.

Indicates whether the front panel identity LED is on or off. Enumeration: 'notAvailable': 3, 'on': 1, 'off': 0, 'blinking': 2.

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.

Blade system status entry

Blade LED table index.

The numeric blade ID. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

Indicates whether the blade specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates the power state of the blade specified. Enumeration: 'standby': 3, 'on': 1, 'hibernate': 4, 'off': 0, 'unknown': 255.

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 MM is currently in the process of discovering this blade. Communications Error: The MM failed to communicate with this blade. No Power: No power to the blade's domain. Flashing: Flashing in progress. Initialization Failure: Blade failed to initialized. Insufficient Power: Not enough power is left in the blade's domain to power the blade. Power Denied: Power was denied to the blade. Enumeration: 'insufficientPower': 10, 'good': 1, 'maintMode': 12, 'noPower': 7, 'unknown': 0, 'commError': 6, 'powerDenied': 11, 'warning': 2, 'critical': 3, 'discovering': 5, 'flashing': 8, 'initFailure': 9, 'kernelMode': 4, 'firehoseDump': 13.

The name of the blade as a null terminated string.

Indicates whether the blade fault LED is on or off. Enumeration: 'on': 1, 'off': 0.

Indicates whether the blade check log information LED is on or off. For Write access, the LED can be turned off only. Enumeration: 'on': 1, 'off': 0.

Indicates whether the blade identify LED is on, off, or blinking. Enumeration: 'on': 1, 'off': 0, 'blinking': 2.

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.

Blade LEDs Details entry

The LED index number.

The bay number of the main server blade that the LED is grouped into.

Type of the component/subcomponent grouping for this LED.

Text label for a LED.

Text description which denotes color or on/off/blink state for a LED. Enumeration: 'on': 1, 'off': 0, 'blinking': 2.

Location of this LED.

Table of switch module LEDs information.

Switch module LEDs information entry

Switch module LEDs table index.

The bay number of the switch.

The name associated with the LED.

NOTE: This table entry is read-write ONLY when Label = 'Enclosure Identity'. All other Label values have read-only access. Enumeration: 'on': 1, 'off': 0, 'blinking': 2.

The physical location where the LED can be found on the Switch.

Table of chassis fan LEDs information.

Chassis fan LEDs information entry

Chassis fan LEDs table index.

The numeric chassis fan ID. Enumeration: 'chassisfan2': 2, 'chassisfan3': 3, 'chassisfan1': 1, 'chassisfan6': 6, 'chassisfan7': 7, 'chassisfan4': 4, 'chassisfan5': 5, 'chassisfan10': 10, 'chassisfan8': 8, 'chassisfan9': 9.

Indicates whether the chassis fan specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates whether the chassis fan error LED is on, off, or not available. Enumeration: 'notAvailable': 2, 'on': 1, 'off': 0.

Table of fan pack LEDs information. This table is deprecated because the LEDs for the power modules' fans are no longer on the fan packs, the LEDs are on the power modules. See the MIB tables, componentLEDsTable and componentLEDsDetailsTable, for the power modules' LEDs. NOTE: Fan packs are also referred to as Power Module Cooling Devices.

Fan Pack LEDs information entry

Fan Pack LEDs table index.

The numeric fan pack ID. Enumeration: 'fanPack1': 1, 'fanPack2': 2, 'fanPack3': 3, 'fanPack4': 4, 'fanPack5': 5, 'fanPack6': 6.

Indicates whether the fan pack specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates whether the fan pack error LED is on or off. Enumeration: 'notAvailable': 2, 'on': 1, 'off': 0.

Table of Fuel Gauge information.

Fuel Gauge entry

Fuel Gauge Table Index.

Fuel Gauge Table Power Domain Number. Enumeration: 'powerDomain1': 1.

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.

Fuel Gauge Table Power Module capacity in Watts in the power domain.

Power Management Policy Setting for each power domain. A new powerPolicyTable has been added which provides more detailed information regarding a domains power policy information. This table also has the capability to SET the power policy for a given domain. Power Module Redundancy Intended for a single power source into the chassis where each Power Module is on its own dedicated circuit. Maximum power is limited to one less than the number of Power Modules when more than one Power Module is present. One Power Module can fail without affecting compute node operation. Multiple Power Module failures can cause the chassis to power off. Note that some compute nodes may not be allowed to power on if doing so would exceed the policy power limit. Power Module Redundancy with Compute Nodes Throttling Allowed Very similar to Power Module Redundancy. This policy allows for a higher power limit; however, capable compute nodes may be allowed to throttle down if one Power Module fails. Basic Power Management Maximum power limit is higher than other policies and is limited only by the nameplate power of all the Power Modules combined. This is the least conservative approach, since it does not provide any protection for power source or Power Module failure. If any single power supply fails, compute node and/or chassis operation may be affected. Power Source Redundancy Intended for dual power sources into the chassis. Maximum power is limited to the capacity of half the number of installed power modules. This is the most conservative approach and is recommended when all power modules are installed. When the chassis is correctly wired with dual power sources, one power source can fail without affecting compute node server operation. Note that some compute nodes may not be allowed to power on if doing so would exceed the policy power limit. Power Source Redundancy with Compute Node Throttling Allowed Very similar to the Power Source Redundancy. This policy allows for a higher power limit, however capable compute nodes may be allowed to throttle down if one power source fails. Enumeration: 'power-module-redundancy-throttle': 1, 'power-source-redundancy': 3, 'notApplicable': 255, 'power-source-redundancy-throttle': 4, 'basic': 2, 'power-module-redundancy': 0.

This field displays the total available power for each power domain based on installed power modules and the current Power Management Policy Setting.

This field displays the power that has been reserved in each power domain.

This field displays the remaining power available in each domain. Remaining Power = Total Power minus Power In Use

This field displays the total power being used in each power domain.

Table of Power Domain 1.

Fuel Gauge entry

Power Domain 1 Table Index.

Power Domain 1 Table Bay Number. The following Bay Number IDs are used: notApplicable(1), notApplicable(2), fanPackBay1(3), fanPackBay2(4), fanPackBay3(5), fanPackBay4(6), fanPackBay5(7), fanPackBay6(8), chassisfanBay1(9), chassisfanBay2(10), chassisfanBay3(11), chassisfanBay4(12), chassisfanBay5(13), chassisfanBay6(14), chassisfanBay7(15), chassisfanBay8(16), chassisfanBay9(17), chassisfanBay10(18), managementModuleBay1(19), managementModuleBay2(20), ioModuleBay1(21), ioModuleBay2(22), ioModuleBay3(23), ioModuleBay4(24), serverBladeBay1(25), serverBladeBay2(26), serverBladeBay3(27), serverBladeBay4(28), serverBladeBay5(29), serverBladeBay6(30), serverBladeBay7(31), serverBladeBay8(32), serverBladeBay9(33), serverBladeBay10(34), serverBladeBay11(35), serverBladeBay12(36), serverBladeBay13(37), serverBladeBay14(38), notApplicable(39)

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. Enumeration: 'notApplicable': 255, 'yes': 1, 'no': 0.

Power Domain 1 Table Module Throttle Status. Enumeration: 'insufficientPower': 0, 'notApplicable': 255, 'moduleNotThrottling': 2, 'moduleIsThrottling': 1.

Power Domain 1 Table Module Name.

Power Domain 1 Table Module State. Enumeration: 'on': 1, 'hibernate': 4, 'off': 3, 'standby': 0, 'notApplicable': 255, 'notPresent': 2.

Power Domain 1 Table Allocated Power Current indicates the current power allocation for the module in Watts. NOTE: When a server blade spans multiple slots (e.g. double wide or triple wide), the current power allocation for the module is equally divided among the slots.

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

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

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

Power Domain 1 Table Module Throttle indicates whether the server blade may be allowed to throttle or not. Enumeration: 'notApplicable': 255, 'yes': 1, 'no': 0.

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 Enumeration: 'dynamicPowerMeasurementWithPowerCapping': 6, 'fixedPowerManagement': 2, 'dynamicPowerManagement': 3, 'dynamicPowerMeasurement1': 4, 'noAbility': 0, 'notApplicable': 255, 'staticPowerManagement': 1, 'dynamicPowerMeasurement2': 5.

Power Domain 1 Table Module Measured Or Static. Enumeration: 'measured': 1, 'static': 0, 'notApplicable': 255.

The topology path for the component in this table. The chassis and each installed component is represented by a hardware topology tree, where each node in the tree represents a component. The path to a particular component consists of one or more , pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade POWER, 0x04 Power Supply, Power Module, etc COOLING, 0x05 Fan, blower, or other cooling device IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge MEDIA, 0x07 Media device PROCESSOR, 0x08 Any processor, processor module, etc STORAGE, 0x09 Any type of storage device EXPANSION, 0x0A Expansion Card (not covered by more specific type) MEMORY, 0x0B Any memory device, module, etc MFRU, 0x0C Managed FRU Device PANEL, 0x0D Any sort of panel device, such as a front panel BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc CARD_EXPANSION, 0x0F Expansion card, ie. daughter card CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card INTERPOSER, 0x11 Interposer device CLOCK, 0x12 Clock card MUX, 0x13 Mulitplexer card ADDIN, 0x14 cKVM card & other addin cards STORAGE_MODULE, 0x15 Container of one or more Storage Devices SYS_EXPANSION_CARD, 0x16 Management card BATTERY, 0x17 A single battery BATTERY_MODULE, 0x18 Container of one or more batteries REAR_LED, 0x19 Rear LED card MEMORY_BANK, 0x1A Memory banks AIR_FILTER, 0x1B Filter mechanism (bezel) SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports PARENT, 0x1D Reference to parent for multi-parent support PHY_PORT, 0x1E Physical port IO_EXPANDER, 0x1F RAID card CABLE, 0x20 Cable/Interconnect FAN_MUX 0x29 Fan multiplexer card PCI_EXPRESS, 0x32 PCI express card on (PEN) FLASH_DIMM, 0x33 Used for SPD devices that matches the silkscreen of the DIMM slot RACK, 0x50 Rack PLATFORM, 0x51 Generic Platform like rack mounted server/appliance DATAPLEX, 0x52 DataPlex OTHER, 0x53 Other unknown etc. PERIPHERAL_MODULE, 0x54 SYSTEM_BOARD, 0x55 System board PROCESSOR_MODULE, 0x56 BACK_PANEL, 0x57 POWER_SYSTEM_BOARD, 0x58 STORAGE_BACKPLANE, 0x59 Drive back plane PROC_BOARD, 0x5A Holds 1 or more processors POWER_DI, 0x5B Power mgt / power distribution board CHASSIS_BACK_PANEL, 0x5C SUB_CHASSIS, 0x5D OTHER_CHASSIS_BOARD, 0x5E DEVICE_MODULE, 0x5F REMOTE_DEVICE, 0x60 Remote mgt communication device EXTERNAL_ENVIRONMENT, 0x61 Such as external temp sensor for outside box temps PROC_MEMORY_MODULE, 0x62 Processors and memory on same module

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. Enumeration: 'last6Hours': 1, 'lastHour': 0, 'last24Hours': 3, 'last12Hours': 2.

Table of Power Domain 1 Power Trending Information.

Power Domain 1 Power Trending Sample entry.

Power Domain 1 Power Trending Sample Table Index.

Power Domain 1 Power Trending Sample Table Timestamp.

Power Domain 1 Power Trending Table Average Power.

Table of Blade Module Details.

Blade Module Details entry.

Blade Module Details Table Index.

Blade Module Details Table Blade Id. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

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. Blade must be powered on to set this value. If the value of maximum power config is zero, it means the blade doesn't support the power capping feature

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

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

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. Enumeration: 'notApplicable': 255, 'enable': 1, 'disable': 0.

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. Enumeration: 'notApplicable': 255, 'enable': 1, 'disable': 0.

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. Enumeration: 'notApplicable': 255, 'enable': 1, 'disable': 0.

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. Enumeration: 'none': 0, 'psave': 3, 'notApplicable': 255, 'measurementpsave': 4, 'measurement': 1, 'measurementpcap': 2, 'measurementpcappsave': 5.

Blade Module Details Table power capping Minimum value in watts. The blade must support the advanced power management feature. If the value of Pcap Min is 'notApplicable', it means the blade doesn't support the power capping feature. If the value of Pcap Min is 'notAvailable', it means the data could not be obtained.

Blade Module Details Table power capping Guaranteed Minimum value in watts. The blade must support the advanced power management feature. If the value of Pcap Guaranteed Min is 'notApplicable', it means the blade doesn't support the power capping feature. If the value of Pcap GuaranteedMin is 'notAvailable', it means the data could not be obtained.

Blade Module Details Table power capping Maximum value in watts. The blade must support the advanced power management feature. If the value is ' Watts, Watts', which means, - if bladeDetailsDynamicPowerSaver is enabled, it is - otherwise it is If the value of Pcap Max is 'notApplicable', it means the blade doesn't support the power capping feature. If the value of Pcap Min is 'notAvailable', it means the data could not be obtained.

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. Since the power trending data is constantly being computed and saved in the management application database, some queries of the bladePowerTrendingSampleTable may not provide information for a very short window of time. If the table returns empty, please wait a short period and retry the query. Enumeration: 'last6Hours': 1, 'lastHour': 0, 'last24Hours': 3, 'last12Hours': 2.

Blade Module Power Trending Blade Id. NOTE: The Blade Id should be configured before displaying the bladePowerTrendingTable. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

The topology Path is a location identifier for a blade. The chassis and each installed blade is represented by a hardware topology tree, where each node in the tree represents a blade. The path to a particular blade consists of one or more , pairs, where each successive pair is a child of the previous parent pair. This topology path is used to identify blades such as blade storage devices. Some examples. A storage blade with a controller card plugged into slot 1 topology location would be represented as : 010103010301--> Storage Controller card #1 of Sub-Chassis #1 A storage blade with a controller card plugged into slot 2 topology location would be represented as : 010103010302--> Storage Controller card #2 of Sub-Chassis #1

Table of Blade Module Power Trending Information. Since the power trending data is constantly being computed and saved in the management application database, some queries of this table may not provide information for a very short window of time. If the table data returns empty,please wait a short period and retry the query.

Blade Module Power Trending Sample entry.

Blade Module Power Trending Sample Table Index.

Blade Module Power Trending Sample Table Blade Id. If the blade is defined using a topology location by using the scalar bladePowerTrendingTopologyPath, a zero will be displayed in the bladePowerTrendingSampleId. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

Blade Module Power Trending Sample Table Timestamp.

Blade Module Power Trending Sample Table Maximum Power.

Blade Module Power Trending Sample Table Minimum Power.

Blade Module Power Trending Sample Table Average Power.

Blade module topology path. This field will have a topology location when a blade is a storage blade or a blade defined with a sub chassis. If the blade is defined with a primary slot location by using the scalar bladePowerTrendingBladeId, 'not applicable' will be displayed in the bladePowerTrendingSampleTopologyId.

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. Enumeration: 'last6Hours': 1, 'lastHour': 0, 'last24Hours': 3, 'last12Hours': 2.

Switch Module Power Trending Switch Id. NOTE: The Switch Id should be configured before displaying the switchPowerTrendingTable. Enumeration: 'module4': 4, 'module3': 3, 'module2': 2, 'module1': 1.

Table of Switch Module Power Trending Information.

Switch Module Power Trending Sample entry.

Switch Module Power Trending Sample Table Index.

Switch Module Power Trending Sample Table Switch Id. Enumeration: 'module10': 10, 'module9': 9, 'module8': 8, 'module7': 7, 'module6': 6, 'module5': 5, 'module4': 4, 'module3': 3, 'module2': 2, 'module1': 1.

Switch Module Power Trending Sample Table Timestamp.

Switch Module Power Trending Sample Table Maximum Power.

Switch Module Power Trending Sample Table Minimum Power.

Switch Module Power Trending Sample Table Average Power.

Specify time period for chassis fan module power trending information table view. NOTE: This time period should be configured before displaying the following Power Trending Information table for chassis fan module. Enumeration: 'last6Hours': 1, 'lastHour': 0, 'last24Hours': 3, 'last12Hours': 2.

Chass fan mModule power trending fan ID. NOTE: The ID should be configured before displaying the chassisFanPowerTrendingTable. Enumeration: 'chassisFan2': 2, 'chassisFan3': 3, 'chassisFan1': 1, 'chassisFan6': 6, 'chassisFan7': 7, 'chassisFan4': 4, 'chassisFan5': 5, 'chassisFan10': 10, 'chassisFan8': 8, 'chassisFan9': 9.

Table of chassis fan Module Power Trending Information.

Chassis fan Module Power Trending Sample entry.

Chassis fan Module Power Trending Sample Table Index.

Chassis fan Module Power Trending Sample Table Id. Enumeration: 'chassisFan2': 2, 'chassisFan3': 3, 'chassisFan1': 1, 'chassisFan6': 6, 'chassisFan7': 7, 'chassisFan4': 4, 'chassisFan5': 5, 'chassisFan10': 10, 'chassisFan8': 8, 'chassisFan9': 9.

Chassis fan Module Power Trending Sample Table Timestamp.

Chassis fan Module Power Trending Sample Table Maximum Power.

Chassis fan Module Power Trending Sample Table Minimum Power.

Chassis fan Module Power Trending Sample Table Average Power.

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.

Chassis total power being used, which displays the total power being consumed by all modules in the chassis. It also includes power consumed by the blowers (chassis cooling devices) for the chassis.

Chassis total thermal output, which displays the thermal output (load) in BTUs per hour. It is calculated based on the total input power in use. (1 Watt = 3.412 BTU/hour).

The chassis power service mode. NOTE: This MIB object is for BCS only. This object has been deprecated. See the object, powerModuleDescription, for similar information. Enumeration: 'volt220': 2, 'notAvailable': 255, 'volt110': 1.

Specify time period of power trending information. NOTE: This time period should be configured before displaying the following Power Trending Information table for Chassis. Enumeration: 'last6Hours': 1, 'lastHour': 0, 'last24Hours': 3, 'last12Hours': 2.

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

Chassis Power Trending Sample entry in specified time period.

Chassis Power Trending Sample Index in specified time period.

Chassis Power Trending Sample Timestamp in specified time period.

Chassis Power Trending Sample Average Power in specified time period.

Specify time period of thermal trending information. NOTE: This time period should be configured before displaying the following Thermal Trending Information table for Chassis. Enumeration: 'last6Hours': 1, 'lastHour': 0, 'last24Hours': 3, 'last12Hours': 2.

Table of rear LED card Thermal Trending Information.

Rear LED Card Thermal Trending entry.

Rear LED Card Thermal Trending Table Index.

Rear LED Card Thermal Trending Table Sample Timestamp.

Rear LED Card Thermal Trending Table Average Temperature.

Rear LED Card Thermal Trending Table Minumum Temperature.

Rear LED Card Thermal Trending Table Maximum Temperature.

Table of Cubic Feet per Minute Thermal Trending Information.

Chassis CFM Thermal Trending entry.

Cubic Feet per Minute Thermal Trending Table Index.

Cubic Feet per Minute Thermal Trending Table Sample Timestamp.

Cubic Feet per Minute Thermal Trending Table The Current CFM of air flow calculated at this sample time.

Cubic Feet per Minute Thermal Trending Table The Maximum CFM of air flow the chassis can provide at this sample time.

Table of Exhaust Heat Index Thermal Trending Information.

Chassis Exhaust Heat Index Thermal Trending entry.

Exhaust Heat Index Thermal Trending Table Index.

Chassis Exhaust Heat Index Thermal Trending Table Sample Timestamp.

Chassis Exhaust Heat Index Thermal Trending Table Minimum Exhaust Heat Index since last reboot.

Chassis Exhaust Heat Index Thermal Trending Table Maximum Exhaust Heat Index since last reboot.

Chassis Exhaust Heat Index Thermal Trending Table Average of last 2 Exhaust Heat Index calculations since last reboot.

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.

Power Policy Entry

The unique idenitifier of a row in the powerPolicyTable.

The power domain number which this row is associated with. Enumeration: 'powerDomain1': 1, 'powerDomain2': 2.

The short name of the power policy. The following are the possible names and their detailed description: Power Module Redundancy Intended for a single 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 power source or Power Module failure. If any single power supply fails, blade and/or chassis operation may be affected. Power Source Redundancy Intended for dual 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 power sources, one 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. Power Source Redundancy with Blade Throttling Allowed Very similar to the Power Source Redundancy policy. This policy allows you to draw more total power; however, capable blades may be allowed to throttle down if one power source fails.

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

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

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

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 MM 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. Enumeration: 'disabled': 0, 'enabled': 1.

Table of MM users currently logged in.

MM users currently logged in entries.

Index for MM users currently logged in.

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

Access method for MM users currently logged in.

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

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

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

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

Machine chassis manufacturing ID.

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.

Machine chassis FRU number.

Machine chassis manufacture date.

Machine chassis part number.

Machine chassis FRU serial number.

Machine chassis manufacturer ID Number.

Machine chassis product ID.

Machine chassis subsystem manufacturer.

Machine chassis Common Language Equipment Identification (CLEI).

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.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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.

Table of MM Firmware VPD.

MM Firmware VPD entry.

Firmware VPD index.

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

Firmware VPD build identification.

Firmware VPD revision number.

Firmware VPD file name.

Firmware VPD build date.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

Blade expansion card (daughter card) VPD type. For consistent results, view as a table and not as individual entries. Enumeration: 'unknown': 0, 'storageExpansion': 2, 'pciExpansion': 3, 'networkExpansion': 1, 'genericExpansion': 4.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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. Enumeration: 'bladeNetworkCNAExpCard': 12, 'bladeEthernetExpCard': 1, 'unknown': 0, 'bladeIscsiExpCard': 6, 'bladeSASConnectivityCard': 9, 'bladeSATAConnectivityCard': 10, 'bladeNetworkCFFeExpCard': 8, 'bladeNetworkCFFzExpCard': 11, 'bladeGenericExpCard': 7, 'bladeOpticalPassThrough': 4, 'bladeInfinibandExpCard': 5, 'bladeFiberChannelExpCard': 2, 'serialPortExpCard': 3.

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. Enumeration: 'notApplicable': 255, 'yes': 1, 'no': 0.

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.

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.

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

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

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

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

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.

Blade or expansion card WWN/GUID/SAS Type. For consistent results, view as a table and not as individual entries. Enumeration: 'notAvailable': 0, 'sas': 3, 'guid': 2, 'wwn': 1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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.

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

Blade firmware VPD table entry

Blade firmware VPD table index.

The numeric blade ID. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

Indicates whether the server blade specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates the power state of the blade specified. Enumeration: 'standby': 3, 'on': 1, 'hibernate': 4, 'off': 0.

The name of the blade as a null terminated string.

The build ID for the blade firmware.

The revision of the blade firmware.

The date of the blade firmware.

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

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

Blade firmware VPD table entry

Blade firmware VPD table index.

The numeric blade ID. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

Indicates whether the server blade specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates the power state of the blade specified. Enumeration: 'standby': 3, 'on': 1, 'hibernate': 4, 'off': 0.

The name of the blade as a null terminated string.

The build ID for the blade firmware.

The revision of the blade firmware.

The date of the blade firmware.

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

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

Blade firmware VPD table entry

Blade firmware VPD table index.

The numeric blade ID. Enumeration: 'blade14': 14, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

Indicates whether the server blade specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates the power state of the blade specified. Enumeration: 'standby': 3, 'on': 1, 'hibernate': 4, 'off': 0.

The name of the blade as a null terminated string.

The build ID for the blade firmware.

The revision of the blade firmware.

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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.

Switch module main application VPD information table.

Switch module main application VPD table entry

Switch module main application VPD entry index.

The switch module numeric identifier. Enumeration: 'module10': 10, 'module9': 9, 'module8': 8, 'module7': 7, 'module6': 6, 'module5': 5, 'module4': 4, 'module3': 3, 'module2': 2, 'module1': 1.

Indicates whether the switch module specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates the type of switch module installed. Enumeration: 'serialCM': 4, 'fibre': 2, 'infiniband': 6, 'unknown': 0, 'highSpeed': 20, 'passThrough': 30, 'ethernet': 1, 'sas': 40, 'opm': 3, 'copperPassThrough': 5.

Switch module firmware build id.

Switch module firmware build date.

Switch module firmware revision number.

Switch module firmware build id.

Switch module firmware build date.

Switch module firmware revision number.

I/O Module firmware build id.

I/O Module firmware build date.

I/O Module firmware revision number.

Indicates the subtype of switch module installed. Enumeration: 'fibre': 2, 'infiniband': 6, 'icpm': 9, 'unknown': 0, 'sas': 7, 'ethernet': 1, 'raidsas': 8.

Switch module boot ROM VPD information table.

Switch module boot ROM VPD table entry

Switch module boot ROM VPD entry index.

The switch module numeric identifier. Enumeration: 'module10': 10, 'module9': 9, 'module8': 8, 'module7': 7, 'module6': 6, 'module5': 5, 'module4': 4, 'module3': 3, 'module2': 2, 'module1': 1.

Indicates whether the switch module specified exists or not. Enumeration: 'true': 1, 'false': 0.

Indicates the type of switch module installed. Enumeration: 'serialCM': 4, 'fibre': 2, 'infiniband': 6, 'unknown': 0, 'highSpeed': 20, 'passThrough': 30, 'ethernet': 1, 'sas': 40, 'opm': 3, 'copperPassThrough': 5.

Switch module firmware build ID.

Switch module firmware build date.

Switch module firmware revision number.

Indicates the subtype of switch module installed. Enumeration: 'fibre': 2, 'infiniband': 6, 'icpm': 9, 'unknown': 0, 'sas': 7, 'ethernet': 1, 'raidsas': 8.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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.

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

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

Rear LED card 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.

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

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

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

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

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

Rear LED card 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.

Rear LED card hardware VPD Manufacture Date.

Rear LED card hardware VPD Part Number.

Rear LED card hardware VPD FRU Serial.

Table of chassis fan controller firmware vital product data (VPD) information.

Chassis fan controller firmware VPD table entry

Chassis fan controller firmware VPD table index.

The numeric chassis fan ID. Enumeration: 'chassisFan2': 2, 'chassisFan3': 3, 'chassisFan1': 1, 'chassisFan6': 6, 'chassisFan7': 7, 'chassisFan4': 4, 'chassisFan5': 5, 'chassisFan10': 10, 'chassisFan8': 8, 'chassisFan9': 9.

Indicates whether the chassis fan specified exists or not. Enumeration: 'true': 1, 'false': 0.

The revision of the chassis fan controller firmware.

Table of the chassis fan hardware components.

Chassis fan hardware VPD entry.

Chassis fan hardware VPD index.

Chassis fan hardware VPD Bay number.

Chassis fan hardware VPD manufacturing ID.

Chassis fan hardware VPD FRU number.

Chassis fan hardware VPD hardware revision.

Chassis fan hardware VPD UUID.

Chassis fan hardware VPD manufacture Date.

Chassis fan hardware VPD Part Number.

Chassis fan hardware VPD FRU serial number.

Chassis fan hardware VPD manufacturer ID.

Chassis fan hardware VPD product ID.

Chassis fan hardware VPD subsystem manufacturer ID.

Chassis fan hardware VPD Common Language Equipment Identifier (CLEI).

Chassis fan hardware VPD hardware revision in string format.

Table of Power Module controller firmware vital product data (VPD) information.

Power Module controller firmware VPD table entry

Power Module controller firmware VPD table index.

The numeric Power Module ID. Enumeration: 'powerModule5': 5, 'powerModule4': 4, 'powerModule6': 6, 'powerModule1': 1, 'powerModule3': 3, 'powerModule2': 2.

Indicates whether the Power Module specified exists or not. Enumeration: 'true': 1, 'false': 0.

The revision of the Power Module controller firmware.

Table of system component hardware VPD activity log. For consistent results, view as a table and not as individual entries.

System component hardware VPD activity log entry. For consistent results, view as a table and not as individual entries.

System component level VPD activity log index. For consistent results, view as a table and not as individual entries.

System component level VPD activity log FRU number. For consistent results, view as a table and not as individual entries.

System component level VPD activity log serial number. For consistent results, view as a table and not as individual entries.

System component level VPD activity log manufacturing ID. For consistent results, view as a table and not as individual entries.

System component level VPD activity log Bay number. For consistent results, view as a table and not as individual entries.

System component level VPD activity log action (added/removed). For consistent results, view as a table and not as individual entries.

System component level VPD activity log timestamp. For consistent results, view as a table and not as individual entries.

The module name which this row is associated with. For consistent results, view as a table and not as individual entries.

The chassis and each installed component is represented by a hardware topology tree, where each node in the tree represents a component. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. The topology path's numeric designations for the components are: CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade POWER, 0x04 Power Supply, Power Module, etc COOLING, 0x05 Fan, blower, or other cooling device IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge MEDIA, 0x07 Media device PROCESSOR, 0x08 Any processor, processor module, etc STORAGE, 0x09 Any type of storage device EXPANSION, 0x0A Expansion Card (not covered by more specific type) MEMORY, 0x0B Any memory device, module, etc MFRU, 0x0C Managed FRU Device PANEL, 0x0D Any sort of panel device, such as a front panel BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc CARD_EXPANSION, 0x0F Expansion card, ie. daughter card CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card INTERPOSER, 0x11 Interposer device CLOCK, 0x12 Clock card MUX, 0x13 Mulitplexer card ADDIN, 0x14 cKVM card & other addin cards STORAGE_MODULE, 0x15 Container of one or more Storage Devices SYS_EXPANSION_CARD, 0x16 Management card BATTERY, 0x17 A single battery BATTERY_MODULE, 0x18 Container of one or more batteries REAR_LED, 0x19 Rear LED card MEMORY_BANK, 0x1A Memory banks AIR_FILTER, 0x1B Filter mechanism (bezel) SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports PARENT, 0x1D Reference to parent for multi-parent support PHY_PORT, 0x1E Physical port IO_EXPANDER, 0x1F RAID card CABLE, 0x20 Cable/Interconnect FAN_MUX, 0x29 Fan multiplexer card PCI_EXPRESS, 0x32 PCI express card on (PEN) FLASH_DIMM, 0x33 Used for SPD devices that matches the silkscreen of the DIMM slot RACK, 0x50 Rack PLATFORM, 0x51 Generic Platform like rack mounted server/appliance DATAPLEX, 0x52 DataPlex OTHER, 0x53 Other unknown etc. PERIPHERAL_MODULE, 0x54 SYSTEM_BOARD, 0x55 System board PROCESSOR_MODULE, 0x56 BACK_PANEL, 0x57 POWER_SYSTEM_BOARD, 0x58 STORAGE_BACKPLANE, 0x59 Drive back plane PROC_BOARD, 0x5A Holds 1 or more processors POWER_DI, 0x5B Power mgt / power distribution board CHASSIS_BACK_PANEL, 0x5C SUB_CHASSIS, 0x5D OTHER_CHASSIS_BOARD, 0x5E DEVICE_MODULE, 0x5F REMOTE_DEVICE, 0x60 Remote mgt communication device EXTERNAL_ENVIRONMENT, 0x61 Such as external temp sensor for outside box temps PROC_MEMORY_MODULE, 0x62 Processors and memory on same module

Reload all VPD data (firmware, hardware, MAC address, WWN/GUID and other Unique ID). NOTE: The value returned for the GET command is meaningless. Enumeration: 'execute': 1.

Reload firmware VPD data. NOTE: The value returned for the GET command is meaningless. Enumeration: 'execute': 1.

Reload hardware VPD data. NOTE: The value returned for the GET command is meaningless. Enumeration: 'execute': 1.

Reload blade MAC addresses. NOTE: The value returned for the GET command is meaningless. Enumeration: 'execute': 1.

Reload blade and I/O module WWN/GUID and other VPD data. NOTE: The value returned for the GET command is meaningless. Enumeration: 'execute': 1.

Disable/Enable/Reset the passive air filter. When enabled, sending an enable or reset will reset the replace date. Enumeration: 'disabled': 0, 'reset': 2, 'enabled': 1.

The chassis environment. 1 month indicates high dust, 3 months indicates moderate dust and, 6 months indicates low dust. Enumeration: 'sixMonths': 6, 'threeMonths': 3, 'oneMonth': 1.

The scheduled replacement date of the air filter.

Table of component inventory information. Not all components will provide every object defined in the ComponentInventoryEntry. Also, if a component does not have inventory information or the CMM is not able to read the data from the device, then there will not be a row in this table for the component.

Component inventory information.

The unique identifier for a row in this table. The chassis and each installed component is represented by a hardware topology tree, where each node in the tree represents a component. The path to a particular component consists of one or more , pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. This component inventory table is indexed by this unique topology path and the numeric designations for the components are: CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade POWER, 0x04 Power Supply, Power Module, etc COOLING, 0x05 Fan, blower, or other cooling device IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge MEDIA, 0x07 Media device PROCESSOR, 0x08 Any processor, processor module, etc STORAGE, 0x09 Any type of storage device EXPANSION, 0x0A Expansion Card (not covered by more specific type) MEMORY, 0x0B Any memory device, module, etc MFRU, 0x0C Managed FRU Device PANEL, 0x0D Any sort of panel device, such as a front panel BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc CARD_EXPANSION, 0x0F Expansion card, ie. daughter card CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card INTERPOSER, 0x11 Interposer device CLOCK, 0x12 Clock card MUX, 0x13 Mulitplexer card ADDIN, 0x14 cKVM card & other addin cards STORAGE_MODULE, 0x15 Container of one or more Storage Devices SYS_EXPANSION_CARD, 0x16 Management card BATTERY, 0x17 A single battery BATTERY_MODULE, 0x18 Container of one or more batteries REAR_LED, 0x19 Rear LED card MEMORY_BANK, 0x1A Memory banks AIR_FILTER, 0x1B Filter mechanism (bezel) SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports PARENT, 0x1D Reference to parent for multi-parent support PHY_PORT, 0x1E Physical port IO_EXPANDER, 0x1F RAID card CABLE, 0x20 Cable/Interconnect FAN_MUX, 0x29 Fan multiplexer card PCI_EXPRESS, 0x32 PCI express card on (PEN) FLASH_DIMM, 0x33 Used for SPD devices that matches the silkscreen of the DIMM slot RACK, 0x50 Rack PLATFORM, 0x51 Generic Platform like rack mounted server/appliance DATAPLEX, 0x52 DataPlex OTHER, 0x53 Other unknown etc. PERIPHERAL_MODULE, 0x54 SYSTEM_BOARD, 0x55 System board PROCESSOR_MODULE, 0x56 BACK_PANEL, 0x57 POWER_SYSTEM_BOARD, 0x58 STORAGE_BACKPLANE, 0x59 Drive back plane PROC_BOARD, 0x5A Holds 1 or more processors POWER_DI, 0x5B Power mgt / power distribution board CHASSIS_BACK_PANEL, 0x5C SUB_CHASSIS, 0x5D OTHER_CHASSIS_BOARD, 0x5E DEVICE_MODULE, 0x5F REMOTE_DEVICE, 0x60 Remote mgt communication device EXTERNAL_ENVIRONMENT, 0x61 Such as external temp sensor for outside box temps PROC_MEMORY_MODULE, 0x62 Processors and memory on same module

The slot number or instance of a particular component. Typically, if the component plugs into the chassis, this represents the slot number. However, some components are connected to another component, and this represents the instance. For example, a blade may have several expansion cards that connect to the blade system planar, and in this case, this value identifies which expansion card instance the row represents. Note that this slot/instance value can be determined from the componentInventoryTopologyPath object, but this componentInventoryInstance object is provided as a convenience to the user.

A short text string describing the particular component. If a text string is not available, a value of 'Not available' is presented. For more detail, also refer to the componentInventoryProductName object in this table or the componentXXXXName object of any of the other component tables under the 'components' section of the MIB.

The machine type and model number of this component. Typically, the format is XXXXYYY, where XXXX reprsents the machine type and YYY represents the model number.

The machine serial number of this component.

The asset identifier of this component, typically set by some other authority than the manufacturer.

The part number of this component.

The Field Replaceable Unit (FRU) number of this component.

The Field Replaceable Unit (FRU) serial number of this component.

The text description of the manufacturer of this component.

The hardware revision number of the this component.

The date when the manufacturer created this component. The format is XXYY, where XX is the week number of the year 20YY.

The Universally Unique IDentifier (UUID) of this component, represented as a 16 byte hex number.

The product identifier of the component assigned by the manufacturer.

The text sub-description of the manufacturer of this component, often used to identify a supplier for a component which has multiple suppliers.

The Common Language Equipment Identifier (CLEI) of this component.

The asset tag of this component.

A speed designation for the component, for example, processor speed.

A unique identifier assigned by the manufacturer to the component, for example, a processor ID.

A size designation for the component, for example, a memory DIMM size or hard drive capacity.

The architecture specification of a memory device. Enumeration: 'ddrsgram': 6, 'sdram': 4, 'fpmdram': 1, 'ddr3sdram': 11, 'edo': 2, 'multiplexedram': 5, 'edodram': 3, 'ddrsdram': 7, 'ddr2sdrm': 8.

The product name assigned by the manufacturer for this component. For more detail, also refer to the componentInventoryDescription object.

The product version assigned by the manufacturer for this component.

The type designation for processor components. Enumeration: 'central': 3, 'unknown': 2, 'dsp': 5, 'other': 1, 'video': 6, 'math': 4.

The family designation for processor components.

The number of cores present on a processor component.

The number of threads present on a processor component.

The level 1 data cache size of a processor component.

The level 1 instruction cache size of a processor component.

The level 2 cache size of a processor component.

The level 3 cache size of a processor component.

The voltage rating for a processor component.

The external clock speed of a processor component.

The maximum data bus width capability of a processor component, expressed typically in bits.

The identification number assigned for the component by the manufacturer.

The global identifier (GLID) of this component. This ID is a unique identifier for the CMM chassis (midplane), set by the manufacturer. This ID and the associated inventory is passed back to IBM via the Electronic Service Agent and the Call Home feature. This ID and the accompanying chassis inventory will be stored and retained resulting in a configuration/change history file of the inventory for a chassis associated with a particular GLID. This ID can be used by a customer to identify and categorize all the content that resides within a chassis, much like a physical serial number is associated with a single box server.

The timeout value (in seconds) of the cached data for the table, componentInventoryTable. This value is static (constant) and cannot be set.

Table of component firmware information. Not all components will provide every object defined in the ComponentFirmwareEntry.

Component firmware information.

The unique identifier for a component in this table. The chassis and each installed component is represented by a hardware topology tree, where each node in the tree represents a component. The path to a particular component consists of one or more , pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. Note that this TP is preceded by a single octet that specifies the TP length. This is required since this table is indexed with two indices and, therefore, the TP length must be explicitly provided. This component firmware table is indexed by this unique topology path and the numeric designations for the components are: CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade POWER, 0x04 Power Supply, Power Module, etc COOLING, 0x05 Fan, blower, or other cooling device IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge MEDIA, 0x07 Media device PROCESSOR, 0x08 Any processor, processor module, etc STORAGE, 0x09 Any type of storage device EXPANSION, 0x0A Expansion Card (not covered by more specific type) MEMORY, 0x0B Any memory device, module, etc MFRU, 0x0C Managed FRU Device PANEL, 0x0D Any sort of panel device, such as a front panel BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc CARD_EXPANSION, 0x0F Expansion card, ie. daughter card CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card INTERPOSER, 0x11 Interposer device CLOCK, 0x12 Clock card MUX, 0x13 Mulitplexer card ADDIN, 0x14 cKVM card & other addin cards STORAGE_MODULE, 0x15 Container of one or more Storage Devices SYS_EXPANSION_CARD, 0x16 Management card BATTERY, 0x17 A single battery BATTERY_MODULE, 0x18 Container of one or more batteries REAR_LED, 0x19 Rear LED card MEMORY_BANK, 0x1A Memory banks AIR_FILTER, 0x1B Filter mechanism (bezel) SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports PARENT, 0x1D Reference to parent for multi-parent support PHY_PORT, 0x1E Physical port IO_EXPANDER, 0x1F RAID card CABLE, 0x20 Cable/Interconnect FAN_MUX, 0x29 Fan multiplexer card PCI_EXPRESS, 0x32 PCI express card on (PEN) FLASH_DIMM, 0x33 Used for SPD devices that matches the silkscreen of the DIMM slot RACK, 0x50 Rack PLATFORM, 0x51 Generic Platform like rack mounted server/appliance DATAPLEX, 0x52 DataPlex OTHER, 0x53 Other unknown etc. PERIPHERAL_MODULE, 0x54 SYSTEM_BOARD, 0x55 System board PROCESSOR_MODULE, 0x56 BACK_PANEL, 0x57 POWER_SYSTEM_BOARD, 0x58 STORAGE_BACKPLANE, 0x59 Drive back plane PROC_BOARD, 0x5A Holds 1 or more processors POWER_DI, 0x5B Power mgt / power distribution board CHASSIS_BACK_PANEL, 0x5C SUB_CHASSIS, 0x5D OTHER_CHASSIS_BOARD, 0x5E DEVICE_MODULE, 0x5F REMOTE_DEVICE, 0x60 Remote mgt communication device EXTERNAL_ENVIRONMENT, 0x61 Such as external temp sensor for outside box temps PROC_MEMORY_MODULE, 0x62 Processors and memory on same module

Each component may have one or more types of firmware associated with it, and this index object identifies the particular instance.

The slot number or instance of a particular component. Typically, if the component plugs into the chassis, this represents the slot number. However, some components are connected to another component, and this represents the instance. For example, a blade may have several expansion cards that connect to the blade system planar, and in this case, this value identifies which expansion card instance the row represents. Note that this slot/instance value can be determined from the componentFirmwareTopologyPath object, but this componentFirmwareComponentInstance object is provided as a convenience to the user.

A short text string describing the particular component. For the MM and blades, this name will be the configured name or its serial number if no user configured name is available. For all other components, this object will provide text to identify the component. If a text string is not available, a value of 'Not available' is presented. For more detail, also refer to the componentInventoryProductName object.

A text description of the type of firmware load.

A text description of the build identifier for this firmware load.

A text description of the release date for this firmware load.

A text description of the filename of this firmware load.

A text description of the revision level of this firmware load.

A numeric identifier of the revision major number for this firmware load.

A numeric identifier of the revision minor number for this firmware load.

The level status of the firmware build ID. It has three possible values as Different (mismatch firmware build ID), Match (the same firmware build ID), Unique (only one such firmware build ID).

A text description of the build identifier for this pending firmware load.

A text description of the release date for this pending firmware load.

A text description of the revision level of this pending firmware load.

A text description of the firmware release level this firmware load.

This object indicates whether this firmware image is the active (1) firmware,otherwise this firmware image is inactive (0). Enumeration: 'active': 1, 'na': 255, 'inactive': 0.

A text description with the firmware image information.

Indicates the type of firmware load with a numeric identifier. Enumeration: 'mgmtModuleMainApplPendingRestart': 62, 'bladeMP': 6, 'expansionCardGeneric': 101, 'fanController': 81, 'switchModuleMainAppl': 40, 'bladeFwBios': 1, 'expansionCardFcode': 103, 'unknown': 255, 'bladeUEFI': 7, 'bladeSysMgmtProcessor': 3, 'mgmtModuleMainAppl': 61, 'expansionCardMain': 105, 'expansionCardEfi': 102, 'powerSupplyFirmware': 91, 'bladecKVM': 5, 'expansionCardBios': 104, 'bladeDSA': 8, 'bladeDiagnostics': 2, 'switchModuleBootROM': 43, 'switchModuleMainAppl1': 41, 'switchModuleMainAppl2': 42, 'powerSupplyFanController': 92, 'bladeFpga': 4, 'expansionCardMulti': 106.

The timeout value (in seconds) of the cached data for the table, componentFirmwareTable. This value is static (constant) and cannot be set.

Table of firmware levels of installed nodes. This information is grouped by Machine Type/Model and includes two or more nodes with the same Type/Model. This information is intended to be used in determining which components firmware may need upgrade.

Node firmware analysis information.

The index for the node firmware levels.

The machine type or model of node firmware.

The firmware type.

The firmware build id.

The firmware release date.

The firmware revision level.

The node topology.

The node device name.

Table of firmware levels of installed IOMs. This information is grouped by Product Id and includes two or more IOMs with the same product id. This information is intended to be used in determining which components firmware may need upgrade.

IOM firmware analysis information.

The index for the IOM firmware levels.

The IOM product id.

The IOM product name.

The IOM firmware type.

The IOM firmware version.

The IOM release date.

The IOM topology.

When a blade management controller, switch or the MM is reset, the inventory data is refreshed in the MM database. This includes items like IBM VPD (e.g. - serial number, UUID) and MAC address information. Applications need to know when this information has been populated on the MM before they begin to query it using SNMP or other means. This simple flag object will return a ready or notReady indication when all blades and switches have completed initialization and the inventory information has been provided to the MM. Note that due to components that may be experiencing a 'communication failure' or 'initialization failure' condition, this object may continue to show notReady. Therefore, any application that polls this object should also incorporate a timeout A more granular, per-blade status is available via the bladeSystemStatusTable Enumeration: 'notReady': 0, 'ready': 1.

Table of information indicating presence of a disk drive on a component. The management module does not receive any inventory VPD from the component, so only the presence of a drive can be indicated by this table.

Component drive information.

The unique identifier for a row in this table. The chassis and each installed component is represented by a hardware topology tree, where each node in the tree represents a component. The path to a particular component consists of one or more , pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. This component table is indexed by this unique topology path and the numeric designations for the components are: CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade POWER, 0x04 Power Supply, Power Module, etc COOLING, 0x05 Fan, blower, or other cooling device IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge MEDIA, 0x07 Media device PROCESSOR, 0x08 Any processor, processor module, etc STORAGE, 0x09 Any type of storage device EXPANSION, 0x0A Expansion Card (not covered by more specific type) MEMORY, 0x0B Any memory device, module, etc MFRU, 0x0C Managed FRU Device PANEL, 0x0D Any sort of panel device, such as a front panel BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc CARD_EXPANSION, 0x0F Expansion card, ie. daughter card CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card INTERPOSER, 0x11 Interposer device CLOCK, 0x12 Clock card MUX, 0x13 Mulitplexer card ADDIN, 0x14 cKVM card & other addin cards STORAGE_MODULE, 0x15 Container of one or more Storage Devices SYS_EXPANSION_CARD, 0x16 Management card BATTERY, 0x17 A single battery BATTERY_MODULE, 0x18 Container of one or more batteries MEDIA_MODULE, 0x19 Container of one or more media devices MEMORY_BANK, 0x1A Memory banks AIR_FILTER, 0x1B Filter mechanism (bezel) SERIAL_PORT_MODULE, 0x1C Container of one or more serial ports PARENT, 0x1D Reference to parent for multi-parent support PHY_PORT, 0x1E Physical port IO_EXPANDER, 0x1F RAID card

A short text string describing the particular drive on the component.

The timeout value (in seconds) of the cached data for the table, componentDriveTable. This value is static (constant) and cannot be set.

Table of license key information.

License key information entry.

License key component table index. Enumeration: 'blade14': 14, 'switchModule2': 42, 'blade12': 12, 'blade13': 13, 'blade10': 10, 'blade11': 11, 'switchModule4': 44, 'switchModule1': 41, 'switchModule3': 43, 'blade8': 8, 'blade9': 9, 'blade4': 4, 'blade5': 5, 'blade6': 6, 'blade7': 7, 'blade1': 1, 'blade2': 2, 'blade3': 3.

The license key index for the chassis component.

The description for a license key.

The date and time of this license key.

The unique identifier for this license key.

Any other information related to this license key.

The current status of this license key. Enumeration: 'usageExceeded': 4, 'unknown': 0, 'invalid': 2, 'notApplicable': 99, 'valid': 1, 'expired': 3.

Table of chassis license key information.

Chassis License key information entry.

The key index for the chassis license keys.

The name of the Feature for the license key.

The Feature Type Code for the license key.

The description of the license key.

System information for the license key.

Identification of the license key.

Validation of the license key.

The current status of the license key. Enumeration: 'invalidMAC': 3, 'signatureValidationFailed': 4, 'usageExceeded': 6, 'keyExpired': 5, 'notApplicable': 8, 'valid': 0, 'validatingKey': 1, 'invalidMTSN': 2, 'validateElsewhere': 7.

Date and Time (GMT) when license expires.

Number of times remaining for license usage. A negative value indicates that there is no Usage Limit for the license.

Table of event log entry information.

Event log table entry

The event log index number.

A string of data detailing an event.

Clear the event log. NOTE: Value returned for the GET command is meaningless for this MIB object. Enumeration: 'execute': 1.

If disabled, it means the info LED will not turn on when the log gets full and no alerts will be sent out. If enabled, the LED will turn on when the log gets full and alerts will be sent out. Enumeration: 'disabled': 0, 'enabled': 1.

Table of enhanced event log entry information.

Enhaced Event log table entry, new entries could be added for new items.

The event log number for the enhanced event log.

A string of data detailing an event log's attribute, such as the Event ID and Call Home Flag. The Event ID is a hexadecimal number representing an specific or class of events. The call home flag indicates that the corresponding problem may result in a call home.

A string of data detailing an event log message.

The sequence number for the enhanced event log. This number is the next sequence number when this event record was create. This number continues to grow, even if this event log is cleared, until it reaches the maximum value of 4294967295. The next sequence number following the maximum value is 1.

Table of audit log entry information. Audit log includes the logs whose source is 'Audit'

Audit log table entry, new entries could be added for new items.

The audit log number.

A string of data detailing an audit eventlog's attribute.

A string of data detailing an audit event log message.

The sequence number for the audit event log. This number is the next sequence number when this event record was create. This number continues to grow, even if this event log is cleared, until it reaches the maximum value of 4294967295. The next sequence number following the maximum value is 1.

Clear the audit log. NOTE: Value returned for the GET command is meaningless for this MIB object. Enumeration: 'execute': 1.