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

112 Servicing & Upgrading
Replacing the Controller in a Single-Controller Array
Replacing a controller in a single-controller array is complicated by the fact
that there is not a second controller to clone the firmware and maps. In this
situation there are two alternatives for recovering the firmware and maps. The
procedure used is determined by the nature of the controller failure.
Functioning Controller
If the original controller is functional, the following procedure is recommended:
1 Install the replacement controller with replacement DIMMs in the available
controller slot and let the controller auto clone the firmware. The amount of
memory on each controller must be the same.
2 Remove the original controller.
3 If desired, shutdown the array and move the new controller to the original
slot.
Failed Controller
If the controller had a solid failure that precludes autocloning, the following
procedure is recommended:
1 Determine what version of firmware was installed on the failed controller.
2 Replace the failed controller.
3 Power on the array. It will come up with a status of NO MAPs.
4 Update the controller firmware to the version that the array was running.
Do not update to a different version.
5 Verify the firmware update completed successfully.
6 Issue the
vfprecover command, and wait for the recovery to complete.
Note When a recover is performed, the controller must have the same
version of firmware as the original controller and the array must
have the same disks that were included in the configuration
when the maps were created.