HP SAN Virtualization Services Platform 3.0.5 Release Notes (5697-1031, June 2011)

ManualsBrandsHP ManualsSoftwareHP SAN Virtualization Services Platform Hardware Bundle

Table Of Contents

HP StorageWorks SAN Virtualization Services

Platform 3.0.5 Release Notes

HP Part Number: 5697-1031

Published: June 2011

Edition: 13

Summary of content (24 pages)

PAGE 1
HP StorageWorks SAN Virtualization Services Platform 3.0.
PAGE 3
Description HP StorageWorks SAN Virtualization Services Platform (SVSP) is a hardware and software solution that enhances the storage capabilities of approved storage arrays. Using Virtualization Service Manager (VSM) software, redundant VSM servers and Data Path Modules (DPMs) map application server I/O to locations on storage systems. Versions HP SAN Virtualization Services Platform 3.0.5, which includes: • Virtualization Services Manager software version 1.2.583 supported by LSI HBA driver version 9.1.
PAGE 4
• Any DPM failure will cause a DPM reboot. Previously, some failures would not cause an expected reboot, and leave the DPM in an uncertain state, requiring a manual reboot. • Improvements were made to the resource recovery algorithms for synchronous mirrors to provide improved stability and better behavior under high-stress workloads. Previously, a high-stress workload could trigger a significant degradation in synchronous mirror write performance, as well as poor wire-level behavior.
PAGE 5
3. 4. In the “For product” field of the Step 2 area, enter DSM and click Go. A screen listing other multipath software for Windows is displayed. Click Windows MPIO DSM for SAN Virtualization Services Platform. The following auto-failover and recovery tools are not supported: • Cluster Extensions (CLX) • Disaster Tolerant Cluster Services (DTCS) • MetroCluster To obtain the IBM AIX MPIO ODM for SVSP: 1. Go to http://www.hp.com/go/svsp and click Support & Documents. 2.
PAGE 6
• DPM maximum number synchronous mirror groups: 128 per DPM group (512 with 4 DPM groups) • Defined maximum distances: ◦ Asynchronous mirrors are supported up to 150 ms one-way separation (iSCSI only), and minimum bandwidth set to 3 Mbps. ◦ Synchronous mirrors supports up to 0.5 ms one-way separation (Fibre Channel transport only).
PAGE 7
SVSP back-end capabilities and limitations • Back-end array capacity of the SVSP system: 2 PB • Total back-end target ports: 128 (32 arrays with 4 ports per array) • Maximum number of paths per back-end LU: 8 • Maximum number of back-end LUs: 1024 • Maximum number of back-end paths: 4096 • Largest back-end LUN: 2047 GB • Smallest back-end LUN: array dependent • Maximum number of back-end LUNs per back-side initiator/target pair: 254 (LUNs 1–254) • Maximum number of stripe set members: 16 C
PAGE 8
• To change the computer name of a VSM server, you must disconnect it from the SAN, delete it from the configuration in the VSM GUI, rename the server, and reboot. Once rebooted, connect it to the SAN. Do not change the computer name if only one VSM is connected to the SAN. • Do not initiate an iSCSI connection for a VSM server to itself. Loopback is not supported. • Do not establish an iSCSI connection between two VSM servers in the same domain.
PAGE 9
1. 2. 3. 4. 5. 6. 7. Halt the second I/O stream to the snapshot (initiated in step 7 above). Unpresent the snapshot to its host (presented in step 6 above). Delete the snapshot (created in step 5 above). Delete the PiT (created in step 4 above). Halt the first I/O stream to the virtual disk (initiated in step 3 above). Unpresent the virtual disk to its host (presented in step 2 above). Delete the virtual disk (created in step 1 above).
PAGE 10
• Before replacing a DPM, you must manually identify all virtual disks and synchronous mirror groups for which the removed DPM is the active DPM, and change their active DPM. • When performing remote asynchronous mirror split and merge operations, after the split, and before the merge operation, you need to perform a VSM failover in the destination domain. Afterwards, you can perform the merge operation. Otherwise, the operation fails.
PAGE 11
4. 5. Verify the correct exposure of the virtual disks in both DPMs. 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.
PAGE 12
• Windows only recognizes 254 LUNs with the HP DSM driver though the Windows operating system supports 255 LUNs (maximum). • Automatic failback of Microsoft Cluster Service resource groups does not occur when both the HBA cables of one node are pulled out and reinserted. OpenVMS support without async mirrors OpenVMS 8.3 is supported with the exception of asynchronous mirrors.
PAGE 13
Disabled Delete menu when virtual disk is member of synchronous mirror group The Delete menu of a virtual disk that is a member of a synchronous mirror may become disabled (grayed out). If this virtual disk was previously added to a synchronous mirror group that no longer exists, then do one of the following: • Fail over the active VSM to the passive VSM. • Start and stop the active VSM using the SVSP Monitor.
PAGE 14
Threshold limit message only sent once When a threshold limit is reached, a single event log message is generated, instead of a message being sent every five minutes. Restoring a VSM setup from a backup cannot have PiTs Restoring a VSM setup from a backup can be safely performed only if there are no PiTs in the system.
PAGE 15
MSA capacity can be reported in base 2 or base 10 The VSM reports capacity in base 2 (for example, 1 TB = 1024 GB). The MSA can report capacity in base 10 (1 TB = 1000 GB) or can be configured to report in base 2. The MSA setting can be changed from the management GUI or from the CLI: From the management GUI: 1. Log in to the MSA using the management IP address in the browser window. 2. Click on the storage controller in the config view on the left side of the screen. 3.
PAGE 16
ForceActive with VSM server in unknown state If the ForceActive utility is running and the VSM server enters an unknown state, stop the VSM GUI, stop the ForceActive utility, restart the VSM, and then run the utility again. Deletion of last DPM in a DPM group Do not delete the last DPM in a DPM group (even though it is enabled for recovery purposes).
PAGE 17
3. 4. Click Device Manager. In the right pane, right-click Disk Drives, and select Scan for hardware changes. 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.
PAGE 18
NOTE: All the above communications are confined to the SVSP domains. External communications (for example, the GUI and other SOAP clients connected to the web server) are done according to the site configuration (either through IPv4 or IPv6 addresses). • If an IPv6 address is added or deleted while VSM is running, the SVSP Monitor cannot detect this change without restarting the VSM application.
PAGE 19
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.
PAGE 20
of errors reported for that link in the port statistics. If there are errors, replace the SFPs and cable. The port can also be manually set to 4 Gb speed on the DPM. DPM NTP configuration does not work with Windows 2000 domain controllers The DPM only supports NTP servers that support network time protocol query (ntpq) and the full RFC-1305 specification. In particular, Windows 2000 only implements 'Simple NTP' and is not supported by the DPM as an NTP server.
PAGE 21
VS-ALUA'. An alterative workaround would be to reboot both DPMs after FF-DSM has been installed and the personality for the UDH has been changed. HP Command View SVSP issues HP Command View SVSP has reached end-of-life The HP Command View SVSP GUI has been discontinued. HP recommends that you use the HP Virtualization Services Manager (VSM) GUI with SVSP.
PAGE 22
Incorrect error message when creating 65th PiT on a virtual disk When creating the 65th PiT on a virtual disk using the VSM CLI, you receive an error message indicating A SCSI error in I/O to the switch. The correct error message should be the Virtual disk has too many PiTs. HP is working to resolve this issue. The ListSnapshots command fails to return data with too many PiTs The ListSnapshots command with a –PiT argument does not return data with 2048 PiTs.
PAGE 23
Error with DeleteVirtualDisk command when virtual disk LUN number is out of range When deleting a virtual disk with the DeleteVirtualDisk command, and the LUN number is out of range, you will receive a SCSI I/O error message. This is expected behavior. The CreateAsyncMirrorGroupEx command cannot be run in Linux At this time, the CreateAsyncMirrorGroupEx command cannot be run in Linux. HP is working to resolve this issue.
PAGE 24
Obtaining product documentation You can find related documents on the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals Under storage, select Storage Software and then select HP StorageWorks SAN Virtualization Services Platform under Storage Virtualization Software. For product white papers, browse to http://www.hp.com/go/svsp and click the White papers link.