HP StorageWorks SAN Virtualization Services Platform 3.0.2 Release Notes (5697-0347, May 2010)

of the synchronous mirror group are failed over to the other DPM before disconnecting an active DPM

from the SAN.

DPM issues

Both DPMs crash when creating a sync mirror group on an inaccessible virtual disk

Both DPMs crash if a synchronous mirror virtual disk is created on a back-end LUN that is not accessible

to either DPM (but was accessible to the VSM). This is an incorrect configuration (zoning or LUN

presentation error) but the DPMs should not crash due to this misconfiguration. This issue will be fixed

in a future release.

Both DPMs crash when LUN ID changed for an existing back-end LU

Both DPMs crash if the LUN number for an existing back-end LUN is changed. This operation is

documented as not being allowed but the DPMs should not crash due to this misconfiguration. This

issue will be fixed in a future release.

SNMP set community CLI command does not function as expected

After setting the community to a new value, querying the DPM mib through snmputil still returns the

default community value. This issue will be fixed in a future release.

Changing the LUN number of back-end virtual disks is not supported

Changing the LUN number of back-end virtual disks can lead to data unavailability and causes the

DPMs to reboot. This issue will be fixed in a future release, although changing LUN numbers will still

not be supported.

Changing back-end virtual disks to be write protected is not supported

Changing back-end virtual disks to be write protected could lead to I/O errors and data unavailability,

and is therefore not supported.

Replacing a DPM in a DPM group when upgrading from SVSP 2.x to SVSP 3.0.x

When upgrading from SVSP 2.x to SVSP 3.0.x, an issue occurs when replacing a DPM in a DPM

group that was created in SVSP 2.x. This may also occur when trying to add a new DPM to the old

DPM group. The newly added DPM will not join the old DPM group. To recover from this issue, perform

the following steps:

1. Manually delete the old (partial) DPM group.

2. Verify the front-end HBA list is the same for both DPMs, their rank is the opposite, and they have

the same WWNN.

3. Manually create a new DPM group consisting of the two DPMs.

4. Verify the correct exposure of the virtual disks in both DPMs.