HP StoreVirtual 4000 Release Note

Notes HP Part Number: AX696-96235 Published: September 2012 Edition: 7

• Failover Manager ESX and Failover Manager Hyper-V software Version 9.5.00.1215 • HP P4000 Centralized Management Console Version 9.5.00.1215 • HP P4000 Command Line Interface (Cliq) Version 9.5.0.1050 • HP P4000 Application Integration Solution Pack Version 9.5.00.968 (was HP P4000 Windows Solution Pack) • HP P4000 Application Aware Snapshot Manager Version 9.5.0.996 (was VSS Provider) • HP P4000 DSM for MPIO Version 9.5.0.981 • SRA for VMware SRM 5 Version 9.5.0.615 • SRA for VMware SRM 1x/4x Version 9.5.00.1215 Updated software components in this release NOTE: New names for Version 9.5 software • The HP P4000 Windows Solution Pack is now the HP P4000 Application Integration Solution Pack. • The VSS Provider is now delivered as part of the Application Aware Snapshot Manager component of the Application Integration Solution Pack. • SAN/iQ software • HP P4000 Centralized Management Console • HP P4000 Command Line Interface • HP P4000 Application Integration Solution Pack HP P4000 Application Aware Snapshot Manager ◦ ◦ HP P4000 DSM for MPIO ◦ HP P4000 Storage Replication Adapter for VMware SRM Supported upgrade paths Direct upgrades to Version 9.5 can be performed from the following released versions: • Version 9.0 • Version 8.5 • Version 8.1 • Version 8.0 If you are upgrading from Version 7.0.01 SP1, the online upgrade automatically upgrades to Version 8.0 before upgrading to Version 9.5. Description 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 9.0 and earlier versions upgrade to Version 9.5. Updated software components in this release 3

Platforms supported for this release Upgrades to Version 9.5 software are available for the following platforms: • HP P4300 G2 • HP P4500 G2 • HP P4800 G2 • HP LeftHand P4300 • HP LeftHand P4500 • VSA for ESX and for Hyper-V • Failover Manager for ESX and for Hyper-V • NSM 2120 G2 • NSM 2060 G2 • NSM 2120 • DL 320s • DL 185 Languages Version 9.5 supports the following languages: • English • Simplified Chinese • Japanese • Korean • Spanish NOTE: The Configuration Interface and the on-system CLI are not localized. Announcing Microsoft Windows Server 2012 support with HP LeftHand SAN/iQ software version 10.0 (releasing in late Fall 2012) To use your HP P4000/StoreVirtual SAN Solutions on Windows Server 2012, you must upgrade your storage system to 10.0 first and then upgrade to Windows Server 2012. SAN/iQ software version 10.0 is the first version that will support Windows Server 2012 and will include the latest set of SAN/iQ features and performance enhancements. SAN/iQ 9.5 support for Windows Server 2012 will be delivered shortly after the SAN/iQ 10.0 release. Stay tuned for the general availability date for SAN/iQ software version 10.0. For more information, go to: http://www.hp.com/go/LeftHandDownloads Enhancements The 9.5 release is a comprehensive release that includes enhancements in the following areas: • Application managed snapshots for VMware ESX Server and Microsoft Hyper-V Server • SAN Status Home Page — the SAN Status home page is the new home page for the CMC and presents key information for all management groups in the storage environment in a single view. 4 Platforms supported for this release

CMC. Go from “zero” to a fully functional virtual SAN in just a few easy steps. Scriptable install tool allows ROBO customers to script install once and deploy VSA quickly at multiple remote locations. • Peer Motion data mobility with cluster swap — Cluster swap allows users to replace or upgrade P4000 clusters. Edit cluster menu guides decisions about adding, removing, or exchanging storage systems. Easily migrate data online between tiers. • Remote Copy performance improvements — Improvements to remote copy times, the time required to scan volumes, ability to support more frequent snapshots, reduction of RPOs for DR solutions. • Storage Replication Adapter for Vsphere Site Recovery Manager 5.x — Supports automated failback and is included on the HP P4000 Application Integration Solution Pack • Best Practice configuration wizards — Configuration wizards guide towards highest availability configurations: add Failover Manager for 2–node configuration, configure disk RAID 6 for single-node configurations, recommends volume replication when expanding clusters to more than one storage system Fixes Released patch sets and patches that are included in Version 9.5 software. Patch set 01 Includes the following fixes: • Online upgrade issues when attempting to install a patch as part of the 9.0 upgrades • Update to resolve specific language translations for specific languages Patch set 02 Upgrade to the Centralized Management Console (CMC) to version 9.0.01.0125 includes the following fixes: • Resolves an issue where the CMC is unable to discover a storage system due to a MAC address change • Added Cancel button in the upgrade dialogue box which gives an option to cancel the upgrade in progress • Improved recovery from failed or cancelled upgrades with better error messages. • The Performance Monitor in the CMC now displays correct values for network utilization statistics on 10 Gigabit Ethernet networks • Version 9.0 and greater VSA upgrades are no longer permitted for unsupported 32-bit ESX systems • Online upgrades pause all schedules for a management group while the CMC upgrades that management group. Schedules are restarted upon upgrade completion. Patch 10054-03: Upgrade improvements to support the CMC changes for online upgrades. Patch 20020 which includes the following fixes: • Resolves a condition affecting memory use by a SAN/iQ manager under heavy network traffic • Corrects the presentation of the queue depth statistics in the Performance Dashboard for storage systems connecting to VMware ESX initiators running 4.1 or later Fixes 5

non-English CMC when configuring the interface through the TCP/IP tab with DHCP or a static IP address • Resolves a situation where, under certain conditions, on reboots after an upgrade to 9.0, SAN/iQ 9.0 appears to detect and report an erroneous controller cache discard event long after the original condition has been addressed, corrected and no longer exists Patch set 03 Included in Patch Set 03 are the following fixes: • Address potential security issues in SAN/iQ 9.0 • Prevent SAN/iQ process restart due to invalid SCSI command from any iSCSI initiator • Increase the efficiency of volume/snapshot re-synchronization calculations when a storage system is restarted, or added to a cluster, or is replaced in a cluster • Update the location of a support log file so it gets rotated correctly and Log Utilization remains in normal range • Added a critical alarm, "The ’Log Partition’ status is ’Read Only’" that is displayed when the SAN/iQ log partition becomes read-only due to a previous hardware problem • The CMC, along with supporting patch 10054-04, now prevents an upgrade if the SAN/iQ log partition is in an unexpected state • Added a Warning alarm “The SAN/iQ memory requirements check status is ’Insufficient’ Required x GB” that is displayed when the storage server is offline because of insufficient memory • Allow upper case letters for IQN names • Suppress benign boot messages being displayed on the VGA console • CMC now correctly reports cluster usage when managing an 8.5 management group with a 9.0 CMC • CMC now connects to the management gateway/CIM server when accessing storage systems via a separate management network • Edit Management Group now shows out-of-date Remote Copy relationships, so you can disassociate them to clear an alarm about an old remote management group being down • Added new translated strings from the last patch set Patch 10059: Enables cross-version Remote Copy where storage systems running SAN/iQ 8.0, 8.1, and 8.5, that are not supported with SAN/iQ 9.0, get a SAN/iQ 9.0 manager, which allows them to be configured as remote management groups and to receive remote snapshots from a primary management group with storage systems running SAN/iQ 9.0. Patch set 04 Included in Patch Set 04 are the following fixes: • Large multi-terabyte volumes with small or sparsely filled snapshots now no longer experience degraded performance with Remote Copy • Large multi-site SAN clusters where Ethernet flow control is not configured now no longer experience degraded performance with SAN/iQ 9.0 • The Adaptive Load Balancing (ALB) bond configuration updelay parameter for both 1GbE and 10GbE has been changed to 30 seconds for more efficiency in failover situations • 9.0 SNMP now reports accurate storage system performance statistics for storageRaidStats OIDs in the Storage MIB • Allow special characters in SNMP community string, such as ~`!@$%^&*():;=+[]{}|,.<>? 6 Fixes

status message along with resolution steps to recover from this situation • Corrects the 9.0 CMC Performance Dashboard so that if the monitoring interval is set to minutes or hours using the Edit Monitoring Interval from the Tasks menu, it can subsequently be changed using the Edit Monitoring Interval • Corrects the 9.0 CMC Performance Dashboard error that displayed read throughput values as zero for volume sizes of 2TB or later • Corrects the error message displayed by the 9.0 CMC when connecting to storage systems running a higher version of SAN/iQ • Added a check to 9.0 CMC online upgrades for any existing hardware problems in a pre-9.0 storage system during the upgrade pre-qualification tests, and ensures that the hardware passes the required tests before proceeding with the upgrade. If a hardware problem is detected, the upgrade fails with an appropriate error message and can be retried after resolving the problem. • 9.0 CMC online upgrades now provide the ability to apply prerequisite patches to storage systems before upgrading to the appropriate SAN/iQ version • Corrected the 9.0 CLI makePrimary command to retain the thin provisioning attribute of the volume/snapshot being converted to primary • Corrected the 9.0 CLI commands getsnapshotinfo and getremotesnapshotinfo to execute correctly when used with the deletesnapshot command • Corrected the 9.0 CLI command getperformancestats to work correctly when there is a Failover Manager in the management group • The CLI recoverQuorum command now works successfully in the rare cases that it previously failed to restore quorum to the management group • Fixes a security vulnerability in the SAN/iQ management service logging • Fixes excessive benign messages in some log files to improve supportability • Improves supportability by archiving specific P4800 RAID controller log files as is done in other P4000 SAN platforms Prerequisites HP P4000 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 P4000 Application Integration Solution Pack • Microsoft iSCSI Software Initiator - Recommended: Version 2.08 (or later) • Application Aware Snapshot Manager (was VSS Provider) Windows ◦ Windows Server 2003 R2 SP2 ◦ Windows Server 2008 ◦ Windows Server 2008 R2 Prerequisites 7

◦ ESX Server 5.0 • HP DSM for MPIO Windows Server 2003 R2 SP2 ◦ ◦ Windows Server 2008 ◦ Windows Server 2008 R2 HP P4000 Command-line interface (Cliq) • 10 MB available space • Windows Server 2003 R2 SP2 • Windows Server 2008 • Windows Server 2008 R2 • Windows XP SP2 • Windows Vista • Windows 7 Failover Manager for VMware ESX Server • VMware ESX Server version 4.x or later • Microsoft .Net 2.0 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 Failover Manager for Microsoft Hyper-V Server • 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 • A single virtual CPU with at least 2000 MHz reserved Version requirements To upgrade to Version 9.5 SAN/iQ software, the storage systems must be at Version 7.0.01 SP1 or later. If the storage systems are at a lower version, please contact Customer Support for access to the interim upgrade files. Refer to “HP technical support” (page 16) for customer support contact information. 8 Version requirements

upgrades first to Version 8.0 and then to Version 9.5. Required version of the Microsoft iSCSI Software Initiator - version 2.08 (or later) Upgrading the SAN Release Versions 9.x have automatic online upgrades. To begin using the online upgrades feature, you must first install the Version 9.x CMC. You can download the latest CMC from www.hp.com/go/P4000downloads Install the CMC and begin using the online upgrades as described in the rest of this section. Upgrade planning Review the planning checklist to ensure you are prepared to upgrade your storage systems and SAN. Table 1 Upgrade planning checklist Information and Instructions Upgrade Task Use “Supported upgrade paths” (page 3) to determine if there is a direct upgrade path for your storage systems, or if Verify the software version you are currently running and the upgrade path to the new release software. you have to upgrade to an 8.x version before upgrading to Version 9.5. If you are running iSCSI load balancing, you must have a Virtual IP Address configured on each cluster. Are you running iSCSI load balancing? Verify that each cluster has a VIP configured. The SAN/iQ software upgrade will reboot the storage system. Therefore, for volumes to remain online during the upgrade Plan for volume access and the impact to iSCSI sessions that the upgrade will have. process, they must be Network RAID-5 or higher. Volumes that are Network RAID-0 should be disconnected (logged off) from the application server(s). Rebooting the storage system will cause all iSCSI sessions on that storage system to be terminated and recovered to one of the remaining storage systems in the cluster. Consequently, application IO to the volume may stop until the iSCSI session is recovered. Consider upgrading during off-peak time (if possible) to avoid application impact. The actual time to upgrade a storage system or a management group depends on the specific platform(s) and configuration. Schedule time for upgrade. Upgrade the components in the following order: Upgrading the CMC, the SAN/iQ software, and the Solution Pack components. 1. The CMC, including CLI, MIBs and FOM. 2. Any patches or other components as indicated during the Upgrade process, in the Install Action Required window. 3. The DSM for MPIO If you are running Version 7.x of the HP P4000 DSM for MPIO , the installer prompts you to first uninstall that version before installing the current version. 4. The SAN/iQ software. 5. The remaining Solution Pack components, as required. Plan to save the upgrade information. After the upgrade, a window opens that allows you to export the upgrade Keep log files and the support bundle information to a file. Also keep the Storage System Support Bundle. You will need these if you call Support. Performing the upgrade 1. Select Configuration Summary in the Navigation pane of the CMC. 2. Select the Upgrades tab. Upgrading the SAN 9

4. Upgrade the CMC. 5. When the CMC is upgraded and restarted, return to the Upgrades tab. Click Continue for each management group that shows Upgrades Available. For the P4000 CLI: 1. Ensure that you have Administrator privileges before beginning the upgrade. 2. Use the appropriate package installer that is downloaded from the Upgrades feature. Double-click the .exe to start the installation wizard. 3. Click Install. Using Advanced upgrades Using the Normal Upgrade Selection Mode, all patches available are applied to the storage system. Using the Advanced Upgrade Selection Mode allows you to apply individual patches to the current version of SAN/iQ software, or to upgrade to a specific software version that is not necessarily the latest version. If patches are available for the current version of SAN/iQ, and have not been applied, they will be listed in the Package Selection window when upgrading storage systems. To use Advanced upgrades 1. Click Help→Preferences. 2. On the Preferences window, select Upgrades. 3. On the pane, select Advanced for the Upgrade Selection Mode. 4. Click OK. Upgrading software in an offline environment Downloading files 1. Install the Version 9.5 CMC on a computer that can connect to the Internet outside of a firewall. 2. Start the CMC. 3. Select Configuration Summary and click the Upgrades tab. Click Start Download to download all the upgrade and patch files to the computer where the CMC is installed. 4. Click Help→Preferences→Upgrades. 5. Note the download directory. This is where all the upgrade files were downloaded. The default location in Microsoft Windows is Program Files→HP→P4000→UI→downloads. 6. Close the CMC. 7. Return the computer to your own network. 8. Copy the downloaded files to a network share location or to portable media, or use the CMC on that computer to upgrade your storage systems. If you do copy the files to a network location, any CMC you use to do upgrades must point to that network location to see the files. a. Click Help→Preferences→Upgrades. b. Browse to the network location where you copied the files. c. Click OK to close the Preferences window and continue with the upgrade. Upgrading using an offline directory The option to use local media is only available if the CMC can’t connect to the FTP server. 1. Start the CMC. 2. Select Configuration Summary and click the Upgrades tab. 3. Click Use Local Media. 4. Choose the network directory where you stored the files, and proceed with the upgrades. 10 Upgrading the SAN

Upgrade the Version 9.5 software components in the following order: 1. CMC 2. HP DSM for MPIO 3. SAN/iQ software 4. Application Aware Snapshot Manager (was VSS Provider) HP P4000 Application Integration Solution Pack compatibility with SAN/iQ software The P4000 Application Integration Solution Pack software is not forward compatible. If you upgrade your SAN/iQ software to Version 9.5, you must also upgrade the Solution Pack software components to Version 9.5. Upgrading the HP P4000 Application Integration Solution Pack 1. Ensure that you have Administrator privileges before beginning the upgrade. 2. Use the Solution Pack installer that is downloaded from the Upgrades feature. Double-click the .exe to start the installation wizard. 3. Click Install to open the menu of Solution Pack components. 4. Click the Solution Pack component you want to install. The installation wizard takes you through the installation process for the selected component. Upgrading the HP P4000 DSM for MPIO • If you are running a Version 7.x of the HP DSM for MPIO 1. Uninstall the previous version of the HP DSM for MPIO. 2. Reboot the server. 3. Download and install the latest version of the MS iSCSI Initiator. You must select the Microsoft MPIO Multipathing Support for iSCSI option when installing the Microsoft iSCSI Initiator. 4. Install the Version 9.x HP DSM for MPIO • If you are running Version 8.0 or 8.1 of the HP DSM for MPIO, use the Solution Pack for Microsoft Windows DVD to upgrade to Version 9.0. After upgrading to Version 9.0, use the new installer provided in the HP P4000 Application Integration Solution Pack DVD. Upgrading the Application Aware Snapshot Manager (was VSS Provider) 1. After the Application Aware Snapshot Manager is installed, a reminder window opens. This reminder states that you must open the Authentication Console to configure user names and passwords for management groups for the Application Aware Snapshot Manager to work properly with other backup applications. 2. Click Next to continue. 3. Click Finish on the final window to complete the wizard. 4. Click Menu on the installer window to open the installer main window. 5. If you have finished installing Solution Pack components, click Exit to close the installer. Upgrading the SAN 11

Table 2 Upgrades troubleshooting error messages Description Error Message This message appears if the upgrades XML file is missing or corrupted after it has already been downloaded. Download the upgrade XML file again. An error occurred while reading the upgrade configuration file. If the file was from a web connection, click Try Download Again, otherwise recreate your media image. The CMC cannot connect to the FTP site to check for upgrades, or FTP is connected but the vsftpd service is stopped. There was a problem connecting to the download site. Please check your Internet connection and click Check For Upgrades, or use local media by clicking Use Local Media. This message appears when the CMC cannot write to the downloads directory. Check the permissions on the directory and try again, or select a different directory. The CMC cannot write to the downloads directory. Select a different directory in Upgrade Preferences and click Try Download Again. The drive where the CMC is trying to write the files has <=2GB of space left. The download stops so that the drive does not fill up. There is insufficient space on the drive for the upgrade packages. Free up some space or use Upgrade Preferences to change the download directory. Then click Try Download Again. A file or files was corrupted during the download. The file(s) is automatically deleted, so they can re-download. We also allow you to proceed with upgrades in the event that the bad file is not one that they need. At least one file was corrupted when downloading from the FTP site. This is usually caused by a transient network error. Either wait a few minutes or fix the network connection, and then click Try Download Again. You can also try to install the files. If the installation requires one of the missing files, a message will inform you that the installation was not successful. Best practices Upgrading management groups with Remote Copy associations If you are upgrading management groups with Remote Copy associations, you should upgrade the remote management groups first. If you upgrade the primary group first, Remote Copy may stop working temporarily, until both the primary management group and the remote group have finished upgrading. Upgrade the primary site to 9.5 immediately after upgrading the remote site to 9.5. Refer to “How to verify management group version” (page 13). Cross-Version Remote Copy was introduced in Version 9.0, and allows storage systems running SAN/iQ Versions 8.0, 8.1, and 8.5, that are not supported with SAN/iQ 9.x, get a SAN/iQ 9.x manager that allows them to be configured as remote management groups to receive remote snapshots from a primary management group with storage systems running SAN/iQ 9.x. Increase the size of the OS disk on both VSAs (ESX) and Failover Managers (ESX) if upgrading from pre-8.5 version Due to changes in the size of the VMware tools that get installed during this software upgrade, you must increase the size of the OS disk before upgrading the VSA (ESX) and the Failover Manager (ESX). Additional space requirements are necessary for future software releases, as well. Therefore, we recommend increasing the size of the OS disk to accommodate both requirements at this time. NOTE: These instructions apply to VMware ESX Server. Other VMware products have similar instructions for extending a virtual disk. Please consult the appropriate VMware documentation for the product you are using To increase the OS disk size on the VSA: 1. Using the CMC, power off the VSA. 2. Open the VI Client and select VSA→Edit Settings→Hardware. 3. Select Hard disk 1 (verify that the Virtual Device Node is SCSI (0:0)). 4. Under Disk provisioning, change the provisioned size to 8 GB. 5. Click OK. 12 Upgrading the SAN

7. Using the VI Client, power on the VSA. 8. Find the VSA in the CMC and apply the 9.5 upgrade. To increase the OS disk size on the Failover Manager: 1. Using the CMC, power off the Failover Manager. 2. Open the VI Client and select VSA→Edit Settings→Hardware. 3. Select Hard disk 1 (verify that the Virtual Device Node is SCSI (0:0)). 4. Under Disk provisioning, change the provisioned size to 8 GB. 5. Click OK. 6. Repeat these steps for Hard disk 2 (verify the Virtual Device Node is SCSI (0:1)). 7. Using the VI Client, power on the Failover Manager. 8. Find the Failover Manager in the CMC and apply the 9.5 upgrade. Verify management group version • When upgrading to Version 9.5, the management group version will not change to Version 9.5 until all storage systems in the management group (and in the remote management group if a Remote Copy relationship exists) are upgraded to Version 9.5. • When upgrading to Version 9.5, the upgrade process validates the hardware identity of all of the storage systems in the management group. If this validation fails for any reason, the management group version will not be upgraded to 9.5. For example, if a management group has a mix of platforms, some of which are unsupported by a software release; then only the supported platforms get upgraded successfully. Therefore, the management group version will not be upgraded if the unsupported platforms remain in that management group. How to verify management group version In the CMC navigation window, select the management group, and then select the Registration tab. The management group version number is at the top of the Registration Information section. To install the SNMP MIBs When installing the CMC, select the Complete install option. The MIBs are installed in the directory with the CMC, at HP→P4000→UI→mibs. Retaining snapshot if an SRA operation takes longer than 30 minutes In the P4000 SRA, an operation should complete within 30 minutes. However, to ensure that the corresponding remote snapshot schedule retains a copy if the operation takes longer, set the snapshot retention schedule to keep three snapshots (3x30=90 minutes). Configuring SRM and vCenter servers for the VmImageConsistency feature To ensure that the VmImageConsistency feature works properly, you must install the Application Aware Snapshot Manager on the vCenter server and the P4000 SRA on the SRM server. In most P4000 SRA for VMware SRM configurations, the SRM server and the vCenter server are two separate server machines. For these configurations, you must manually create all servers in the CMC and configure the controlling server. When using the P4000 SRA for SRM, configure the server IQN even when using CHAP authentication When you manually create servers in the CMC for the SRA, add the server IQN even if CHAP authentication is enabled. Upgrading the SAN 13

including for the Failover Manager, Microsoft Windows, and VMware Server, refer to the HP P4000 SANs compatibility matrix (White Paper/4AA2-5654ENW.pdf), at http://www.hp.com/go/p4000compatibility. Mixed SAN/iQ software versions in management groups P4000 SAN Solution management groups can accommodate storage systems that are running different versions of the SAN/iQ 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 9.5 software to a management group currently running the Version 8.5 software. You cannot add a storage system running 8.5 software to a management group that is running 9.5 software. If you partially upgrade a SAN Solution management group, the management group will continue to run on the earlier software version until the entire cluster is upgraded. Workarounds While cross–version Remote Copy is occurring from 9.x to 8.5 management groups, if the copying halts because of Cluster full, the CMC shows the Error Message - "See Alarms Window," although the 8.5 management group does not have Alarms The Version 9.x Alarms and Events feature is not compatible with pre-9.x versions of software. Review the Alarm panel for Version 9.x or later management groups and, if operating in a mixed SAN environment with management groups earlier than Version 9.x, also review the Alerts panel. IQN names and uppercase letters When configuring the P4000 SRA, do not use uppercase letters in the IQN names when configuring servers in the CMC. Although the servers will still be created, SRA operations can fail. CMC on Windows 2008 is unable to auto discover storage systems if firewall is on Disable the Windows Firewall on the computer on which the CMC is installed. Application-managed snapshots will not work if the Windows server running VirtualCenter Server is not in the domain The following workarounds apply to all supported versions of Microsoft Windows. The Windows server computer name and full computer name have to be the same for the workarounds to work. Use either one of these options. • Create a domain and join the management computer to the domain • Change the Pegasus server service logon: 1. Open the service property page. 2. Select logon type. 3. Change the logon type from Local Service to the account that has administrative credentials. 9.5 Online Help is missing translated graphics in Spanish When using the Spanish version of the CMC and online help, screenshots and graphics are in English. Translated screenshots and graphics will be in an updated CMC delivered in an upcoming software patch set. 14 Compatibility/interoperability

Configuration before upgrading System settings are not retained after upgrading from Version 8.5 to Version 9.5. In the case of systems in a management group, one system in the group serves as the source for the settings that are applied to all the 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 system settings that may be retained after upgrading to Version 9.5 include settings for the following features: • Alerts, including Alert emails • SNMP general settings and traps • Remote log files Blank windows when installing CMC on HPUX11 If you experience blank windows during an install of the CMC and you are using the HPUX Window Manager (SXM/CDE), check the default font. If it is white, change it to black and begin the installer again. CMC install and uninstall wizards contain special characters such as question marks The following unsupported configurations may result in the CMC install and/or uninstall wizards to display special characters instead of the expected text. • System OS language is set to a different language than the system locale language, for example if 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 Spanish. SNMP clients and multi-byte characters SNMP clients must be configured to use UTF-8 encoding to get multi-byte characters. CHAP name in multi-byte characters requires 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. Safe to Remove status shows Yes to all drives when two drives need to be rebuilt in Raid 6 Systems using smart array controllers incorrectly report a Safe to Remove status for all drives when two drives need to be rebuilt in Raid 6. Affected systems include • DL 320s • NSM 2120 • NSM 2120 G2 Workarounds 15

• HP LeftHand P4300 • HP LeftHand P4500 • HP P4300G2 • HP P4500G2 Verify the controller by navigating to the Diagnostics category and refreshing the Hardware Information report. The controller is listed in the Controller/Cache Items category. Do not pull any drives from the array while RAID 6 is rebuilding. 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 you may get the event notice “NIC Motherboard:Port2=down.” You can safely ignore this event. An error occurs when an application-managed snapshot is created during NIC failover on an application server If an application-managed snapshot is created while a NIC failover is in progress on an application server, the following error may display in the Windows event log: App-Managed SS Failed: Could not get list of volumes on server Wait until the NIC failover has completed. Application-managed snapshots should then resume successfully. 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 SAN/iQ 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 snapshot” or “failed to create snapshots for one or more VMs” will display. Also, the Application Aware Snapshot Manager will not indicate that snapshots were deleted. To resolve the issue, you must delete the intermediate snapshots manually. HP Technical Support For technical support, call 1-800-633-3600, then say “LeftHand Solutions” at the voice prompt. Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial numbers • Error messages • Operating system type and revision level • Detailed questions You can find more information about the HP P4000 products from the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals 16 HP Technical Support

• Disk Storage Systems→P4000 SAN Solutions →HP P4000 G2 SAN Solutions • Disk Storage Systems→P4000 SAN Solutions →HP LeftHand P4000 SAN Solutions • Storage Software→Storage Virtualization Software→HP P4000 Virtual SAN Appliance Software Receive support alerts (such as Customer Advisories), driver updates, software, firmware, and customer replaceable components, in your email through HP Subscriber's Choice. Sign up for Subscriber's Choice Driver, Patch, Security, and Support alerts at the following website: http://www.hp.com/go/myadvisory HP Technical Support 17