HP StorageWorks SAN Virtualization Services Platform 3.0 release notes (5697-0404, April 2010)

DPM issues
Replacing a DPM in a DPM group when upgrading from SVSP 2.x to SVSP 3.0
When upgrading from SVSP 2.x to SVSP 3.0, 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.
5. To redistribute the virtual disk between the two DPMs in the group, do the following:
a. Go to the DPM groups display and select this DPM group.
b. Select the Virtual Disks tab in the lower pane.
c. Right-click on every virtual disk that needs to be moved back to the new DPM.
d. Select Manage > Manage Data Path Module/SVSP > Change Primary/Secondary Data Path
Module/SVSP.
e. After changing the primary DPM for all required virtual disks, go to the upper pane and
right-click on the DPM group.
f. Select Manage > Redistribute.
Enabling Ethernet port without a cable results in diagnostic message on console
Enabling an Ethernet port on a DPM that is not physically connected causes a diagnostic message to
be printed to the serial console. This message can be ignored. This issue will be fixed in a future
release.
A DPM upgrade reverts to SNMP host name setup
Upgrading a DPM triggers the loss of the host name information configured for SNMP. After a DPM
upgrade, SNMP traps are generated with the default IP address (127.0.1.1), instead of the actual
address for the DPM. Performing a modify chassis name xxx command (re-assigning the same
chassis name) after the upgrade fixes the configuration. This issue will be fixed in a future release.
DPM fails with No Bootable Device error
Occasionally when a DPM is rebooted, the message No Bootable Device is displayed on the
serial console and the DPM will not boot. This is related to the internal flash disk of the DPM and a
workaround is power-cycling the DPM. Sometimes several power-cycles may be required. This is
believed to be a low probability occurrence. This issue is under investigation.
SAN Virtualization Services Platform 3.0 release notes 19