HP P9000 Command View Advanced Edition Suite Software Administrator Guide (Web Version) Part number: TB581-96361 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 .............................................................................................. 21 1 System configuration and requirements ............................................... 23 System configuration ................................................................................................................. Hardware configuration ...................................................................................................... Software configuration ......................
System configuration for using a virtual command device server configuration to manage copy pairs .................................................................................................................. System configuration for using an SVP configuration to manage copy pairs (when copy pairs are defined in a configuration definition file) ...................................................................
Controlling management client access to the management server .................................................. 110 Changing the password-encoding level in the Device Manager CLI and the Tiered Storage Manager CLI ........................................................................................................................................ 112 5 Configuring Device Manager for use with related products .................. 113 Linking with PA .........................................................
Format of the perf_cmddev.properties file ...................................................................... Controlling the SLP service ....................................................................................................... Software prerequisites for using the service discovery function ................................................ Starting and stopping the SLP service ..................................................................................
Procedure for migrating databases ..................................................................................... Installing P9000 Command View AE Suite on the migration-destination server ......................... Exporting databases from the migration-source server ........................................................... Exporting databases in a non-cluster configuration ......................................................... Exporting databases in a cluster configuration ......................
12 Setting up Host Data Collector ....................................................... 261 Installing Host Data Collector ................................................................................................... Prerequisites for installing Host Data Collector ..................................................................... Installing Host Data Collector (Windows) ............................................................................. Installing Host Data Collector (Linux) ..........
14 Support and other resources .......................................................... 333 Contacting HP ........................................................................................................................ HP technical support ......................................................................................................... Subscription service .......................................................................................................... Documentation feedback .....
logger.hbase.MaxFileSize ................................................................................................. Device Manager dispatcher properties (dispatcher.properties file) ................................................. server.dispatcher.message.timeout ...................................................................................... server.dispatcher.message.timeout.in.processing ................................................................... server.dispatcher.daemon.
HTTPPort ......................................................................................................................... 369 HTTPSPort ........................................................................................................................ 370 B Tiered Storage Manager server properties ........................................ 371 Tiered Storage Manager server property files .............................................................................
C Host Data Collector properties ......................................................... 385 Host Data Collector property files ............................................................................................. Changing Host Data Collector properties ............................................................................ Properties related to Host Data Collector operation (hdcbase.properties file) ................................... hdc.service.localport ...................................
server.agent.maxMemorySize ............................................................................................ server.agent.shutDownTime ................................................................................................ server.agent.JRE.location ................................................................................................... server.http.entity.maxLength ............................................................................................... server.http.
Figures 1 Basic system configuration ........................................................................................ 23 2 Most secure configuration: separate management LAN plus firewall .............................. 27 3 Second-most secure configuration: separate management LAN plus firewalled devices ..................................................................................................................
23 Example of a configuration in which the management server is used as a bridge between networks ................................................................................................................ 92 24 CIM components for Device Manager ..................................................................... 151 25 Example of a system configuration in which performance information of a storage system is acquired .....................................................................................
Tables 1 Maximum number of management resources .............................................................. 30 2 Appropriate memory heap size for Common Component ............................................. 31 3 Appropriate memory heap size for the Device Manager server ..................................... 33 4 Hosts that can be managed by Device Manager ......................................................... 35 5 Host management software supported by Device Manager .................................
26 Port number that must be registered as a firewall exception between the Host Data Collector computer and a host ............................................................................................... 86 27 Port numbers that must be registered as firewall exceptions between the management server and an SMI-S provider ...................................................................................
57 Settings for registering the HBase Storage Mgmt Common Service as a resource (for Microsoft Cluster Service) ....................................................................................... 174 58 Settings for registering the HBase Storage Mgmt Web Service as a resource (for Microsoft Cluster Service) .....................................................................................................
80 Recommended property values for a host that will manage 100 or more LUs (when the host is using a volume manager in HP-UX) ................................................................ 232 81 Resident processes of the Device Manager agent (Windows) ...................................... 233 82 Resident processes of the Device Manager agent (UNIX) ............................................ 233 83 Items that can be set by using the hdvmagt_setting command .....................................
112 Meanings of the operation targets (Res) output to the audit log ................................... 303 113 Information output in message details ...................................................................... 304 114 Commands output in message details ...................................................................... 305 115 Targets output in message details ............................................................................ 305 116 Options output in message details ................
Preface This manual explains how to configure HP StorageWorks P9000 Command View Advanced Edition (abbreviated hereafter as Device Manager), HP StorageWorks P9000 Tiered Storage Manager (abbreviated hereafter as Tiered Storage Manager), and HP StorageWorks P9000 Command View Advanced Edition Suite Common Component (abbreviated hereafter as Common Component), and also explains how to set up an environment as well as how to troubleshoot management servers.
Preface
1 System configuration and requirements This chapter describes the system configuration and system requirements for Device Manager and Tiered Storage Manager. System configuration The following figure shows a basic system configuration in which Device Manager and Tiered Storage Manager are used. Figure 1 Basic system configuration A TCP/IP network must be used to connect a management server to management clients, and the management server to storage systems.
Management server A management server is a computer that integrates and manages storage systems and host computers. P9000 Command View AE Suite is installed on this computer. The management server supports an active-standby type clustering configuration consisting of two computers. Management client A management client is a computer used to operate Device Manager and Tiered Storage Manager. Host (application server) A host (application server) is a computer that uses the volumes in a storage system.
NOTE: Only Host Data Collector can be installed on a separate computer. Device Manager agent The Device Manager agent component collects information about hosts or storage systems that it then reports to the Device Manager server.
Common security risks System administrators frequently separate production LANs from management LANs. In such cases, management LANs act as a separate network, which isolates management traffic from a production network and reduces the risk of security-related threats. If a management controller such as the SVP exists on a production LAN, the storage systems are left open for access by any entity on the IP network.
Figure 2 Most secure configuration: separate management LAN plus firewall Level 2 security: Placing managed devices behind the firewall and creating a separate management LAN In this configuration, the machine hosting the Device Manager server and all other application servers must be single-homed, and the actual managed devices must be separated from Device Manager by a firewall.
Figure 3 Second-most secure configuration: separate management LAN plus firewalled devices Level 3 security: Dual-homed management servers and creating a separate management LAN In this configuration, the management servers themselves act as the intersection point between the management LAN and a production LAN. The server running Device Manager or management applications is dual-homed.
Figure 4 Third-most secure configuration: dual-homed management servers plus separate management LAN Level 4 security: A flat network Here, the management application servers, managed devices, and managed clients all coexist on the same network. This configuration is the least secure, though it is the most flexible. It affords no protection to any of the components required for storage management operations, so management application server hardening is paramount.
Figure 5 Least secure configuration: flat network Management server requirements This section describes the system requirements for the management server. Maximum number of resources that can be managed There are upper limits to the number of resources that can be managed by Device Manager, Tiered Storage Manager, and Replication Manager. HP recommends that you operate each product within these limits.
Number of paths = number of LDEVs x average number of paths per LDEV Related topics • Changing Device Manager server properties, page 338 • server.cim.support.job, page 343 Changing the memory heap size of Common Component To change the memory heap size for Common Component, use the hcmdschgheap command.
If you manage both open volumes and mainframe volumes, calculate the number of copy pairs by using the following formula: number-of-open-system-copy-pairs x 6 + number-of-mainframe-systemcopy-pairs To change the memory heap size: 1. Stop the P9000 Command View AE Suite product services. 2. Check the current setting for the memory heap size. In Windows: installation-folder-for-Common-Component\bin\hcmdschgheap /print 3.
Information to collect in advance • Number of LDEVs to be managed Table 3 Appropriate memory heap size for the Device Manager server Memory heap size OS Managed resource Windows (IPF) Window(x86), Window(x64) or Linux 256 MB (Min: 128 MB) 512 MB (Min: 128 MB) 1,024 MB (Min: 128 MB) Number of LDEVs per storage system 2,000 or less 2,001 or more -- Number of LDEVs per storage system 2,000 or less 2,001 to 6,000 6,001 or more Legend: --: You cannot specify this memory heap size.
P9000 Command View AE Suite products can be used with the following JDK versions: Operations to complete in advance • Check the JDK for P9000 Command View AE Suite products For details, see HP P9000 Command View Advanced Edition Suite Software System Requirements. To change the JDK: 1. Stop the services of P9000 Command View AE Suite products. 2. Execute the command below, and in the window that opens, select the JDK you want to use.
Hosts that can be managed by Device Manager To allocate storage system volumes to hosts (application servers) or check the volume usage of each host, target hosts must be registered in Device Manager as Device Manager resources. Device Manager can manage the volume usage of the hosts in the following table.
If both Host Data Collector and the Device Manager agent manage information about normal hosts or virtual machines, the Device Manager GUI or CLI uses the information acquired by the Device Manager agent. • With Host Data Collector: Host Data Collector can manage normal hosts, virtual machines, and virtualization servers. Network hosts that are found from the Device Manager GUI or CLI are registered in Device Manager.
When managing a Windows host • A user with Administrator permissions is assigned as a user who can execute the Host Data Collector service. • admin$ is shared over the network. You can check this by using the Windows net share command. If a security-monitoring program is installed on a normal host, Host Data Collector might not be able to collect the host information. • In the Windows Firewall settings, File and Printer Sharing is registered as an exception.
Related topics • Chapter 12, page 261 Prerequisites for normal hosts managed by Device Manager agent To use the Device Manager agent to manage normal hosts, install the Device Manager agent on each normal host. After installation, specify the environment settings such as the management server information and the execution interval of the HiScan command. In addition, on normal hosts running the AIX OS, set the ODMDIR environment variable.
Figure 6 Environment settings on virtual machines (when Host Data Collector is used for management) Host Data Collector comes with P9000 Command View AE Suite, which is installed on the management server, but can also be installed on a computer other than the management server. Before you register virtual machines in Device Manager, the following environment settings must already be specified on the virtual machines.
• Registering virtual WWN in Device Manager (when managing the virtualization server with vMA) When managing a UNIX host (When information about the host is collected by using the root account) • SSH is enabled. • Settings have been performed so that you can log in as root via a remote SSH login with password authentication.
NOTE: If a general user account is used to register a host into Device Manager, do not use the root account to register the host a second time.
• For virtual machines running the AIX OS, set the ODMDIR environment variable. • If an HBA is shared by multiple virtual machines • Install a Device Manager agent on any one of the virtual machines. • For virtual machines running the AIX OS, set the ODMDIR environment variable. • If a virtual HBA is allocated to each virtual machine (if an NPIV HBA is used) • Install a Device Manager agent on each virtual machine.
Configuration in which an HBA is shared by multiple virtual machines Figure 9 Operation workflow for allocating volumes to virtual machines (when sharing an HBA by multiple virtual machines) 1. Register one of the virtual machines that share an HBA as a normal host in Device Manager. Do not register the virtualization server that runs in the same physical environment in Device Manager. 2.
Configuration in which a virtual HBA is allocated for each virtual machine (by using NPIV HBAs) Figure 10 Operation workflow for allocating volumes to virtual machines (when allocating a virtual HBA to each virtual machine) 1. 2. 3. 4. Register the virtualization servers that run the virtual machines whose volume status you want to manage in Device Manager.
Registering virtual WWNs in Device Manager (createnpivinfo command) When using vMA to manage virtualization servers on which NPIV HBAs are used, execute the createnpivinfo command to register the virtual WWN assigned to each virtual machine in Device Manager.
If you move a virtual machine from one virtualization server to another : You need to update (refresh) the information of the source and destination virtualization servers in Device Manager. After moving a virtual machine, if there are no volumes assigned to the source virtualization server, manually delete the information about the source virtualization server from Device Manager. If a virtual WWN was added or changed: 1. Execute the createnpivinfo command to register the virtual WWN in Device Manager.
Figure 11 Environment settings on virtualization servers (when Host Data Collector is used for management) • Host Data Collector comes with P9000 Command View AE Suite, which is installed on the management server, but can also be installed on a computer other than the management server. To install multiple Host Data Collector computers, make sure that the same Host Data Collector version and revision are installed on all computers.
Figure 12 Environment settings on virtualization servers (when vMA is used for management) • You must deploy vMA on a virtualization server, and then specify the virtualization server or VMware vCenter Server as the monitoring target of vMA. • IPv6 can also be used for communication between the Device Manager server and vMA.
Figure 13 System configuration in which vMA monitors VMware ESX that is in the same physical environment Figure 14 System configuration in which vMA monitors VMware ESX that is in a different physical environment To register a virtualization server in Device Manager, you need to specify vMA information such as the IP address and user account. When you specify the vMA information, the physical environment managed by vMA is registered as a virtualization server.
NOTE: • If a virtualization server is managed by Device Manager, do not make the virtual machines running on that virtualization server management targets of Device Manager, except when NPIV HBA is used in the configuration. • If you change vMA information such as the IP address and user account, you must re-register the vMA in Device Manager (but you do not need to delete it).
NOTE: • If a virtualization server is managed by Device Manager, do not make the virtual machines running on that virtualization server management targets of Device Manager, except when NPIV HBA is used in the configuration.
• Re-register the vMA that manages the virtualization servers in Device Manager (but you do not need to delete it). Note that, if you change the hardware configuration of a virtualization server, after the configuration information of the monitored virtualization server is applied to vMA and VMware vCenter Server, you need to update (refresh) the Device Manager information.
Related products This section describes the products related to Device Manager and Tiered Storage Manager. Replication Manager Replication Manager provides centralized management of configurations and operating statuses of replication volumes distributed over a storage network. The Replication Manager GUI can be displayed from Device Manager GUI. Hitachi Dynamic Link Manager Hitachi Dynamic Link Manager manages each LUN path between a storage system and host.
• Storage system requirements for managing copy pairs, page 65 System configuration for managing copy pairs Device Manager supports the following four types of system configurations to manage copy pairs. • Local management method In this configuration, copy pairs are managed for each host by connecting a command device to each application server via Fibre Channel.
CAUTION: The requirements for defining or managing copy pairs by specifying a volume that belongs to the resource group used in data migration with a virtual ID are as shown below: • Copy pairs must be configured in such a way that they are managed with the central management method. • The configuration definition file must be recreated to match the new environment after migration. - Specify the physical ID for Serial# of the HORCM_LDEV parameter.
• A host that recognizes the S-VOL Host (application server) conditions: • Device Manager agent must be installed on hosts as follows: If there is one host that recognizes the P-VOL and one host that recognizes the S-VOL, install a Device Manager agent on each of the hosts. If there are multiple hosts that recognize the P-VOL and multiple hosts that recognize the SVOL, install a Device Manager agent on one of the hosts that recognize the P-VOL and one of the hosts that recognize the S-VOL.
• A shared resource group in which a command device has been registered must be created and assigned to each user. Note that, if each user uses a different command device, register the command device in a resource group managed by the user, instead of registering it in a shared resource group.
If the command devices recognized by the pair management server support the authentication function, install version 01-25-03/01 or later of RAID Manager on the pair management server. • If there are multiple NICs on the pair management server, the Device Manager agent and RAID Manager must use the same IP address. Copy pair (P-VOL and S-VOL) conditions: • The P-VOL and S-VOL must be managed by a single management server (Device Manager server).
• How to install RAID Manager: RAID Manager documentation System configuration for using a virtual command device server configuration to manage copy pairs Set up the management server, hosts (application servers), virtual command device server, and storage system so that the prerequisites are satisfied.
CAUTION: • If the HORCM_ALLOW_INST parameter is specified in the configuration definition file on the virtual command device server, the default port number (34000+instance-number+1) must be used for the RAID Manager initiator port of the application server.
System configuration for using an SVP configuration to manage copy pairs (when copy pairs are defined in a configuration definition file) Set up the management server, pair management server, and storage system so that the prerequisites are satisfied.
Resource group requirements (when managing partitioned resources in P9500) • The volumes below must be registered in a resource group managed by the user. - P-VOL - S-VOL - All pool volumes that make up a pool (when managing Snapshot or Fast Snap pairs) - All journal volumes that make up a journal (when managing Continuous Access Journal pairs) Note that managing partitioned resources might slow the display for some Replication Manager GUI operations.
Figure 22 Example of a system configuration for managing copy pairs (when copy pairs are defined as a device group) Management server conditions: • The following computers must be registered as the Device Manager management resources: - A host that recognizes the P-VOL - A host that recognizes the S-VOL • • • • Device Manager agent version 7.1 or later must be installed on the management server. RAID Manager version 01-25-03/01 or later must be installed on the management server.
• From the P-VOL and S-VOL, LUN security must be set for the host (application server). The management server does not need to recognize the P-VOL or S-VOL. • The P-VOL and S-VOL must be recognized by the hosts (application servers). HP recommends that P-VOL and S-VOL be assigned to separate application servers. Resource group requirements (when managing partitioned resources in P9500) • The volumes below must be registered in a resource group managed by the user.
Storage system requirements for managing copy pairs Use Element Manager to set up an environment appropriate for the storage system requirements. Table 7 Storage system requirements for managing copy pairs Storage system Function Requirements • Prerequisite software for Continuous Access Journal must be installed and the license must be enabled. • There must be a fibre-channel connection between the two ports used for an MCU-RCU path.
Storage system Function Requirements • Prerequisite software for Snapshot must be installed and the license must be enabled. Snapshot • To be used as an S-VOL, a V-VOL (a special LU) must be prepared in advance. Perform the preparations in the following order: • Create a pool. • Create a V-VOL. • Prerequisite software for Fast Snap must be installed and the license must be enabled. Fast Snap • To be used as an S-VOL, a V-VOL (a special LU) must be prepared in advance.
Prerequisite version of the Device Manager agent for managing copy pairs The prerequisite version of the Device Manager agent varies depending on the storage system to be managed and the program to be used. When using the GUI to manage copy pairs The prerequisite version of the Device Manager agent varies depending on the target storage system. Table 8 Device Manager agent requirements for managing copy pairs by using the GUI Storage system Device Manager agent version P9500 7.
The following table lists the Device Manager agent version required for each storage system model. Table 10 Device Manager agent version required for each storage system model when managing copy pairs by using the CLI Storage system model Device Manager agent version P9500 7.0 or later XP24000 5.7 or later XP20000 5.8 or later XP12000 XP10000 1.
that these copy pairs satisfy the conditions written below. If there are copy pairs that do not satisfy the conditions, modify the configuration definition file.
System configuration and requirements
2 Network configuration This chapter describes the settings for the P9000 Command View AE Suite products that are required in various network configurations. Port settings This section describes the port numbers and firewall settings used by the P9000 Command View AE Suite products. Ports used by P9000 Command View AE Suite products Avoid specifying port numbers used by other programs installed on the same computer for the port numbers used by P9000 Command View AE Suite products.
Port number Description 23018/tcp Used internally for Common Component communication (receiving a termination message from the Web server). This port number can be changed. Used internally for Common Component communication (communication with the Web server). 23025/tcp This port number can be changed. Used internally for Common Component communication (receiving a termination message from the Web server). 23026/tcp This port number can be changed.
Port number Description Used for communication with a CIM client (service discovery). 427/tcp You cannot change the settings by using Device Manager. If products using these ports are installed on the same computer, change the settings of those products. Used internally for Device Manager server communication, for communication with management clients (via the GUI or the CLI),for communication with storage systems, and for communication with hosts (Device Manager agents).
Ports used by the Tiered Storage Manager server For the management server, ensure that the port numbers specified for use by the Tiered Storage Manager server are different from the port numbers used by other programs installed on the same computer. Table 13 Ports used by the Tiered Storage Manager server Port number Description Used for communication with management clients (via the GUI or the CLI). 20352/tcp You can change the port by modifying the server.rmi.port property in the server.
Port number 22105/tcp 22106/tcp Description Used for SSL communication between the Device Manager server and the RMI server. You can change the port by using the hdc.common.rmi.ssl.serverPort property in the hdcbase.properties file of Host Data Collector. Used for SSL communication between the Device Manager server and the class loader. You can change the port by using the hdc.common.https.serverPort property in the hdcbase.properties file of Host Data Collector.
Port number Description Used internally for Device Manager agent communication. 24043/tcp You can change the port by using the server.http.localPort property in the server.properties file of the Device Manager agent. Related topics • • • • Changing Device Manager agent properties, page 395 server.agent.port, page 402 server.http.localPort, page 402 server.http.
Target storage system Port number Description 51099/tcp Used for communication with the management server or management clients (GUI). This port number cannot be changed. 51100/tcp Used for communication with the management server or management clients (GUI). This port number cannot be changed. 80/tcp Used for communication with management clients (GUI). This port number cannot be changed. XP12000 443/tcp Used for starting Element Manager by SSL from management clients (GUI).
4. If you change the following port numbers, you need to change the URLs of all P9000 Command View AE Suite products that are installed on the management server: • 23015/tcp (used for accessing HBase Storage Mgmt Web Service) You need to change the URLs if you use non-SSL for communication between the management server and management clients.
Default port number Settings files Location In Windows: installation-folder-for-Common-Component\CC\web\containers\HiCommand\ usrconf\usrconf.properties In Linux: webserver.connector.ajp13.port installation-directory-for-CommonComponent/CC/web/containers/HiCommand/usrconf/usrconf.properties In Windows: 23018/tcp installation-folder-for-Common-Component\CC\web\containers\HiCommand\ usrconf\usrconf.properties In Linux: webserver.shutdown.
Default port number Settings files Location In Windows: installation-folder-for-Common-Component\HDB\CONF\emb\HiRDB.ini In Linux: PDNAMEPORT installation-directory-for-CommonComponent/HDB/conf/emb/HiRDB.
Registering firewall exceptions When the ports or processes used by P9000 Command View AE Suite products are registered as firewall exceptions, connection to the registered ports or processes from outside the network is permitted.
Originator Destination Remarks Port number Machine Port number Machine 24500/tcp# Management server Management client any/tcp (Tiered Storage Manager CLI) This setting is required when SSL communication is used. #: This port number can be changed.
Originator Destination Remarks Port number Machine Port number Machine • P9500 • XP24000 • XP20000 any/tcp Management server 51099/tcp • XP12000 • XP10000 - • SVS200 • XP1024 • XP128 any/tcp Management server 51100/tcp any/tcp Management server 51100/tcp • XP24000 • XP20000 • P9500 This setting is required when you perform an upgrade installation to a Device Manager server version 6.0.0-00 or later. - Legend: -: Not applicable #: This port number can be changed.
Originator Destination Remarks Port number Machine Port number Machine • P9500 • XP24000 • XP20000 any/tcp Management client (GUI) 1099/tcp • XP12000 • XP10000 - • SVS200 • XP1024 • XP128 • P9500 • XP24000 • XP20000 any/tcp Management client (GUI) 51099/tcp • XP12000 • XP10000 - • SVS200 • XP1024 • XP128 any/tcp Management client (GUI) • P9500 51100/tcp • XP24000 - • XP20000 Legend: -: Not applicable Table 21 Port numbers that must be registered as firewall exceptions between the mana
This port number can be changed. Table 22 Port numbers that must be registered as firewall exceptions between the management server and a virtualization server Originator Destination Remarks Port number Machine Port number Machine • VMware ESX • VMware vCenter Server that manages VMware ESX This setting is required when a virtual WWN is assigned to a virtual machine by using NPIV.
Register the value specified for the client.launch.HPPA.report.port property in the client.properties file.
#: This port number can be changed. Table 27 Port numbers that must be registered as firewall exceptions between the management server and an SMI-S provider Originator Destination Remarks Port number Machine Port number Machine any/tcp SMI-S provider 5983/tcp# Management server - any/tcp Management server 5988/tcp# SMI-S provider This setting is required when non-SSL communication is used.
This port number can be changed. Table 29 Port numbers that must be registered as firewall exceptions between the management server and a mail server Originator Destination Remarks Port number Machine Port number Machine This setting is required to send an email to a user when the following events occur: any/tcp Management server (Device Manager server) 25/tcp#1 Mail server#2 • An alert occurs in a storage system. • A task executed from the Migrate Data wizard completes.
Originator Destination Remarks Port number Machine Port number Machine any/tcp Management server 1812/udp# RADIUS server - Legend: -: Not applicable #: This port number is generally used. However, a different port number might be used for an external authentication server.
Component Name added to the exceptions list Path Tiered Storage Manager(htsmHDvMUser) installation-folder-for-the-Tiered-Storage-Manager-server\inst\htsmHDvMUser.exe Tiered Storage Manager(htsmVersion) installation-folder-for-the-Tiered-Storage-Manager-server\inst\htsmVersion.exe Tiered Storage Manager(schemaDrop) installation-folder-for-the-Tiered-Storage-Manager-server\inst\schemaDrop.
2. Select Firewall configuration, use the Tab key to move to the Run Tool button, and then press Enter. The Firewall Configuration window is displayed. 3. Set Security Level to Enabled by pressing the space key to select Enabled, use the Tab key to move to the Customize button, and then press Enter. The Firewall Configuration - Customize window is displayed. 4. In Other ports specify the port to be registered as an exception, use the Tab key to move to the OK button, and then press Enter.
Network settings for using the management server as a network bridge To use the management server as a network bridge by installing multiple network interface cards (NICs) on the server, set up the networks so that the management server, management client, and storage systems can mutually communicate. The sections where settings must be specified are explained by using the configuration example shown below.
Device Manager settings in IPv6 environments Device Manager supports IPv6-based communication. To use Device Manager in an IPv6 environment, you need to change the Device Manager settings according to the environment's requirements. To use Device Manager in an IPv6 environment, make sure that the Device Manager settings meet the following requirements: • Set up the OS so that both IPv6 and IPv4 can be used because, even if IPv6 is being used, IPv4 is also required for processing in the product.
3. Delete the heading hash mark (#) from the #Listen [::]:port-number line to enable IPv6-based communication. For example, in the httpsd.conf file configured for SSL communication, the location of the line from which you delete a hash mark (#) is shown below. CAUTION: • If you use non-SSL communication, you do not need to delete the hash mark (#) from the Listen line under SSLSessionCacheSize. • By default, all IPv6 addresses are set to allow communication.
Related topics • Changing Device Manager server properties, page 338 • server.http.host, page 339 Changing the IP address or host name of the management server If you change the IP address or host name of the management server because of changes to the network configuration, you also need to change the settings for P9000 Command View AE Suite products.
4. Edit the httpsd.conf file. Change the value for the ServerName parameter to the new host name. • In Windows: installation-folder-for-Common-Component\httpsd\conf\httpsd.conf • In Linux: installation-directory-for-Common-Component/httpsd/conf/httpsd.conf If TLS/SSL is used for communication between the management server and management clients, you also need to change the following settings: • If a host name has been specified for the tag, change the host name to an asterisk (*). 5.
Information to collect in advance Changed IP address of the management server CAUTION: Do not change the settings in the cluster configuration file (the cluster.conf file). To change the IP address of the management server: 1. Stop the P9000 Command View AE Suite product services. 2. Edit the httpsd.conf file. If the old IP address is specified for the ServerName parameter, change the IP address to the host name or the new IP address.
Required operations after changing the IP address or host name of the management server If you change the IP address or host name of the management server, you might have to review the settings for Device Manager, Tiered Storage Manager, and Replication Manager depending on the operating environment. • When the old host name or IP address is specified for the server.http.
• Changing the settings for enabling or disabling SSL communication • Migrating to a cluster environment To change P9000 Command View AE Suite product URLs: • Execute the hcmdschgurl command.
Network configuration
3 User account management This chapter describes the settings required for managing user accounts of P9000 Command View AE Suite products. About password policies A password policy is a set of conditions related to the number of characters or combinations of character types that can be used in passwords for user accounts. By setting a password policy, you can prevent users from setting easily guessed passwords, and reduce the risk of unauthorized access from third parties.
To set a password policy: • Edit the security.conf file. The security.conf file is stored in the following locations: • In Windows: installation-folder-for-Common-Component\conf\sec\security.conf • In Linux: installation-directory-for-Common-Component/conf/sec/security.conf The following table shows the password policies that can be set in the security.conf file. Table 32 Password policies that can be set in the security.conf file Item Description password.min.
CAUTION: • In all P9000 Command View AE Suite products, set password policies apply only to user accounts that are added and passwords that are changed after the policy was set. New password policies do not apply to existing user accounts, so users of such accounts can log in to the system even if their passwords do not satisfy the set conditions. • You can also set password policies from the GUI.
failed login attempts to 3 and a user fails to log in to Device Manager once, Tiered Storage Manager once, and then Replication Manager once, the user account is automatically locked. Setting account locking policies You can set an account locking policy for P9000 Command View AE Suite products in the security.conf file. To set an account locking policy: • Edit the security.conf file. The security.
2. Open the user.conf file. The user.conf file is stored in the following locations: • In Windows: installation-folder-for-Common-Component\conf\user.conf • In Linux: installation-directory-for-Common-Component/conf/user.conf If the user.conf file does not exist, create it. 3. Use the following format to specify the account.lock.system property: account.lock.system=true 4. Start the P9000 Command View AE Suite product services.
To unlock a locked account: • Execute the hcmdsunlockaccount command to unlock the account.
4 Security This chapter describes the security settings required to operate P9000 Command View AE Suite products. Login warning banners A warning banner is a field for security messages displayed in the Login panel of P9000 Command View AE Suite products. P9000 Command View AE Suite products can display an optional message (warning banner), as a security risk measure at login.
To create and register a message displayed on a warning banner: 1. Use a text editor to create a message. Sample messages in English (bannermsg.txt) and Japanese (bannermsg_ja.txt) are provided in the following locations: • In Windows: installation-folder-for-Common-Component\sample\resource • In Linux: installation-directory-for-Common-Component/sample/resource These sample files are overwritten at installation so, if you wish to use a sample file, copy it and then edit it.
NOTE: If you execute the hcmdsbanner command and a message for the specified locale is already registered, it will be updated by being overwritten. TIP: You can also use the GUI to perform the following operations: • Registering a message without the locale specified • Editing a message that has been registered by the hcmdsbanner command with the locale option omitted When you use the GUI to perform operations, the following restrictions apply: • Available HTML tags are limited.
TIP: You can also use the GUI to delete the following messages: • A message registered from the GUI • A message registered by the hcmdsbanner command with the locale option omitted If the system is in a cluster configuration, operations from the GUI are applied only to the executing node. To apply the operation to the standby node, switch the nodes and then perform the same operations. Communication security mode This information is under export control and is not available on the web.
2. Add information about the management clients that can access the management server to the last line of the httpsd.conf file. Location of the httpsd.conf file • In Windows: installation-folder-for-Common-Component\httpsd\conf\httpsd.conf • In Linux: installation-directory-for-Common-Component/httpsd/conf/httpsd.conf Format for specifying clients in the httpsd.conf file order allow,deny allow from management-client [management-client...
• Stopping services, page 192 Changing the password-encoding level in the Device Manager CLI and the Tiered Storage Manager CLI This information is under export control and is not available on the web. To view the contents of this chapter, see the manual that is shipped with the product.
5 Configuring Device Manager for use with related products This chapter describes the settings required for linking with related products. Linking with PA Linking Device Manager or Tiered Storage Manager to PA will allow you to use the Mobility tab to check performance information, such as the parity group usage and the volume IOPS. It will also let you launch the PA GUI.
Related topics • Starting services, page 191 • Stopping services, page 192 • Properties for connecting to PA (hppa.properties file), page 368 Launching the PA GUI Before you can launch the PA GUI, you must set up the client.properties file on the Device Manager server. However, if you want to launch the PA GUI from the Tiered Storage Manager GUI in Legacy mode, you must set up the client.properties file on the Tiered Storage Manager server. Operations to complete in advance • Set up PA.
Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux). Information to collect in advance • Storage Essentials startup URL For details, see the Storage Essentials documentation. To launch the Storage Essentials GUI: 1. Use a text editor to create a file named StorageEssentials.conf. In the StorageEssentials.conf file you created, set the LaunchURL parameter in the following format: LaunchURL=Storage-Essentials-startup-URL 2.
To manage a storage system by SCVMM 2012: • On the window for registering the SMI-S provider of SCVMM 2012, specify the following items: • Protocol Specify SMI-S CIMXML. • IP address for the SMI-S provider Specify the IP address for the Device Manager server. Related topics • Changing Device Manager server properties, page 338 • server.cim.request.queue.
6 Setting up logs and alerts This chapter describes the settings required to use the P9000 Command View AE Suite products to monitor the status of the system and errors. Setting up integrated log files Common Component provides a common library used for logging. P9000 Command View AE Suite products use this library to output trace log information to log files. Setting up trace log files (Windows) To change the number or size of Common Component trace log files, use the Windows HNTRLib2 utility.
Setting up trace log files (Linux) To change the number or size of Common Component trace log files, use the utility program (hntr2util). WARNING! Changing the common trace log settings affects other program products that use the common trace logs. Operations to complete in advance Log in to the system as a root user. To set up Common Component trace log files: 1. Execute the utility program stored in the following location: /opt/hitachi/HNTRLib2/bin/hntr2util 2.
To collect Tiered Storage Manager CLI log files: • Set the necessary properties in the HtsmgetTI.properties file stored in the following location. In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\SupportTools\CollectTool\ In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/SupportTools/CollectTool/ Table 34 Properties set in the HtsmgetTI.properties file Property Description Specify the directory in which Tiered Storage Manager CLI is installed.
Categories Description Events indicating hardware or software failures: Failure • Hardware failures • Software failures (memory error, etc.
Categories Description Events indicating that abnormal communication occurred: • SYN flood attacks to a regularly used port, or protocol violations • Access to an unused port (port scanning, etc.) Different products generate different types of audit log data. For details on the contents of the output audit log data, see “Checking audit log data” on page 287.
Type description Automatic account lock Audit event Severity Message ID Failed login (to the external authentication server) 4 KAPM02451-W Successful logout 6 KAPM08009-I Automatic account lock (repeated authentication failure or expiration of account) 4 KAPM02292-W Table 38 Audit events that are output to audit logs (when the category is ConfigurationAccess) Type description Audit event Severity Message ID User registration Successful user registration 6 KAPM07230-I Failed user regist
Type description Audit event Severity Message ID Failed account lock release using the hcmdsunlockaccount command 3 KAPM07240-E Successful authentication method change 6 KAPM02452-I Failed authentication method change 3 KAPM02453-E Authorization group addition Successful addition of an authorization group 6 KAPM07247-I (GUI) Failed addition of an authorization group 3 KAPM07248-E Successful deletion of one authorization group 6 KAPM07249-I Authorization group deletion Failed deletio
Type description Audit event Severity Message ID User group deletion Successful deletion of a user group 6 KAPM07265-I Failed deletion of a user group 3 KAPM07266-E Successful update of a user group 6 KAPM07267-I Failed update of a user group 3 KAPM07268-E Successful registration of a role 6 KAPM07269-I Failed registration of a role 3 KAPM07270-E Successful deletion of a role 6 KAPM07271-I Failed deletion of a role 3 KAPM07272-E Successful update of a role 6 KAPM07273-I Faile
Type description Database input/output Database area creation or deletion Authentication data input/output Audit event Severity Message ID Successful data output using the hcmdsdbmove command 6 KAPM06543-I Failed data output using the hcmdsdbmove command 3 KAPM06544-E Successful data input using the hcmdsdbmove command 6 KAPM06545-I Failed data input using the hcmdsdbmove command 3 KAPM06546-E Successful database area creation using the hcmdsdbsetup command 6 KAPM06348-I Failed databas
Type description Device Manager server (via CIM) processing Acquisition of storage domain information#3 Acquisition of migration group information#3 126 Audit event Severity Message ID Response transmission (normal) 6 KAIC53100-I Response transmission (abnormal) 3 KAIC53300-E Request reception (normal) 6 Request reception (abnormal) 3 Response transmission (normal) 6 Response transmission (abnormal) 3 Successful acquisition of all storage domain information 6 KATS90000-I Failed acqu
Type description Acquisition of storage system information#3 Acquisition of task information#3 Acquisition of storage tier information#3 Acquisition of pool information#3 Audit event Severity Message ID Successful acquisition of migration group summary information 6 KATS90000-I Failed acquisition of migration group summary information 4 KATS90001-W Successful acquisition of storage system information 6 KATS90000-I Failed acquisition of storage system information 4 KATS90001-W Successful
Type description Acquisition of keystore file information#3 Acquisition of volume information#3 Acquisition of information about unused capacity of parity groups#3 Acquisition of external connection settings#3 Storage domain operations#3 128 Audit event Severity Message ID Failed acquisition of the number of pools returned from a search 4 KATS90001-W Successful acquisition of keystore file information 6 KATS90000-I Failed acquisition of keystore file information 4 KATS90001-W Successful a
Type description Migration group operations#3 Task operations#3 Audit event Severity Message ID Failed update of a storage domain 4 KATS90001-W Successful volume addition to a migration group 6 KATS90000-I Failed volume addition to a migration group 4 KATS90001-W Successful acquisition of the list of storage tiers that can be specified as migration destinations 6 KATS90000-I Failed acquisition of the list of storage tiers that can be specified as migration destinations 4 KATS90001-W Suc
Type description Storage tier operations#3 Audit event Severity Message ID Successful registration of a storage tier 6 KATS90000-I Failed registration of a storage tier 4 KATS90001-W Successful deletion of a storage tier 6 KATS90000-I Failed deletion of a storage tier 4 KATS90001-W Successful update of storage tier information 6 KATS90000-I Failed update of storage tier information 4 KATS90001-W #1: If an account is locked because the authentication method was changed for a user whose
Type description Audit event Severity Message ID No permission to stop a task 4 KATS90010-W Note: This information is output only by operations from the Tiered Storage Manager CLI or the Tiered Storage Manager GUI in Legacy mode.
Type description Acquisition of information from an external authentication server Audit event Severity Message ID Successful acquisition of user information from the LDAP directory server 6 KAPM10135-I Failed acquisition of user information from the LDAP directory server 3 KAPM10136-E Successful acquisition of the SRV record from the DNS server 6 KAPM10137-I Failed acquisition of the SRV record from the DNS server 3 KAPM10138-E For details about the output format of message text, see “Mess
Item Description Specify the audit event categories to be generated. When specifying multiple categories, use commas (,) to separate them. In this case, do not insert spaces between categories and commas. If Log.Event.Category is not specified, audit log data is not output. For information about the available categories, see Table 36 to Table 40. Log.Event.Category is not case-sensitive. If an invalid category name is specified, the specified file name is ignored. Log.Event.
Although you can specify this value, HP does not recommend that you specify it. The table below shows the correspondence between the severity levels of audit events, the values indicating severity that are specified in the syslog.conf file, and the types of event log data. Table 43 Correspondence between the severity levels of audit events, the severity levels in syslog.conf, and the types of event log data Severity of audit events Severity in syslog.
For storage system alerts, you can specify that the contents of received alerts are automatically sent to users by email. Error detection by Device Manager Device Manager detects errors in management-target storage systems as follows: • Polling (default) Device Manager regularly monitors the operating status of the storage systems, and displays an alert when an error is detected. An alert includes the location where an error occurred and overview of the error.
• Settings for reporting SNMP traps to Device Manager • The IP address of the management server must be registered in the SNMP Agent settings for storage systems as a target for trap notification. After the above settings finish, the Device Manager server receives SNMP traps from all communities and displays them as alerts. Related topics • Changing Device Manager server properties, page 338 • server.dispatcher.daemon.
NOTE: • Device Manager sends email only once when an alert is issued. If the Device Manager server fails to send an email, the same email will not be sent again. Information on an alert and email address of the intended destination of this email, are output to the Device Manager trace log file. • If the Device Manager server service stops before the Device Manager server sends an email about an alert, the email will not be sent.
TIP: The users who receive emails need to use email software that supports Unicode (UTF-8) encoding because, when sending an email, the Device Manager server sets the character encoding of the email to Unicode (UTF-8).
Operations to complete in advance • Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux). • Set the server.mail.smtp.auth property of the Device Manager server Specify true. Information to collect in advance • User ID and password for which All Resources has been assigned as a resource group and Admin has been set as the role in Device Manager. • User ID and password used for SMTP authentication. To register an SMTP authentication user account in Device Manager: 1.
In Windows: installation-folder-for-the-Device-Manager-server\Server\config In Linux: installation-directory-for-the-Device-Manager-server/Server/config The following shows the settings of the default mail-alert-detection.txt file: Specify the mail-alert-detection.txt file so that all of the conditions below are satisfied. If at least one condition is not satisfied, the Device Manager server will create an email by using the default settings. • Do not change the file name and location.
Parameter name Description Time at which the Device Manager server acquired alert information occurrenceTime Display format: yyyy/mm/dd hh:mm:ss hh is displayed by using 24-hour display. Related topics • Starting services, page 191 • Stopping services, page 192 Sending SNMP traps to log files Device Manager receives SNMP traps issued by devices on the network and outputs them to log files.
• Device Manager must be able to use port 162/udp of the management server. • Specify true for the server.dispatcher.daemon.receiveTrap property. • Settings required to report SNMP traps to Device Manager# • The management server information must be registered in SNMP related software as the target for trap notification. For example, to receive storage system SNMP traps, SNMP Agent settings must be specified.
Event Description Specified time elapsed This event occurs when a period specified by a user for a migration group created via the Tiered Storage Manager CLI or Tiered Storage Manager GUI in Legacy mode has elapsed (for the GUI the period is until a specified date; for the CLI the period is a specified number of days).
TIP: To send notifications about executed tasks via the Tiered Storage Manager CLI or the Tiered Storage Manager GUI in Legacy mode, the following properties in the Tiered Storage Manager server server.properties file must be set: • server.mail.from • server.mail.smtp.host • server.mail.smtp.port • server.mail.smtp.auth • server.mail.errorsTo • server.eventNotification.mail.to • server.
Type Event Template file • In Windows: installation-folder-for-theTiered-Storage-Manager-server\ conf\mail-shreddingtask-end.txt Shredding task ended#2 • In Linux: installation-directory-for-theTiered-Storage-Manager-server/ conf/mail-shreddingtask-end.txt • In Windows: installation-folder-for-theTiered-Storage-Manager-server\ conf\mail-lockingtask-end.txt Locking task ended#2 • In Linux: installation-directory-for-theTiered-Storage-Manager-server/ conf/mail-lockingtask-end.
#1: The template files are stored in the following locations: • In Windows: installation-folder-for-the-Device-Manager-server\Server\template • In Linux: installation-directory-for-the-Device-Manager-server/Server/template #2: The template files are stored in the following locations: • In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\template • In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/template By specifying, within the template files, parameters that will a
The parameters that can be specified in a template depend on the events. The parameters are listed in Table 48 to Table 50. Table 48 Parameters for events that occur when tasks end (migration tasks created via the Migrate data wizard) Parameter Description task Task name taskType Task type status Task status description Task description user The user ID of the user who created the task.
Parameter Description targetStorageTierName Name of the target storage tier eraseData Whether data after migration is to be deleted migratedVolumes Device numbers of both migrated volumes and volumes whose data has been erased shreddingMethod Shredding method shreddedVolumes Device numbers of shredded volumes guardMode Lock mode retentionDays Retention period (days) lockedVolumes Device numbers of locked volumes unlockedVolumes Device numbers of unlocked volumes moveToMigrationGroupName
TIP: To send notifications about executed tasks via the Tiered Storage Manager CLI or the Tiered Storage Manager GUI in Legacy mode, an SMTP authentication user account must be set up on the Tiered Storage Manager server by using the htsmmodmailuser command. Format of the hdvmmodmailuser command The SMTP authentication user settings set by the hdvmmodmailuser command are also used for alert email notification .
Related topics • Starting services, page 191 • Stopping services, page 192 Format of the htsmmodmailuser command Execute the command after moving to the following folder or directory: In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\bin In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/bin The following shows the syntax of the htsmmodmailuser command: Format htsmmodmailuser -u Tiered-Storage-Manager-user-ID -p Tiered-Storage-Manager-password SMTP-authentication-use
7 Configuring Device Manager for CIM/WBEM This chapter explains how to configure Device Manager for CIM/WBEM . About CIM/WBEM Device Manager supports CIM and WBEM, which have been defined by the DMTF standards group. CIM is a method of managing systems in a network environment. WBEM is a standard for managing network devices, such as hosts and storage systems, over the Internet. The CIM model that Device Manager uses complies with the SMI-S specifications advocated by SNIA, and is compatible with SNIA-CTP.
The SMI-S specifications, which Device Manager conforms to, define the interfaces for devices that make up a storage network, such as storage systems, virtual storage systems, switches, and hosts. The functions that need to be provided by the management service to manage the devices are grouped in a profile for each device. The profiles used by the CIM/WBEM functions of Device Manager are the Array profile and its subprofiles. The Array profile defines the interfaces for storage systems.
Specify root/smis/smisxx (xx is an abbreviation for the version number). For example, to specify version 1.5.0, enter root/smis/smis15. The latest namespaces that complies with the specified SMI-S version is selected. • Specify the condition current. Enter root/smis/current. The current namespace is selected. • Specify interop. SMI-S 1.3.0 or a later version supports the namespace interop.
Role in Device Manager CIM method that can be executed Admin Modify View Peer Service methods CIM operations -- -- -- Yes Not permitted Permitted Legend: Yes: This role has been assigned. --: This role has not been assigned. Permitted: These CIM methods can be executed. Not permitted: These CIM methods cannot be executed. Enabling CIM/WBEM functions When P9000 Command View AE Suite has been installed as a new installation, the CIM/WBEM functions are enabled.
CAUTION: • If you delete a storage system while disabling CIM/WBEM functions, perform step 2 in the following order to restart the services. 1. In the server.properties file, change the server.logicalview.initialsynchro property to true. 2. Restart the P9000 Command View AE Suite product services. 3. In the server.properties file, change the server.logicalview.initialsynchro property back to false.
• • • • server.cim.http.port, page 343 server.cim.https.port, page 343 HTTPPort, page 369 HTTPSPort, page 370 Settings for acquiring storage system performance information by using CIM/WBEM functions This section describes the system configuration that is required to use the performance information acquisition function, and how to specify settings for acquiring performance information.
Device Manager agent version 7.0 or later is required for P9500 storage systems, and Device Manager agent version 5.9 or later is required for XP24000/XP20000 or XP12000/XP10000/SVS200 storage systems. HP recommends that use the same computer for the management server and for the host that acquires performance information.
3. Use the perf_findcmddev command to register command devices. CAUTION: • If you upgrade the Device Manager agent from version 6.3 or earlier to version 6.4 or later, the settings in the perf_cmddev.properties file remain unchanged. If you are using a storage system in an SLPR environment, after the upgrade installation finishes, refresh the information of SLPR command devices defined in the perf_cmddev.properties file. • If you are using the Device Manager agent version 6.
Storage directory of the command In Windows: installation-folder-for-the-Device-Manager-agent\bin In Linux: /opt/HDVM/HBaseAgent/bin Options write [-file file-name] This option outputs the settings of all command devices recognized by the host to the file. You can use the -file file-name option to specify the desired file name. To specify the file name, you can use an absolute or relative path. If you do not specify the -file option, the perf_cmddev.properties file will be overwritten.
Raid ID Serial# R500 14050 R601 44332 R501 UNKNOWN SLPR# 0 1 - LDEV# 345 456 1045 Device file name \\.\PhysicalDrive3 \\.\Volume{xxxxxxx-xxxx-xxx-xxxxxxxx} \\.\PhysicalDrive10 Related topics • Format of the perf_cmddev.properties file, page 160 Format of the perf_cmddev.properties file Edit the perf_cmddev.properties file to define the command device of the target storage system. Storage directory of the perf_cmddev.
Setting item Value LDEV-number Specify the CU:LDEV number of the command device by using a decimal (base 10) number. Specify the command device identifier (the PhysicalDrive number, VolumeGUID, or device file name) that the host recognizes in the following format:# • In Windows: \\.\PhysicalDriveX deviceFileName \\.\Volume{GUID} • In Linux: /dev/sdx x is an integer.
OpenSLP 1.2.0 OpenSLP is provided with the SUSE Linux Enterprise Server system. For details on OpenSLP, see the Novell website (http://www.novell.com/). Starting and stopping the SLP service This section describes how to start and stop the SLP service. Starting and stopping the SLP service (Windows) Operations to complete in advance Log in as a user with Administrator permissions.
To stop the SLP daemon: • Execute the following command: installation-directory-for-the-Device-Manager-server/Server/wsi/bin/ slpd.sh stop Starting and stopping the SLP service (SUSE Linux Enterprise Server) Operations to complete in advance Log in as a user with root user.
2. Execute the following command: slpd -remove Releasing the SLP daemon (Linux) Operations to complete in advance Log in as a user with root user. To release the SLP daemon: 1. Stop the SLP daemon. 2. If /etc/init.d/slpd exists, delete it. # chkconfig --level 01345 slpd off # chkconfig --del slpd # rm -f /etc/init.
8 Setting up a cluster environment By clustering two P9000 Command View AE Suite product management servers together in an active-standby configuration, the availability of P9000 Command View AE Suite products can be improved. This chapter explains how to set up a cluster environment for P9000 Command View AE Suite products. Verifying the management server environment The setup procedure differs depending on the management server environment.
The sizes of the Device Manager, Tiered Storage Manager, Replication Manager, and Common Component databases are equal to the sizes of the folders or directories that contain the database files for the corresponding products. For details about the sizes of other P9000 Command View AE Suite product databases, see the manuals for those products. CAUTION: • The disk configuration must be the same on all the nodes that make up a cluster.
2. If any other P9000 Command View AE Suite products are included in the cluster environment, remove the P9000 Command View AE Suite product services and resource group from the targets of the cluster management. CAUTION: Do not remove the following resources from the cluster management • Shared disk • Cluster management IP address • Logical host name 3. Perform a new installation of P9000 Command View AE Suite on the executing node.
6. Use a text editor to create a cluster-configuration file. This step is not required if the cluster environment has been configured for other P9000 Command View AE Suite products. The items to be specified in the cluster-configuration file are as follows: mode=online virtualhost=logical-host-name onlinehost=executing-node-host-name standbyhost=standby-node-host-name Save the created file as cluster.conf in installation-folder-of-Common-Component\ conf. CAUTION: • Specify online for mode.
9. Execute the following command to back up the database after the new installation. As preparation in case of a failure, HP recommends that you back up the databases. installation-folder-of-Common-Component\bin\hcmdsbackups /dir target-folder-for-storing-backup-files /auto dir Using an absolute path, specify the local disk folder for the database backup files. Verify that the folder for the dir option is empty. auto Automatically starts or stops P9000 Command View AE Suite services.
11. Execute the following command to migrate the database to the shared disk: installation-folder-of-Common-Component\bin\hcmdsdbclustersetup / createcluster /databasepath target-folder-for-re-creating-database / exportpath target-folder-for-storing-database /auto createcluster This option changes the P9000 Command View AE Suite product in a non-cluster configuration to a cluster configuration. databasepath Specify the folder in which you want to re-create the database.
• Services and resource group that need to be removed from the cluster management: The manuals for P9000 Command View AE Suite products. • How to install P9000 Command View AE Suite: HP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide Installing on the standby node (new installation) To perform a new installation of P9000 Command View AE Suite on the standby node: 1. Perform a new installation of P9000 Command View AE Suite on the standby node.
5. Set the database on the shared disk as the database to be used. The procedure is described in steps 6 through 7. If a cluster environment has been configured for another P9000 Command View AE Suite product, there is no need to perform the steps for changing the settings if you want to use the database on the shared disk. Proceed to step 8. 6. If HiRDB is currently using a different port number than the default (23032/tcp), keep a note of the current port number. 7.
9.
Dialog box name Setting Dependencies Register the drive letter and network name of the shared disk. Generic Service Parameters Registry Replication Service name: HiRDBClusterService_HD0 Start parameters: Specify nothing. Specify nothing. Table 57 Settings for registering the HBase Storage Mgmt Common Service as a resource (for Microsoft Cluster Service) Dialog box name New Resource Setting Name: HBase Storage Mgmt Common Service (optional) Resource type: Generic Service.
Dialog box name Generic Service Parameters Registry Replication Setting Service name: DeviceManagerWebService Start parameters: Specify nothing. Specify nothing. Table 60 Settings for registering the DeviceManagerServer as a resource (for Microsoft Cluster Service) Dialog box name New Resource Setting Name: DeviceManagerServer (optional) Resource type: Generic Service. Possible Owners Make sure that the executing and standby nodes have been added.
• If there is a resource group in which another P9000 Command View AE Suite product has been registered, use that resource group. Make sure that the resource group consists of only those resources that are related to P9000 Command View AE Suite products. To set up Windows Server Failover Clustering: 1. Right-click the name of the resource group, and choose Add Resource, then Generic service.
Tab name Setting Advanced Policies Possible Owners: Make sure that the executing and standby nodes have been added. Policies Specify nothing. Registry Replication Specify nothing. Table 64 HBase Storage Mgmt Web Service property settings (for Windows Server Failover Clustering) Tab name Setting General Startup parameters (or Startup type): Specify nothing (if a value is specified, delete it). Dependencies Register HBase Storage Mgmt Common Service.
Tab name Setting Registry Replication Specify nothing. Table 67 HP StorageWorks XP Tiered Storage Manager property settings (for Windows Server Failover Clustering) Tab name Setting General Startup parameters (or Startup type): Specify nothing (if a value is specified, delete it). Dependencies Register DeviceManagerServer. Advanced Policies Possible Owners: Make sure that the executing and standby nodes have been added. Policies Specify nothing. Registry Replication Specify nothing.
4. Use the cluster management application on the executing node to take the following service offline: 5. • HiRDB/ClusterService _HD0 On the standby node, perform the same operations described in steps 1 to 4. 6. Use the cluster management application to suppress failover of the resource group. On the executing or standby node, change the settings of the resources listed below.
3. Execute the following command to back up the database after the upgrade or overwrite installation is complete: installation-folder-of-Common-Component\bin\hcmdsbackups /dir target-folder-for-storing-backup-files /auto dir Using an absolute path, specify the local disk folder for the database backup files. Verify that the folder for the dir option is empty. auto Automatically starts or stops P9000 Command View AE Suite services.
4. 5. In the Services window, open the properties for the following services, and then change Startup Type from Automatic to Manual: • HBase Storage Mgmt Common Service • HBase Storage Mgmt Web Service • HCS Device Manager Web Service • DeviceManagerServer • HP StorageWorks XP Tiered Storage Manager Use the cluster management application to enable failover of the resource group. Change the settings of the resources listed below.
Manager, or Replication Manager server operating in a non-cluster configuration is used for the executing node in the cluster. CAUTION: During setup of a cluster environment, P9000 Command View AE Suite services stop. Therefore, do not access P9000 Command View AE Suite while setup is in progress. To change the management server environment to a cluster configuration: 1. Install P9000 Command View AE Suite on the computer to be used as the standby node. 2.
4. Use a text editor to create a cluster-configuration file on the executing node and a cluster configuration file on the standby node.
6. Execute the following command to back up the database at the executing node. installation-folder-of-Common-Component\bin\hcmdsbackups /dir target-folder-for-storing-backup-files /auto dir Using an absolute path, specify the local disk folder for the database backup files. Verify that the folder for the dir option is empty. auto Automatically starts or stops P9000 Command View AE Suite services.
8. From the executing node, execute the following command to migrate the database to the shared disk. installation-folder-of-Common-Component\bin\hcmdsdbclustersetup / createcluster /databasepath target-folder-for-re-creating-database / exportpath target-folder-for-storing-database /auto createcluster This option changes the P9000 Command View AE Suite product in a non-cluster configuration to a cluster configuration. databasepath Specify the folder in which you want to re-create the database.
11. On both the executing and standby nodes, change settings so that the following services start manually. • • • • • HBase Storage Mgmt Common Service HBase Storage Mgmt Web Service HCS Device Manager Web Service DeviceManagerServer HP StorageWorks XP Tiered Storage Manager In the Services panel, open the properties of each service, and then change Automatic to Manual in Startup Type. 12. Using the cluster software, register resources.
6. Use the cluster management application to suppress failover of the resource group. Perform the following operation on the services listed in step 5 that you do not want to delete: 7. If Microsoft Cluster Service is used: Right-click the resource name, and choose Properties, the Advanced tab, and then Do not restart. If Windows Server Failover Clustering is used: Right-click the resource name, and choose Properties, the Policies tab, and then If resource fails, do not restart.
16. To continue using the remaining resource group, enable failover. Specify the following settings for the resources whose failover was suppressed in step 6: If Microsoft Cluster Service is used: Right-click the resource name, and choose Properties, the Advanced tab, and then Restart.
9 Starting and stopping services This chapter explains how to start and stop the P9000 Command View AE Suite product services on the management server. Resident processes of P9000 Command View AE Suite P9000 Command View AE Suite (Device Manager, Tiered Storage Manager, and Replication Manager) operation requires that resident processes are running on the OS. The following table describes the resident processes of Device Manager, Tiered Storage Manager, and Replication Manager.
Process name Service name Function pdservice.exe#3 HiRDB/EmbeddedEdition _HD0 HiRDB process server control #1: Do not register it as a cluster resource. #2: Displayed in Windows (x64) only. #3: This process must always be running. Do not stop it manually or register it as a cluster resource.
Starting services You can start the P9000 Command View AE Suite product services from the Windows menu or by using the hcmdssrv command. Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux). To start the services: • Perform the following operations.
Stopping services You can stop the P9000 Command View AE Suite product services from the Windows menu or by using the hcmdssrv command. Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux).
Related topics • How to stop the services of the P9000 Command View AE Suite products whose versions are earlier than 5.7: See the manuals for the corresponding versions of P9000 Command View AE Suite products. Checking the operating status of services You can check the operating status of the P9000 Command View AE Suite product services from the Windows menu or by using the hcmdssrv command.
Starting and stopping services
10 Managing the database This chapter describes how to back up and restore the database for P9000 Command View AE Suite products. Managing databases The following table describes backing up and restoring, as opposed to exporting and importing. Table 70 Backing up and restoring as opposed to exporting and importing Item Backing up and restoring Exporting and importing Restrictions on P9000 Command View AE Suite product versions No restrictions Version 5.
Required space: (total-size-of-all-P9000-Command-View-AE-Suite-product-databases-to-bebacked-up + 2.
2. Execute the hcmdsbackups command to back up the database. In Windows: installation-folder-for-Common-Component\bin\hcmdsbackups /dir folder-for-storing-backup-files /auto In Linux: installation-directory-for-Common-Component/bin/hcmdsbackups -dir directory-for-storing-backup-files -auto dir Specify the absolute path of the directory on the local disk in which the database backup files are stored. In Linux, do not specify a path that includes a space.
3. Execute the hcmdssrv /stop command to stop the P9000 Command View AE Suite product services. Then, execute the hcmdssrv /statusall command to make sure that the services have stopped or that the return code of the command is 0. 4. Use the cluster management application to take the following service offline: 5. • HiRDBClusterService _HD0 Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below. 6.
8. Use the cluster management application to enable failover of the resource group. Change the settings of the resources listed below. 9.
When the hcmdsdbrepair command is executed, all of the P9000 Command View AE Suite databases installed on the management server are forcibly deleted and then replaced by the exported databases. Restoring a database when a data inconsistency occurs If a database inconsistency occurs, execute the hcmdsdb command to restore the database by using a database backed up via the hcmdsbackups command. CAUTION: • The hcmdsdb command, which is used in the procedure below, creates temporary files during execution.
2. Execute the hcmdsdb command to restore the database. In Windows: installation-folder-for-Common-Component\bin\hcmdsdb.bat /restore backup-file /type name-of-the-P9000-Command-View-AE-Suite-productto-be-restored /auto In Linux: installation-directory-for-Common-Component/bin/hcmdsdb -restore backup-file -type name-of-the-P9000-Command-View-AE-Suite-productto-be-restored -auto restore Specify the absolute path to the database backup file (backup.hdb) that was created by using the hcmdsbackups command.
10. Check the status of Device Manager tasks from the Device Manager GUI. If a Device Manager task is not completed or has failed, re-create the task or change the execution schedule of the task as necessary. 11. See the message log of Tiered Storage Manager. When Tiered Storage Manager is started for the first time after a database is restored, make sure that the message KATS50354-E is output to a log file.
5. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below. 6.
9. Use the cluster management application to enable failover of the resource group. Change the settings of the resources listed below.
Restoring a database when a database is corrupted If a database is corrupted, execute the hcmdsdbrepair command to restore the database by using a database that was exported via the hcmdsdbtrans. CAUTION: During database restoration, P9000 Command View AE Suite services stop. Therefore, do not access P9000 Command View AE Suite while restoration is in progress. Restoring a database when it is corrupted (in a non-cluster configuration) To restore a database if the management server is not clustered: 1.
12. See the message log of Tiered Storage Manager. When Tiered Storage Manager is started for the first time after a database is restored, make sure that the message KATS50354-E is output to a log file. The task IDs of Tiered Storage Manager tasks whose status was changed to Failure are output to KATS50354-E. 13. See the volume information of the tasks indicated in the message KATS50354-E and check whether those tasks are completed.
5. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below. 6.
11. On the executing node and standby node, change the value of the server.base.initialsynchro property on the Device Manager server back to false. 12. On the executing node and standby node, change the value of the server.base.initialsynchro property on the Tiered Storage Manager server back to false. 13. Refresh the storage system from the Device Manager GUI or CLI. 14.
Prerequisites and restrictions on migrating databases The following are notes on the databases, product types, versions, and user information of P9000 Command View AE Suite products on the migration source and destination servers. Notes on databases, product types, and versions of P9000 Command View AE Suite products: • If Replication Monitor 5.x or earlier is already installed on the migration source server, before exporting the database, upgrade the product to version 6.
Exporting databases from the migration-source server To export the databases of P9000 Command View AE Suite products, a directory for temporarily storing the database data and a directory for storing archive files are required. For each directory, ensure that a comparable capacity to the total size of the following directories is available.
Exporting databases in a cluster configuration This section explains how to export the databases on the migration destination server when the OS of the management server is in a cluster configuration. CAUTION: Use the executing node (a machine that has online set for mode in the cluster.conffile) to export databases. To export databases using Microsoft Cluster Service or Windows Server Failover Clustering: 1. Log on to the management server as a user with Administrator permissions. 2.
7. Execute the hcmdsdbtrans command to export the databases. installation-folder-for-Common-Component\bin\hcmdsdbtrans /export / workpath working-folder /file archive-file workpath Specify the absolute path to the working folder where you want to temporarily store database data. Specify a folder on your local disk. Make sure that no files or subfolders are in the folder specified for the workpath option. file 8. Using an absolute path, specify the name of the archive file to be output.
To import databases into the migration-destination server in a non-cluster configuration: 1. Log on to the management server as a user with Administrator permissions or root permissions. 2. If you specified a value other than the default value for a property on the migration source management server, check and review the property value set on the migration destination server as required. The property file will not be migrated to the migration destination server even if the database is imported.
3. Execute the hcmdsdbtrans command to import the databases.
Product Value Other products Refer to the manual for each product. #1: When importing databases that were exported from an environment of version 7.0 or later, regardless of whether you have registered a Tiered Storage Manager license, import both the Device Manager and Tiered Storage Manager databases at the same time. #2: To import the Replication Manager database, you must also import the Device Manager database at the same time. auto 4.
Importing databases in a cluster configuration This section explains how to import the databases on the migration destination server when the OS of the management server is in a cluster configuration. CAUTION: Use the executing node (a machine that has online set for mode in the cluster.conf file) to import databases. To import databases using Microsoft Cluster Service or Windows Server Failover Clustering: 1. Log on to the management server as a user with Administrator permissions. 2.
7. Start HiRDB. installation-folder-of-Common-Component\bin\hcmdsdbsrv /start 8. Execute the hcmdsdbtrans command to import the databases. installation-folder-for-Common-Component\bin\hcmdsdbtrans /import / workpath working-folder [/file archive-file] /type {ALL|P9000-Command-View-AE-Suite-products-whose-databases-will-be-migrated} workpath When using the archive file for the import: Specify the absolute path to the folder used to extract the archive file. Specify a folder on your local disk.
9. On the executing node and standby node, specify true for the server.base.initialsynchro property of the Device Manager server. Because, other than user information, the hcmdsdbtrans command does not migrate the Common Component repository, you need to synchronize the repository information with the imported Device Manager database data. 10. On the executing node and standby node, specify true for the server.base.initialsynchro of the Tiered Storage Manager server. 11.
18. Back up the databases. After resuming operations, you cannot import the archive file that was exported in version 6.4 or earlier. In preparation for a failure, HP recommends that you back up the databases immediately after importing them.
Managing the database
11 Using the Device Manager agent This chapter explains the settings that must be specified to run the Device Manager agent. This chapter also explains Device Manager agent operations. Prerequisites for running the Device Manager agent This section provides the prerequisites for running the Device Manager agent. This section also provides notes on using the Device Manager agent.
• If you have installed the Device Manager agent and then upgraded the host OS under any of the following conditions, perform an overwrite installation of the Device Manager agent: • Upgrading Solaris from a version earlier than 9 to version 9 or later • Upgrading AIX from a version earlier than 5.2 to version 5.
You must specify these settings if you use Device Manager or Replication Manager to manage copy pairs. • Settings required when 100 or more LUs are managed for a host You must specify these settings if a host recognizes 100 or more LUs that are managed by Device Manager.
Specify this argument to select the latest version of the Java execution environment from Oracle JDK and Oracle JRE installed on the host. If the versions of the installed JDK and JRE are the same, the JDK takes precedence. • bundle Specify this argument to select the Java execution environment bundled with the Device Manager agent. • Java-execution-environment-installation-path If you want to use a specific Java execution environment, specify the absolute path of the installation path.
Location of the command installation-folder-for-Device-Manager-agent\bin Options -set Adds firewall exceptions. -unset Removes firewall exceptions. Related topics • server.agent.port, page 402 • server.http.localPort, page 402 • server.http.
3. Restart the host. Related topics • server.agent.JRE.location, page 404 Managing copy pairs If you use Device Manager or Replication Manager to manage copy pairs, depending on the environment, you must change property settings on the Device Manager agent or the Replication Manager server. • If RAID Manager is installed in a location other than the default location, or if the host OS is Windows and the RAID Manager installation drive is different from the Device Manager agent installation drive: server.
might terminate in an error. HP recommends that you change the following property values in advance: • server.agent.rm.moduleTimeOut property in the server.properties file of the Device Manager agent Set the value to 1800 or greater. • agent.rm.TimeOut property in the agent.properties file of the Device Manager agent Set the value to 1800 or greater. • hdvmagtif.MaxPollingCount property in the agentif.properties file of the Replication Manager server Set the value to 100. • hdvmagtif.
• • • • • • • server.agent.rm.exclusion.instance, page 406 server.agent.rm.location, page 407 server.agent.rm.optimization.userHorcmFile, page 407 server.agent.rm.pairDefinitionForm, page 408 server.agent.rm.ignorePairStatus, page 410 server.agent.rm.moduleTimeOut, page 411 About the hdvmagtif.MaxPollingCount property and the hdvmagtif.PollingInterval property in the Replication Manager server agentif.
Recommended property values to be set for a host that will manage 100 or more LUs (when the host is not using a volume manager) The following table lists the recommended property values for hosts that do not use a volume manager. Table 75 Recommended property values for a host that will manage 100 or more LUs (when the host is not using a volume manager) Number of LUs managed by Device Manager, and recognized by the host server.http. entity.maxLength (units: bytes) server.http. server.
shown in the tables is not recommended: It will take more than one hour for the HiScan operation to complete, and the operation might fail. Table 76 Recommended property values for a host that will manage 100 or more LUs (when the host is using a volume manager in Windows) Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) server.http. server.timeOut (units: seconds) server.util.
Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) 1,000/1,000 72,000,000 or more server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) 1,200 server.agent.
Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) server.agent.
The following describes the resident processes of the Device Manager agent. Table 81 Resident processes of the Device Manager agent (Windows) Process name Service name Function hbsa_service.exe HBsA Service Device Manager agent service Table 82 Resident processes of the Device Manager agent (UNIX) Process name Function hbsa_service Device Manager agent service Immediately after Device Manager agent installation is completed, the Device Manager agent service is enabled.
Specify this option to start the Device Manager agent service. stop Specify this option to stop the Device Manager agent service. If the -f option is also specified, the command forces the Device Manager agent service to stop. In such a case, all processing is forced to terminate, thus ongoing processing of jobs is not guaranteed. status Specify this option to check the operating status of the Device Manager agent service. CAUTION: • If any add-on module or version 5.
Device Manager agent operations This section explains Device Manager agent operations. Checking the available agent functions (hbsa_modinfo command) Use the hbsa_modinfo command to display the names and versions of available add-on modules. The names and versions of add-on modules are displayed in V.R1.R2-MM format (V: version number, R1 and R2: revision number, MM: modification version number).
• Replication Manager agent Monitors the status of storage system replication. • Replication Manager Application agent Centrally manages backup operations on a unit basis using the high-speed copy function of the storage system. Deleting the Device Manager agent's registry entries and files (hbsa_util command) If the OS of the host is Windows, you can use the hbsa_util command to delete the Device Manager agent's registry entries and files.
In AIX: /usr/HDVM/HBaseAgent/bin Setting the Device Manager server's information, HiScan command's execution period, and RAID Manager's information (hdvmagt_setting command) Use the hdvmagt_setting command to set the Device Manager server's information, the HiScan command's automatic execution period, and the information necessary for using RAID Manager. This command lets you interactively set the items listed in the following table.
Information to collect in advance • IP address or host name of the Device Manager server • Port number of the Device Manager server You can check this value by using the server.http.port property in the server.properties file for the Device Manager server. • User ID and password for the Device Manager agent The relevant user account must belong to the Device Manager PeerGroup.
Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for UNIX). Information to collect in advance • IP address or host name of the Device Manager server • Port number of the Device Manager server • User ID and password for the Device Manager agent If you want to use another account with the Device Manager agent, you must register the user ID in the PeerGroup user group in advance.
Specifies the interval (in seconds) at which host information is sent to the Device Manager server. Host information is continuously sent to the Device Manager server at the specified interval, until a forced termination occurs. Values of less than ten seconds are recognized as invalid. Specify a value in the range from 10 to 2147483647. -t Specify this option if you want to output the host information that was sent to the Device Manager server to an XML file. The file is output to the current directory.
Location of the command In Windows: installation-folder-for-Device-Manager-agent\util\bin In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/util/bin In AIX: /usr/HDVM/HBaseAgent/util/bin Options -d Specify this option to display information about the LDEV specified as an argument of this option. (The argument is either a drive number (in Windows) or device special file name (in UNIX).) If the argument is omitted, the command displays information about all LDEVs that are currently recognized.
LDEV information using the file system name that is included in each logical device and assigned the lowest ASCII code. If you do not specify the -s option, the command outputs LDEV information in the order in which it has processed the information. -serdec Specify this option to display the serial number of the storage system in decimal format. -k Specify this option to send the contents of the latest execution log file to the standard output. This processing involves no hardware access.
Information displayed by the hldutil command The following table lists and describes the information output when you execute the hldutil command. The information items are output in the order shown in the table. The items displayed differ depending on the OS and the specified options.
Storage system models corresponding to RaidID values displayed by the hldutil command The RaidID values displayed by the hldutil command are strings that indicate storage system models. The following table shows the correspondence between RaidID values and storage system models.
Sort key Descriptions tid Target ID vend Vendor name wwnn Node WWN name wwnp Port WWN name Configuration definition file for managing copy pairs In Device Manager, you can use a user-created RAID Manager configuration definition file to manage copy pairs. Prerequisite environment for using the configuration definition file To use the configuration definition file, you need to set up the environment as follows on the host on which RAID Manager is installed.
3. Use the Device Manager GUI or CLI to refresh the storage system that contains the copy pair volumes for which the configuration definition file was created. NOTE: • If a parameter not supported by Device Manager is used, the configuration definition file is assumed to be invalid and the system does not execute normal processing. Even though a parameter is supported, Device Manager might not support certain description formats.
# These parameters are supported by Device Manager agent version 6.2 or later. Note that when you create or use a copy pair, even if HORCM_CTQM information is defined in the configuration definition file, the Device Manager agent will operate while ignoring the definition. The Device Manager agent does not add the HORCM_CTQM definitions to the configuration definition file, nor does it add a pair group to the existing definitions.
HORCM_MON parameter description format Use the HORCM_MON parameter to specify the machine information for the local host and the interval for monitoring errors in copy pair volumes. • ip_address Specify the IP address (the Device Manager agent whose version is 5.9 or later supports the IPv6 protocol), host name, NONE, or NONE6.
Specify the port name or port number. • Specify the port name using 1 to 15 single-byte characters. The environment must support the conversion of port names to port numbers. • Specify the port number as a numeric value from 0 to 65535. • poll Specify a value (in ten millisecond units) or -1. • timeout Specify the timeout period in ten millisecond units. Table 88 Support status of HORCM_MON parameter description format Item Version ip_address service poll timeout 6.1 or later Yes Yes Yes Yes 5.
GUID format \\.\Volume{GUID} CMD format \\.\CMD-serial-number[-logical-device-number[-port-name[-host-groupnumber]]] You must use base-10 numbers to specify the serial number and logical device number. For the host group number, if the version of the Device Manager agent is 5.6 or later, specify a value from 0 to 254. If the version of the Device Manager agent is 5.5 or earlier, specify a value from 0 to 127. In UNIX, you can specify a command device in IPCMD or CMD format, or in a special file.
Yes: Supports all description formats. Related topics • Editing the configuration definition file, page 245 • Description conventions for the configuration definition file, page 247 • Notes on using the configuration definition file, page 258 HORCM_DEV parameter description format Use the HORCM_DEV parameter to specify information about the storage system that contains volumes to be used as copy pairs. • dev_group Specify the group name.
If no value is specified or 0 is specified, multi-target configuration pairs cannot be created with Continuous Access. When the version of the Device Manager agent is from 6.0 to 7.3.1: Business Copy: 0 to 2 Snapshot: 0 to 63 Continuous Access: Not specified Continuous Access Journal: Not specified#, 0#, h1, h2, or h3 #: If no value is specified or 0 is specified, multi-target configuration pairs cannot be created with Continuous Access. When the version of the Device Manager agent is 5.
• Specify no more than 31 single-byte characters. A hyphen (-) cannot be specified at the beginning of the character string. • Serial# Specify the system number of the storage system using the decimal number or serial-number:journal-ID format. • CU:LDEV(LDEV#) Specify the LDEV number using the decimal number, hexadecimal number, or CU:LDEV format.
Continuous Access Journal: h1, h2, or h3 Table 91 Support status of HORCM_LDEV parameter description format Item Version dev_group 6.2 or later Yes dev_name Serial# Yes CU:LDEV(LDEV#) MU# Yes Yes Yes Yes No 6.1 to 05-60 Yes Yes Yes Supports description formats other than the serial-number:journal-ID format. Earlier than 05-50 No No No No Legend: Yes: Supports all description formats. No: Does not support any description formats.
• The table below lists the values that can be specified for ip_address. Note that some formats cannot be specified for ip_address because they cannot identify a host. Table 92 Values that can be specified for the ip_address of HORCM_INST parameter Device Manager agent version Value 05-80 or later 05-70 or earlier IP address Yes Yes Host name Yes Yes Loopback IP addresses (127.0.0.1 to 127.255.255.
• HORCM_DEV parameter description format, page 251 • HORCM_LDEV parameter description format, page 252 • Notes on using the configuration definition file, page 258 HORCM_INSTP parameter description format Use the HORCM_INSTP parameter to specify the machine information and path group ID of the remote host. • dev_group Specify the contents specified for dev_group of the HORCM_DEV parameter or HORCM_LDEV parameter. • You cannot specify ip_address more than once for the same host for a single dev_group.
• Specify the port name using 1 to 15 single-byte characters. The environment must support the conversion of port names to port numbers. • Specify the port number as a numeric value from 0 to 65535. • pathID Specify the path group ID as a decimal number from 1 to 255. • You cannot specify multiple path group IDs for a single copy group. • If you omit path group ID specification (that is, if you select CU Free), use the HORCM_INST parameter instead of the HORCM_INSTP parameter.
3. Change the storage location of the configuration definition file. 4. Specify the new storage location that was changed in step 3 in the server.agent.rm.horcmSource property of the server.properties file of the Device Manager agent. 5. Execute the hbsasrv command to start the Device Manager agent service. Related topics • Starting and stopping the Device Manager agent service, and checking the operating status of the service (hbsasrv command), page 233 • server.agent.rm.
If you do not want the configuration definition file to be deleted, back up of the configuration definition file before you delete the copy pairs. Related topics • Editing the configuration definition file, page 245 • server.agent.rm.optimization.
Using the Device Manager agent
12 Setting up Host Data Collector This chapter explains how to set up Host Data Collector. Installing Host Data Collector This section explains how to install Host Data Collector on a computer other than the management server. Prerequisites for installing Host Data Collector The items that you can specify during installation of Host Data Collector, such as the installation path and port number, have default values. HP recommends using the default values, when possible.
Item Port number Description Port number of RMI registry The non-SSL communication port number of the RMI registry. Port number for RMI server The non-SSL communication port number of the RMI server. Port number for class loader The non-SSL communication port number of the class loader.
TIP: • You can also download the Host Data Collector installer from the Device Manager GUI. • If version 7.4.1 or earlier of Host Data Collector is installed on a drive other than the system drive, if you upgrade install to version 7.5.0 or later, a temp folder is created directly under the Host Data Collector installation drive. If you do not need this folder, delete it.
2. Move to the directory that contains the installer (setup.sh). The installer is located in the following location: DVD-drive/AGENTS/HHDC/platform-name/ 3. Execute the following command: # ./setup.sh 4. Follow the instructions in the displayed messages. When the installation is successful, the following message appears: Host Data Collector installation completed successfully. TIP: You can also download the Host Data Collector installer from the Device Manager GUI.
Registering a Host Data Collector computer on the management server If Host Data Collector is installed on a computer other than the management server, you need to add the information for that computer to the properties in the hostdatacollectors.properties file on the Device Manager server. When the information for the Host Data Collector computer is registered on the management server, you can register hosts and check the volume usage on each host.
• • • • • • hdc.common.rmi.registryPort, page 386 hdc.common.rmi.serverPort, page 387 hdc.common.http.serverPort, page 387 hdc.common.rmi.ssl.registryPort, page 388 hdc.common.rmi.ssl.serverPort, page 388 hdc.common.https.serverPort, page 389 Specifying the Host Data Collector environment settings This section explains how to specify Host Data Collector environment settings.
NOTE: In a cluster configuration, while the Host Data Collector service on the executing node is running, the Host Data Collector service on the standby node must also be active. Related topics • “Resident processes of P9000 Command View AE Suite” on page 189 Starting the Host Data Collector service Use the controlservice command to start the Host Data Collector service. Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux).
Related topics • Resident processes of the Host Data Collector, page 266 • Starting the Host Data Collector service, page 267 • Checking the operating status of the Host Data Collector service, page 268 Checking the operating status of the Host Data Collector service Use the controlservice command to check the operating status of the Host Data Collector service. Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux).
Location of the command installation-folder-for-Host-Data-Collector\HDC\Base\bin Options add Adds firewall exceptions. del Removes firewall exceptions. Related topics • • • • Registering an exception for the Host Data Collector service (for SSL communication), page 269 hdc.common.rmi.registryPort, page 386 hdc.common.rmi.serverPort, page 387 hdc.common.http.
TIP: To check the registered information, execute the following commands: In Windows Server 2003 or Windows Server 2003 R2: netsh firewall show portopening In Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012: netsh advfirewall firewall show rule name=all Related topics • • • • • • Starting the Host Data Collector service, page 267 Stopping the Host Data Collector service, page 267 Registering an exception for the Host Data Collector service (for non-SSL communication), page 268 hdc.
Specifying settings if the Host Data Collector machine has multiple IP addresses If the Host Data Collector machine has multiple IP addresses, you must specify the IP address to be used for communication with the Device Manager server for the hdc.service.rmi.registryIPAddress property in the hdcbase.properties file for Host Data Collector. Related topics • hdc.service.rmi.
TIP: If you remove an instance of Host Data Collector of version 7.4.1 or earlier that is installed on a drive other than the system drive, the temp folder might remain in the root folder of the drive where Host Data Collector was installed. If you do not need this folder, delete it. Removing Host Data Collector (Linux) You can remove Host Data Collector if it is no longer needed for host management. Execute the .unsetup.sh command to remove Host Data Collector.
13 Troubleshooting This chapter describes how to resolve problems that occur during Device Manager and Tiered Storage Manager operation, and how to read log files. Common problems and solutions This section describes problems that might occur while setting the environments of or operating Device Manager and Tiered Storage Manager, and the causes of and solutions to these problems.
No. Problem and cause PROBLEM: Device Manager server cannot be accessed from the GUI or CLI after starting the Management server or P9000 Command View AE Suite product services. 3 CAUSE: If the KAIC03100-E error message is output to the Device Manager trace log file, the communication process from Device Manager server to the database has timed out. Solution Startup of the Device Manager service might have failed.
No. Problem and cause Solution PROBLEM: An inconsistency exists between the database information and the storage system status. CAUSE: Possible causes are as follows: 3 • The Tiered Storage Manager server terminated abnormally due to a forced termination or an unexpected error. • A failover occurred in a cluster environment.
No. Problem and cause Solution Perform the following procedure to restore the consistency between the database information and the storage system status: 1. After restarting the P9000 Command View AE Suite product services, refresh all storage systems by using Device Manager. 2. If a migration task was being created or canceled during an abnormal termination of the Tiered Storage Manager server, perform the creation or cancellation again.
No. Problem and cause Solution 3. 4 PROBLEM: Tiered Storage Manager operations cannot be performed because an error occurred in the database. If there are LDEVs that have not been migrated yet, remove the cause of the error, and then re-create and execute the migration task. Restore a backed up database. CAUSE: The repository cannot be accessed because an error occurred in the database.
No. Problem 5 In a Windows environment, two copies of HBase Agent are displayed in the Programs and Features window of the computer on which the Device Manager agent or Hitachi Dynamic Link Manager is installed. 6 7 In a Windows environment, HBaseAgent is displayed in the Programs and Features window even after you remove both the Device Manager agent and Hitachi Dynamic Link Manager.
No. Problem Solution • This problem might occur if a host recognizes 100 or more LUs that are managed by Device Manager. To avoid this, follow the procedure in “Settings required for a host to manage 100 or more LUs” on page 228. • Depending on the load status of the Device Manager server, an OutOfMemory error might occur. If the following error message is output to the log file specified for the -t option of the HiScan command or the HiScan.
No. 12 Problem Solution In an AIX environment, SC_DISK_ERR2 (Device Busy) is output in the error log of the standby node. The active node is providing disk reserve normally for the shared disk, and therefore there is no problem with the system. Shared disk information is acquired from the Device Manager agent running on the active node, and therefore there is no problem with the operation of Device Manager. In addition, HSDRV_RSV_CONFLICT is output to the error log.
• Java VM thread dump If any of the following problems occurs, you need to acquire the thread dumps of HBase Storage Mgmt Common Service and HCS Device Manager Web Service to locate the cause of the problem. • The Device Manager logon window is not displayed when you start the GUI. • The Device Manager main window is not displayed after logging on to Device Manager.
Specify the absolute path to the directory on a local disk that contains collected maintenance information. If the directory has already been created, empty the directory. The maximum length of a path name that can be specified is 41 bytes. You can specify any printable ASCII character excluding certain special characters.
TIP: If the KAPM05318-I or KAPM05319-E message is not output, the cvxpaegetlogs command did not complete because sufficient free space was not available for the directory specified in the dir option. Free up sufficient space in the directory, and then re-execute the cvxpaegetlogs command.
Operations to complete in advance • Copy a file to the host Copy the following file to the target managed host from the computer on which Host Data Collector is installed: In Windows: installation-folder-for-Host-Data-Collector\Base\bin\hdc_target_getras.bat In UNIX: installation-directory-for-Host-Data-Collector/Base/bin/hdc_target_getras.sh • Log in as a user with Administrator permissions (for Windows) or as a root user (for UNIX) Command format In Windows: hdc_target_getras.
In UNIX: TIC.sh [-outdir directory-name [-f]] Location of the command In Windows: installation-folder-for-Device-Manager-agent\bin In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/bin In AIX: /usr/HDVM/HBaseAgent/bin Options -outdir Use the absolute path or a relative path from the current directory to specify the output destination for the maintenance information.
4. From the Services window, start the HBase Storage Mgmt Common Service. The javacorexxx.xxxx.txt file is output when using JDK bundled with P9000 Command View AE Suite, or the HiCommand.log file is output when using Oracle JDK, to the following folder: installation-folder-for-Common-Component\CC\web\containers\HiCommand If you are using the Oracle JDK, the HiCommand.log file is overwritten each time it is output. HP recommends saving the file by using a different name after the file is output.
The javacorexxx.xxxx.txt file is output to installation-directory-for-Common-Component/CC/web/containers/HiCommand. Related topics • Starting services, page 191 • Stopping services, page 192 Acquiring a thread dump of the HCS Device Manager Web Service (Linux) To acquire a thread dump of HCS Device Manager Web Service, execute the kill command, and then restart the P9000 Command View AE Suite product services.
In the General tab of Event Properties which is displayed when the event is opened by selecting Event Viewer, Windows Logs, and then Application. Audit log data has the following format. program-name [process-ID]: message-portion • In Linux: The contents of a syslog file Audit log data has the following format. date-time server-name (or IP-address) program-name[process-ID]: message-portion The format and contents of message-portion are described below.
Item#1 Description Message ID. message-ID For details, see “Information included in audit logs” on page 121. date-and-time The date and time when the message was output. This item is output in the format of yyyy-mm-ddThh:mm:ss.stime-zone. detected-entity Component or process name. detected-location Host name. audit-event-type Event type. audit-event-result Event result. audit-event-result-subjectidentification-information Account ID, process ID, or IP address corresponding to the event.
#2: When array information in the message text portion of the Tiered Storage Manager audit log is output, the basic log data indicating the start of the array is output first. Next, detailed log data is output one line at a time for each element of the array, followed by basic log data indicating the end of the array. Output example: ...,i,BasicLog,,,"......NumSD=n, Start SDs" ...,i,DetailLog,,,"SD[1]=(domainId-1,domainName-1)" ...,i,DetailLog,,,"SD[2]=(domainId-2,domainName-2)" ..... ...
Message text for Device Manager server processing When the Device Manager server receives a request for Device Manager server processing (for example, a request to change the configuration or to acquire information) or sends a response for the request, message text about the request or response is output as audit log data. The following explains the format of, and information in, the message text.
Item Description A unique ID that indicates which response (the result of polling the server about the requested operation) corresponds to which request, when a request and the operation are performed asynchronously. request-operation-start-uniqueID This ID corresponds to the message output as an attribute of the RequestStatus element of GetRequestStatus (command: Get, target: RequestStatus). This message ID is output to the detailed message when a request is received.
Format of message text output when the Device Manager server receives a request to launch a related product or sends a response (if an error occurred): unique-ID[ launch-session-ID] error-message-ID Table 105 Information in message text output when the Device Manager server receives a request or sends a response (for launching a product) Item Description unique-ID A unique request identifier. For response transmission, the unique ID of the request is output.
The following examples show output message text.
CAUTION: If a job is created through asynchronous processing, no completion notification is output as audit log data. Table 107 Information in message text output when the Device Manager server receives a request or sends a response (for processing via CIM) Item Description unique-ID A unique request identifier. For response transmission, the unique ID of the request is output. For processing via the SVP, this identifier is also output as audit log data on the SVP.
Message text for Tiered Storage Manager processing If operations are performed from the Tiered Storage Manager CLI or from the Tiered Storage Manager GUI in Legacy mode, the output format of the audit log message text and the information to be output are as follows: message-text operation-type (OP), operation-target (Res) [, failure-cause (RC)][, storage-domain-information (SD)] [, storage-system-information (SS)][, migration-group-information (MG)] [, target-migration-group-information-after-task-completi
Item Description Output format When multiple items exist: NumSD=n, Start SDs 1. Number of elements (n) SD[1]=(id-1,name-1) 2. Storage domain ID (id) ... 3. Storage domain name (name) SD[n]=(id-n,name-n) Number of storage domain information items (n) storage-system-information (SS) 1. Storage system name (name) 2.
Item Description Output format When a single item exists: volume-information (VL) 1. Controller logical device number (devnum) 2. Object ID of LU or LDEV (id) VL=(devnum,id) When multiple items exist: NumVL=n, Start VLs 1. Number of elements (n) VL[1]=(devnum-1,id-1) 2. Controller logical device number (devnum) ... 3. Object ID of LU or LDEV (id) End VLs Number of volumes (n) VL[n]=(devnum-n,id-n) NumVL=n When a single item exists: volume-pair (VP) 1.
Item Description Output format external-connection-settings (EM) Number of external connection settings items (n) NumEM=n When a single item exists: PG=(id) Path group ID (id) path-group-information (PG) When multiple items exist: Number of path group information items (n) emulation-type-information (EM) Number of emulation type information items (n) NumPG=n NumEM=n For a migration task: 1. Task ID (id) 2. Task type (type) = 0 3.
Item Description Output format For multiple types of task information: 1. Number of tasks NumTK=n, Start TKs 2. Task ID (id) TK[1]=(id-1,type-1) 3. Task type (type) ...
Item Description Output format When changing a task: 1. Task status after the change (status) 0x01020600: Executing a task 0x02030000: Erased 0x02040000: Stopped 0x02050000: Stopping mid-task 2.
Message (Specific application information) Message ID Description If the audit log data contains multiple lines, this message appears immediately following the KATS90000-I message. Outputs the subsequent lines of the KATS90000-I message. KATS90020-I This message occurs when, due to successful access to the resources managed by Tiered Storage Manager, an audit event for the Configuration Access type occurred.
OpId OpName Meaning 20 Create Create 30 Delete Delete 40 Modify Update 50 Add Add 60 Remove Remove 70 Change Change status 80 Execute Execute 90 Refresh Refresh 100 Cancel Cancel 110 Stop Stop 120 Choose Select 130 Check Check Table 112 Meanings of the operation targets (Res) output to the audit log ResId ResName Formal name Meaning 10 LC License License information 20 SD Storage Domain Storage domain 21 RS Refresh Status Storage refresh status 30 MG
ResId ResName Formal name Meaning 150 FSR Free Space Range Free space range to be searched for 160 EXM External Mapping External connection settings 170 PG Path Group Path group 180 EM Emulation Emulation The following are examples of audit log data output: TSMgr[00000974]:CELFSS,1.1,1,KATS90000-I,2006-11-09T19:58:45.4+09:00, TSM_Srv, Hostname1,ConfigurationAccess,Success,uid=user01,,,,,,,,,,,, BasicLog,,,"The operation requested by the client has completed.
Commands in message details The table below lists the commands that can be output in message details.
Output character string Full name Operation HostRef HostRefresh HostInfo update HostScan HostScan Automatic host setup HostVol HostVolume Host volume information notification to the Device Manager server HSD HostStorageDomain Host group and iSCSI target configuration change ISCSIForHSD ISCSINameForHostStorageDomain Change of iSCSI names that belong to iSCSI targets JrnlPool JournalPool Pool configuration change LDEVForVolMig LDEVForVolumeMigration LDEV VolumeMigration attribute settin
Output character string Full name Operation Subscrbr Subscriber Event listener addition or deletion TrngPlcy TieringPolicy Tiering policy change URLLink URLLink URL Link information configuration change User User User setting or reference VolFmtPrgrss VolumeFormatProgress Acquisition of the progress of normal formatting of volumes VolMig VolumeMigration Migration plan setting or information acquisition VolShred VolumeShredding Shredding function execution requests or information acqui
Output character string Operation • If the target is StorageArray Also acquires information on an SMI-S enabled storage system. • If the target is URLLink all Also acquires the URL of the management server for an SMI-S enabled storage system. assign Associates a THP/Smart pool with a THP/Smart volume. bulk Creates the specified number of volumes or multiple volumes of the specified size. changerank Changes the tier rank of an external volume.
Output character string Operation • If the target is JournalPool Applies the THP/Smart pool name to storage systems. nameSync:true • If the target is ObjectLabel Applies the volume label to storage systems. noformat Creates a logical unit without formatting. nolabelbefore Assumes an error if a label has already been set. numOfLUs:n Specifies the number of volumes or THP/Smart volumes to be created (indicated by n). • If the target is Host Hosts with the same name are overwritten.
Output character string Operation update Modifies an existing pair configuration. validate:false Does not validate HORCM files when modifying a pair. validate:true Validates HORCM files when modifying a pair. waitingViewSynchro Returns a completion response after the database is updated. ZeroPageReclaim Performs zero page reclaim to release unused capacity. Parameters in message details The format and content of the parameters (parameter, above) output in message details are described below.
The table below shows the sequence in which attribute values are output for each element.
Output character string Full name and content Sequence in which attribute values are output#1 CommandComplete CommandComplete (Information required by clients when the Get Request Status command is issued) -- CommParameters CommParas (Information about how to access the storage system) -- Component (Information about the storage system configuration) Comp Condition (Limits the results of the Get command by using the Filter elements at the same time) Cond -- LU type, element identifier of an LD
Output character string Full name and content Sequence in which attribute values are output#1 DataRetention DataRetention (Data retention information) -- DataRetentions DataRetentions (LDEV data retention information) -- Datastore DS ErrI ErrList (Data store information) -- ErrorInfo error code of the error detected in the storage system, date and time of the error detected (Information about the error that occurred in the storage system) ErrorList number of ErrorInfo elements (A list incl
Output character string Full name and content FreeSpace FreeSpace (Information about the free space in the parity group of the storage system) FileSystem (File system information acquired from the Device Manager agent) FSys Host (Host information used by the logical volume) Host HostInfo HostI (Information about accesses between the LU and host) Sequence in which attribute values are output#1
Output character string Full name and content Sequence in which attribute values are output#1 deviceFileName, vendorID, model#2, serialNumber, port, devNum#4, hsDeviceID, name, , ipAddress, ipv6Address, mountPoint, OSscsiBus, OSscsiID, OSlun, hbaWWN, portWWN, subsystemPortWWN, fileSystemType, fileSystemName, sizeInMB, percentUsed, pairType, dlmPathName, numberOfDlmPath, pairTypeTCMirror, numberOfPath, relatedPathName, portISCSIName, hostGroupID, , , HostStorageDomain HSD (Information about a host group
Output character string Full name and content Sequence in which attribute values are output#1 , name, poolFunction, poolID, threshold, threshold2, threshold2mode, inflowControl, dataOverflowWatch, unitOfPathWatchTime, pathWatchTime, forwardPathWatchTime, useOfCache, speedOfLine, deltaResyncFailure, raidLevel, overProvisioningWarning, overProvisioningLimit, volumeThresholdFlag, tierControl, autoMigration, migrationInterval, monitorStartTime, monitorEndTime, moni
Output character string Full name and content LogicalUnit LU (Information that represents the LU) Sequence in which attribute values are output#1 , number of LDEV contained in a logical unit#4, volume size, emulation mode, default number of port controllers, whether the LU is used as a command device, whether command device security is set, THP/Smart pool volume ID, THP/Smart pool threshold, whether the LU is a Differential Management LU, tier rank
Output character string ObjLabel Full name and content Sequence in which attribute values are output#1 ObjectLabel Object ID, label to give to the object (Sets the object label of the Device Manager server) targetID, label , name Caution: and indicate the element name and element identifier other than those specified for the ObjectName attribute.
Output character string Full name and content Path Path (Information about the path between the host and host group ) Sequence in which attribute values are output#1 , name, port ID, domain ID of host group or iSCSI target, name of the host group or iSCSI target to be operated on, SCSI ID, LUN assigned to the path between the host and host group , device number for logical unit identification#4, port ID of the host group or iSCS
Output character string RepCon Full name and content Sequence in which attribute values are output#1 ReplicationConnection MCU-side port name, RCU-side port name (Information about communication between the MCU and RCU) ReplicationControllerPair RepCtrlPair (Information about MCU and RCU) ReplicationGroup RepGrp (Information about the HORCM instance group) masterPortDisplayName, remotePortDisplayName
Output character string Full name and content Sequence in which attribute values are output#1 , pairName, pvolArrayType#2, pvolSerialNumber, pvolDevNum#4, pvolPortID, pvolPoolID, svolArrayType#2, svolSerialNumber, svolDevNum#4, svolPortID, svolPoolID, replicationFunction#6, muNumber, fenceLevel, copyTrackSize, pvolMngAreaPoolID, svolMngAreaPoolID ReqStatus RequestStatus message ID (Returns the status of the preceding request) messageID
Output character string SmrtFldr Full name and content Sequence in which attribute values are output#1 SmartFolder , logical group path (Information about a logical group) , logicalPath SortCondition SortCond (Element for which SortItems were collected) SortItem SortItem (Sorting conditions within SearchCondition) -- column name used as sort key, sort order, sort priority key, order, priority SearchCondition SrchCond SrcHost (Search conditions for acquiring ListVie
Output character string TrngPlcy Full name and content Sequence in which attribute values are output#1 TieringPolicy , maximum capacity threshold for tier 1, minimum capacity threshold for tier 1, maximum capacity threshold for tier 3, minimum capacity threshold for tier 3 (Tiering policy information for Smart volume#5) URLLink URLLink (Links between a P9000 Command View AE Suite object and an application) User User (Account information of a single u
Output character string Full name and content Sequence in which attribute values are output#1 VolumeFormatProgress VolFmtPrgrss (Progress of normal formatting of the volume) VolumeGroup VolGrp (Volume group information) VolumeMigration VolMig VolShred (Information about the migration plan) -- type, name, volume group capacity, number of drives that belong to the volume group type, name, size, numberOfDisk , owner ID of the
The lower field of each element indicates the output order represented with the names used within Device Manager. #2: This information is output as the storage system model, and is the common output name indicated in Table 119. #3: This information is output as the ObjectName element . is not output as the element attribute.
GUI operations and the corresponding audit log data To determine what operations were performed from the Tiered Storage Manager GUI in Legacy mode by examining the output audit log data: 1. Extract the audit log data output by Tiered Storage Manager (data where the program name is TSMgr). The audit log data created by using the GUI is output by Tiered Storage Manager and has the TSM_GUI application identifier information.
GUI operation Key OpName# ResName# Additional information# Note Displaying a storage domain list M Get SD NumSD -- M Get SD SD -- -- Get RS SD -- Displaying a storage tier list M Get ST SD, NumST -- Displaying storage tier detailed information M Get ST SD, ST -- Creating a migration group M Create MG SD, MG -- Editing a migration group M Modify MG SD, MG -- Deleting a migration group M Delete MG MG -- Displaying a migration group list M Get MG SD, NumM
GUI operation Key OpName# ResName# Additional information# Note Displaying task detailed information M Get TK TK -- Canceling a task M Cancel TK TK -- Stopping a task M Change TK TK -- Modifying a task M Modify TK TK -- Deleting a task M Delete TK TK -- Legend: M: Main key --: Not applicable # For details, see Table 108 through Table 112.
2. To determine the CLI command used, compare the details of the output audit log data with the contents of Table 122 and look for a matching pattern. Except for commands starting with Get, you can identify user-executed commands by examining the audit log data that has an M in the key column.
CLI command CreateStorageDomain OpName ResName Additional information#2 -- Get TK TK M Create SD SD, SS -- -- Get SD SD -- M Create ST SD, ST -- M Create TK TK, SD, MG, NumVL, VLs TK=(id,3,...
CLI command GetMigrationGroups GetPools #1 Key #2 OpName #2 ResName Note M Get FS SS, NumFS Only acquires the number of storage systems specified in the subsystemname parameter M Get MG SD, NumMG, [MGs] -- -- Get_num PO NumPO -- -- Get SD SD -- M Get PO SD, NumPO -- M Get SD NumSD, [SDs] -- -- Get RS NumSD, SDs -- M Get ST SD, NumST, [STs] -- -- Get SD SD -- M Get TK {TK | NumTK} -- -- Get_num VL NumVL -- GetStorageDomains GetStorageTiers Ge
CLI command OpName ResName Additional information#2 M Modify ST SD, ST -- -- Get TK TK -- M Modify TK TK -- Key #1 #2 #2 Note ModifyTask -- Get_summary SD NumSD M Refresh SD SD -- -- Get_summary SD SD -- -- Get MG SD, MG -- -- Get VL SD, NumVL -- M Remove VL SD, MG, VL -- Refresh RemoveVolumeFromMigrationGroup StopTask M Change TK Legend: M: Main key --: Not applicable #1 Indicates key audit log data for determining the command.
14 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 123 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: RAID Manager • RAID Manager • RAID Manager XP • XP RAID Manager This abbreviation is used when it is not necessary to distinguish the following products: • P9000 Snapshot Snapshot • Snapshot • Snapshot XP • XP Snapshot Administrator Guide (Web Version) 335
Support and other resources
A Device Manager server properties This section describes the property files of a Device Manager server. Device Manager server property files Device Manager server property files include property files related to Device Manager configuration information and the Device Manager database. The following table describes the contents of property files of a Device Manager server.
Property file Description • jserver.properties file • cimxmlcpa.properties file This property file is related to the CIM/WBEM functions. • cimxmlscpa.properties file CAUTION: • For ordinary use, you do not need to change the values set in the property files of a Device Manager server. Use extreme caution when you are modifying the values, because you can cause the server to fail or to function incorrectly. Do not modify the values unless you have sufficient expertise.
• The backslash (\) is reserved as an escape character. Since absolute path names in Windows include backslashes, you must add an escape character before every backslash in a Windows path name. For example, the path name of the file C:\CVXPAE\docroot\foo.bar should be entered as C:\\CVXPAE\\docroot\\foo.bar. When you specify properties, there is no need to precede other characters with the escape character \.
server.http.port Specify the port to be used for non-SSL communication by the Device Manager server. The conventional port number used for a standard web server is 80, but there might already be an intranet server running on this port. Moreover, you should avoid low-numbered ports because these could conflict with other services installed on the server. As a general rule, you can pick any port between 1024 and 49151.
CAUTION: If you change the value of this property, you also need to change the following settings: • The port number for the Device Manager server of the information source registered in Replication Manager (for SSL communication with the Device Manager server) • The pop-up blocker settings of the management client, when using Internet Explorer 6 • The hdvmcli.serverurl property of the hdvmcli.properties file in the Device Manager CLI (for SSL communication with the Device Manager server) server.rmi.
server.horcmconfigfile.hostname Specify whether to use the IP address (ipaddress) or the host name (hostname) when Device Manager edits the configuration definition file. Default: ipaddress CAUTION: • Changing the IP address or host name specified when a copy pair was created might disable operations on the copy pair. If this is the case, you need to modify the configuration definition file and refresh the storage systems. • The setting for this property is ignored in Replication Manager.
server.cim.support.job Specify whether a method for creating or deleting a volume, setting or releasing a LUN path, setting or canceling security for a LUN, or creating or deleting a LUSE volume is executed asynchronously or synchronously. If you set this property to true, the method is executed asynchronously. If you set this property to false, the method is executed synchronously. If the CIM client does not support the job control subprofile, specify false.
Default: 5989 CAUTION: If you change the value of this property, also change the HTTPSPort property of the Device Manager server to the same value. Related topics • server.cim.support.protocol, page 343 • HTTPSPort, page 370 server.cim.request.queue.time When using the storage management function of SCVMM 2012 to operate XP24000/XP20000 or XP12000/XP10000/SVS200, you need to change the value of this property to properly execute jobs in a cluster environment in SCVMM 2012.
If you specify true, the information will be synchronized. If you specify false, the information will not be synchronized. Default: false server.mail.enabled Specify whether to send alerts and events to users by email. To enable this email notification function, set this property to true. To disable this function, set this property to false. Default: true CAUTION: If this property is set to true, set the server.mail.smtp.host property. Related topics • server.mail.smtp.host, page 345 server.mail.
server.mail.smtp.port Specify the port number of the SMTP server. To send alerts and events to users by email, you must specify this property. Specifiable range: 0 to 65535. Default: 25 server.mail.smtp.auth Specify whether to use SMTP authentication to send alerts and events to users by email. To use SMTP authentication, set this property to true. To not use SMTP authentication, set this property to false. Default: false server.mail.
server.mail.alert.status Specify the severity of alerts that are sent to users by email. The Device Manager server reports alerts whose severity is equal to or higher than the severity specified for this property. The following values (listed in ascending order of severity) can be specified: Normal, Service, Moderate, Serious, Acute Default: Moderate server.subsystem.ssid.availableValues Specify the range of the SSIDs that can be assigned automatically to storage systems registered in Device Manager.
server.agent.differentialrefresh.periodical.enabled Specify whether to update the database information only for resources whose configuration has changed since the last refresh when automatically refreshing a storage system. This property is valid only for P9500 storage systems. If you specify true for this property, refresh processing is more efficient because database updates are skipped for resources whose configuration has not changed since the last refresh.
dbm.startingCheck.retryPeriod Specify the interval (in seconds) that the Device Manager server (at startup) retries checking of whether the DBMS has started. The specifiable values are from 0 to 60 (seconds). Under normal conditions, you do not need to change the default value of this property. Default: 10 (seconds) Device Manager log output properties (logger.properties file) The logger.properties file contains the log output properties.
Related topics • logger.MaxFileSize, page 350 logger.MaxFileSize Specify the maximum size for the access.log, cim_access.log, error.log, service.log, stdout.log, stderr.log, statuscheck.log, trace.log, CIMOMTrace.log, and SMISClientTrace.log. If the maximum size is exceeded, a new log file is created. Unless KB is specified for kilobytes or MB for megabytes, the specified size is interpreted to mean bytes. Specifiable range: from 512 KB to 32 MB Default: 1 MB logger.hbase.
Related topics • logger.hbase.MaxFileSize, page 351 logger.hbase.MaxFileSize Specify the maximum size of each operation (trace) log file and error log file that is written by Common Component. The log files are HDvMtracen.log, HDvMGuiTracen.log, and HDvMGuiMessagen.log (the n in the file name indicates the backup generation number of the file). The specified size is assumed to be in bytes unless you specify KB for kilobytes, MB for megabytes or GB for gigabytes.
A value of 0 will disable these polling threads. Default: 5 (minutes) server.dispatcher.traps.purgePeriod Specify the purging interval for stale SNMP traps or alerts (in minutes). A value of 0 will disable the purging of traps from the server. Default: 5 (minutes) server.dispatcher.daemon.receiveTrap Specify whether Device Manager receives SNMP traps generated by network resources such as storage systems and switches. To receive SNMP traps, set this property to true.
CAUTION: • If the GUI displays a warning message, manually refresh the corresponding storage system information. You can also specify the settings so that information in the database is automatically updated in case a user forgets to perform a manual refresh after changing the storage system configuration. To do so, set up the following properties: server.dispatcher.daemon.autoSynchro.doRefresh property server.dispatcher.daemon.autoSynchro.
CAUTION: If you specify true, only the information about the P9500 or XP24000/XP20000 is updated in the database. The information in the configuration file of a host that recognizes the command device of P9500 or XP24000/XP20000 is not updated in the database. Related topics • server.dispatcher.daemon.autoSynchro.type, page 354 server.dispatcher.daemon.autoSynchro.
server.dispatcher.daemon.autoSynchro.startTime Specify the time at which storage system information is automatically refreshed (updated) in the database starts in the format hh:mm. Specify a value from 00 to 23 for hh, and 00 to 59 for mm. This property is enabled only if the server.dispatcher.daemon.autoSynchro.type property is set to D or W. In addition, storage system information is automatically refreshed (updated) according to the time zone setting for the management server.
• A • • • • change in the maximum reservation amount of the following volumes: THP pool Smart pool Data pool of Snapshot Data pool of Fast Snap • A change in the monitoring mode for the Smart pool • A change in the settings regarding performance monitoring and hierarchical relocation of the Smart pool • A change in the settings regarding tiering policy for the Smart volume. The Smart volume is a virtual volume created from the Smart pool (associated with the Smart pool).
Default:00:10 Related topics • server.dispatcher.daemon.autoSynchro.performance.doRefresh, page 356 server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh Specify whether to automatically update logical group information when any of the operations below occur. If this property is set to true, logical group information is automatically updated each time one of the events below occurs.
Device Manager client properties (client.properties file) The client.properties file contains the client properties. • In Windows: installation-folder-for-the-Device-Manager-server\Server\config\client.properties • In Linux: installation-directory-for-the-Device-Manager-server/Server/config/ client.properties This property file contains the settings related to display and operation of Device Manager GUI. client.rmi.port Specify the port number for the Device Manager RMI server.
CAUTION: If this property is set to false, any migration tasks created via migration groups cannot be referenced or operated on from Tasks under the Task & Alerts tab. As such, make sure that there are no incomplete migration tasks when changing the value of this property from true to false. If there are any incomplete tasks, end the tasks via one of the following methods: • Execute the tasks immediately.
customizedsnmptrap.customizedSNMPTrapEnable Specify whether to output SNMP traps received by Device Manager to log files. To output SNMP traps to log files, set this property to true. To not output SNMP traps to log files, set this property to false. If you set this property to true, also set the customizedsnmptrap.customizelist property. Default: false NOTE: If the server.dispatcher.daemon.
Item Format Specify the severity of each trap by using one of the character strings below. You cannot use character strings other than the following: severity Remarks This item is optional. If you omit this item, Null is assumed.
Related topics • customizedsnmptrap.customizedSNMPTrapEnable, page 360 Device Manager launchable applications properties (launchapp.properties file) The launchapp.properties file contains the launchable applications properties. • In Windows: installation-folder-for-the-Device-Manager-server\Server\config\launchapp.properties • In Linux: installation-directory-for-the-Device-Manager-server/Server/config/ launchapp.
installation-directory-for-the-Device-Manager-server/Server/config/ host.properties host.mf.agent.connection.timeout Specify the timeout value (in seconds) for communication processing between the Device Manager server and P9000 mainframe agent. Valid values are 0 and from 30 to 3600 (seconds). If you specify 0, no timeout applies. Modify this property only if you are an expert system administrator and you want to fine-tune the performance of P9000 mainframe agent. Default: 300 host.agent.access.
For the IP address, you can use either an IPv4 address or IPv6 address. If you use an IPv6 address, you must enclose the IP address with square brackets ([ and ]). The port number must match the value specified for the property hdc.common.rmi.registryPort or hdc.common.rmi.ssl.registryPort of the hdcbase.properties file. If you omit the port number, it is assumed to be 22098 if the value of the hdc.usessl property is false, and 22104 if the value is true.
CAUTION: The IP address or host name of the computer where Host Data Collector is installed must be the same for the properties hdc.rmiregistry, hdc.rmiserver, and hdc.classloader. In addition, if multiple IP addresses are assigned to the computer where Host Data Collector is installed, specify the same values for the hdc.service.rmi.registryIPAddress property in the hdcbase.properties file of Host Data Collector. Related topics • • • • • • hdc.rmiregistry, page 363 hdc.classloader, page 365 hdc.
• • • • hdc.usessl, page 366 hdc.common.http.serverPort, page 387 hdc.common.https.serverPort, page 389 hdc.service.rmi.registryIPAddress, page 389 hdc.usessl Specify whether to use SSL to communicate between the Host Data Collector machine and the Device Manager server. If SSL is used for communication, specify true.
migration.dataErase.defaultValue Specify the status of the Shredding check box when the Migrate Data wizard starts. When true is set: The Shredding check box is selected. When false is set: The Shredding check box is not selected. To prevent data leaks, HP recommends that you delete the data on migration source volumes after migration. Default: false migration.plan.candidateVolumeCountLimit Specify whether to limit the number of candidate volumes that are displayed when creating a migration plan.
Properties for connecting to PA (hppa.properties file) The hppa.properties file contains properties related to connecting to PA. • In Windows: installation-folder-for-the-Device-Manager-server\Server\config\ hppa.properties • In Linux: installation-directory-for-the-Device-Manager-server/Server/config/ hppa.properties hppa.infoAcquirePeriod Specify the period for which performance information, such as the parity group usage rate and the volume IOPS, is collected and summarized.
Default: 300 Properties for the CIM/WBEM functions (jserver.properties file, cimxmlcpa.properties file, cimxmlscpa.properties file) The jserver.properties file, cimxmlcpa.properties file, and cimxmlscpa.properties file contain properties related to the CIM/WBEM functions. • Location of the jserver.properties file • In Windows: installation-folder-for-the-Device-Manager-server\Server\config • In Linux: installation-directory-for-the-Device-Manager-server/Server/config • Location of the cimxmlcpa.
CAUTION: • If you change the value of this property, you must also change the values of the Device Manager server server.cim.http.port property to the same value. • The cimxmlcpa.properties file is deleted when the service for the Device Manager server starts. Create a new cimxmlcpa.properties file every time the port is changed. Related topics • server.cim.http.port, page 343 HTTPSPort In the case of SSL communication, specify the port number to be used by the CIM/WBEM functionality.
B Tiered Storage Manager server properties This section describes the property files of the Tiered Storage Manager server. Tiered Storage Manager server property files There is a Tiered Storage Manager server property file for Tiered Storage Manager server operations and another property file for accessing the Device Manager server. These property files apply only to operations (processes) from the Tiered Storage Manager CLI or from the Tiered Storage Manager GUI in Legacy mode.
Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux). To change Tiered Storage Manager server properties: 1. Stop the services of P9000 Command View AE Suite product. 2. Use a text editor to set appropriate values in the Tiered Storage Manager server property files. 3. Start the services of P9000 Command View AE Suite product.
Tiered Storage Manager server operations properties (server.properties file) The server.properties file contains properties related to Tiered Storage Manager server operations. • In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\conf\server.properties • In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/conf/ server.properties server.rmi.secure Specify whether to use SSL for communications between the Tiered Storage Manager server and the CLI client.
Related topics • server.rmi.secure, page 373 server.rmi.security.port For configurations using SSL communication, specify the RMI port number used by Tiered Storage Manager to accept processing requests. The range of specifiable values is from 1 to 65535. This property takes effect when 2, 3, or 4 is specified for the server.rmi.secure property. Default: 24500 CAUTION: If you change the value of this property, you also need to change the following settings: • The htsmserver.
Default: htsmserver server.mail.errorsTo Specify the address to which an undeliverable notification email will be sent when an event notification email cannot be delivered. If this property is not specified, the undeliverable notification email is sent to the email address specified in server.mail.from. Note that the conditions for sending undeliverable notification emails vary according to the SMTP server settings. Make sure to review these settings. Default: None Related topics • server.mail.
server.migration.multiExecution Specify the number of migration pairs that can be simultaneously executed in a storage system. The range for specifiable values is from 1 to 64. Default: 8 server.checkOutVolumeRange Specify whether filter conditions used for searching volumes or defining storage tiers have their values checked for validity. Specify a Boolean value for this property. If you specify true, values will be checked. If you specify false, values will not be checked.
Default: true server.migrationPlan.candidateCapacityGroupDisplayMaxCount Specify how many volumes with a larger capacity than the migration source volume to display in addition to the volumes with the same capacity as the migration source volume when creating a migration plan. You can specify a value from 0 to 10. Specify 0 to display only volumes with the same capacity as the migration source volume.
When migration finishes, Tiered Storage Manager requests that the storage system splits the source volume and migration target volume pair. While the storage system is splitting the pair, if another migration in the same task finishes and the storage system begins an internal refresh, the pair will not split properly. Therefore, there must be enough time from when the pair split is requested until the pair split can finish.
client.launch.HPPA.report.host Specify the host name or IP address included in the PA URL when launching the PA GUI from the Tiered Storage Manager GUI in Legacy mode. Default: None client.launch.HPPA.report.port Specify the port number included in the PA URL when launching the PA GUI from the Tiered Storage Manager GUI in Legacy mode. Default: None Tiered Storage Manager database properties (database.properties file) The database.properties file contains properties related to databases.
hdvm.protocol Specify the protocol to be used when accessing the Device Manager server. Default: http hdvm.port Specify the port number of the Device Manager server you are accessing. You must specify the same value as the one specified for the server.http.port property of the Device Manager server. Default: 2001 Related topics • server.http.port, page 340 hdvm.timeout Specify the timeout period (in milliseconds) for communications with the Device Manager server you are accessing.
The following figure shows the relationship between the threshold value of the output levels and the output messages. Figure 26 Relationship between the threshold value of the output levels and the output messages logger.messagelogLevel Specify a threshold output level for the messages logged by Tiered Storage Manager. This property applies to the Tiered Storage Manager server message log (HTSMServerMessagen.log) and the GUI message log (HTSMGuiMessagen.log).
Specify a value from 0 to 30. HP recommends that the default value be used. Default: 20 Table 128 Output level of trace log data Type of message Output level Message descriptions 0 An error occurred that affects the operation of the management server or Java servlet. 10 An execution error occurred due to a reason such as an operational mistake. 20 An error occurred, but execution can continue with limitations.
logger.serverTraceFileCount Specify the number of trace log files used by the Tiered Storage Manager server. The range of specifiable values is from 2 to 16. When a log file reaches the maximum size specified in the logger.serverTraceMaxFileSize property, the file is renamed by adding a counter to the file name (for example, HTSMServerTrace2.log). The log files are used and written to in the order of the counter.
Related topics • logger.guiTraceMaxFileSize, page 384 logger.serverMessageMaxFileSize Specify the maximum size of message log files used by the Tiered Storage Manager server (HTSMServerMessagen.log). The range of specifiable values is from 32,768 bytes (32 KB) to 2,147,483,647 bytes (2,048 MB). When specifying this property, use KB to represent the size in kilobytes, and MB to represent the size in megabytes. If a unit is not specified, it is assumed that the value is specified in bytes.
C Host Data Collector properties This section describes the Host Data Collector property file. Host Data Collector property files The Host Data Collector property files include a property file related to Host Data Collector operation and a property file related to log output. The following table describes the Host Data Collector property files . Table 129 Host Data Collector property files Property file Description hdcbase.properties file This property file is related to Host Data Collector operation.
Properties related to Host Data Collector operation (hdcbase.properties file) The hdcbase.properties file contains properties related to Host Data Collector operation. • In Windows: installation-folder-for-Host-Data-Collector\HDC\Base\config\hdcbase.properties • In Linux: installation-directory-for-Host-Data-Collector/HDC/Base/config/hdcbase.properties hdc.service.
NOTE: If you changed the value of this property, the following settings must be performed: • Use the firewall_setup command to reset the firewall exemptions (when the value of the hdc.ssl.secure property is 1 or 2). • Set the same value as the hdc.rmiregistry property of the Device Manager server (when non-SSL communication is used by Host Data Collector and the Device Manager server). Related topics • Registering an exception for the Host Data Collector service (for non-SSL communication), page 268 • hdc.
NOTE: If you changed the value of this property, the following settings must be performed: • Use the firewall_setup command to reset the firewall exemptions (when the value of the hdc.ssl.secure property is 1 or 2). • Set the same value as the hdc.classloader property of the Device Manager server (when non-SSL communication is used by Host Data Collector and the Device Manager server). Related topics • Registering an exception for the Host Data Collector service (for non-SSL communication), page 268 • hdc.
NOTE: If you changed the value of this property, the following settings must be performed: • Use the netsh command to reset the firewall exemptions (when the value of the hdc.ssl.secure property is 2 or 3). • Set the same value as the hdc.rmiserver property of the Device Manager server (when SSL communication is used by Host Data Collector and the Device Manager server). Related topics • Registering an exception for the Host Data Collector service (for SSL communication), page 269 • hdc.
Default: None# #: If you do not specify an IP address, the IP address acquired by Host Data Collector will be used. Related topics: • hdc.rmiregistry, page 363 • hdc.rmiserver, page 364 • hdc.classloader, page 365 hdc.service.fileCleanup.startTime Specify the time at which host information files that Host Data Collector collected from managed hosts are deleted, in the format hhmm. Specify a value from 00 to 23 for hh, and 00 to 59 for mm. Default: 2300 hdc.adapter.esx.
hdc.ssl.secure property value 3 Port numbers to be opened (Default) RMI server 22099/tcp, 22105/tcp Class loader 22100/tcp, 22106/tcp RMI registry 22098/tcp, 22104/tcp RMI server 22105/tcp Class loader 22106/tcp # The non-SSL communication port for the RMI registry (22098/tcp by default) is always open because it is also used for internal communication by Host Data Collector. Default: 1 Related topics • • • • • • hdc.common.rmi.registryPort, page 386 hdc.common.rmi.serverPort, page 387 hdc.
Message type Output level Description INFO 30 information - 40 debug You can specify 0, 10, 30, or 40. Default: 30 logger.trace.maxFileSize Specify the maximum size of the Host Data Collector trace log. The specified size is assumed to be in bytes unless you specify KB for kilobytes, MB for megabytes or GB for gigabytes. Specifiable range: 4096 to 2147483647. Default: 5242880 logger.trace.numOfFiles Specify the maximum number of backup files for the Host Data Collector log.
generated. After the specified number of backup log files is created, each time a new backup file is created, the oldest backup file is deleted. Specifiable range: 2 to 16. Default: 10 Related topics • logger.iotrace.maxFileSize, page 392 Properties related to the Host Data Collector's Java environment (javaconfig.properties file ) The javaconfig.properties file contains properties related to the Java environment of the Host Data Collector.
Host Data Collector properties
D Device Manager agent properties This section describes the property files of a Device Manager agent. Device Manager agent property files There is a Device Manager agent property file for Device Manager agent operations and a property file for settings related to the connection between the Device Manager agent and the Replication Manager server. The following table describes the Device Manager agent property files. Table 132 Device Manager agent property files Property file Description agent.
2. Use a text editor to set appropriate values in the Device Manager agent property files. 3. Execute the hbsasrv command to start the Device Manager agent service. Related topics • Starting and stopping the Device Manager agent service, and checking the operating status of the service (hbsasrv command), page 233 Device Manager agent properties for connecting to the Replication Manager server (agent.properties file) The agent.
Normally, the values set for these parameters do not need to be changed. To change their values, you need expert knowledge of the Device Manager agent. agent.rm.shutdownWait Specify the wait time when stopping the HORCM instance for monitoring (in seconds). Specify a value from 1 to 60. Default: 5 agent.rm.horcmInstance Specify the instance number of the HORCM file for monitoring. Specify a value from 0 to 4,094.
agent.logger.loglevel Specify the output level of the log file for the Replication Manager agent functionality. Log data that has a level equal to or higher than the specified value is output. Specify one of the following values (listed in ascending order of importance): DEBUG, INFO, WARN, ERROR, FATAL Default: INFO agent.logger.MaxBackupIndex Specify the maximum number of log files for the Replication Manager agent functionality. Specify a value from 1 to 20.
Device Manager agent properties for hldutil command operations (hldutil.properties file) The hldutil.properties file contains properties related to hldutil command operations. • In Windows: installation-folder-for-Device-Manager-agent\util\bin\hldutil.properties • In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/util/bin/hldutil.properties • In AIX: /usr/HDVM/HBaseAgent/util/bin/hldutil.properties agent.util.hpux.
NOTE: The files access.log, error.log, service.log, and trace.log are output to the following locations: In Windows: installation-folder-for-the-Device-Manager-agent\agent\logs\ In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/agent/logs/ In AIX: /usr/HDVM/HBaseAgent/agent/logs/ logger.loglevel Specify the minimum level of log data that the Device Manager agent outputs to the files error.log and trace.log.
logger.MaxFileSize Specify the maximum size of the files access.log, error.log, service.log, and trace.log. If a log file becomes larger than this value, the Device Manager agent creates a new file and writes log data to it. Unless KB is specified for kilobytes or MB for megabytes, the specified size is interpreted to mean bytes. Specify a value from 512 KB to 32 MB. Default: 5 MB The size of an output log file depends on the number of copy pairs managed by Replication Manager.
/opt/HDVM/HBaseAgent/agent/config/server.properties • In AIX: /usr/HDVM/HBaseAgent/agent/config/server.properties server.agent.port Specify the port number for the Device Manager agent's daemon process (or service). Avoid specifying small port numbers because such numbers might conflict with other applications. The normal range is 1024 to 49151. If a version of Hitachi Dynamic Link Manager earlier than 5.8 is installed, specify 23013.
For operation in an IPv6 environment, specify a global address. If you specify a site-local address or link-local address, the IPv4 address will be used. It is necessary to match the IP address version to the one specified in server.http.socket.bindAddress. The IP address that you specified in this property can also be used when creating or editing the RAID Manager configuration definition file.
Related topics • For details on the required memory size for Device Manager: “Settings required for a host to manage 100 or more LUs” on page 228 • For details on the required memory size for Replication Manager:“Managing copy pairs” on page 226 server.agent.shutDownTime Specify the period to shutdown the Device Manager agent's Web server after it receives or sends the last HTTP/XML message (in milliseconds). Specify a value from 1 to 9223372036854775807.
In the following example, the specification permits the address 191.0.0.2 and addresses from 192.168.0.0 to 192.168.255.255 to connect to the Device Manager agent: server.http.security.clientIP=191.0.0.2, 192.168.*.* In the following example, the specification permits the addresses 2001::203:baff:fe36:109a and 2001::203:baff:fe5b:7bac to connect to the Device Manager agent: server.http.security.
disable Specify this value to manage copy pairs for each host when the system uses the local management method. To use the local management method, you need to install the Device Manager agent and RAID Manager on each host. When the local management method is used, if you specify LUs as a copy pair that has different hosts, make sure that each LU is recognized by each host.
server.agent.rm.location Specify the RAID Manager installation directory if RAID Manager is installed in a location other than the default or if the host OS is Windows and the RAID Manager installation drive is different from the Device Manager agent installation drive. For Windows, use a forward slash (/) as the path delimiter. Default for Windows: drive-where-Device-Manager-agent-is-installed/HORCM Default for UNIX: /HORCM server.agent.rm.optimization.
server.agent.rm.temporaryInstance Specify the instance number of the configuration definition file that the Device Manager agent temporarily uses to acquire copy pair information. Specify a value from 0 to 3997. An instance number in the range specified-value to specified-value +98 is used. Default: 900 server.agent.rm.temporaryPort Specify the UDP port number of the configuration definition file that the Device Manager agent temporarily uses to acquire copy pair information.
The following table describes the conditions under which the Device Manager agent decides whether to use the HORCM_DEV or HORCM_LDEV format in the configuration definition file. Table 133 Conditions on which the Device Manager agent decides which format should be used in the configuration definition file Which format is used in the existing configuration definition file Format to be used in the configuration definition file Pair operation If a format is specified in the property: No format is used.
CAUTION: Do not specify HORCM_LDEV in an environment where RAID Manager 01-17-03/04 or later is not installed. If you do this, the message An attempt to create a pair has failed. Error detail, host "host-name" : "error-detail" is displayed, and the attempt to create pairs fails. server.agent.rm.userAuthentication Specify whether to check that the authentication mode for command devices is enabled. Specify true to check that the authentication mode for command devices is enabled.
In Windows: System folder (represented by the environment variable %windir%) In UNIX: /etc directory Related topics • Changing the storage location of the configuration definition file, page 257 server.agent.rm.moduleTimeOut Specify a timeout value for receiving command execution results when the Device Manager agent executes a RAID Manager command (in seconds).
Device Manager agent properties
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
DoS Denial of Services FC Fibre Channel FC-SP Fibre Channel - Security Protocol FCoE Fibre Channel over Ethernet FQDN Fully Qualified Domain Name FTP File Transfer Protocol GUI Graphical User Interface HBA Host Bus Adapter HTTP HyperText Transfer Protocol HTTPS HyperText Transfer Protocol Secure I/O Input/Output ID IDentifier IETF Internet Engineering Task Force IOPS Input Output Per Second IP Internet Protocol IPF Itanium Processor Family IPv4 Internet Protocol Version 4 I
MU Multiple Unit NAS Network Attached Storage NAT Network Address Translation NIC Network Interface Card NPIV N Port ID Virtualization NTP Network Time Protocol OS Operating System P-VOL Primary VOLume PAP Password Authentication Protocol PDEV Physical Device PEM Privacy Enhanced Mail PID Process ID PP Program Product RADIUS Remote Authentication Dial-In User Service RAID Redundant Array of Independent Disks RCU Remote Control Unit RDN Relative Distinguished Name RFC Reque
SNMP Simple network management Protocol SP Service Pack SRV SeRVice SSH Secure SHell SSID Storage Subsystem ID SSL Secure Sockets Layer SSO Single Sign - On SVP Service Processor TCP Transmission Control Protocol TLS Transport Layer Security UDP User Datagram Protocol URL Uniform Resource Locator V-VOL Virtual VOLume WAN Wide Area Network WBEM Web - Based Enterprise Management WWN Worldwide name XML eXtensible Markup Language 416 Acronyms and abbreviations
Index A account.lock.num, 104 acquiring maintenance information on management server, 281 agent.logger.loglevel, 398 agent.logger.MaxBackupIndex, 398 agent.logger.MaxFileSize, 398 agent.properties file, 396 agent.rm.everytimeShutdown, 396 agent.rm.horcmInstance, 397 agent.rm.horcmService, 397 agent.rm.shutdownWait, 397 agent.rm.TimeOut, 396 agent.util.hpux.
client.launch.HPPA.report.port, 359 client.launch.HPPA.report.port (Tiered Storage Manager GUI in Legacy mode), 379 client.launch.HPPA.report.protocol, 359 client.launch.HPPA.report.protocol (Tiered Storage Manager GUI in Legacy mode), 378 client.ldev.rowsperpage.retain.enabled, 378 client.migration.use.legacymode, 358 client.properties, 358 client.properties file, 378 client.rmi.
Device Manager server, 24 audit log data, 291 audit log data using CIM, 294 ports, 72 property files, 337 devicemanager.properties file, 379 dispatcher.
Host Data Collector, 24 acquiring maintenance information, 283 acquiring maintenance information [host], 283 checking version, 271 environment settings, 266 firewall, 268 installing, 261 installing (Linux), 263 installing (Windows), 262 ports, 74 prerequisites for installing, 261 property files, 385 registering on management server, 265 removing, 271 removing (Linux), 272 removing (Windows), 271 resident process, 266 Host Data Collector service checking operating status, 268 exception registration, 268, 269
logger.trace.level, 391 logger.trace.maxFileSize, 392 logger.trace.numOfFiles, 392 logger.tracelogLevel, 381 logs audit log data, 287 setup, 117 M mail-alert-detection.
prerequisites normal host (Device Manager agent), 38 normal host (Host Data Collector), 36 virtual machine (Device Manager agent), 41 virtual machine (Host Data Collector), 38 virtualization server (Host Data Collector), 46 virtualization server (vMA), 47 prerequisites for installing Host Data Collector, 261 programproductinfo.
server.agent.rm.userAuthentication, 410 server.agent.shutDownTime, 404 server.base.home, 341 server.base.initialsynchro, 342, 374 server.checkOutVolumeRange, 376 server.cim.agent, 342 server.cim.http.port, 343 server.cim.https.port, 343 server.cim.request.queue.time, 344 server.cim.support, 342 server.cim.support.job, 343 server.cim.support.protocol, 343 server.configchange.enabled, 344 server.dispatcher.daemon.autoSynchro.dayOfWeek, 354 server.dispatcher.daemon.autoSynchro.doRefresh, 353 server.dispatcher.
starting Device Manager agent service, 233 Host Data Collector service, 267 P9000 Command View AE Suite product service, 191 SLP service, 162 stopping Device Manager agent service, 233 Host Data Collector service, 267 P9000 Command View AE Suite product service, 192 SLP service, 162 Storage Essentials launching, 114 storage location configuration definition file, changing, 257 storage system, 24 acquiring performance information (by using CIM/WBEM functions), 156 copy pair, 53 requirements for managing copy
