HP StorageWorks controllers Configuring the HP StorageWorks controller

This topic describes how to make use of the SAN Volume Controller code, version 1.2.0, in all supported scenarios.

The SAN Volume Controller code, version 1.1.1, introduced support for the HP StorageWorks Controllers, however, this support was limited to a single fibre channel connection. In the SAN Volume Controller code, version 1.2.0, this has been enhanced to support up to 4 fibre channel connections per HP StorageWorks subsystem. The support for partitioned LUNs is restricted to a single fibre channel connection in the 1.2.0 code version.

Attention: Attention: Before making any changes to your system, consider backing up important data.

If you issue the HP StorageWorks command "SHOW UNITS", any units that are partitioned are shown. The following table shows an example.

Table 48. Determining partition usage
HSG80 "SHOW UNITS" LUN Uses Used by
D1 R50
D2 R52
D3 R53 (partition)
D4 R54
D5 DISK50000 (partition)
D6 D51
D7 DISK30300 (partition)
D8 DISK10000 (partition)
D9 R55

Here D3, D5, D7 and D8 are partitioned units.

Scenario 1

This scenario assumes that you have no partitioned units on any HP StorageWorks controllers.

If there are no partitions on any of the HP StorageWorks controllers that are or will be connected to the SAN Volume Controller, then simply ensuring that the SAN Volume Controller code, version 1.2.0, is installed on each of the SAN Volume Controller clusters is all that is necessary. Once this code level is present and running correctly, then additional fibre channel connections can be zoned (and physically connected).

Scenario 2

This scenario assumes that you are using HP StorageWorks controllers on the SAN Volume Controller code, version 1.1.1, with a single fibre channel attached or zoned in. If partitions are present on the HP StorageWorks controllers, then there are two options available:

Option 1: Migrate data from the partitioned units

Migrate data residing on partitioned units and then delete the partitioned units. Perform the following steps to migrate your data:

  1. Perform a concurrent code load to get the code to version 1.2.0.
  2. Migrate data residing on partitioned units. This can be done in two ways:
    1. Migrate all virtual disks, using the svctask migratevdisk, that are in groups that include at least one partitioned unit to groups that contain no partitioned units. You can use the svcinfo lsmdisk command and the "SHOW UNITS FULL" command to correlate which HP StorageWorks units correspond with which MDisks on the SAN Volume Controller by comparing the unit identifiers (UIDs).
    2. Or, ensure that the managed disks groups have enough unused space on the MDisks that correspond to unpartitioned units for a copy of all the data on MDisks that correspond to the partitioned units. Then, delete the MDisks using the svctask rmmdisk command, which may require the use of the force flag.
  3. Re-zone to take advantage of the extra ports on the HP StorageWorks controller.

Option 2: Retain partitioned units

Perform a concurrent code load to get the SAN Volume Controller code to version 1.2.0. Retain the partitioned units and continue using a single fibre channel attachment.

Note:Note: You must not zone in any additional fibre channel ports on the HP StorageWorks controller because MDisks based on partitioned units will be taken offline. If you have partitioned LUNs that are not allocated to unit numbers and you subsequently add these to your configuration, then these units must be online to the controller that has the zoned in fibre channel port. You can accomplish this by pressing the reset button on the other controller. This is only necessary for unmanaged MDisks.

Scenario 3

This scenario assumes that you have partitions present on a HP StorageWorks controller that is to be connected to the SAN Volume Controller already running version 1.2.0.

In this case, you must initially zone in a single fibre channel connection to one of the HP StorageWorks controllers, and ensure that all the units are online to this controller. You can accomplish this by pressing the reset button on the other controller. You can then choose from the two options shown in Scenario 2. You won't need to do the concurrent code load as the code is already at version 1.2.0.

(C) Copyright International Business Machines Corporation 2003, 2004