HP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide Part number: TB581-96080 Fifth edition: November 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 Prerequisites for basic configurations ...........................................................................................
Using event notifications ...................................................................................................... 42 Synchronizing databases ..................................................................................................... 43 3 Agent installation ............................................................................. 45 Planning for Device Manager agent installation ............................................................................
Installing the server in a Linux environment (unattended installation) .......................................... Performing a Device Manager agent unattended installation .......................................................... Prerequisites for Device Manager agent unattended installations .............................................. Installing a Device Manager agent on a Windows host (unattended installation) ........................
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 requirements ..................................
Preface This manual provides information about installing and removing P9000 Command View AE Software.
Preface
1 Overview This chapter provides basic system configuration information for P9000 Command View AE Software. Basic system configuration P9000 Command View AE Software can manage different storage systems. A basic configuration must include a management server and appropriate components. Figure 1 shows a basic system configuration.
Provides user account management, security monitoring, and other functions common to all P9000 Command View AE Software products. • Device Manager server The component used by P9000 Command View AE Software to manage storage system volumes. • Tiered Storage Manager server The component used by Tiered Storage Manager to manage storage system volume migration. • Replication Manager server The component used by Replication Manager to manage storage system volume replication.
• The Device Manager agent is installed only on the pair management server used to centrally manage copy pairs. • The Host Data Collector component is installed on the management server (from a silent installation initiated by the integrated installer). NOTE: Other configurations are possible. For more information, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide and the HP P9000 Replication Manager Software Configuration Guide.
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 using an earlier software version, upgrade to 6.x and then to 7.0 or later.
2 P9000 Command View AE Software server installation This module describes how to install and set up servers. Planning for server installation Before you install the P9000 Command View AE Software server, verify the 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 required information. NOTE: HP recommends accepting default values when available.
NOTE: The expected volume and copy pair counts below are based on the default memory heap size.
Prerequisites for server installation locations (new installations only) You can change the default installation location for the server . If you change the destination, ensure that the path adheres to the restrictions in Table 1. Table 1 Server installation path requirements Condition Requirements Absolute path length 64 bytes maximum Windows: Allowed characters A to Z, a to z, 0 to 9, periods (.
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 to Z, a through z, 0 to 9, periods (.), underscores (_), left parentheses ( ( ), right parentheses ( ) ), single-byte spaces, backslashes (\), and colons (:) Linux: A to Z, a to z, 0 to 9, periods (.
• Installing P9000 Command View AE Software in a Linux environment, page 32 Determining memory heap size Estimate the number of volumes and copy pairs managed by P9000 Command View AE Software (resource count) to determine the memory heap size. Set the larger required memory heap size for the volume count and the memory heap size for the copy pair count. NOTE: When changing settings to lower values, remove and re-install P9000 Command View AE Software.
Memory Heap Size Environment Managed Resources Small (Min: 128 MB, Max: 256 MB) Medium (Min: 256 MB, Max: 512 MB) Large (Min: 512 MB, Max: 1,024 MB) Legend: -- : You cannot specify this memory heap size.
Condition Requirements Windows: Allowed characters A to Z, a through z, 0 to 9, periods (.), underscores (_), left parentheses ((), right parentheses ()), single-byte spaces, backslashes (\), and colons (:) Linux: A to Z, a to z, 0 to 9, underscores (_), and forward slashes (/) Windows: • Do not include consecutive spaces. • Do not include a period or space at the end of a folder name. Other conditions • Do not use parentheses, except when the path includes the Program Files (x86) directory.
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 Installer Check value Operating System Initial Value HiRDB Common Component kernel.shmall 692147456 268435456 26214400 26214400 Table 7 Kernel parameter values for /etc/sysctl.conf (2/2) Kernel Parameter Device Manager Tiered Storage Manager Software Replication Manager Software fs.file-max 108109 512 512 kernel.threads-max 162 30 30 kernel.msgmni 44 0 0 4th parameter of kernel.sem 10 1 1 2nd parameter of kernel.sem 122 50 50 kernel.
+ value-for-Tiered-Storage-Manager + value-for-Replication-Manager + value-for-HiRDB • All other kernel parameters and shell restrictions: 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.
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.
• • • • Common Component Device Manager Tiered Storage Manager Replication Manager 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.conf (1/2) Kernel Parameter Installer Check value Operating System Initial Value HiRDB Common Component fs.file-max 213556 50525 53898 53898 kernel.threads-max 8598 8192 576 184 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 } • 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-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.
• Installing P9000 Command View AE Software in a Linux environment, page 32 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.
To install P9000 Command View AE Software: 1. Log on to Windows as the administrator. 2. Insert the installation DVD. 3. Click Install in the window that appears. NOTE: If the installation window does not display automatically, run the following command: DVD-drive\HCS\setup.exe 4. When you are prompted, enter the required information. 5. In the Installation Completed window, select the When installation completes, open the Device Manager GUI check box. 6. Click Finish.
NOTE: If the integrated installation media is automatically mounted (Red Hat Enterprise Linux only), unmount the media and then re-mount it without specifying the noexec mount option. These characters can be specified in the mount path of a DVD-ROM: A to Z, a to z, 0 to 9, underscores (_), forward slashes (/).
Registering licenses Before you can use P9000 Command View AE Software to operate and manage storage systems and hosts, you must register a license key for each product. To register a license key for a product: 1. In the product login window, click Licenses. 2. Add the license key. 3. Click Save. License Information by Product is updated with the license information for the associated product.
6. From the list of users in the Users tab, select a user account and click Assign User Groups. 7. Register the account into the group AdminGroup. AdminGroup is a built-in user group. 8. On the Administration tab, click Users and Permissions. 9. In the tree view, select the user account and click Change Permission. 10. From All Applications, select the Admin, Modify, View, and Execute check boxes.
User management permissions • Admin allows the user to manage users and security for all P9000 Command View AE Software products. This permission can be set in conjunction with assigned roles for each product. Tiered Storage Manager CLI permissions These permissions are required when using the Tiered Storage Manager CLI. In addition, All Resources must be assigned and roles must be set. • Admin: Allows the user to view information about Tiered Storage Manager resources and tasks.
Roles Built-in user group name Description PeerGroup This user group applies only to Device Manager agents and files server management software. Users that belong to this group and have no other P9000 Command View AE Software permissions are not allowed to log in to P9000 Command View AE Software, nor can they view resource information. The HaUser account is assigned to this group after installation completes.
Backing up databases Back up databases after upgrades. Refreshing storage systems Always refresh storage systems. Refreshing virtualization server information If Device Manager manages virtualization servers, refresh the virtualization server information. Resetting user accounts After upgrading from these versions, reset user accounts: • 5.00 to 5.10-04 • 5.50 to 5.50-02 • 5.60 Resetting roles and permissions When upgrading from 7.1.0 or earlier, reset roles and permissions.
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.
Resetting user accounts To improve user account security from versions earlier than 5.7, change user passwords. To change the password for a user account: 1. Log in to Device Manager using the System account. 2. On the Administration tab, click Users and Permissions. 3. Select the target user. 4. Click Change Password. 5. Type the new password and verify it. 6. Click OK. 7. Confirm that the user can log in with the new password. Resetting roles and permissions When upgrading from 7.1.
Before upgrading From version 6.x and earlier Device Manager permissions (roles) Y Tiered Storage Manager permissions None Resource group User defined resource groups After upgrading Resource groups and permissions are released, but only the accounts remain registered. To restart Device Manager operations, do the following: Register user accounts in user groups. Allocate resource groups to user groups. Set roles to resource groups.
Before upgrading From version Device Manager permissions (roles) Tiered Storage Manager permissions Resource group 7.1.0 Y None All Resources User groups, resource groups, and roles are inherited. Operations can be restarted without performing any additional tasks. 7.1.0 Y None User defined resource groups User groups, resource groups, and roles are inherited. Operations can be restarted without performing any additional tasks.
For more information, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide. Synchronizing databases When you use Replication Manager, after you perform an upgrade or overwrite installation, you must synchronize the Replication Manager database and the P9000 Command View AE Software database to update the Replication Manager database to the latest configuration. To synchronize databases: 1. If Replication Manager Application Agent version 7.
P9000 Command View AE Software server installation
3 Agent installation This module describes how to install and set up Device Manager agents. Planning for Device Manager agent installation Before you install the Device Manager agent, verify the prerequisites and gather the information you need to perform the installation. Prerequisites for agent installation Before performing a new installation, gather the appropriate information for the installation wizard, including the installation folder.
• HiScan command execution schedule. Default: Daily at 2:30 AM. For RAID Manager: • Installation location. Default in Windows: Device Manager agent installation drive. • Default in UNIX: /HORCM • By default, copy pairs are not batch managed by the agent host (default is no).
Prerequisites for agent installation locations Before specifying an installation folder for the Device Manager agent, verify that the required disk space is available. When creating the installation location for the Device Manager agent, adhere to the naming conventions in Table 16. Table 16 Agent installation folder naming requirements Condition Requirements Maximum length 64 characters Allowed characters A to Z, a to z, 0 to 9, periods (.
Server host name allowed characters: A through Z, a through z, 0 through 9, hyphens (-), underscores (_), periods (.), and at signs (@) Other server host name conditions: Do not use a hyphen as the first or last character. • The server port number. This is used by the agent and the server. • User ID and password. This is the user account for logging in to the Device Manager server. The user account must belong to PeerGroup.
Related topics • • • • Prerequisites for agent installation, page 45 Agent installation prerequisites, page 49 Installing the Device Manager agent on a Windows host, page 54 Installing the Device Manager agent on a UNIX host, page 55 Agent installation prerequisites Before installing the Device Manager agent, review the general prerequisites and check the host settings and the status of each affected program to confirm that the host system is in the appropriate state.
• 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. To install an earlier version, first remove the Device Manager agent that is currently installed.
NOTE: The Microsoft terms for this functionality differ, depending on the Windows operating system. These terms can refer to the same functionality: • Terminal Services in the Remote Administration mode • Remote Desktop for Administration • Remote Desktop Connection Keep the following in mind when working with Windows remote desktop: • When using the remote desktop, connect to the console session of the target server in advance and ensure that no one else connects to your session.
Related topics • General prerequisites, page 49 • Installing the Device Manager agent on a UNIX host, page 55 Removing agents when using Solaris 10 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, it is installed in the global and non-global zones. Since 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.
Related topics • General prerequisites, page 49 • Installing the Device Manager agent on a UNIX host, page 55 Linux prerequisites Do not install Device Manager agents in Linux environments when symbolic links exist for the following directories: • /opt • /opt/HDVM and its subdirectories • /var • /var/opt • /var/opt/HBaseAgent and its subdirectories • /var/opt/HDVM and its subdirectories • /var/tmp Related topics • General prerequisites, page 49 • Installing the Device Manager agent on a UNIX host, page 55
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). • Do not create a symbolic link for any of the directories below. If you have already created a symbolic link by using any of the directories below, do not install the Device Manager agent.
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 • Prerequisites for agent installation, page 45 • Agent installation prerequisites, page 49 • Device Manager agent post-installation tasks, page 56 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.
To reapply the setting, go to Windows Computer Management and modify the HBsA Service service account information. Registering firewall exceptions (Windows) When you perform an unattended installation and you have Windows Firewall enabled, you must add port numbers to the firewall exceptions list. • The port number specified for the server.agent.port property in the server.properties file (Default: 24041/tcp) • The port number specified for the server.http.port property in the server.
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.
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. Related topics • Prerequisites for removing P9000 Command View AE Software server, page 59 Removing P9000 Command View AE Software from a Linux host Remove P9000 Command View AE Software from Linux hosts using the command line.
• 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.
4. Click Remove. You can also execute Device-Manager-agent-installation-folder\bin\ agent_uninstShortcut.bat. To remove agents from 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. NOTE: The following tasks that run the HiScan command remain after you remove Device Manager agent.
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.
Related information For additional information, see the following HP websites: • • • • • http://www.hp.com/ http://www.hp.com/go/storage/ http://www.hp.com/support/manuals/ http://www.hp.com/support/cvae/manuals/ http://www.hp.com/storage/spock/ Conventions This guide follows the conventions shown in Table 17 to refer to HP P9000 products.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Synchronous Continuous Access Synchronous • XP Continuous Access Synchronous • Continuous Access XP Synchronous • P9000 Continuous Access Synchronous This abbreviation is used when it is not necessary to distinguish the following products: Data Retention Utility • Data Retention Utility • XP Data Retention Utility • LUN Security XP Extension This abbreviat
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • Snapshot Snapshot • XP Snapshot • Snapshot XP • P9000 Snapshot This abbreviation is used when it is not necessary to distinguish the following products: Volume Shredder • Volume Shredder • XP Volume Shredder • P9000 Volume Shredder 66 Support and other resources
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 Details Default Value HINST_IGNORE_NETWORKING_CHECK Specify whether to continue the installation when the host name or IP address that was specified in HINST_IPADDRESS is not communicating with the network. FALSE • TRUE: Continue the installation • FALSE: Stop the installation. HINST_IGNORE_VIRTUAL_MEMORY_CHECK Specify whether to continue the installation when there is insufficient virtual memory. • TRUE: Continue the installation FALSE • FALSE: Stop the installation.
To access the prerequisite checker in Linux, run the prereqchk.sh file in DVD-ROM-mount-point/ HCS/Platform-name/ For system requirements, see the HP P9000 Command View Advanced Edition Suite Software Release Notes. To check task status, see the HP P9000 Command View Advanced Edition Suite Software User Guide.
• About post-installation tasks (overwrite or upgrade), page 37 Installing the server in a Linux environment (unattended installation) You can perform unattended server installations on Linux. To perform an unattended installation of the server in a Linux environment: 1. Log on to the Linux operating system as the root user. 2.
You must have the Device Manager agent installation folder ready for the new installation and configure the settings for basic setup by editing the HDVMAgent.conf file to provide basic setup values that are accessed during the unattended installation. The HDVMAgent.conf file is stored in the following location: • In Windows: DVD-drive:\AGENTS\HDVM\Windows\HDVMAgent.conf • In UNIX: DVD-ROM-mount-directory/AGENTS/HDVM/platform-name/HDVMAgent.conf NOTE: If HDVMAgent.
Property Name Details Default value If you specify a value other than N for HiScanPeriod, specify the timing for executing the HiScan command using one of the following methods: To specify execution at a scheduled time, use the following format: • Once an hour: Specify the time as mm. • Once a day: Specify the time as hh:mm. • Once a week: Specify the time as hh:mm.
Installing a Device Manager agent on a Windows host (unattended installation) An unattended installation is one that has the user input stored in a script file and then read from that file. To perform an unattended installation in Windows: 1. Log on to the Windows operating system with administrator permissions. 2. Open a command window or a PowerShell window, and change the directory to the location of the installer program (setup.exe).
2. Open a shell window, and change the directory to the location of the installer program (install.sh). NOTE: To perform basic setup tasks during the installation, change the directory to the location of the copy you made of the install.sh file. 3. Enter the following command: # install.sh -s [-u] Specify the -u option to perform basic setup during installation. 4.
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 being installed or removed. Wait for the current process to finish and perform the installation 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.
You can verify the returned values shown in Table 21 to determine the result. Table 21 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. Wait for the current process to finish, and then attempt to remove the Device Manager agent again. • A process for removing a related program failed.
Performing unattended installation and removal
B Ports This appendix describes the ports used for P9000 Command View AE Software. For a complete list of system requirements, see the HP P9000 Command View Advanced Edition Suite Software Release Notes. P9000 Command View AE Software server ports Ensure that P9000 Command View AE Software ports do not overlap with those used by other programs on the management server. Some ports can overlap with ports temporarily assigned by the operating system.
Port Number Description 23015/tcp to 23018/tcp 23025/tcp 23026/tcp Common Component ports 23032/tcp If the port is in use by another product Change the settings for the product that uses this port or change Common Component settings. NOTE: If Common Component is installed and you changed its ports, you do not need to reset the values.
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, 47 modifying properties, 56 registering firewall exceptions, 57 resetting service execution user, 56 agent configuration HiScan execution, 48 RAID Manager, 48 agent installation AIX precautions, 52 HP-UX prerequisites, 53 Linux prerequisites, 53 prerequisites, 45, 47, 49, 50 server information, 47 Stack Execution Disable function, 52 unattended, 71, 74, 75 unattended Windows, 74 UNIX, 55 Windows, 54 agent removal, 60 prerequisites, 60 unattended, 77, 78 unattended UNI
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, 53 firewall changes, 53 Linux unattended installation server, 71 M management client, 11 management server, 12 installation information, 18 memory heap size server installation, 19 P password changing, 34 port number validation server installation, 22 R RAID manager agent configuration, 48 Red Hat Enterprise
service execution user resetting, 56 setup.exe, 70, 74, 75 shell restrictions Linux, 22 Red Hat Enterprise Linux, 25 SUSE Linux Enterprise Server, 26, 29 short names automatic generation, 51 Solaris agent installation prerequisites, 51 storage tiers, 22 SUSE Linux Enterprise Server /etc/security/limits.conf, 29 /etc/sysctl.
