CME-MIB

type

TEXTUAL-CONVENTION

Represents an IPv6 network address. Since MIB browsers may require different formats, the address is expected to be the 16 byte address in network-byte order, and shortened formats such as 0::0 are not accepted in SET operations. Two common examples are: The NetSNMP command line will accept SET requests like: snmpset -v1 -cprivate <host> s 2001:00:00:00:FFFF:CCC4:BBB2:AAA6 Other MIB browsers may require the SET request value to be formatted as: # 0x20 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0xFF 0xFF 0xCC 0xC4 0xBB 0xB2 0xAA 0xA6

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

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.

OBJECT-IDENTITY

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-IDENTITY

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

Table of hot air recirculation status information.

OBJECT-TYPE

Hot air recirculation status entry

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

The name of the component as a null terminated string

OBJECT-TYPE

The text label of the sensor as a null terminated string

OBJECT-TYPE

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

OBJECT-TYPE

Indicates whether this component has exceeded the threshold of the acceptable temperature being monitored for hot air recirculation.

OBJECT-IDENTITY

OBJECT-TYPE

Table of chassis Fan information.

OBJECT-TYPE

Chassis Fan information entry

OBJECT-TYPE

Chassis Fans table index.

OBJECT-TYPE

The numeric chassis fan ID.

OBJECT-TYPE

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.

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

The controller health state for the chassis fan.

OBJECT-TYPE

The cooling zone for the chassis fan.

OBJECT-TYPE

Table of chassis cooling zone information.

OBJECT-TYPE

Chassis cooling zone information entry

OBJECT-TYPE

Chassis Cooling Zones table index.

OBJECT-TYPE

The cooling zone for the chassis component.

OBJECT-TYPE

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

OBJECT-TYPE

A component within a cooling zone.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

Power Module health entry

OBJECT-TYPE

Power module index.

OBJECT-TYPE

Indicates whether the power module specified exists or not.

OBJECT-TYPE

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

OBJECT-TYPE

The details for this power module.

OBJECT-TYPE

The description for this power module.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

MM BIST Real Time Clock test result.

OBJECT-TYPE

MM BIST Local I2C bus test result.

OBJECT-TYPE

MM BIST Primary Main Application Firmware test result.

OBJECT-TYPE

MM BIST Secondary Main Application test result.

OBJECT-TYPE

MM BIST Boot Firmware test result.

OBJECT-TYPE

MM BIST external eth0 ethernet port test result.

OBJECT-TYPE

MM BIST external I2C devices test result.

OBJECT-TYPE

MM BIST internal external switch test result.

OBJECT-TYPE

MM BIST primary kernel test result.

OBJECT-TYPE

MM BIST secondary kernel test result.

OBJECT-TYPE

MM BIST Physical Network Link test result.

OBJECT-TYPE

MM BIST Logical Network Link test result.

OBJECT-TYPE

The blades that are installed on the chassis. The blades are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number of blades supported. If a blade is installed in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if blades are installed in bays 1, 5, and 13, and 14 blades are supported, the string would look like '10001000000010'.

OBJECT-TYPE

The blades that are communicating on the chassis. The blades are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number of blades supported. If a blade installed in a bay is communicating, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if blades are communicating in bays 1, 5, and 13, and 14 blades are supported, the string would look like '10001000000010'.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Indicates whether a rear LED card is installed

OBJECT-TYPE

Indicates whether a rear LED card is communicating

OBJECT-TYPE

Indicates whether a redundant MM is installed.

OBJECT-TYPE

Indicates whether a redundant MM is communicating.

OBJECT-TYPE

The power modules that are installed on the chassis. The power modules are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number of power modules supported. If a power module is installed in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if power modules are installed in bays 1 and 3, and 4 power modules are supported, the string would look like '1010'.

OBJECT-TYPE

The power modules that are functional on the chassis. The power modules are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number of power modules supported. If a power module is installed and functioning in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if power modules are installed and functioning in bays 1 and 3, and 4 power modules are supported, the string would look like '1010'.

OBJECT-TYPE

The switch modules that are installed on the chassis. The switch modules are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number of switch modules supported. If a switch module is installed in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if switch modules are installed in bays 1 and 3, and 4 switch modules are supported, the string would look like '1011'.

OBJECT-TYPE

The switch modules that are communicating on the chassis. The switch modules are listed as a bitmap. The bitmap is a string containing a list of 1's and 0's that is as long as the number of switch modules supported. If a switch module is installed and functioning in a bay, a 1 is present in the string in the position representing the bay ID as read from left to right. For example, if switch modules are installed and functioning in bays 1 and 3, and 4 switch modules are supported, the string would look like '1011'.

OBJECT-TYPE

Indicates whether chassis fan MUX A is installed

OBJECT-TYPE

Indicates whether chassis fan MUX A is functional

OBJECT-TYPE

Indicates whether chassis fan MUX B is installed

OBJECT-TYPE

Indicates whether chassis fan MUX B is functional

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Standby MM BIST external I2C devices test result collected when the standby MM was primary. The time of the last update can be obtained by querying rbistUpdateTimePrimary object.

OBJECT-TYPE

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

OBJECT-TYPE

Standby MM BIST Physical Network Link test result collected when the standby MM was primary. The time of the last update can be obtained by querying rbistUpdateTimePrimary object.

OBJECT-TYPE

Standby MM BIST Logical Network Link test result collected when the standby MM was primary. The time of the last update can be obtained by querying rbistUpdateTimePrimary object.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Indicates whether a rear LED card is installed

OBJECT-TYPE

Indicates whether a rear LED card is communicating

OBJECT-TYPE

Indicates whether a standby MM was installed when the standby MM was once primary.The time of the last update can be obtained by querying rbistUpdateTimePrimary object.

OBJECT-TYPE

Indicates whether a standby MM was communicating when the standby MM was once primary. The time of the last update can be gotten from the object 'rbistUpdateTimePrimary'.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Indicates whether chassis fan MUX A is installed

OBJECT-TYPE

Indicates whether chassis fan MUX A is functional

OBJECT-TYPE

Indicates whether chassis fan MUX B is installed

OBJECT-TYPE

Indicates whether chassis fan MUX B is functional

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

Fan Pack entry

OBJECT-TYPE

Fan Pack sequence index.

OBJECT-TYPE

Indicates whether the fan pack specified exists or not.

OBJECT-TYPE

The health state for the fan pack. 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

OBJECT-TYPE

The number of fans in the fan pack.

OBJECT-TYPE

The average speed of all fans in the fan pack expressed in percent(%) of maximum RPM. If the fan pack is determined not to be running or the fan pack speed cannot be determined, the string will indicate 'Offline'. The string 'Not Readable!' indicates that the given monitor is not supported on this system.

OBJECT-TYPE

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

OBJECT-TYPE

The health state for the controller for the fan pack.

OBJECT-IDENTITY

OBJECT-TYPE

Indicates status of system health for the system in which the MM resides. Value of 'critical' indicates a severe error has occurred and the system may not be functioning. A value of 'nonCritical' indicates that a error has occurred but the system is currently functioning properly. A value of 'systemLevel' indicates that a condition has occurred that may change the state of the system in the future but currently the system is working properly. A value of 'normal' indicates that the system is operating normally.

OBJECT-TYPE

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

OBJECT-TYPE

System Health Summary entry

OBJECT-TYPE

System health summary index.

OBJECT-TYPE

System health summary severity.

OBJECT-TYPE

System health summary description.

OBJECT-TYPE

System health summary date time.

OBJECT-TYPE

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.

OBJECT-TYPE

System health summary event ID.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Indicates whether the front panel system error LED is on or off.

OBJECT-TYPE

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

OBJECT-TYPE

Indicates whether the front panel identity LED is on or off.

OBJECT-IDENTITY

OBJECT-TYPE

Table of blade status information. NOTE: Querying objects in this table may take significantly longer than normal, so it is recommended that the query timeout be set to a large value. On a fully populated chassis, the timeout should be set to 120 seconds or more.

OBJECT-TYPE

Blade system status entry

OBJECT-TYPE

Blade LED table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The system health state for the blade. Unknown: Blade is in an undefined state. Good: Blade is operating normally. Warning: One or more outstanding warnings exist for this blade. Critical: One or more outstanding critical events for this blade. Kernel Mode: Blade is in kernel mode. Discovering: The 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.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

Indicates whether the blade fault LED is on or off.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Table of blade LEDs detailed information. NOTE: Querying objects in this table may take significantly longer than normal, so it is recommended that the query timeout be set to a large value. On a fully populated chassis, the timeout should be set to 120 seconds or more.

OBJECT-TYPE

Blade LEDs Details entry

OBJECT-TYPE

The LED index number.

OBJECT-TYPE

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

OBJECT-TYPE

Type of the component/subcomponent grouping for this LED.

OBJECT-TYPE

Text label for a LED.

OBJECT-TYPE

Text description which denotes color or on/off/blink state for a LED.

OBJECT-TYPE

Location of this LED.

OBJECT-IDENTITY

OBJECT-TYPE

Table of switch module LEDs information.

OBJECT-TYPE

Switch module LEDs information entry

OBJECT-TYPE

Switch module LEDs table index.

OBJECT-TYPE

The bay number of the switch.

OBJECT-TYPE

The name associated with the LED.

OBJECT-TYPE

NOTE: This table entry is read-write ONLY when Label = 'Enclosure Identity'. All other Label values have read-only access.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

Table of chassis fan LEDs information.

OBJECT-TYPE

Chassis fan LEDs information entry

OBJECT-TYPE

Chassis fan LEDs table index.

OBJECT-TYPE

The numeric chassis fan ID.

OBJECT-TYPE

Indicates whether the chassis fan specified exists or not.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

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.

OBJECT-TYPE

Fan Pack LEDs information entry

OBJECT-TYPE

Fan Pack LEDs table index.

OBJECT-TYPE

The numeric fan pack ID.

OBJECT-TYPE

Indicates whether the fan pack specified exists or not.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of Fuel Gauge information.

OBJECT-TYPE

Fuel Gauge entry

OBJECT-TYPE

Fuel Gauge Table Index.

OBJECT-TYPE

Fuel Gauge Table Power Domain Number.

OBJECT-TYPE

Fuel Gauge Table Status for the power domain. The response will start out with a numeric value (0 = unknown, 1 = good, 2 = warning, and 3: bad), followed by a text message.

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

Table of Power Domain 1.

OBJECT-TYPE

Fuel Gauge entry

OBJECT-TYPE

Power Domain 1 Table Index.

OBJECT-TYPE

Power Domain 1 Table Bay Number. The following Bay Number IDs are used: 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)

OBJECT-TYPE

Power Domain 1 Table Blade Primary Slot can be useful when a server blade spans multiple slots (e.g. double wide or triple wide). For example if the blade is double wide and is installed in slot 3 and 4. 3 is primary slot while 4 is not.

OBJECT-TYPE

Power Domain 1 Table Module Throttle Status.

OBJECT-TYPE

Power Domain 1 Table Module Name.

OBJECT-TYPE

Power Domain 1 Table Module State.

OBJECT-TYPE

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

OBJECT-TYPE

Power Domain 1 Table Allocated Power Max indicates the maximum power allocation for the module in Watts. It is indicative of the maximum amount of power the module will consume in the domain when it is fully populated with memory chips, expansion cards, etc. NOTE: When a server blade spans multiple slots (e.g. double wide or triple wide), the maximum power allocation for the module is equally divided among the slots.

OBJECT-TYPE

Power Domain 1 Table Allocated Power Min indicates the minumum power allocation for the module in Watts. It is indicative of the minumum power consumption of the component in the domain based on its maximum throttle limit. NOTE: When a server blade spans multiple slots (e.g. double wide or triple wide), the minimum power allocation for the module is equally divided among the slots.

OBJECT-TYPE

Power Domain 1 Table Module CPUs Duty Cycles applies to blade servers only. It displays the duty cycle for each CPU on the blade as a percentage. Note that some blades do not report the CPU duty cycles. In this case, 'notApplicable' will be displayed. NOTE: The CPU duty cycles are reported only on a primary slot when a server blade spans multiple slots (e.g. double wide or triple wide). For example if the blade is double wide and is installed in slot 3 and 4. 3 is primary slot while 4 is not. The CPU duty cycles are reported on slot 3 while 'notApplicable' is displayed for slot 4.

OBJECT-TYPE

Power Domain 1 Table Module Throttle indicates whether the server blade may be allowed to throttle or not.

OBJECT-TYPE

Power Domain 1 Table Module Power Capabilities. staticPowerManagement: the module with the static worst case power values. fixedPowermanagement: the module with the static power values but ability to throttle. dynamicPowerManagement: the module with power meter capability, measurement enabled, but capping disabled. dynamicPowerMeasurement1: the module with power meter capability, measurement enabled, phase 1 only dynamicPowerMeasurement2: the module with power meter capability, measurement enabled, phase 2 or higher dynamicPowerMeasurementWithPowerCapping: the module with power meter capability, both measurement and capping enabled, phase 2 or higher

OBJECT-TYPE

Power Domain 1 Table Module Measured Or Static.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

Specify time period for power domain 1 power trending information table view. NOTE: This time period should be configured before displaying the following Power Trending Information table for Power Domain.

OBJECT-TYPE

Table of Power Domain 1 Power Trending Information.

OBJECT-TYPE

Power Domain 1 Power Trending Sample entry.

OBJECT-TYPE

Power Domain 1 Power Trending Sample Table Index.

OBJECT-TYPE

Power Domain 1 Power Trending Sample Table Timestamp.

OBJECT-TYPE

Power Domain 1 Power Trending Table Average Power.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of Blade Module Details.

OBJECT-TYPE

Blade Module Details entry.

OBJECT-TYPE

Blade Module Details Table Index.

OBJECT-TYPE

Blade Module Details Table Blade Id.

OBJECT-TYPE

Blade Module Details Table Maximum Power Configuration. Allow the user to set the maximum power that can be used by the blade. This function is also known as power capping. 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

OBJECT-TYPE

Blade Module Details Table Effective CPU Clock Rate applies to DPM blades only. It displays processor's effective clock rate based on sample interval. Note that some blades do not effective clock rate. In this case, 'notApplicable' will be displayed. NOTE: The effective clock rate are reported only on a primary slot when a server blade spans multiple slots (e.g. double wide or triple wide). For example if the blade is double wide and is installed in slot 3 and 4. 3 is primary slot while 4 is not. The effective clock rate are reported on slot 3 while 'notApplicable' is displayed for slot 4.

OBJECT-TYPE

Blade Module Details Table Maximum CPU Clock Rate applies to DPM blades only. It displays processor's maximum clock rate based on sample interval. Note that some blades do not maximum clock rate. In this case, 'notApplicable' will be displayed. NOTE: The maximum clock rate are reported only on a primary slot when a server blade spans multiple slots (e.g. double wide or triple wide). For example if the blade is double wide and is installed in slot 3 and 4. 3 is primary slot while 4 is not. The maximum clock rate are reported on slot 3 while 'notApplicable' is displayed for slot 4.

OBJECT-TYPE

When enabled, the static low power saver mode allows the blade to selectively alter its operating voltage and frequency to reduce power consumption. This feature is not available on all blade types. Please refer to the blade documentation for details. If a blade does not support the static low power saver mode, this object will return notApplicable (255). Under certain rare circumstances, the enabling of the static low power saver mode may not complete successfully due to interactions with other blade functions, such as BIOS. Therefore, it is highly recommended that the user perform a GET of this object after performing a SET, in order to verify the completion of the intended operation. NOTE: enabling this object will disable bladeDetailsDynamicPowerSaver if its not already disabled.

OBJECT-TYPE

When enabled, Dynamic Power Saver allows the voltage and frequency of the CPUs on the blade to be controlled based on how busy the CPU is. This feature is not available on all blade types. Please refer to the blade documentation for details. If a blade does not support the dynamic power saver, this object will return notApplicable (255). Under certain rare circumstances, the enabling of the dynamic power saver may not complete successfully due to interactions with other blade functions, such as BIOS. Therefore, it is highly recommended that the user perform a GET of this object after performing a SET, in order to verify the completion of the intended operation. NOTE: enabling this object will disable bladeDetailsPowerSaverMode if its not already disabled.

OBJECT-TYPE

When enabled, Dynamic Power Favor Performance Over Power supports a max performance mode that pushes the system past its nominal CPU frequency when CPU and memory utilization implies it would help and the system allows it. Dynamic Power Performance Over Power can be active on the blade only after Dynamic Power Saver is enabled. This feature is not available on all blade types. Please refer to the blade documentation for details. If a blade does not support the dynamic power saver, this object will return notApplicable (255). Under certain rare circumstances, the enabling of the dynamic power favor performance over power may not complete successfully due to interactions with other blade functions, such as BIOS. Therefore, it is highly recommended that the user perform a GET of this object after performing a SET, in order to verify the completion of the intended operation.

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

Specify time period for blade module power trending information table view. NOTE: This time period should be configured before displaying the following Power Trending Information table for Blade Module. 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.

OBJECT-TYPE

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

OBJECT-TYPE

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 <blade>,<instance> pairs, where each successive pair is a child of the previous parent pair. This topology path is used to identify blades such as blade storage devices. Some examples. A storage blade with a controller card plugged into slot 1 topology location would be represented as : 010103010301--> 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

OBJECT-TYPE

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.

OBJECT-TYPE

Blade Module Power Trending Sample entry.

OBJECT-TYPE

Blade Module Power Trending Sample Table Index.

OBJECT-TYPE

Blade Module Power Trending Sample Table Blade Id. If the blade is defined using a topology location by using the scalar bladePowerTrendingTopologyPath, a zero will be displayed in the bladePowerTrendingSampleId.

OBJECT-TYPE

Blade Module Power Trending Sample Table Timestamp.

OBJECT-TYPE

Blade Module Power Trending Sample Table Maximum Power.

OBJECT-TYPE

Blade Module Power Trending Sample Table Minimum Power.

OBJECT-TYPE

Blade Module Power Trending Sample Table Average Power.

OBJECT-TYPE

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.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Specify time period for switch module power trending information table view. NOTE: This time period should be configured before displaying the following Power Trending Information table for Switch Module.

OBJECT-TYPE

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

OBJECT-TYPE

Table of Switch Module Power Trending Information.

OBJECT-TYPE

Switch Module Power Trending Sample entry.

OBJECT-TYPE

Switch Module Power Trending Sample Table Index.

OBJECT-TYPE

Switch Module Power Trending Sample Table Switch Id.

OBJECT-TYPE

Switch Module Power Trending Sample Table Timestamp.

OBJECT-TYPE

Switch Module Power Trending Sample Table Maximum Power.

OBJECT-TYPE

Switch Module Power Trending Sample Table Minimum Power.

OBJECT-TYPE

Switch Module Power Trending Sample Table Average Power.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Specify time period for 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.

OBJECT-TYPE

Chass fan mModule power trending fan ID. NOTE: The ID should be configured before displaying the chassisFanPowerTrendingTable.

OBJECT-TYPE

Table of chassis fan Module Power Trending Information.

OBJECT-TYPE

Chassis fan Module Power Trending Sample entry.

OBJECT-TYPE

Chassis fan Module Power Trending Sample Table Index.

OBJECT-TYPE

Chassis fan Module Power Trending Sample Table Id.

OBJECT-TYPE

Chassis fan Module Power Trending Sample Table Timestamp.

OBJECT-TYPE

Chassis fan Module Power Trending Sample Table Maximum Power.

OBJECT-TYPE

Chassis fan Module Power Trending Sample Table Minimum Power.

OBJECT-TYPE

Chassis fan Module Power Trending Sample Table Average Power.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Chassis Power Trending Sample entry in specified time period.

OBJECT-TYPE

Chassis Power Trending Sample Index in specified time period.

OBJECT-TYPE

Chassis Power Trending Sample Timestamp in specified time period.

OBJECT-TYPE

Chassis Power Trending Sample Average Power in specified time period.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

Table of rear LED card Thermal Trending Information.

OBJECT-TYPE

Rear LED Card Thermal Trending entry.

OBJECT-TYPE

Rear LED Card Thermal Trending Table Index.

OBJECT-TYPE

Rear LED Card Thermal Trending Table Sample Timestamp.

OBJECT-TYPE

Rear LED Card Thermal Trending Table Average Temperature.

OBJECT-TYPE

Rear LED Card Thermal Trending Table Minumum Temperature.

OBJECT-TYPE

Rear LED Card Thermal Trending Table Maximum Temperature.

OBJECT-TYPE

Table of Cubic Feet per Minute Thermal Trending Information.

OBJECT-TYPE

Chassis CFM Thermal Trending entry.

OBJECT-TYPE

Cubic Feet per Minute Thermal Trending Table Index.

OBJECT-TYPE

Cubic Feet per Minute Thermal Trending Table Sample Timestamp.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Table of Exhaust Heat Index Thermal Trending Information.

OBJECT-TYPE

Chassis Exhaust Heat Index Thermal Trending entry.

OBJECT-TYPE

Exhaust Heat Index Thermal Trending Table Index.

OBJECT-TYPE

Chassis Exhaust Heat Index Thermal Trending Table Sample Timestamp.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

Table of Power Policy information for all power domains. Reading this table can tell you about the available power policies that can be configured for a domain and also which is currently selected. The powerPolicyActivate object can also be SET to select which policy should be active for a given power domain.

OBJECT-TYPE

Power Policy Entry

OBJECT-TYPE

The unique idenitifier of a row in the powerPolicyTable.

OBJECT-TYPE

The power domain number which this row is associated with.

OBJECT-TYPE

The short name of the power policy. The following are the possible names and their detailed description: Power Module Redundancy Intended for a single 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.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

When read, this object provides the status of this power policy. If the value is enabled(1), it means this is the active power policy for the associated domain. When set to a value of enabled(1), the power policy will be made the active one for the associated domain. A set of disabled(0) is not allowed. The SET may fail when the user goes from a less restrictive policy to a more restrictive policy, e.g. no power management to redundant power modules. This happens because the 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.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of MM users currently logged in.

OBJECT-TYPE

MM users currently logged in entries.

OBJECT-TYPE

Index for MM users currently logged in.

OBJECT-TYPE

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

OBJECT-TYPE

Access method for MM users currently logged in.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Machine chassis manufacturing ID.

OBJECT-TYPE

Machine chassis hardware revision. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

Machine chassis FRU number.

OBJECT-TYPE

Machine chassis manufacture date.

OBJECT-TYPE

Machine chassis part number.

OBJECT-TYPE

Machine chassis FRU serial number.

OBJECT-TYPE

Machine chassis manufacturer ID Number.

OBJECT-TYPE

Machine chassis product ID.

OBJECT-TYPE

Machine chassis subsystem manufacturer.

OBJECT-TYPE

Machine chassis Common Language Equipment Identification (CLEI).

OBJECT-TYPE

Machine chassis hardware revision in string format. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Management module hardware VPD hardware revision. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Management module hardware VPD hardware revision in string format. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-IDENTITY

OBJECT-TYPE

Table of MM Firmware VPD.

OBJECT-TYPE

MM Firmware VPD entry.

OBJECT-TYPE

Firmware VPD index.

OBJECT-TYPE

Firmware VPD name description. '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.

OBJECT-TYPE

Firmware VPD build identification.

OBJECT-TYPE

Firmware VPD revision number.

OBJECT-TYPE

Firmware VPD file name.

OBJECT-TYPE

Firmware VPD build date.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade hardware VPD hardware revision. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade hardware VPD hardware revision in string format. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade expansion card (daughter card) VPD hardware revision. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade expansion card (daughter card) VPD hardware revision in string format. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade expansion card VPD hardware revision. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade expansion card (daughter card) VPD type code that describes the expansion card. For consistent results, view as a table and not as individual entries. NOTE: The CFFe expansion card is also referred to as a CFFh expansion card.

OBJECT-TYPE

Blade expansion card (daughter card) VPD high speed that indicates whether the expansion card is high speed or not. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

Blade expansion card VPD hardware revision in string format. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-TYPE

Table of World Wide Names (WWN), Global Unique IDs (GUID) and Serial Attach SCSI IDs (SAS) of the blade server and its expansion cards (daughter cards). For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

For expansion cards, it's the blade bay number of the blade expansion card. For blades, it's the bay number of the blade. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade management card VPD hardware revision. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade management card VPD hardware revision in string format. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

Blade firmware VPD table entry

OBJECT-TYPE

Blade firmware VPD table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the server blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

The build ID for the blade firmware.

OBJECT-TYPE

The revision of the blade firmware.

OBJECT-TYPE

The date of the blade firmware.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade firmware VPD table entry

OBJECT-TYPE

Blade firmware VPD table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the server blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

The build ID for the blade firmware.

OBJECT-TYPE

The revision of the blade firmware.

OBJECT-TYPE

The date of the blade firmware.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Blade firmware VPD table entry

OBJECT-TYPE

Blade firmware VPD table index.

OBJECT-TYPE

The numeric blade ID.

OBJECT-TYPE

Indicates whether the server blade specified exists or not.

OBJECT-TYPE

Indicates the power state of the blade specified.

OBJECT-TYPE

The name of the blade as a null terminated string.

OBJECT-TYPE

The build ID for the blade firmware.

OBJECT-TYPE

The revision of the blade firmware.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Switch module hardware VPD hardware revision. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

The WWN/GUID/SAS entry is actually World Wide Name, Global Unique ID or Serial Attach SCSI ID. For consistent results, view as a table and not as individual entries.

OBJECT-TYPE

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

OBJECT-TYPE

Switch module hardware VPD hardware revision in string format. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-IDENTITY

OBJECT-TYPE

Switch module main application VPD information table.

OBJECT-TYPE

Switch module main application VPD table entry

OBJECT-TYPE

Switch module main application VPD entry index.

OBJECT-TYPE

The switch module numeric identifier.

OBJECT-TYPE

Indicates whether the switch module specified exists or not.

OBJECT-TYPE

Indicates the type of switch module installed.

OBJECT-TYPE

Switch module firmware build id.

OBJECT-TYPE

Switch module firmware build date.

OBJECT-TYPE

Switch module firmware revision number.

OBJECT-TYPE

Switch module firmware build id.

OBJECT-TYPE

Switch module firmware build date.

OBJECT-TYPE

Switch module firmware revision number.

OBJECT-TYPE

I/O Module firmware build id.

OBJECT-TYPE

I/O Module firmware build date.

OBJECT-TYPE

I/O Module firmware revision number.

OBJECT-TYPE

Indicates the subtype of switch module installed.

OBJECT-TYPE

Switch module boot ROM VPD information table.

OBJECT-TYPE

Switch module boot ROM VPD table entry

OBJECT-TYPE

Switch module boot ROM VPD entry index.

OBJECT-TYPE

The switch module numeric identifier.

OBJECT-TYPE

Indicates whether the switch module specified exists or not.

OBJECT-TYPE

Indicates the type of switch module installed.

OBJECT-TYPE

Switch module firmware build ID.

OBJECT-TYPE

Switch module firmware build date.

OBJECT-TYPE

Switch module firmware revision number.

OBJECT-TYPE

Indicates the subtype of switch module installed.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Power module hardware VPD hardware revision. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then the HardwareRevisionString version of this MIB object should be used.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

Power module hardware VPD hardware revision in string format. For consistent results, view as a table and not as individual entries. If a hardware revision is programmed in the OEM VPD area for this component, then this MIB object should be used.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

Rear LED card hardware VPD Manufacture Date.

OBJECT-TYPE

Rear LED card hardware VPD Part Number.

OBJECT-TYPE

Rear LED card hardware VPD FRU Serial.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

Chassis fan controller firmware VPD table entry

OBJECT-TYPE

Chassis fan controller firmware VPD table index.

OBJECT-TYPE

The numeric chassis fan ID.

OBJECT-TYPE

Indicates whether the chassis fan specified exists or not.

OBJECT-TYPE

The revision of the chassis fan controller firmware.

OBJECT-IDENTITY

OBJECT-TYPE

Table of the chassis fan hardware components.

OBJECT-TYPE

Chassis fan hardware VPD entry.

OBJECT-TYPE

Chassis fan hardware VPD index.

OBJECT-TYPE

Chassis fan hardware VPD Bay number.

OBJECT-TYPE

Chassis fan hardware VPD manufacturing ID.

OBJECT-TYPE

Chassis fan hardware VPD FRU number.

OBJECT-TYPE

Chassis fan hardware VPD hardware revision.

OBJECT-TYPE

Chassis fan hardware VPD UUID.

OBJECT-TYPE

Chassis fan hardware VPD manufacture Date.

OBJECT-TYPE

Chassis fan hardware VPD Part Number.

OBJECT-TYPE

Chassis fan hardware VPD FRU serial number.

OBJECT-TYPE

Chassis fan hardware VPD manufacturer ID.

OBJECT-TYPE

Chassis fan hardware VPD product ID.

OBJECT-TYPE

Chassis fan hardware VPD subsystem manufacturer ID.

OBJECT-TYPE

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

OBJECT-TYPE

Chassis fan hardware VPD hardware revision in string format.

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

Power Module controller firmware VPD table entry

OBJECT-TYPE

Power Module controller firmware VPD table index.

OBJECT-TYPE

The numeric Power Module ID.

OBJECT-TYPE

Indicates whether the Power Module specified exists or not.

OBJECT-TYPE

The revision of the Power Module controller firmware.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Disable/Enable/Reset the passive air filter. When enabled, sending an enable or reset will reset the replace date.

OBJECT-TYPE

The chassis environment. 1 month indicates high dust, 3 months indicates moderate dust and, 6 months indicates low dust.

OBJECT-TYPE

The scheduled replacement date of the air filter.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

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.

OBJECT-TYPE

Component inventory information.

OBJECT-TYPE

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 <component>,<instance> pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. This component inventory table is indexed by this unique topology path and the numeric designations for the components are: CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade POWER, 0x04 Power Supply, Power Module, etc COOLING, 0x05 Fan, blower, or other cooling device IO_MODULE, 0x06 Has I/O interface, i.e. - switch or bridge MEDIA, 0x07 Media device PROCESSOR, 0x08 Any processor, processor module, etc STORAGE, 0x09 Any type of storage device EXPANSION, 0x0A Expansion Card (not covered by more specific type) MEMORY, 0x0B Any memory device, module, etc MFRU, 0x0C Managed FRU Device PANEL, 0x0D Any sort of panel device, such as a front panel BLADE_EXPANSION_MODULE, 0x0E Expansion option (BEM) such as PEU, BSE, etc CARD_EXPANSION, 0x0F Expansion card, ie. daughter card CARD_HS_EXPANSION, 0x10 High Speed Expansion card, ie. daughter card INTERPOSER, 0x11 Interposer device CLOCK, 0x12 Clock card MUX, 0x13 Mulitplexer card ADDIN, 0x14 cKVM card & other addin cards STORAGE_MODULE, 0x15 Container of one or more Storage Devices SYS_EXPANSION_CARD, 0x16 Management card BATTERY, 0x17 A single battery BATTERY_MODULE, 0x18 Container of one or more batteries 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

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

The machine serial number of this component.

OBJECT-TYPE

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

OBJECT-TYPE

The part number of this component.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

The text description of the manufacturer of this component.

OBJECT-TYPE

The hardware revision number of the this component.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

The product identifier of the component assigned by the manufacturer.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

The asset tag of this component.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

The architecture specification of a memory device.

OBJECT-TYPE

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

OBJECT-TYPE

The product version assigned by the manufacturer for this component.

OBJECT-TYPE

The type designation for processor components.

OBJECT-TYPE

The family designation for processor components.

OBJECT-TYPE

The number of cores present on a processor component.

OBJECT-TYPE

The number of threads present on a processor component.

OBJECT-TYPE

The level 1 data cache size of a processor component.

OBJECT-TYPE

The level 1 instruction cache size of a processor component.

OBJECT-TYPE

The level 2 cache size of a processor component.

OBJECT-TYPE

The level 3 cache size of a processor component.

OBJECT-TYPE

The voltage rating for a processor component.

OBJECT-TYPE

The external clock speed of a processor component.

OBJECT-TYPE

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

OBJECT-TYPE

The identification number assigned for the component by the manufacturer.

OBJECT-TYPE

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.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

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

OBJECT-TYPE

Component firmware information.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

A text description of the type of firmware load.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

A text description of the filename of this firmware load.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

This object indicates whether this firmware image is the active (1) firmware,otherwise this firmware image is inactive (0).

OBJECT-TYPE

A text description with the firmware image information.

OBJECT-TYPE

Indicates the type of firmware load with a numeric identifier.

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

Node firmware analysis information.

OBJECT-TYPE

The index for the node firmware levels.

OBJECT-TYPE

The machine type or model of node firmware.

OBJECT-TYPE

The firmware type.

OBJECT-TYPE

The firmware build id.

OBJECT-TYPE

The firmware release date.

OBJECT-TYPE

The firmware revision level.

OBJECT-TYPE

The node topology.

OBJECT-TYPE

The node device name.

OBJECT-TYPE

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.

OBJECT-TYPE

IOM firmware analysis information.

OBJECT-TYPE

The index for the IOM firmware levels.

OBJECT-TYPE

The IOM product id.

OBJECT-TYPE

The IOM product name.

OBJECT-TYPE

The IOM firmware type.

OBJECT-TYPE

The IOM firmware version.

OBJECT-TYPE

The IOM release date.

OBJECT-TYPE

The IOM topology.

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

Component drive information.

OBJECT-TYPE

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 <component>,<instance> pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. This component 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

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-TYPE

Table of license key information.

OBJECT-TYPE

License key information entry.

OBJECT-TYPE

License key component table index.

OBJECT-TYPE

The license key index for the chassis component.

OBJECT-TYPE

The description for a license key.

OBJECT-TYPE

The date and time of this license key.

OBJECT-TYPE

The unique identifier for this license key.

OBJECT-TYPE

Any other information related to this license key.

OBJECT-TYPE

The current status of this license key.

OBJECT-TYPE

Table of chassis license key information.

OBJECT-TYPE

Chassis License key information entry.

OBJECT-TYPE

The key index for the chassis license keys.

OBJECT-TYPE

The name of the Feature for the license key.

OBJECT-TYPE

The Feature Type Code for the license key.

OBJECT-TYPE

The description of the license key.

OBJECT-TYPE

System information for the license key.

OBJECT-TYPE

Identification of the license key.

OBJECT-TYPE

Validation of the license key.

OBJECT-TYPE

The current status of the license key.

OBJECT-TYPE

Date and Time (GMT) when license expires.

OBJECT-TYPE

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

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of event log entry information.

OBJECT-TYPE

Event log table entry

OBJECT-TYPE

The event log index number.

OBJECT-TYPE

A string of data detailing an event.

OBJECT-TYPE

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

OBJECT-TYPE

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.

OBJECT-TYPE

Table of enhanced event log entry information.

OBJECT-TYPE

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

OBJECT-TYPE

The event log number for the enhanced event log.

OBJECT-TYPE

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.

OBJECT-TYPE

A string of data detailing an event log message.

OBJECT-TYPE

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.

OBJECT-TYPE

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

OBJECT-TYPE

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

OBJECT-TYPE

The audit log number.

OBJECT-TYPE

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

OBJECT-TYPE

A string of data detailing an audit event log message.

OBJECT-TYPE

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.

OBJECT-TYPE

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

OBJECT-TYPE

Table of system log entry information. System log includes the logs whose source is other than 'Audit'

OBJECT-TYPE

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

OBJECT-TYPE

The system log index number.

OBJECT-TYPE

A string of data detailing an system event log's attribute.

OBJECT-TYPE

A string of data detailing an system event log message.

OBJECT-TYPE

The sequence number for the system 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.

OBJECT-TYPE

Clear the system log. NOTE: Value returned for the GET command is meaningless for this MIB object.

OBJECT-TYPE

Table of system log entry auxiliary information.

OBJECT-TYPE

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

OBJECT-TYPE

The system log auxiliary index number. To relate this information to the system log, match Sequence number of this entry to the Sequence number of the system log entry.

OBJECT-TYPE

The sequence number for the system event log that contains this Auxiliary information. Value is from 1 through 4294967295 and then wraps.

OBJECT-TYPE

A string of data detailing the auxiliary information from the log event.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Number in seconds to delay between retries if sending a remote alert is unsuccessful.

OBJECT-TYPE

Number of additional times a remote alert will be retried if not successfully sent. A value of zero indicates no retries will be attempted.

OBJECT-TYPE

Use this field to specify how users attempting to login should be authenticated. There are two methods: Local authentication. Userid and password are verified by searching the list of users locally configured under Local Login Profiles. LDAP based authentication. Users are authenticated via a remote LDAP server. One or both authentication methods can be selected. If both methods should be used, the order must be specified.

OBJECT-TYPE

The maximum number of simultaneous active sessions allowed for each LDAP user. If the value is 0, this option is disabled. The minimum value is 1 and the maximum value is 20.

OBJECT-TYPE

Use this option to set how long, in seconds, MM will not log the authentication events for the same user. The default setting is 5 minutes. 0 indicates log all authentication events, 255 indicates don't log any new authentication events.

OBJECT-TYPE

This option indicates tracking different IP addresses for the same user is enabled or not. If it is enabled then an access every second from alternating IP addresses will result in multiple log entries, regardless of the time duration set in the 'authenticaionLoggingTimeout'field. If this flag is disabled, multiple accesses by varying IP addresses will only be logged as 'new' accesses if they are out of the 'authenticationLoggingTimeout'.

OBJECT-IDENTITY

OBJECT-TYPE

The level of security needed for local user login passwords. The legacy level: - no password required - no password expiration - no password re-use restrictions - no frequency of password change restrictions - account is locked for 2 minutes after 5 login failures - simple password rules - no account inactivity monitoring The high level: - password required - factory default 'USERID' account password must be changed on next login - force user to change password on first login - password expires in 90 days - password re-use checking enabled (last 5 passwords kept in history) - minimum 24 hours interval between password changes - account is locked for 60 minutes after 5 login failures - complex password rules with 2 degrees of difference from previous password - alert on account inactivity after 120 days - accounts disabled after 180 days of inactivity The custom level: - set the password settings individually under customSecuritySettings The default value is legacy.

OBJECT-IDENTITY

OBJECT-TYPE

The number of days before login passwords expire. The minimum value is 1 day and the maximum value is 365 days. The default value is 90 days. A value of 0 disables this option.

OBJECT-TYPE

If enabled, the factory default 'USERID' account password must be changed on next login. The default value is disabled.

OBJECT-TYPE

The number of unique passwords a user must choose before reusing a password. The default value is none.

OBJECT-TYPE

If enabled, the minimum complexity rules will be enforced for all local login passwords and 'User login password required' rule will be enabled. The complex rules are as follows: must be 8-31 characters must contain at least one number must contain at least one letter cannot contain white space characters cannot be a repeat or reverse of user name no more than 3 of the same characters used consecutively must contain at least 2 of the following combinations: at least one upper case letter at least one lower case letter at least one special character Password and password confirm values must match If disabled, the lagacy rules are: must be 5-31 characters must contain at least one number must contain at least one letter cannot contain white space characters Password and password confirm values must match The default value is disabled.

OBJECT-TYPE

The required minimum number of characters in the new password different from the previous password. The default value is 2. A SET of this object is ignored until the complexPasswordRules option is enabled and the minimumPasswordReuseCycle is not none(0)

OBJECT-TYPE

If enabled, the login user will be forced to change their password on the first access after the account has been established or on the first access after an administrator has changed the password for the user, except for the administrator password for USERID. The default value is disabled.

OBJECT-TYPE

The period of time in days before generating an alert for a dormant account. This value applies to all login accounts, including the administrator account. The minimum value is 1 day and the maximum value is 365 days. The default value is 0 which disables this option. NOTE: This value must be less than the inactivityAlertDisablePeriod.

OBJECT-TYPE

The period of time in days before generating an alert and disabling a dormant account. This value applies to all login accounts, excluding the administrator account. The minimum value is 1 day and the maximum value is 365 days. The default value is 0 which disables this option. NOTE: This value must be greater than the inactivityAlertPeriod.

OBJECT-TYPE

The period of time in minutes that a user is locked out after the maximum number of login failures was reached. The minimum value is is 1 minute and the maximum value is 2880 minutes. The default value is 2 minutes for the Legacy security level and 60 minutes for the High security level. A value of 0 disables this option.

OBJECT-TYPE

The maximum number of login failures before a user account is locked. A value of 0 disables this option. The default value is 5.

OBJECT-TYPE

A minimum period of time that user is not able to change their own password. The range of acceptable values will be from 0 to 1440 (or 60 days). A value of 0 disables this option. If the password expiration period is set, it must be greater than the minimum password change interval.

OBJECT-IDENTITY

OBJECT-TYPE

Baud rate for the serial port.

OBJECT-TYPE

Parity setting for the serial port.

OBJECT-TYPE

Number of stop bits for the serial port.

OBJECT-IDENTITY

OBJECT-TYPE

Table of remote alert entries. This table lets you configure remote alert recipients. You can define up to 12 unique recipients. NOTE: All selected alert events will be sent to all enabled alert recipients.

OBJECT-TYPE

Remote alert entries.

OBJECT-TYPE

Index for remote alert entry.

OBJECT-TYPE

Remote alert entry status, invalid means entry not defined yet, disabledAndValid means entry defined but not enabled to send an alert, enabledAndValid means entry defined and enabled to send an alert.

OBJECT-TYPE

A null terminated string that either contains an IP address of the form '1.2.3.4' or a host name (if DNS is enabled) for the alert entry.

OBJECT-TYPE

A null terminated string that contains a text description of this entry.

OBJECT-TYPE

Remote alert entry notification method. Types include unknown when the type can't be determined (read-only), snmpOverLan for an SNMP alert over ethernet, and emailOverLan for a E-Mail alert over ethernet.

OBJECT-TYPE

A null terminated string that contains an E-Mail Address. For example, 'xyz@us.ibm.com'. Used only for an E-mail over LAN notification type.

OBJECT-TYPE

Remote alert entry selective alert setting. A value of critOnlyAlerts will only send critical alerts to this remote alert recipient, a value of allAlerts will send all alerts to this remote alert recipient.

OBJECT-TYPE

Generate a Test Alert. This will send a test alert to all configured and enabled remote alert recipients. NOTE: Value returned for the GET command is meaningless for this MIB object.

OBJECT-IDENTITY

OBJECT-TYPE

Table of remote access profiles. This table lets you to configure all login profiles. NOTE: By default, the management module comes configured with one login profile that allows remote access using a login ID of 'USERID' and a password of 'PASSW0RD' (the 0 is a zero). To avoid a potential security exposure, we strongly recommend that you change this default Login Profile to values of your choice.

OBJECT-TYPE

Remote access entries.

OBJECT-TYPE

Index for Remote access entry.

OBJECT-TYPE

Remote access entry null terminated string that contains the userid. It must not be a duplicate of any previously configured ones. This field is only allowed to be set when the entry status is under creation.

OBJECT-TYPE

Remote access password. The password rules are dictated by a combination of the chassis security policy setting (securityPolicySetting) and the user account security level setting (accountSecurityLevel). Refer to object complexPasswordRules to understand the requirements. NOTE: Value returned by the GET command is meaningless for this MIB object.

OBJECT-TYPE

A list of permission groups for this userid, delmited with a '|'

OBJECT-TYPE

Indicates if user is currently logged in or not.

OBJECT-TYPE

Timestamp for the last successful login by the user.

OBJECT-TYPE

Indicates if user complies with all of the password rules currently in effect.

OBJECT-TYPE

The number of days until the user's current password expires.

OBJECT-TYPE

Indicates if the user account has been inactive for a specified amount of time based on inactivityAlertDisablePeriod in the customSecuritySettings section.

OBJECT-TYPE

Indicates the state of the user: Active - normal state Disabled - user cannot use account until enabled by a supervisor or chassis user account manager. An account can get disabled after being dormant for a specified amount of time OR as a result of a supervisor or chassis user account manager disabling it. Locked - account is temporarily locked due to repeated unsuccessful login attempts as specified by lockoutPeriod in the customSecuritySettings section. Account can be unlocked by a supervisor or chassis user account manager OR can be automatically unlocked after the lockoutPeriod expires. NOTE: The disable action does not apply to supervisor or chassis user account manager accounts.

OBJECT-TYPE

Actions that only a supervisor or chassis user account manager can perform for each user id: Enable - enables an account in the Disabled state Disable - disables an account in the Active or Locked state Unlock - unlock an account in the Locked state NOTE: The disable action does not apply to supervisor or chassis user account manager accounts. NOTE: Value returned for the GET command is meaningless for this MIB object.

OBJECT-TYPE

The number of sessions the user is currently logged in to.

OBJECT-TYPE

The maximum number of simultaneous active sessions allowed for the user. If the value is 0, this option is disabled. The minimum value is 1 and the maximum value is 20.

OBJECT-TYPE

This object manages the creation and deletion of this entry. The steps recommended to add a new group are: 1. Create a new entry in this table remoteAccessIdEntryStatus = createRequest 2. Set remoteAccessId as required. The remoteAccessIdUserId and the remoteAccessIdPassword must be set before the entry becomes valid. To set the remoteAccessIdsEntryPermgroups or remoteAccessIdsEntryMaxSessions before the entry is valid, set these fields before both the password and userId are set. Only one row will be allowed to be underCreation at one time, and it must have the next index in the table. valid(1) - Indicates that the group represented by this entry is available for use. createRequest(2) - A new entry will be created in this table for the specified group and the new entry will transition to the underCreation(3). underCreation(3) - Indicates that this entry exists in the agent but is unavailable for use. After completing the create operation, the agent will set this object to underCreation(3). invalid(4) - Deletes this entry.

OBJECT-TYPE

Indicates if the user has been provisioned as an IPMI account. If this is user is provisioned as an IPMI account, the nodes (scope) and authorities will be determined by the scope and authorities of the permission groups to which this user belongs. These can be seen in the remoteAccessRBSscopeTable and remoteAccessRBSroleTable for the permission groups to which this user is assigned. If the userid is longer than 16 characters or there are more than 12 user accounts enabled for IPMI provisioning, setting the value to yes will return an error. When provisioning an IPMI account by setting this object to yes(1), the SNMPv3 account is also automatically provisioned.

OBJECT-TYPE

Indicates if the user has been provisioned as an SNMPv3 account. If this is user is provisioned as an SNMPv3 account, the nodes (scope) and authorities will be determined by the scope and authorities of the permission groups to which this user belongs. These can be seen in the remoteAccessRBSscopeTable and remoteAccessRBSroleTable for the permission groups to which this user is assigned. If the userid is longer than 16 characters or there are more than 12 user accounts enabled for SNMPv3 provisioning, setting the value to yes will return an error. When provisioning a SNMPv3 account by setting this object to yes(1), the IPMI account is also automatically provisioned.

OBJECT-TYPE

Table of RBS User Role profiles.

OBJECT-TYPE

User Role entries.

OBJECT-TYPE

Index for RBS User Role entry.

OBJECT-TYPE

Remote access RBS role entry null terminated string that contains the permission group ID. It must not be a duplicate of any previously configured ones. This field is only allowed to be set when the entry status is under creation.

OBJECT-TYPE

User has no restrictions.

OBJECT-TYPE

User has read-only access, and cannot perform any save, modify, clear, or state affecting operations (e.g. restart MM, restore defaults, upgrade the firmware, etc.).

OBJECT-TYPE

User has ability to browse status and properties of chassis components (MM, chassis fans, midplane, power modules). Ability to backup MM configuration to a file. Saving MM configuration to chassis requires supervisor access.

OBJECT-TYPE

User can add/modify/delete user login profiles. Ability to backup MM configuration to a file. Changing global login settings require chassis configuration authority.

OBJECT-TYPE

User has ability to clear the MM event log, change log policy settings, and backup MM configuration to a file.

OBJECT-TYPE

User can modify and save any chassis configuration parameter (except user profiles and event log settings). Ability to restore MM factory defaults if the user also has chassis administration permissions. Ability to change the global login settings, SOL configuration, and backup MM configuration to a file.

OBJECT-TYPE

User has ability to do MM firmware updates, modify chassis LEDs, restore MM factory defaults if the user also has chassis configuration permissions. Ability to restart MM and backup MM configuration to a file.

OBJECT-TYPE

User has ability to browse status and properties of blades.

OBJECT-TYPE

User has ability to access the blades remote console. The ability to issue the CLI console command to start an SOL session to a blade will also require this authority.

OBJECT-TYPE

User can modify and save any blade configuration parameter.

OBJECT-TYPE

User can power on/off and restart blades, activate standby blades, do firmware updates, and modify blade LEDs.

OBJECT-TYPE

User has ability to browse status and properties of I/O Modules, and to ping I/O Modules.

OBJECT-TYPE

User can modify the I/O Module IP address, configure I/O Module Advanced Management parameters, and restore factory defaults on an I/O Module. Note that a user requires both I/O Module configuration and I/O Module administration roles in order to be able to launch a telnet or web UI session to an I/O Module, or to restore factory defaults on an I/O Module.

OBJECT-TYPE

User can power on/off and restart the I/O Modules, update I/O Module firmware, enable/disable the Fast POST and External Ports of an I/O Module. Note that a user requires both I/O Module configuration and I/O Module administration roles in order to be able to launch a telnet session to an I/O Module, or to restore factory defaults on an I/O Module.

OBJECT-TYPE

This object manages the creation and deletion of this entry. The steps recommended to add a new group are: 1. Create a new entry in this table rbsEntryStatus = createRequest 2. Set roleId as required. Only one row will be allowed to be underCreation at one time, and it must have the next index in the table. valid(1) - Indicates that the group represented by this entry is available for use. createRequest(2) - A new entry will be created in this table for the specified group and the new entry will transition to the underCreation(3). underCreation(3) - Indicates that this entry exists in the agent but is unavailable for use. After completing the create operation, the agent will set this object to underCreation(3). invalid(4) - Deletes this entry.

OBJECT-TYPE

Table of RBS User Scope profiles.

OBJECT-TYPE

User Scope entries.

OBJECT-TYPE

Index for RBS User Scope Entry.

OBJECT-TYPE

Remote access RBS scope entry null terminated string that contains the permission group ID.

OBJECT-TYPE

User has access to the MM and chassis functions.

OBJECT-TYPE

User has access to the blade in slot 1.

OBJECT-TYPE

User has access to the blade in slot 2.

OBJECT-TYPE

User has access to the blade in slot 3.

OBJECT-TYPE

User has access to the blade in slot 4.

OBJECT-TYPE

User has access to the blade in slot 5.

OBJECT-TYPE

User has access to the blade in slot 6.

OBJECT-TYPE

User has access to the blade in slot 7.

OBJECT-TYPE

User has access to the blade in slot 8.

OBJECT-TYPE

User has access to the blade in slot 9.

OBJECT-TYPE

User has access to the blade in slot 10.

OBJECT-TYPE

User has access to the blade in slot 11.

OBJECT-TYPE

User has access to the blade in slot 12.

OBJECT-TYPE

User has access to the blade in slot 13.

OBJECT-TYPE

User has access to the blade in slot 14.

OBJECT-TYPE

User has access to I/O module 1.

OBJECT-TYPE

User has access to I/O module 2.

OBJECT-TYPE

User has access to I/O module 3.

OBJECT-TYPE

User has access to I/O module 4.

OBJECT-TYPE

User has access to I/O module 5.

OBJECT-TYPE

User has access to I/O module 6.

OBJECT-TYPE

User has access to I/O module 7.

OBJECT-TYPE

User has access to I/O module 8.

OBJECT-TYPE

User has access to I/O module 9.

OBJECT-TYPE

User has access to I/O module 10.

OBJECT-TYPE

Indicates whether CMM is the central manager of the IPMI and SNMPv3 accounts. For a write, it can only be set to enabled. Once the CMM state is enabled, it can only be cleared by doing a reset to defaults. WARNING: Enabling CMM IPMI/SNMPv3 user account management will cause all presently existing IPMI/SNMPv3 user accounts on nodes to be overwritten. Please be sure to save any existing node IPMI/SNMPv3 account information before proceeding.

OBJECT-IDENTITY

OBJECT-TYPE

Enable/Disable CLI access to the MM (telnet and SSH). The value enabled(3) means both telnet and ssh are enabled.

OBJECT-TYPE

Enable/Disable SNMP v1 and v3 access to the MM. The value enabled(3) means both telnet and ssh are enabled.

OBJECT-TYPE

Enable/Disable TCP command mode (TCM) access to the MM. A value of 0 means disabled, any value from 1 to 20 means enabled. NOTE: MM will provide a max of 20 connections for both Secure TCP Command Mode and TCP Command Mode.

OBJECT-TYPE

Enable/Disable Web access (HTTP/HTTPS) to the MM. NOTE: Disabling web access to the MM will cause all currently active web sessions to disconnect, and you will no longer be able to access the MM management functions using a web browser.

OBJECT-TYPE

Enable/Disable secure TCP command mode (STCM) access to the MM. A value of 0 means disabled, any value from 1 to 20 means enabled. NOTE: MM will provide a max of 20 connections for both Secure TCP Command Mode and TCP Command Mode. If no valid server certificate is in place, Secure TCP Command Mode will not be allowed to set to enable.

OBJECT-IDENTITY

OBJECT-TYPE

A table that contains client authentication public key information.

OBJECT-TYPE

A information list about a particular SSH public key used for client authentication. The primary table index is the same value as the associated remoteAccessIdEntryIndex. The secondary table index allows selection of the Nth public key for that remoteAccessIdEntryIndex.

OBJECT-TYPE

The primary table index is the same value as the associated remoteAccessIdEntryIndex used as an index into the remoteAccessIdsTable.

OBJECT-TYPE

The secondary table index used to select one of the client authentication public keys for a particular remote access Id. The index is an integer value from 1 to N where N is the number of keys associated with a particular remote access Id. An addition always causes the value of N to increase by one, effectively adding an entry after the existing keys for that remote access Id. If an entry is deleted from the table by setting mmSshClientAuthPubKeyEntryStatus = invalid, the key associated with that entry is deleted. If the deleted key was not the last key for a remote access Id (mmSshClientAuthPubKeyIndex is not the 'last' or Nth entry), the subsequent entries are renumbered after the deletion. A deletion always causes the value of N to decrease by one. The underlying SSH server implementation searches the keys in order from 1 to N when attempting public key authentication. NOTE:A maximum of 4 public keys can be installed for one remote access Id.

OBJECT-TYPE

The type of the SSH public key represented by this entry.

OBJECT-TYPE

The size of the SSH public key represented by this entry.

OBJECT-TYPE

The RSA fingerprint of the SSH public key represented by this entry. This value can be used with the SSH client to verify, on the initial connection, that the Secure Shell server responding to the request is the server running on the managed entity. This is the fingerprint of the operational host key pair. If the key pair represented by this entry is not operational then sixteen null octets must be returned.

OBJECT-TYPE

This is a filter that describes the set of SSH client IP addresses and host names that can establish SSH connections to the MM authenticated by the public key represented by this entry of the table. The filter is a comma-separated list of IP addresses and/or hostnames. A question mark may be used to match any single character. An asterisk may be used to match multiple characters. An exclamation point may preceed an IP address or hostname to deny acccess from that IP address or hostname. The format of the Accept From specification is: from=PATTERN-LIST PATTERN-LIST is the filter, which must be enclosed in double quotation marks. NOTE:This MIB object can be manipulated after the corresponding SSH public key is installed.

OBJECT-TYPE

This is a descriptive string that the administrator may use to help identify the public key represented by this entry. It serves no function in the operation of the SSH server. NOTE:This MIB object can be manipulated after the corresponding SSH public key is installed.

OBJECT-TYPE

import(1) starts the TFTP file transfer of an SSH client authentication public key from the TFTP server to the MM. The import operation is only accepted if the associated RemoteAccessIdsEntry row is configured and the current value of mmSshClientAuthPubKeyEntryStatus is underCreation(3) or valid(1), if the current value of mmSshClientAuthPubKeyEntryStatus is valid(1), it will replace the key with a new key, If the import is successful the value of mmSshClientAuthPubKeyRowStatus changes to valid(1). export(2) starts the TFTP file transfer of an SSH client authentication public key from the MM to the TFTP server. The export operation is only accepted if the current value of mmSshClientAuthPubKeyEntryStatus is valid(1). NOTE: Users should compare the fingerprint value mmSshClientAuthPubKeyFingerprint to the fingerprint of client authentication key files imported or exported using the TFTP file transfer protocol to guard against possible file corruption. Value returned for the GET command is meaningless for this MIB object.

OBJECT-TYPE

This object manages the creation and deletion of this entry. The steps recommended to install and to activate a new client authorization public key are: 1. Set values for mmSshClientAuthPubKeyTftpServer, mmSshClientAuthPubKeyFileName, mmSshClientAuthPubKeyFileFormat 2. Create a new entry in this table mmSshClientAuthPubKeyEntryStatus = createRequest 3. Import a new key mmSshClientAuthPubKeyAction = import This entry will be valid after mmSshClientAuthPubKeyAction is successfully imported. 4. Set mmSshClientAuthPubKeyAcceptFrom and mmSshClientAuthPubKeyComment as required. valid(1) - Indicates that the public key pair represented by this entry is available for use by the Secure Shell Server for client authentication. createRequest(2) - A new entry will be created in this table for the specified host key pair and the new entry will transition to the underCreation(3) state. The operation is only accepted if the associated RemoteAccessIdsEntry row defining a local user account is configured. underCreation(3) - Indicates that this entry exists in the agent but is unavailable for use. After completing the create operation, the agent will set this object to underCreation(3). invalid(4) - Deletes this entry and any client authentication public key that may be associated with it. Note: only one row may be created at one time.

OBJECT-TYPE

The userid for the key entry.

OBJECT-TYPE

The number of available storage locations that may be used to install additional Client Authentication Public Keys. This number decreases by one when a new key is added to the configuration.

OBJECT-TYPE

IP address or host name of the TFTP server where an SSH client authentication public key is to be installed from or exported to. The address must be entered in a dotted decimal IP string (e.g. 9.37.44.2).

OBJECT-TYPE

File name on the TFTP server of an SSH client authentication public key.

OBJECT-TYPE

File format of SSH client authentication public key files imported from or exported to the TFTP file server.

OBJECT-IDENTITY

OBJECT-TYPE

Table of Group profiles. This table lets you to configure all group profiles. You can define up to 16 unique profiles.

OBJECT-TYPE

Group ID entries.

OBJECT-TYPE

Index for Group IDs entry.

OBJECT-TYPE

Group ID. It is a null terminated string that contains the group-id. It must not be a duplicate of any previously configured ones.

OBJECT-TYPE

Group Role. It indicates if the group has supervisor, operator, or custom access.

OBJECT-TYPE

This object manages the creation and deletion of this entry. The steps recommended to add a new group are: 1. Create a new entry in this table groupEntryStatus = createRequest 2. Set groupId as required. Then the entry will be valid. valid(1) - Indicates that the group represented by this entry is available for use. createRequest(2) - A new entry will be created in this table for the specified group and the new entry will transition to the underCreation(3). underCreation(3) - Indicates that this entry exists in the agent but is unavailable for use. After completing the create operation, the agent will set this object to underCreation(3). invalid(4) - Deletes this entry.

OBJECT-TYPE

Table of Group Role profiles.

OBJECT-TYPE

Group Role entries.

OBJECT-TYPE

Index for Group Role entry.

OBJECT-TYPE

Group ID

OBJECT-TYPE

Group has no restrictions.

OBJECT-TYPE

Group has read-only access, and cannot perform any save, modify, clear, or state affecting operations (e.g. restart MM, restore defaults, upgrade the firmware, etc.).

OBJECT-TYPE

Group has ability to browse status and properties of chassis components (MM, chassis fans, midplane, power modules). Ability to backup MM configuration to a file. Saving MM configuration to chassis requires supervisor access.

OBJECT-TYPE

Group can add/modify/delete user login profiles. Ability to backup MM configuration to a file. Changing global login settings require chassis configuration authority.

OBJECT-TYPE

Group has ability to clear the MM event log, change log policy settings, and backup MM configuration to a file.

OBJECT-TYPE

Group can modify and save any chassis configuration parameter (except user profiles and event log settings). Ability to restore MM factory defaults if the group also has chassis administration permissions. Ability to change the global login settings, SOL configuration, and backup MM configuration to a file.

OBJECT-TYPE

Group has ability to do MM firmware updates, modify chassis LEDs, restore MM factory defaults if the group also has chassis configuration permissions. Ability to restart MM and backup MM configuration to a file.

OBJECT-TYPE

Group has ability to browse status and properties of blades.

OBJECT-TYPE

Group has ability to access the blade remote console The ability to issue the CLI console command to start an SOL session to a blade will also require this authority.

OBJECT-TYPE

Group can modify and save any blade configuration parameter.

OBJECT-TYPE

Group can power on/off and restart blades, activate standby blades, do firmware updates, and modify blade LEDs.

OBJECT-TYPE

Group has ability to browse status and properties of I/O Modules, and to ping I/O Modules.

OBJECT-TYPE

Group can modify the I/O Module IP address, configure I/O Module Advanced Management parameters, and restore factory defaults on an I/O Module. Note that a group requires both I/O Module configuration and I/O Module administration roles in order to be able to launch a telnet session to an I/O Module, or to restore factory defaults on an I/O Module.

OBJECT-TYPE

Group can power on/off and restart the I/O Modules, update I/O Module firmware, enable/disable the Fast POST and External Ports of an I/O Module. Note that a group requires both I/O Module configuration and I/O Module administration roles in order to be able to launch a telnet session to an I/O Module, or to restore factory defaults on an I/O Module.

OBJECT-TYPE

Table of Group Scope profiles.

OBJECT-TYPE

Group Scope entries.

OBJECT-TYPE

Index for Group Scope Entry.

OBJECT-TYPE

Group ID

OBJECT-TYPE

Group has access to the MM and chassis functions.

OBJECT-TYPE

Group has access to the blade in slot 1.

OBJECT-TYPE

Group has access to the blade in slot 2.

OBJECT-TYPE

Group has access to the blade in slot 3.

OBJECT-TYPE

Group has access to the blade in slot 4.

OBJECT-TYPE

Group has access to the blade in slot 5.

OBJECT-TYPE

Group has access to the blade in slot 6.

OBJECT-TYPE

Group has access to the blade in slot 7.

OBJECT-TYPE

Group has access to the blade in slot 8.

OBJECT-TYPE

Group has access to the blade in slot 9.

OBJECT-TYPE

Group has access to the blade in slot 10.

OBJECT-TYPE

Group has access to the blade in slot 11.

OBJECT-TYPE

Group has access to the blade in slot 12.

OBJECT-TYPE

Group has access to the blade in slot 13.

OBJECT-TYPE

Group has access to the blade in slot 14.

OBJECT-TYPE

Group has access to I/O module 1.