HP StorageWorks P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide Part number: TB581-96048 Third edition: April 2011
Legal and notice information © Copyright 2010-2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Preface ................................................................................................ 9 1 Overview ........................................................................................ 11 Basic system configuration ......................................................................................................... 11 About the installation DVD .........................................................................................................
3 Agent installation ............................................................................. 41 Planning for Device Manager agent installation ............................................................................ Verifying agent installation conditions ................................................................................... Creating the agent installation location ................................................................................. About modifying agent services ........
Performing a Device Manager agent unattended removal .............................................................. Removing a Device Manager agent from a Windows host (unattended removal) ......................... Removing a Device Manager agent from a UNIX host (unattended removal) .............................. Verifying the Device Manager agent unattended removal ........................................................ 72 72 73 74 B Ports ...............................................................
Figures 1 P9000 Command View AE Software: Basic configuration ............................................
Tables 1 Server installation path requirements ......................................................................... 17 2 Database file storage path and location requirements .................................................. 18 3 Appropriate memory heap size for Common Component ............................................. 19 4 Appropriate memory heap size for the Device Manager server ..................................... 20 5 Database path and location requirement ...................................
Preface This manual provides information for installing and removing P9000 Command View AE Software.
Preface
1 Overview This chapter provides basic system configuration information for P9000 Command View AE Software. It includes the following topics: Basic system configuration P9000 Command View AE Software can manage many different types of storage systems. The information in this manual assumes the following system configuration: • P9000 Command View AE Software (and Common Component) are used to manage user accounts. • The system is not linked to an external authentication server.
Figure 1 P9000 Command View AE Software: Basic configuration You use P9000 Command View AE Software through a management client (either the web client GUI or the Device Manager and Tiered Storage Manager CLI) from which you can operate, Tiered Storage Manager, and Replication Manager. The management server (on which P9000 Command View AE Software is installed) centrally manages the storage systems and hosts.
The pair management server centrally manages copy pair status and configuration. The following components are installed on the pair management server: • Device Manager agent Collects hosts and storage system information. • RAID Manager Controls storage system copy pairs. The management server accesses the management clients and storage systems over a TCP/IP network.
NOTE: The noted versions of the following software support an upgrade installation from the installation DVD: • From version 5.0 or later: Device Manager server Tiered Storage Manager server • From version 6.0 or later: Replication Manager server When working from a software version earlier than specified, first upgrade to version 6.x, and then upgrade to version 7.0 or later.
2 P9000 Command View AE Software server installation This module describes how to install the server. Planning for server installation Before you install the P9000 Command View AE Software server, verify the following conditions and gather the information you need to perform the installation. Verifying server installation conditions Before using the installer for the P9000 Command View AE Software server, determine the information you need to provide.
NOTE: The expected volume and copy pair counts below are based on the default memory heap size.
Creating the server installation location (new installation only) You can change the default installation destination for the server . If you change the destination, ensure that the path adheres to the conventions in Table 1. Table 1 Server installation path requirements Condition Requirements Absolute path length Maximum length: 64 bytes Windows: Allowed characters A through Z, a through z, 0 through 9, periods (.
Creating the database file storage location (new installation only) You can change the default database file storage destination for P9000 Command View AE Software. If you change the destination, ensure that the absolute path and location adhere to the restrictions in Table 2. Table 2 Database file storage path and location requirements Condition Requirements Absolute path length 90 bytes maximum Windows: Allowable characters A through Z, a through z, 0 through 9, periods (.
When using an IP address to access a management server with multiple NICs, use the IP address for the system connected to the management client.
Memory Heap Size Environment Managed Resources Both open volumes and mainframe volumes# Small (Min: 128 MB, Max: 256 MB) Medium (Min: 256 MB, Max: 512 MB) Large (Min: 512 MB, Max: 1,024 MB) 40,000 or less 40,001 to 60,000 60,001 or more Legend: -- : You cannot specify this memory heap size.
If you plan to use a path other than the default, ensure that the new path adheres to the restrictions in Table 5. Table 5 Database path and location requirement Condition Requirements Absolute path length Maximum 150 bytes Windows: Allowed characters A through Z, a through z, 0 through 9, periods (.), underscores (_), left parentheses ((), right parentheses ()), single-byte spaces, backslashes (\), and colons (:) Linux: A through Z, a through z, 0 through 9, periods (.
CAUTION: When you upgrade P9000 Command View AE Software to version 7.0 or later, storage tiers (custom tiers) that were created in versions earlier than 7.
NOTE: Ensure that the maximum value you set for a kernel parameter does not exceed the maximum value specified by Linux. Related topics • P9000 Command View AE Software server installation prerequisites, page 21 • Installing P9000 Command View AE Software in a Linux environment, page 32 • Modifying kernel parameter values and shell restrictions, page 30 Recommended Red Hat Enterprise Linux /etc/sysctl.
Kernel Parameter Device Manager Tiered Storage Manager Software Replication Manager Software kernel.threads-max 55 30 30 kernel.msgmni 44 0 0 4th parameter of kernel.sem 9 1 1 2nd parameter of kernel.sem 120 50 50 kernel.shmmax 280100864 50000000 100000000 kernel.shmmni 0 0 0 kernel.shmall 386839552 100695040 100000000 The following formulas are for calculating the values for the kernel parameters: • For kernel.
kernel-parameter-value-to-be-set = Max{ Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS } + value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager , value-for-HiRDB } NOTE: Max {x, y, z} indicates the maximum value among x, y, and z. Related topics • Setting kernel parameters and shell restrictions (Linux), page 22 • Recommended Red Hat Enterprise Linux /etc/security/limits.
The following tables show the shell restriction values you need to set. The formula for calculating these values follow the tables. Table 8 Shell restriction values for /etc/security/limits.conf (1/2) Shell Restriction Installer Check Value Operating System Initial Value HiRDB Common Component nofile (soft/hard) 1596 1024 1344 572 nproc (soft/hard) 8358 8192 512 165 Table 9 Shell restriction values for /etc/security/limits.
The appropriate values for each of these settings depend on which of the following P9000 Command View AE Software products you are installing: • • • • Common Component Device Manager Tiered Storage Manager Software Replication Manager Software The following tables show the kernel parameter values you need to set. The formulas for calculating these values follow the tables. Table 10 Kernel parameter values for /etc/sysctl.
kernel-parameter-value-to-be-set = Max { Max { value-that-is-enabled-in-the-system , initial-value-of-the-OS } , value-for-Common-Component + value-for-Device-Manager + value-for-Tiered-Storage-Manager + value-for-Replication-Manager , value-for-HiRDB } • For kernel.
Related topics • Setting kernel parameters and shell restrictions (Linux), page 22 • Recommended SUSE Linux Enterprise Server /etc/security/limits.conf values, page 29 • Modifying kernel parameter values and shell restrictions, page 30 Recommended SUSE Linux Enterprise Server /etc/security/limits.conf values Before installing P9000 Command View AE Software on a SUSE Linux Enterprise Server system, set the shell restrictions for the /etc/security/limits.conf file.
+ + + + value-for-Common-Component value-for-Device-Manager value-for-Tiered-Storage-Manager value-for-Replication-Manager , value-for-HiRDB } NOTE: Max {x, y} indicates the larger value of x or y. Related topics • Setting kernel parameters and shell restrictions (Linux), page 22 • Recommended SUSE Linux Enterprise Server /etc/sysctl.
P9000 Command View AE Software server installation When you install P9000 Command View AE Software on the management server, use the installation procedure that is appropriate for the operating system you are using.
6. Click Finish. The GUI login window appears. Related topics • • • • Verifying server installation conditions, page 15 P9000 Command View AE Software server installation prerequisites, page 21 Post-installation tasks (new installation), page 32 Post-installation tasks (overwrite or upgrade), page 37 Installing P9000 Command View AE Software in a Linux environment You install P9000 Command View AE Software on a Linux host by using the installation DVD. To install P9000 Command View AE Software: 1.
• Change the system account passwords (recommended). • Create a new user to whom you can assign permissions for all P9000 Command View AE Software resources and who will become the storage administrator. After you have created a storage administrator, the storage administrator can register storage systems and hosts, add accounts for other storage administrators and begin operating P9000 Command View AE Software.
2. On the Administration tab, click Users and Permissions. 3. In the tree view, select Users. 4. In the list of users, select the System account. 5. Click Change Password, type the new password and verify it, and then click OK. 6. Confirm that the user account can log on to P9000 Command View AE Software with the new password. Creating user accounts Create an account for each user and set the appropriate permissions (roles) for management tasks.
• Resource groups can be managed (when All Resources is assigned). • Management resources can be registered, management resource settings can be changed, and management resource information can be referenced. • Modify: Management resources can be registered, management resource settings can be changed, and management resource information can be referenced. • View: Management resource information can be referenced.
• Built-in user groups, page 36 Built-in user groups Device Manager provides the following built-in user groups. Table 14 Built-in user groups Roles Built-in user group name Description Resource group Admin Modify View Peer AdminGroup When an upgrade installation is performed from version 7.0.1 or earlier, all users that were assigned All Resources and had Device Manager Admin permission are registered in this user group.
Related topics • User permissions in P9000 Command View AE Software products other than Device Manager, page 35 • Device Manager roles, page 34 Post-installation tasks (overwrite or upgrade) After performing an overwrite or upgrade P9000 Command View AE Software installation, set the information required by each installed product according to version of each product before the overwrite or upgrade installation: • For all overwrite or upgrade installations: • Back up the database • Refresh each storage syst
2. Execute the hcmdsbackups command to back up the database. For Windows: Common-Component-installation-folder\bin\hcmdsbackups /dir folder-for-storing-backup-files /auto For Linux: Common-Component-installation-directory/bin/hcmdsbackups -dir directory-for-storing-backup-files /auto NOTE: The dir option is used to specify the absolute path of the folder or directory on the local disk where the database backup files are stored.
To synchronize databases: 1. If Replication Manager Application Agent version 7.1 or later is installed on the management server, set the value of the base.refreshdginfo.exec property in the Replication Manager base.properties file to 0. The base.properties file is stored in the following location: • In Windows: Replication-Manager-server-installation-folder\conf • In Linux: Replication-Manager-server-installation-directory/conf 2. Log in to Device Manager using the System account. 3.
• Roles for Device Manager must be set to resource groups. Users with Tiered Storage Manager permissions: • When users also have Device Manager permissions User accounts are migrated according to the resource groups that were allocated in Device Manager, as well as the Tiered Storage Manager permissions remaining the same.
3 Agent installation This module describes how to install agents. Planning for Device Manager agent installation Before you install the Device Manager agent, verify the following conditions and gather the information you need to perform the installation. Verifying agent installation conditions Before performing a new installation, gather the information you need to provide to the installation wizard, including the default installation folder.
• The HiScan command execution default: Daily at 2:30 AM. For RAID Manager: • The Windows default installation folder: The Device Manager agent installation drive • The UNIX default installation directory: /HORCM • By default, copy pairs are not batch managed by the agent host (Default: no).
When creating the installation location for the Device Manager agent, adhere to the naming conventions in Table 15. Table 15 Agent installation folder naming requirements Condition Requirements Maximum length 64 bytes Allowed characters A through Z, a through z, 0 through 9, periods (.), underscores (_), left parentheses ( ( ), right parentheses ( ) ), and single-byte spaces • Do not use a space as the first or last character of the installation folder name.
When creating the host name for this server, adhere to the naming conventions in Table 16. Table 16 Server host naming conventions Condition Requirements Maximum length 50 bytes Allowed characters A through Z, a through z, 0 through 9, hyphens (-), underscores (_), periods (.), and at signs (@) Other conditions Do not use a hyphen as the first or last character of the host name.
• The location of the RAID Manager installation folder: • For Windows: The installation drive • For UNIX: The installation directory • The method used for managing copy pairs: • Batch managed on a Device Manager agent host. • Managed for each host on which the Device Manager agent is installed.
• hbsasrv • hdvmagt#1 • hdvmagt_setting • hdvmagt_account#2 • hdvmagt_schedule#2 • HiScan • hldutil • stop_hdvmagt#1 • TIC #1 Commands for Device Manager agent versions earlier than 5.0. #2 Commands for Device Manager agent versions earlier than 7.0. If you run these one of these commands by mistake, restart your system when the installation or upgrade completes. • Do not perform an overwrite installation of Device Manager agent using a version that is earlier than the one currently installed.
• If the Windows logon account contains multi-byte characters, agents cannot be installed. Specify a folder that does not include multi-byte characters for the TMP environment variable. P9000 Command View Advanced Edition Software products for Windows support the Windows Remote Desktop functionality. NOTE: The Microsoft terms for this functionality differ, depending on the Windows operating system.
• /var/tmp Keep the following in mind when installing the Device Manager agent in a Solaris 10 environment: • Do not specify system zone settings. • If the Device Manager agent (version 4.1- 5.1) was upgraded to 5.5 or later by an overwrite installation in an environment with the non-global zone specified, then it is installed in the global and non-global zones. Because the agent is not required for the non-global zone, you can remove it. To remove the Device Manager agent from the non-global zone: 1.
NOTE: To return the SED mode to all after installing the Device Manager agent, exclude the Java process used by the Device Manager agent from the SED protection targets. For details, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Administrator Guide.
• Verify that the file system mounted on the host matches that defined in /etc/fstab. • Verify that the network settings (such as those in the hosts file) are correct. NOTE: Do not try to install the Device Manager agent on an HP-UX workstation. If you do, the installation fails and the following message appears: ERROR: Could not apply the software selection "HDVMAgent" because there are no product variations that are compatible with the destination host(s).
3. In the installation window, click Install next to Device Manager Agent. If the installation window does not display automatically, run the following command: DVD-drive\AGENTS\HDVM\Windows\ setup.exe NOTE: To install the Device Manager agent and automatically configure the appropriate settings for Replication Manager operation, click Install next to Replication Manager add-on. 4. Enter the required information when prompted. 5. Log out. 6.
Related topics • Verifying agent installation conditions, page 41 • Agent installation prerequisites, page 45 • Device Manager agent post-installation tasks, page 52 Device Manager agent post-installation tasks After the Device Manager agent installation completes, additional tasks may be required, depending on the previous version of the agent that was installed.
Resetting the service execution user (Windows) After an update or recovery installation in Windows, the agent service execution user setting reverts to the default (LocalSystem). If the agent execution user is not LocalSystem, change this setting after the installation. To reapply the setting, go to Windows Computer Management and modify the HBsA Service service account information.
Agent installation
4 Removing P9000 Command View AE Software This module describes how to remove P9000 Command View AE Software and components. Removing P9000 Command View AE Software server You can remove P9000 Command View AE Software when you no longer need to manage storage systems and hosts.
To remove P9000 Command View AE Software: 1. Log on to Windows as the administrator. 2. Navigate to Start > Settings > Control Panel. 3. Double-click Add or Remove Programs. 4. In the Add or Remove Programs window, select HP P9000 Command View Advanced Edition Suite. 5. Click Remove. 6. Follow the on-screen instructions. When P9000 Command View AE Software is removed, the Removal Complete window appears.
• For HP-UX: Verify that the file system mounted on the host matches that defined in /etc/fstab. • If you perform another operation while the Device Manager agent is being removed, the operation terminates with an error. If a program related to the Device Manager agent is installed on the host when this occurs, some Device Manager agent data may remain on the host.
Double-click Add or Remove Programs. In the Add or Remove Programs window, select Device Manager agent. Click Remove. • Change directories to Device-Manager-agent-installation-folder\bin\ and run agent_uninstShortcut.bat. For Windows Server 2008 or Windows Server 2008 R2: • In the Server Core environment, enter the following command at the prompt that displays when you log in: agent_uninstShortcut.bat. When Device Manager agent is removed, the InstallShield Wizard Completed window appears.
5 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
• You no longer have to manually update information when an upgrade installation of is performed; settings in the Tiered Storage Manager properties file are automatically inherited.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: Continuous Access Asynchronous • XP Continuous Access Asynchronous • Continuous Access XP Asynchronous • Continuous Access XP Extension This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Journal Continuous Access Journal • XP Continuous Access Journal • Continuous Access XP Journal • P9000 Continuous Access Journal Th
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: LUN Manager • LUN Manager • XP LUN Manager This abbreviation is used when it is not necessary to distinguish the following products: • Open Volume Management Open Volume Management • XP Virtual LVI/LUN (VLL) • Security Manager XP • XP Data Shredder • LUN Configuration and Security Manager XP (Virtual LVI) This abbreviation is used when it is not necessary to distinguish the f
A Performing unattended installation and removal This appendix describes unattended installation and removal operations. Performing a P9000 Command View AE Software server unattended installation P9000 Command View AE Software provides an unattended feature so that you do not need to provide responses during installation. You can perform an unattended installation by creating and executing a script file when the conditions on multiple management servers are the same.
Property Name Details Default Value Windows: For a new installation: Specify the directory for database files. HINST_DBDIR#2 value-specified-for-HINST_INSTDIR \ database Linux: /var/value-specified-for-HINST_INSTDIR/ database For a new installation: Specify the IP address or host name of the management server. HINST_IPADDRESS#3 Host name obtained by the hostname command.
Property Name #1 Details Default Value program-files-folder indicates the following location: • For Windows x86: The folder specified in the Windows system environment variable %ProgramFiles% • For Windows x64 or IPF: The folder specified in the Windows system environment variable %ProgramFiles(x86)% #2 When installing in a cluster environment, default values are not specified automatically. You must explicitly specify values.
2. Open a command window or a PowerShell window and navigate to DVD-drive\HCS\. NOTE: This is the location of the installer program (setup.exe). In Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2, use the command prompt or PowerShell window you opened as the administrator. 3. Enter the following command: • In a command window: > setup.exe /v"/qr property-name=value" To specify a value that contains a space, add a backslash and quotation mark (\") before and after the value.
When the installation completes, the result is written in the HInstReport.txt file in the /tmp directory. If you see SUCCESS in the summary section of the file, the installation was successful.
Property Name Details Default value Specify the interval of HiScan.
Property Name Details Default value Specify whether to overwrite the settings during an overwrite installation. enable: Overwrite the settings disable: Do not overwrite the settings configOverwrite (optional) disable Caution: If you enable overwriting installation of the Device Manager agent, the user ID and password used for communication with the Device Manager server are set to the default.
Related topics • • • • • Verifying agent installation conditions, page 41 Agent installation prerequisites, page 45 Prerequisites for Device Manager agent unattended installation, page 67 Verifying the Device Manager agent unattended removal, page 74 Device Manager agent post-installation tasks, page 52 Installing a Device Manager agent on a UNIX host (unattended installation) An unattended installation is one that has the user input stored in a script file and then read from that file.
Return value# Description Action The following are likely causes: • There is insufficient free disk space. Secure the required disk space, and perform the installation again. • The host operating system is not supported. Verify that the operating system is supported. • A program other than Device Manager agent is either being installed or removed. Wait for the current process to finish, and then remove the Device Manager agent again. • The software that provides the Java execution environment cannot run.
Return value# Description Action 0x95 The Device Manager agent functionality setup succeeded. However, an error may have occurred while setting up Replication Manager application agent functionality. Verify that the operating system is supported and the required updates have been applied, and then perform installation again. 0x96 The user attempting this operation does not have Administrator permissions. Retry the operation using a user ID with Administrator permissions.
3. Execute the following command at the command prompt: NOTE: In Windows Server 2008 or Windows Server 2008 R2, use the command prompt you started as administrator. copy-destination-folder\agent_uninstShortcut.bat /s 4. To check the success of the removal, enter the following command: > echo %ERRORLEVEL% If the returned value is 0x00, the Device Manager agent is successfully removed. 5. Delete the copy of agent_uninstShortcut.bat you made in step 2.
Verifying the Device Manager agent unattended removal When unattended removal of the Device Manager agent completes, check the returned values shown in Table 22 to determine the result. Table 22 Device Manager agent unattended removal returned values Return value# Description Action 0x00 Normal termination -The following are likely causes: • A program other than the Device Manager agent is either being installed or removed.
B Ports This appendix describes the ports used for P9000 Command View AE Software. For a complete list of system requirements, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Release Notes. P9000 Command View AE Software server ports P9000 Command View AE Software uses the ports described in Table 23. For more information, see HP StorageWorks P9000 Command View Advanced Edition Suite Software Administrator Guide.
Port Number Description Change the settings of either the product currently using the port, or the port number used by Common Component. 23015/tcp to 23018/tcp 23025/tcp 23026/tcp If the port is in use by another product Port number used by Common Component. 23032/tcp NOTE: If Common Component has already been installed and you changed its settings to use different port numbers, you can install the Device Manager server by using those ports. You do not need to reset the values to the default ports.
Glossary This glossary defines the special terms used in this document. Click the desired letter at the bottom of each page to display the glossary entries that start with that letter. allocated volume A volume for which one or more host paths are defined. cache A set of RAM (Random Access Memory) modules used to store data temporarily. capacity The amount of data storage space available on a drive or storage system.
HBA Host bus adapter host group A means of segregating hosts by operating system. HSD Host storage domain. A group defined in Device Manager that is used to strengthen the security of volumes in storage systems. By associating and grouping hosts and volumes by storage system port, host storage domains can be used to restrict access from hosts to volumes. Device Manager defines the host groups set up with the storage system LUN security function as host storage domains.
pair status The current status of the copy pair. pool A set of volumes that are reserved for storing Snapshot data or Thin Provisioning write data. pool volume (pool-VOL) A logical volume that is reserved for storing snapshot data for Snapshot operations or write data for Thin Provisioning. P-VOL (primary volume) The source volume that is copied to another volume using the volume replication functionality of a storage system. properties files The files that define the operating environment.
web client browser WWN Worldwide name. A node name that is unique.
Index A agent modifying agent services, 43 modifying properties, 52 registering firewall exceptions, 53 resetting service execution user, 53 Solaris non-global zone, 48 agent configuration HiScan execution, 44 RAID Manager, 44 agent installation AIX precautions, 48 HP-UX prerequisites, 49 Linux prerequisites, 49 prerequisites, 41, 43, 45, 46 server information, 43 Stack Execution Disable function, 48 unattended, 67, 69, 70 unattended Windows, 69 UNIX, 51 Windows, 50 agent removal, 56 prerequisites, 56 unatt
L Linux agent installation prerequisites, 22 kernel parameters, 22 server installation, 32 server installation prerequisites, 15, 16, 22 shell restrictions, 22 Linux prerequisites agent installation, 49 firewall changes, 49 Linux unattended installation server, 66 M management client, 12 management server, 11 installation information, 18 memory heap size server installation, 19 N non-global zone removing, 48 P password changing, 33 port number validation server installation, 22 R RAID manager agent conf
server removal, 55 Linux, 56 prerequisites, 55 Windows, 55 server settings unattended installation, 63 server unattended installation prerequisites, 65 properties, 63 service execution user resetting, 53 setup.exe, 66, 69, 70 shell restrictions Linux, 22 Red Hat Enterprise Linux, 25 SUSE Linux Enterprise Server, 26, 29 short names automatic generation, 47 Solaris agent installation prerequisites, 47 storage tiers, 22 SUSE Linux Enterprise Server /etc/security/limits.conf, 29 /etc/sysctl.
Windows unattended removal agent, 72 84
