ArrayManager-MIB: View SNMP OID List / Download MIB

Version information for the Dell OpenManage Array Manager software.

Global health information for the subsystem managed by the Dell Array Manager software. This global status is customized for HP OpenView. Other applications should refer to the agentSystemGlobalStatus entry in the globalData object group. Possible values: 1: Critical 2: Warning 3: Normal 4: Unknown Enumeration: 'unknown': 4, 'critical': 1, 'warning': 2, 'normal': 3.

Manufacturer information for the Dell Array Manager software.

Product information for the Dell Array Manager software.

Product Description for the Dell Array Manager software.

Name of this agent for display purposes.

A short description of this agent such as <The Dell Storage Consolidation SNMP Agent>.

The name of the agent software manufacturer.

Version information for the Dell OpenManage Array Manager software.

Global health information for the subsystem managed by the Dell Array Manager software. This global status should be used by applications other than HP OpenView. HP OpenView should refer to the arrayMgrGlobalStatus in the root level object group. This is a rollup for the entire agent including any monitored devices. The status is intended to give initiative to a snmp monitor to get further data when this status is abnormal. Possible values: 1: Normal 2: Warning 3: Non-critical Error 4: Failure 5: Unknown Enumeration: 'failure': 4, 'warning': 2, 'nonCriticalError': 3, 'unknown': 5, 'normal': 1.

The the previous global status of the system managed by the Dell Array Manager software. Possible values: 1: Normal 2: Warning 3: Non-critical Error 4: Failure 5: Unknown Enumeration: 'failure': 4, 'warning': 2, 'nonCriticalError': 3, 'unknown': 5, 'normal': 1.

The last time that the agent values have been updated. Universal time in sec since UTC 1/1/70.

Suggested timeout value in milliseconds for how long the SNMP getter should wait while attempting to poll the SNMP agent.

Agent functional modifiers, when set the modifier is active. Bit definitions: Bit 3: agent in debug mode. All other bits are product specific

Rate in seconds at which the agent cached data is being updated.

The fully qualified network hostname of the host where the agent is running.

The IP Address of the host where the agent is running and at which the SNMP agent can be contacted.

Status of the Array Manager Database service software. 1: Database Up - Communication with the database is possible for SNMP queries. 2: Database Down - Communication with the database is not possible for SNMP queries. Enumeration: 'databaseUp': 1, 'databaseDown': 2.

Version of the Array Manager SNMP extension agent for Windows, SNMP provider for Netware.

Version of the Array Manager MIB.

Instance number of this provider entry.

The name of the module that supports either a family of devices or a set of functions.

The status of this provider. 1: Loaded 2: Failed 3: Unknown Enumeration: 'loaded': 1, 'unknown': 3, 'failed': 2.

This version and build number of the provider module.

A table of managed RAID controllers. The number of entries is related to number of RAID controllers discovered in the system.

An entry in the table of RAID controllers. A row in this table cannot be created or deleted by SNMP operations on columns of the table.

Instance number of this controller entry.

The name of the contoller in this subsystem as represented in Array Manager. Includes the controller type and instance. For example: Perc3/QC 1.

The controller's (re)seller's name. For Dell controllers this will = Dell.

The type of this controller: 1: SCSI 2: PV660F 3: PV662F 4: IDE (Integrated/Intelligent Drive Electronics) Enumeration: 'scsi': 1, 'ide': 4, 'pv662F': 3, 'pv660F': 2.

The status of this controller's subsystem (which includes any devices connected to it.) Possible states: 0: Unknown 1: Ready 2: Failed 3: Online 4: Offline 6: Degraded Enumeration: 'ready': 1, 'failed': 2, 'offline': 4, 'degraded': 6, 'online': 3.

Seriousness of the controller state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The percent of the compute cycles dedicated to rebuilding failed array disks.

The controller's current firmware version.

The controller's current amount of cache memory in megabytes. If this size is 0, it is less than a megabyte.

The controller's current amount of cache memory that is less than a megabyte. This combined with the controllerCacheSizeInMB will be the total amount of memory.

Number of physical devices on the controller channel including both disks and the controller.

Number of virtual disks on the controller.

Indicates availability of the redundant controller in a redundant configuration. Booting: Controller is powering up. OK: Controller is in fully redundant status. Inserted: Controller is there, but not acting as a partner. Kill Partner Command Received: Failed: UnknownStatus: SCSI Comm Failure:

The number of host ports on this controller. Host Port: An active fibre port connected to an arbitrated loop. The port may be opened by an initiator on the loop and process i/o requests.

Size of memory in megabytes on the controller. If this size is 0, it is less than a megabyte.

Size of memory on the controller that is less than a megabyte. This combined with the controllerMemorySizeInMB will be the total size of the memory.

The number of redundant drive channels for the controller.

Indicates whether the controller is enabled to be fault tolerant. 0: no 1: yes Enumeration: 'yes': 1.

World Wide name for the first port on controller 0.

The unique value/name assigned to the controller's first active port.

The controller's preferred host port/loopid as specified by controller option 'hard loop id' for its first port.

The controller in slot 0 (it should always be the master controller.)

Channel number of the controller's first port. Channel: A path for the transfer of data and controller information between the host or the physical disk drives and the controller.

Manufacturer's identification of controller on first port.

Current state of battery on the controller's first port. Possible values: 0: Unknown 1: OK (present and operational) 2: Failed (cannot hold charge or cannot be recharged) 7: Reconditioning (PV660 Only) 9: High 10: Low 12: Charging 21: Missing (Adaptec Only) Enumeration: 'ok': 1, 'missing': 21, 'reconditioning': 7, 'high': 9, 'failed': 2, 'low': 10, 'charging': 12.

World Wide name for the first port on controller 1.

The unique value/name assigned to the controller's second active port.

The controller's preferred host port/loopid as specified by controller option 'hard loop id' for its second port. (Value of 255 = C1 controller not there)

The controller in slot 1. (Value of 255 = controller not there)

Channel number of the controller's second port. Channel: A path for the transfer of data and controller information between the host or the physical disk drives and the controller. (Value of 255 = controller not there)

Manufacturer's identification of controller on second port. (Value of 255 = controller not there)

Current state of battery on the controller's second port. Possible values: 0: Unknown 1: OK (present and operational) 2: Failed (cannot hold charge or cannot be recharged) 7: Reconditioning (PV660 Only) 9: High 10: Low 12: Charging 21: Missing (Adaptec Only) Enumeration: 'ok': 1, 'missing': 21, 'reconditioning': 7, 'high': 9, 'failed': 2, 'low': 10, 'charging': 12.

Used as the node name for the storage subsystem.

World Wide name for the second port on controller 0.

World Wide name for the second port on controller 1.

The number of charges that have been applied to the battery on this controller.

A table of controller channels. The number of entries is related to number of channels supported in a RAID controllers. Perc2 RAID controller supports a max of 4 channels per controller. The maximum number of entries is implementation dependent.

An entry in the channel table. A row in this table cannot be created or deleted by SNMP operations on columns of the table.

Instance number of this channel entry.

The name of the channel as represented in Array Manager. The name will include the word channel and the instance. For example: Channel 1

The current state of this channel. Possible states: 0: Unknown 1: Ready - The I/O has resumed. 2: Failed 3: Online 4: Offline - The I/O has paused. 6: Degraded Enumeration: 'ready': 1, 'failed': 2, 'offline': 4, 'degraded': 6, 'online': 3.

Seriousness of the channel state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The type of SCSI termination on this channel. Termination is required for proper operation of this channel. 1: Wide Termination (16 bit) 2: Narrow Termination (8 bit) 3: Not Terminated Enumeration: 'wide': 1, 'narrow': 2, 'notTerminated': 3.

The SCSI ID of the controller to which the channel belongs.

Instance number of the enclosure entry.

The enclosure's name as represented in Array Manager.

The enclosure's (re)seller's name.

The state of the controller. Possible states: 0 : Unknown 1 : Ready 2 : Failed 3 : Online 4 : Offline 6 : Degraded 55: Communication Lost Enumeration: 'commLost': 55, 'failed': 2, 'online': 3, 'ready': 1, 'offline': 4, 'degraded': 6.

Seriousness of the enclosure state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'warining': 1, 'failure': 3, 'error': 2.

For fibre channel - The number of the enclosure in the subsystem. For SCSI - The SCSI address of the processor.

Firmware version of the enclosure's processor. For Fibre Channel only.

Enclosure identification used when consulting customer support.

Customer definable asset tag for the enclosure.

Customer definable asset name of the enclosure.

The enclosure's split bus part number.

The enclosure's product identification. This also corresponds to the enclosure type.

The version of the enclosure's kernel (Dell PV200S, PV201S, PV210S, and PV211S only.)

This entry is obsolete.

This entry is obsolete.

The type of this enclosure. Possible values: 1: Internal 2: Dell PV200S (PV201S) 3: Dell PV210S (PV211S) 4: Dell PV220S (PV221S) 5: Dell PV660F 6: Dell PV224F 7: Dell PV660F / PV224F Enumeration: 'dELLPV210SPV211S': 3, 'dELLPV200SPV201S': 2, 'internal': 1, 'dELLPV220SPV221S': 4, 'dELLPV660F': 5, 'dELLPV660F224F': 7, 'dELLPV224F': 6.

This entry is obsolete.

The current configuration of the enclosure's backplane. Possible values: 1: Joined 2: Split Bus 3: Clustered Enumeration: 'clustered': 3, 'splitBus': 2, 'joined': 1.

The channel number, or bus, to which the enclosure is connected.

The current status of the enclosure's alarm (PV220S, and PV221S only.) Possible values: 1: Off 2: On Enumeration: 'on': 2, 'off': 1.

The part number of the enclosure's backplane.

The SCSI ID of the controller to which this enclosure is attached.

A table of managed Array Disks. The number of entries is related to number of Array Disks discovered in the system. The maximum number of entries is implementation dependent.

An entry in the Array Disk table . A row in this table cannot be created or deleted by SNMP operations on columns of the table.

Instance number of this array disk entry.

The name of the array disk as represented in Array Manager.

The array disk's (re)seller's name.

The current state of the array disk. Possible states: 0: Unknown 1: Ready - Available for use, but no RAID configuration has been assigned. 2: Failed - Not operational. 3: Online - Operational. RAID configuration has been assigned. 4: Offline - The drive is not available to the RAID controller. 6: Degraded - Refers to a fault-tolerant array/virtual disk that has a failed disk. 7: Recovering - Refers to state of recovering from bad blocks on disks. 11: Removed - Indicates that array disk has been removed. 15: Resynching - Indicates one of the following types of disk operations: Transform Type, Reconfiguration, and Check Consistency. 24: Rebuild 25: No Media - CD-ROM or removable disk has no media. 26: Formatting - In the process of formatting. 28: Diagnostics - Diagnostics are running. 35: Initializing: Applies only to virtual disks on PERC, PERC 2/SC, and PERC 2/DC controllers. Enumeration: 'recovering': 7, 'resynching': 15, 'initializing': 35, 'rebuild': 24, 'diagnostics': 28, 'noMedia': 25, 'failed': 2, 'formatting': 26, 'online': 3, 'ready': 1, 'offline': 4, 'removed': 11, 'degraded': 6.

Severity of the array disk state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The model number of the array disk.

The array disk's unique identification number from the manufacturer.

The firmware version of the array disk.

The SCSI ID of the enclosure processor to which this array disk belongs.

The bus to which this array disk is connected.

The size in megabytes of the array disk. If this size is 0, it is smaller than a megabyte.

The size of the array disk in bytes that is less than a megabyte. This size plus the arrayDiskLengthInMB is the total size of the array disk.

The size in megabytes of the largest contiguous free space on the array disk. If this size is 0, it is less than a megabyte.

The size of the largest contiguouis free space on this array disk in bytes that is less than a megabyte. This size plus the arrayDiskLargestContiguousFreeSpaceInMB is the total size of the largest contiguous free space on the array disk.

The SCSI target ID which this array disk is assigned.

The array disk's logical unit number.

The amount in megabytes of the used space on the array disk. If this size is 0, it is smaller than a megabyte.

The size in bytes of the used space on the array disk that is smaller than a megabyte. This size plus the arrayDiskUsedSpaceInMB is the total amount of used space on the array disk.

The amount in megabytes of the free space on the array disk. If this size is 0, it is smaller than a megabyte.

The size in bytes of the free space on the array disk that is smaller than a megabyte. This size plus the arrayDiskFreeSpaceInMB is the total amount of free space on the array disk.

The bus type of the array disk. Possible values: 1: SCSI 2: IDE 3: Fibre Channel 4: SSA 6: USB Enumeration: 'fibre': 3, 'scsi': 1, 'ide': 2, 'ssa': 4, 'usb': 6.

The status of the array disk as a spare. Possible states: 1: disk is a member of a virtual disk 2: disk is a member of a disk group 3: disk is a global hot spare 4: disk is a dedicated hot spare Enumeration: 'memberVD': 1, 'globalHotSpare': 3, 'dedicatedHotSpare': 4, 'memberDG': 2.

A table of the connections between array disks, their enclosure, and their associated controller. For each object in the table, its object number corresponds to an instance number in the appropriate MIB table for that object where all of the object properties can be found.

Instance number of this array disk connection entry. This table shows the array disk to SCSI or Fibre Channel enclosure relationship.

The name of the array disk in this connection as represented in Array Manager.

The instance number of the array disk in the arrayDiskTable in this connection.

The name of the enclosure as represented in Array Manager to which this array disk belongs.

The instance number in the enclosureTable of the enclosure to which this array disk belongs.

The name of the controller as represented in Array Manager to which this array disk is connected.

The instance number in the controllerTable of the controller to which this array disk is connected.

A table of the connections between array disks, their channel, and their associated controller. For each object in the table, its object number corresponds to an instance number in the appropriate MIB table for that object where all of the object properties can be found.

Instance number of this array disk connection entry. This table shows the array disk to SCSI channel relationship. There is no enclosure service processor associated with these array disks.

The name of the array disk in this connection as represented in Array Manager.

The instance number of the array disk in the arrayDiskTable in this connection.

The name of the channel as represented in Array Manager to which is array disk is connected.

The instance number of the channel in the channelTable to which this array disk is connected.

The name of the controller as represented in Array Manager to which this array disk is connected.

The instance number in the controllerTable of the controller to which this array disk is connected.

Instance number of this fan entry.

The fan's name as represented in Array Manager.

The fan's (re)seller's name.

Current state of the fan. Possible states: 0 : Unknown 1 : Ready 2 : Failed 3 : Online 4 : Offline 6 : Degraded 55: Communication Lost Enumeration: 'ready': 1, 'failed': 2, 'degraded': 6, 'removed': 11, 'commLost': 55.

Seiousness of the fan state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The minimum value that will force the fan into a warning state.

The minimum value that will force the fan into an error state.

The maximum value that will force the fan into a warning state.

The maximum value that will force the fan into an error state.

The current speed of the fan.

The part number of the fan in the enclosure.

This entry is obsolete.

A table of the connections between each fan on the managed node and its enclosure. Each enclosure number in the table corresponds to that enclosure instance in the Enclosure Table.

Instance number of this fan connection entry.

The name of the fan in this connection as represented in Array Manager.

The instance number of the fan in the fanTable in this connection.

The name of the enclosure as represented in Array Manager to which this fan belongs.

The instance number of the enclosure in the enclosureTable to which this fan belongs.

Instance number of this powersupply entry.

The power supply's name as represented in Array Manager.

The power supply's (re)seller's name.

Current state of the power supply. Possible states: 0 : Unknown 1 : Ready 2 : Failed 55: Communication Lost Enumeration: 'ready': 1, 'failed': 2, 'commLost': 55.

Seriousness of the power supply state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The part number of the power supply of the enclosure.

This entry is obsolete.

A table of the connections between each power supply on the managed node and its enclosure. Each enclosure number in the table corresponds to that enclosure instance in the Enclosure Table.

Instance number of this powersupply connection entry.

The name of the power supply in this connection as represented in Array Manager.

This instance number in the powersupplyTable of the power supply in this connection.

The name of the enclosure to which this power supply is connected as represented in Array Manager.

The instance number of the enclosure in the enclosureTable to which this power supply is connected.

Instance number of this temperature probe entry.

Name of this temperature probe as represented in Array Manager.

Temperature probe's (re)seller's name.

Current state of this temperature probe. Possible states: 0 : Unknown 1 : Ready 2 : Failed 4 : Offline 6 : Degraded 55: Communication Lost Enumeration: 'ready': 1, 'failed': 2, 'offline': 4, 'degraded': 6, 'commLost': 55.

Seriousness of the temperature probe state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The units that will be used to display temperatures for this temperature probe.

The minimum temperature that will force the probe into a warning state.

The minimum temperature that will force the probe into an error state.

The maximum temperature that will force the probe into a warning state.

The maximum temperature that will force the probe into an error state.

The current temperature of this probe.

A table of the connections between each temperature probe on the managed node and its enclosure. Each enclosure number in the table corresponds to that enclosure instance in the Enclosure Table.

Instance number of this temperature probe connection entry.

The name of the temperature probe in this connection as represented in Array Manager.

The instance number in the temperatureTable of the temperature probe in this connection.

The name of the enclosure as represented in Array Manager to which this temperature probe belongs.

The instance number of the enclosure in the enclosureTable to which this temperature probe belongs.

A table of managed Enclosure Memory Modules. The number of entries is related to number of Enclosure Memory Modules discovered in the system. The maximum number of entries is implementation dependent.

Instance number of this enclosure memory module entry.

Name of this enclosure memory module as represented in Array Manager.

The management module's (re)seller's name.

The state of the enclosure management module. Possible states: 0 : Unknown 1 : Ready 2 : Failed 3 : Online 4 : Offline 6 : Degraded 55: Communication Lost Enumeration: 'commLost': 55, 'failed': 2, 'online': 3, 'ready': 1, 'offline': 4, 'degraded': 6.

Seriousness of the enclosure management module state. Possible values: 0: OK 1: Warning 2: Error 3: Failure

The part number of the enclosure memory module.

The type of the enclosure management module. Possible values: 0: Unknown 1: EMM 2: Termination Card Enumeration: 'eMM': 1, 'terminationCard': 2.

Firmware version of the enclosure memory module.

The maximum bus speed of the enclosure management module.

A table of the connections between each enclosure management module on the managed node and its enclosure. Each enclosure number in the table corresponds to that enclosure instance in the Enclosure Table.

Instance number of this enclosure management module connection entry.

The name of the enclosure management module in this connection as represented in Array Manager.

The instance number of the enclosure management module in the enclosureManagementModuleTable in this connection.

The name of the enclosure as represented in Array Manager to which this enclosure management module belongs.

The instance number of the enclosure in the enclosureTable to which this enclosure management module belongs

A table of managed Virtual Disks. The number of entries is related to number of Virtual Disks discovered in the system. The maximum number of entries is implementation dependent.

An entry in the Virtual Disk table. A row in this table cannot be created or deleted by SNMP operations on columns of the table.

Instance number of this virtual disk entry.

The virtual disk's label generated by the provider or entered by the user.

Device name used by this virtual disk's member disks.

The current state of this virtual disk. Possible states: 0: Unknown 1: Ready - The disk is accessible and has no known problems. 2: Failed - Access has been lost to the data or is about to be lost. 3: Online 4: Offline - The disk is not accessible. The disk may be corrupted or intermittently unavailable. 6: Degraded - The data on the virtual disk is no longer fault tolerant because one of the underlying disks is not online. 15: Resynching 24: Rebuilding 26: Formatting 35: Initializing Enumeration: 'rebuilding': 24, 'verifying': 7, 'initializing': 35, 'failed': 2, 'failedRedundancy': 18, 'formatting': 26, 'online': 3, 'ready': 1, 'offline': 4, 'resynching': 15, 'degraded': 6.

Seriousness of the virtual disk state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The size of this virtual disk in megabytes. If this size is 0, it is smaller than a megabyte.

The portion of the virtual disk in bytes that is smaller than a megabyte. This size plus the virtualDiskLengthInMB is the total size of the virtual disk.

Amount of free space in megabytes on virtual disk. If this size is 0, it is smaller than a megabyte.

The portion of the free space on the virtual disk in bytes that is smaller than a megabyte. This size plus the virtualDiskFreeSpaceInMB is the total free space on the virtual disk.

Indicates whether the controller's write cache will be used when writing to a virtual disk. Possible values: 1: Enabled - Write Back 2: Disabled - Write Through Enumeration: 'disabled': 2, 'enabled': 1.

Indicates whether the controller's read cache will be used when reading from a virtual disk. Note: Virtual Disks on a PV660F do not have a read cache policy. Possible values: 1: Enabled - Read Ahead 2: Disabled - No Read Ahead 3: Adaptive Read Ahead Enumeration: 'disabled': 2, 'adaptiveReadAhead': 3, 'enabled': 1.

Indicates whether the controller's cache is used when reading from or writing to a virtual disk. Possible values: 1: Direct I/O 2: Cached I/O Enumeration: 'cachedIO': 2, 'directIO': 1.

The virtual disk's RAID type. Possible values: 1: Concatenated 2: Raid-0 3: Raid-1 4: Raid-2 5: Raid-3 6: Raid-4 7: Raid-5 8: Raid-6 9: Raid-7 10: Raid-10 11: Raid-30 12: Raid-50 13: Add Spares 14: Delete Logical 15: Transform Logical 18: Raid-0-plus-1 (0+1) Enumeration: 'raid-50': 12, 'raid-0-plus-1': 18, 'transformLogical': 15, 'addSpares': 13, 'concatenated': 1, 'raid-30': 11, 'raid-1': 3, 'raid-0': 2, 'raid-3': 5, 'raid-2': 4, 'raid-5': 7, 'raid-4': 6, 'raid-7': 9, 'raid-6': 8, 'deleteLogical': 14, 'raid-10': 10.

The stripe size of this virtual disk in megabytes. If this size is 0, it is smaller than a megabyte.

The portion of the stripe size in bytes that is smaller than a megabyte. This size plus the virtualDiskCurStripeSizeInMB is the total stripe size on the virtual disk.

The virtual disk's channel number.

The virtual disk's target ID.

The virtual disk's LUN ID.

A table of managed disks that are a member of a Virtual Disk. The number of entries is related to the number of online array disks discovered in the system. The maximum number of entries is implementation dependent.

An entry in the Member Disk table. A row in this table cannot be created or deleted by SNMP operations on columns of the table.

Instance number of the disk entry.

The disk's name as represented in Array Manager.

Device name of the virtual disk that includes this disk. This is used to link the Disk to its virtual disk.

The current state of the Disk. Possible states: 0: Unknown 1: Ready 2: Failed 3: Online - The disk is accessible and has no known problems. 4: Offline 6: Degraded 24: Rebuild 25: No Media 40: Not Ready Enumeration: 'rebuild': 24, 'noMedia': 25, 'notReady': 40, 'failed': 2, 'online': 3, 'ready': 1, 'offline': 4, 'degraded': 6.

Seriousness of the disk state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The disk's LDM device type. Possible values: 1: Dynamic 2: Removable 3: CD-ROM 4: Basic 5: Basic with no signature 6: OEM 7: DVD Enumeration: 'removable': 2, 'dvd': 7, 'cd-rom': 3, 'dynamic': 1, 'basicNoSignature': 5, 'oem': 6, 'basic': 4.

The name identifying the disk type.

Length of the disk in megabytes. If this size is 0, it is smaller than a megabyte.

The portion in bytes of the disk length that is less than a megabyte. This size plus the diskLengthInMB is the total length of the disk.

The amount of free space on this disk in megabytes. If this size is 0, it is smaller than a megabyte.

The portion in bytes of the disk free space that is less than a megabyte. This size plus the diskFreeSpaceInMB is the total free space on the disk.

The name of the controller to which the device(s) represented by this disk object are connected.

The disk's port number as represented in Array Manager.

The disk's target ID as represented in Array Manager.

The disk's LUN ID as represented in Array Manager.

The disk's (re)seller's name.

A table of the connections between array disks, the virtual disk to which they belong, and their associated logical disk. For each object in the table, its object number corresponds to an instance number in the appropriate MIB table for that object where all of the object properties can be found.

Instance number of this array disk logical connection entry.

The name of the array disk in this logical connection.

The instance number of the array disk in this logical connection.

The name of the virtual disk to which this array disk belongs.

The instance number of the virtual disk to which this array disk belongs.

The name of the disk group to with this array disk belongs.

This instance number of the disk group to with this array disk belongs.

The name identifying this sub-disk.

The current state of the sub-disk. Possible states: 0: Unknown 1: Ready 2: Failed 3: Online - The disk is accessible and has no known problems. 4: Offline 6: Degraded Enumeration: 'ready': 1, 'failed': 2, 'offline': 4, 'degraded': 6, 'online': 3.

Severity of the sub-disk state. Possible values: 0: OK 1: Warning 2: Error 3: Failure

Length of the sub-disk in megabytes. If this size is 0, it is smaller than a megabyte.

The portion in bytes of the sub-disk length that is less than a megabyte. This size plus the subDiskLengthInMB is the total length of the sub-disk.

Instance number of the partition entry.

The partition's name as represented in Array Manager.

The state of the partition. Possible states: 0: Unknown 1: Ready 2: Failed 3: Online 6: Degraded Enumeration: 'ready': 1, 'failed': 2, 'degraded': 6, 'online': 3.

Severity of the partition state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

The length of the partition in megabytes. If this size is 0, it is smaller than a megabyte.

The portion of the partition length that is less than a megabyte. This size plus the partitionLengthInMB is the total length of the partition.

The partition's LDM volume type. Possible values: 1: Basic - standard DOS/Windows disk signature 2: Extended 3: Logical 4: CD ROM 5: Simple 6: Stripe 7: Mirror 8: Raid5 9: Span 10: Dynamic - upgraded disk Enumeration: 'extended': 2, 'span': 9, 'simple': 5, 'mirror': 7, 'dynamic': 10, 'logical': 3, 'raid5': 8, 'stripe': 6, 'basic': 1, 'cdrom': 4.

The instance number of this extended partition entry.

The name of this extended partition as represented in Array Manager

The current state of the extended partition. Possible states: 0: Unknown 1: Ready 2: Failed 3: Online 6: Degraded Enumeration: 'ready': 1, 'failed': 2, 'degraded': 6, 'online': 3.

Seriousness of the extended partition state. Possible values: 0: OK 1: Warning 2: Error 3: Failure Enumeration: 'failure': 3, 'warning': 1, 'error': 2.

A table of volumes that are recognized by the operating system.

An entry in the volume table. A row in this table cannot be created or deleted by SNMP operations on columns of the table.

Instance number of the volume entry.

The volume's path (or drive letter) according to the operating system.

The volume's current state. Possible states: 0: Unknown 1: Ready - The volume is accessible and has no known problems. 2: Failed - The volume cannot be started automatically. 3: Online 4: Offline 6: Degraded 18: Failed Redundancy - The data on the volume is no longer fault tolerant because one of the underlying disks is not online. 25: No Media 26: Formatting - The volume is being formatted using the specifications you chose for formatting. ?: Initializing - The volume is being initialized. ?: Resynching - The volume's mirrors are being resynchronized so that both mirrors contain identical data. ?: Regenerating - Data and parity are being regenerated for the RAID-5 volume. ?: Failed Redundancy (At Risk) - The data on the volume is no longer fault tolerant, and I/O errors have been detected on the underlying disk ?: No Media - No media has been inserted into the CD-ROM or removable drive. Enumeration: 'noMedia': 25, 'failed': 2, 'failedRedundancy': 18, 'formatting': 26, 'online': 3, 'ready': 1, 'offline': 4, 'degraded': 6.

The severity of the volume. Possible values: 0: OK 1: Warining 2: Error 3: Failure Enumeration: 'warning': 1, 'failrue': 3, 'error': 2.

The volume's LMD volume type. Possible values: 1: Basic - standard DOS/Windows disk signature 2: Extended 3: Logical 4: CD ROM 5: Simple 6: Stripe 7: Mirror 8: Raid5 9: Span 10: Dynamic Enumeration: 'extended': 2, 'mirrror': 7, 'simple': 5, 'cd-rom': 4, 'dynamic': 10, 'logical': 3, 'raid5': 8, 'stripe': 6, 'basic': 1, 'span': 9.

The user definable label for this volume.

The volume's operating system file system type.

The size of the volume in megabytes. If this size is 0, it is smaller than a megabyte.

The portion in bytes of the volume that is smaller than a megabyte. This size plus the volumeLengthInMB is the total length of the volume.

The amount of free space on the volume in megabytes. If this size if 0, it is smaller than a megabyte.

The portion in bytes of the free space on the volume that is smaller than a megabyte. This size plus the volumeFreeSpaceInMB is the total length of the volume.

Instance number of the plex entry.

The name identifying this plex as represented in Array Manager.

The width of the plex stripe in megabytes. If this size is 0, it is smaller than a megabyte.

The portion in bytes of the plex stripe that is smaller than a megabyte. This size plus the plexStripeWidthInMB is the total size of the stripe.

The number of columns in one plex.

The type of RAID of this plex. Possible values: 1: Striped Subdisks 2: Concatenated Subdisks 3: RAID layout Enumeration: 'raidLayout': 3, 'concatenatedSubdisks': 2, 'stripedSubdisks': 1.

A table of the connections between array disks, the virtual disk to which they belong, their associated logical basic disk, extended partition, partition and volume. For each object in the table, its object number corresponds to an instance number in the appropriate MIB table for that object where all of the object properties can be found.

Instance number of this basic disk connection entry.

The name of an array disk that is part of the basic disk in this connection table entry.

The instance number in the arrayDiskTable of the array disk in this basic disk connection entry.

The name of the virtual disk that is part of the basic disk in this connection table entry.

The instance number in the virtualDiskTable of this virtual disk that is part of the basic disk.

The name of the basic disk in this connection table entry.

The instance number in the diskTable of the disk in this conneciton table entry.

The name of the extended partition that is part of the basic disk in this connection table entry.

The instance number in the extendedPartitionTable of this extended partition that is part of the basic disk.

The name of the partition that is part of the basic disk in this connection table entry.

The instance number in the partitionTable of this partition that is part of the basic disk.

The path (or drive letter) of the volume to which this basic disk belongs.

The instance number in the volumeTable of the volume to which this basic disk belongs.

A table of the connections between array disks, the virtual disk to which they belong, their associated logical basic disk, partition and volume. For each object in the table, its object number corresponds to an instance number in the appropriate MIB table for that object where all of the object properties can be found.

Instance number of this basic disk connection entry.

The name of an array disk that is part of the basic disk in this connection table entry.

The instance number in the arrayDiskTable of the array disk in this basic disk connection entry.

The name of the virtual disk that is part of the basic disk in this connection table entry.

The instance number in the virtualDiskTable of this virtual disk that is part of the basic disk.

The name of the basic disk in this connection table entry.

The instance number in the diskTable of the disk in this conneciton table entry.

The name of the partition that is part of the basic disk in this connection table entry.

The instance number in the partitionTable of this partition that is part of the basic disk.

The path (or drive letter) of the volume to which this basic disk belongs.

The instance number in the volumeTable of the volume to which this basic disk belongs.

A table of the connections between array disks, the virtual disk to which they belong, their associated logical dynamic disk, sub-disk, plex and volume. For each object in the table, its object number corresponds to an instance number in the appropriate MIB table for that object where all of the object properties can be found.

Instance number of this dynamic disk connection entry.

The name of an array disk that is part of the dynamic disk in this connection table entry.

The instance number in the arrayDiskTable of the array disk in this dynamic disk connection entry.

The name of the virtual disk that is part of the dynamic disk in this connection table entry.

The instance number in the virtualDiskTable of this virtual disk that is part of the dynamic disk.

The name of the dynamic disk in this connection table entry.

The instance number in the diskTable of the disk in this conneciton table entry.

The name of the dynamic sub-disk in this connection.

The instance number in the subDiskTable of the dynamic sub-disk in this connection.

The name of the plex to which this dynamic disk belongs.

The instance number in the plexTable of the plex to which this dynamic disk belongs.

The path (or drive letter) of the volume to which this dynamic disk belongs.

The instance number of the volume to which this dynamic disk belongs.

Controller Name for which trap is generated.

Channel Number for which trap is generated.

SCSI ID of the device for which trap is generated.

Virtual Disk for which trap is generated.

Array Disk for which trap is generated.

Current Virtual Disk configuration for which trap is generated

New Virtual Disk configuration for which trap is generated.

Enclosure Number for which trap is generated.

Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)

Enclosure Name for which trap is generated.

Unit Number for which trap is generated. (Fan, Power Supply, Temperature Probe)

Amount of time specified in the trap message.

Volume Drive Letter for which trap is generated.

Combination of the enclosure name and unit number for which trap is generated.

New name of the virtual disk for which trap is generated.

Name of the device for which trap is generated. Note: The device type contained in this generic variable could change for different occurrences of a trap.

Sense Key data for this trap in hexidecimal.

Sense Code data for this trap in hexidecimal.

Sense Qualifier data for this trap in hexidecimal.

Firmware version for EMM 0.

Firmware version for EMM 1.

New rebuild rate for controller in this event.

%s, %s failed.

%s, %s removed.

%s, %s offline.

%s, %s degraded.

%s, %s inserted.

%s, virtual disk (%s) created.

%s, virtual disk (%s) deleted.

%s, virtual disk (%s) configuration changed from %s to %s

%s, virtual disk (%s) failed.

%s, virtual disk (%s) degraded.

%s, virtual disk (%s) is no longer redundant.

%s, virtual disk (%s) check consistency started.

%s, virtual disk (%s) format started.

%s, %s format started.

%s, virtual disk (%s) initialization started.

%s, %s initialize started.

%s, virtual disk (%s) reconfiguration from %s stripe size to %s stripe size started.

%s, virtual disk (%s) rebuild started.

%s, %s rebuild started.

%s, %s diagnostics started.

%s, virtual disk (%s) consistency check cancelled.

%s, virtual disk (%s) format cancelled.

%s, %s format cancelled.

%s, virtual disk (%s) initialization cancelled.

%s, %s initialize cancelled.

%s, virtual disk (%s) reconfiguration cancelled.

%s, virtual disk (%s) rebuild cancelled.

%s, %s rebuild cancelled.

%s, %s diagnostics cancelled.

%s, virtual disk (%s) consistency check failed.

%s, virtual disk (%s) format failed.

%s, %s format failed.

%s, virtual disk (%s) initialization failed.

%s, %s initialize failed.

%s, virtual disk (%s) reconfiguration failed.

%s, virtual disk (%s) rebuild failed.

%s, %s rebuild failed.

%s, %s diagnostics failed.

%s, virtual disk (%s) consistency check completed.

%s, virtual disk (%s) format completed.

%s, %s format completed.

%s, virtual disk (%s) initialization completed.

%s, %s initialize completed.

%s, virtual disk (%s) reconfiguration completed.

%s, virtual disk (%s) rebuild completed.

%s, %s rebuild completed.

%s, %s diagnostics completed.

%s, %s reported predictive failure. If this disk is part of a redundant virtual disk, select the 'Offline' option and then replace the disk. Then configure a hot spare and it will start the rebuild automatically. If this disk is a hot spare, select the 'Prepare to Remove' option and then replace the disk. If this disk is part of a non-redundant disk, you should back-up your data immediately. If the disk fails, you will not be able to recover the data.

%s, %s SCSI sense failure. If this disk is part of a redundant virtual disk, select the 'Offline' option and then replace the disk. Then configure a hot spare and it will start the rebuild automatically. If this disk is a hot spare, select the 'Prepare to Remove' option and then replace the disk. If this disk is part of a non-redundant disk, you should back-up your data immediately. If the disk fails, you will not be able to recover the data.

%s, Channel %s I/O paused, I/O will automatically resume after the allotted time (%d seconds).

%s, Channel %s I/O resumed.

%s, assigned %s as Hot Spare.

%s, unassigned %s as Hot Spare.

%s battery needs reconditioning.

%s battery low.

%s battery is reconditioning.

%s battery reconditioning completed.

%s I/O paused, I/O will automatically resume after the allotted time.

%s I/O resumed.

%s SMART:FPT_EXCEEDED on %s.

%s SMART configuration change on %s.

%s SMART warning on %s.

%s SMART warning temperature on %s.

%s SMART warning degraded on %s.

%s, On %s the failure prediction threshold exceeded due to test-No action needed.

%s, %s has exceded the maximum warning threshold.

%s, %s has dropped below the minimum warning threshold.

%s, %s has exceded the maximum error threshold.

%s, %s has dropped below the minimum error threshold.

%s, %s failed.

%s, %s is offline.

%s, %s is in an unknown state.

%s, %s is in a warning state.

%s, %s is degraded.

%s, %s Shutting down.

%s, %s Shutting down the server.

%s, Virtual Disk (%s) consistency check paused.

%s, Virtual Disk (%s) consistency check resumed.

%s, Virtual Disk (%s) split mirror.

%s, Virtual Disk (%s) unmirrored.

%s, %s renamed to %s.

%s, %s is in a ready state.

%s, %s SES communication timeout.

%s, %s SES communication lost.

%s, %s SES communication restored.

Communication with the Array Manager database is now possible.

Communication with the Array Manager database is NOT possible.

%s Array Manager has lost communication with this RAID controller and subsystem.

%s, %s Sense Key = %s, Sense Code = %s, Sense Qualifier = %s A format unit operation was interrupted prior to completion.

%s, %s Sense Key = %s, Sense Code = %s, Sense Qualifier = %s If this disk is part of a non-redundant virtual disk, the data for this block cannot be recovered.

%s, %s EMMfirmware mismatch (%s / %s.) This is an unsupported configuration. Please download the firmware to this enclosure again to correct this condition.

%s, %s conservative cache mode enabled.

%s, %s conservative cache mode disabled.

%s, %s firmware version %s downloaded successfully.

%s, %s alarm enabled.

%s, %s alarm disabled.

%s, %s alarm enabled.

%s, %s alarm disabled.

%s, rebuild rate changed to %s.

%s, %s forced online.

%s, %s forced offline.

%s, virtual disk %s background initialization started.

%s, virtual disk %s background initialization cancelled.

%s, virtual disk %s background initialization failed.

%s, virtual disk %s background initialization completed.

%s, %s is not installed.

A hard disk has been placed online.

A hard disk added as hot spare.

Hard disk error found.

Hard disk PFA condition found, this disk may fail soon.

An automatic rebuild has started.

A rebuild has started.

Rebuild is over.

Rebuild is cancelled.

Rebuild stopped with error.

Rebuild stopped with error. New device failed.

Rebuild stopped because logical drive failed.

A hard disk has failed.

A new hard disk has been found.

A hard disk has been removed.

A previously configured disk is now available.

Expand Capacity Started.

Expand Capacity Completed.

Expand Capacity Stopped with error.

SCSI command timeout on hard device.

SCSI command abort on hard disk.

SCSI command retried on hard disk.

Parity error found.

Soft error found.

Misc error found.

SCSI device reset.

Active spare found.-

Warm spare found.-

Request Sense Data available.

Initialization started.

Initialization completed.

Initialization failed.

Initialization canceled.

A hard disk failed because write recovery failed.

A hard disk failed because SCSI bus reset failed.

A hard disk failed because double check condition occured.

A hard disk failed because device is missing.

A hard disk failed because of gross error on SCSI processor.

A hard disk failed because of bad tag from the device.

A hard disk failed because command to the device timed out.

A hard disk failed because of the system reset.

A hard disk failed because of busy status or parity error.

A hard disk set to failed state by host.

A hard disk failed because access to the device met with a selection time out.

A hard disk failed because of a sequence error in the SCSI bus phase handling.

A hard disk failed because device returned an unknown status.

A hard disk failed because device is not ready.

A hard disk failed because device was not found on start up.

A hard disk failed because write operation of the 'Configuration On Disk' failed.

A hard disk failed because write operation of 'Bad Data Table' failed.

Physical device status changed to offline.

Physical device status changed to Hot Spare.

Physical device status changed to rebuild.

Physical device ID did not match.

Physical device failed to start.

Physical device negotiated different offset than config.

Physical device negotiated different bus width than config.

Physical drive missing on startup.

Rebuild startup failed due to lower disk capacity.

Physical drive is switching from a channel to the other channel.

Temporary-Dead physical drive is automatically made online.

A standby rebuild has started.

Device Loop Id Conflict (Soft Addressing) Detected.

Consistency check is started.

Consistency check is finished.

Consistency check is cancelled.

Consistency check on logical drive error.

Consistency check on logical drive failed.

Consistency check failed due to physical device failure.

Logical drive has been made offline.

Logical drive is critical.

Logical drive has been placed online.

An automatic rebuild has started on logical drive.

A manual rebuild has started on logical drive.

Rebuild on logical drive is over.

Rebuild on logical drive is cancelled.

Rebuild stopped with error.

Rebuild stopped with error. New device failed.

Rebuild stopped because logical drive failed.

Logical drive initialization started.

Logical drive initialization done.

Logical drive initialization cancelled.

Logical drive initialization failed.

A logical drive has been found.

A logical drive has been deleted.

Expand Capacity Started.

Expand Capacity Completed.

Expand Capacity stopped with error.

Bad Blocks found.

System drive size changed.

System drive type changed.

Bad data blocks found. Possible data loss.

System drive LUN mapping has been written to config.

Attempt to read data from block that is marked in Bad Data Table

Data for Disk Block has been lost due to Logical Drive problem

Temporary-Offline RAID5/RAID3 array is available to the user again with the possibility of data loss in the array.

Temporary-Offline RAID0+1/RAID1/RAID0/JBOD array is available to the user again.

An standby rebuild has started on logical drive.

Fan failure.

Fan has been restored.

Fan failure.

Storage cabinet fan is not present.

Power supply failure.

Power supply has been restored.

Power supply failure.

Storage cabinet power supply is not present.

Over temperature. Temperature is above 70 degrees Celsius.

Temperature is above 50 degrees Celsius.

Normal temperature has been restored.

Over temperature.

Storage cabinet temperature sensor is not present.

Storage Works enclosure reported failure state.

Storage Works enclosure reported critical state.

Storage Works enclosure reported normal state.

Uninterruptible Power Supply Disabled.

Uninterruptible Power Supply AC Failed.

Uninterruptible Power Supply Battery Low.

Uninterruptible Power Supply Failed.

Uninterruptible Power Supply Normal.

Fan failure.

Fan has been restored.

Fan is not present.

Power supply failure.

Power supply has been restored.

Power supply is not present.

Temperature is over safe limit. Failure imminent.

Temperature is above working limit.

Normal temperature has been restored.

Temperature sensor is not present.

Enclosure access critical.

Enclosure access has been restored.

Enclosure access is offline.

Enclosure Soft Addressing Detected.

Enclosure services ready

Access to temperature sensor has been lost.

Access to power supply status information has been lost.

Access to fan status information has been lost.

Array management server software started successfully.

Write back error.

Internal log structures getting full,PLEASE SHUTDOWN AND RESET THE SYSTEM IN THE NEAR FUTURE.

Controller is dead. System is disconnecting from this controller.

Controller has been reset.

Controller is found.

Controller is gone. System is disconnecting from this controller.

BBU Present.

BBU Power Low.

BBU Power OK.

Controller is powered off.

Controller powered on

Controller is online.

Controller is offline.

Controller's partner is gone, controller is in failover mode now.

BBU reconditioning is started.

BBU reconditioning is finished.

BBU reconditioning is canceled.

Installation aborted.

Controller firmware mismatch.

BBU removed.

WARM BOOT failed.

Controller entered Conservative Cache Mode.

Controller entered Normal Cache Mode.

Controller Device Start Complete.

Soft ECC error Corrected.

Hard ECC error Corrected.

BBU Recondition Suggested.

Controller's Partner Has Been Removed.

BBU out of service.

Updated partner's status.

Relinquished partner.

Inserted Partner.

Dual Controllers Enabled.

Killed Partner.

Dual Controllers entered Nexus.

Controller Boot ROM Image needs to be reloaded.

Controller is using default non-unique world-wide name.

Mirror Race recovery failed.

Mirror Race on critical drive.

System started.-

Size table full.

User logged in.

User logged out.-

Server alive.

Lost connection to server, or server is down.

Automatic reboot count has changed.

Channel Failed.

Channel Online.

Back End SCSI Bus Dead.

Back End SCSI Bus Alive.

Back End Fibre Dead.

Back End Fibre Alive.

Event Log Empty.

Event Log Entries Lost.

Request Sense

Set Real Time Clock.

New Configuration Received.

Configuration Cleared.

Configuration Invalid.

Configuration On Disk Access Error.

Configuration On Disk Converted.

Configuration On Disk Import Failed.

A Debug Dump exists on this system.

A Debug Dump exists on this system.

Internal Controller is in the hung state.

Internal Controller has encountered a Firmware breakpoint.

Internal Controller has encountered i960 processor specific error.

Internal Controller has encountered Strong-ARM processor specific error

Logical drive background initialization started.

Logical drive background initialization stopped.

Logical drive background initialization paused.

Logical drive background initialization restarted.

Logical drive background initialization failed.

Logical drive background initialization completed.

BBU calibration cycle started.

BBU calibration cycle finished.

BBU calibration cycle is canceled.

BBU battery not present.

Low battery charge level. Logical drive may have lost data.

Controller connected to cluster.

Controller disconnected from cluster.

Controller improperly shutdown! Data may have been lost.

Dual Active Automatic Flash of Replacement Controller.

Dual Active Negotiation failed jumpers.

Dual Active Negotiation failed ID's.

Dual Active Negotiation failed board types.

Dual Active Negotiation failed disk channels.

Dual Active Negotiation failed host ports.

Dual Active Negotiation failed memory size.

Dual Active Negotiation failed cache memory size.

Hot spare replaced with a smaller capacity drive.

Controller failed, SES not operational. This trap is similar to 981 but may occur for older firmware versions.

Unable to get enclosure status. Doing a PV660F Subsystem rescan may resolve this problem. This trap is similar to 980 but may occur for more recent firmware versions.

Free disk space has reached warning threshold on volume %s.

Free disk space has reached error threshold on volume %s.