HP StoreVirtual Storage Release Notes

Transcription

1 HP StoreVirtual Storage Release Notes HP Part Number: AX Published: July 2013 Edition: 11

2 Copyright 2009, 2013 Hewlett-Packard Development Company, L.P.

3 Version: LeftHand OS software version HP StoreVirtual Centralized Management Console version HP StoreVirtual LeftHand OS Command Line Interface (CLI) version HP StoreVirtual Failover Manager for VMware vsphere and HP StoreVirtual Failover Manager for Microsoft Hyper-V software version HP StoreVirtual Application Integration Solution Pack version HP StoreVirtual Application Aware Snapshot Manager version HP StoreVirtual DSM for Microsoft MPIO version (installs Microsoft certified DSM driver version ) HP StoreVirtual SRA Software for VMware vcenter SRM 5.0.1/5.1 version NOTE: SRA for VMware SRM 4.1 is no longer supported. If you upgrade to 10.0 or later, you must upgrade to SRA for VMware SRM or 5.1. HP StoreVirtual Recovery Manager HP LeftHand SNMP MIBs Updated software components in this release LeftHand OS software HP StoreVirtual Centralized Management Console HP StoreVirtual LeftHand OS Command Line Interface HP StoreVirtual Application Integration Solution Pack HP StoreVirtual Application Aware Snapshot Manager HP StoreVirtual SRA Software for VMware vcenter SRM Supported upgrade paths Description Direct upgrades to version 10.5 can be performed from the following released versions: Version 10.0 Version 9.5 Version 9.0 If you are upgrading to version 10.5 from version 8.x (8.5, 8.1), Online Upgrades will first upgrade to version 9.5 and then upgrade to version These release notes provide information about upgrading to this release, and about enhancements and fixes in this release. These release notes are current as of the published date. Update recommendation HP recommends that all customers running version 10.0 or earlier upgrade to version Supersedes Version 10.5 supersedes versions 10.0, 9.5, 9.0, 8.5, and 8.1. Updated software components in this release 3

4 Platforms supported for this release Languages HP StoreVirtual 4530 HP StoreVirtual 4630 HP StoreVirtual 4730 HP StoreVirtual 4730 FC HP StoreVirtual 4130 HP StoreVirtual 4330 HP StoreVirtual 4330 FC HP P4900 G2 HP P4800 G2 HP StoreVirtual VSA for VMware vsphere HP StoreVirtual VSA for Microsoft Hyper-V HP P4500 G2 HP P4300 G2 HP P4000 VSA Version 10.5 software supports the following languages: English Simplified Chinese Japanese Korean Spanish NOTE: The Configuration Interface and the on-system CLI are not localized. Changes made in version 10.5 may not be fully localized. However, they will be fully localized in the next major release. The version 10.5 documentation is published in English only. Enhancements The 10.5 release supports the rebranding to HP StoreVirtual Storage and the release of the HP StoreVirtual 4530, the HP StoreVirtual 4630, the HP StoreVirtual 4730, and the HP StoreVirtual 4730 FC. The 10.5 release includes the enhancements contained in the 10.0 release. A description of the 10.0 enhancements can be found in the version 10.0 release notes ( bc/docs/support/supportmanual/c /c pdf). Rebranding to HP StoreVirtual Storage and LeftHand OS Over the next year HP is transitioning to new product naming in our product, documentation, and solution materials. HP StoreVirtual Storage is the new name for the LeftHand P4000 product family and LeftHand OS is the new name for the SAN/iQ operating system. Fixes Version 10.5 includes the 9.5 patch set fixes, which can be found in the version 10.0 release notes ( 4 Platforms supported for this release

5 The following issues were fixed in the version 10.5 software: After upgrading to 10.0, storage system login failed due to a corrupted password file. In 10.0, the password file format was changed to support Active Directory and after the 10.0 upgrade, the older file format may still be used. The fix ensures that when upgrading from 9.x to 10.5, the password file format is changed to the newer file format. If you experienced this issue upgrading to 10.0, HP Support must manually fix the issue and you can then successfully upgrade to If a communication disruption with the global database occurs when an iscsi initiator is logging in to a volume, the operation to lock the volume for this connection may fail. (The volume lock guarantees that only one storage system services a volume at any time.) As a result, it may look like the volume is locked by another storage system, which could persist for an extended period of time. The LeftHand OS software now ensures a retry of global database operations after communication is restored to prevent volumes from becoming locked. If the VSA for Hyper-V configuration is running version 9.5 or later, only disk 1 can be used if you are using physical disk pass-thru on any Dell server (multiple VHDs can be used). This issue is resolved with an updated Linux kernel, which will be included in Patch This patch is scheduled for release shortly after the release of Resolving this issue requires upgrading to the 10.5 VSA and installing patch However, you should not upgrade to the 10.5 VSA until patch is available. When an upgrade reboots a storage system, the iscsi sessions are typically restored immediately to other storage systems. However, when the SAN is being accessed by highly sensitive applications, these applications may occasionally experience interruption in volume access. This is due to the iscsi sessions being rebalanced for multiple volumes in quick succession after the upgraded storage system is back online. To resolve this issue, the timing of the iscsi session rebalancer was changed so that the initial rebalance does not occur until 30 minutes after the upgrade or reboot of the storage system and volumes are rebalanced in 5 minute intervals. After upgrading to the 10.0 Application Aware Snapshot Manager, creating application managed snapshots of VMware volumes caused vcenter CPU utilization to reach 100%. This issue is fixed in The version 10.0 CLI command getperformancestats failed when a Failover Manager was added to a version 9.5 or 10.0 management group. The fix to the CLI code in version 10.5 prevents this failure. A memory leak that could cause volume unavailability is fixed in version A security vulnerability in the version 10.0 SANIQ_CIM_SERVER that uses an untrusted path to the binary was reported while building a Windows 2012 Server. The vulnerability is fixed in version The customer support ID field in the CMC was limited to 8 characters, which was not enough characters to accommodate the Service Agreement ID. The field length has been extended to 40 characters. In certain cases of sparse I/O workloads or network configurations using bridging or routing (common in Multi-Site SAN configurations), 40ms latency on writes may be reported by performance monitoring tools such as the CMC performance monitor, Windows perfmon, or VMware performance tools. This is most noticeable after upgrading from version 9.0 to 9.5. The TCP (Transmission Control Protocol) issue is resolved in LeftHand OS version Some Windows configurations using MS Clusters, Hyper-V volumes, and the associated SAN volumes experienced faster failover using the MS DSM rather than the DSM for MPIO. Some customer reports indicated that connectivity to the SAN volumes might be lost at times. Previous releases of the DSM for MPIO used nonstandard registry settings that affect how applications detect lost connections, retry accessing the data, and when the application decides to fail a connection and perform a failover. The DSM for MPIO installer now sets these registry values to Fixes 5

6 Prerequisites the current Windows recommended default value. The DSM for MPIO, in terms of failover rates, will now fail over connections at approximately the same rate that the MS DSM does. You cannot convert volumes from Network RAID 10 to Network RAID 5 as a way to save space when the cluster is full or nearly full. If you attempt this, it will cause volumes to hang and the only fix is to delete volumes. Information about how to best reclaim space in a cluster is presented in the Advanced tab of the Edit Volume window beginning with version Patch HP StoreVirtual Centralized Management Console For the CMC complete installation, 35 MB disk space and 50 MB RAM during runtime Minimum monitor resolution for the CMC is 1024 x 600 HP StoreVirtual Application Integration Solution Pack HP StoreVirtual Application Aware Snapshot Manager Windows Windows Server 2003 R2 SP2 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 VMware vsphere 4.x vsphere 5.x HP StoreVirtual DSM for Microsoft MPIO Windows Server 2003 R2 SP2 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 HP StoreVirtual LeftHand OS Command Line Interface (CLI) 10 MB available space Windows Server 2003 R2 SP2 Windows Server 2008 Windows Server 2008 R2 Windows XP SP2 Windows Vista Windows 7 Windows Server Prerequisites

7 HP StoreVirtual VSA on Windows Server 2012 The VSA installer will run on Windows Server Deploying a VSA for Hyper-V or a Failover Manager from a Windows Server 2012 system is supported. HP StoreVirtual Failover Manager for VMware vsphere VMware vsphere version 4.x or later Microsoft.NET 4.5 or later on the installer client 1 GB RAM Bridged connection through the VMware Console, or assigned network in VI Client 15 GB of disk space HP StoreVirtual Failover Manager for Microsoft Hyper-V Windows Server 2012 Windows Server 2008 versions 2008 R2 Standard 2008 R2 Enterprise 2008 R2 Datacenter 2008 R2 Server Core 2008 SP2, except for Core, which is not supported 15 GB available drive space on Windows server for the Failover Manager Hyper-V role installed and running At least 1 GB of memory reserved for the Failover Manager Two virtual CPUs with at least 2000 MHz reserved Version requirements To upgrade to version 10.5 LeftHand OS software, the storage systems must be at version or later. For versions 8.1 and 8.5, Online Upgrades will first upgrade to version 9.5 and then upgrade to version Upgrading the SAN Automatic Online Upgrades are supported in version 9.x or later. See the HP StoreVirtual Storage Upgrade Guide for more information. NOTE: Upgrading from 10.0 to 10.5 does not require a reboot of the system. Only the services are restarted. Patches and 10137, which contain a firmware update for the RAID controller on specific platforms, are automatically applied during the 10.5 upgrade. These patches are applied before the LeftHand OS 10.5 software is upgraded and they require a reboot. Depending on the size of your configuration, the patch installation could take a few minutes to a few hours to complete. Plan the upgrade accordingly. Upgrades and Manager Quorum Alarms In version 10.0, the notifications for optimum manager configuration in a management group move from the Best Practice Summary to Alarms. Therefore, when you upgrade to version 10.0 or later, you might receive alarms about any manager configurations that do not meet the recommended best practice. Version requirements 7

8 Compatibility/interoperability For a complete list of supported LeftHand OS software releases and application software compatibility, including for the Failover Manager, Microsoft Windows, and VMware Server, see the HP StoreVirtual 4000 Storage Compatibility Matrix, which is located at: Cross-version compatibility for Remote Copy, the CLI, and the Application Aware Snapshot Manager The LeftHand OS versions and versions supported for these features and applications are listed in Table 1 (page 8). Table 1 Cross-version compatibility LeftHand OS version 8.x CLI 8.x 9.x 10.x Remote Copy Application Aware Snapshot Manager 8.x Mixed LeftHand OS software versions in management groups HP StoreVirtual Storage management groups can accommodate storage systems that are running different versions of the LeftHand OS software. However, you can only add storage systems that are running a greater software version to a management group that is running an earlier software version. For example, you can add a storage system running the version 10.5 software to a management group currently running the version 9.0 software. You cannot add a storage system running 9.0 software to a management group that is running 10.5 software. If you partially upgrade a HP StoreVirtual Storage management group, the management group will continue to run on the earlier software version until the entire cluster is upgraded. 8 Compatibility/interoperability

9 Workarounds HP StoreVirtual LeftHand OS Command Line Interface Using the CLI to add DNS servers may not work properly The LeftHand OS has a limit of three DNS servers allowed when adding DNS servers using the CMC. Using the CLI command setdnsinfo may allow more than three servers to be added, or may add fewer than the requested number of servers. To avoid this issue, only add DNS servers using the CMC. The CLI command, creategroup, fails when using storage systems with different LeftHand OS versions software This issue is fixed in a future release. To resolve this issue, create the management group using the CMC. A disassociated Active Directory user can still execute CLI commands After a user is removed from an Active Directory group, the user can still successfully execute CLI commands. To resolve this issue, perform one of the following actions: Reboot the entire management group. Create and run a script containing five getnsminfo commands from five different authorized users on the storage system that the user is logged in to. This will flush the user out of the cache. You cannot use the CLI to delete an SNMP community string that has no IP mask You cannot delete a community string using the CLI command deletesnmpcommunitystring if the community string does not contain an IP mask. To resolve this issue, use one of the following options: Use the deletesnmpcommunitystring command and do not specify the IP Mask. Use the ClearSnmpSettings command instead. The CLI command setadinfo fails with an incorrect message when an incorrect base DN is given If the CLI command setadinfo fails, it may be because the Active Directory server or the base DN is incorrect or do not match. However, the error message that currently displays indicates that the "CLIQ credentials failed." If this error message displays, verify that the Active Directory server and/or the base DN is listed correctly. HP StoreVirtual Centralized Management Console Online Upgrade feature does not identify which order the patches will be applied in during a software upgrade When using the Online Upgrade feature in the CMC to upgrade the LeftHand OS software, the CMC does not identify which prerequisite patches will be installed, nor does it indicate in what order the patches will be installed (before or after the LeftHand OS software upgrade). Most of the firmware patches do require a reboot of the storage system and, depending on the size of the SAN configuration, the patch installation could take a few minutes to a few hours to complete. Plan the upgrade accordingly. A new management group does not have the 60 day evaluation license To resolve this issue, do one of the following: Delete the management group and recreate it to activate the 60 day evaluation period. Obtain license keys for the storage systems in the management group. Workarounds 9

10 The CMC does not show results if you try to convert volumes to Network RAID-5 to free up space in the cluster You cannot convert volumes from Network RAID 10 to Network RAID 5 as a way to save space. If you attempt this, it will cause volumes to hang and the only fix is to delete volumes. A user with valid Active Directory credentials cannot log into the CMC An Active Directory password may contain a special character that is not allowed in the CMC. The Active Directory validation will succeed in the CMC, however, you will not be able to log in using that password and will see the following error message: The character x is not allowed in passwords. Characters allowed in passwords in the CMC include the # $ % ^ & * Characters not allowed in passwords in the CMC include the following: :. / To resolve this issue, change the Active Directory password to contain only supported characters. HP recommends making this change before upgrading. User name character length requirement changed in version 10.0 Beginning with version 10.0, user names can be 3 to 30 characters in length. Previously, the maximum length was 40 characters. When upgrading to version 10.0 or later, if there are any user names longer than 30 characters, you will be prompted to stop the upgrade and change the user names before continuing. Export Events fails when the management group name contains certain special characters When exporting events to a file, the default file name is the same as the management group name. If the management group name contains either an asterisk (*) or a question mark (?), the export will fail. To resolve this issue, delete the special character from the suggested file name. The CMC Performance Dashboard is unable to monitor statistics for Fibre Channel Boot from SAN volumes Instead of numbers, N/A is displayed. Statistics for non-boot volumes are shown correctly. HP StoreVirtual DSM for Microsoft MPIO HP StoreVirtual DSM for Microsoft MPIO driver info is not displayed under Storage controllers in the Windows Device Manager Beginning with release 10.0, the DSM for MPIO driver is listed under the System devices section of the Device Manager. In previous versions, the DSM for MPIO was listed under the Storage controllers section of the Device Manager. Changing the Fibre Channel load balancing policy for Microsoft MPIO fails and disables path verification If you try to change the Fibre Channel load balancing policy from Round Robin With Subset to Fail Over Only, the change will fail. Additionally, it will disable path verification. You must manually reset path verification on the LeftHand P4000 disk Multi-Path Disk Device Properties dialog box. On the MPIO tab, click Details. On the DSM Details dialog box, select Path Verify Enabled. Disks are reported as offline in the Windows Disk Manager after uninstalling the DSM for MPIO In very rare circumstances, after removing the DSM for MPIO and rebooting the server, some volumes may display as offline. To resolve this issue, open the Windows Disk Manager, right-click the offline disk and select Online Repeat for each offline disk. 10 Workarounds

11 Microsoft Windows Server 2012 NIC teaming is not supported for use with iscsi To use multiple interfaces for iscsi, remove iscsi-designated interfaces from NIC teams and use supported MPIO configurations instead. Upgrading to Windows Server 2012 from Windows 2008 R2 renders DSM for MPIO and disks inoperable After upgrading to Windows Server 2012 from Windows Server 2008 on a system with DSM for MPIO installed, the DSM for MPIO is no longer functional and the volumes no longer display in the Disk Manager. You must reinstall and configure the DSM for MPIO after the operating system upgrade. Notifications and alerts SNMP clients and multi-byte characters SNMP clients must be configured to use UTF-8 encoding to properly display multi-byte characters. The alarm does not clear when a DNS server is fixed or comes back online Failover Manager The following warning may display when the system attempts to send an alert: EID_GLOBAL_CONFIG_MISCONFIGURED: The ' ' configuration status is 'Misconfigured'. If DNS and the server are unavailable briefly, the configuration is deleted. When DNS and the server become available again, this message displays because the configuration no longer exists. You must reset the configuration to stop this warning message and begin receiving alerts again. Unable to upgrade a management group to 10.0 that is running a version 8.1 Failover Manager When using a version 10.0 CMC and logging into a Failover Manager running version 8.1, the following error message is displayed: HAL device is missing. If this error message displays, you will be unable to upgrade the management group that contains this Failover Manager. To resolve this issue: 1. Remove the 8.1 Failover Manager. 2. Upgrade the CMC version on the management group. 3. Add a 10.0 Failover Manager to the management group. HP StoreVirtual Failover Manager for Microsoft Hyper-V installer hangs on Windows Server 2012 When installing the Hyper-V Failover Manager on a server running Windows Server 2012, the installation hangs. To resolve this issue, you must install.net 3.5 before installing the Failover Manager. Normally the missing files will be downloaded from Windows Update, but if access to Windows Update is not possible, enabling.net Framework 3.5 will fail unless an alternate source for the missing files has been specified. If Windows Server 2012 is installed in Server Core installation mode, you must use the command line (DISM.exe) to install.net 3.5. If Windows Server 2012 is installed as a full installation (in Server with a GUI mode), you can use the command line or Windows Server Manager Add Roles and Features to install.net 3.5. NOTE: You will need to change the DVD drive specification. A degraded Failover Manager can cause management group outage due to manager timeouts If a Failover Manager becomes unresponsive and cannot participate in quorum, the management group cannot respond to commands. However, the management group does not recognize the problem with the Failover Manager, and the management group becomes unresponsive. This issue can be caused if the Failover Manager is installed on the HP StoreVirtual Storage that is in the same management group instead of on a different storage device. Installing the Failover Manager on the HP StoreVirtual Storage is not supported. Workarounds 11

12 Fibre Channel Windows 2008 and Windows 2008 R2 require hot fixes to avoid volume availability issues when using Fibre Channel Transient errors may cause issues whereby an MPIO disk device could incorrectly be removed from the host after a short duration Fibre Channel link failure. This can result in data unavailability issues and possibly data loss issues. To resolve these issues, perform the following steps: 1. Install the hotfix listed in HP recommends rebooting the server before installing Install the hotfix listed in There is also another hotfix available for Microsoft cluster services that can supersede KB This hotfix addresses an issue in Microsoft clusters where a cluster resource could unexpectedly end up in redirected state. This hotfix is not recommended unless you experience an issue similar to what is outlined in the article found at For a Fibre Channel volume, the Performance Monitor reports 0.0 for the first volume statistics when a second volume is created and mounted on the same server This happens because the path of first volume gets changed when the second volume is mounted, so the Performance Monitor displays 0.0 for the older path. To solve this issue, remove the older path and add the new path of the first volume to see the correct performance values. Fibre Channel boot from SAN with Citrix may experience intermittent failures HP recommends not using boot from SAN with Citrix in this release. HP-UX servers cannot see LeftHand OS Fibre Channel LUNs Fibre Channel on LeftHand OS does not work with HPUX and is not supported at this time. Windows Server 2012 Hyper-V cluster shows disk errors on the active node during scheduled application-managed snapshots when using Fibre Channel The snapshot process quiesces the volume, then takes the snapshot, then mounts the snapshot using Fibre Channel, then unmounts the snapshot. Unmounting the snapshot breaks the Fibre Channel connection, and this sometimes generates MPIO and disk errors in the Windows Event log. You can ignore these errors. The snapshot completed successfully. Hardware and platforms 12 Workarounds For the HP StoreVirtual 4630, the additional NICS that display for the management network are only usable when ports are added to the management network The CMC shows an additional two NICS available for the management network. To use these two NICs (BladeBoard3 and BladeBoard4) in the server profile, you must add ports and assign them to the desired management network using HP Virtual Connect Manager under Enclosure Information in the Onboard Administrator. In the HP StoreVirtual 4730, when two drives are unavailable and the hot spare is rebuilding, the Device status is not reported properly on the RAID Setup tab in the CMC The status remains at 0% estimating. However, you can see the updated RAID rebuilding status, with the percentage completed and estimated time remaining, on the storage system Hardware Information tab. Failed drive status in HP StoreVirtual 4730 shows as Hot spare down,off or removed When a drive is removed in an HP StoreVirtual 4730, that drive status is incorrectly reported as Hot spare down,off or removed. However, the hot spare drive status is either active or rebuilding against the failed drive at that point in time. The removed drive is the only drive that is off or removed.

13 Removing a volume from an ESX server may result in the inability to discover new volumes To resolve this issue, perform a manual reboot of the storage system that is holding the Virtual IP address for the storage cluster. When running certain reports, the HP StoreVirtual 4730 performance degrades for up to 15 seconds This issue applies to the following reports: Generate Platform Diagnostic Report in the storage system Diagnostics Export Support Bundle Generate HpADU logs using the Systems Management Homepage To avoid this issue, do not run the reports unless the storage system experiences issues with physical drives or controllers. If an Array diagnostic report is required, only generate a support bundle report at the storage system level instead of the management group level. NOTE: Generating the SIM ADU report could cause the server to go into Automatic Performance Protection mode and generate a store process overload event. When upgrading to 10 GbE for storage systems running LeftHand OS version 9.5 or later, the RAM must be installed When upgrading to 10 GbE on a P4000 G2 platform running LeftHand OS version 9.5 or later, ensure that you install the RAM as instructed in the HP StorageWorks P4000 G2 10 GbE SFP+ Hardware Installation Instructions. Without the RAM installed, there will not be sufficient memory for the 9.5 store to start. A P4900 G2 controller firmware mismatch event does not generate an SNMP trap If the P410 controllers in a P4900 G2 storage system have different firmware versions, the firmware version mismatch generates an event. However, that event does not generate an SNMP trap. This situation could occur if a controller is replaced in a storage system and the replacement controller is at a different firmware version. Emulex 10 GbE card offers a new port speed setting of 9 Gb with LeftHand OS 10.0 The Emulex 10 GbE card now supports a 9 Gb port speed setting with the P4800 G2. The 9 Gb port speed setting may display as an option for the 10 GbE card when used on other storage system models besides the P4800 G2. The 9 Gb port speed setting should only be used with the P4800 G2. When splitting the P4800 G2 10 GbE NICS into a custom configuration for iscsi and management, the TCP speed/duplex reports Unknown On P4800 G2 storage systems running the LeftHand OS software versions listed in the table, if the Ethernet ports are configured with a speed other than the supported speeds listed, the network controller Speed/Method and Duplex/Method are reported as Unknown when viewed on the TCP Status tab of the storage system Network category. LeftHand OS software version Patch Set 2 or greater or greater Supported NIC configurations 100 Mb, 9.9 Gb, 10 Gb 100 Mb, 1 Gb, 9 Gb, 9.9 Gb, 10 Gb Additionally, an event notification is received for "NIC Speed slow." This is a reporting issue only; it does not affect actual functionality or the bandwidth allocated to network ports. To resolve this issue, configure the network bandwidth of the P4800 G2 Ethernet ports to supported speeds. Workarounds 13

14 Undefined and Unknown values are showing for Usage Remaining and Wear Status of drives under SmartSSD Wear Gauge in System Management Homepage for P4900 G2 SSDs The System Management Homepage displays incorrect values for the SSD status. The correct status is viewable on the ADU. The CMC also reports the correct status in the following locations: The Hardware Information report in the storage system Diagnostics category The Disk Setup tab in the storage system Storage category An event is also generated with the SSD status. The CMC reports a drive status as Active and Normal, but the Drive Status is degraded in ilo The ilo reports the HDD status as Degraded, but the CMC shows the drive as Active on the Storage category Disk Setup tab. The Hardware Information report shows the drive status as Normal and in the Diagnostics tests, the Disk Smart Health test passes. This issue is due to failed communication with the drive carrier. The ADU and ilo logs show warning message Authentication on this drive carrier failed due to a communication error. This may not be an authentic HP carrier. I/O operations to the device will not be affected, but the Smart Array controller will not control the LEDs to this device." However the problem was not communicated to the CMC. The raw capacity and usable disk space are reported in different units of measurement for an HP StoreVirtual storage system Due to the different units of measurement between Terabytes (TB) and Tebibytes (TiB), the raw capacity reported in an HP StoreVirtual storage system may appear to be lower than expected. One TB of data is 10^12 bytes where a TiB is 2^40 bytes, a difference of approximately 100 GB. The CMC reports values in TiB and HDD manufacturers typically report their size in TB. For example, a 3 TB HDD would be reported as having a size of GB by the CMC. For an HP StoreVirtual 4330 storage system with 8 1 TB HDDs, a raw capacity of 7 TB would be expected when using RAID 5 (where one drive is used for data parity), but the CMC would report a raw capacity of GB. This is the expected behavior, and it is simply two different methods of representing the same number of bytes. Installation and upgrades No warning that 10.x upgrade does not complete when management group contains unsupported platforms If a management group contains a storage system that does not support an upgrade to 10.x and you attempt to upgrade the management group to 10.x, the upgrade will not complete. Further, there will not be a warning or message that the upgrade cannot complete. To resolve this issue, you must migrate the systems that cannot be upgraded to 10.x out of the management group. Supported systems are the P4x00 G2 and 4x30. During an online upgrade from 8.5 to 10.x with storage systems on different subnets, I/O stops for approximately 2 minutes No data is lost but I/O to the volume may stop long enough for applications to timeout. If a timeout occurs, the application must be restarted manually. If there is a critical application involved that cannot tolerate an interruption in service, then an upgrade requiring a double hop should be scheduled during a time when the application can be taken offline. The installation wizard for the Hyper-V VSA does not show the correct available virtual disk space When installing the Hyper-V VSA, if you enter the total available drive space reported in the wizard, the installation fails with the error that there is not enough space on the disk. The formula for calculating the available drive space is incorrect and will be fixed in a future release. To resolve this issue, create the disk using less than the total available space reported in the wizard. 14 Workarounds

15 Incorrect.NET version listed in User Guides The HP StoreVirtual Storage VSA Installation and Configuration Guide and the Failover Manager section in the HP StoreVirtual Storage User Guide incorrectly list Microsoft.NET 2.0 or later as the prerequisite for installing the VSA and the Failover Manager on VMware vsphere. The correct version is Microsoft.NET 4.5. Windows installers may have their VeriSign certificates show up as "un-verified When using a Windows installer for StoreVirtual products, you may see a message that the certificate could not be verified. To solve this issue, go to the following website for additional information and a solution: actp=search&viewlocale=en_us Proxy server with required credentials is not supported If you are using a proxy server that requires credentials to be entered, the Online Upgrades functionality in the CMC will not work. The CMC does not support proxy servers with required credentials. A CMC on a Windows 2008 Server is unable to automatically discover storage systems if the firewall is on Disable the Windows Firewall on the computer on which the CMC is installed. To ensure desired system settings are retained after upgrading from version 8.5, use Copy Configuration before upgrading Storage system settings are not retained after upgrading from version 8.5 to version In the case of storage systems in a management group, one storage system in the group serves as the source for the settings that are applied to all the storage systems being upgraded. Therefore, use the Copy Configuration function in a version 8.5 or earlier CMC to apply the desired settings to all the systems that will be upgraded. The storage system settings that may be retained after upgrading to version 10.0 include settings for the following features: Alerts, including Alert s SNMP general settings and traps Remote log files Blank windows appear when installing the CMC on an HP-UX 11 server If blank windows appear during an installation of the CMC and you are using the HP-UX Window Manager (SXM/CDE), check the default font. If it is white, change it to black and begin the installer again. The CMC install and uninstall wizards contain special characters such as question marks The following unsupported configurations may cause the CMC install and/or uninstall wizards to display special characters instead of the expected text: The system OS language is set to a different language than the system locale language (for example, the OS is set to Chinese and the system locale is set to Japanese). The system locale is set to an unsupported language, such as French. Workarounds 15

16 Upgrading the CMC using Online Upgrades on a 64-bit Red Hat Enterprise Linux 6.x server To upgrade the CMC using Online Upgrades on a 64-bit RHEL 6.x server, install the following two packages from 32-bit RHEL 6.x: glibc libstdc++ After installing these packages, try installing the CMC again. Upgrading the CMC from version 9.5 and earlier to version 10.5 not supported on 64 bit OpenJDK on RHEL When upgrading the CMC from version 9.5 or earlier to 10.5, the following error message is displayed: Not Supported OpenjDK 64-Bit Server VM on amd64 Linux not supported. If you are already running a CMC on RHEL with 64 bit OpenJDK, you may see other issues with the CMC. To resolve this issue, install Oracle Java version 1.6 or greater. The HP StoreVirtual Centralized Management Console is not upgraded when using Online Upgrades on an HPUX server To resolve this issue, contact HP Support. The CMC installation wizard shows special characters when the location is set to Korean on a Red Hat Enterprise Linux 6.1 server When using the CMC installer on a RedHat Linux 6.1 server and the location is set to Korea, Korean characters are not displayed correctly. Special characters are displayed instead. Online Upgrades proxy type is not documented If you are using a proxy server, the Online Upgrade feature in the CMC supports HTTP, FTP and SOCKS proxy servers. You must enter the port number of the proxy server. The following ports are the default, or are commonly used for these proxy servers. Update the proxy details on the Preferences Upgrades window. Proxy type FTP SOCKS HTTP Proxy port , NOTE: HTTP proxy server may not work properly due to certain issues. This issue will be fixed in 10.5 Patch Set 01. Clicking "View Notifications" causes the CMC to become unresponsive while downloading the upgrade files via Online Upgrades If you close the View Notifications window while the upgrade files are downloading, and then you attempt to open the View Notifications window again, the CMC stops responding. After all the upgrade files finish downloading, the CMC becomes responsive again. The "Exchange storage system" and "Swap storage system" options are labeled with the same localized text in the Japanese version of the CMC This issue will be corrected in a future release. 16 Workarounds

17 The current Japanese translation gives a wrong meaning for the word Complete in the CMC Installation Wizard. This issue will be corrected in a future release. On Windows 2008 Server, if proxy is configured, the VSA installer cannot connect to the ESX Server If proxy settings are configured on the Windows 2008 Server on which you are attempting to run the VSA installer, the installer is unable to connect to the ESX Server. Before running the VSA installer, you must disable any proxy settings on the Windows 2008 Server. iscsi CHAP name in multi-byte characters requires the server to be configured with the IQN name You must create the server first and then edit that server to add the CHAP name: 1. Create a new server and select CHAP not required, and enter the IQN. 2. Next, select CHAP required and enter the CHAP information. 3. Click OK. The server is created with both CHAP and the IQN information. You can also edit an existing server to add the IQN if necessary: 1. Log off the target in the iscsi initiator. 2. In the CMC, navigate to the server. Right-click and select Edit Server. 3. In the Authentication section, select CHAP not required and enter the IQN in the Initiator Node Name field. 4. Select CHAP required and click OK. 5. Reconnect the volume in the iscsi initiator. iscsi sessions fail if server configuration is changed Due to a code enhancement, if any of the following items for the iscsi server configuration are changed, all server connections will be disconnected: iscsi initiator node name CHAP required or not required CHAP name, target secret, and initiator secret (if CHAP is required) This change ensures that the connections be re-established as soon as changes are implemented. Workarounds 17

18 Networking In rare situations, creating a bond may result in an event notice Due to timing issues in the software, after you create a new bond, the event notice NIC Motherboard:Port2=down may appear. You can safely ignore this event. To verify that the bond was created correctly, check the status of the bond by navigating to the storage system Network category and select the TCP/IP tab. HP StoreVirtual Recovery Manager Remote Copy Snapshots The CLI must be installed on the same system where the HP StoreVirtual Recovery Manager is installed for auto-mount policy-related commands to work properly To use related CLI commands, ensure that the CLI is installed on the same system where the Recovery Manager is installed. The Auto-Mount Policy window in the Recovery Manager does not indicate if the policy is added for a volume set The Recovery Manager can only provide volume set information on snapshots, not volumes. The Windows Application Event log continuously fills with error messages if the auto-mount service failed to mount a snapshot when the server is not found in the management group 1. In the Recovery Manager, pause the Auto-Mount policy until the server is added to the management group. 2. In the CMC, add a server to the management group that contains the snapshot. 3. In the Recovery Manager, start the policy. The Recovery Manager documentation for versions 10.x does not list the current supported versions of LeftHand OS and Windows The Recovery Manager documentation (Online Help and Deployment Guide) was not updated for versions 10.x. Therefore, the "Supported version of Microsoft Windows Server" and "Supported versions of LeftHand OS" lists do not include Microsoft Windows Server 2012 Datacenter and LeftHand OS versions 10.x, respectively. However, all of these versions are supported with Recovery Manager. The Recovery Manager documentation will be updated in the next release of the Recovery Manager. While cross version Remote Copy is occurring from 10.0 to 8.5 management groups, if copying halts because the cluster is full, the CMC displays the "See Alarms Window" error message, although the 8.5 management group does not have the Alarms window The version 9.x and greater Alarms and Events feature is not compatible with pre-9.x versions of software. Review the Alarms window for version 9.x or later management groups. If you are operating in a mixed SAN environment with management groups earlier than version 9.x, also review the Alerts window. RDM volumes and application managed snapshot support Creating application-managed snapshots of volumes that are attached to VMware virtual machines (VM) as a Raw Device Mapping (RDM) in virtual compatibility mode do not result in snapshots on HP StoreVirtual Storage. When using HP StoreVirtual Application Aware Snapshot Manager to create a snapshot of a VMFS data store that contains VMs using RDM disk resources, VMware takes a snapshot of the RDMs and maintains changes to these RDMs in the same VMFS data store. 18 Workarounds

19 You can locate files representing the snapshot of a RDM by browsing to the VM s location on VMFS data store. RDMs in physical compatibility mode are not supported with HP StoreVirtual. Disable memory snapshots on VMware virtual machines to improve snapshot performance when creating application-managed snapshots To disable VMware memory snapshots, add a key to the Registry Editor: 1. Open the Registry Editor and go to the path HKLM\Software\HP\P4000\Client Settings\1.0. If this path does not exist, you can create it. 2. Create a string value called VMMemorySnapshot and set it to false (VMMemorySnapshot=false). Issue with using the CLI to create managed snapshots when typing the volume name incorrectly If a volume name contains a colon, and you use the CLI to create a managed snapshot and you type the volume name incorrectly, the managed snapshot is created. However, the snapshot may get created on a volume different than the volume name entered, or the volume name may be truncated at the colon. To prevent either issue, use volume names that do not include colons. Intermediate VMware snapshots are not deleted when a timeout error occurs The process of creating an application-managed snapshot for a VMware volume involves creating snapshots for all virtual machines on the volume, creating the LeftHand OS snapshot, and deleting the intermediate virtual machine snapshots. If a timeout error occurs when the snapshot is being created (this can occur if a virtual machine is busy), the snapshot will still be created, but the intermediate virtual machine snapshots will not be deleted. You can determine if this issue occurred by reviewing the event log. Error messages such as Failed to create application-managed snapshotor Failed to create snapshots for one or more VMs will appear. Also, the Application Aware Snapshot Manager will not indicate that snapshots were deleted. To resolve the issue, you must delete the intermediate snapshots manually. When creating an application-managed snapshot of a cluster shared volume, an error message displays on the passive server If you have a Hyper-V configuration with cluster shared volumes, you may see the following error when an application aware managed snapshot is taken on one of the cluster shared volumes. Cluster Shared Volume 'Volume3' ('CSV3') is no longer directly accessible from this cluster node. I/O access will be redirected to the storage device over the network through the node that owns the volume. This may result in degraded performance. If redirected access is turned on for this volume, please turn it off. If redirected access is turned off, please troubleshoot this node's connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished. The error indicates that the volume is no longer accessible, but the volume is in a passive state on that particular node (and active on the other node). The snapshot is taken successfully. You can ignore this message. The CLI command GETSERVERCAPABILITIES fails on Windows 2008 Server Core Microsoft does not support.net on Windows 2008 Server Core. With the release of version 9.5, which included.net, the Application Aware Snapshot Manager is no longer supported on Windows 2008 Server Core. The Application Aware Snapshot Manager documentation (online help and deployment guide) incorrectly list support for Windows 2008 Server Core. This information will be removed in a future release. Windows 2008 Server R2 Core is still supported with Application Aware Snapshot Manager. Workarounds 19

20 The Application Aware Snapshot Manager is causing VSS error messages on the Windows cluster server that does not own the volume If you have a failover cluster configuration using Windows Server 2012 servers and an application-managed snapshot is taken on a volume, the following error message may display in the Windows Application log on the cluster server that does not own the volume: Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x , Access is denied. This message can be ignored. The snapshot was take successfully on the cluster server where the volume resides. Scheduled application-managed snapshots fail intermittently if volumes have active I/O This issue occurs if there are cluster shared volumes in the configuration and the I/O load is set to 8K OLTP. The failures generate error messages indicating that the application-managed snapshot has failed due to a connection timing out or due to some other conflict. The error messages include the following examples: The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Completed with Warning: VSS Provider: Point in time snapshot is created. The system could not quiesce.' The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Failed: Another app-managed snapshot is in progress.' The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Failed: VSS operation timed out.' The snapshot schedule 'xxxx' status in cluster 'xxxx' is 'Failed': 'App-Managed SS Failed: Cannot get application server information: connection timed out'. If application-managed snapshots of Exchange/SQL data and log files will be taken, they must NOT reside on Cluster Shared Volumes (CSVs). Application-managed snapshots do not work on SMB file shares presented by a Windows Failover Cluster With Windows Server 2012, SQL Server is not quiesced when an application-managed snapshot is taken on an SMB file share that is presented by a Windows Failover Cluster. The snapshot appears as if it is a managed snapshot, but because SQL Server was not quiesced, it is not a true managed snapshot. Unable to create application-managed snapshots for a locally mounted LeftHand OS volume when the Application Aware Snapshot Manager is installed on a server that also has VMware vcenter Server installed Mount the LeftHand OS volume on a different server that is not running vcenter Server and perform managed snapshots there. 20 Workarounds

21 SRA SRA 10.5 on Fibre Channel protocol The 10.5 SRA for VMware SRM does not provide Fibre Channel support. It only supports iscsi mounted volumes. The VMware SRM 5.0 does not work properly with HP StoreVirtual SRA Software for VMware vcenter SRM version 10.0 and 10.5 SRA version 10.5 will only work with SRM versions and 5.1 SRA version 10.0 will only work with SRM versions and 5.1. SRA version 9.5 will only work with SRM versions 5.0 and 5.1. If you run the SRA version 10.5 or 10.0 with SRM 5.0, the Recovery operation will not work and the SRM services on the recovery site will stop working. There is no way to make the Recovery operation work with SRM 5.0; this is a known issue in SRM 5.0 and was fixed by VMware in SRM You must uninstall the SRM and SRA on both the protected and recovery sites, and then install the SRM version or 5.1 and the SRA version SRM 4.1 is no longer supported If you upgrade to LeftHand OS version 10.0 or later, you must upgrade the SRM version to or 5.1. VSA Upgrading a VSA for Hyper-V from version 9.5 to version 10.x is unsuccessful Notification of the upgrades says the upgrade completed successfully, but the software version still shows version 9.5. This issue occurs if you are upgrading a 32-bit 9.5 VSA to The 10.0 VSA only supports 64-bit. NOTE: Failover Managers can be 32-bit. When installing VSAs that use more than 8 TB of datastores, increase the VMFS heap size VMware says that the VMFS heap size must be increased to access more than 8TB of VMDKs in a VM. This means that a VSA that uses more than 8TB of datastores should have the heap size increased. The default heap size in ESXi/ESX 3.5/4.0 for VMFS-3 is set to 16 MB. This allows for a maximum of 4 TB of open virtual disk capacity on a single ESX host. The default heap size has been increased in ESXi/ESX 4.1 and ESXi 5.x to 80 MB, which allows for 8 TB of open virtual disk capacity on a single ESX host. NOTE: In ESXi/ESX 4.x and earlier releases, the maximum heap size is 128 MB. This allows a maximum of 32 TB of open storage. In ESXi 5.x, the maximum heap size is 256 MB. This allows a maximum of 25 TB of open storage. To adjust the value, perform the following steps: 1. Log in to vcenter Server or the ESXi/ESX host using VMware Infrastructure (VI) Client. If connecting to vcenter Server, select the ESXi/ESX host from the inventory. 2. Select the Configuration tab. 3. Click Advanced Settings. Workarounds 21