Hp P6000 Command View 9.4 Release Notes

Transcript

HP P6000 Command View 9.4 Release Notes HP Part Number: T5494-96472 Published: October 2011 Edition: 3 © Copyright 2011 Hewlett-Packard Development Company, L.P. Version HP P6000 Command View 9.4 Description This document describes the HP P6000 Command View 9.4 release for array-based management and server-based management. IMPORTANT: HP P6000 Command View (formerly HP StorageWorks Command View EVA) supports all HP P6000/Enterprise Virtual Array (EVA) models. General references to HP P6000 Command View may also refer to earlier versions of HP Command View EVA. P6000 is the new branding for the Enterprise Virtual Array product family. The information in this document is specific to the following releases of HP management software: • HP P6000 Command View 9.4 • HP Command View EVAPerf 9.4 • Storage Management Initiative Specification for Enterprise Virtual Array (HP SMI-S EVA) 9.4 • HP Storage System Scripting Utility (SSSU) 9.4 • HP Management Integration Framework (MIF) 1.3 To determine which versions of array controller software support HP P6000 Command View 9.4, see Table 2.0, “HP P6000 Command View interoperability support,” in the HP P6000 Enterprise Virtual Array Compatibility Reference. For the location of this document, see “Product websites and documentation” (page 17). For more information about HP XCS, see the release notes for the specific XCS version. Update recommendation Users should upgrade to HP P6000 Command View 9.4. Description 3 HP P6000 Command View This section contains information about the enhancements, fixes, licenses, compatibility and interoperability, and workarounds and limitations for HP P6000 Command View 9.4. Enhancements HP P6000 Command View 9.4 enhancements: • HP XCS 10000000 controller software—Supports controller software XCS 10000000. • iSCSI controller support—Supports the 1 GB iSCSI module and the 10 GB iSCSI/FCoE module. • New product support—Supports the new P6300 and P6500 storage systems. • User-selectable asynchronous mode—Select the type of asynchronous mode (basic or enhanced) used for remote data replication. • Hard disk drive firmware upgrades on array-based management—Supports hard disk drive firmware upgrades when running array-based HP P6000 Command View 9.4 and XCS 10000000. • Disk drive remote power cycling feature—Disk drive remote power cycling is supported. • Thin provisioning—Create and manage thin provisioned virtual disks. This feature dynamically increases the space allocated to a virtual disk. • Demand-allocated containers—Create containers as a demand-allocated type. • Online virtual disk migration (change Vraid or disk group)—Change a virtual disk's redundancy level (Vraid) or disk group membership without impacting host I/O. • Online mirrorclone migration —Migrates data without impacting host I/O by reversing the identities of a source virtual disk and its synchronized mirrorclone. • Warranty data displayed—The product part number and serial number are now displayed to facilitate accurate warranty entitlement. • Large LUN support—Supports snapshot replication of LUNs greater than 2 TB. Expanding and shrinking of large LUNs is also supported. • Controller auto-boot on power cycle—EVA4400, P6300 and P6500 arrays provide a setting in the HP P6000 Web-based Operator Control Panel that enables the controllers to boot automatically when power is applied after a full shutdown. • Converged network adapter based server support—HP P6000 Command View can be installed on a converged network adapter based server to manage arrays discovered over FCoE protocol. • Web-interface security—Provides HP P6000 Command View web-interface security improvements. IMPORTANT: After upgrading to HP P6000 Command View 9.4, be sure to clear your browser’s cache completely using the method for your browser. For example, to clear browser cache on Microsoft Internet Explorer, select Tools→Internet Options. Under Browsing history, click Delete. Select Temporary Internet Files , and then click Delete. 4 HP P6000 Command View Fixes The following fixes have been implemented in HP P6000 Command View 9.4: • Deletion of default disk group warns of EVA restart, rather than resync—The correct message is now displayed, indicating that a resynchronization (not a restart) will occur. • HP P6000 Command View online help incorrectly states support for basic and enhanced async—Online help has been updated to accurately reflect supported write modes. • Derived unit deletion error causes virtual disk deletion issues—Operation no longer causes virtual disk deletion issues. • Controller events reporting many ‘Error Getting Name’ entries—The controller event now shows the controller name. • Cross-scripting issue in HP Command View EVA 9.2—Resolved the cross-scripting issue to improve security. • HP P6000 Command View 9x EVA3000/5000 events not propagated to Windows application event log—Events are now logged to the application event log. • VCS 4.100 terminating with 420c0184 after upgrade to HP Command View EVA 9.3—Resolved issue by ensuring an invalid SCSI command is no longer sent to the array. • Unable to add host when password is enabled on a password-protected array—A host can now be added on a password-protected array. • SNMP event notification changes are not retained during an HP P6000 Command View service restart—SNMP event notification changes are now retained during a service restart. • HP P6000 Command View service stops when HP Virtual Library System is zoned to the management server—The HP P6000 Command View service no longer stops because the length of the product ID is now checked before accessing the HP Virtual Library System. • SMTP authentication is not working correctly for e-mail notification feature—The formatting error that was causing this problem has been corrected. • Email notification time defaults to the GMT timezone due to the TZ (time zone) not being included in the SMTP header—The email notification time now is displayed using the correct time zone. • Host mode being incorrectly set to Unknown for MPX200—The host mode is now being set to Windows 2008, as required by the MPX200. Compatibility and interoperability IPv6 information If both IPv4 and IPv6 are installed on a single system, then, by default, HP P6000 Command View starts on the IPv4 address. To start HP P6000 Command View on a specific address, you must add the address entry under the webserver section of the cveva.cfg file. For example, to start HP P6000 Command View on IPv6, enter address 0::0 under the webserver section of cveva.cfg. Clarifying HP P6000 array-based management support HP P6000 Command View array-based management: • Manages only one array. • Cannot manage HP P6000 Continuous Access relationships (HP P6000 Command View can only see one side of the DR group). High availability solutions that rely on HP P6000 Continuous Access, like HP Cluster Extension Software (CLX) and HP Metrocluster, cannot be managed using HP P6000 Command View array-based management. HP P6000 Command View 5 • Supports Insight Remote Support Standard (starting with HP Command View EVA 9.1) and Insight Remote Support Advanced (starting with HP P6000 Command View 9.4). • Does not support HP SMI-S EVA and HP Command View EVAPerf natively. However, both HP SMI-S EVA and HP Command View EVAPerf support EVAs that are managed by HP P6000 Command View array-based management. To do so, install the software on a Windows server from the Command View installer. With the HP SMI-S EVA provider, be sure to give the IP address and credentials of the array running HP P6000 Command View to the provider. See the HP P6000 Command View Installation Guide for instructions. • Supports hard disk drive firmware upgrades when running HP P6000 Command View 9.4 and XCS 10000000. Installation and upgrade requirements For supported HP P6000 Command View upgrade paths, see Table 2.1, “HP P6000 Command View upgrade support,” in the HP P6000 Enterprise Virtual Array Compatibility Reference. For complete information on requirements and installation and upgrade procedures, see the HP P6000 Command View Installation Guide. Installing HP P6000 Command View 9.4 with HP Command View for Tape Libraries IMPORTANT: • HP Command View must be upgraded to version 9.4 before installing or upgrading HP Replication Solutions Manager to version 5.3 or HP Command View for Tape Libraries to version 2.6, if all three products are installed on the same server. • If HP Command View for Tape Libraries is installed, you must remove it before installing HP P6000 Command View 9.4. • HP recommends that you install HP Command View for Tape Libraries 2.6 before installing HP P6000 Replication Solutions Manager to avoid Postgre SQL error messages. Workarounds and limitations Most of the issues described in this section have a workaround and include a resolution. Some, however, are limitations and should be noted for reference. Trace history disabled in HP P6000 Command View trace logs In HP Command View EVA 9.2 or later, the history of trace information that accompanies a critical (level 1) error log in the cvevatrace*.log files is disabled by default. To generate sufficient trace information when a critical error log is observed in the trace files, change the configuration parameter backtrace=0 to backtrace=1 at the beginning of the file ccbtrace.cfg. This file is located in the default HP P6000 Command View installation directory, C:\Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\. You must restart the management server for this change to take effect. CAUTION: Enabling trace history may adversely affect HP P6000 Command View performance. HP Insight Remote Support Advanced software supported with HP P6000 Command View array-based management In addition to server-based management, HP Insight Remote Support Advanced software is supported with array-based management. To enable array-based management support, you must set identical credentials for both the HP P6000 Command View host (where you used discoverer.bat to set up the connection to array-based management) and the array management module. 6 HP P6000 Command View Verifying HP P6000 Command View code HP products deliver on the “trustworthy and reliable” brand promise. Creating and delivering an electronic cryptographic "signature" for HP code (such as software, firmware, drivers, applications, patches, and solutions) provides an industry-standard method to verify the integrity and authenticity of the code you receive from HP before deployment. Digitally signed code helps you manage your security vulnerability risk from using non-HP versions of the software and firmware, which may fail to meet expectations and may contain malicious code (like a virus or worm). To verify the HP P6000 Command View code before installing the software, contact your HP representative for instructions. Emulex HBA requires latest driver version Servers that use an Emulex HBA with Storport drivers (earlier than version 5-2.00a12) may experience a system hang that requires a reboot, or an Array Discovery issue in HP P6000 Command View. Ensure that the Storport driver version you have is 5-2.00a12 or later. To obtain the drivers, go to the following HP website: http://www.hp.com/support/downloads NOTE: For Windows 2003 systems, the new driver (5-2.00a12) requires the Microsoft hotfix KB932755. To obtain the hotfix, go to the following Windows website: http://support.microsoft.com/KB/932755 Windows 2003 server requires a hotfix If the management server is running Microsoft Windows 2003, HP P6000 Command View might not display any array. To resolve this issue, you must install a Microsoft hotfix. Go to the following link for details and the hotfix download: http://support.microsoft.com/kb/945119/ If you are using the server for storage only, not as a management server, you do not need to install this hotfix. Antivirus software may degrade performance To avoid HP P6000 Command View performance issues when antivirus software is installed on the management server, HP recommends that you exclude from the antivirus software scan the log-related files that change frequently, including the following: • \Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\cache • \Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\log • \Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\logs • \Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\trace If HP Command View EVAPerf is installed: • \Program Files\Hewlett-Packard\EVA Performance Monitor\logs • \Program Files\Hewlett-Packard\EVA Performance Monitor\cache If HP SMI-S EVA is installed: • \Program Files\Hewlett-Packard\SMI-S\CXWSCimom\logs • \Program Files\Hewlett-Packard\SMI-S\EVAProvider\logs HP P6000 Command View 7 Windows 2008 and LUN shrink LUN shrink on Windows 2008 systems is supported only on basic disks and dynamic simple volumes that are spanned or are mirrors. Striped or RAID 5 dynamic disks are not supported with LUN shrink. Large LUN presentation requires Windows 2003 hotfixes The presentation of large LUNs (larger than 2 TB) requires Windows hotfixes KB949001 and KB919117. To obtain the hotfixes, go to the following Microsoft websites: http://support.microsoft.com/KB/949001 http://support.microsoft.com/KB/919117 Setting the HP Management Integration Framework Web Service IP address in a multi-homed configuration For authentication, on a multi-homed machine (a machine with multiple NICs), HP Management Integration Framework binds to the first IP address reported by the operating system. If this is not the desired IP address, set the HP Management Integration Framework Web Service IP address as follows: 1. Navigate to the HP Management Integration Framework Configuration GUI and log on. The Configuration window opens. 2. 3. 4. Expand the General pane. In the Web Service IP Address box, enter the IP address. Click Save Changes. Wait until the change is saved. 5. Click Restart Service. HP Management Integration Framework will bind to the IP address. Array-based management proxy displays incorrectly In an array-based management configuration, the managed proxy displayed will be different from that of the web access point. When a layered application uses this information, it will see different IP addresses in Managed Proxy and Launch URL. Although the management proxy displays incorrectly, the URL for HP P6000 Command View launches the array-based management correctly. Cannot access HP P6000 Command View from HP Systems Insight Manager or HP P6000 Replication Solutions Manager To log on to HP P6000 Command View directly from HP Systems Insight Manager (HP SIM) or HP P6000 Replication Solutions Manager, a trust relationship, referred to as Single Sign-on, must be established between the applications. When the trust relationship is broken, HP P6000 Command View cannot be run from HP SIM or HP P6000 Replication Solutions Manager. In this case, you must re-establish the trust relationship. See “Single Sign-on from HP Systems Insight Manager” in the HP P6000 Command View User Guide. Using HP P6000 Command View for Single Sign-on with HP SIM 5.3 Although launching HP P6000 Command View 9.4 or later from HP SIM 5.3 opens another browser window with a login screen for HP P6000 Command View for Single Sign-on (automatic login), the feature needs HP SIM 6.0 to work as designed. Install of HP Command View for Tape Libraries 2.6 fails during database install When you install HP Command View for Tape Libraries 2.6, an error message is displayed indicating that installation of the database has failed. This error message may be displayed if Cygwin is installed on the server and appears in the path environment variable. If this is the cause of the failure, you can temporarily remove Cygwin from the path and attempt installation again as follows: 1. Right-click My Computer. 8 HP P6000 Command View 2. Select Properties. The System Properties dialog box opens. 3. 4. If Cygwin appears in the path environment in either the User variables or the System variables, remove it. Click the Advanced tab and select Environment Variables. The Environment Variables dialog box opens. 5. 6. Save your changes and click OK twice to exit the Environment Variables and System Property windows. Reinstall HP Command View for Tape Libraries 2.6. After successful installation, you can add Cygwin back into the PATH environment variable. Internet Explorer 8 language code change In Japan, Microsoft Internet Explorer 8 (IE8) installs using the Japanese language code ja_JP by default. This is a change from earlier and current English versions, which default to ja. To use HP P6000 Command View with IE8 as a Japanese client, you must set the browser language preference ja. To change the language preference, select Tools→Languages→Language→Add. Setting the Network Time Protocol server time using array-based management When setting the Network Time Protocol (NTP) server time using array-based management, the system time is not updated immediately. The system time should update to match the NTP server within 10 minutes. Not able to log in to HP Replication Solutions Manager server If the Windows TEMP environment variable is not set correctly, you may not be able to log in to the HP Replication Solutions Manager server. Ensure that the TEMP environment variable is pointing to an existing folder and the folder is accessible. Write cache policy not maintained when migrating a virtual disk When migrating the Vraid type and/or disk group of a virtual disk using the Online virtual disk migration feature, the write cache policy is set to write-back. If the virtual disk had write cache policy was set to write-through, the policy is changed to write-back. Multi-home Agent IP does not change for SNMP traps for different VLANs Server-based HP P6000 Command View can be installed on a multi-homed server where multiple IP addresses are configured. The array can be accessed from any of the IP addresses of the server through HP P6000 Command View. Consider the following when using HP P6000 Command View on a multi-homed server: • If the network is not accessible through an IP address on the server, the array will remain actively managed by HP P6000 Command View on that IP address. However, it may be necessary to use an HP P6000 Command View instance on another IP address to take management of the array away from the inaccessible HP P6000 Command View instance. • When SNMP traps are configured from HP P6000 Command View, the SNMP agent IP address that generates the trap will be the same, regardless of the destination IP address to which the trap is to be sent. The agent IP address will be the IP address from which the array is actively managed. Online virtual disk migration limitation HP P6000 Command View should not be restarted or management of the array transferred while a migration is in progress. Doing so will cause HP P6000 Command View to abandon the migration tasks, leaving behind temporary mirrorclones that must be deleted manually. This does not impact host I/O directed at the original virtual disk. HP P6000 Command View 9 Changing the management IP address of an iSCSI controller using the CLI When the management IP address of the iSCSI controller is changed using the CLI, HP P6000 Command View loses connection with iSCSI controller, resulting in Not Available status displayed in the iSCSI controller GUI pages. To correct this, use the HP P6000 Command View GUI to delete the existing iSCSI controller, and then add the new IP address using the Add iSCSI controller page. Providing credentials for Microsoft Exchange email notification When using the HP P6000 Command View server-based management/array-based management email notification feature with a Microsoft Exchange server, it may be necessary to provide credentials to receive the messages. This is determined by the configuration of the Microsoft Exchange server as follows: • If Microsoft Exchange is configured with only anonymous enabled, it is not necessary to provide credentials to receive HP P6000 Command View email notification. • If Microsoft Exchange is configured with only auth login enabled, you must provide credentials to receive HP P6000 Command View email notification. • If Microsoft Exchange is configured with anonymous and auth login enabled, you must provide credentials to receive HP P6000 Command View email notification. This applies whether the “require authentication” option is selected or not. If auth login is enabled in any way, credentials are required. Using an FCoE CNA-based server with MPX200 connectivity When managing an EVA using an FCoE Converged Network Adapter-based server and through MPX200 connectivity, unpresenting the last FCoE LUN from the MPX200 iSCSI controller may cause HP P6000 Command View to lose communication with the array. To resolve this issue, use the lunmask add wizard in the MPX200 CLI to present LUN 0 from each array target WWN to each MPX200 FCoE port and to each management server FCoE-CNA port. To gather the necessary information, use the show fc, show targets, and show initiators MPX200 CLI commands. Then, use the lunmask add wizard. iSCSI or iSCSI/FCoE module configuration file indicates zero bytes When saving the iSCSI or iSCSI/FCoE module configuration (from the iSCSI Controller Configuration page in HP P6000 Command View), HP P6000 Command View may indicate the file size is zero bytes. If this occurs, you must restart the controller and then save the configuration again by performing the following steps: 1. Select the applicable iSCSI controller in the navigation pane. 2. Select Shutdown on the iSCSI Controller Properties window. 3. Select Restart on the iSCSI Controller Shutdown Properties window. 4. After the controller has restarted, select the iSCSI controller in the navigation pane. 5. Select Set Options. 6. Select Save/Restore Configuration. 7. Select Save Configuration. If you attempt to restore the configuration from a zero byte file, the iSCSI or iSCSI/FCoE module configuration will not be restored and it may cause the HP P6000 Command View content page to hang. iSCSI/FCoE controller inaccessible from HP P6000 Command View If an iSCSI/FCoE controller is inaccessible from HP P6000 Command View, avoid performing any management operations on that controller and any iSCSI/FCoE objects displayed in HP P6000 Command View. 10 HP P6000 Command View Installer displays error that user does not have administrator privileges Upon starting the installation of version 9.4 (or upgrade from version 9.2 or 9.3), you may receive an error message that you do not have administrator privileges. To avoid this error message, ensure that you add your user name to the local Administrators group before starting the installation or upgrade. Creating disk groups with double protection level When creating a disk group with double protection level on an array running XCS 10000000, a minimum of 10 disk drives is required on the array. If the disk group contains fewer than 10 drives and double protection is requested, only single protection level will be used. If all the physical disks in the disk group are of the same capacity, double protection level is achieved by reserving capacity equal to four times the capacity of a single disk. If the physical disks in the disk group are of different capacities, double protection is achieved by reserving capacity equal to the sum of the four highest capacity disks. HP Management Integration Framework 1.3 Reduced number of ports HP Management Integration Framework 1.3 reduces the number of used ports to the following four: • Discovery (UDP) port. The default is 9000. • Web Server (TCP) port. The default is 2374. • Unsecure Web Services (TCP/HTTP) port. The default is system assigned. • Secure Web Services (TCP/HTTPS) port. The default is system assigned. The following information about HP Management Integration Framework configuration files applies when installing MIF 1.3: • Configuration files found on startup will be automatically converted and backed up. • All port properties in xfsc.cfg, xfi.cfg, and xfd.cfg (except for discoveryURI) have been removed. • If you have commented out legacy ports in the configuration files, these will not be removed. • The following shows the new http/https port properties entry in xf.cfg: Section ServicePorts { #httpPort 0 #httpsPort 0 } HP Command View EVAPerf 9.4 This section describes enhancements and workarounds for HP Command View EVAPerf 9.4. HP Management Integration Framework 1.3 11 Fixes The following fix has been implemented in HP Command View EVAPerf 9.4: • hc command did not display entire WWN for iSCSI/ FCoE hosts—The complete WWN of the host HBA is now displayed. • Evaperf rc command displays incorrect error message for wrong WWN—Correct error message is now displayed for wrong WWN input value to rc command. Workarounds and limitations Domain names not supported in hostname parameter of fnh command If the host name you specify in the fnh command is a full domain name (for example, nt12345.asiapacific.xyzcompany.net ), the friendly names host file is not created. Use localhost or the host name without the domain when running the fnh command. Examples of supported entries follow: evaperf fnh localhost hpadmin@localhost evaperf fnh nt12345 [email protected] Windows Performance Monitor limitations When using Windows Performance Monitor to view HP Command View EVAPerf performance data on a management server running Windows 2003 Enterprise Edition, Windows Performance Monitor may hang when the number of counters exceeds 900 (for example, a virtual disk object that exceeds 100 instances, with 9 counters per instance). pd and hps command limitation The incorrect enclosure and bay IDs are displayed in the evaperf pd command when running VCS 4.100 or XCS 6.000. • HSV100 controllers running VCS 4.100 report inconsistent enclosure and bay IDs on both controllers. • HSV200 controllers running XCS 6.000 report the enclosure and bay ID as "-" on one of the controllers after a reboot. evaperf nall command fails to execute The evaperf nall command fails to execute in continuous mode on a Windows 2008 server in both local mode and remote mode. Use the evaperf all command instead. hist command limitation When used with the object type state_diskgroup, the hist command does not display data for the EVA4400 and EVA6400/8400. HP SMI-S EVA 9.4 HP SMI-S EVA 9.4 is shipped with the HP P6000 Command View software suite. HP SMI-S EVA enables Common Information Model (CIM)-capable management software to manage EVA storage systems. HP SMI-S EVA is based on the Managed Object Format (MOF) 2.15 and is SMI-S 1.4 compliant. NOTE: If a version of HP SMI-S EVA earlier than 8.0.x is installed, you must remove it before installing HP SMI-S EVA 9.4. 12 HP SMI-S EVA 9.4 Compatibility and interoperability Supported main profiles and subprofiles The HP SMI-S EVA Provider 9.4 supports the following main profiles and subprofiles: • Main profiles—Array and Server • Subprofiles—Software, Masking and Mapping Subprofile, Copy Services, Block Services, Disk Drive Lite, FC Target Ports, FC Initiator Ports, Job Control, Access Points, Physical Package, Multiple Computer System, SAS Initiator port, thin provisioning, and Profiles Registration SSL certificates For information about Secure Sockets Layer (SSL) certificates for HP P6000 Command View, see the HP P6000 Command View Installation Guide. HP SMI-S EVA initial cache building may take longer with array-based management If you are using the HP SMI-S EVA Provider with array-based management, allow several minutes after the IP address is added to the Discoverer tool or after the HP SMI-S EVA Provider host is rebooted, to build the cache. Applications using HP SMI-S EVA do not have access to the array details until cache building is complete. To determine the status of cache building, use the getarrayrefreshstatus.bat file. Multiple array-based management systems per HP SMI-S EVA Provider HP recommends a maximum of 12 HP P6000 Command View array-based management systems configured for the HP SMI-S EVA Provider. Workarounds and limitations Data Protector backup fails with error Failed to create target volume When performing a Data Protector backup of a snapshot created from the HP P6000 Command View GUI, the backup may fail with the error Failed to create target volume. To avoid this situation, after creating a snapshot using the HP P6000 Command View GUI, wait for the next incremental SAL refresh (or force a refresh) before running a Data Protector job on the snapshot. HP Storage System Scripting Utility 9.4 This section describes HP SSSU 9.4 enhancements, fixes, limitations, and other information. HP Storage System Scripting Utility 9.4 13 Enhancements HP SSSU 9.4 enhancements: • Improved performance in interactive mode—In interactive mode, by default there was a 10 second delay between SSSU commands. The default is now zero (no delay). This improves the speed at which SSSU scripts are executed. If the delay is required, it can be set manually using the command set options command_delay=delay_time. Fixes The following fixes have been implemented in HP SSSU 9.4: • HP SSSU displays incorrect operational state for cache battery 2—HP SSSU now displays the correct status for cache battery 2. Limitations and workarounds • If you use the CODELOAD DISK command to upgrade firmware on multiple disk drives, no error is displayed for disks configured with Vraid0. • The grep command must be entered in lowercase; uppercase does not work. • Executing a command with grep and redirecting the output in a file does not work. However, output can be captured by specifying the command with grep in a script file and executing it using the FILE command with redirection. Syntax error when capturing configuration of array in DR relationship When using HP SSSU to capture the configuration of an array that is in a DR relationship, the resulting configuration file contains a syntax error that renders the file unusable when restoring the configuration. The capture configuration incorrectly captures two properties at a time for the SET DR_GROUP command: SET DR_GROUP "\Data Replication\DR Group 001" LINK_DOWN_AUTOSUSPEND=DISABLE SET DR_GROUP "\Data Replication\DR Group 001" LINK_DOWN_AUTOSUSPEND=DISABLE FULLCOPY_AUTOSUSPEND=ENABLE Attempting a restore using a file with this syntax error will fail because HP SSSU attempts to set two properties at a time. After capturing the configuration, edit the SET DR_GROUP command in the configuration file as follows: SET DR_GROUP "\Data Replication\DR Group 001" LINK_DOWN_AUTOSUSPEND=DISABLE SET DR_GROUP "\Data Replication\DR Group 001" FULLCOPY_AUTOSUSPEND=ENABLE Editing the file before it is needed enables you to restore the configuration successfully, if necessary. Running HP SSSU in OpenVMS There are two options for running HP SSSU in OpenVMS: • Change to the directory where HP SSSU is installed and run the application from there. • To run HP SSSU from any directory, set an environment variable to the HP SSSU executable file name and path. For example: Env_Var_Name :== [Path] file_name_of_executable HP SSSU memory utilization issue on VMware ESX 3.5 In VMware ESX 3.5, if HP SSSU closes due to a memory utilization issue, increase the console memory to more than 400 MB. 14 HP Storage System Scripting Utility 9.4 HP SSSU does not create an FCoE host with HP-UX The HP P6000 Command View GUI enables you to create an FCoE host with operating system type as HPUX. However, HP SSSU does not support this operation. HP SSSU may hang when using long commands on Solaris When using long commands on Solaris, the HP SSSU process may hang. This is a result of how Solaris handles long commands. The ADD MULTISNAP command creates write-protected snapshots and snapclones By default, the ADD MULTISNAP command creates write-protected snapshots and snapclones. (By default, the ADD COPY and ADD SNAPSHOT commands create write-enabled snapshots and snapclones.) Before you present a snapshot or snapclone that was created using the ADD MULTISNAP command, use the SET VDISK command and set the NOWRITE_PROTECT option to False if the operating system does not allow you to mount volumes using the snapshot or snapclone. Accessing the HP Storage System Scripting Utility The latest versions of HP SSSU are on the HP P6000 Command View software CD. Prerequisites HP SSSU 9.4 requires VC9.0 SP1 redistributable packages on Windows 2003 and 2008 hosts. Select one of the following links to install the package for the applicable host processor architecture: • x86 :http://www.microsoft.com/downloads/details.aspx? familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en • x64 :http://www.microsoft.com/downloads/details.aspx? familyid=BA9257CA-337F-4B40-8C14-157CFDFFEE4E&displaylang=en • ia64 :http://www.microsoft.com/downloads/details.aspx? FamilyID=DCC211E6-AB82-41D6-8DEC-C79937393FE8&displaylang=en Installing the HP Storage System Scripting Utility For installation instructions, see the HP P6000 Command View Installation Guide. HP Storage System Scripting Utility 9.4 15 Documentation updates The following updates apply to the HP P6000 Command View 9.4 documentation: • Support for disk drive remote power cycling feature—The HP P6000 Command View online help states that the disk drive remote power cycling feature (for HP service personnel) is supported in controller software XCS 09000000 or later. It should state that the feature is supported in XCS 09500000 and later. • Restricted IP addresses for array-based management module—The HP P6000 Command View online help states that IP addresses 10.0.0.1, 10.0.0.2 and 10.0.0.3 should not be used for any device that connects to an HP storage system management module. It should state that restricted IP addresses are dependent on the version of controller software. For controller software prior to XCS 10000000, the restricted IP addresses are: 10.0.0.1, 10.0.0.2 and 10.0.0.3 . For XCS 1000000 and later, the restricted IP addresses are: 10.253.251.230 – 10.253.251.249. • IPv6 support—The HP P6000 Command View online help states that IPv6 is not supported with array-based Command View. It should state that IPv6 support is provided with both server-based and array-based HP P6000 Command View. • 1 TB license availabilty—The HP P6000 Command View online help states that 1 TB licenses are available for HP P6000/Enterprise Virtual Array (EVA) storage systems. This is incorrect. The 1 TB licenses are no longer available from HP. • Upgrading disk drive firmware—The online help for the “Code load disk drive page” topic refers HP EVA4400 customers to the Release Notes for the procedure to upgrade disk drive firmware. It should refer customers to the Updating Product Software Guide for the applicable array model and XCS controller software version for the procedure. Also, the online help should state that upgrading disk drive firmware in an array-based management environment is dependent on the controller software version. For controller software versions prior to XCS 10000000, upgrading disk drive firmware on an HP EVA4400 must be performed using server-based HP P6000 Command View. For XCS 10000000 or later, you can upgrade disk drive firmware on an HP EVA4400 or P6300/P6500 EVA using array-based HP P6000 Command View. • Management module reset button behavior—The “Connecting to the management module (initial setup)” topic in the P6000 WOCP online help and user guide incorrectly describes how the reset button on the management module works. The correct behavior is that the green LED on the management module blinks when the reset has started. When the reset is completed, the green LED turns solid and sets IP addresses of 192.168.0.1/24 (IPv4) and fd50:f2eb:a8a::7/48 (IPv6). Use the appropriate IP address to log into the P6000 WOCP. • Missing reference in HP P6000 Command View User Guide—In the “Containers” section of Chapter 5, Replicating storage, the text regarding preallocated snapshot redundancy levels should include a reference as follows: For a preallocated snapshot, the redundancy (Vraid) level of the container must be the same or lower than the source. If the source has other snapshots, the redundancy (Vraid) level of the container must be the same as the other snapshots. For descriptions of redundancy (Vraid levels), see Redundancy (Vraid) levels (page 27). 16 • No help topic for Vdisk Cache Data Lost window—An incorrect help topic is displaying for the Vdisk Cache Data Lost window. The correct help topic will be added in the next release. • Help topic not being generated when viewing the online help for the EVA4400 running XCS 09xxxxxx—The help topic for the Log tab of the DR Group Properties (Destination) window is not generating when you select hsv300v0900 as the help type. • Setting the controller power on behavior–In the P6000 WOCP online help and user guide, the “Controller power on behavior” and “Setting controller power on behavior” sections describe the Documentation updates new WOCP feature that can be set so that the array boots up automatically when power is applied after a full shutdown. To further clarify this feature: ◦ If this feature is disabled and you turn on power to the array from the rack power distribution unit (PDU), only the disk enclosures boot up. With this feature enabled, the controllers will also boot up, making the entire array ready for use. ◦ If, after setting this feature, you remove the management module from its slot and reinsert it to reset power or you restart the management module from the WOCP, only the controllers will automatically boot up after a full shutdown. In this scenario, you must ensure that the disk enclosures are powered up first; otherwise, the controller boot up process may be interrupted. ◦ After setting this WOCP feature, if you have to shut down the array, perform the following steps: 1. Use HP P6000 Command View to shut down the controllers and disk enclosures. 2. Turn off power from the rack power distribution unit (PDU). 3. Turn on power from the rack PDU. After startup of the management module, the controllers will automatically start. Product websites and documentation All documentation associated with this release is available on the Web. You can find the documents on the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals In the Storage section, click Storage Software, and then select HP P6000 Command View Software under Storage Device Management Software. Table 1 HP storage websites Item HP website EVA3000 http://www.hp.com/support/manuals. Select Disk Storage Systems under Storage, and then select HP 3000 Enterprise Virtual Array under P6000/EVA Disk Arrays. EVA4400 http://www.hp.com/go/eva4400 EVA6400/EVA8400 http://www.hp.com/go/eva6484 EVA5000 http://www.hp.com/support/manuals. Select Disk Storage Systems under Storage, and then select HP 5000 Enterprise Virtual Array under P6000/EVA Disk Arrays. EVA4000/4100 EVA6000/6100 EVA8000/8100 http://h18006.www1.hp.com/storage/disk_storage/eva_diskarrays/eva_arrays/index.html P6300/P6500 http://www.hp.com/go/p6000 HP P6000 Command View http://h18006.www1.hp.com/products/storage/software/cmdvieweva/index.html HP P6000 Business Copy http://h18006.www1.hp.com/products/storage/software/bizcopyeva/index.html HP P6000 Continuous Access http://h18006.www1.hp.com/products/storage/software/conaccesseva/index.html HP P6000 Replication Solutions Manager http://h18006.www1.hp.com/products/storage/software/repsolmgr/index.html An HP Command View EVAPerf white paper is also available from the following HP website: http://h18006.www1.hp.com/storage/softwhitepapers.html Product websites and documentation 17