HP StorageWorks Virtual Array 7000 Family User and Service Guide (January 2005)
Table Of Contents
- Warranty Information
- Product Overview
- System Configurations
- Lowest Entry Point, Non-HA Minimum Configuration (VA 7100 only)
- Lowest Entry Point, Non-HA Minimum Configuration (VA 7410)
- Entry Level Non-Cluster With Path Redundancy (All VA arrays)
- Entry Level Cluster with Path Redundancy High Availability (VA 7410)
- Midrange Non-Cluster (All VA arrays)
- Midrange Non-Cluster (VA 7410)
- Midrange Non-Cluster with Full Storage Path Redundancy (All VA Arrays)
- Typical Non-Clustered with Path Redundancy (VA 7410)
- Typical Clustered Configuration (All VA models)
- Typical Clustered Configuration (VA 7410)
- HP-UX MC Service Guard or Windows 2000 Cluster (All VA arrays)
- Highly Redundant Cluster (VA 7410)
- Typical Highly Redundant Cluster (All VA models)
- Typical Highly Redundant Cluster (VA 7410)
- Troubleshooting
- Servicing & Upgrading
- Specifications & Regulatory Statements

86 Troubleshooting
Array Controller Logs
Types of Array Controller Logs
There are two types of array controller logs:
■ Controller logs. Controller logs contain events relating to the operation of
all FRUs in the array, obtained from the controller during the operation of
the array. The CommandView SDM logging routine polls the array every
15 minutes to retrieve and store the log entries in special controller log files.
Each log entry has a decimal event number and an event name. A list of
the “Controller Log Event Code Descriptions” is available at:
http://www.hp.com/support/va7100
http://www.hp.com/support/va7400
http://www.hp.com/support/va7410
http://www.hp.com/support/va7110
■ Usage logs. Entries for the usage log are created using the output of the
armdsp -a command. The CommandView SDM logging routine runs
the command and stores its output as entries in the usage log file. This
occurs every 24 hours by default, but can be changed to a setting from 1 to
100 hours.
Location of Array Controller Logs
Array controller logs are stored in three locations:
■ NVSDRAM. 256 kilobytes of NVSDRAM memory is reserved to hold one
thousand log entries.
■ Image Disks. The logs in NVSDRAM are mirrored and backed up by the
image disks.
■ Host OS directory. Polls the controller every 10 minutes and updates the
following host directory, located on the host internal disk:
<command view home dir>/sanmgr/cmdview/server/logs