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
3. Click Device Manager. In the right pane, right-click Disk Drives, and select Scan for hardware
changes.
4. After the screen stops refreshing, open the VSM GUI and navigate to Entities > Back End LUs >
Rescan Devices. The added LUs appear in the GUI under the list of back-end LUs.
LUNs must have a preferred path/controller
VSM does not support EVA LUNs that are configured in No Preference mode. They must be preferred
to Path A or B. If No Preference LUNs are presented to the VSM server, they will not display in the
GUI, and are therefore not manageable by the VSM. To resolve this issue:
1. Using HP Command View EVA or MSA management interface, unpresent the No Preference
LUNs.
2. Perform a rescan of the hardware with the VSM GUI.
a. Log in to the VSM server, right-click on the My Computer icon, and select Manage.
b. Click Device Manager. In the right pane, right-click Disk Drives, and select Scan for hardware
changes.
3. Ensure the LUNs are configured in the correct operation mode (Controller A failover/failback or
Controller B failover/failback) and present the LUNs again.
4. Perform a rescan as described in step 2.
Import some HP and IBM back-end LUs only to designated pools
HP HSG-80 and IBM FAStT 200/500 LUNs should be imported-in-place only to pools designated for
LUN import, as no new volumes may be created from these pools. Data must be migrated to another
pool that is not designated for LUN import.
NOTE: These LUN import pools only need to have 1 GB of capacity and may be reused after
detaching the previously imported LUN. Ensure the pool has more than 5% free space before starting
a migration. See the “Working with back-end LUs” chapter in the HP StorageWorks SAN Virtualization
Services Platform Manager User Guide for more details.
Asynchronous mirrors and jobs do not fail when the source site is unavailable
Asynchronous mirror groups and jobs on the destination system do not fail when the source system is
down. It is expected VSM behavior that a job stays in a Normal state when the source site is down.
Accessing VSM may require Java Web Services cleanup
It may be necessary that Java Web Services be run (using Start > Run > Javaws) in order to access
VSM through Internet Explorer or Mozilla. Delete all entries in the windows. (This is required when a
remote client cannot be opened.) Some of the files may be locked by another user or application (like
Remote Desktop), or you need to delete these sessions before running Java Web Services.
IPv6 support limitations
The following are limitations with IPv6 support:
• When changing the iSCSI connections from IPv4 to IPv6 (or from IPv6 to IPv4) between domains,
the favorite targets are not updated with new addresses. To update to the new addresses, delete
the favorite targets and then add them again.
• Communications between VSM servers and the web server (running on the VSM server) and the
CORBA layer is still based on IPv4 addresses. In addition, the SaSnap utility needs an IPv4 address
to fetch the data from a remote VSM server. Consequently, each VSM server must have at least
one IPv4 address, but may have IPv6 addresses as well.
Issues and workarounds 17