CPQIDA-MIB: View SNMP OID List / Download MIB

The Major Revision level. A change in the major revision level represents a major change in the architecture of the MIB. A change in the major revision level may indicate a significant change in the information supported and/or the meaning of the supported information, correct interpretation of data may require a MIB document with the same major revision level.

The Minor Revision level. A change in the minor revision level may represent some minor additional support, no changes to any pre-existing information has occurred.

The overall condition (status) of the system represented by this MIB. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

Array Controller Driver Interface Name. This is the name of the device driver for the Array Controllers.

Array Controller Driver Interface Version. This is the version number of the device driver for the Array Controllers.

Array Controller Driver Interface Poll Type. The Insight Agent collects information from the device driver in two ways: Polled (2) Indicates that the information is periodically requested and stored by the server based agent and is available when requested. Demand (3) Indicates that the information is collected at the time of the request. Enumeration: 'polled': 2, 'other': 1, 'demand': 3.

Array Controller Driver Interface Poll Time. If the Poll Type is Polled, this value shows how frequently, in seconds, the instrument agent requests Information from the device driver. For example, if the Poll Type is Polled and the Poll Time is two, the instrument agent will poll the device driver every two seconds. To change the Poll Time for NetWare, unload and then reload the instrument agent using the following commands: UNLOAD CPQDSKSA LOAD CPQDSKSA [/Un] The parameter /U specifies the frequency of updates in seconds. The variable n represents the number of seconds that the NLM should wait before collecting new data. The minimum value is one second. The maximum value is 300 seconds (five minutes).

Array Controller Driver Statistics Table. This is a table of logical drive statistics which are gathered by the device driver.

Array Controller Driver Statistics Table Entry. One entry in the driver statistics table. Each entry represents a logical drive for which the statistics are kept.

Array Controller Index. This maps the logical drives into their respective controllers. This controller index matches the controller group entries.

Array Logical Drive Index. This is the logical drive number which keeps track of multiple instances of logical drives which are on the same controller. For each controller index value, the logical drive index starts at 1 and increments for each logical drive.

Array Logical Drive Total Reads. This shows the total number of reads performed by the IDA device driver to this logical drive. This number is reset each time the device driver is loaded for this logical drive.

Array Logical Drive Total Writes. This shows the total number of writes performed by the IDA device driver to this logical drive. This number is reset each time the device driver is loaded for this logical drive.

Array Logical Drive Corrected Reads. This is the total number of read commands sent to the specified logical drive which had to be corrected by fault tolerance. This number is reset each time the device driver is loaded for this logical drive. If the number of corrected reads is higher than normal for a particular system, check the physical drive screen for abnormal activity. There may be a problem with a drive. If you suspect that a problem exists, schedule server down time to run diagnostics on the monitored system.

Array Logical Drive Corrected Writes. This is the total number of write commands sent to the specified logical drive which had to be corrected by fault tolerance. This number is reset each time the device driver is loaded for this logical drive. If the number of corrected writes is higher than normal for a particular system, check the physical drive screen for abnormal activity. There may be a problem with a drive. If you suspect that a problem exists, schedule server down time to run diagnostics on the monitored system.

Array Logical Drive Fatal Reads. This is the total number of read commands sent to the specified logical drive which failed. This number is reset each time the device driver is loaded for this logical drive. The drive array was unable to correct these reads. Check the drive status to see if any of the drives have failed. If a drive has failed you will need to replace the drive.

Array Logical Drive Fatal Writes. This is the total number of write commands sent to the specified logical drive which failed. This number is reset each time the device driver is loaded for this logical drive. The drive array was unable to correct these writes. Check the drive status to see if any of the drives have failed. If a drive has failed you will need to replace the drive.

Volume Map Table. This is a table of NetWare volumes which map into the logical drives

Volume Map Table Entry. One entry in the volume map table. Each entry represents a logical drive for which the volume map is kept.

Array Controller Index. This maps the logical drives into their respective controllers. This controller index matches the controller group entries.

Array Logical Drive Index. This is the logical drive number which keeps track of multiple instances of logical drives which are on the same controller. For each controller index value, the logical drive index starts at 1 and increments for each logical drive.

NetWare Volume Map. This is a data structure containing the volume mappings for this logical drive. There are 8 entries in a volume mapping. Each entry has the following format. An entry can be null indicating no mapping exists. BYTE Name[16] BYTE Segment

The Insight Agent's polling frequency. The frequency, in seconds, at which the Insight Agent requests information from the device driver. A frequency of zero (0) indicates that the Insight Agent retrieves the information upon request of a management station, it does not poll the device driver at a specific interval. If the poll frequency is zero (0) all attempts to write to this object will fail. If the poll frequency is non-zero, setting this value will change the polling frequency of the Insight Agent. Setting the poll frequency to zero (0) will always fail, an agent may also choose to fail any request to change the poll frequency to a value that would severely impact system performance.

A table of software modules that provide an interface to the device this MIB describes.

A description of a software module that provides an interface to the device this MIB describes.

A unique index for this module description.

The module name.

The module version in XX.YY format. Where XX is the major version number and YY is the minor version number. This field will be a null (size 0) string if the agent cannot provide the module version.

The module date. field octets contents range ===== ====== ======= ===== 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minute 0..59 6 7 second 0..60 (use 60 for leap-second) This field will be set to year = 0 if the agent cannot provide the module date. The hour, minute, and second field will be set to zero (0) if they are not relevant. The year field is set with the most significant octect first.

The purpose of the module described in this entry.

Drive Array MIB Collection Reset. This variable is used to force the collection agent for this MIB to scan the associated hardware for configuration changes. The following values are defined: other(1) The agent is unable to determine if collection reset is supported. Any attempts to write to this variable will be ignored. resetSupported(2) The agent supports collection reset. A value of doReset(4) may be written to force a collection reset. resetNotSupported(3) The agent does not support collection reset. Any attempts to write to this variable will be ignored. doReset(4) This is a write only value used to cause a collection reset. Writing this value is only allowed when a read of this variable returns resetSupported(2). Enumeration: 'resetNotSupported': 3, 'other': 1, 'doReset': 4, 'resetSupported': 2.

Array Controller Table.

Array Controller Entry.

Array Controller Index. This value is a logical number whose meaning is OS dependent. Each physical controller has one unique controller number associated with it.

Array Controller Model. The type of controller card. The valid types are: Other (1) You may need to upgrade your driver software and\or instrument agent(s). You have a drive array controller in the system that the instrument agent does not recognize. IDA (2) Compaq 32-Bit Intelligent Drive Array Controller. The physical drives are located inside the system. IDA Expansion (3) Compaq 32-Bit Intelligent Drive Array Expansion Controller. The physical drives are located in the Array Expansion System that is connected to the system by a cable. IDA - 2 (4) Compaq Intelligent Drive Array Controller-2 (IDA-2). The physical drives are located inside the system. SMART (5) Compaq SMART Array Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. SMART - 2/E (6) Compaq SMART-2/E Array Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. SMART - 2/P (7) Compaq SMART-2/P Array Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. SMART - 2SL (8) Compaq SMART-2SL Array Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. Smart - 3100ES (9) Compaq Smart Array 3100ES Controller. The physical drives are located inside the system. Smart - 3200 (10) Compaq Smart Array 3200 Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. SMART - 2DH (11) Compaq SMART-2DH Array Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. Smart - 221 (12) Compaq Smart Array 221 Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. Smart Array 4250ES (13) Compaq Smart Array 4250ES Controller. The physical drives are located inside the system. Smart Array 4200 (14) Compaq Smart Array 4200 Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. Integrated Smart Array (15) Compaq Integrated Smart Array Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. Smart Array 431 (16) Compaq Smart Array 431 Controller. The physical drives can be located inside the system or outside the system in a ProLiant Storage System that is connected to the system by a cable. Smart Array 5300 (17) HP Smart Array 5300 Controller. RAID LC2 Controller (18) Compaq RAID LC2 Controller. Smart Array 5i (19) HP Smart Array 5i Controller. Smart Array 532 (20) Compaq Smart Array 532 Controller. Smart Array 5312 (21) Compaq Smart Array 5312 Controller. Smart Array 641 (22) HP Smart Array 641 Controller. Smart Array 642 (23) HP Smart Array 642 Controller. Smart Array 6400 (24) HP Smart Array 6400 Controller. Smart Array 6400 EM (25) HP Smart Array 6400 EM Controller. Smart Array 6i (26) HP Smart Array 6i Controller. Generic Array (27) Array Controller. Reserved (28) Smart Array P600 (29) HP Smart Array P600 Controller. Smart Array P400 (30) HP Smart Array P400 Controller. Smart Array E200 (31) HP Smart Array E200 Controller. Smart Array E200i (32) HP Smart Array E200i Controller. Smart Array P400i (33) HP Smart Array P400i Controller. Smart Array P800 (34) HP Smart Array P800 Controller. Smart Array E500 (35) HP Smart Array E500 Controller. Smart Array P700m (36) HP Smart Array P700m Controller. Smart Array P212 (37) HP Smart Array P212 Controller. Smart Array P410 (38) HP Smart Array P410 Controller. Smart Array P410i (39) HP Smart Array P410i Controller. Smart Array P411 (40) HP Smart Array P411 Controller. Smart Array B110i SATA RAID (41) HP Smart Array B110i SATA RAID Controller. Smart Array P712m (42) HP Smart Array P712m Controller. Smart Array P711m (43) HP Smart Array P711m Controller. Smart Array P812 (44) HP Smart Array P812 Controller. StorageWorks 1210m (45) HP StorageWorks 1210m Scalable Storage Controller. Smart Array P220i (46) HP Smart Array P220i Controller. Smart Array P222 (47) HP Smart Array P222 Controller. Smart Array P420 (48) HP Smart Array P420 Controller. Smart Array P420i (49) HP Smart Array P420i Controller. Smart Array P421 (50) HP Smart Array P421 Controller. Smart Array B320i (51) HP Dynamic Smart Array B320i Controller. Smart Array P822 (52) HP Smart Array P822 Controller. Smart Array P721m (53) HP Smart Array P721m Controller. Smart Array B120i (54) HP Dynamic Smart Array B120i Controller. HP Storage p1224 (55) HP Storage p1224 Array Controller. HP Storage p1228 (56) HP Storage p1228 Array Controller. HP Storage p1228m (57) HP Storage p1228m Array Controller. Smart Array P822se (58) HP Smart Array P822se Controller. HP Storage p1224e (59) HP Storage p1224e Array Controller. HP Storage p1228e (60) HP Storage p1228e Array Controller. HP Storage p1228em (61) HP Storage p1228em Array Controller. Smart Array P230i (62) HP Smart Array P230i Controller. Smart Array P430i (63) HP Smart Array P430i Controller. Smart Array P430 (64) HP Smart Array P430 Controller. Smart Array P431 (65) HP Smart Array P431 Controller. Smart Array P731m (66) HP Smart Array P731m Controller. Smart Array P830i (67) HP Smart Array P830i Controller. Smart Array P830 (68) HP Smart Array P830 Controller. Smart Array P831 (69) HP Smart Array P831 Controller. Enumeration: 'sa-p831': 69, 'sa-4250es': 13, 'sa-5300': 17, 'smart-3100es': 9, 'sa-6i': 26, 'sa-p411': 40, 'sa-p410': 38, 'smart-2p': 7, 'sa-e200': 31, 'sa-p822': 52, 'sa-p431': 65, 'sa-p430': 64, 'sa-p711m': 43, 'sa-p830': 68, 'sw-1210m': 45, 'hps-1228em': 61, 'sa-p600': 29, 'sa-e500': 35, 'smart-2e': 6, 'raidLc2': 18, 'sa-p212': 37, 'smart-2dh': 11, 'smart-2sl': 8, 'sa-p731m': 66, 'hps-1224e': 59, 'hps-1228': 56, 'sa-6400': 24, 'sa-p400i': 33, 'other': 1, 'sa-p400': 30, 'idaExpansion': 3, 'sa-p721m': 53, 'sa-p230i': 62, 'sa-generic': 27, 'smart': 5, 'sa-p420i': 49, 'sa-5i': 19, 'sa-p410i': 39, 'hps-1224': 55, 'sa-e200i': 32, 'sa-5312': 21, 'sa-p420': 48, 'sa-p700m': 36, 'sa-p800': 34, 'sa-p421': 50, 'sa-p830i': 67, 'sa-p812': 44, 'hps-1228m': 57, 'sa-532': 20, 'smart-3200': 10, 'sa-p712m': 42, 'hps-1228e': 60, 'sa-b320i': 51, 'sa-4200': 14, 'sa-b120i': 54, 'sa-6400em': 25, 'sa-p220i': 46, 'sa-p222': 47, 'sa-642': 23, 'sa-641': 22, 'sa-p822se': 58, 'sa-431': 16, 'sa-integrated': 15, 'smart-221': 12, 'sa-p430i': 63, 'sa-b110i': 41, 'ida-2': 4, 'ida': 2.

Array Controller Firmware Revision. The firmware revision of the drive array controller. This value can be used to help identify a particular revision of the controller. For B-Series controllers this value is the RAID Stack Revision that is running and this value may change when upgrading or downgrading the operating system device driver.

The status of the Standard Interface. The Standard Interface is how DOS communicates with a drive. The following values are valid for Standard Interface: Other (1) The device driver may not be loaded for this controller. The instrument agent could not read the information from the device. Please load the device driver. Primary (2) The Standard Interface is using the primary address for communication. DOS can access this drive and use this drive as the primary boot device if it has been configured for this purpose. Secondary (3) The Standard Interface is using the secondary address for communication. DOS can access these drives, but cannot boot from them. Disabled (4) The Standard Interface is not enabled for communication. DOS will not be able to access these drives. Unavailable (5) This controller does not support a Standard Interface. DOS cannot access these drives. Enumeration: 'disabled': 4, 'unavailable': 5, 'other': 1, 'primary': 2, 'secondary': 3.

Array Controller Slot. This identifies the physical slot where the array controller resides in the system. For example, if this value is three, the array controller is located in slot three of your computer.

The condition of the device. This value represents the overall condition of this controller, and any associated logical drives, physical drives, and cache modules. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

Array Controller Product Revision. The Product Revision of the drive array controller. This value can be used to further identify a particular revision of the controller model. This will be one character ASCII value that is zero terminated. If the controller model or the firmware does not support the product revision, the agents will return a NULL string.

Array Controller Partner Slot. For duplexed array controllers, this is the slot number of the partner controller. For non-duplexed controllers and partner controllers that reside in a separate host system, the value should be -1.

Array Controller Current Role. For duplexed array controllers, this is the controllers current role. The following values are valid: other (1) Indicates that the instrument agent does not recognize the role of the controller. You may need to upgrade the instrument agent. notDuplexed (2) This array controller is not duplexed. active (3) This duplexed array controller is the active controller. backup (4) This duplexed array controller is the backup controller. asymActiveActive (5) This array controller is part of an asymmetrical active-active set of controllers. Enumeration: 'active': 3, 'notDuplexed': 2, 'asymActiveActive': 5, 'other': 1, 'backup': 4.

Array Controller Board Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the status of the controller. You may need to upgrade the instrument agent. ok (2) The array controller is operating properly. generalFailure (3) The array controller is failed. After the system is rebooted, check the variable cpqDaCntlrLastLockupCode for the controller's last lockup code. cableProblem (4) The array controller has a cable problem. Please check all cable connections to this controller. poweredOff (5) The array controller is powered off. Please replace the controller and restore power to the slot. cacheModuleMissing (6) The array controller is operating without a cache module which is an unsupported configuration. Please install a cache module to the controller. Enumeration: 'generalFailure': 3, 'cableProblem': 4, 'cacheModuleMissing': 6, 'poweredOff': 5, 'other': 1, 'ok': 2.

Array Controller Partner Board Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the status of the controller. You may need to upgrade the instrument agent. ok (2) The partner array controller is operating properly. generalFailure (3) The partner array controller is failed. cableProblem (4) The partner array controller has a cable problem. Please check all cable connections to this controller. poweredOff (5) The array controller is powered off. Please replace the controller and restore power to the slot. Enumeration: 'generalFailure': 3, 'cableProblem': 4, 'other': 1, 'ok': 2, 'poweredOff': 5.

The condition of the device. This value represents the condition of the controller and any associated cache modules. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

The condition of the device. This value represents the condition of the controller and any associated cache modules. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

Array Controller Drive Ownership. For duplexed controllers, indicates to which controller slot the shared devices are associated. The following values are valid: other (1) Indicates that the instrument agent does not recognize the status of the controller. You may need to upgrade the instrument agent. owner (2) All the logical, physical and spare drives are associated with this controller. notOwner (3) The logical, physical and spare drives are not associated with this controller. Enumeration: 'owner': 2, 'notOwner': 3, 'other': 1.

Array Controller Serial Number. The serial number of the array controller. This field will be a null (size 0) string if the controller does not support serial number.

Array Controller Redundancy Type. The following values are valid: other (1) Indicates that the instrument agent does not recognize the redundancy type of the controller. You may need to upgrade the instrument agent. notRedundant (2) The array controller is not in a redundant configuration. driverDuplexing (3) The array controller is using a controller duplexing algorithm implemented exclusively in the operating system driver. fwActiveStandby (4) The array controller is using an active/standby algorithm implemented in the controller firmware and the operating system driver. fwPrimarySecondary (5) The array controller is using a primary/secondary algorithm implemented in the controller firmware and the operating system driver. fwActiveActive (6) The array controller is using an active/active algorithm implemented in the controller firmware. Enumeration: 'fwActiveStandby': 4, 'fwActiveActive': 6, 'other': 1, 'driverDuplexing': 3, 'fwPrimarySecondary': 5, 'notRedundant': 2.

Array Controller Redundancy Error. The following values are valid: other (1) Indicates that the instrument agent does not recognize the redundancy error of the controller. You may need to upgrade the instrument agent. noFailure (2) No failures have been detected. noRedundantController (3) No redundant controller is installed. differentHardware (4) The other controller indicates a different hardware model. noLink (5) An inter-controller link to the other controller could not be established. differentFirmware (6) The other controller indicates a different firmware version. differentCache (7) The other controller indicates a different cache size. otherCacheFailure (8) The other controller indicates a cache failure. noDrives (9) This controller cannot see any attached drives, but the other controller can. otherNoDrives (10) This controller can see the attached drives, but the other controller cannot. unsupportedDrives (11) One or more attached drives has been determined to be incapable of properly supporting redundant controller operation. expandInProgress (12) Expand operation in progress. Redundant operation not supported until expand operation is complete. Enumeration: 'noDrives': 9, 'noLink': 5, 'expandInProgress': 12, 'noRedundantController': 3, 'unsupportedDrives': 11, 'other': 1, 'noFailure': 2, 'differentCache': 7, 'otherCacheFailure': 8, 'differentFirmware': 6, 'otherNoDrives': 10, 'differentHardware': 4.

Array Controller RAID ADG Enabler Module Status. The following values are valid: other (1) Indicates that the agent does not recognize the RAID ADG Enabler Module status. You may need to upgrade the agent. notSupported (2) Indicates that the RAID ADG Enabler Module is not supported on this type of controller. notPresent (3) Indicates that the RAID ADG Enabler Module is not present or is not accessible. badSignature (4) Indicates that the RAID ADG Enabler Module is present, but has an incorrect signature. badChecksum (5) Indicates that the RAID ADG Enabler Module is present, but the checksum failed. fullyFunctional (6) Indicates that the RAID ADG Enabler Module is present and fully functional. upgradeFirmware (7) Indicates that the RAID ADG Enabler Module is present, but a firmware upgrade is required to make it fully functional. Enumeration: 'upgradeFirmware': 7, 'badChecksum': 5, 'badSignature': 4, 'other': 1, 'fullyFunctional': 6, 'notPresent': 3, 'notSupported': 2.

Array Controller Daughter Board Type. The following values are valid: other (1) Indicates that the agent does not recognize the daughter board type. You may need to upgrade the agent. notSupported (2) Indicates that the daughter board type field is not supported on this type of controller. notPresent (3) Indicates that no daughter board is present. scsiBoardPresent (4) Indicates that the SCSI daughter board is present. fibreBoardPresent (5) Indicates that the Fibre daughter board is present. arrayExpansionModulePresent (6) Indicates that an array Expansion Module is present. Enumeration: 'scsiBoardPresent': 4, 'other': 1, 'arrayExpansionModulePresent': 6, 'notPresent': 3, 'notSupported': 2, 'fibreBoardPresent': 5.

A text description of the hardware location of the controller. A NULL string indicates that the hardware location could not be determined or is irrelevant.

Array Controller Number of Buses. This value is the number of SCSI buses on the controller.

Controller Physical Drive Blink Time Count. The controller blink time variable allows the drive tray LEDs of all physical drives attached to this controller to blink. This value indicates the amount of time, in tenths of a second, that the physical drive LEDs will continue to blink. A value of zero indicates the drive LEDs are not blinking. If the value cannot be determined or no drive on this controller is in a hot plug tray, 4,294,967,295 is returned. To blink the drive LEDs on all physical drives attached to this controller, set this value to the time to blink in tenths of seconds. To stop the drive LEDs from blinking, set this value to 0.

Array Controller Rebuild Priority. This is the controller's rebuild priority. The following values are valid: other (1) Indicates that the instrument agent does not recognize the rebuild priority of the controller. You may need to upgrade the instrument agent. low (2) The rebuild priority is low. medium (3) The rebuild priority is medium. high (4) The rebuild priority is high. Enumeration: 'high': 4, 'medium': 3, 'other': 1, 'low': 2.

Array Controller Expand Priority. This is the controller's expand priority. The following values are valid: other (1) Indicates that the instrument agent does not recognize the expand priority of the controller. You may need to upgrade the instrument agent. low (2) The expand priority is low. medium (3) The expand priority is medium. high (4) The expand priority is high. Enumeration: 'high': 4, 'medium': 3, 'other': 1, 'low': 2.

Array Controller Number of Internal Ports. This value is the number of internal connectors on the controller.

Array Controller Number of External Ports. This value is the number of external connectors on the controller.

Array Controller Drive Write Cache State. This is the controller's drive write cache setting. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. disabled (2) The controller will disable drive write cache for all drives. enabled (3) The controller will enable drive write cache for all drives. Enumeration: 'disabled': 2, 'other': 1, 'enabled': 3.

Array Controller Partner Serial Number. The serial number of the partner array controller. This field will be a null (size 0) string if the partner controller does not support serial number or in the absence of a partner controller.

Array Controller Option ROM Revision. The option ROM revision of the chipset or HBA being used by the B-Series controller. If the controller does not support the option ROM revision, the agents will return a NULL string.

Array Controller HBA Firmware Revision. The firmware revision of the chipset or HBA being used by the B-Series controller. If the controller does not support the HBA firmware revision, the agents will return a NULL string.

Array Controller HBA Mode Option Rom Revision. The revision of option ROM that would run on this chipset or HBA (being used by the B-Series controller), if it were to run in HBA mode. If the controller does not support HBA mode option ROM revision, the agents will return a NULL string.

Array Controller Current Temperature. This is the temperature of the array controller in degrees Celsius. The field will contain -1 if the controller temperature cannot be calculated or if the controller does not support reporting temperature.

Array Controller Last Lockup Code. The lockup code of the array controller if a lockup occurred prior to the last controller reset. This value will be nonzero if the controller supports last lockup code and has a last lockup code to report.

Array Controller Encryption Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. notEnabled (2) Indicates that controller encryption is not enabled. Check other controller encryption values for further details. enabledLocalKeyMode (3) Array controller encryption is enabled and is configured to operate in local key mode. enabledRemoteKeyManagerMode (4) Array controller encryption is enabled and is configured to operate in remote key manager mode. Enumeration: 'other': 1, 'notEnabled': 2, 'enabledRemoteKeyManagerMode': 4, 'enabledLocalKeyMode': 3.

Array Controller ASIC Encryption Self Test Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. selfTestsPass(2) Indicates that ASIC encryption self tests for this array controller have passed. selfTestsFailed (3) Indicates that ASIC encryption self tests for this array controller have failed. The array controller is not encrypted. Enumeration: 'other': 1, 'selfTestsFailed': 3, 'selfTestsPass': 2.

Array Controller Encryption Critical Security Parameter NVRAM Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. ok(2) Indicates that the array controller has successfully detected CSP NVRAM. detectionFailed (3) Indicates that the array controller has failed to detect CSP NVRAM. The controller is not encrypted. Enumeration: 'other': 1, 'ok': 2, 'detectionFailed': 3.

Array Controller Encryption Crypto Officer Password Set Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. false(2) Indicates that the array controller's Crypto Officer password has not been set. true(3) Indicates that the array controller's Crypto Officer password has been set. Enumeration: 'true': 3, 'other': 1, 'false': 2.

Array Controller Encryption Controller Password Set Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. false(2) Indicates that the controller password has not been set. true(3) Indicates that the controller password has been set. Enumeration: 'true': 3, 'other': 1, 'false': 2.

Array Controller Encryption Controller Password Availability Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. passwordMissing (2) Indicates that the array controller password is missing. One or more encrypted drives are currently locked and inaccessible. passwordActive (3) Indicates that the array controller password is active and in use. Enumeration: 'other': 1, 'passwordMissing': 2, 'passwordActive': 3.

Array Controller Unencrypted Logical Drive Creation Policy. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. false (2) Unencrypted logical drive creation is not allowed. Check Smart Array controller documentation for further information. true(3) Unencrypted logical drive creation is allowed. Enumeration: 'true': 3, 'other': 1, 'false': 2.

Array Controller Encrypted Logical Drive Creation Policy. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. false (2) Encrypted logical drive creation is not allowed. Check Smart Array controller documentation for further information. true(3) Encrypted logical drive creation is allowed. Enumeration: 'true': 3, 'other': 1, 'false': 2.

Array Controller Encryption Firmware Lock Status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. false(2) Indicates that the array controller's firmware is not locked. true(3) Indicates that the array controller's firmware has been locked. Enumeration: 'true': 3, 'other': 1, 'false': 2.

Cache Module Board Table. Note that for some controller models, a cache module board that physically attaches to the controller or chipset may not be an available option. For these configurations, the Instrument Agent will continue to populate variables that are related to read caching operations.

Cache Module Board Entry.

Cache Module Board Controller Index. This value is a logical number whose meaning is OS dependent. The value has a direct mapping to the controller table index such that controller 'i' has cache module table entry 'i'.

Cache Module/Operations Status. This describes the status of the cache module and/or cache operations. Note that for some controller models, a cache module board that physically attaches to the controller or chipset may not be an available option. For these configurations, the Instrument Agent will continue to populate variables that are related to read caching operations. The status can be: Other (1) Indicates that the instrument agent does not recognize the status of the cache module. You may need to upgrade the instrument agent. Invalid (2) Indicates that a cache module board has not been installed in this system or is present but not configured. Enabled (3) Indicates that cache operations are currently configured and enabled for at least one logical drive. Temporarily Disabled (4) Indicates that cache operations have been temporarily disabled. View the cache module board error code object to determine why the write cache operations have been temporarily disabled. Permanently Disabled (5) Indicates that cache operations have been permanently disabled. View the cache module board error code object to determine why the write cache operations have been disabled. Cache Module Flash Memory Not Attached (6) Indicates that the flash memory component of the flash backed cache module is not attached. This status will be set when the flash memory is not attached and the Supercap is attached. This value is only used on flash backed cache modules that support removable flash memory. Cache Module Degraded Failsafe Speed (7) Indicates that the cache module board is currently degraded and operating at a failsafe speed. View variables cpqDaCacheMemoryDataWidth and cpqDaCacheMemoryTransferRate to obtain the cache module board's current memory data width and memory transfer rate. Cache Module Critical Failure (8) Indicates that the cache module board has encountered a critical failure. The controller is currently operating in Zero Memory Raid mode. Read Cache Could Not Be Mapped (9) Indicates that the read cache memory in a split cache configuration could not be mapped by the operating system and as a result is not available. This status may be caused by virtual space limitations in certain operating systems and is only applicable to B-Series controllers. Enumeration: 'cacheReadCacheNotMapped': 9, 'cacheModFlashMemNotAttached': 6, 'tmpDisabled': 4, 'enabled': 3, 'invalid': 2, 'other': 1, 'cacheModCriticalFailure': 8, 'permDisabled': 5, 'cacheModDegradedFailsafeSpeed': 7.

Write Cache Memory. This shows the amount of memory allocated for the write cache in kilobytes. Because data is kept in duplicate (mirrored), the actual amount of usable memory is half the amount shown.

Cache Module Board Bad Data. The following values are valid: None (2) Indicates that no data loss occurred. The battery packs were properly charged when the system was initialized. Possible (3) Indicates that at power up, the battery packs were not sufficiently charged. Because the batteries did not retain sufficient charge when the system resumed power, the board has not retained any data that may have been stored. If no data was on the board, no data was lost. Several things may have caused this condition: * If the system was without power for eight days, and the battery packs were on (battery packs only activate if system looses power unexpectedly), any data that may have been stored in the cache was lost. * There may be a problem with the battery pack. See the Battery Status for more information. * This status will also appear if the Cache Module board is replaced with a new board that has discharged batteries. No data has been lost in this case, and posted writes will automatically be enabled when the batteries reach full charge. Enumeration: 'none': 2, 'other': 1, 'possible': 3.

Cache Module Board Error Code. Use this to determine the status of the write cache operations. The status can be: Other (1) Indicates that the instrument agent does not recognize the error code. You may need to update your software. Invalid (2) Indicates that write cache operations are currently configured and enabled for at least one logical drive. No write cache errors have occurred. Bad Configuration (3) Indicates that write cache operations are temporarily disabled. The Cache Module board was configured for a different controller. This error could be caused if boards were switched from one system to another. Rerun the configuration utility and ensure that the board has been properly configured for this system. Note: If data from another system was stored on the board, running configuration utility will cause the data to be lost. Low Battery Power (4) Indicates that write cache operations are temporarily disabled due to insufficient battery power. Please view the Battery Status object instance for more information. Disable Command Issued (5) Indicates that write cache operations are temporarily disabled. The device driver issues this command when the server is taken down. This condition should not exist when the system regains power. No Resources Available (6) Indicates that write cache operations are temporarily disabled. The controller does not have sufficient resources to perform write cache operations. For example, when a replaced drive is being rebuilt, there will not be sufficient resources. Once the operation that requires the resources has completed, this condition will clear and write cache operations will resume. Board Not Connected (7) Indicates that write cache operations are temporarily disabled. The Cache Module board has been configured but is not currently attached to the controller. Check the alignment of the board and connections. Bad Mirror Data (8) Indicates that write cache operations have been permanently disabled. The Cache Module board stores mirrored copies of all data. If data exists on the board when the system is first powered up, the board performs a data compare test between the mirrored copies. If the data does not match, an error has occurred. Data may have been lost. Your board may need servicing. Read Failure (9) Indicates that write cache operations have been permanently disabled. The Cache Module board stores mirror copies of all data. While reading the data from the board, memory parity errors have occurred. Both copies were corrupted and cannot be retrieved. Data has been lost, and you should service the board. Write Failure (10) Indicates that write cache operations have been permanently disabled. This error occurs when an unsuccessful attempt was made to write data to the Cache Module board. Data could not be written to write cache memory in duplicate due to the detection of parity errors. This error does not indicate data loss. You should service the Cache Module board. Config Command (11) Indicates that write cache operations have been permanently disabled. The configuration of the logical drives has changed. You need to reconfigure the Cache Module board. Expand in Progress (12) Indicates that cache operations are temporarily disabled due to an expand of a logical drive. When the expand operation completes, the cache module will be enabled. Snapshot In Progress (13) Indicates that cache operations are temporarily disabled due to a snapshot operation that is queued up or in progress. When the snapshot operation completes, the cache module will be enabled. Redundant Low Battery (14) Indicates that cache operations are temporarily disabled. The redundant controller has insufficient cache battery power. Redundant Size Mismatch (15) Indicates that cache operations are temporarily disabled. The cache sizes on the redundant controllers do not match. Redundant Cache Failure (16) Indicates that cache operations are temporarily disabled. The cache on the redundant controller has failed. Excessive ECC Errors (17) Indicates that write cache operations have been permanently disabled. The number of cache lines experiencing excessive ECC errors has reached a preset limit. RAID ADG Enabler Module Missing (18) Indicates that write cache operations have been temperarily disabled. A RAID ADG logical drive is configured but the RAID ADG Enabler Module is broken or missing. Power On Self Test (Post) ECC Errors (19) Indicates that write cache operations have been permanently disabled. The cache has been disabled due to a large number of ECC errors detected while testing the cache during Power On Self Test (Post). Backup Power Source Hot Removed (20) Indicates that write cache operations have been permanently disabled. The cache has been disabled because a backup power source has been hot removed. Flash Backed Cache Module Capacitor Charge Low (21) Indicates that write cache operations are temporarily disabled due to insufficient capacitor power. Not Enough Batteries (22) Indicates that write cache operations have been permanently disabled. The cache has been disabled because there are not enough batteries attached to the controller to ensure write cache will be held without power for the advertised length of time. Cache Module Not Supported By Firmware (23) Indicates that write cache operations have been permanently disabled. The cache has been disabled because the current cache module is not supported by the currently running firmware. Battery Not Supported (24) Indicates that write cache operations have been permanently disabled. The cache has been disabled because one or more attached batteries are not supported by the currently running firmware. No Capacitor Attached (25) Indicates that write cache operations have been permanently disabled. The cache has been disabled because there are no capacitors attached to the flash backed cache module. Flash Backed Cache Module Backup Failed (26) Indicates that write cache operations have been permanently disabled. The cache has been disabled because the flash backed cache module backup operation has failed. Flash Backed Cache Module Restore Failed (27) Indicates that write cache operations have been permanently disabled. The cache has been disabled because the flash backed cache module restore operation has failed. Flash Backed Cache Module Hardware Failure (28) Indicates that write cache operations have been permanently disabled. The cache has been disabled because the flash backed cache module has encountered a hardware failure. Capacitor Failed To Charge (29) Indicates that write cache operations have been permanently disabled. The cache has been disabled because the flash backed cache module capacitor has failed to charge. Flash Backed Cache Module Memory Being Erased (30) Indicates that write cache operations have been temporarily disabled. The cache has been disabled because the flash backed cache module is erasing its flash memory. Incompatible Cache Module (31) Indicates that write cache operations have been permanently disabled. The cache has been disabled because an incompatible cache module is being used. Flash Backed Cache Module Charger Circuit Failure (32) Indicates that write cache operations have been permanently disabled. The cache has been disabled because the charger circuit on the flash backed cache module has failed. Enumeration: 'noResources': 6, 'capacitorBasedHWMemBeingErased': 30, 'batteryHotRemoved': 20, 'badConfig': 3, 'capacitorFailedToCharge': 29, 'redundantLowBattery': 14, 'snapshotInProgress': 13, 'lowBattery': 4, 'badMirrorData': 8, 'batteryNotSupported': 24, 'postEccErrors': 19, 'invalid': 2, 'notEnoughBatteries': 22, 'cacheModuleNotSupported': 23, 'other': 1, 'fbcmChargerCircuitFailure': 32, 'capBasedRestoreFailed': 27, 'notConnected': 7, 'noCapacitorAttached': 25, 'redundantCacheFailure': 16, 'readErr': 9, 'expandInProgress': 12, 'writeErr': 10, 'configCmd': 11, 'capBasedModuleHWFailure': 28, 'disableCmd': 5, 'excessiveEccErrors': 17, 'incompatibleCacheModule': 31, 'adgEnablerMissing': 18, 'capacitorChargeLow': 21, 'redundantSizeMismatch': 15, 'capBasedBackupFailed': 26.

Cache Module Board Backup Power Status. This monitors the status of each backup power source on the board. The backup power source can only recharge when the system has power applied. The type of backup power source used is indicated by cpqDaAccelBackupPowerSource. The following values are valid: Other (1) Indicates that the instrument agent does not recognize backup power status. You may need to update your software. Ok (2) The backup power source is fully charged. Recharging (3) The array controller has one or more cache module backup power sources that are recharging. Cache module operations such as Battery/Flash Backed Write Cache, Expansion, Extension and Migration are temporarily suspended until the backup power source is fully charged. Cache module operations will automatically resume when charging is complete. Failed (4) The battery pack is below the sufficient voltage level and has not recharged in 36 hours. Your Cache Module board needs to be serviced. Degraded (5) The battery is still operating, however, one of the batteries in the pack has failed to recharge properly. Your Cache Module board should be serviced as soon as possible. NotPresent (6) A backup power source is not present on the cache module board. Some controllers do not have backup power sources. Capacitor Failed (7) The flash backed cache module capacitor is below the sufficient voltage level and has not recharged in 10 minutes. Your Cache Module board needs to be serviced. Enumeration: 'ok': 2, 'recharging': 3, 'failed': 4, 'other': 1, 'degraded': 5, 'capacitorFailed': 7, 'notPresent': 6.

Cache Module Board Read Errors. This shows the total number of read memory parity errors that were detected while reading from the Cache Module board. The mirrored copy of data on the board can be accessed to obtain correct data if a memory parity errors occurs. Memory parity errors occur when the system detects that information has not been transferred correctly. A parity bit is included for each byte of information stored in memory. When the microprocessor reads or writes data, the system counts the value of the bits in each byte. If a total does not match the system's expectations, a parity error has occurred. A bad memory chip, memory corruption, or lack of refresh may cause memory parity errors.

Cache Module Board Write Errors. This shows the total number of write memory parity errors that were detected while writing to the Cache Module board. Write parity errors occur when the system detects that information has not been transferred to the Cache Module board correctly. A parity bit is included for each byte of information stored in memory. When the microprocessor reads or writes data, the system counts the value of the bits in each byte. If the total does not match the system's expectations, a parity error has occurred.

The condition of the device. This value represents the overall condition of this cache module. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

Read Cache Memory. This shows the amount of memory allocated for the read cache in kilobytes. Because data is kept in duplicate (mirrored), the actual amount of usable memory is half the amount shown. Read cache is not available on IDA, IDA-2, IDA Expansion System, or SMART controllers. Entries for these controllers will return 0 for this value.

Cache Module Serial Number. The serial number of the Cache Module. This field will be a null (size 0) string if the cache module does not support serial number.

Total Cache Memory. This value is the total amount of cache module memory in kilobytes, including both battery-backed and non-battery-backed memory.

Read Cache Percent. This shows the percent of cache memory allocated for read ahead caching. If the data cannot be determined or is not applicable, the value is set to 4,294,967,295.

Write Cache Percent. This shows the percent of cache memory allocated for posted write caching. If the data cannot be determined or is not applicable, the value is set to 4,294,967,295.

Cache Module Failed Batteries. This lists the location of cache module failed batteries. Each octet present contains the position number of a failed battery. An octet string of length zero indicates that there are no failed batteries or that the controller does not have the ability to identify individual failed batteries.

Cache Module Board Backup Power Source. This describes the backup power source being used by the Cache Module board. The status can be: Other (1) Indicates that the instrument agent does not recognize the backup power source used by the Cache Module board. You may need to upgrade the instrument agent. Battery (2) Indicates that a battery is the backup power source for the Cache Module board. Capacitor (3) Indicates that a capacitor is the backup power source for the Cache Module board. Enumeration: 'battery': 2, 'other': 1, 'capacitor': 3.

Cache Module Board Current Temperature. This is the temperature of the cache module board in degrees Celsius. The field will contain -1 if the cache module board temperature cannot be calculated or if the controller does not support reporting cache module board temperature.

Cache Module Capacitor Current Temperature. This is the temperature of the Super-Cap in degrees Celsius. The field will contain -1 if the Super-Cap temperature cannot be calculated or if the controller does not support reporting Super-Cap temperature.

Cache Memory Data Width. This is the memory data width (in bits), for the attached cache module. The field will contain -1 if the memory data width cannot be calculated or if the controller does not support reporting memory data width.

Cache Memory Transfer Rate. This is the memory transfer rate in megatransfers per second (MT/s), for the attached cache module . The field will contain -1 if the memory transfer rate cannot be calculated or if the controller does not support reporting memory transfer rate.

Drive Array Managed Cable Table.

Drive Array Managed Cable Entry.

Managed Cable Index. This index identifies a controller and managed cable association. This index uniquely identifies a single managed cable connected to a controller.

Managed Cable Controller Index. This value maps the managed cables into their respective controllers. This value is a logical number whose meaning is OS dependent. The value has a direct mapping to the controller table index such that controller 'i' has managed cable controller index 'i'.

Managed Cable Host Connector. This is the port connector to which the managed cable is attached. If the host connector cannot be determined, the agent will return a NULL string.

Managed Cable Status. The following values are defined: Other (1) Indicates that the instrument agent can not determine the managed cable status. Ok (2) Indicates the cable is functioning properly. Non Fatal Fault (3) Indicates the cable has reported a non fatal fault. See cpqDaManagedCableFaultCode for more information. Fatal Fault (4) Indicates the cable has reported a fatal fault. See cpqDaManagedCableFaultCode for more information. Enumeration: 'fatalFault': 4, 'other': 1, 'ok': 2, 'nonFatalFault': 3.

Managed Cable Fault Code. The following values are defined: Other (1) Indicates that the instrument agent can not determine the managed cable fault code. None (2) Indicates that no cable fault codes have been reported. Link Fault (3) Indicates that the cable is reporting a non fatal link fault. No Communication With Cable's Management Interface (4) Indicates that Smart Array firmware could not communicate with the cable's management interface. Cannot Configure Cable (5) Indicates that Smart Array firmware could not configure the cable and has disabled it. Enumeration: 'none': 2, 'other': 1, 'linkFault': 3, 'noComWithCableMgmtInterface': 4, 'cannotConfigureCable': 5.

Managed Cable Vendor Revision. Indicates the vendor revision of the managed cable. If the managed cable does not support vendor revision, the instrument agent will return a NULL string.

Managed Cable Vendor Serial Number. Indicates the vendor serial number of the managed cable. If the managed cable does not support vendor serial number, the instrument agent will return a NULL string.

Managed Cable Vendor Part Number. Indicates the vendor part number of the managed cable. If the managed cable does not support vendor part number, the instrument agent will return a NULL string.

Managed Cable Length. Indicates the length of the managed cable in meters. This field will contain -1 if the cable length cannot be determined or if the managed cable does not support reporting cable length.

Drive Array Logical Drive Table. A table of logical drive entries.

Drive Array Logical Drive Entry. A logical drive entry.

Drive Array Logical Drive Controller Index. This maps the logical drives into their respective controllers. Controller index 'i' under the controller group owns the associated drives in the logical drive group which use that index.

Drive Array Logical Drive Index. This logical drive number keeps track of multiple instances of logical drives which are on the same controller. For each controller index value, the logical drive index starts at 1 and increments for each logical drive.

Logical Drive Fault Tolerance. This shows the fault tolerance mode of the logical drive. The following values are valid for the Logical Drive Fault Tolerance: None (2) Fault tolerance is not enabled. If a physical drive reports an error, the data cannot be recovered by the drive array controller. Mirroring - RAID 1/RAID 1+0 (3) For each physical drive, there is a second physical drive containing identical data. If a drive fails, the data can be retrieved from the mirror drive. Data Guard - RAID 4 (4) One of the physical drives is used as a data guard drive and contains the exclusive OR of the data on the remaining drives. If a failure is detected, the drive array controller rebuilds the data using the data guard information plus information from the other drives. Distributed Data Guard - RAID 5 (5) Distributed Data Guarding, sometimes referred to as RAID 5, is similar to Data Guarding, but instead of storing the parity information on one drive, the information is distributed across all of the drives. If a failure is detected, the drive array controller rebuilds the data using the data guard information from all the drives. Advanced Data Guarding - RAID 6 (7) Advanced Data Guarding (RAID ADG) is the fault tolerance method that provides the highest level of data protection. It 'stripes' data and parity across all the physical drives in the configuration to ensure the uninterrupted availability of uncorrupted data. This fault-tolerance method is similar to distributed data guard (RAID 5) in that parity data is distributed across all drives in the array, except in RAID ADG the capacity of multiple drives is used to store parity data. Assuming the capacity of 2 drives is used for parity data, this allows continued operation despite simultaneous failure of any 2 drives in the array, whereas RAID 4 and RAID 5 can only sustain failure of a single drive. RAID 50 (8) Distributed data guarding (RAID 5) with multiple parity groups. RAID 60 (9) Advanced data guarding (RAID 6) with multiple parity groups. RAID 1 ADM (10) - Advanced Data Mirroring - For each physical drive, there are two or more physical drives containing identical data. If a drive fails, the data can be retrieved from any of the mirrored drives. RAID 10 ADM (11) - Advanced Data Mirroring with Striping - For each physical drive, there are two or more physical drives containing identical data in addition to data being striped across multiple drives. If a drive fails, the data can be retrieved from any of the mirrored drives. Enumeration: 'none': 2, 'raid50': 8, 'mirroring': 3, 'raid10Adm': 11, 'distribDataGuard': 5, 'other': 1, 'raid60': 9, 'dataGuard': 4, 'advancedDataGuard': 7, 'raid1Adm': 10.

Logical Drive Status. The logical drive can be in one of the following states: Ok (2) Indicates that the logical drive is in normal operation mode. Failed (3) Indicates that more physical drives have failed than the fault tolerance mode of the logical drive can handle without data loss. Unconfigured (4) Indicates that the logical drive is not configured. Recovering (5) Indicates that the logical drive is using Interim Recovery Mode. In Interim Recovery Mode, at least one physical drive has failed, but the logical drive's fault tolerance mode lets the drive continue to operate with no data loss. Ready Rebuild (6) Indicates that the logical drive is ready for Automatic Data Recovery. The physical drive that failed has been replaced, but the logical drive is still operating in Interim Recovery Mode. Rebuilding (7) Indicates that the logical drive is currently doing Automatic Data Recovery. During Automatic Data Recovery, fault tolerance algorithms restore data to the replacement drive. Wrong Drive (8) Indicates that the wrong physical drive was replaced after a physical drive failure. Bad Connect (9) Indicates that a physical drive is not responding. Overheating (10) Indicates that the drive array enclosure that contains the logical drive is overheating. The drive array is still functioning, but should be shutdown. Shutdown (11) Indicates that the drive array enclosure that contains the logical drive has overheated. The logical drive is no longer functioning. Expanding (12) Indicates that the logical drive is currently undergoing a transformation (expansion, shrinkage or movement). During transformation, fault tolerance algorithms redistribute logical drive data according to the transformation operation selected. Not Available (13) Indicates that the logical drive is currently unavailable. If a logical drive is expanding and the new configuration frees additional disk space, this free space can be configured into another logical volume. If this is done, the new volume will be set to not available. Queued For Expansion (14) Indicates that the logical drive is ready for transformation (expansion, shrinkage or movement). The logical drive is in the queue for transformation. Multi-path Access Degraded (15) Indicates that previously all disk drives of this logical drive had more than one I/O path to the controller, but now one or few of them have only one I/O path. Erasing (16) Indicates that the logical drive is currently being erased. Predictive Spare Rebuild Ready (17) Indicates that the logical drive is ready to perform a predictive spare rebuild. The logical drive is in the queue for rebuild. Rapid Parity Initialization In Progress (18) Indicates that the logical drive is currently undergoing rapid parity initialization (RPI). The logical drive is unavailable to the operating system during RPI and will be made available once RPI has completed. Rapid Parity Initialization Pending (19) Indicates that the logical drive is currently pending rapid parity initialization and will be unavailable. No Access - Encrypted with No Controller Key (20) Indicates that the logical drive is currently encrypted and cannot be accessed because the array controller has not yet received the encryption key from iLO nor was it found in the controller's CSP NVRAM. Unencrypted to Encrypted Transformation in Progress (21) Indicates that the logical drive is currently being transformed from unencrypted to encrypted and the volume is online. Data will be written unencrypted if the write is directed to an LBA range on the logical drive that has not yet been migrated. New Logical Drive Key Rekey in Progress (22) Indicates that the logical drive is currently encrypted and all data is currently being rekeyed with a new logical drive key using the background capacity expansion transformation task. The logical drive is online. No Access - Encrypted with Controller Encryption Not Enabled (23) Indicates that the logical drive is currently encrypted and cannot be accessed because the array controller does not have encryption enabled. Unencrypted To Encrypted Transformation Not Started (24) Indicates that the logical drive has received a request to transform from unencrypted to encrypted but this process has not yet started. The unencrypted logical drive is currently online. New Logical Drive Key Rekey Request Received (25) Indicates that the logical drive is encrypted and has received a request to rekey all data with a new logical drive encryption key. The logical drive is online. Enumeration: 'erasing': 16, 'expanding': 12, 'overheating': 10, 'noAccessEncryptedCntlrEncryptnNotEnbld': 23, 'shutdown': 11, 'noAccessEncryptedNoCntlrKey': 20, 'readyForRebuild': 6, 'rapidParityInitInProgress': 18, 'multipathAccessDegraded': 15, 'newLogDrvKeyRekeyInProgress': 22, 'failed': 3, 'other': 1, 'rebuilding': 7, 'rapidParityInitPending': 19, 'badConnect': 9, 'notAvailable': 13, 'unencryptedToEncryptedNotStarted': 24, 'ok': 2, 'recovering': 5, 'wrongDrive': 8, 'predictiveSpareRebuildReady': 17, 'unconfigured': 4, 'unencryptedToEncryptedInProgress': 21, 'queuedForExpansion': 14, 'newLogDrvKeyRekeyRequestReceived': 25.

Array Controller Logical Drive Auto-Reliability Delay. This value indicates how many seconds the logical drive will wait with no requests before beginning Auto-Reliability monitoring. For example, the default value is five, so the logical drive will begin Auto-Reliability monitoring if it receives no requests for five seconds. If the value is zero, the logical drive will not perform Auto-Reliability monitoring. Auto-Reliability only operates if the logical drive is configured in one of the fault tolerance modes. If the logical drive receives a request while performing Auto-Reliability monitoring, the drive will stop monitoring to process the request. Once it has satisfied all incoming requests, the drive will wait for the Auto-Reliability delay to expire before returning to Auto-Reliability monitoring. Auto-Reliability monitoring is a process to insure the highest level of data reliability. In this process each disk is scanned to verify that all of the sectors in the drive array are readable. If the Auto-Reliability monitoring process detects any bad sectors on the drives, it automatically remaps these bad sectors where possible.

Logical Drive Rebuild Blocks Remaining. After a failed physical drive has been replaced, the physical drive must have its data rebuilt. This value shows how many blocks of data still need to be rebuilt. When the value reaches zero, the rebuilding process is complete. The drive array continues to operate in interim recovery mode while a drive is rebuilding. When a logical volume is Expanding, the drive must redistribute the logical volume data across the physical drives. This value shows how many blocks of data still need to be redistributed. When the value reaches zero, the expand process is complete. The drive array continues to operate normally while the drive is expanding. This value is only valid if the Logical Drive Status is rebuilding (7) or expanding (12).

Logical Drive Has Cache Module Board. This indicates whether the logical drive has a Cache Module board configured and enabled. The following values are valid: Other (1) Indicates that the instrument agent does not recognize the Cache Module board. You may need to upgrade your software. Unavailable (2) Indicates that there is no Cache Module board configured for this logical drive. Enabled (3) Indicates that the Cache Module board is configured and enabled for this logical drive. Disabled (4) Indicates that the Cache Module board is configured but not enabled for this logical drive. Enumeration: 'disabled': 4, 'other': 1, 'enabled': 3, 'unavailable': 2.

Drive Array Logical Drive Available Spares. This indicates if this logical drive has one or more spares designated for it that are not currently in use by another drive. Each octet present will be a physical drive ID that is an available spare for this logical drive. These are the same ID's which can be used as indices into the physical drive table. An octet string of length zero indicates that there are no available spares for this logical drive. For array controllers that support a larger number of drives, the Drive Array Logical Drive Available Spare Extended Attachment Table should be used.

Logical Drive Size. This is the size of the logical drive in megabytes. This value is calculated using the value 1,048,576 (2^20) as a megabyte. Drive manufacturers sometimes use the number 1,000,000 as a megabyte when giving drive capacities so this value may differ from the advertised size of a drive.

Drive Array Logical Drive Physical Drive IDs. This lists the physical drive IDs which are associated with this logical drive. These are the same IDs which can be used as indices into the physical drive table. Each byte of the string is an index. For array controllers that support a larger number of drives, the Drive Array Logical Drive Extended Physical Drive Attachment Table should be used to determine drive associations.

The Logical Drive condition. This value represents the overall condition of this logical drive and any associated physical drives. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

Logical Drive Percent Rebuild. After a failed physical drive has been replaced, the physical drive must have its data rebuilt. This value is the percent complete of the rebuild. When the value reaches 100, the rebuilding process is complete. The drive array continues to operate in interim recovery mode while a drive is rebuilding. When a logical volume is Expanding, the drive must redistribute the logical volume data across the physical drives. This value shows how many blocks of data still need to be redistributed. When the value reaches one hundred (100), the expand process is complete. The array continues to operate normally while the drive is expanding. When a logical drive's encryption state is transforming from unencrypted to encrypted or when the logical drive is being rekeyed with a new key, this value is the percent complete of the operation. When the value reaches 100, the transformation or rekey process is complete. This value is only valid if the logical drive status is rebuilding (7), expanding (12), unencryptedToEncryptedInProgress(22) and newLogDrvKeyRekeyInProgress(23). If the value cannot be determined or a rebuild is not active, the value is set to 4,294,967,295.

Logical Drive Stripe Size. This is the size of a logical drive stripe in kilobytes.

Logical Drive OS Name. The OS name for this array logical drive. This field will be a null (size 0) string if the agent does not support OS name.

Logical Drive Physical Drive Blink Time Count. The logical drive blink time variable allows the drive tray LEDs of all physical drives in a logical drive to blink. This value indicates the amount of time, in tenths of a second, that the physical drive LEDs will continue to blink. A value of zero indicates the drive LEDs are not blinking. If the value cannot be determined or no drive in this logical drive is in a hot plug tray, 4,294,967,295 is returned. To blink the drive LEDs on all physical drives in this logical drive (including any configured spare drives), set this value to the time to blink in tenths of seconds. To stop the drive LEDs from blinking, set this value to 0.

Logical Drive Spare To Replacement Drive Map. This data structure contains the spare to physical drive replacement map. The format is: octet contents ===== ======== 1 Spare drive physical drive index 2 Replaced drive physical drive index These 2 octets are repeated for each replaced drive. For n replaced drives, the string is 2 * n octets long. An octet string of length zero indicates that there are no replaced drives currently in use. For array controllers that support larger number of drives, the Drive Array Logical Drive Spare Replacement Extended Attachment Table should be used.

Logical Drive Physical Drive Rebuilding Index. This is the physical drive index of the physical drive that is currently rebuilding. If the value cannot be determined or is not applicable, the value is set to -1.

Logical Drive Multi-path Access. This indicates whether all the physical disks including spares of this logical drive have been configured to have and currently still have more than one I/O path to the controller. The following values are valid: Other (1) Indicates that the instrument agent can not determine if this logical drive has multi-path access. Not Supported (2) Indicates that multi-path access to this logical drive is not supported. Not Configured (3) Indicates that this logical drive is not configured to have multi-path access. Path Redundant (4) Indicates that all disks of this logical drive currently have more than one I/O path to the controller. No Redundant Path (5) Indicates that all disks of this logical drive previously had more than one I/O path to the controller, but now one or few of them have no redundant I/O path. Enumeration: 'notSupported': 2, 'pathRedundant': 4, 'other': 1, 'noRedundantPath': 5, 'notConfigured': 3.

Logical Drive Number Of Parity Groups. Indicates the number of parity groups (i.e. RAID 4/5/6 subvolumes), that are being striped across.

Logical Drive Split Mirror Backup Logical Drive. Indicates if this logical drive is a backup logical drive belonging to a split mirror. The following values are defined: other(1) The instrument agent is unable to determine if this logical drive is a backup logical drive. You may need to upgrade the instrument agent. isNotBackupLogicalDrive(2) The logical drive is not a backup logical drive. isBackupLogicalDrive(3) The logical drive is a backup logical drive. Enumeration: 'other': 1, 'isNotBackupLogicalDrive': 2, 'isBackupLogicalDrive': 3.

Logical Drive Cache Volume Accelerator Association Type. Indicates the way in which this logical drive is associated with a cache volume accelerator group. The following values are defined: Other(1) The instrument agent is unable to determine if this logical drive is part of a cache volume accelerator group. Logical drive cache volume acceleration may not be enabled on this controller or you may need to upgrade the instrument agent. Non Member (2) Indicates that this logical drive is not a member of a cache volume accelerator group. Logical Drive Member(3) This logical drive is using a cache volume. Cache Volume Member(4) This logical drive is being utilized as a cache volume. Enumeration: 'cacheVolumeMember': 4, 'nonMember': 2, 'other': 1, 'logicalDriveMember': 3.

Logical Drive Cache Volume Index. The logical drive index of the cache volume used by this logical drive. The value of this index is the same as the logical drive index used in the cache volume accelerator table. If the value cannot be determined or is not applicable, the value is set to -1.

Logical Drive Rapid Parity Initialization Percent Complete. When a fault tolerant logical volume is created, parity data for the volume must be initialized. This value is the percent complete of the rapid parity initialization (RPI) process. When the value reaches 100, the RPI process is complete and the logical drive is made available to the operating system. If the value cannot be determined or rapid parity initialization is not active, the value is set to 4,294,967,295.

Logical Drive SSD Smart Path Status. Indicates the logical drive SSD Smart Path status. An SSD Smart Path for a logical drive can be utilized only when both the Smart Array firmware and Smart Array controller driver support such a path. The following values are defined: Other (1) Indicates that the instrument agent can not determine the logical drive's SSD Smart Path status. Update Driver (2) Indicates that an updated Smart Array controller driver is needed in order for the SSD Smart Path to be supported for this logical drive. SSD Smart Path Disabled(3) Indicates that an SSD Smart Path for this logical drive is disabled. Check Smart Array controller documentation. SSD Smart Path Enabled(4) Indicates that an SSD Smart path for this logical drive is enabled. The Smart Array controller driver is able to use an SSD Smart Path for this logical drive. Enumeration: 'ssdSmartPathDisabled': 3, 'other': 1, 'ssdSmartPathEnabled': 4, 'updateDriver': 2.

Logical Drive Encryption Status. Indicates the logical drive encryption status. The following values are defined: Other (1) Indicates that the instrument agent can not determine the logical drive's encyption status. Encrypted (2) Indicates that data-at-rest encryption is enabled for this logical drive. Not Encrypted(3) Indicates that data-at-rest encryption is not enabled for this logical drive. Enumeration: 'encrypted': 2, 'other': 1, 'notEncrypted': 3.

Drive Array Logical Drive Physical Drive Extended Attachment Table. A table of logical drives and their associated physical drives.

Drive Array Logical Drive Extended Physical Drive Attachment Entry.

Drive Array Logical Drive Extended Attach Index. This index identifies a controller, logical drive and physical drive connection. This index uniquely identifies a connection for each attached hard drive.

Drive Array Logical Drive Controller Extended. This maps the logical drives into their respective controllers. This value is a logical number whose meaning is OS dependent. The value has a direct mapping to the controller table index such that controller 'i' has logical drive controller extended table entry 'i'.

Drive Array Logical Drive Extended. This logical drive number keeps track of multiple instances of logical drives which are on the same controller. For each controller value, the logical drive value starts at 1 and increments for each logical drive.

Drive Array Logical Drive Physical Drive Extended. This value is used for selecting the physical drive number in the table entry. This number keeps track of multiple instances of physical drives which are on the same controller.

Drive Array Logical Drive Spare Replacement Extended Attachment Table. A table of logical drives, physical drives and their replacement drives. If spare drives are not used, this table will not be populated.

Drive Array Logical Drive Spare Replacement Extended Attachment Entry.

Drive Array Logical Drive Spare Replacment Extended Attach Index. This index uniquely identifies a controller, logical drive, physical drive and replacement drive connection.

Drive Array Logical Drive Spare Replacement Controller Extended. This value maps the spare replacement drives into their respective controllers. This value is a logical number whose meaning is OS dependent. The value has a direct mapping to the controller table index such that controller 'i' has spare replacement controller extended table entry 'i'..

Drive Array Logical Drive Spare Replace Logical Drive Extended. This logical drive number keeps track of multiple instances of logical drives which are on the same controller. For each controller value, the logical drive value starts at 1 and increments for each logical drive.

Drive Array Logical Drive Spare Replace Replaced Physical Drive Extended. This is the replaced drive physical drive number.

Drive Array Logical Drive Spare Replace Spare Physical Drive Extended. This is the replacement spare physical drive number.

Drive Array Logical Drive Available Spare Extended Attachment Table. A table of logical drives and their available spare drives. This table indicates when a logical drive has one or more spare drives designated for it. This table will not be populated when available spares are not being used.

Drive Array Logical Drive Available Spare Extended Attachment Entry.

Drive Array Logical Drive Available Spare Extended Attach Index. This index uniquely identifies a controller, logical drive and available spare drive connection.

Drive Array Logical Drive Available Spare Controller Extended. This value maps the available spare drives into their respective controllers This value is a logical number whose meaning is OS dependent. The value has a direct mapping to the controller table index such that controller 'i' has available spare controller extended table entry 'i'..

Drive Array Logical Drive Available Spare Logical Drive Extended. This logical drive number keeps track of multiple instances of logical drives which are on the same controller. For each controller value, the logical drive value starts at 1 and increments for each logical drive.

Drive Array Logical Drive Available Spare Available Spare Extended. This is the available spare drive number assigned to one or more logical drives.

Drive Array Logical Drive Cache Volume Accelerator Table. The cpqDaLogDrvCacheVolumeAccelTable table contains configuration and statistical information about cache volumes. This table will not be populated when logical drive cache volumes are not being used.

Drive Array Logical Drive Cache Volume Accelerator Entry. A cache volume entry.

Drive Array Logical Drive Cache Volume Accelerator Controller Index. This index maps the cache volume back to the controller to which it is attached. The value of this index is the same as the index used under in the controller table.

Drive Array Logical Drive Cache Volume Accelerator Logical Drive Index. The logical drive index for this cache volume. The value of this index is the same as the logical drive index used in the logical drive table.

Drive Array Logical Drive Cache Volume Accelerator Caching Algorithm. The caching algorithm currently in use for the cache volume. The following values are defined: Other(1) The instrument agent is unable to determine the caching algorithm for this cache volume. You may need to upgrade the instrument agent. Multi Segment(2) Multiple tiers to track cached and potentially cacheable data. The multi-segment cache takes into account frequency, spatial locality and temporal locality of data accesses. The replacement policy is conservative making the algorithm ideal for workloads that have a mixture of cacheable and non-cacheable data with hot spots that remain hot for some time. Single Segment (3) A single tier tracks cached data. The single-segment cache takes into account spatial and temporal locality of data accesses. The replacement policy is very aggressive resulting in the algorithm being ideal for workloads that have very few non-cacheable data accesses and hotspots that move frequently. Enumeration: 'singleSegment': 3, 'other': 1, 'multiSegment': 2.

Drive Array Logical Drive Cache Volume Accelerator Cache State. The current cache state of the cache volume. The following values are defined: Other(1) The instrument agent is unable to determine the cache state of this cache volume. You may need to upgrade the instrument agent. Ok (2) Indicates that the cache volume is in normal operation mode and is fully functional. Degraded (3) Indicates that this cache volume is currently degraded with limited functionality. Cache Volume Offline(4) Indicates that the cache volume member is currently offline. Logical Drive Offline(5) Indicates that the logical drive member is currently offline. Never Configured(6) Indicates that the cache volume was never configured. Flushing(7) Indicates that cache data is currently flushing from DDR cache. Configuring(8) Indicates that cache is currently configuring. Cache Configuration Failed(9) Indicates that cache configuration has failed. Enumeration: 'ok': 2, 'configuring': 8, 'logDriveOffline': 5, 'other': 1, 'flushing': 7, 'cacheConfigurationFailed': 9, 'neverConfigured': 6, 'degraded': 3, 'cacheVolOffline': 4.

Drive Array Logical Drive Cache Volume Accelerator Write Policy. The write policy that the cache volume has been configured to use. The following values are defined: Other(1) The instrument agent is unable to determine the write policy of this cache volume. You may need to upgrade the instrument agent. Read Only (2) Indicates that this cache volume is currently using a read only policy. Write Through(3) Indicates that this cache volume is currently using a write through policy. Write Back Safe(4) Indicates that this cache volume is currently using a write back safe policy. Writing is being executed to a cache volume that utilizes a redundant RAID level. If the cache volume's redundancy becomes degraded, the cache volume will utilize the write through write policy until redunancy is restored. Write Back Unsafe(5) Indicates that this cache volume is currently using a write back unsafe policy. Writing is being executed to a cache volume that is not utilizing a redundant RAID level. Write Through No Load(6) Indicates that this cache volume is currently using a write through no load policy. The cache volume will process write requests but will only write if the line is already loaded. Enumeration: 'writeThroughNoLoad': 6, 'writeBackUnsafe': 5, 'writeThrough': 3, 'readOnly': 2, 'other': 1, 'writeBackSafe': 4.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Hits (high). cpqDaLogDrvCacheVolAccelNoOfReadHitsH and cpqDaLogDrvCacheVolAccelNoOfReadHits together show the number of read cache hits for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Hits (low). cpqDaLogDrvCacheVolAccelNoOfReadHits and cpqDaLogDrvCacheVolAccelNoOfReadHitsH together show the number of read cache hits for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Do Load (high). cpqDaLogDrvCacheVolAccelNoOfReadMissDoLoadH and cpqDaLogDrvCacheVolAccelNoOfReadMissDoLoad together show the number of times a read cache request for this cache volume was missed and prompted a load of data from the primary storage to the drive cache. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Do Load (low). cpqDaLogDrvCacheVolAccelNoOfReadMissDoLoad and cpqDaLogDrvCacheVolAccelNoOfReadMissDoLoadH together show the number of times a read cache request for this cache volume was missed and prompted a load of data from the primary storage to the drive cache. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Loading (high). cpqDaLogDrvCacheVolAccelNoOfReadMissLoadingH and cpqDaLogDrvCacheVolAccelNoOfReadMissLoading together show the number of times a read cache request for this cache volume was not serviced right away because the data was loading. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Loading (low). cpqDaLogDrvCacheVolAccelNoOfReadMissLoading and cpqDaLogDrvCacheVolAccelNoOfReadMissLoadingH together show the number of times a read cache request for this cache volume was not serviced right away because the data was loading. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Skip (high). cpqDaLogDrvCacheVolAccelNoOfReadMissSkipH and cpqDaLogDrvCacheVolAccelNoOfReadMissSkip together show the number of times a read cache request for this cache volume was serviced by primary storage and not the cache volume, exluding those that triggered loads or where a load was already taking place. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Skip (low). cpqDaLogDrvCacheVolAccelNoOfReadMissSkip and cpqDaLogDrvCacheVolAccelNoOfReadMissSkipH together show the number of times a read cache request for this cache volume was serviced by primary storage and not the cache volume, exluding those that triggered loads or where a load was already taking place. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Read Cache Hit Rate. The rate (percentage) that the read cache for this cache volume is being utilized. If the value cannot be determined or read cache hit rate is not supported for this cache volume, it is set to 4,294,967,295.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Hits (high). cpqDaLogDrvCacheVolAccelNoOfWriteHitsH and cpqDaLogDrvCacheVolAccelNoOfWriteHits together show the number of write cache hits for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Hits (low). cpqDaLogDrvCacheVolAccelNoOfWriteHits and cpqDaLogDrvCacheVolAccelNoOfWriteHitsH together show the number of write cache hits for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Do Load (high). cpqDaLogDrvCacheVolAccelNoOfWriteMissDoLoadH and cpqDaLogDrvCacheVolAccelNoOfWriteMissDoLoad show the number of times a write cache request for this cache volume was missed and prompted a load of data from the primary storage to the drive cache. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Do Load (low). cpqDaLogDrvCacheVolAccelNoOfWriteMissDoLoad and cpqDaLogDrvCacheVolAccelNoOfWriteMissDoLoadH show the number of times a write cache request for this cache volume was missed and prompted a load of data from the primary storage to the drive cache. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Loading (high). cpqDaLogDrvCacheVolAccelNoOfWriteMissLoadingH and cpqDaLogDrvCacheVolAccelNoOfWriteMissLoading show the number of times a write cache request for this cache volume was not serviced right away because the data was loading. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Loading (low). cpqDaLogDrvCacheVolAccelNoOfWriteMissLoading and cpqDaLogDrvCacheVolAccelNoOfWriteMissLoadingH show the number of times a write cache request for this cache volume was not serviced right away because the data was loading. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Skip (high). cpqDaLogDrvCacheVolAccelNoOfWriteMissSkipH and cpqDaLogDrvCacheVolAccelNoOfWriteMissSkip together show the number of times a write cache request for this cache volume was serviced by primary storage and not the cache volume, exluding those that triggered loads or where a load was already taking place. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Skip (low). cpqDaLogDrvCacheVolAccelNoOfWriteMissSkip and cpqDaLogDrvCacheVolAccelNoOfWriteMissSkipH together show the number of times a write cache request for this cache volume was serviced by primary storage and not the cache volume, exluding those that triggered loads or where a load was already taking place. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Write Cache Hit Rate. The rate (percentage) that the write cache for this cache volume is being utilized. If the value cannot be determined or write cache hit rate is not supported for this cache volume, it is set to 4,294,967,295.

Drive Array Logical Drive Cache Volume Accelerator Load Failures. The number of times data failed to load onto this cache volume due to an error. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Cache Line Size. cpqDaLogDrvCacheVolAccelCacheLineSize is the cache line size in number of blocks. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Locked (high). cpqDaLogDrvCacheVolAccelNoOfReadMissLockedH and cpqDaLogDrvCacheVolAccelNoOfReadMissLocked together show the number of times a read cache request for this cache volume was missed due to the primary LUN being written to. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Locked (low). cpqDaLogDrvCacheVolAccelNoOfReadMissLocked and cpqDaLogDrvCacheVolAccelNoOfReadMissLockedH together show the number of times a read cache request for this cache volume was missed due to the primary LUN being written to. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Locked (high). cpqDaLogDrvCacheVolAccelNoOfWriteMissLockedH and cpqDaLogDrvCacheVolAccelNoOfWriteMissLocked together show the number of times a write cache request for this cache volume was missed due to the primary LUN being written to. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Locked (low). cpqDaLogDrvCacheVolAccelNoOfWriteMissLocked and cpqDaLogDrvCacheVolAccelNoOfWriteMissLockedH together show the number of times a write cache request for this cache volume was missed due to the primary LUN being written to. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Total (high). cpqDaLogDrvCacheVolAccelNoOfReadMissTotalH and cpqDaLogDrvCacheVolAccelNoOfReadMissTotal together show the total number of read cache misses for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Read Cache Misses - Total (low). cpqDaLogDrvCacheVolAccelNoOfReadMissTotal and cpqDaLogDrvCacheVolAccelNoOfReadMissTotalH together show the total number of read cache misses for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Total (high). cpqDaLogDrvCacheVolAccelNoOfWriteMissTotalH and cpqDaLogDrvCacheVolAccelNoOfWriteMissTotal together show the total number of write cache misses for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Logical Drive Cache Volume Accelerator Number Of Write Cache Misses - Total (low). cpqDaLogDrvCacheVolAccelNoOfReadMissTotal and cpqDaLogDrvCacheVolAccelNoOfReadMissTotalH together show the total number of write cache misses for this cache volume. If the value cannot be determined or is not applicable, it is set to -1.

Drive Array Spare Table. A table of spare entries.

Drive Array Spare Entry. An entry in the spare table.

Drive Array Spare Controller Index. This index maps the spare drive back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Spare Physical Drive Index. This index maps the spare to the physical drive it represents. The value of this index is the same as the one used with the physical drive table.

Spare Status. This shows the status of the on-line spare drive. The following values are valid for the spare status: Failed (3) The on-line spare has failed and is no longer available for use. Inactive (4) The monitored system has an on-line spare configured, but is not currently in use. Building (5) A physical drive has failed. Automatic Data Recovery is in progress to recover data to the on-line spare. Active (6) A physical drive has failed. Automatic Data Recovery is complete. The system is using the on-line spare as a replacement for the failed drive. Enumeration: 'building': 5, 'invalid': 2, 'failed': 3, 'inactive': 4, 'active': 6, 'other': 1.

Spare Replaced Drive. If the spare status is active(6) or building(5), then this has the physical drive number of the replaced drive. Otherwise a value of -1 will be returned.

Drive Array Spare Number Of Rebuild Blocks Left. If the spare status is building(5), then this is the number of blocks left to rebuild before completion. The data contained on the failed physical drive must be reconstructed from the fault tolerance data and copied to the spare so that the spare can function in place of the failed drive. When the number reaches zero (0), the building process is complete and the spare has replaced the physical drive.

The Spare Drive condition. This value represents the overall condition of this spare drive and any associated physical drives. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

Spare Drive SCSI Bus Number. The bus number indicates to which SCSI bus this spare drive is attached. The first instance is one and increments for each SCSI bus on a controller. A value of -1 will be returned if the spare drive is attached to a controller that does not support multiple SCSI busses. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Spare Drive Bay Location. This value matches the bay location where the physical drive has been installed. For a SCSI drive, this is the SCSI ID of the drive.

Spare Replaced Drive Bus Number. If the spare status is active(6) or building(5), then this has the physical drive bus number of the replaced drive. If the value cannot be determined or is not applicable, the value is set to -1.

Spare Replaced Drive Bay. If the spare status is active(6) or building(5), then this has the physical drive bay number of the replaced drive. If the value cannot be determined or is not applicable, the value is set to -1.

Drive Array Spare Percent Rebuild. If the spare status is building(5), then this is percent complete of of the rebuild. The data contained on the failed physical drive must be reconstructed from the fault tolerance data and copied to the spare so that the spare can function in place of the failed drive. When the number reaches one hundred (100), the building process is complete and the spare has replaced the physical drive. If the value cannot be determined or a rebuild is not active, the value is set to 4,294,967,295.

Spare Drive Location String. This string describes the location of the drive in relation to the controller. If the location string cannot be determined, the agent will return a NULL string.

Drive Array Physical Drive Table. A table of physical drive entries.

Drive Array Physical Drive Entry. A physical drive entry.

Drive Array Physical Drive Controller Index. This index maps the physical drive back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Physical Drive Index. This index is used for selecting the physical drive table entry. This number, along with the cpqDaPhyDrvCntlrIndex uniquely identify a specific physical drive.

Physical Drive Model. This is a text description of the physical drive. The text that appears depends upon who manufactured the drive and the drive type. If a drive fails, note the model to identify the type of drive necessary for replacement. If a model number is not present, you may not have properly initialized the drive array to which the physical drive is attached for monitoring.

Physical Drive Firmware Revision. This shows the physical drive revision number. If the firmware revision is not present, you have not properly initialized the drive array.

Physical Drive Bay Location. This value matches the bay location where the physical drive has been installed. For a SCSI drive, this is the SCSI ID of the drive. For a SAS or SATA drive, this is the bay number on the enclosure.

Physical Drive Status. This shows the status of the physical drive. The following values are valid for the physical drive status: Other (1) Indicates that the instrument agent does not recognize the drive. You may need to upgrade your instrument agent and/or driver software. Ok (2) Indicates the drive is functioning properly. Failed (3) Indicates that the drive is no longer operating and should be replaced. Predictive Failure(4) Indicates that the drive has a predictive failure error and should be replaced. Erasing(5) Indicates that the drive is being erased. Erase Done(6) Indicates that the drive has been erased and is now in an offline state. Erase Queued(7) Indicates that an erase operation is currently queued for the drive. SSD Wear Out(8) Indicates that a solid state drive is approaching the maximum usage limit for writes (wear out) and should be replaced as soon as possible. Not Authenticated(9) Indicates the physical drive could not be authenticated as a genuine HP hard drive. The array controller will no longer control the drive LEDs. Please replace the hard drive with a genuine HP hard drive. Enumeration: 'erasing': 5, 'ok': 2, 'eraseDone': 6, 'failed': 3, 'other': 1, 'notAuthenticated': 9, 'predictiveFailure': 4, 'eraseQueued': 7, 'ssdWearOut': 8.

This shows the number of spare sectors available for remapping at the time the physical drive was shipped. The physical drive will use these spare sectors for remapping bad sectors that exist on the drive. Not all drives support factory reallocation.

Physical Drive Used Reallocated Sectors. This shows the number of sectors of the reallocation area that have been used by the physical drive. To see how many sectors were originally available for use in the reallocation area, refer to the factory reallocation information if it exists. Not all drives support factory reallocation. Because of the nature of magnetic disks, certain sectors on a drive may have media defects. The reallocation area is part of the disk drive that the drive manufacturer sets aside to compensate for these defects. The drive array controller writes information addressed from these unusable sectors to available sectors in the reallocation area. If too many sectors have been reallocated, there may be a problem with the drive. If you suspect a problem, schedule server down time to run diagnostics to verify that a problem exists.

Reference Time in hours. This shows the total number of hours that a physical drive has been in operation since the drive was stamped. The drive will have either been stamped when it left the factory or when you ran diagnostics on your new drive. You can use the reference time to calculate rates for other physical drive events.

Sectors Read (high). The phyDrvHReads and the phyDrvReads together shows the total number of sectors read from the physical disk drive during the reference time (phyDrvRefHours). The actual number of sectors read equals the phyDrvHReads times 2^32 plus the phyDrvReads. This information may be useful for determining rates. For instance, if you wanted to calculate the average number of reads per hour of operation, divide this number by the reference hours.

Sectors Read (low). The phyDrvHReads and the phyDrvReads together shows the total number of sectors read from the physical disk drive during the reference time (phyDrvRefHours). The actual number of sectors read equals the phyDrvHReads times 2^32 plus the phyDrvReads. This information may be useful for determining rates. For instance, if you wanted to calculate the average number of reads per hour of operation, divide this number by the reference hours.

Sectors Written (high). The phyDrvHWrites and the phyDrvWrites together shows the total number of sectors written to the physical disk drive during the reference hours (phyDrvRefHours). The actual number of sectors written equals the phyDrvHWrites times 2^32 plus the phyDrvWrites. This information may be useful for determining rates. For instance, if you wanted to calculate the average number of writes per hour of operation, divide this number by the reference hours.

Sectors Written (low). The phyDrvHWrites and the phyDrvWrites together shows the total number of sectors written to the physical disk drive during the reference hours (phyDrvRefHours). The actual number of sectors written equals the phyDrvHWrites times 2^32 plus the phyDrvWrites. This information may be useful for determining rates. For instance, if you wanted to calculate the average number of writes per hour of operation, divide this number by the reference hours.

Total Seeks (high). The phyDrvHSeeks and the phyDrvSeeks together shows the total number of seek operations performed by the physical disk drive during the reference hours (phyDrvRefHours). The actual number of seeks equals the phyDrvHSeeks times 2^32 plus the phyDrvWriteSeeks.

Total Seeks (low). The phyDrvHSeeks and the phyDrvSeeks together shows the total number of seek operations performed by the physical disk drive during the reference hours (phyDrvRefHours). The actual number of seeks equals the phyDrvHSeeks times 2^32 plus the phyDrvWriteSeeks.

Hard Read Errors. This shows the number of read errors that have occurred on a drive that could not be recovered by a physical drive's Error Correction Code (ECC) algorithm or through retries during the reference time (phyDrvRefTime). Over time, a disk drive may produce these errors. If you receive these errors, a problem may exist with your drive. The value increases every time the physical drive detects another error. The severity of these errors depends on whether the monitored system is running in a fault tolerant mode. With fault tolerance, the controller can remap data to eliminate the problems caused by these errors. In either case, if you see an increase in these errors, schedule server down time to run diagnostics to verify that a problem exists.

Recovered Read Errors. This shows the number of read errors corrected through physical drive retries during the reference time (phyDrvRefTime). Over time, all disk drives produce these errors. If you notice a rapid increase in the value for Recovered Read Errors (or Hard Read Errors), a problem may exist with the drive. The value increases every time the physical drive detects and corrects another error. Expect more Recovered Read Errors than Hard Read Errors. If you suspect that a problem may exist with the drive, schedule server down time to run diagnostics.

Hard Write Errors. This shows the number of write errors that could not be recovered by a physical drive during the reference time (phyDrvRefTime). Over time a disk drive may detect these errors. If you notice an increase in the value shown for Hard Write Errors or Recovered Write Errors, a problem may exist with the drive. The value increases every time the physical drive detects another error. On average, these errors should occur less frequently than read errors. If you see an increase in these errors, schedule server down time to run diagnostics to verify that a problem exists.

Recovered Write Errors. This shows the number of write errors corrected through physical drive retries or recovered by a physical drive during the reference time (phyDrvRefTime). Over time a disk drive may produce these errors. If you notice an increase in the value shown for Hard Write Errors or Recovered Write Errors, a problem may exist with the drive. The value increases every time the physical drive detects and corrects an error. Only an unusually rapid increase in these errors indicates a problem. On average, these errors should occur less frequently than hard read errors. If you suspect that a problem may exist with the drive, schedule server down time to run diagnostics.

Seek Errors (High). The phyDrvHSeekErrs and the phyDrvSeekErrs together shows the total number of times that the physical disk drive detected a seek error during the reference hours (phyDrvRefHours). The actual number of seek errors equals the phyDrvHSeekErrs times 2^32 plus the phyDrvWriteSeekErrs. Over time, a disk drive usually produces these errors. If you notice a rapid increase in the value shown for Seek Errors, this physical drive may be failing. The value increases every time the physical drive produces another error. Only an unusually rapid increase in these errors indicates a problem. If you suspect that a problem exists, schedule server down time to run diagnostics.

Seek Errors (low). The phyDrvHSeekErrs and the phyDrvSeekErrs together shows the total number of times that the physical disk drive detected a seek error during the reference hours (phyDrvRefHours). The actual number of seek errors equals the phyDrvHSeekErrs times 2^32 plus the phyDrvWriteSeekErrs. Over time, a disk drive usually produces these errors. If you notice a rapid increase in the value shown for Seek Errors, this physical drive may be failing. The value increases every time the physical drive produces another error. Only an unusually rapid increase in these errors indicates a problem. If you suspect that a problem exists, schedule server down time to run diagnostics.

Spin up Time in tenths of seconds. This is the time it takes for a physical drive to spin up to full speed. Disks require time to gain momentum and reach operating speed. As cars are tested to go from 0 mph to 60 mph in x number of seconds, drive manufacturers have preset expectations for the time it takes the drive to spin to full speed. Drives that do not meet these expectations may have problems. The value may be zero (0) under one of the following conditions: * If you are monitoring a physical drive that is part of the monitored system's internal drive array storage, and you use a warm boot to reset the monitored system. During a warm boot, the drives continue to spin. * If you are monitoring a physical drive in an ProLiant Storage System and you reset the monitored system but not the ProLiant Storage System.

Functional Test 1. This provides information about a series of tests that indicate how well a physical drive works. These tests compare the way the physical drive currently operates when performing various tasks with the way it worked when it was new. A percent value is displayed that represents how the drive works currently when compared to how the drive worked when new. New drives operate at the 100 percent level. By default, if the current value is less than or equal to 80 percent, a problem may exist. If you suspect a problem, schedule server down time to run diagnostics to verify that a problem exists. If the value cannot be determined, it is set to 4,294,967,295.

Functional Test 2. This provides information about a series of tests that indicate how well a physical drive works. These tests compare the way the physical drive currently operates when performing various tasks with the way it worked when it was new. A percent value is displayed that represents how the drive works currently when compared to how the drive worked when new. New drives operate at the 100 percent level. By default, if the current value is less than or equal to 80 percent, a problem may exist. If you suspect a problem, schedule server down time to run diagnostics to verify that a problem exists. If the value cannot be determined, it is set to 4,294,967,295.

Functional Test 3. This provides information about a series of tests that indicate how well a physical drive works. These tests compare the way the physical drive currently operates when performing various tasks with the way it worked when it was new. A percent value is displayed that represents how the drive works currently when compared to how the drive worked when new. New drives operate at the 100 percent level. By default, if the current value is less than or equal to 80 percent, a problem may exist. If you suspect a problem, schedule server down time to run diagnostics to verify that a problem exists. If the value cannot be determined, it is set to 4,294,967,295.

DRQ Timeouts. The number of times that a physical drive continued to request data, but did not get a command completion during the reference time (phyDrvRefTime). This value increases every time a DRQ timeout occurs for the physical drive. A defective drive or cable may cause DRQ timeouts to occur. If you see an increase in these errors, complete the following steps for the monitored system: 1. Check the cables connecting the drive to ensure that they are intact. 2. If the cables are properly connected, schedule server down time to run diagnostics to verify that a problem exists. If the value is not supported, it is set to 4,294,967,295.

Other Timeouts. The number of times that a physical drive did not respond with an interrupt within a controller-defined period of time after a command had been issued during the reference time (phyDrvRefTime). This does not include DRQ timeouts. If you suspect a problem, complete the following steps for the monitored system: 1. Check the cables connecting the drive to ensure that they are intact. 2. If the cables are properly connected, schedule server down time to run diagnostics to verify that a problem exists.

Spin up Retries. The number of times that a physical drive had to retry to spin up before successfully achieving operating speed during the reference time (phyDrvRefTime). This value represents the spin-up retries that occurred since the last time you turned on the monitored system. If you suspect a problem, schedule server down time to run diagnostics verify that a problem exists.

Recovery Failed (Bad) Read Error. The number of times a read error occurred while performing Automatic Data Recovery from this physical drive to another drive during the reference time (phyDrvRefTime). If a read error occurs, Automatic Data Recovery stops. These errors indicate that the physical drive has failed. If you suspect a problem, schedule server down time to run diagnostics to verify that a problem exists.

Recovery Failed (Bad) Write Error. The number of times a write error occurred while performing Automatic Data Recovery from another drive to this physical drive during the reference time (phyDrvRefTime). If a write error occurs, Automatic Data Recovery stops. These errors indicate that the physical drive has failed. If you suspect a problem, schedule server down time to run diagnostics to verify that a problem exists.

Format Error. The number of times a format operation failed when the controller attempted to remap a bad sector during the reference time (phyDrvRefTime). Zero indicates that no format errors have occurred. The value increases each time a format error occurs. A failed format operation may cause the controller to mark a drive failed. If you suspect a problem, schedule server down time to run diagnostics verify a problem exists.

Power On Self Test (Post) Error. The number of times that a physical drive failed its self test during the reference time (phyDrvRefTime). The physical drive does a self test each time power is applied to the system. If the value is not supported, it is set to 4,294,967,295.

Drive Not Ready Errors. The number of times the physical drive failed after the spin up command was issued during the reference time (phyDrvRefTime). When the spin up command was issued, the drive failed to reach its ready state. If the current value is zero, the drive has not failed. If the current value is greater than zero, at least one failure occurred. This error could be caused because the physical drive has failed to spin. If you suspect a problem: 1. Check the cables connecting the drive to ensure that they are intact. 2. If the cables are properly connected, schedule server down time to run diagnostics to verify that a problem exists.

Physical Drive Reallocation Aborts. The number of times the physical drive has failed due to an error that occurred when the controller was trying to reallocate a bad sector during the reference time (phyDrvRefTime). Zero (0) indicates that no Reallocation Abort errors have occurred. The value increases each time a Reallocation Abort error occurs. Because of the nature of magnetic disks, certain sectors on a drive may have media defects. The reallocation area is part of the disk drive that is set aside to compensate for these defects. The array controller writes information addressed from unusable sectors to available sectors in the reallocation area. If you suspect a problem, schedule server down time to run diagnostics verify a problem exists.

Physical Drive Factory Threshold Passed (Exceeded). When the drive is shipped, certain thresholds have been set to monitor performance of the drives. For example, a threshold might be set for Spin up Time. If the time that it takes the drive to spin up exceeds the factory threshold, there may be a problem with one of the drives. If you suspect a problem, schedule server down time to run diagnostics. Note: These thresholds may be under warranty under certain conditions. Enumeration: 'true': 2, 'false': 1.

Physical Drive Has Monitor Information. All of the physical disk table fields except for the physical disk status (phyDrvStatus) and the bay location (phyDrvBayLocation) are invalid unless this field has a value of true(2). Enumeration: 'true': 2, 'false': 1.

The condition of the device. This value represents the overall condition of this physical drive. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2.

Physical Drive Hot Plug Count. This value indicates the number of times this physical drive was hot-plugged (removed) from a ProLiant Storage System. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Physical Drive Media Failure Count. This value indicates the number of times this physical drive was failed due to unrecoverable media errors. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Physical Drive Hardware Error Count. This value indicates the number of times this physical drive returned a bad hardware status. The drive may be failed if retries do not work. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Physical Drive Aborted Command Failures. This value indicates the number of times this physical drive was failed due to aborted commands that could not be retried successfully. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Physical Drive Spin-Up Failure Count. This value indicates the number of times this physical drive was failed due to a failure of a spin-up command. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Physical Drive Bad Target Count. This value indicates the number of times this physical drive performed some action that did not conform to the SCSI-2 bus protocol. These actions will cause the SCSI bus to be reset. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Drive Physical Location. This is the physical location of where the drive is located. The following values are defined: other(1) The location of the drive is not known. internal(2) The drive is located inside of the computer system box. external(3) The drive is located outside of the computer system box. proLiant(4) The drive is located outside of the computer system box in a ProLiant Storage System. Enumeration: 'proLiant': 4, 'other': 1, 'internal': 2, 'external': 3.

Physical Drive Size in MB. This is the size of the physical drive in megabytes. This value is calculated using the value 1,048,576 (2^20) as a megabyte. Drive manufacturers sometimes use the number 1,000,000 as a megabyte when giving drive capacities so this value may differ from the advertised size of a drive. This field is only applicable for controllers which support SCSI drives, and therefore is not supported by the IDA or IDA-2 controllers. The field will contain 0xFFFFFFFF if the drive capacity cannot be calculated or if the controller does not support SCSI drives.

Physical Drive Bus Fault Count. This value indicates the number of times that a bus fault was detected for the drive by the controller. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Physical Drive IRQ Deglitch Count. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Physical Drive Hot Plug Support Status. The following values are defined: other(1) The Insight Agent is unable to determine if this drive supports hot plug replacement. hotPlug(2) The drive supports hot plug replacement. nonhotPlug(3) The drive does not support hot plug replacement. Enumeration: 'other': 1, 'nonHotPlug': 3, 'hotPlug': 2.

Physical Drive Placement. The following values are defined: other(1) The agent is unable to determine if the drive is internal or external to the system chassis. internal(2) The drive is located in the system chassis. external(3) The drive is located outside the system chassis in an expansion box. Enumeration: 'other': 1, 'internal': 2, 'external': 3.

Physical Drive SCSI Bus Number. The bus number indicates to which SCSI bus this physical drive is attached. The first instance is one and increments for each SCSI bus on a controller. A value of -1 will be returned if the physical drive is attached to a controller that does not support multiple SCSI busses. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers. For SAS and SATA drives, the bus number corresponds to the enclosure where the drive resides.

Physical Drive Serial Number. This is the serial number assigned to the physical drive. This value is based upon the serial number as returned by the SCSI inquiry command but may have been modified due to space limitations. This can be used for identification purposes.

Drive Array Physical Drive Predictive Failure Monitoring. The following values are defined: other(1) The agent is unable to determine if the drive supports predictive failure monitoring. notAvailable(2) This drive does not support predictive failure monitoring. available(3) This drive supports predictive failure monitoring. Enumeration: 'notAvailable': 2, 'available': 3, 'other': 1.

Drive Array Physical Drive Current Width. The following values are defined: other(1) The agent is unable to determine the current negotiated data transfer width for this drive. narrow(2) The negotiated data transfer width for this drive is narrow (8 data bits). wide16(3) The negotiated data transfer width for this drive is wide (16 data bits). Enumeration: 'wide16': 3, 'other': 1, 'narrow': 2.

Drive Array Physical Drive Current Data Transfer Speed. The following values are defined: other(1) The agent is unable to determine the current negotiated data transfer speed for this drive. asynchronous(2) The negotiated data transfer speed for this drive is asynchronous. fast(3) The negotiated data transfer speed for this drive is 10 million transfers per second). ultra(4) The negotiated data transfer speed for this drive is 20 million transfers per second. ultra2(5) The negotiated data transfer speed for this drive is 40 million transfers per second. ultra3(6) The negotiated data transfer speed for this drive is 80 million transfers per second. ultra320(7) The negotiated data transfer speed for this drive is 160 million transfers per second. Enumeration: 'ultra320': 7, 'ultra2': 5, 'ultra3': 6, 'other': 1, 'asynchronous': 2, 'fast': 3, 'ultra': 4.

Drive Array Physical Drive Failure Code. This value is the drive failure reason code returned by the array firmware. It is valid only when the drive is failed. If the drive is not failed, 0 is returned.

Physical Drive Blink Time Count. This value indicates the amount of time, in tenths of a second, that the physical drive LEDs will continue to blink. A value of zero indicates the drive LEDs are not blinking. If the value cannot be determined or the drive is not in a hot plug tray, 4,294,967,295 is returned. To blink the drive LEDs, set this value to the time to blink in tenths of seconds. To stop the drive LEDs from blinking, set this value to 0.

Physical Drive S.M.A.R.T Status. The following values are defined: other(1) The agent is unable to determine if the status of S.M.A.R.T predictive failure monitoring for this drive. ok(2) Indicates the drive is functioning properly. replaceDrive(3) Indicates that the drive has a S.M.A.R.T predictive failure error and should be replaced. replaceDriveSSDWearOut(4) Indicates that the solid state drive has a S.M.A.R.T wear error and is approaching the maximum usage limit for writes (wear out). The solid state drive should be replaced as soon as possible. Enumeration: 'replaceDrive': 3, 'other': 1, 'ok': 2, 'replaceDriveSSDWearOut': 4.

Physical Drive Configuration Status. The following values are defined: other(1) The agent is unable to determine the configuration status of this physical drive. configured(2) Indicates the drive is configured to be part of a logical drive as either a member drive or a spare drive. notConfigured(3) Indicates the drive is not configured to be part of a logical drive as either a member drive or a spare drive. Enumeration: 'configured': 2, 'other': 1, 'notConfigured': 3.

Drive Array Physical Drive Rotational Speed. The following values are defined: other(1) The agent is unable to determine the rotational speed for this drive. rpm7200(2) The rotational speed for this drive is 7200 rpm. rpm10K(3) The rotational speed for this drive is 10000 rpm. rpm15K(4) The rotational speed for this drive is 15000 rpm. rpmSsd(5) The drive is made of solid state electronics and does not have a rotational speed. Enumeration: 'rpm10K': 3, 'other': 1, 'rpm15K': 4, 'rpm7200': 2, 'rpmSsd': 5.

Physical Drive Type. The following values are defined: other(1) The agent is unable to determine the type for this drive. parallelScsi(2) The drive type is parallel SCSI. sata(3) The drive type is Serial ATA. sas(4) The drive type is Serial Attached SCSI. Enumeration: 'sas': 4, 'sata': 3, 'other': 1, 'parallelScsi': 2.

Physical Drive SATA Version. The following values are defined: other(1) The agent is unable to determine the SATA version for this drive or it is not a SATA drive. sataOne(2) The drive is SATA version one. sataTwo(3) The drive is SATA version two. Enumeration: 'sataOne': 2, 'sataTwo': 3, 'other': 1.

Physical Drive Host Connector. This is the host connector to which the drive is ultimately attached. If the host connector cannot be determined, the agent will return a NULL string.

Physical Drive Box on Connector. The box on connector indicates to which box instance this physical drive belongs. The instances start at one and increment for each box attached to a connector. A value of -1 is returned for drives that do not support cpqDaPhyDrvBoxOnConnector.

Physical Drive Location String. This string describes the location of the drive in relation to the controller. If the location string cannot be determined, the agent will return a NULL string.

Drive Array Physical Drive Negotiated Link Rate. The following values are defined: other(1) The agent is unable to determine the negotiated link rate this drive or it is not a SAS or SATA drive. rate-1-5(2) The negotiated link rate for this drive is 1.5 Gigabits per second. rate-3-0(3) The negotiated link rate for this drive is 3.0 Gigabits per second. rate-6-0(4) The negotiated link rate for this drive is 6.0 Gigabits per second. rate-12-0(5) The negotiated link rate for this drive is 12.0 Gigabits per second. Enumeration: 'rate-12-0': 5, 'other': 1, 'rate-6-0': 4, 'rate-3-0': 3, 'rate-1-5': 2.

Drive Array Physical Drive Native Command Queueing. The following values are defined: other(1) The agent is unable to determine the NCQ configuration for this drive or it is not a SATA drive. noControllerSupport(2) The array controller does not support NCQ. noDriveSupport(3) The array controller does support NCQ, but the drive does not. ncqDisabled(4) The array controller and drive support NCQ, but it is disabled. ncqEnabled(5) The array controller and drive support NCQ and it is enabled. Enumeration: 'noControllerSupport': 2, 'other': 1, 'ncqEnabled': 5, 'noDriveSupport': 3, 'ncqDisabled': 4.

Drive Array Physical Drive PHY Count. This value indicates how many PHYs exist on SAS/SATA disk. For parallel SCSI disks, this value is set to -1.

Drive Array Physical Drive Multi-path Access Status. This indicates if this physical drive has been configured to have and currently still has more than one I/O path to the controller. The following values are valid: Other (1) Indicates that the instrument agent can not determine if this physical drive has multi-path access. Not Supported (2) Indicates that multi-path access to this physical drive is not supported. Not Configured (3) Indicates that the physical drive is not configured to have multi-path access. Path Redundant (4) Indicates that the physical drive currently has more than one I/O path to the controller. No Redundant Path (5) Indicates that the physical drive previously had more than one I/O path to the controller, but now has no redundant I/O path. Drive Failed (6) Indicates that the physical drive has failed. Enumeration: 'notConfigured': 3, 'pathRedundant': 4, 'other': 1, 'driveFailed': 6, 'notSupported': 2, 'noRedundantPath': 5.

Drive Array Physical Drive Media Type. The following values are defined: other(1) The instrument agent is unable to determine the physical drives media type. rotatingPlatters(2) The physical drive media is composed of rotating platters. solidState(3) The physical drive media is composed of solid state electronics. Enumeration: 'solidState': 3, 'other': 1, 'rotatingPlatters': 2.

Drive Array Physical Drive Current Temperature. This is the temperature of the physical drive in degrees Celsius. The field will contain -1 if the drive temperature cannot be calculated or if the controller does not support reporting drive temperature.

Drive Array Physical Drive Temperature Threshold. This is the temperature in degrees Celsius at which the drive says it is overheated. The field will contain -1 if the drive temperature threshold cannot be calculated or if the controller does not support reporting drive temperature threshold.

Drive Array Physical Drive Maximum Temperature. This is the maximum temperature in degrees Celsius that the drive has reached. The field will contain -1 if the maximum drive temperature cannot be calculated or if the controller does not support reporting maximum drive temperature.

Drive Array Physical Drive Solid State Disk Wear Status. This shows the wear status of the solid state physical drive. The following values are valid for the physical drive solid state wear status: Other (1) The instrument agent is unable to determine the physical drives solid state disk wear status. This value would be used for non SSD drives or SSD drives that do not support wear reporting. Ok (2) Indicates the solid state disk is not in any imminent danger of wear out. Fifty Six Day Threshold Passed (3) Indicates that based upon the current workload, the solid state disk will reach the maximum usage limit for writes (wear out) within fifty-six days. You should modify your write workload or begin preparing to replace your SSD drive. Five Percent Threshold Passed (4) Indicates that the solid state disk has passed the five percent threshold and is at or below five percent of reaching the maximum usage limit for writes (wear out). You should begin to prepare to replace your SSD drive. Two Percent Threshold Passed (5) Indicates that the solid state disk has passed the two percent threshold and is at or below two percent of reaching the maximum usage limit for writes (wear out). You should begin to prepare to replace your SSD drive. SSD Wear Out(6) Indicates that a solid state drive is approaching the maximum usage limit for writes (wear out) and should be replaced as soon as possible. Enumeration: 'twoPercentThreshold': 5, 'ok': 2, 'fivePercentThreshold': 4, 'other': 1, 'fiftySixDayThreshold': 3, 'ssdWearOut': 6.

Drive Array Physical Drive Power On Hours. This is the total number of hours that the physical disk has been powered on. This value will be 4,294,967,295 if the disk power on hours cannot be determined or is not supported.

Drive Array Physical Drive Solid State Percent Endurance Used. This value specifies the hundredths of the percentage of solid state disk life used. The value of this field is allowed to exceed 100%. As an example, if the value reported is 50, this would indicate .50 percent endurance used. This value will be 4,294,967,295 if the percent endurance used cannot be determined or is not supported.

Drive Array Physical Drive Solid State Estimated Time Remaining In Hours. This is the estimated total number of hours that the solid state physical disk has remaining. This value will be 4,294,967,295 if the solid state disk estimated time remaining in hours cannot be determined or is not supported.

Drive Array Physical Drive Authentication Status. The following values are defined: Other (1) Indicates that the instrument agent can not determine the physical drive's authentication status. Not Supported (2) Indicates that authentication for this physical drive is not supported. Authentication Failed(3) The physical drive could not be authenticated as a genuine HP hard drive. The array controller will no longer control the drive LEDs. Please replace the hard drive with a genuine HP hard drive. Authentication Passed(4) The physical drive has passed all authentication tests and has been validated to be a genuine HP hard drive. Enumeration: 'notSupported': 2, 'authenticationPassed': 4, 'other': 1, 'authenticationFailed': 3.

Physical Drive Smart Carrier Application Firmware Revision. This displays the physical drive smart carrier application firmware revision number. This value will be nonzero if the physical drive supports authentication and cpqDaPhyDrvAuthenticationStatus has a value of authenticationPassed(4).

Physical Drive Smart Carrier Bootloader Firmware Revision. This displays the physical drive smart carrier bootloader firmware revision number. This value will be nonzero if the physical drive supports authentication and cpqDaPhyDrvAuthenticationStatus has a value of authenticationPassed(4).

Physical Drive Encryption Status. The physical drive's encryption status. The following values are valid: other (1) Indicates that the instrument agent does not recognize the value. You may need to upgrade the instrument agent. Encrypted (2) Indicates this drive is online and a member of a logical drive that is encrypted. Not Encrypted (3) Indicates this drive is not a member of a logical drive that is encrypted. Enumeration: 'encrypted': 2, 'other': 1, 'notEncrypted': 3.

Drive Array Physical Drive Error Log Table. A table of physical drive entries. The Error Log Table is not supported by the IDA, IDA Expansion, or IDA-2 controllers.

Drive Array Physical Drive Entry.

Drive Array Physical Drive Error Log Controller Index. This index maps the physical drive back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Physical Drive Error Log Index. This index is used for selecting the physical drive table entry. This number, along with the cpqDaPhyDrvErrCntlrIndex uniquely identify a specific physical drive.

Drive Array Physical Drive Error Log Index. This index is used for selecting the physical drive table entry. This number, along with the cpqDaPhyDrvErrCntlrIndex uniquely identify a specific physical drive.

Physical Drive Error Log Error Type. The type of error in the error log. The valid types are: Other (1) Indicates that the instrument agent does not recognize the type of error in the error log. No Error (2) Indicates that this error log entry does not have an error. SCSI Error (3) Indicates that this error log entry is a SCSI Error. CAM Error (4) Indicates that this error log entry is a CAM error. Enumeration: 'noError': 2, 'other': 1, 'scsiError': 3, 'camError': 4.

Physical Drive Error Log SCSI Operation. This is the SCSI Command Operation Code byte associated with the error log entry. For further specifications consult a SCSI-2 logical specification or other SCSI reference.

Physical Drive Error Log SCSI Status. This is the SCSI Status Code byte associated with the error log entry. For further specifications consult a SCSI-2 logical specification or other SCSI reference.

Physical Drive Error Log CAM Status. This is the SCSI CAM Status byte associated with the error log entry. For further specifications consult a SCSI-2 logical specification or other SCSI reference.

Physical Drive Error Log Sense Key. This is the SCSI Sense Key byte associated with the error log entry. For further specifications consult a SCSI-2 logical specification or other SCSI reference.

Physical Drive Error Log Qualifier. This is the SCSI Additional Sense Code Qualifier byte (as returned by the Request Sense command) associated with the error log entry. For further specifications consult a SCSI-2 logical specification or other SCSI reference.

Physical Drive Error Log Sense Code. This is the SCSI Sense Code associated with the error log entry. For further specifications consult a SCSI-2 logical specification or other SCSI reference.

Physical Drive Error Log Block Address Is Valid. The valid values are: False (1) Indicates that the Block Address object (cpqDaPhyDrvBlock) is not a valid address. True (2) Indicates that the Block Address object (cpqDaPhyDrvBlock) is a valid address. Enumeration: 'true': 2, 'false': 1.

Physical Drive Error Log Block Address. This is the SCSI Block Address (as returned by the Request Sense Command) associated with the error log entry. For further specifications consult a SCSI-2 logical specification or other SCSI reference.

Physical Drive Error Log Reference Time. This gives a relative time stamp as to when the error log entry occurred. The Reference Time shows the number of hours that a physical drive has been spinning since the drive was initialized for monitor and performance.

Physical Drive Error Log User Description. This is a string built by the agent which contains the Reference Time (cpqDaPhyDrvTime) and a brief description of the disk error associated with the particular error log entry. This field is being deprecated, and future management station applications should be aware that this field may not contain ASCII string data.

The index used to display an error associated with a physical drive. This number refers to an entry in a list of error strings enumerating the possible physical drive errors associated with a particular physical disk drive. The valid values are: DriveFailure (1) The Management Station should display the following string: 'Drive Failure'. CommFailure(2) The Management Station should display the following string: 'Communication Failure'. DriveIOError(3) The Management Station should display the following string: 'Drive I/O Error'. SCSICommError(4) The Management Station should display the following string: 'SCSI Communication Error'. UpgradeRequired(5) The Management Station should display the following string: 'Configuration Utility or OS upgrade required'. DriveWriteProtected(6) The Management Station should display the following string: 'Drive Write Protected - Check Drive Jumpers'. InvalidRequest(7) The Management Station should display the following string: 'Invalid Request'. SCSIMessageError(8) The Management Station should display the following string: 'SCSI Message Error'. ControllerFailure(9) The Management Station should display the following string: 'Controller Failure'. InternalExternalConflict(10) The Management Station should display the following string: 'Internal/External Conflict on Port 1'. InternalDriveFailure(11) The Management Station should display the following string: 'Internal Drive Failure'. SCSIErrorOutOfRange(12) The Management Station should display the following string: 'SCSI Error, Sense Code = %xh' where %x is the value of the cpqDaPhyDrvSenseCode object. This index will only be provided if the specified object exceeds the valid range. CAMErrorOutOfRange(13) The Management Station should display the following string: 'CAM Error, CAM status =%xh' where %x is the value of the cpqDaPhyDrvCamStatus object. This index will only be provided if the specified object exceeds the valid range. ErrorTypeOutOfRange(14) The Management Station should display the following string: 'Error type =%xh' where %x is the value of the cpqDaPhyDrvErrType object. This index will only be provided if the specified object exceeds the valid range. Enumeration: 'internExternConflict': 10, 'camErrorOutOfRange': 13, 'driveFailure': 1, 'scsiMessageError': 8, 'scsiErrorOutOfRange': 12, 'driveIOError': 3, 'commFailure': 2, 'driveWriteProtected': 6, 'controllerFailure': 9, 'invalidRequest': 7, 'errorTypeOutOfRange': 14, 'internalDriveFailure': 11, 'scsiCommError': 4, 'compaqUpgradeRequired': 5.

Drive Array Physical Drive Access Path Table. A table of access path entries supporting physical drive multi-path cabling configuration.

Drive Array Physical Drive Access Path Entry.

Drive Array Physical Drive Access Path Controller Index. This index maps the physical drive access path back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Physical Drive Access Path Drive Index. This index maps the access path to a physical drive.

Drive Array Physical Drive Access Path Index. This path index keeps track of multiple instances of access paths from a controller to a physical drive. This number, along with the cpqDaPhyDrvPathCntlrIndex and cpqDaPhyDrvPathDrvIndex uniquely identify a specific physical drive access path.

Physical Drive Access Path Status. This shows the status of the physical drive access path. The following values are valid: Other (1) Indicates that the instrument agent can not determine the status of this access path. OK (2) Indicates the access path is functioning properly. Link Down (3) Indicates that the controller can no longer access the physical drive through this path. Enumeration: 'linkDown': 3, 'other': 1, 'ok': 2.

Physical Drive Access Path Current Role. This shows the current role of physical drive access path. The following values are valid: Other (1) Indicates that the instrument agent does not recognize the role of this access path. Active (2) Indicates that this path is currently the default active I/O path to access the physical drive from the controller. Alternate (3) Indicates that this path is currently the alternate I/O path to access the physical drive from the controller. Enumeration: 'active': 2, 'alternate': 3, 'other': 1.

Physical Drive Access Path Host Connector. This is the host connector to which the access path is ultimately attached. If the host connector cannot be determined, the agent will return a NULL string.

Physical Drive Access Path Box on Connector. The box on connector indicates to which box instance this physical drive access path belongs.

Physical Drive Access Path Location String. This string describes the physical drive access path in relation to the controller. If the location string cannot be determined, the agent will return a NULL string.

Drive Array Physical Drive Threshold Table. A table of physical drive threshold entries.

Drive Array Physical Drive Threshold Entry. A physical drive threshold entry.

Drive Array Physical Drive Threshold Controller Index. This index maps the physical drive thresholds back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Physical Drive Threshold Index. This index maps the thresholds to a physical drive. The value of this index is the same as the one used with the physical drive table.

Used Reallocated Sectors Maximum Threshold. This shows the maximum threshold of the reallocation area that has been used by the physical drive. This threshold is associated with the cpqDaPhyDrvUsedReallocs object in the Physical Drive Table.

Reference Time Maximum Threshold in hours. This shows the maximum threshold in hours that a physical drive has been spinning since the drive was stamped. This threshold is associated with the cpqDaPhyDrvRefHours object in the Physical Drive Table.

Hard Read Errors Maximum Threshold. This shows the maximum threshold of read errors on a drive that could not be recovered by a physical drive's Error Correction Code (ECC) algorithm or through retries during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvHardReadErrs object in the Physical Drive Table.

Recovered Read Errors Maximum Threshold. This shows the maximum threshold of read errors corrected through physical drive retries during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvRecvReadErrs object in the Physical Drive Table.

Hard Write Errors Maximum Threshold. This shows the maximum threshold of write errors that could not be recovered by a physical drive during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvHardWriteErrs object in the Physical Drive Table.

Recovered Write Errors Maximum Threshold. This shows the maximum threshold of write errors corrected through physical drive retries or recovered by a physical drive during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvRecvWriteErrs object in the Physical Drive Table.

Seek Errors Maximum Threshold (high). The cpqDaphyDrvThrHSeekErrs and the cpqDaphyDrvThrSeekErrs together show the maximum threshold of total number of times that the physical disk drive detected a seek error during the reference hours (phyDrvRefHours). This threshold is associated with the cpqDaPhyDrvHSeekErrs object in the Physical Drive Table.

Seek Errors Maximum Threshold (low). The cpqDaphyDrvThrHSeekErrs and the cpqDaphyDrvThrSeekErrs together show the maximum threshold of total number of times that the physical disk drive detected a seek error during the reference hours (phyDrvRefHours). This threshold is associated with the cpqDaPhyDrvSeekErrs object in the Physical Drive Table.

Spin up Time Maximum Threshold in tenths of seconds. This shows the maximum of time it takes for a physical drive to spin up to full speed. This threshold is associated with the cpqDaPhyDrvSpinupTime object in the Physical Drive Table.

Functional Test 1 Minimum Threshold. This provides the minimum threshold for information about a series of tests that indicate how well a physical drive works. These tests compare the way the physical drive currently operate when performing various tasks with the way it worked when it was new. This threshold is associated with the cpqDaPhyDrvFunctTest1 object in the Physical Drive Table.

Functional Test 2 Minimum Threshold. This provides the minimum threshold for information about a series of tests that indicate how well a physical drive works. These tests compare the way the physical drive currently operates when performing various tasks with the way it worked when it was new. This threshold is associated with the cpqDaPhyDrvFunctTest2 object in the Physical Drive Table.

Functional Test 3 Minimum Threshold. This provides the minimum threshold for information about a series of tests that indicate how well a physical drive works. These tests compare the way the physical drive currently operates when performing various tasks with the way it worked when it was new. This threshold is associated with the cpqDaPhyDrvFunctTest3 object in the Physical Drive Table.

DRQ Timeouts Maximum Threshold. This shows the maximum threshold of the number of times that a physical drive continued to request data, but did not get a command completion during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvDrqTimeouts object in the Physical Drive Table.

Other Timeouts Maximum Threshold. This shows the maximum threshold of the number of times that a physical drive did not respond with an interrupt within a controller-defined period of time after a command had been issued during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvOtherTimeouts object in the Physical Drive Table.

Spin up Retries Maximum Threshold. This shows the maximum threshold of the number of times that a physical drive had to retry to spin up before successfully achieving operating speed during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvSpinupRetries object in the Physical Drive Table.

Recovery Failed (Bad) Read Error Maximum Threshold. This shows the maximum threshold of the number of times a read error occurred while performing Automatic Data Recovery from this physical drive to another drive during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvBadRecvReads object in the Physical Drive Table.

Recovery Failed (Bad) Write Error Maximum Threshold. This shows the maximum threshold of the number of times a write error occurred while performing Automatic Data Recovery from another drive to this physical drive during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvBadRecvWrites object in the Physical Drive Table.

Format Error Maximum Threshold. This shows the maximum threshold of the number of times a format operation failed when the controller attempted to remap a bad sector during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvFormatErrs object in the Physical Drive Table.

Power On Self Test (Post) Error Maximum Threshold. This shows the maximum threshold of the number of times that a physical drive failed its self test during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvPostErrs object in the Physical Drive Table.

Drive Not Ready Errors Maximum Threshold. This shows the maximum threshold of the number of times the physical drive failed after the spin up command was issued during the reference time (phyDrvRefTime). When the spin up command was issued, the drive failed to reach its ready state. This threshold is associated with the cpqDaPhyDrvNotReadyErrs object in the Physical Drive Table.

Physical Drive Reallocation Aborts Maximum Threshold. This shows the maximum threshold of the number of times the physical drive has failed due to an error that occurred when the controller was trying to reallocate a bad sector during the reference time (phyDrvRefTime). This threshold is associated with the cpqDaPhyDrvReallocAborts object in the Physical Drive Table.

Physical Drive Hot Plug Count Maximum Threshold. This shows the maximum threshold of the number of times this physical drive can be hot-plugged (removed) from a ProLiant Storage System. This threshold is associated with the cpqDaPhyDrvHotPlugs object in the Physical Drive Table.

Physical Drive Media Failure Count Maximum Threshold. This shows the maximum threshold of the number of times this physical drive can be failed due to unrecoverable media errors. This threshold is associated with the cpqDaPhyDrvMediaErrs object in the Physical Drive Table.

Physical Drive Hardware Error Count Maximum Threshold. This shows the maximum threshold of the number of times this physical drive can return a bad hardware status. The drive may be failed if retries do not work. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers. This threshold is associated with the cpqDaPhyDrvHardwareErrs object in the Physical Drive Table.

Physical Drive Aborted Command Failures Maximum Threshold. This shows the maximum threshold of the number of times this physical drive can be failed due to aborted commands that could not be retried successfully. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers. This threshold is associated with the cpqDaPhyDrvAbortedCmds object in the Physical Drive Table.

Physical Drive Spin-Up Failure Count Maximum Threshold. This shows the maximum threshold of the number of times this physical drive was failed due to a failure of a spin-up command. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers. This threshold is associated with the cpqDaPhyDrvSpinUpErrs object in the Physical Drive Table.

Physical Drive Bad Target Count Maximum Threshold. This shows the maximum threshold of the number of times this physical drive can perform some action that did not conform to the SCSI-2 bus protocol. These actions will cause the SCSI bus to be reset. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers. This threshold is associated with the cpqDaPhyDrvBadTargetErrs object in the Physical Drive Table.

Used Reallocated Sectors Threshold Has Been Violated. This is used to indicate whether the number of used sectors of the reallocation area for a physical drive has ever exceeded the maximum allowable threshold. The valid values are: false (1) Indicates that the Used Reallocated Sectors object (cpqDaPhyDrvUsedReallocs) value has not exceeded the maximum threshold (cpqDaPhyDrvThrUsedReallocs). true (2) Indicates that the Used Reallocated Sectors object (cpqDaPhyDrvUsedReallocs) value has exceeded the maximum threshold (cpqDaPhyDrvThrUsedReallocs). unknown (4294967295) The agent is unable to determine if the drive has a threshold violation. Enumeration: 'true': 2, 'false': 1, 'unknown': 4294967295.

Spin up Time in tenths of seconds Threshold Has Been Violated. This is used to indicate whether the time it took for a physical drive to spin up to full speed has ever exceeded the maximum allowable threshold. The valid values are: false (1) Indicates that the Spin up Time object (cpqDaPhyDrvSpinupTime) value has not exceeded the maximum threshold (cpqDaPhyDrvThrSpinupTime). true (2) Indicates that the Spin up Time object (cpqDaPhyDrvSpinupTime) value has exceeded the maximum threshold (cpqDaPhyDrvThrSpinupTime). unknown (4294967295) The agent is unable to determine if the drive has a threshold violation. Enumeration: 'true': 2, 'false': 1, 'unknown': 4294967295.

Functional Test 1 Threshold Has Been Violated. This is used to indicate whether the percentage value returned from Functional Test 1 has every dropped below the allowable threshold for that test. The valid values are: false (1) Indicates that the Functional Test 1 object (cpqDaPhyDrvFunctTest1) value has not fallen below the minimum threshold (cpqDaPhyDrvThrFunctTest1). true (2) Indicates that the Functional Test 1 object (cpqDaPhyDrvFunctTest1) value has fallen below the minimum threshold (cpqDaPhyDrvThrFunctTest1). unknown (4294967295) The agent is unable to determine if the drive has a threshold violation. Enumeration: 'true': 2, 'false': 1, 'unknown': 4294967295.

Functional Test 2 Threshold Has Been Violated. This is used to indicate whether the percentage value returned from Functional Test 2 has every dropped below the allowable threshold for that test. The valid values are: false (1) Indicates that the Functional Test 2 object (cpqDaPhyDrvFunctTest2) value has not fallen below the minimum threshold (cpqDaPhyDrvThrFunctTest2). true (2) Indicates that the Functional Test 2 object (cpqDaPhyDrvFunctTest2) value has fallen below the minimum threshold (cpqDaPhyDrvThrFunctTest2). unknown (4294967295) The agent is unable to determine if the drive has a threshold violation. Enumeration: 'true': 2, 'false': 1, 'unknown': 4294967295.

Functional Test 3 Threshold Has Been Violated. This is used to indicate whether the percentage value returned from Functional Test 3 has every dropped below the allowable threshold for that test. The valid values are: false (1) Indicates that the Functional Test 3 object (cpqDaPhyDrvFunctTest3) value has not fallen below the minimum threshold (cpqDaPhyDrvThrFunctTest3). true (2) Indicates that the Functional Test 3 object (cpqDaPhyDrvFunctTest3) value has fallen below the minimum threshold (cpqDaPhyDrvThrFunctTest3). unknown (4294967295) The agent is unable to determine if the drive has a threshold violation. Enumeration: 'true': 2, 'false': 1, 'unknown': 4294967295.

Physical Drive Bus Fault Count Maximum Threshold. This shows the maximum threshold of the number of times this physical drive can return a bus fault status. The drive may be failed if retries do not work. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers. This threshold is associated with the cpqDaPhyDrvBusFaults object in the Physical Drive Table.

Physical Drive IRQ Deglitch Count Maximum Threshold. This shows the maximum threshold of the number of times this physical drive can return a IRQ deglitch status. The drive may be failed if retries do not work. This is not supported by the IDA, IDA Expansion, or IDA-2 controllers. This threshold is associated with the cpqDaPhyDrvIrqDeglitches object in the Physical Drive Table.

Drive Array Controller Performance Monitor Table. A table of controller entries supporting the performance monitor information.

Drive Array Controller Performance Monitor Entry. A performance monitor entry.

Drive Array Controller Performance Monitor Controller Index. This maps the performance monitor information into their respective controllers which support performance data.

Drive Array Controller Performance Monitor Instance Index. This maps the performance monitor information for a specific controller and sample interval to controllers which support performance data.

Array Controller Performance Monitor Sample Interval. This value indicates the length of the performance interval for this controller and all logical volumes associated with this controller. This value is reported in seconds.

Array Controller Performance Monitor Version. This value specifies the version of the performance monitor interface.

Array Controller Performance Monitor Cpu Percent Busy. This value specifies the total CPU percent busy as a number from 0 to 100 inclusive. If the value cannot be determined or is not applicable, the value is set to -1.

Array Controller Performance Monitor Command Count. This value shows the total number of read and write commands processed in this sample. This value is expressed in read and write commands per second.

Array Controller Performance Monitor Average Command Latency. This value shows the average command latency for this sample in 1/100,000 second units.

Drive Array Logical Drive Performance Monitor Table. A table of logical drive entries supporting the performance monitor information.

Drive Array Logical Drive Performance Monitor Entry. A performance monitor entry.

Drive Array Logical Drive Performance Monitor Controller Index. This maps the performance monitor information into their respective controllers which support performance data.

Drive Array Logical Drive Performance Monitor Drive Index. This maps the performance monitor information into their respective logical drives which support performance data.

Drive Array Logical Drive Performance Monitor Instance Index. This maps the performance monitor information for a specific controller, logical drive and sample interval to controllers which support performance data.

Array Logical Drive Performance Monitor Sample Interval. This value indicates the length of the performance interval for this controller and all logical volumes associated with this controller. This value is reported in seconds.

Array Logical Drive Performance Monitor Average Queue Depth. This value indicates the average command queue depth of the logical volume.

Array Logical Drive Performance Monitor Reads. This value is the count of read requests for the logical volume expressed in reads per second.

Array Logical Drive Performance Monitor Writes. This value is the count of write requests for the logical volume expressed in writes per second.

Array Logical Drive Performance Monitor Total I/O. This value shows the total number of read and write requests for the logical volume expressed in reads and writes per second.

Array Logical Drive Performance Monitor Cache Hits. This value shows the total number of read cache hits for the logical volume. This value is expressed in cache hits per second.

Array Logical Drive Performance Monitor Cache Misses. This value shows the total number of read cache misses for the logical volume. This value is expressed in cache misses per second.

Array Logical Drive Performance Monitor Read Ahead Sectors. This value shows the total number read ahead sectors pre-fetched for the logical volume for this interval. This value is expressed in sectors per second.

Array Logical Drive Performance Monitor Sectors Read. This value shows the number of sectors read for the logical volume for this interval. This value is expressed in sectors per second.

Array Logical Drive Performance Monitor Sectors Written. This value shows the number of sectors written for the logical volume for this interval. This value is expressed in sectors per second.

Drive Array Tape Drive Table. A table of tape drive entries.

Drive Array Tape Drive Entry. A tape drive entry.

Drive Array Tape Drive Controller Index. This index maps the tape drive back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Tape Drive SCSI Bus Index. This is the controller SCSI bus to which the tape drive is attached.

Drive Array Tape Drive SCSI Index. This is the SCSI Target Id of the tape drive.

Drive Array Tape Drive Logical Unit Number Index. This is the logical unit number of the tape drive.

Drive Array Tape Drive Model Name. This is the model name of the tape drive. It can be used for identification purposes.

Drive Array Tape Drive Serial Number. This is the unit serial number for the tape drive. It can be used for identification purposes.

Drive Array Tape Drive Firmware Revision. This is firmware revision level of the tape drive. It can be used for identification purposes.

Drive Array Tape Drive Status. The tape drive can be in one of the following states: other(1) The tape drive is in a state other than one of those listed below. ok(2) Indicates that the tape drive is in normal operation mode. No user action is necessary. degraded(3) Indicates that the tape drive has degraded in some manner. failed(4) Indicates that the tape drive has failed and can no longer return data. The tape drive may need to be replaced. offline(5) Indicates that the Agents can no longer communicate with the tape drive. This could be caused by a cabling problem or the tape drive may be powered off. missingWasOk(6) Indicates that a tape drive had a status of OK and is no longer present. The drive has been removed. missingWasOffline(7) Indicates that a tape drive had a status of OFFLINE and is no longer present. The drive has been removed. Enumeration: 'missingWasOffline': 7, 'ok': 2, 'missingWasOk': 6, 'failed': 4, 'other': 1, 'degraded': 3, 'offline': 5.

Drive Array Tape Drive Condition. This value represents the overall condition of the tape drive.

Drive Array Tape Drive Firmware Subtype. This is used to differentiate the firmware versions which have the same tape drive type (as specified by cpqDaTapeDrvType). Tape drives will contain a value of 1 for this variable when they first ship, and this value will be incremented if future versions are shipped which are not firmware compatible with the predecessor. If the tape drive does not support this capability, a value of 0 will be returned.

Drive Array Tape Drive Type. This is the drives model, and can be used for identification purposes. The following values are defined: other(1) The management agent does not recognize this model. You may need to upgrade your software. cpqDat4-16(2) Compaq 4/8-Gigabyte TurboDAT Drive. cpqDatAuto(3) Compaq TurboDAT Autoloader. cpqDat2-8(4) Compaq 2/8-Gigabyte TurboDAT Drive. cpqDlt10-20(5) Compaq 10/20-GB DLT Drive. cpqDlt20-40(6) Compaq 20/40-GB DLT Drive. cpqDlt15-30(7) Compaq 15/30-GB DLT Drive. cpqDlt35-70(8) Compaq 35/70-GB DLT Drive. cpqDat4-8(9) Compaq 4/8-GB DAT Drive. cpqSlr4-8(10) Compaq 4/8-GB SLR Drive. cpqDat12-24(11) Compaq 12/24-GB DAT Drive. cpqDatAuto12-24(12) Compaq 12/24-GB DAT Autoloader. cpqAit35(14) Compaq AIT 35GB Drive. cpqAit50(15) Compaq AIT 50GB Drive. cpqDat20-40(16) Compaq 20/40GB DAT Drive. cpqDlt40-80(17) Compaq 40/80GB DLT Drive. cpqDatAuto20-40(18) Compaq 20/40GB DAT Autoloader. Enumeration: 'cpqDat20-40': 16, 'cpqDat2-8': 4, 'cpqDat4-8': 9, 'cpqDatAuto': 3, 'cpqDlt15-30': 7, 'cpqAit35': 14, 'cpqDat4-16': 2, 'cpqDlt35-70': 8, 'cpqDatAuto20-40': 18, 'other': 1, 'cpqDlt40-80': 17, 'cpqDlt20-40': 6, 'cpqDlt10-20': 5, 'cpqDat12-24': 11, 'cpqAit50': 15, 'cpqDatAuto12-24': 12, 'cpqSlr4-8': 10.

Drive Array Tape Drive Cleaning Required. This is an indication of whether the tape drive heads require a cleaning session to occur. If this variable indicates a need to clean the tape heads, then a cleaning tape will need to be inserted and run through a cleaning cycle. This variable can be in one of the following states: other(1) The tape drive does not support monitoring of the cleaning required status. true(2) The tape drive requires a cleaning tape session in order to clean the heads. false(3) The tape drive does not require any cleaning tape session. Enumeration: 'false': 3, 'other': 1, 'true': 2.

Drive Array Tape Drive Cleaning Tape Replacement. This variable is only applicable to autoloader tape drives. This variable indicates whether the cleaning tape which is inserted in an autoloader needs to be replaced because its cleaning capability is exhausted (it is at end of tape). This variable can be in one of the following states: other(1) The tape drive does not support monitoring of the cleaning tape replacement status. true(2) The autoloader tape drive requires a new cleaning tape to be inserted. false(3) The tape drive does not require a new cleaning tape. Enumeration: 'false': 3, 'other': 1, 'true': 2.

Drive Array Tape Drive Cleaning Tape Count. This variable is a count from a tape drive of the number of cleanings done by the tape cleaner last in the drive.

Drive Array Tape Drive Library Drive. This variable indicates whether or not the tape drive is part of a tape library. It can be in one of the following states: other(1) Indicates that the instrument agent cannot determine if the tape drive is part of a tape library. true(2) The tape drive is part of a tape library. false(3) The tape drive is not part of a tape library. Enumeration: 'false': 3, 'other': 1, 'true': 2.

Tape Physical Drive Magazine Size. This variable indicates the number of tape slots available in the tape autoloader magazine cartridge that is currently loaded into the tape drive. For non-autoloader devices, this value will be -1.

Drive Array Tape Drive Hot Plug Support Status. The following values are defined: other(1) The agent is unable to determine if this drive supports hot plug replacement. hotPlug(2) The drive supports hot plug replacement. nonhotPlug(3) The drive does not support hot plug replacement. Enumeration: 'other': 1, 'nonHotPlug': 3, 'hotPlug': 2.

Drive Array Tape Drive Placement. The following values are defined: other(1) The agent is unable to determine if the tape drive is internal or external to the system chassis. internal(2) The tape drive is located in an internal Proliant system chassis. external(3) The tape drive is located in an external Proliant storage system. Enumeration: 'other': 1, 'internal': 2, 'external': 3.

Drive Array Tape Drive Current Width. The following values are defined: other(1) The agent is unable to determine the current negotiated data transfer width for this drive. narrow(2) The negotiated data transfer width for this drive is narrow (8 data bits). wide16(3) The negotiated data transfer width for this drive is wide (16 data bits). Enumeration: 'wide16': 3, 'other': 1, 'narrow': 2.

Drive Array Tape Drive Current Data Transfer Speed. The following values are defined: other(1) The agent is unable to determine the current negotiated data transfer speed for this drive. asynchronous(2) The negotiated data transfer speed for this drive is asynchronous. fast(3) The negotiated data transfer speed for this drive is 10 million transfers per second). ultra(4) The negotiated data transfer speed for this drive is 20 million transfers per second. ultra2(5) The negotiated data transfer speed for this drive is 40 million transfers per second. ultra3(6) The negotiated data transfer speed for this drive is 80 million transfers per second. Enumeration: 'ultra2': 5, 'ultra3': 6, 'other': 1, 'asynchronous': 2, 'fast': 3, 'ultra': 4.

Drive Array Tape Drive Protocol. The following values are defined: other(1) The agent is unable to determine the protocol for this drive. parallelScsi(2) The drive protocol is parallel SCSI. sata(3) The drive protocol is Serial ATA. sas(4) The drive protocol is Serial Attached SCSI. Enumeration: 'sas': 4, 'sata': 3, 'other': 1, 'parallelScsi': 2.

Drive Array Tape Drive Negotiated Link Rate. The following values are defined: other(1) The agent is unable to determine the negotiated link rate this drive. rate-1-5(2) The negotiated link rate for this drive is 1.5 Gigabits per second. rate-3-0(3) The negotiated link rate for this drive is 3.0 Gigabits per second. Enumeration: 'other': 1, 'rate-3-0': 3, 'rate-1-5': 2.

Drive Array Tape Counters Table.

Drive Array Tape Counters Entry.

Drive Array Tape Counters Controller Index. This index maps the tape drive back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Tape Counters Scsi Bus Index. This is the controller SCSI bus to which the tape drive is attached.

Drive Array Tape Counters SCSI Index. This is the SCSI Target Id of the tape drive.

Drive Array Tape Counters Logical Unit Number Index. This is the logical unit number of the tape drive.

Tape Device Re-write count. This is the number of times blocks had to be re-written to the device. This value is maintained since the Tape Hardware Interface driver was loaded. Re-write errors may occasionally occur. If this value should rise dramatically, you may need to clean the device. If you continue to have re-writes, you may have a problem. Some common causes include radio frequency interference (RFI) on the bus cables, bad or missing terminating resisters on the drives or having more than one device with the same SCSI ID. Insure the bus cable is free of obstructions and that the devices on the bus are properly configured.

Tape Device Re-read count. This is the number of times blocks had to be re-read from the device. This value is maintained since the Tape Hardware Interface driver was loaded. Re-read errors may occasionally occur. If this value should rise dramatically, you may need to clean the device. If you continue to have re-reads, you may have a problem. Some common causes include radio frequency interference (RFI) on the bus cables, bad or missing terminating resisters on the drives or having more than one device with the same SCSI ID. Insure the bus cable is free of obstructions and that the devices on the bus are properly configured.

Tape Device Total Errors. This is the total number of read/write errors encountered. This value is maintained since the Tape Hardware Interface driver was loaded. Errors may occasionally occur. If this value should rise dramatically, you may need to clean the device. If you continue to have errors, you may have a problem. Some common causes include radio frequency interference (RFI) on the bus cables, bad or missing terminating resisters on the drives or having more than one device with the same SCSI ID. Insure the bus cable is free of obstructions and that the devices on the bus are properly configured.

Tape Device Total Uncorrectable Errors. This is the total number of read and write errors which could not be corrected. This value is maintained since the Tape Hardware Interface driver was loaded. Errors may occasionally occur. If this value should rise dramatically, you may need to clean the device. If you continue to have errors, you may have a problem. Some common causes include radio frequency interference (RFI) on the bus cables, bad or missing terminating resisters on the drives or having more than one device with the same SCSI ID. Insure the bus cable is free of obstructions and that the devices on the bus are properly configured.

Tape Device Total Bytes. This is the number total number of bytes read/written to the tape currently installed in the device. This value is reset whenever a new tape is inserted into the device.

Drive Array Tape Library Table.

Drive Array Tape Library Entry.

Drive Array Tape Library Controller Index. This index maps the tape library back to the controller to which it is attached. The value of this index is the same as the one used under the controller group.

Drive Array Tape Library Scsi Bus. The bus index indicates to which SCSI bus instance on a controller this table entry belongs. The instances start at one and increment for each SCSI bus on a controller.

Drive Array Tape Library Scsi Target. The target index indicates to which SCSI ID on a controller SCSI bus this table entry belongs.

Drive Array Tape Library Scsi Lun. The Lun index indicates to which logical unit on a SCSI ID on a controller SCSI bus this table entry belongs.

Drive Array Tape Library Serial Number. This is the unit serial number for the tape library. It can be used for identification purposes.

Drive Array Tape Library Model. This is the model name of the tape library. It can be used for identification purposes.

Drive Array Tape Library Serial Number. This is firmware revision level of the tape library. It can be used for identification purposes.

Drive Array Tape Library Status. The library can be in one of the following states: other(1) The library is in a state other than one of those listed below. ok(2) Indicates that the library is in normal operation mode. No user action is necessary. degraded(3) Indicates that the library has degraded in some manner. failed(4) Indicates that the library has failed and can no longer return data. The library may need to be replaced. offline(5) Indicates that the Insight Agents can no longer communicate with the library. This could be caused by a cabling problem or the library may be powered off. Enumeration: 'failed': 4, 'degraded': 3, 'other': 1, 'ok': 2, 'offline': 5.

Drive Array Tape Library Door Status. The door can be in one of the following states: other(1) The door is in a state other than one of those listed below. notSupported(2) The door status is not supported by the device. closed(3) The door is closed. open(4) The door is open. Enumeration: 'notSupported': 2, 'other': 1, 'open': 4, 'closed': 3.

Drive Array Tape Library Condition. This value represents the overall condition of the tape library.

Drive Array Tape Library Overall Condition. This value represents the overall condition of the tape library and any associated tape drives.

Drive Array Tape Library Last Error. This is the last error returned by the tape library.

Drive Array Tape Library Stat Hours. This is the number of hours of operation for the library.

Drive Array Tape Library Stat Moves. This is the number of tape moves for the library loader arm.

Drive Array Tape Library Tape Drive List. This is a data structure containing the list of tape drive ids that are present in this library. The format is: field octets contents ===== ====== ======== 1 1 Tape controller slot index 2 2 Tape drive SCSI bus 3 3 Tape drive SCSI target 4 4 Tape drive SCSI logical unit number These 4 octets are repeated for each drive in the library. For n tape drives in a library, the string is 4 * n octets long.

Drive Array Tape Library Current Width. The following values are defined: other(1) The agent is unable to determine the current negotiated data transfer width for this library. narrow(2) The negotiated data transfer width for this library is narrow (8 data bits). wide16(3) The negotiated data transfer width for this library is wide (16 data bits). Enumeration: 'wide16': 3, 'other': 1, 'narrow': 2.

Drive Array Tape Library Current Data Transfer Speed. The following values are defined: other(1) The agent is unable to determine the current negotiated data transfer speed for this library. asynchronous(2) The negotiated data transfer speed for this library is asynchronous. fast(3) The negotiated data transfer speed for this library is 10 million transfers per second). ultra(4) The negotiated data transfer speed for this library is 20 million transfers per second. ultra2(5) The negotiated data transfer speed for this library is 40 million transfers per second. ultra3(6) The negotiated data transfer speed for this library is 80 million transfers per second. Enumeration: 'ultra2': 5, 'ultra3': 6, 'other': 1, 'asynchronous': 2, 'fast': 3, 'ultra': 4.

Drive Array Tape Library Tape Drive List 2. This is a data structure containing the list of tape drive ids that are present in this library. The format is: field octets contents ===== ====== ======== 1 1-4 Tape controller index 2 5 Tape drive SCSI bus 3 6 Tape drive SCSI target 4 7 Tape drive SCSI logical unit number These 7 octets are repeated for each drive in the library. For n tape drives in a library, the string is 7 * n octets long.

Drive Array Tape Library Protocol. The following values are defined: other(1) The agent is unable to determine the protocol for this library. parallelScsi(2) The library protocol is parallel SCSI. sata(3) The library protocol is Serial ATA. sas(4) The library protocol is Serial Attached SCSI. Enumeration: 'sas': 4, 'sata': 3, 'other': 1, 'parallelScsi': 2.

Drive Array Tape Library Negotiated Link Rate. The following values are defined: other(1) The agent is unable to determine the negotiated link rate for this library. rate-1-5(2) The negotiated link rate for this library is 1.5 Gigabits per second. rate-3-0(3) The negotiated link rate for this library is 3.0 Gigabits per second. Enumeration: 'other': 1, 'rate-3-0': 3, 'rate-1-5': 2.

The total number of trap packets issued by the drive array enterprise since the instrument agent was loaded.

The maximum number of entries that will currently be kept in the trap log. If the maximum size has been reached and a new trap occurs the oldest trap will be removed.

An ordered list of trap log entries (conceptually a queue). The trap log entries will be kept in the order in which they were generated with the most recent trap at index 1 and the oldest trap entry at index trapLogMaxSize. If the maximum number size has been reached and a new trap occurs the oldest trap will be removed when the new trap is added so the trapMaxLogSize is not exceeded.

A description of a trap event.

This value uniquely identifies this trapLogEntry at this time. The most recent trap will have an index of 1 and the oldest trap will have an index of trapLogMaxSize. Because of the queue-like nature of the trapLog this particular trap event's index will change as new traps are issued.

The type of the trap event that this entry describes. This number refers to an entry in a list of traps enumerating the possible traps the Drive Array agent may issue. Enumeration: 'cpqDaAccelStatusChange': 5, 'cpqDa2PhyDrvStatusChange': 3003, 'cpqDa2AccelBadDataTrap': 3006, 'cpqDa2AccelBatteryFailed': 3007, 'cpqDa2AccelStatusChange': 3005, 'cpqDaPhyDrvThreshExceededTrap': 4, 'cpqDa2LogDrvStatusChange': 3001, 'cpqDaLogDrvStatusChange': 1, 'cpqDaAccelBatteryFailed': 7, 'cpqDaAccelBadDataTrap': 6, 'cpqDa2SpareStatusChange': 3002, 'cpqDaSpareStatusChange': 2, 'cpqDaPhyDrvStatusChange': 3, 'cpqDa2PhyDrvThreshExceededTrap': 3004.

The time of the trap event that this entry describes. The time is given in year (first octet), month, day of month, hour, minute, second (last octet) order. Each octet gives the value in BCD.

Logical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array logical drive. The variable cpqDaLogDrvStatus indicates the current logical drive status.

Spare Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array spare drive. The variable cpqDaSpareStatus indicates the current spare drive status. The variable cpqDaSpareBusNumber indicates the SCSI bus number associated with this drive.

Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. The variable cpqDaPhyDrvBusNumber indicates the SCSI bus number associated with this drive.

Physical Drive Threshold Passed. This trap signifies that the agent has detected a factory threshold associated with one of the physical drive objects on a drive array has been exceeded. The variable cpqDaPhyDrvBusNumber indicates the SCSI bus number associated with the drive.

Accelerator Board Status Change. This trap signifies that the agent has detected a change in the cpqDaAccelStatus of an array accelerator write cache. The current status is represented by the variable cpqDaAccelStatus.

Accelerator Board Bad Data. This trap signifies that the agent has detected an array accelerator cache board that has lost battery power. If data was being stored in the accelerator memory when the server lost power, that data has been lost.

Accelerator Board Battery Failed. This trap signifies that the agent has detected a battery failure associated with the array accelerator cache board. The current battery status is indicated by the cpqDaAccelBattery variable.

Logical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array logical drive. The variable cpqDaLogDrvStatus indicates the current logical drive status.

Spare Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array spare drive. The variable cpqDaSpareStatus indicates the current spare drive status. The variable cpqDaSpareBusNumber indicates the SCSI bus number associated with this drive.

Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. The variable cpqDaPhyDrvBusNumber indicates the SCSI bus number associated with this drive.

Physical Drive Threshold Passed. This trap signifies that the agent has detected a factory threshold associated with one of the physical drive objects on a drive array has been exceeded. The variable cpqDaPhyDrvBusNumber indicates the SCSI bus number associated with the drive.

Accelerator Board Status Change. This trap signifies that the Insight Agent has detected a change in the cpqDaAccelStatus of array accelerator cache. The current status is represented by the variable cpqDaAccelStatus.

Accelerator Board Bad Data. This trap signifies that the agent has detected an array accelerator cache board that has lost battery power. If data was being stored in the accelerator memory when the server lost power, that data has been lost.

Accelerator Board Battery Failed. This trap signifies that the agent has detected a battery failure associated with the array accelerator cache board. The current battery status is indicated by the cpqDaAccelBattery variable.

Logical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array logical drive. The variable cpqDaLogDrvStatus indicates the current logical drive status.

Spare Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array spare drive. The variable cpqDaSpareStatus indicates the current spare drive status. The variable cpqDaSpareBusNumber indicates the SCSI bus number associated with this drive.

Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. The variable cpqDaPhyDrvBusNumber indicates the SCSI bus number associated with this drive.

Physical Drive Threshold Passed. This trap signifies that the agent has detected a factory threshold associated with one of the physical drive objects on a drive array has been exceeded. The variable cpqDaPhyDrvBusNumber indicates the SCSI bus number associated with the drive.

Accelerator Board Status Change. This trap signifies that the agent has detected a change in the cpqDaAccelStatus of an array accelerator cache board. The current status is represented by the variable cpqDaAccelStatus.

Accelerator Board Bad Data. This trap signifies that the agent has detected an array accelerator cache board that has lost battery power. If data was being stored in the accelerator memory when the server lost power, that data has been lost.

Accelerator Board Battery Failed. This trap signifies that the agent has detected a battery failure associated with the array accelerator cache board. The current battery status is indicated by the cpqDaAccelBattery variable.

Controller Status Change. This trap signifies that the agent has detected a change in the status of a drive array controller. The variable cpqDaCntlrBoardStatus indicates the current controller status. User Action: If the board status is generalFailure(3), the you may need to replace the controller. If the board status is cableProblem(4), check the cable connections between the controller and the storage system.

Controller Active. This trap signifies that the agent has detected that a backup array controller in a duplexed pair has switched over to the active role. The variable cpqDaCntlrSlot indicates the active controller slot and cpqDaCntlrPartnerSlot indicates the backup. User Action: Check the partner controller for problems. If this was the result of a user initiated switch over, no action is required.

Spare Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array spare drive. The variable cpqDaSpareStatus indicates the current spare drive status. User Action: If the spare drive status is failed, replace the drive.

Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. User Action: If the physical drive failed or predicting failure, replace the drive.

Physical Drive Threshold Passed. This trap signifies that the agent has detected a factory threshold associated with one of the physical drive objects on a drive array has been exceeded. User Action: If the physical drive is predicting failure, replace the drive.

Tape Library Status Change. This trap signifies that the agent has detected a change in the status of a tape library. The variable cpqDaTapeLibraryStatus indicates the current tape library status. The variable cpqDaTapeLibraryScsiTarget indicates the SCSI ID of the tape library. User Action: If the tape library is failed, check the tape library front panel.

Tape Library Door Status Change. This trap signifies that the agent has detected a change in the door status of a tape library. The variable cpqDaTapeLibraryDoorStatus indicates the current tape library door status. The variable cpqDaTapeLibraryScsiTarget indicates the the SCSI ID of the tape library. User Action: If the tape library door is open, close the tape library door.

Tape Drive Status Change. This trap signifies that the agent has detected a change in the status of a tape drive. The variable cpqDaTapeDrvStatus indicates the current tape status. The variable cpqDaTapeDrvScsiIdIndex indicates the the SCSI ID of the tape drive. User Action: If the tape is failed, check the tape and all SCSI connections.

Tape Drive Cleaning Required trap. The agent has detected a tape drive that needs to have a cleaning tape inserted and run. This will cause the tape drive heads to be cleaned.

Tape Drive Cleaning Tape Needs Replacing. The agent has detected that an autoloader tape unit has a cleaning tape that has been fully used and therefore needs to be replaced with a new cleaning tape.

Accelerator Board Status Change. This trap signifies that the agent has detected a change in the status of an array accelerator cache board. The current status is represented by the variable cpqDaAccelStatus. User Action: If the accelerator board status is permDisabled(5), you may need to replace the accelerator board.

Accelerator Board Bad Data. This trap signifies that the agent has detected an array accelerator cache board that has lost battery power. If data was being stored in the accelerator cache memory when the server lost power, that data has been lost. User Action: Verify that no data has been lost.

Accelerator Board Battery Failed. This trap signifies that the agent has detected a battery failure associated with the array accelerator cache board. User Action: Replace the Accelerator Cache Board.

Controller Status Change. This trap signifies that the agent has detected a change in the status of a drive array controller. The variable cpqDaCntlrBoardStatus indicates the current controller status. User Action: If the board status is generalFailure(3), you may need to replace the controller. If the board status is cableProblem(4), check the cable connections between the controller and the storage system.

Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. User Action: If the physical drive status is failed(3) or predictiveFailure(4), replace the drive.

Physical Drive Threshold Passed. This trap signifies that the agent has detected a factory threshold associated with one of the physical drive objects on a drive array has been exceeded. User Action: Replace the physical drive.

Tape Library Status Change. This trap signifies that the agent has detected a change in the status of a tape library. The variable cpqDaTapeLibraryStatus indicates the current tape library status. The variable cpqDaTapeLibraryScsiTarget indicates the SCSI ID of the tape library. User Action: If the tape library is failed, check the tape library front panel.

Tape Drive Status Change. This trap signifies that the agent has detected a change in the status of a tape drive. The variable cpqDaTapeDrvStatus indicates the current tape status. The variable cpqDaTapeDrvScsiIdIndex indicates the the SCSI ID of the tape drive. User Action: If the tape is failed, check the tape and all SCSI connections.

Controller Status Change. This trap signifies that the agent has detected a change in the status of a drive array controller. The variable cpqDaCntlrBoardStatus indicates the current controller status. User Action: If cpqDaCntlrBoardStatus is 'generalFailure(3)', you may need to reboot the server or replace the controller. After the system is rebooted, check the variable cpqDaCntlrLastLockupCode for the controllers last lockup code. If cpqDaCntlrBoardStatus is 'cableProblem(4)', check the cable connections between the controller and the storage system. If cpqDaCntlrBoardStatus is 'cacheModuleMissing(6)', the array controller is operating in an unsupported configuration and requires that a cache module be attached to the controller.

Logical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array logical drive. The variable cpqDaLogDrvStatus indicates the current logical drive status.

Spare Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array spare drive. The variable cpqDaSpareStatus indicates the current spare drive status. User Action: If the spare drive status is failed, replace the drive.

Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. User Action: If the physical drive status is failed(3) or predictiveFailure(4), replace the drive.

Physical Drive Threshold Passed. This trap signifies that the agent has detected a factory threshold associated with one of the physical drive objects on a drive array has been exceeded. User Action: Replace the physical drive.

Cache Module Board Status Change. This trap signifies that the agent has detected a change in the status of a cache module board. The current status is represented by the variable cpqDaAccelStatus. User Action: If cpqDaAccelStatus is 'permDisabled(5)', you may need to replace the cache module board. If cpqDaAccelStatus is 'cacheModFlashMemNotAttached(6)', install the flash memory.

Cache Module Board Bad Data. This trap signifies that the agent has detected a cache module board that has lost backup power. If data was being stored in the cache module memory when the server lost power, that data has been lost. The backup power source is indicated by cpqDaAccelBackupPowerSource. User Action: Verify that no data has been lost.

Cache Module Board Backup Power Source Failed. This trap signifies that the agent has detected a backup power source failure associated with the cache module board. The backup power source is indicated by cpqDaAccelBackupPowerSource. User Action: Replace the Backup Power Source.

Tape Library Status Change. This trap signifies that the agent has detected a change in the status of a tape library. The variable cpqDaTapeLibraryStatus indicates the current tape library status. The variable cpqDaTapeLibraryScsiTarget indicates the SCSI ID of the tape library. User Action: If cpqDaTapeLibraryStatus is 'failed(4)', check the tape library front panel.

Tape Library Door Status Change. This trap signifies that the agent has detected a change in the door status of a tape library. The variable cpqDaTapeLibraryDoorStatus indicates the current tape library door status. The variable cpqDaTapeLibraryScsiTarget indicates the the SCSI ID of the tape library. User Action: If cpqDaTapeLibraryDoorStatus is 'open(4)', close the tape library door.

Tape Drive Status Change. This trap signifies that the agent has detected a change in the status of a tape drive. The variable cpqDaTapeDrvStatus indicates the current tape status. The variable cpqDaTapeDrvScsiIdIndex indicates the the SCSI ID of the tape drive. User Action: If cpqDaTapeDrvStatus is 'failed(4)', check the tape and all SCSI connections.

Tape Drive Cleaning Required trap. The agent has detected a tape drive that needs to have a cleaning tape inserted and run. This will cause the tape drive heads to be cleaned.

Tape Drive Cleaning Tape Needs Replacing. The agent has detected that an autoloader tape unit has a cleaning tape that has been fully used and therefore needs to be replaced with a new cleaning tape.

Physical Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array physical drive. The variable cpaDaPhyDrvStatus indicates the current physical drive status. User Action: If cpaDaPhyDrvStatus is 'failed(3)', 'predictiveFailure(4)', 'ssdWearOut(8)', or 'notAuthenticated(9)', replace the drive.

Spare Drive Status Change. This trap signifies that the agent has detected a change in the status of a drive array spare drive. The variable cpqDaSpareStatus indicates the current spare drive status. User Action: If cpqDaSpareStatus is 'failed(3)', replace the drive.

Partner Controller Status Change. This trap signifies that the agent has detected a change in the status of a drive array partner controller. The variable cpqDaCntlrPartnerBoardStatus indicates the current partner controller status. The variable cpqDaCntlrSerialNumber indicates the controllers serial number and cpqDaCntlrPartnerSerialNumber indicates the partner controllers serial number. User Action: Check the partner controller for problems. If lost communication with the partner controller is the result of a user initiated action, no remedial action is required.

Solid State Disk Wear Status Change. This trap signifies that the agent has detected a change in the SSD wear status of a drive array physical drive. The variable cpqDaPhyDrvSSDWearStatus indicates the current SSD wear status. User Action: If cpqDaPhyDrvSSDWearStatus is 'ssdWearOut(6)', replace the drive.