HP SAN Virtualization Services Platform 3.0.5 Release Notes (5697-1031, June 2011)
Table Of Contents
- HP StorageWorks SAN Virtualization Services Platform 3.0.5 Release Notes
- Description
- Versions
- Product models
- Fixes
- Prerequisites
- Installation instructions
- Host operating systems and multipath drivers
- Devices supported
- SVSP-supported storage arrays
- Capabilities and limitations
- SVSP system capabilities and limitations
- SVSP front-end capabilities and limitations
- SVSP back-end capabilities and limitations
- Configuration best practices
- Operational best practices
- Issues and workarounds
- Upgrade issues
- Upgrading with large back-end disks
- Upgrade order
- Replacing a DPM in a DPM group when upgrading from SVSP 2.x to SVSP 3.0.x
- Operating system issues
- Decreased DPM performance in VMware environment
- The Windows Server 2008 UAC prevents applications requiring admin privileges from working
- Windows offers to format newly discovered disks resulting in data loss
- Miscellaneous Windows issues
- OpenVMS support without async mirrors
- SMI-S provider can delete some setup virtual disks
- Servers running HP-UX 11.23 disconnect from SAN
- Setting the cluster bit for Serviceguard in Linux or HP-UX
- Capacity limits with thin provisioned volumes
- VSM issues
- Thin virtual disks must have read/write permission and cluster flag
- VSM GUI indicates passive VSM not ready for failover
- Disabled Delete menu when virtual disk is member of synchronous mirror group
- SVSP web server hang makes GUIs inaccessible
- WSRM configuration step needed on VSM v2 server
- Imported LUNs must be aligned to a 1 MB capacity
- Verify free space before concatenating thin virtual disk on thick virtual disk
- Manual failover of loaded system with VSM GUI causes a non-expected system state
- VSM GUI unable to remove all host presentations in one operation
- Threshold limit message only sent once
- Restoring a VSM setup from a backup cannot have PiTs
- Error 1618 during VSM installation
- Limit of 63 PiTs on thin virtual disk
- Front-end hosts not able to work with objects
- Export/import query does not work
- Cannot have same first 29 characters in sync mirror task names
- Cannot expand VDG without same DPM as the members
- VSM does not enforce 512 data movers
- Issue when exceeding 180 async mirror tasks
- MSA capacity can be reported in base 2 or base 10
- Error with Continuous Access license capacity when replicated differently
- HP XP array volumes show as failed after creation of storage pool
- Long boot time with large configurations
- Cannot write to file error when using an MSA22xx array
- ForceActive with VSM server in unknown state
- Deletion of last DPM in a DPM group
- Changing virtual disk or group DPM selection from two to one DPM is not allowed
- Windows fault when array unresponsive
- VSM must be enabled for "Reboot on fatal error"
- VSM server connection to the SAN
- New front-end LUNs require rescan
- New back-end LUNs require rescan
- LUNs must have a preferred path/controller
- Import some HP and IBM back-end LUs only to designated pools
- Asynchronous mirrors and jobs do not fail when the source site is unavailable
- Accessing VSM may require Java Web Services cleanup
- IPv6 support limitations
- PiT deletions after reaching threshold Guard level
- Read-only permissions are not supported in the VSM GUI
- Potential for I/O loss with synchronous mirrors due to active DPM failure
- DPM issues
- DPM ports stay present during a DPM reboot
- Failback operation does not work after DPM replacement
- Physically disconnecting a DPM port results in a high rate of invalid transmitted word port errors
- Changing back-end virtual disks to be write protected is not supported
- Enabling Ethernet port without a cable results in diagnostic message on console
- A DPM upgrade reverts to SNMP host name setup
- Change active switch command does not work with Sun Solaris hosts
- Rescan is required after deleting or unpresenting virtual disks
- Period of high back-end load after a DPM reboot when synchronous mirror virtual disks are used
- I/O errors/timeouts when performing failover on large numbers of synchronous mirror virtual disks
- DPM reboots when a host has two different host types or personalities on two different SVSP domains
- DPM ports connected to a 4 Gb Fibre Channel switch may sometimes auto-negotiate to 2 Gb speed
- DPM NTP configuration does not work with Windows 2000 domain controllers
- Initial GUI port statistics values are zero for an extended time
- Running show debug dump command does not work as expected
- Order of magnitude of Tx/Rx Kbytes not correct with show ports stats command
- The ‘%’ option of the show log command moves to the end of the file
- Additional DPM limitations
- HP Command View SVSP issues
- HP Command View SVSP has reached end-of-life
- VSM CLI issues
- The SelectVSMDomain command fails with certain operating systems
- Some VSM CLI commands cause the CLI application to stop
- No error message with PurgeVirtualDisks command
- Exception error using Solaris with no VSM CLI virtual disk
- Host not checked when creating snapclone group
- Error received with GetDpmInfo command when using –SyncGroup argument
- Incorrect error message displayed with CreateSnapshotWithLun command
- Incorrect error message when ExpandVirtualDisk command is missing argument
- Incorrect error message when creating 65th PiT on a virtual disk
- The ListSnapshots command fails to return data with too many PiTs
- The DeleteRemoteAsyncMirrorGroup command does not work in HP-UX
- The BreakAllRemoteAsyncMirrorTasks command does not work in HP-UX
- The ? wildcard character in HP-UX is not reliable
- The ResumeLocalAsyncMirrorTask command does not work in HP-UX the first time
- The ResumeLocalAsyncMirrorTask command gives error in HP-UX if already resumed
- Incorrect error message when ManageSnapcloneGroup command is missing the Opcode argument in HP-UX
- The CreateSnapcloneGroupEx command fails with HP-UX if the group is still building
- The CreateSnapshotWithLun command fails to get last PiT instance for Pit26 with HP-UX
- Do not use DeleteVirtualDisk command with LastInstance argument in HP-UX
- Error with DeleteVirtualDisk command when virtual disk LUN number is out of range
- The CreateAsyncMirrorGroupEx command cannot be run in Linux
- VSS hardware provider issues
- Documentation issues
- Obtaining product documentation
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.
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.
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 (reassigning the same
chassis name) after the upgrade fixes the configuration. This issue will be fixed in a future release.
Change active switch command does not work with Sun Solaris hosts
The change active switch command is an operation that you can initiate on the VSM to force
a virtual disk to become active on the other DPM. This is typically used in maintenance operations to
proactively failover virtual disks to one of the DPMs so that the other DPM can be serviced. When a
Solaris host is running I/O to a virtual disk and the command is applied on that virtual disk, the Solaris
host reactivates the virtual disk and the virtual disk does not become active on the other DPM.
Rescan is required after deleting or unpresenting virtual disks
Hosts may not automatically detect that a virtual disk has been deleted or unpresented. A rescan should
be performed on the host after any virtual disks to that host have been deleted or unpresented. This is
required before any new virtual disks, especially any with the same LUN as a deleted/unpresented
virtual disk, are presented to the host.
Period of high back-end load after a DPM reboot when synchronous mirror virtual disks are used
In a configuration with synchronous mirror virtual disks, there may be a period of higher than normal
load on the back-end storage arrays after a DPM reboot. This will vary depending on the capacity of
the synchronous mirror virtual disks and with the load and write patterns on those virtual disks before
the DPM reboot. To reduce performance impact on production activity, HP recommends that DPM
reboots (for example, during a DPM upgrade) be scheduled for off-hours or during a maintenance
window.
I/O errors/timeouts when performing failover on large numbers of synchronous mirror virtual disks
If there is a heavy load of I/O on a large number of synchronous mirror virtual disks and an event
occurs that requires a large number of virtual disks to be failed over at the same time (for example, a
reboot of a DPM), it is possible that I/O errors or timeouts may be returned to the hosts. HP recommends
that operations requiring a DPM reboot (for example, a DPM firmware upgrade), particularly in a
large environment, be scheduled for off-hours or during a maintenance window, or manually fail over
each synchronous mirror group, one at a time.
DPM reboots when a host has two different host types or personalities on two different SVSP domains
If a DPM is connected to two different SVSP domains, and a host is configured for a different host type
or personality on each of the VSM domains, the DPM may enter a continual reboot mode. A host with
two different host types or personalities is an incorrect configuration and is not supported.
DPM ports connected to a 4 Gb Fibre Channel switch may sometimes auto-negotiate to 2 Gb speed
In some cases, the DPM ports may negotiate to a slower speed than their capability. In these cases,
verify the SFPs in the DPM and switch are supported and that there is not an unusually high number
Issues and workarounds 19