HP Insight Management Agents - Manual (Page 67)

• Read Errors displays the total number of read memory parity errors that were detected
while reading from the Array Accelerator. If a memory parity error occurs, the mirrored
copy of data in the write cache can be accessed to obtain correct data.
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
the total does not match the system value, a parity error occurs. A bad memory chip, memory
corruption, or lack of memory refresh may cause memory parity errors.
• Write Errors displays the total number of write memory parity errors that were detected
while writing to the Array Accelerator.
Write parity errors occur when the system detects that information has not been transferred
to the Array Accelerator 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 value, a parity error occurs.
• Total Memory displays the total amount of accelerator memory in megabytes, including
both battery-backed and non battery-backed memory.
• Write Cache displays the amount of memory allocated for the write cache in megabytes.
The actual amount of usable memory is half the amount shown because data is kept in
duplicate (mirrored).
• Read Cache displays the memory allocated for the read cache in megabytes.
• Serial Number displays the serial number of the accelerator board. Use this value to further
identify the cache controller.
• Error Code displays the status of the cache operations. The status can be one of the following:
— None - Write cache operations are currently configured and enabled for at least one
logical drive. No write cache errors have occurred.
— Bad Configuration - Write cache operations are temporarily disabled. The Array
Accelerator board was configured for a different controller. This error could be caused
if boards were switched from one system to another. Rerun the EISA 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, rerunning EISA
Configuration will cause the data to be lost.
— Low Battery Power - Write cache operations are temporarily disabled due to insufficient
battery power. View the Battery Status object instance for more information.
— Disable Command Issued - 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 - 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. After the operation
that requires the resources has completed, this condition will clear and write cache
operations will resume.
— Board Not Connected - Write cache operations are temporarily disabled. The Array
Accelerator board has been configured but is not currently attached to the controller.
Check the alignment of the board and connections.
— Bad Mirror Data - Write cache operations have been permanently disabled. The Array
Accelerator 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.
Storage Agent 67