HP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide Part number: TB581-96359 Eleventh edition: October 2013
Legal and notice information © Copyright 2010, 2013 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 About basic system configurations ............................................................................................... Prerequisites for basic configurations ........................................................................................... DVD installations ..............
Built-in user groups ............................................................................................................. About post-installation tasks (overwrite or upgrade) ....................................................................... Post-installation tasks (overwrite or upgrade) ........................................................................... Backing up databases ........................................................................................................
Subscription service ............................................................................................................ Documentation feedback ..................................................................................................... Related information ................................................................................................................... Conventions .............................................................................................................
Figures 1 Command View AE Suite: Basic configuration ............................................................
Tables 1 Server installation path requirements ......................................................................... 16 2 Database file storage path and location requirements .................................................. 17 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 configuring HP StorageWorks P9000 Command View Advanced Edition Suite software.
Preface
1 Overview This chapter provides basic system configuration information for HP StorageWorks P9000 Command View Advanced Edition Suite. About basic system configurations HP StorageWorks P9000 Command View Advanced Edition Suite can manage different storage systems. A basic configuration must include a management server and appropriate components. The following figure shows a basic system configuration.
Provides user account management, security monitoring, and other functions common to all Command View AE Suite products. • Device Manager server The component used by Command View AE Suite 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 management server and management client communicate with each other using non-SSL protocol. • For copy pair management: • Command View AE Suite is configured for open-volume copy pair management at a single site. • Copy pairs are centrally managed from a pair management server. • For collecting information about managed hosts: • The Device Manager agent is installed only on the pair management server used to centrally manage copy pairs.
Programs installed by server administrators • Plug-in for Virtualization Server Provisioning Regarding upgrade installations The following software versions support an upgrade installation from the installation DVD. Version 5.0 or later: • Device Manager server • Tiered Storage Manager server Version 6.0 or later: • Replication Manager server When using an earlier software version, first upgrade to 6.x and then to 7.0 or later.
2 HP StorageWorks P9000 Command View Advanced Edition Suite server installation This module describes how to install and set up servers. Planning for server installation Before installing the HP StorageWorks P9000 Command View Advanced Edition Suite (Command View AE Suite) software on the server, verify the conditions and gather the information you need to perform the installation.
Windows: installation-destination-path\backup Linux: /var/installation-destination-path/backup • Memory heap size The expected volume and copy pair counts in the following table are based on the default memory heap size.
Condition Requirements Windows: • Do not include consecutive spaces. • Do not include a period or space at the end of a folder name. • Do not use parentheses, except when the path includes the Program Files (x86) directory. • Do not include a symbolic link and junction for the installation folder. • Do not specify the root of a drive as the destination.
Condition Requirements Windows: • Do not include consecutive spaces. • Do not include a period or space at the end of a folder name. • Do not use parentheses, except when the path includes the Program Files (x86) folder. • Do not include a symbolic link and junction for the installation folder. • Do not specify the destination as a folder directly under a drive (such as D:\ ). • Do not specify a network drive.
To determine the memory heap size, you estimate the number of volumes and copy pairs that are managed by Command View AE Suite (resource count). Then, you set the memory heap size to accommodate the LDEV count or the copy pair count, whichever is larger. Set the larger of the memory heap size for the LDEV count and the memory heap size for the copy pair count. NOTE: To decrease the current memory heap size, you must uninstall the Command View AE Suite, reinstall it, and then change the heap size.
Related topics • • • • • Server installation conditions , page 15 Memory heap size for Device Manager server, page 20 Server installation prerequisites, page 33 Installing Command View AE Suite on Windows, page 34 Installing Command View AE Suite on Linux, page 34 Memory heap size for Device Manager server The value that is set for the memory heap size depends on the numbers of LDEVs managed by HP StorageWorks P9000 Command View Advanced Edition Suite products.
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. • Do not use parentheses, except when the path includes the Program Files (x86) directory.
CAUTION: The following concerns storage tiers and upgrades Command View AE Suite to version 7.0 or later.
NOTE: Ensure that the maximum value set for a kernel parameter does not exceed the maximum value specified by the operating system. Related topics • Command View AE Suite server installation preparations, page 21 • Installing Command View AE Suite on Linux, page 34 • Modifying kernel parameter values and shell restrictions, page 32 Recommended Red Hat Enterprise Linux /etc/sysctl.
Tiered Storage Manager Software Replication Manager Software 162 30 30 kernel.msgmni 44 0 0 4th parameter of kernel.sem 10 1 1 2nd parameter of kernel.sem 125 50 50 kernel.shmmax 360349696 50000000 100000000 kernel.shmmni 497 0 0 kernel.shmall 477076480 100695040 100000000 Kernel Parameter kernel.threads-max Device Manager These formulas are for calculating kernel parameter values: • For kernel.
, 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 • • • • About setting kernel parameters and shell restrictions (Linux), page 22 Recommended Red Hat Enterprise Linux 5 /etc/security/limits.conf values, page 25 Recommended Red Hat Enterprise Linux 6 /etc/security/limits.
Shell Restriction nproc (soft/hard) Installer Check Value Operating System Initial Value 8358 Common Component HiRDB 8192 512 165 Table 9 Shell restriction values for Red Hat Enterprise Linux 5 /etc/security/limits.
• Device Manager • Tiered Storage Manager • Replication Manager The following tables show the shell restriction values you need to set. The formula for calculating these values follow the tables. Table 10 Shell restriction values for Red Hat Enterprise Linux 6 /etc/security/limits.
NOTE: The soft value must be less than or equal to the hard value. These settings depend on which Command View AE Suite products you are installing: • • • • Common Component Device Manager Tiered Storage Manager Replication Manager The following tables show the shell restriction values you need to set. The formula for calculating these values follow the tables. Table 12 Shell restriction values for Red Hat Enterprise Linux 6 /etc/security/limits.d/90-nproc.
Recommended SUSE Linux Enterprise Server /etc/sysctl.conf values Before installing Command View AE Suite on a SUSE Linux Enterprise Server system, set the kernel parameters for the /etc/sysctl.conf file. These settings depend on which Command View AE Suite products you are installing: • • • • 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.
The following formulas are for calculating the values for the kernel parameters: • For kernel.shmmax: 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 • About setting kernel parameters and shell restrictions (Linux), page 22 • Recommended SUSE Linux Enterprise Server /etc/security/limits.conf values, page 31 • Modifying kernel parameter values and shell restrictions, page 32 Recommended SUSE Linux Enterprise Server /etc/security/limits.conf values Before installing Command View AE Suite on a SUSE Linux Enterprise Server system, set the shell restrictions for the /etc/security/limits.conf file.
+ 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 • About setting kernel parameters and shell restrictions (Linux), page 22 • Recommended SUSE Linux Enterprise Server /etc/sysctl.
Command View AE Suite server installation When you install Command View AE Suite on the management server, use the installation procedure that is appropriate for the operating system you are using. Server installation prerequisites Before installing Command View AE Suite, review the information in “Planning for server installation” on page 15. If you are using a Linux management server, a 32-bit library package is required. You can obtain this package from Red Hat or Novell.
Installing Command View AE Suite on Windows Use the installation DVD for Command View AE Suite. 1. Log on to Windows as the administrator. 2. Insert the installation DVD. 3. Click Install in the window that opens. NOTE: If the installation window does not open, 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.
NOTE: If the integrated installation media is automatically mounted (Red Hat Enterprise Linux only), unmount the media and mount it again without specifying noexec. 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 Command View AE Suite to operate and manage storage systems and hosts, you must register a license key for each 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. Changing the system account password The system account is a default account that has user management and execute permission for Command View AE Suite.
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. This grants operating permissions for managing users and using Command View AE Suite products other than Device Manager.
• Modify: Allows the user to perform any operation from Tiers on the Resources tab, and migrate volumes. • Execute: Allows the user to view information about Tiered Storage Manager Software resources and execute Tiered Storage Manager tasks. • View: Allows the user to view information about Tiered Storage Manager resources and tasks. Replication Manager permissions • Admin: Allows the user to perform any operation within a resource group, with the exception of user management.
• Roles, page 37 About post-installation tasks (overwrite or upgrade) After a Command View AE Suite installation, set the information required by each installed product according to the version of each product before the overwrite or upgrade installation. When upgrading from version 7.1.0 or earlier, existing user accounts are migrated according to the previous environment. After upgrading, the storage administrator can modify user group and resource group assignments as necessary.
Related topics • Built-in user groups, page 38 • User permissions, page 37 • Roles, page 37 Backing up databases To prepare against failures, back up databases after completing the installation. NOTE: Backing up the database involves operations that stop HP StorageWorks P9000 Command View Advanced Edition Suite services. Do not attempt to access HP StorageWorks P9000 Command View Advanced Edition Suite during the database back up. 1.
Refreshing virtualization server information Device Manager virtualization server information must be refreshed to reflect the current configuration. Prerequisites Check the following information before proceeding.
7. Confirm that the user can log in with the new password. Roles and permissions after upgrades When upgrading from 7.1.0 and earlier, user roles or permissions can change. To verify user account status after upgrading, output the following CSV files: • user information (you can verify the user group for each user account). • user group information (you can verify the resource group or roles for each user group).
Before upgrading From version 6.x and earlier 6.x and earlier Device Manager permissions (roles) Y Y Tiered Storage Manager permissions Y Y Resource group All Resources User defined resource groups After upgrading User accounts are registered in built-in user groups according to Device Manager permissions. Depending on the user responsibilities, ask the storage administrator to review the allocation of user groups and resource groups to which the user belongs.
Before upgrading From version Device Manager permissions (roles) Tiered Storage Manager permissions Resource group After upgrading User groups, resource groups, and roles are inherited. 7.1.0 Y Y All Resources Depending on the user responsibilities, ask the storage administrator to review the allocation of user groups and resource groups to which the user belongs.
Using event notifications You can use event notifications in Tiered Storage Manager after upgrading HP StorageWorks P9000 Command View Advanced Edition Suite from 7.1.0 or earlier. 1. In the server.properties file for Device Manager, set the following: • server.mail.enabled • server.mail.smtp.host • server.mail.from • server.mail.errorsTo • server.mail.smtp.port • server.mail.smtp.auth • server.eventNotification.mail.to 2. Register SMTP authenticated users to Device Manager. 3.
HP StorageWorks P9000 Command View Advanced Edition Suite 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 on Windows: Device Manager agent installation drive. • Default on UNIX: /HORCM • By default, copy pairs are not batch managed by the agent host (default is No). NOTE: The host name of the machine where the Device Manager agent is installed must be no longer than 50 bytes.
• Enable batch management of copy pairs on the host on which the Device Manager agent is installed: Yes For more information, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide. NOTE: The host name of the machine where the Device Manager agent is installed must be no longer than 50 bytes.
Related topics • • • • Prerequisites for agent installation, page 47 Agent installation prerequisites, page 51 Installing the Device Manager agent on a Windows host, page 56 Installing the Device Manager agent on a UNIX host, page 57 Prerequisites for verifying server information Before installing a Device Manager agent, determine information about the Device Manager server (where the host information is sent). • The server IP address or host name. IPv6 addresses can be specified using global addresses.
• Installing the Device Manager agent on a UNIX host, page 57 Prerequisites for identifying RAID Manager When Device Manager is linked to RAID Manager and used to manage copy pairs, you must determine some information. • The location of the RAID Manager installation folder: • In Windows, the installation drive. • In UNIX, the installation directory. • The method used for managing copy pairs: • Batch managed on a Device Manager agent host.
• If you are running security monitoring programs, either temporarily stop them or change the settings so they do not prevent the installation. • Device Manager agent versions 5.7 and later are compatible with the Daylight Saving Time (DST) rules implemented in the United States and Canada in 2007. When using the Device Manager agent in these time zones, set the host operating system for the new DST rules according to information provided by the operating system vendor.
Host prerequisites for Windows If these conditions are not satisfied, Device Manager agent installation may fail or the Device Manager agent may not work properly. Before installing Device Manager agents, perform the following tasks: • 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. Command View AE Suite products for Windows support the Windows remote desktop functionality.
Removing agents when using Solaris 10 If the Device Manager agent (version 4.1- 5.1) was upgraded to 5.5 or later in an environment with the non-global zone specified, 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. 1. Log in to the non-global zone. 2.
Host prerequisites for Linux 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 • Host prerequisites, page 51 • Installing the Device Manager agent on a UNIX host, page 57 Allowing communication with Linux firewalls If you are installing on a Linux system that has a firewall
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.
6. Add host names to the hosts file: 1. Open the /etc/hosts file. 2. Confirm that the local host name and agent host name are present. If your host is running on Linux, enter the name of the local host in the line before the localhost entry. 3. Restart the Device Manager agent services.
Resetting the agent service execution user on Windows After an overwrite installation or upgrade on 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 account information.
Agent installation
4 Removing Command View AE Suite This module describes how to remove Command View AE Suite and its components. Removing Command View AE Suite server You can remove Command View AE Suite when you no longer need to manage storage systems and hosts. Removing Command View AE Suite deletes all properties files, database files, log files, and other files as well.
6. Follow the on-screen instructions. When Command View AE Suite is removed, the Removal Complete window appears. When you remove Command View AE Suite version 7.4.1 or earlier that is installed on a drive other than the system drive, the temp folder might appear directly below the drive where Command View AE Suite was installed. You can delete the temp folder.
• hdvmagt_setting • HiScan NOTE: If you remove the Device Manager agent while HiScan is executing, the process for removing the agent is canceled. If this occurs, wait until the command terminates, and then remove the agent. • hldutil • TIC • If the host operating system is Solaris 10 or 11, do not specify settings related to a system zone. • When the process for removing the Device Manager agent starts, the Device Manager agent and any add-on modules automatically stop.
Removing Device Manager agents from Windows hosts (other than Windows Server 2008/2012 Server Core) Remove Device Manager agents from Windows hosts (other than Windows Server 2008, Windows Server 2008 R2, and Windows 2012 Server Core) using Programs and Features. NOTE: Instead of using the Windows GUI, you can also execute Device-Manager-agent-installation-folder\bin\agent_uninstShortcut.bat from the command line.
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.
Conventions This guide follows the conventions shown in Table 21 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: Data Retention Utility • Data Retention Utility • XP Data Retention Utility • LUN Security XP Extension This abbreviation is used when it is not necessary to distinguish the following products: External Storage • XP External Storage Software • External Storage XP • External Storage This abbreviation is used when it is not necessary to distinguish the following products: Fast
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 68 Support and other resources
A Unattended installation and removal This appendix describes unattended installation and removal operations. Command View AE Suite server unattended installation Command View AE Suite 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: HINST_DBDIR2 HINST_IPADDRESS3 HINST_DBBACKUP4 For a new installation: Specify the directory for database files. For a new installation: Specify the IP address or host name of the management server.
Property Name Details Default Value Specify whether to continue the installation when there is insufficient unused capacity: HINST_IGNORE_CAPACITY_CHECK • TRUE: Continue the installation FALSE • FALSE: Stop the installation. 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.
Prerequisites for Command View AE Suite server unattended installation Before performing an unattended installation of Command View AE Suite server, review system requirements information. 1. Run Tiered Storage Manager tasks when upgrading from 7.1.0 or earlier: • If there are incomplete tasks (standby, running, being canceled), go to the Tasks & Alerts tab and execute or cancel the tasks. After upgrading, register the canceled tasks as new. 2. 3.
When the installation completes, the result is written in the HInstReport.txt file on the desktop. If you see SUCCESS in the summary section of the file, the installation was successful.
Prerequisites for Device Manager agent unattended installations Before performing an unattended installation of the Device Manager agent, verify the host requirements and system prerequisites and set up the installation machine. 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.
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 uses a script file (HDvMAgent.conf) that contains the necessary user input. 1. Log on to the Windows operating system with administrator permissions. 2. Open a command or PowerShell window, and change the directory to the location of the installer program (setup.exe). NOTE: To perform basic setup during installation, change the directory to the location where the setup.exe and HDvMAgent.
3. Enter the following command: # install.sh -s [-u] Specify the -u option to perform basic setup during installation. 4. To check the success of the installation, enter the following command: # echo $? If the return value is 0x00, the installation completed successfully. When starting the installer from a DVD-ROM, these characters can be specified in the mount path: A to Z, a to z, 0 to 9, underscores (_), forward slashes (/).
Return value (hexadecimal) 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 (hexadecimal) 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, Windows Server 2008 R2, or Windows Server 2012, use the command prompt you started as administrator. copy-destination-folder\agent_uninstShortcut.bat /s 4. To verify removal, enter the following command: echo %ERRORLEVEL% If the returned value is 0x00, the Device Manager agent is removed. 5. Delete the copy of agent_uninstShortcut.bat you made in step 2.
Verifying the Device Manager agent unattended removal When the unattended removal of the Device Manager agent completes, check the returned values and verify them against the following table. Table 25 Device Manager agent unattended removal returned values Return value (hexadecimal) Description Action 0x00 Normal termination -The following are likely causes: • A program other than the Device Manager agent is either being installed or removed.
Unattended installation and removal
B Command View AE Suite ports This appendix describes the ports used for HP StorageWorks P9000 Command View Advanced Edition Suite (Command View AE Suite). For a complete list of system requirements, see HP P9000 Command View Advanced Edition Suite Software System Requirements. Command View AE Suite server ports Ensure that Command View AE Suite 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 If the port is in use by another product 23031/tcp Common Component port when the management server operating system is Windows Change the settings for the product that uses this port or change Common Component settings. Host Data Collector ports Change the settings for the product that uses this port or change Host Data Collector settings.
Glossary allocated volume A logical device (LDEV) for which one or more host LUN 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 physical storage device, generally measured in bytes (MB, GB, TB, and so on). CLI command line interface CLPR See cache logical partition. control unit (CU) Created in an storage system. Also called a CU image.
external path A path from a storage port of a storage system to a volume on a connected external storage system. external volume A logical volume whose data resides on drives that are physically located in an externally connected storage system. FC fibre channel FCoE fibre channel over Ethernet. An encapsulation of fibre channel frames over Ethernet networks. This allows fibre channel to use 10-gigabit Ethernet networks (or higher speeds) while preserving the fibre channel protocol.
JVM Java Virtual Machine JWS Java Web Start LAN local area network. A computer network that spans a relatively small geographic area, such as a single building or group of buildings. LDAP Lightweight Directory Access Protocol LDEV (logical device) A volume created in a storage system. See also LU.
properties file A file that defines aspects of the operating environment. The operating environment can be modified by changing the appropriate properties file. RACF (Resource Access Control Function) Functionality for controlling user authentication and resource access on the mainframe host. RADIUS Remote Authentication Dial In User Service RAID redundant array of independent disks A collection of two or more disk drives that presents the image of a single logical disk drive to the system.
in a high-speed hardware tier, and a data area that has a low I/O load is placed in a low-speed hardware tier. This document refers to the storage area that is created by using Smart as a Smart pool, an actual volume that is one of the volumes making up a Smart pool as a Smart pool volume, and a virtual volume that is created by a Smart pool as a Smart volume.
WWN is essential for defining the SANtinel™ parameters because it determines whether the open systems host is to be allowed or denied access to a specified logical unit or a group of logical units. WWN nickname World wide name nickname. A name that is set for the WWN of an HBA that identifies which HBA to operate on. The WWN nickname easily identifies accessible HBAs that are registered in a host group.
Index A agent modifying agent services, 49 modifying properties, 58 registering firewall exceptions, 59 resetting service execution user, 59 agent installation prerequisites, agent removal, agent configuration HiScan execution, 50 RAID Manager, 51 agent installation AIX precautions, 54 HP-UX prerequisites, 55 Linux prerequisites, 55 prerequisites, 47, 49 - 51, 53 server information, 50 Stack Execution Disable function, 54 unattended, 73 - 74, 76 - 77 unattended Windows, 76 UNIX, 57 Windows, 56 agent removal
K kernel parameters, 22 Linux, 22 Red Hat Enterprise Linux, 23 SUSE Linux Enterprise Server, 29 L Linux kernel parameters, 22 server installation, 34 server installation prerequisites, 15 shell restrictions, 22 Linux prerequisites agent installation, 55 firewall changes, 55 Linux unattended installation server, 73 logical group status, 44 M management client, 11 management server, 12 installation information, 18 memory heap size server installation, 18, 20 P password changing, 36 port number validation s
S server installation, 34 assigning resource groups, 40, 45 changing kernel parameter values, 32 changing shell restriction values, 32 creating user, 36 database backup, 20 database destination, 17 destination, 16 Device Manager roles, 37 Linux, 34 management server, 18 memory heap size, 18, 20 port number validation, 22 prerequisites, 15, 33 refreshing storage systems, 40 registering licenses, 36 Replication Manager Software operation permissions, 37 resetting user account, 41 system account password, 36 t
W Windows additional installation files, 13 agent execution user, 59 agent firewall exceptions, 59 agent installation, 56 agent installation prerequisites, 47, 53 remote access, 53 server installation, 34 server installation prerequisites, 15 Windows (IPF) server installation prerequisites, 15 Windows (x64) server installation prerequisites, 15 Windows (x86) server installation prerequisites, 15 Windows Remote Desktop functionality, 53 Windows unattended installation agent, 76 server, 72 Windows unattended
