Array Accelerator 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 Array Accelerator
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.
Parsed from file CPQFCA2.MIB.txt
Company: None
Module: CPQFCA-MIB
Array Accelerator 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 Array Accelerator
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.
Parsed from file CPQFCA-MIB.mib
Module: CPQFCA-MIB
cpqFcaAccelBadData OBJECT-TYPE SYNTAX INTEGER { other(1), none(2), possible(3) } ACCESS read-only STATUS mandatory DESCRIPTION "Array Accelerator 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 Array Accelerator 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." ::= { cpqFcaAccelEntry 4 }
Vendor: Compaq
Module: CPQFCA-MIB
[Automatically extracted from oidview.com]
cpqFcaAccelBadData OBJECT-TYPE SYNTAX INTEGER { other(1), none(2), possible(3) } ACCESS read-only STATUS mandatory DESCRIPTION "Array Accelerator 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 Array Accelerator 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." ::= { cpqFcaAccelEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.232.16.2.2.2.1.1 | cpqFcaAccelBoxIndex | 0 | 0 | External Array Controller Storage Box Index. The storage box index indicates which storage box this accelerator is in. |
| 1.3.6.1.4.1.232.16.2.2.2.1.2 | cpqFcaAccelBoxIoSlot | 0 | 0 | External Array Controller Box I/O Slot. This identifies the physical I/O slot where this accelerator resides in the storage box. |
| 1.3.6.1.4.1.232.16.2.2.2.1.3 | cpqFcaAccelStatus | 0 | 0 | Array Accelerator Board Status. This describes the status of the Array Accelerator Cache. The status can be: Other (1) Indicates th… |
| 1.3.6.1.4.1.232.16.2.2.2.1.5 | cpqFcaAccelErrCode | 0 | 0 | Array Accelerator Board Error Code. Use this to determine the status of the write cache operations. The status can be: Other (1) In… |
| 1.3.6.1.4.1.232.16.2.2.2.1.6 | cpqFcaAccelBatteryStatus | 0 | 0 | Array Accelerator Board Battery Status. This monitors the status of each battery pack on the board. The batteries can only recha… |
| 1.3.6.1.4.1.232.16.2.2.2.1.7 | cpqFcaAccelReadErrs | 0 | 0 | Array Accelerator Board Read Errors. This shows the total number of read memory parity errors that were detected while reading fr… |
| 1.3.6.1.4.1.232.16.2.2.2.1.8 | cpqFcaAccelWriteErrs | 0 | 0 | Array Accelerator Board Write Errors. This shows the total number of write memory parity errors that were detected while writing … |
| 1.3.6.1.4.1.232.16.2.2.2.1.9 | cpqFcaAccelCondition | 0 | 0 | The condition of the device. This value represents the overall condition of this array accelerator. |
| 1.3.6.1.4.1.232.16.2.2.2.1.10 | cpqFcaAccelWriteCache | 0 | 0 | Write Cache Memory. This shows the amount of memory allocated for the write cache in megabytes. Because data is kept in duplicat… |
| 1.3.6.1.4.1.232.16.2.2.2.1.11 | cpqFcaAccelReadCache | 0 | 0 | Read Cache Memory. This shows the amount of memory allocated for the read cache in megabytes. |
| 1.3.6.1.4.1.232.16.2.2.2.1.12 | cpqFcaAccelSerialNumber | 0 | 0 | Array Accelerator Board Serial Number. This value can be used to further identify the cache controller. If the serial number is … |
| 1.3.6.1.4.1.232.16.2.2.2.1.13 | cpqFcaAccelTotalMemory | 0 | 0 | Array Accelerator Total Memory. This value is the total amount of accelerator memory in megabytes, including both battery-backed … |
| 1.3.6.1.4.1.232.16.2.2.2.1.14 | cpqFcaAccelFailedBatteries | 0 | 0 | Array Accelerator Failed Batteries. This lists the location of accelerator failed batteries. Each octet present contains the posi… |