HP StorageWorks P9000 Command View Advanced Edition Suite Software Administrator Guide (Web Version) Part number: TB581-96065 Fourth edition: August 2011
Legal and notice information © Copyright 2010-2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Preface .............................................................................................. 21 1 System configuration and requirements ............................................... 23 System configuration ................................................................................................................. Hardware configuration ...................................................................................................... Software configuration ......................
System configuration for managing copy pairs: Using an SVP (when defining copy pairs in a configuration definition file) ........................................................................................ System configuration for managing copy pairs: Using an SVP (when defining copy pairs as a device group) ........................................................................................................... Device Manager agent requirements for managing copy pairs ................................
Creating a message ........................................................................................................... Registering a message ........................................................................................................ Deleting the message .......................................................................................................... Security settings for communication .............................................................................................
Verifying properties for executing CIM ....................................................................................... Configuring service discovery ................................................................................................... Setting up service discovery ............................................................................................... Setting up service discovery (Windows) ........................................................................
Restoring a database in a non-cluster configuration ............................................................... Restoring a database in a cluster configuration ..................................................................... Migrating databases ............................................................................................................... Prerequisites and restrictions on migrating databases ............................................................
Required operations when creating or changing a configuration definition file .......................... Note about deleting copy pairs .......................................................................................... Device Manager agent commands ............................................................................................ firewall_setup command .................................................................................................... hbsa_modinfo command .................
Parameters in message details ..................................................................................... Correlation between user operations and Tiered Storage Manager audit log data .................... GUI operations and the corresponding audit log data .................................................... CLI operations and the corresponding audit log data ..................................................... 284 298 298 301 14 Support and other resources .....................................
logger.hbase.sysloglevel .................................................................................................... logger.hbase.MaxBackupIndex .......................................................................................... logger.hbase.MaxFileSize ................................................................................................. Device Manager dispatcher properties (dispatcher.properties file) ................................................. server.dispatcher.message.
Tiered Storage Manager server operations properties (server.properties file) ................................... server.rmi.secure .............................................................................................................. server.rmi.port .................................................................................................................. server.rmi.security.port ...................................................................................................... server.
log4j.appender.A1.MaxFileSize ......................................................................................... 350 log4j.appender.A1.MaxBackupIndex ................................................................................. 350 D Device Manager agent properties ................................................... 351 Overview of Device Manager agent properties ..........................................................................
When the managed host OS is Linux ......................................................................................... 367 When the managed host OS is HP-UX ....................................................................................... 367 Acronyms and Abbreviations .............................................................. 369 Index ...............................................................................................
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 ..................................................................................................................
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 ..................................... 32 4 Host types managed by Device Manager ................................................................... 35 5 System requirements for using Device Manager to manage virtualization servers .....
26 Port number that must be registered as a firewall exception between the Host Data Collector computer and a host ............................................................................................... 77 27 Port numbers that must be registered as firewall exceptions between the management server and a CIM client ...........................................................................................
58 Settings for registering the HBase Storage Mgmt Common Service as a resource (for Microsoft Cluster Service) ....................................................................................... 171 59 Settings for registering the HBase Storage Mgmt Web Service as a resource (for Microsoft Cluster Service) .....................................................................................................
89 HORCM_CMD parameter items and descriptions ...................................................... 224 90 HORCM_DEV parameter items and descriptions ....................................................... 224 91 HORCM_LDEV parameter items and descriptions ...................................................... 224 92 HORCM_INST parameter items and descriptions ...................................................... 225 93 firewall_setup command syntax ........................................................
122 Targets output in message details ............................................................................ 281 123 Options output in message details ........................................................................... 283 124 Parameter information output in message details ....................................................... 285 125 Sequence in which attribute values are output for each element ................................... 285 126 Common output names for storage system models ......
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.
WARNING! P9500, XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128 have a public LAN and a private LAN. Device Manager uses the public LAN to communicate with the SVP about the array and configuration changes. Do not under any circumstances attach the private LAN to an external network because this can cause serious problems on the array. Common security risks System administrators frequently separate production LANs from management LANs.
CAUTION: When a P9500, XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128 storage system is operated from Element Manager, the storage system communicates directly with Java™ Web Start and the Web browser on the management client. For this reason, if the storage system and the management client are on different networks, you must set up the networks so that the storage system and the management client can communicate directly with each other.
CAUTION: When a P9500, XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128 storage system is operated from Element Manager, the storage system communicates directly with Java Web Start and the Web browser on the management client. For this reason, if the storage system and the management client are on different networks, you must set up the networks so that the storage system and the management client can communicate directly with each other.
CAUTION: When a P9500, XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128 storage system is operated from Element Manager, the storage system communicates directly with Java Web Start and the Web browser on the management client. For this reason, if the storage system and the management client are on different networks, you must set up the networks so that the storage system and the management client can communicate directly with each other.
Figure 5 Least secure configuration: flat network Management server requirements This section describes the system requirements for the management server. Memory heap size settings by the number of managed resources An adequate memory heap size must be specified to handle the number of resources assumed in the environment managed by Device Manager, Tiered Storage Manager, and Replication Manager.
#: The total of the number of LDEVs for mainframes and the number of LDEVs for open systems. Setting the memory heap size of Common Component The table below contains guidelines for determining the memory heap size to be set. Specify the larger of the values determined by using the number of LDEVs and the number of copy pairs, respectively.
To set the memory heap size of Common Component: 1. Stop the P9000 Command View AE Suite product services. 2. In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop. In Linux®: installation-directory-for-Common-Component/bin/hcmdssrv -stop Check the current setting for the memory heap size. In Windows: installation-folder-for-Common-Component\bin\hcmdschgheap /print 3.
Memory heap size OS Managed resource OS other than Windows (x86 or IPF) Number of LDEVs per storage system 256 MB (Min: 128 MB) 512 MB (Min: 128 MB) 1,024 MB (Min: 128 MB) 2,000 or less 2,001 to 6,000 6,001 or more Legend: --: You cannot specify this memory heap size. To set the memory heap size of the Device Manager server: 1. Use a text editor to open the following file. In Windows: installation-folder-for-the-Device-Manager-server\Server\Server.ini 2.
NOTE: • If you perform an overwrite or upgrade installation of an Oracle Sun JDK during operation of any P9000 Command View AE Suite product, re-register the JDK after the installation. • If you uninstall an Oracle Sun JDK during operation of any P9000 Command View AE Suite product, make sure that you change to the JDK bundled with P9000 Command View AE Suite. • If the version of the P9000 Command View AE Suite products installed on the management server is 7.
Host requirements Device Manager can manage, as hosts, computers that use volumes on managed storage systems. By assigning the most appropriate volume based on usage, you can centrally manage the disk resources for individual hosts by using Device Manager. Host types managed by Device Manager The following table lists the types of computers that Device Manager can manage as hosts.
• admin$ is shared over the network. • In the Windows Firewall settings, File and Printer Sharing is registered as an exception. When the OS of a normal host to be managed is UNIX (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. Prerequisites for normal hosts managed by Device Manager agent Install a Device Manager agent on the normal hosts to which you want to allocate volumes. NOTE: If a normal host is managed by both Host Data Collector and the Device Manager agent, the Device Manager agent is given priority in displaying the acquired information in the GUI and CLI.
Figure 6 System configuration of virtual machines supported by Device Manager Prerequisites for virtual machines managed by Device Manager agent The prerequisite environment differs depending on the configuration of virtual machines, as follows: • If an HBA is allocated for each virtual machine: Install a Device Manager agent on each virtual machine to which you want to allocate volumes.
For each volume, you need to assign a path to the virtual machine (WWN) that you registered in Device Manager. After assigning the paths, make the virtual machines recognize the volumes as RAW devices. NOTE: If multiple virtual machines share the same HBA, regardless of which virtual machine you assign a volume to, you need to assign all paths for that HBA to the virtual machine that is managed by Device Manager.
2. Execute the following command on the management server to register information of the virtual WWNs in Device Manager. In Windows: installation-folder-for-the-Device-Manager-server\Server\tools\ createnpivinfo [-v] [host-name-or-IP-address user-ID password] In Linux: installation-directory-for-the-Device-Manager-server/Server/tools/ createnpivinfo [-v] [host-name-or-IP-address user-ID password] • -v Specify this option to display details of the command execution result in the standard output.
Prerequisite environment for virtualization servers To use Device Manager to manage virtualization servers, the following requirements must be satisfied. Table 5 System requirements for using Device Manager to manage virtualization servers Prerequisite software Connection type between virtualization servers and storage systems (Upgrade 2 or later) None#1 FC VMware ESX Server 3i Version 3.5 vMA#2 FC VMware ESX 4.0 vMA#2 FC VMware ESXi 4.0 vMA#2 FC VMware ESX 4.1 vMA#2 FC VMware ESXi 4.
Device Manager settings for virtualization servers Device Manager supports the system configurations described below. 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.
Figure 7 System configuration in which vMA monitors VMware ESX that is in the same physical environment Figure 8 System configuration in which vMA monitors VMware ESX that is in a different physical environment In Figure 7, when you specify the vMA information, virtualization server A is registered in Device Manager. In Figure 8, when you specify the vMA information, virtualization server B is registered in Device Manager.
information, the physical environments managed by VMware vCenter Server are registered as virtualization servers. Figure 9 shows an example of a system configuration in which VMware vCenter Server is monitored by vMA. Figure 9 System configuration in which vMA monitors VMware vCenter Server In Figure 9, when you specify the information of vMA, virtualization servers A, B, and C are registered in Device Manager.
Figure 10 System configuration in which VMware ESX is operated without using vMA In this configuration, depending on the virtualization server configuration and the number of connected volumes, it might take several hours to register and refresh the virtualization server in Device Manager. Virtualization server management • To check the most recent information about virtualization server volumes, perform either of the following operations from Device Manager: • Manually refresh each virtualization server.
Prerequisite environment for mainframe hosts To use Device Manager GUI to check the information about volumes assigned to a mainframe host, you need to install P9000 mainframe agent on the mainframe host. The following table lists the versions of P9000 mainframe agent supported by Device Manager. Table 6 Versions of P9000 mainframe agent supported by Device Manager Mainframe host platform Platform version P9000 mainframe agent version OS/390 2.10 5.1 or later z/OS 1.1 to 1.12 5.
HP Storage Essential HP Storage Essential acts as the main console for heterogeneous storage infrastructure management software, providing SAN visualization and reporting, asset management, performance and capacity monitoring and planning, and policy-driven event management.
NOTE: • If copy pairs are managed in a configuration that uses an SVP (the out-of-band method), the processing time of Replication Manager might increase because the command response time of RAID Manager tends to increase, compared to when copy pairs are managed in a configuration that uses a physical command device (the in-band method). • In SVP configurations, you can use the GUI to check the configuration of and change the pair status of copy pairs defined as device groups.
Figure 11 Example of a system configuration for managing copy pairs (local management) • A host that recognizes the P-VOL or S-VOL must be registered in the Device Manager server. • The P-VOL or S-VOL is managed by a single Device Manager server. • From the P-VOL or S-VOL, LUN security must be set for the host.
The setting is required when managing partitioned resources in P9500. 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. • 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.
Figure 12 Example of a system configuration for managing copy pairs (configuration that uses a pair management server) • The server.agent.rm.centralizePairConfiguration property for the Device Manager agent on the pair management server must be set to enable (default: disable). • The pair management server and application servers that recognize the P-VOL and S-VOL are registered in the Device Manager server. • The P-VOL and S-VOL are managed by a single Device Manager server.
• All pool volumes that make up a pool (when managing Snapshot pairs) • All journal volumes that make up a journal (when managing Continuous Access Journal pairs) • A shared resource group in which a command device has been registered must be created and assigned to each user. The setting is required when managing partitioned resources in P9500.
Figure 13 Example of a system configuration for managing copy pairs (configuration that uses a virtual command device server) • Application servers that recognize the P-VOL and S-VOL must be registered in the Device Manager server. • The P-VOL and S-VOL are managed by a single Device Manager server. • From the P-VOL and S-VOL, LUN security must be set for the application server. The virtual command device server does not need to recognize the P-VOL or S-VOL.
• Device Manager agent version 7.1 or later must be installed on the application servers. For details on the correspondence between copy pair operations and required Device Manager agent versions, see “Device Manager agent requirements for managing copy pairs” on page 58. • RAID Manager version 01-25-03/01 or later must be installed on the application servers and virtual command device server. For details on how to install RAID Manager, see the relevant manual for RAID Manager.
Figure 14 Example of a system configuration for managing copy pairs (configuration in which an SVP is used as a virtual command device and copy pairs are defined in a configuration definition file) • Application servers that recognize the P-VOL and S-VOL must be registered in the Device Manager server. • The P-VOL and S-VOL are managed by a single Device Manager server. • From the P-VOL and S-VOL, LUN security must be set for the application server.
• RAID Manager version 01-25-03/01 or later must be installed on the pair management server. For details on how to install RAID Manager, see the relevant documentation for RAID Manager. CAUTION: • You need to authenticate users by executing the raidcom command on the management server before performing copy pair operations from the GUI or CLI. If the management server OS is Windows, you need to authenticate users as a Device Manager agent service (HBsA Service) execution user.
Figure 15 Example of a system configuration for managing copy pairs (configuration in which an SVP is used as a virtual command device and copy pairs are defined as a device group) • Application servers that recognize the P-VOL and S-VOL must be registered in the Device Manager server. • The P-VOL and S-VOL are managed by a single Device Manager server. • From the P-VOL and S-VOL, LUN security must be set for the application server. The management server does not need to recognize the P-VOL or S-VOL.
• Either of the conditions below is satisfied on the management server. • Neither the P-VOL nor S-VOL is assigned. If you want to create a copy pair from the management server, specify enable for the server.agent.rm.centralizePairConfiguration property of the Device Manager agent on the management server (default: disable). • The server.agent.rm.ignorePairStatus property for the Device Manager agent on the management server must be set to true.
If you use the CLI to operate copy pairs, the required version of the Device Manager agent differs depending on the program, operation, and storage system model to be used. Table 9 Device Manager agent requirements for managing copy pairs by using the CLI Program Operation from Device Manager Device Manager agent version# Display the status 1.1 or later Display the status (3DR) 5.5 or later Change the status 5.6 or later Change the status (3DR) 5.5 or later Display the status 1.
Storage system requirements for managing copy pairs In Device Manager, copy pairs in the following storage systems can be managed. Table 11 Copy pairs in the storage systems that can be managed by Device Manager Storage system GUI CLI P9500 Y Y XP24000/XP20000 Y Y XP12000/XP10000/SVS200 Y Y XP1024/XP128 N N Legend: Y: Supported, N: Not supported This section describes the storage system requirements for changing the copy pair configuration.
The following table describes the storage system requirements for managing copy pairs. Table 12 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.#2 • The MCU port for an MCU-RCU path must be an Initiator port, and the RCU port must be an RCU Target port.
#1: For mainframe volume copy pairs, you can only check the configuration by using the Device Manager CLI. There are no storage system requirements for checking the copy pair configuration by using the Device Manager CLI. #2: The settings specified in Continuous Access can be shared with Continuous Access Journal. However, in Continuous Access Journal, the settings must be specified for both storage systems used for the P-VOL and the S-VOL.
NOTE: • For the CLI, you do not need to specify a fence level nor a copy pace. Even if you specify these items, they are not applied to the configuration definition file. • You can use the GUI or CLI to check the HORCM instance number, pair group name, and pair name in a created configuration definition file. • For a a Business Copy copy pair and a a Snapshot copy pair, the Device Manager sets 0 as the MU number in 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 If you use Device Manager with other programs on a computer, be sure to avoid duplicating port numbers.
Port number Description Used internally for Common Component communication (receiving a termination message from the Web server). If a product other than Common Component is using this port number, change the settings of that product or of Common Component. For details about how to change the Common Component settings, see “Changing ports used by Common Component” on page 69. 23018/tcp Used internally for Common Component communication (communication with the Web server).
Port number Description Used internally for Device Manager server communication, for communication with management clients (via the GUI or the CLI), and for communication with hosts (Device Manager agents). 2001/tcp# This port number is used as the temporary port assigned by default in Windows. Therefore, we recommend that you change this port number setting for the Device Manager server by modifying the server.http.port property in the server.properties file.
Ports used by Host Data Collector The following table describes the ports used by Host Data Collector. Table 16 Ports used by Host Data Collector Port number Description 22/tcp Used for SSH communication with a host whose OS is UNIX®. 23050/tcp Used internally for Host Data Collector communication. 23051/tcp Used for communication with the Device Manager server. 23052/tcp Used internally for Host Data Collector communication.
systems use the same port numbers as the ones specified in the services file, an error will not occur but the operation might take a long time. For details about how to check the port numbers and how to specify entries in the services file, see the documentation for each storage system. Changing ports used by Common Component To change the ports used by Common Component after installing the P9000 Command View AE Suite products: 1. Stop the services of P9000 Command View AE Suite products.
NOTE: If you change the port number used to access HBase Storage Mgmt Web Service, depending on the operating environment, you might have to revise the following settings: • If the Plug-in for Virtualization Server Provisioning is being used You must change the settings for the Plug-in for Virtualization Server Provisioning. For details about how to change the settings, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Plug-in for Virtualization Server Provisioning User Guide.
Changing the 23017/tcp port used by Common Component To change the port used for communication with the Web server, you must change the port number written in the following files: In Windows: • worker.worker1.port in installation-folder-for-Common-Component\CC\web\redirector\workers.properties • webserver.connector.ajp13.port in installation-folder-for-Common-Component\CC\web\containers\HiCommand\ usrconf\usrconf.properties In Linux: • worker.worker1.
• worker.worker5.port in installation-directory-for-Common-Component/CC/web/redirector/workers.properties • webserver.connector.ajp13.port in installation-directory-for-Common-Component/CC/web/containers/ DeviceManagerWebService/usrconf/usrconf.properties Changing the 23026/tcp port used by Common Component To change the port through which a termination message from the Web server is received, you must change the port number written in the following file: In Windows: • webserver.shutdown.
• • • • • • • • • • Between Between Between Between Between Between Between Between Between Between the the the the the the the the the the management client and storage systems management server and a normal host management server and a virtualization server management server and a mainframe host Device Manager management server and the PA management server management server and the Host Data Collector computer Host Data Collector computer and a host management server and a CIM client management server
Port number Originator Destination Remarks • XP1024 • XP128 • XP12000 1099/tcp Management server • XP10000 • SVS200 - • XP24000 • XP20000 • P9500 • XP12000 • XP10000 2001/tcp# • SVS200 Management server • XP24000 • XP20000 Set up the firewall so that communication can be established from any port of the storage system to the 2001/ tcp port of the management server.
The following table describes the port numbers that must be registered as firewall exceptions between the management client and storage systems.
The following table describes the port numbers that must be registered as firewall exceptions between the management server and a normal host. Table 21 Port numbers that must be registered as firewall exceptions between the management server and a normal host Port number Originator Destination Remarks 2001/tcp# Normal host Management server - 24041/tcp# Management server Normal host - 24042/tcp# Management server Normal host - Legend: -: Not applicable #: This port number can be changed.
-: Not applicable #: This port number can be changed. The following table describes the port numbers that must be registered as firewall exceptions between the Device Manager management server and the PA management server.
The following table describes the port numbers that must be registered as firewall exceptions between the management server and a CIM client. Table 27 Port numbers that must be registered as firewall exceptions between the management server and a CIM client Port number Originator Destination Remarks 427/tcp CIM client Management server - 5988/tcp# CIM client Management server This setting is required when non-SSL communication is used.
This is the mail server specified for the server.mail.smtp.host property of the Device Manager server. #3: This is the mail server specified for the server.mail.smtp.host property of the Tiered Storage Manager. The following table describes the port numbers that must be registered as firewall exceptions between the management server and an external authentication server.
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. Example: Other ports 162:udp 2001:tcp 23015:tcp NOTE: If a port is already specified, use a space to separate it from the newly added entry. 5. After returning to the Firewall Configuration window, check that Security Level is Enabled, use the tab key to move to the OK button, and then press Enter.
Figure 16 Configuration example using a server computer that has two NICs If you set up the configuration shown in Figure 16, set up routers, the management client, and the management server so that the following devices can communicate with each other as shown by the arrows in the figure: • XP12000/XP10000/SVS200 and the management client • XP12000/XP10000/SVS200 and the management server (the server computer whose IP address is 10.0.0.
#: The host name must be resolvable to the IPv6 address. CAUTION: If XP24000/XP20000 storage or XP12000/XP10000/SVS200 storage that is managed via an IPv4 address is also set up as a Device Manager management-target, IPv4 addresses must also be set for any NICs that have IPv6 addresses specified for the server.http.host property. Settings for migrating Device Manager to an IPv6 environment If Device Manager is used in an IPv4 environment and you then wish to use it in an IPv6 environment, edit the httpsd.
ServerName example.com : Listen 23015 Listen [::]:23015 SSLDisable : SSLSessionCacheSize 0 Listen 23016 #Listen [::]:23016 ServerName example.com SSLEnable : CAUTION: Do not delete or edit the default setting, Listen 23015. If you do this, communication using IPv4 will no longer be available. Settings to establish SSL communication when migrating Device Manager to an IPv6 environment Remove the hash mark (#) from the line that includes Listen [::]:23016 (the default setting).
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. Changing the IP address of the management server This section describes the settings that are required if the IP address of the management server is changed.
4. Make sure that the P9000 Command View AE Suite product services are running properly. • In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Status. • In Linux: installation-directory-for-Common-Component/bin/hcmdssrv -status 5. If the IP address is used in the URLs of P9000 Command View AE Suite products, change the settings of all P9000 Command View AE Suite products that are installed on the management server.
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.
name of the management server. For details about the settings for other P9000 Command View AE Suite products, see the manuals for the relevant products. • When the old host name or IP address is specified for the server.http.host property: You need to replace the old host name or IP address with the new host name or IP address, and then restart the services of P9000 Command View AE Suite products.
Options print: Specify this option to display a list of URLs and programs that are currently registered. list: Specify this option to display the same information as the print option in a different format. change: Specify this option to change a currently registered URL. CAUTION: • The specified URL must be a complete URL that contains protocols and a port number. You cannot use an IPv6 address.
To disconnect the network: 1. Stop the services of the P9000 Command View AE Suite products. • In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop. • In Linux: installation-directory-for-Common-Component/bin/hcmdssrv -stop 2. Edit the pdsys file and the def_pdsys file. Change the value for the pdunit parameter's -x option to the loopback address 127.0.0.1.
6. Make sure that the services of P9000 Command View AE Suite products are running. • In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Status. • In Linux: installation-directory-for-Common-Component/bin/hcmdssrv -status 7. Disconnect the network, and then change the settings or perform maintenance. 8. After the network becomes available, start the services of other P9000 Command View AE Suite products.
3 User account management This chapter describes the settings required for managing user accounts of P9000 Command View AE Suite products. Password conditions for user accounts To prevent user passwords from being guessed by a third party, P9000 Command View AE Suite products allow you to specify password conditions. For example, you can specify a minimum number of characters and a required combination of character types. The password conditions are set in the security.
Item Description password.check.userID Specifies whether the password can be the same as the user ID. Specify true or false. If true is specified, passwords cannot be the same as the corresponding user ID. If false is specified, passwords can be the same as the corresponding user ID. Default: false When you change a setting in the security.conf file, the change takes effect immediately. The password conditions that you set in the security.
attempts is allowed. When you change a setting in the security.conf file, the change takes effect immediately. Unsuccessful attempts to log on to other products in the P9000 Command View AE Suite that use the Single Sign-On function count towards the number of unsuccessful logon attempts.
For value, specify true or false. If you specify true, the System account is subject to automatic and manual locking. If you specify false, the System account is not subject to automatic or manual locking. Note that you need to restart P9000 Command View AE Suite products services for the value set in the user.conf file to take effect. CAUTION: • If P9000 Command View AE Suite product versions 6.1 or later are installed and true is set in the user.
4 Security This chapter describes the security settings required to operate P9000 Command View AE Suite products. Login warning banner In version 5.1 or later of P9000 Command View AE Suite products, an optional message (warning banner) can be displayed as a security risk measure at login. Issuing a warning beforehand to third parties that might attempt invalid access can help reduce the risk of problems such as data loss or information leakage.
CAUTION: • When the message is registered, the HTML syntax is neither checked nor corrected. Edit the message correctly in accordance with HTML syntax rules because the edited message will be registered as is. If there is an error in the HTML syntax in the message, the message might not be displayed correctly in the Login panel. • There are no restrictions on the characters usable in the message, other than that the character encoding must be Unicode (UTF-8).
The locale for a warning banner displayed in the GUI is set, according to the priority of the language set for the web browser that is used. If the locale option is omitted, you can edit the registered contents from the GUI also. However, available HTML tags are limited when you edit from the GUI. Return values 0: Normal termination 253: The number of characters in the message exceeds 1,000 characters. 255: Failure Deleting the message You use the hcmdsbanner command to delete a registered message.
2. Open the httpsd.conf file. The httpsd.conf file is stored in the following location: • In Windows: installation-folder-for-Common-Component\httpsd\conf\httpsd.conf • In Linux: installation-directory-for-Common-Component/httpsd/conf/httpsd.conf 3. In the last line of the httpsd.conf file, register information about management clients that can be connected to the Device Manager server. The following shows how to specify the httpsd.
5. Start the services of P9000 Command View AE Suite product. • In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Start. • In Linux: installation-directory-for-Common-Component/bin/hcmdssrv -start CAUTION: If you log on to a P9000 Command View AE Suite product from a management client that is not registered in the httpsd.conf file, the GUI cannot be started from that P9000 Command View AE Suite product.
Security
5 Configuring Device Manager for use with related products This chapter describes the settings required for linking with related products. Linking with PA By linking with PA, you can use the Mobility tab to check performance information and launch the PA GUI in Tiered Storage Manager. Prerequisites for displaying performance information The following are the prerequisites for displaying performance information, such as parity group usage rates and IOPS: • PA has been set up.
4. Confirm that the settings are specified correctly by using either of the following methods: • When using the GUI: In the Refresh Storage Systems window, select the Refresh Performance data check box, and then refresh the storage system. After that, in the Data Collection Tasks tab, confirm that Completed is displayed for Status of the Refresh Storage Systems task. • When using the CLI: Execute the RefreshPerformanceData command, and confirm that the command finished successfully.
Using Storage Essentials To start Storage Essentials from GUI, you must create the StorageEssentials.conf file and store it in the following location: In Windows: installation-folder-for-Common-Component\common In Linux: installation-directory-for-Common-Component/common In the StorageEssentials.conf file, specify the LaunchURL parameter in the following format: LaunchURL=Storage-Essentials-URL In Storage-Essentials-URL, specify the URL used to start HP Storage Essentials.
Configuring Device Manager for use with related products
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 to acquire log data for P9000 Command View AE Suite products, which use common log files. P9000 Command View AE Suite products use this library to output log data to log files.
Setting the number of Common Component trace log files (Linux) The utility program is stored in the following path: /opt/hitachi/HNTRLib2/bin/hntr2util To specify the number of trace log files: 1. Log in to the system as root. 2. Execute hntr2util. A menu appears. 3. From the menu, select Number of log files. The submenu appears. Hitachi Network Objectplaza Trace Library 2 - Configuration Utility Rel 1.0 Type the number of files [1-16] (Type '!' to return) Current Number: 4 New Number: 4.
program-files-folder\Hitachi\HNTRLib2\bin\hntr2util.exe To change the size of the trace log files: 1. Log in to the system as a user with Administrator privileges. 2. Execute hntr2util.exe. 3. The Hitachi Network Objectplaza Trace Utility 2 window is displayed (see Figure 17). 4. Enter the desired size for the trace log files, and then select OK.
The following table describes the properties set in the HtsmgetTI.properties file. Table 31 Properties set in the HtsmgetTI.properties file Property Description Specify the directory in which Tiered Storage Manager CLI is installed. The following are the default installation directories: In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\CLI CLI_DIR In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/ CLI Specifies the absolute path to syslog.
Categories Description Events indicating that a device, administrator, or end user succeeded or failed in connection or authentication: • FC login Authentication • Device authentication (FC-SP authentication, iSCSI login authentication, SSL server/client authentication) • Administrator or end user authentication Events indicating that a device, administrator, or end user succeeded or failed in gaining access to resources: AccessControl • Access control for devices • Access control for the administrator
• Authentication • ConfigurationAccess • AccessControl • ExternalService Each audit event is assigned a severity level. You can filter audit log data to be output according to the severity levels of events. Table 33 to Table 37 describe the audit log data that can be generated by Device Manager and Tiered Storage Manager. For details on the audit log data generated by other P9000 Command View AE Suite products, see the manuals for the relevant products.
Type description Audit event Severity Message ID Successful multiple user deletion 6 KAPM07231-I Failed multiple user deletion 3 KAPM07240-E Successful password change by the administrator 6 KAPM07232-I Failed password change by the administrator 3 KAPM07240-E Failed authentication processing for verifying old password 3 KAPM07239-E Successful change of login user's own password (from the user's own window) 6 KAPM07232-I Failed change of login user's own password (from the user's own w
Type description Audit event Severity Message ID Successful change of an authorization group's permission 6 KAPM07250-I (GUI) Failed change of an authorization group's permission 3 KAPM07248-E User registration Successful registration of user 6 KAPM07241-I Failed to register user 3 KAPM07242-E User information update Successful update of user information 6 KAPM07243-I (GUI and CLI) Failed to update user information 3 KAPM07244-E User deletion Successful deletion of user 6 KAPM07
Type description Audit event Severity Message ID Assignment of a user account to a user group Successful assignment of the user account to the user group 6 KAPM07275-I Failed assignment of the user account to the user group 3 KAPM07276-E Assignment of a permission to a role Successful assignment of the permission to the role 6 KAPM07277-I (CLI) Failed assignment of the permission to the role 3 KAPM07278-E 6 KAPM07279-I 3 KAPM07280-E Successful backup using the hcmdsbackups command 6
Type description Authentication data input/output Audit event Severity Message ID Successful database area deletion using the hcmdsdbsetup command 6 KAPM06350-I Failed database area deletion using the hcmdsdbsetup command 3 KAPM06351-E Successful data output using the hcmdsauthmove command 6 KAPM05832-I Failed data output using the hcmdsauthmove command 3 KAPM05833-E Successful data input using the hcmdsauthmove command 6 KAPM05834-I Failed data input using the hcmdsauthmove command 3
Type description Acquisition of storage domain information#3 Acquisition of migration group information#3 Acquisition of storage system information#3 Acquisition of task information#3 Audit event Severity Message ID Successful acquisition of all storage domain information 6 KATS90000-I Failed acquisition of storage domain information 4 KATS90001-W Successful acquisition of storage domain information 6 KATS90000-I Failed acquisition of storage domain information 4 KATS90001-W Successful a
Type description Acquisition of storage tier information#3 Acquisition of pool information#3 Acquisition of keystore file information#3 Acquisition of volume information#3 116 Audit event Severity Message ID Successful acquisition of task information 6 KATS90000-I Failed acquisition of task information 4 KATS90001-W Successful acquisition of all task summary information 6 KATS90000-I Failed acquisition of all task summary information 4 KATS90001-W Successful acquisition of task summary
Type description Acquisition of information about unused capacity of parity groups#3 Acquisition of external connection settings#3 Storage domain operations#3 Migration group operations#3 Audit event Severity Message ID Failed acquisition of volume search conditions 4 KATS90001-W Successful acquisition of volume summary information 6 KATS90000-I Failed acquisition of volume summary information 4 KATS90001-W Successful acquisition of parity group information 6 KATS90000-I Failed acquisiti
Type description Task operations#3 Storage tier operations#3 Audit event Severity Message ID Successful update of migration group information 6 KATS90000-I Failed update of migration group information 4 KATS90001-W Successful creation of a migration plan 6 KATS90000-I Failed creation of a migration plan 4 KATS90001-W Successful deletion of a migration plan 6 KATS90000-I Failed deletion of a migration plan 4 KATS90001-W Successful task cancellation 6 KATS90000-I Failed task cancell
#3: This information is output only by operations from the Tiered Storage Manager CLI or the Tiered Storage Manager GUI in Legacy mode.
Type description Authentication with an external authentication server User authentication on an external authentication server Acquisition of information from an external authentication server Audit event Severity Message ID Failed communication with the Kerberos server (no response) 3 KAPM10121-E Successful communication with the DNS server 6 KAPM10122-I Failed communication with the DNS server (no response) 3 KAPM10123-E Successful TLS negotiation with the LDAP directory server 6 KAPM10
To apply the changes to the environment settings file for the audit log, you need to restart the services of the P9000 Command View AE Suite products. CAUTION: A large volume of audit log data might be output. Change the log file size and back up or archive the generated log files accordingly. The auditlog.conf file is stored in the following location: • In Windows: installation-folder-for-Common-Component\conf\sec\auditlog.conf • In Linux: installation-directory-for-Common-Component/conf/sec/auditlog.
The table below shows the values that can be set for Log.Facility and the corresponding values specified in the syslog.conf file. Table 39 Log.facility values and the corresponding values in syslog.conf Facility Corresponding values in syslog.conf 1 user 2 mail# 3 daemon 4 auth# 6 lpr# 16 local0 17 local1 18 local2 19 local3 20 local4 21 local5 22 local6 23 local7 #: Although you can specify this value, we do not recommend that you specify it.
The following shows an example of the auditlog.conf file: # Specify an integer for Facility. (specifiable range: 1-23) Log.Facility 1 # Specify the event category. # You can specify any of the following: # StartStop, Failure, LinkStatus, ExternalService, # Authentication, AccessControl, ContentAccess, # ConfigurationAccess, Maintenance, or AnomalyEvent. Log.Event.Category Authentication,ConfigurationAccess # Specify an integer for Severity. (specifiable range: 0-7) Log.
Storage system Storage system site status SNMP traps XP12000/XP10000/SVS200 Y Y XP1024/XP128 Y Y Legend Y: Supported --: Not supported Required settings for receiving SNMP traps For Device Manager to receive SNMP traps output by storage systems, the following settings must be specified: • Device Manager must be able to use port 162/udp of the management server.
The Device Manager server supports the following SMTP authentication methods: LOGIN or PLAIN. Make sure that you specify one of these authentication methods in the SMTP server that you use. Registering recipients of email alerts Use the Device Manager GUI to set an email destination user so that the following conditions are satisfied: • The resource groups that correspond to the target storage systems are assigned. • Modify is set as the role in Device Manager for the assigned resource group.
2. If SMTP authentication is enabled, use the hdvmmodmailuser command to register an SMTP authentication user account in Device Manager. The SMTP authentication user settings are also used for event notification. If an SMTP authentication user has already been set for event notification, then these settings are not required here. In Windows: installation-folder-for-the-Device-Manager-server\Server\tools\hdvmmodmailuser.
Subject:[DVM] Alert Notification The following alert occurred. MessageID: ${messageID} Alert Type: ${alertType} Source: ${source} Status: ${status} Component: ${component} Description: ${description} Recommended Action: ${recommendedAction} Additional Info: ${additionalInfo} Occurrence Time: ${occurrenceTime} This message was sent automatically by the Device Manager server. The mail-alert-detection.txt file consists of a header (by default, Subject:[DVM] Alert Notification) and the body of the email.
• Each line of the template file is no more than 1024 bytes in length, excluding the line feed character. • In the top line, the header is specified in the following format: Subject:email-title Only one header is specified. • In the second line from the top, a blank line is specified. • In the third line from the top until the bottom line, the contents are specified. • Parameters are specified in the following format: ${parameter-name} The parameter name is case sensitive.
Setting up Device Manager to output SNMP traps To set up Device Manager to receive SNMP traps and output them to log files, the following settings must be specified: • Settings required for Device Manager to receive SNMP traps • Device Manager must be able to use port 162/udp of the management server. • 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.
Item Format Specify the content to be output by using the character strings (variables) below. You cannot use character strings other than the following: content-tobe-output Remarks Optional. If you omit this item, the $a$e$g$s content is output. If you specify Null for the severity, specification for this item is disabled.
Using event notification Tiered Storage Manager uses email to report to users the results of events that are not directly the result of user actions, such as the end of migration and shredding tasks. The following events can be reported by email: Table 44 Tiered Storage Manager events that can be reported via email Event Description Migration task ended This event occurs when a migration task ends successfully, ends due to a failure, or is canceled.
Setting properties for event notification By setting information such as SMTP server information and a notification-source email address for the following properties in the Device Manager server server.properties file, the execution results for events related to Tiered Storage Manager can be sent via email: • server.mail.from • server.mail.smtp.host • server.mail.smtp.port • server.mail.smtp.auth • server.mail.errorsTo • server.eventNotification.mail.
A template file is provided for each event. The following table lists the template files and the events they are used for. Table 45 Template files for event notification email Type Event Template file • For migration tasks created by using the Migrate data wizard#1 In Windows: installation-folder-for-theDevice-Manager-server\Server\config\mail-migrationtask-end.txt In Linux: installation-directory-for-theDevice-Manager-server/Server/config/mail-migrationtask-end.
Type Event Template file • In Windows: installation-folder-for-theTiered-Storage-Manager-server\ conf\mail-unlockingtask-end.txt Unlocking task ended#2 • In Linux: installation-directory-for-theTiered-Storage-Manager-server/ conf/mail-unlockingtask-end.txt • In Windows: Volume lock period expired#2 installation-folder-for-theTiered-Storage-Manager-server\ conf\mail-retention-term-expired.txt • In Linux: installation-directory-for-theTiered-Storage-Manager-server/ conf/mail-retention-term-expired.
The following shows how to create a template, using the template for the Migration task ended event (mail-migrationtask-end.txt) as an example. Set up template files using the following format: • Specify a header in the first line, nothing in the second line, and the email body in the third and following lines. • Specify a header in the format Subject: email-title. • Specify parameters in the format ${parameter-name}. • Use UTF-8 encoding to code the template file.
Parameter Description storageSystem Storage system name migrationSourceHost Migration source: Host migrationSourceLG Migration source: Logical Group migrationSourcePool Migration source: Pool migrationTargetTier Migration target: Tier migrationTargetPool Migration target: Pool options Options migratedVolumes Volume ID of the migrated volume Table 47 Parameters for events that occur when tasks end (tasks created via the Tiered Storage Manager CLI or the Tiered Storage Manager GUI in Legacy
Parameter Description Migration group name migrationGroupName Example: MG011 Name of the target storage tier in the previous migration previousTargetStorageTierName Example: MegaTech-HighCost Name of the target storage tier targetStorageTierName Example: MegaTech-HighCost Whether data after migration is to be deleted Values: eraseData • Yes • No Device numbers of both migrated volumes and volumes whose data has been erased migratedVolumes Example: 3:A6 Shredding method Values: shreddingMethod •
Parameter Description Name of the target migration group after task completion moveToMigrationGroupName Example: MG011 Name of the mapped external storage system mappedExternalSubsystemName Example: XP24000@10.208.115.
Parameter Description Device numbers of expired volumes expiredVolumes Example: 3:A6 Scheduled time when an "elapsed time" event will occur remindAt Example: 2007/03/25 17:00:00 Message that appears when an "elapsed time" event occurs reminderDescription Example: It is scheduled to move. Note: For details, see the HP StorageWorks P9000 Tiered Storage Manager Software CLI Reference Guide.
-u Device-Manager-user-ID Specify the ID of a user for which All Resources has been assigned as a resource group and Admin has been set as the role in Device Manager. -p Device-Manager-password Specify the password used to log in to Device Manager by the user Device-Manager-userID specified using the -u option. SMTP-authentication-user-ID Specify a user ID used for SMTP authentication. SMTP-authentication-password Specify a logon password for the user ID used to log on to the SMTP server.
CAUTION: If the following conditions apply, execute the htsmmodmailuser command from a shell such as tcsh or bash that supports commands that are longer than 256 bytes: • You are executing the htsmmodmailuser command from an instance of Tiered Storage Manager running in Linux • The command exceeds 256 bytes.
Setting up logs and alerts
7 Configuring Device Manager for CIM/WBEM This chapter explains how to configure Device Manager for CIM/WBEM . Device Manager and CIM/WBEM Device Manager supports WBEM, which is defined by the standards-setting organization DMTF. WBEM is a standard proposed by the DMTF for managing networked devices, including hosts and storage systems, over the Internet.
Figure 18 CIM components for Device Manager From a CIM client, you can specify a namespace by using the follow procedure: • Specify the SMI-S version. 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.
Legend: --: N/A You can acquire information about CIM at: http://www.dmtf.org/home/ You can acquire information about SMI-S at: http://www.snia.
Enabling CIM/WBEM functions When P9000 Command View AE Suite has been installed as a new installation, the CIM/WBEM functions are enabled. If you want to enable the CIM/WBEM functions again after having disabled them, you need to specify environment settings as described below. To enable the CIM/WBEM functions: 1. Change the setting in the Device Manager server property file. In the server.properties property file, change the server.cim.support property from false to true. The server.
4. Restart the P9000 Command View AE Suite product services. In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop. Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Start.
To open or close the port: 1. Using the server.cim.support.protocol property in the property file (server.properties) of the Device Manager server, specify whether to open or close each port according to the type of communication. The setting values for server.cim.support.protocol are shown in the table below. Table 51 Setting values for server.cim.support.protocol Port status Setting value 2.
2. Restart the P9000 Command View AE Suite product services. In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop. Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Start.
Setting up service discovery This section describes how to set up the service discovery function. Setting up service discovery (Windows) OpenSLP files are automatically copied over when P9000 Command View AE Suite is installed. You do not need to specify any settings after installation, and can use the service discovery function immediately after installation. If the following message is displayed when P9000 Command View AE Suite is removed, manually release the SLP service from the Windows services.
3. If /etc/init.d/slpd exists, delete it. # chkconfig --level 01345 slpd off # chkconfig --del slpd # rm -f /etc/init.d/slpd Setting up service discovery (SUSE Linux Enterprise Server) OpenSLP is provided with the standard configuration. No settings are required to use the service discovery function after installing SUSE Linux Enterprise Server. You can use the service discovery function as is. Starting and stopping the SLP service This section describes how to start and stop the SLP service.
installation-directory-for-the-Device-Manager-server/Server/wsi/bin/slpd.sh stop Starting and stopping the SLP service (SUSE Linux Enterprise Server) To manually start or stop the SLP daemon, you need to log in to the system as the superuser.
• • • • Number Number Number Number of of of of read I/Os read I/Os that hit the cache write I/Os write I/Os that hit the cache 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. Required system configuration for acquiring performance information This section describes the system configuration required to acquire performance information of a storage system.
We recommend that use the same computer for the management server and for the host that acquires performance information. In this case, the OS for the host that acquires performance information must be able to support both Device Manager server and the Device Manager agent. For example, if the OS for the management server is Windows XP, you cannot install the Device Manager agent, so you cannot use this computer as the host that acquires performance information.
To configure the settings: 1. Install the Device Manager agent. To acquire performance information, a RAID Manager/LIB is necessary. If you install the Device Manager agent on a host, the necessary RAID Manager/LIB is installed. However, if the host OS is UNIX, and a RAID Manager/LIB is already installed on the host, the RAID Manager/LIB is not overwritten. If this is the case, install the proper RAID Manager/LIB, as shown in the following table.
Defining the command device of the target storage system Edit the perf_cmddev.properties file to define the command device of the target storage system. The perf_cmddev.properties file is stored in the following location: In Windows: installation-folder-for-the-Device-Manager-agent\mod\hdvm\config\ perf_cmddev.properties In Linux: /opt/HDVM/HBaseAgent/mod/hdvm/config/perf_cmddev.properties Use the following format to define the command device in the perf_cmddev.properties file.
Setting item Value 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. #: • If this item is specified using the physical drive number in Windows or Linux and you then restart the OS, the physical drive number and device file name might be changed.
If you specify no parameter, multiple parameters, or upper-case parameters, the method for specifying the command is displayed. view This parameter displays the settings for the command devices defined in the perf_cmddev.properties file. The following table describes the command device settings displayed by the perf_findcmddev command. Table 54 Command device settings displayed by the perf_findcmddev command Item Description Displays the RAID ID.
The definition of the command device is valid. • If the host does not recognize a command device defined in the perf_cmddev.properties file: The error message KAIC28615-W and information of the command device that is not recognized by the host are displayed. • If a command device recognized by the host is not defined in the settings file: The error message KAIC28616-W and information of the command device that is not defined in the settings file are displayed.
Configuring Device Manager for CIM/WBEM
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.
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. Furthermore, the installation destination for the P9000 Command View AE Suite products must also be the same (including the drive letter and path).
2. Remove the P9000 Command View AE Suite product services and resource group from the targets of the cluster management. For details about the services and resource group that need to be removed from the cluster management, see the manual for each relevant P9000 Command View AE Suite product. CAUTION: Do not remove the following resources from the cluster management • Shared disk • Cluster management IP address • Logical host name 3.
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.
9. Execute the following command to back up the database after the new installation. 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 This option automatically changes the P9000 Command View AE Suite product services and the HiRDB service to the statuses required for backing up the database.
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-data /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.
14. Use the cluster management application to move the resource group in which the P9000 Command View AE Suite product services are registered to the standby node. If Microsoft Cluster Service is used: Right-click the resource group, and then select Move Group. If Microsoft Failover Cluster is used: Right-click the resource group, and then select Move this service or application to another node.
4. Open the server.properties file and make sure that the logical host name is specified in the server.http.host property. If the logical host name is not set, change the current value to the logical host name. installation-folder-of-the-Device-Manager-server\Server\config\ server.properties 5. Set the database on the shared disk as the database to be used. The procedure is described in steps 6 through 7.
8. Execute the following command to verify that the P9000 Command View AE Suite product services have stopped: installation-folder-of-Common-Component\bin\hcmdssrv /status 9.
To set up Microsoft Cluster Service: 170 Setting up a cluster environment
1. Add Device Manager and Tiered Storage Manager resources to the resource group. Select New, and then Resource. In each dialog box, specify the settings as shown in Table 57 to Table 62, and then select Finish. Table 57 Settings for registering HiRDB as a resource (for Microsoft Cluster Service) Dialog box name New Resource Setting Name: HiRDB/ClusterService _HD0 (optional) Resource type: Generic Service. Possible Owners Make sure that the executing and standby nodes have been added.
Dialog box name New Resource Setting Name: HCS Device Manager Web Service (optional) Resource type: Generic Service. Possible Owners Make sure that the executing and standby nodes have been added. Dependencies Register HBase Storage Mgmt Web Service. Generic Service Parameters Registry Replication Service name: DeviceManagerWebService Start parameters: Specify nothing. Specify nothing.
• Provide a cluster group (resource group), which is a group of services to be clustered (units of service failover). • Configure a resource group that includes the shared disks and client access points (cluster management IP addresses and network names) that can be inherited by the executing and standby nodes. • Make sure that Microsoft Failover Cluster can successfully control resource allocation, resource removal, and operation monitoring.
2. Click the resource name, and then choose Properties. Specify the settings shown in Table 63 through Table 68. Table 63 HiRDB/ClusterService _HD0 property settings (for Microsoft Failover Cluster) Tab name Setting General Startup parameters: Specify nothing (if a value is specified, delete it). Dependencies Register the shared disk and client access point. Advanced Policies Possible Owners: Make sure that the executing and standby nodes have been added. Registry Replication Specify nothing.
Tab name Setting General Startup parameters: Specify nothing (if a value is specified, delete it). Dependencies Register the HBase Storage Mgmt Web Service. Advanced Policies Possible Owners: Make sure that the executing and standby nodes have been added. Registry Replication Specify nothing. Table 68 HP StorageWorks XP Tiered Storage Manager property settings (for Microsoft Failover Cluster) 3. Tab name Setting General Startup parameters: Specify nothing (if a value is specified, delete it).
2. 3. Use the cluster management application on the executing node to take the following services offline: • HP StorageWorks XP Tiered Storage Manager • DeviceManagerServer • HCS Device Manager Web Service (if you are performing an upgrade or overwrite installation from version 7.
2. Perform an upgrade or overwrite installation of P9000 Command View AE Suite. For details about the installation procedure, see the HP StorageWorks P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide. Back up or export the current database according to the installer's instructions.
3. If the P9000 Command View AE Suite product services are running, stop them as follows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop. 4. 5.
2. From the GUI, register licenses for the products you want to use. Access the IP address of the standby node. A license key must be entered for each product that is installed. 3. From the executing node, execute the following command to change the URL for starting the GUI to the logical host name. installation-folder-of-Common-Component\bin\hcmdschgurl /change http:/ /IP-address-or-host-name-of-the-executing-node:port-number http:// logical-host-name:port-number 4.
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 This option automatically changes the P9000 Command View AE Suite product services and the HiRDB service to the statuses required for backing up the database.
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-data /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.
5. 6. If the services listed below are not being used by another application, delete the services using the cluster management application. • HP StorageWorks XP Tiered Storage Manager • DeviceManagerServer • HCS Device Manager Web Service • HBase Storage Mgmt Web Service • HBase Storage Mgmt Common Service • HiRDB/ClusterService _HD0 Use the cluster management application to suppress failover of the resource group.
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 The following table describes the resident processes in Windows. Table 69 Resident processes in Windows Process name Service name Function htsmService.
Process name Function The Device Manager server devmgrsrv installation-directory-for-the-Device-Manager-server/ Server/devmgrsrv P9000 Command View AE Suite servlet service hcmdssso cjstartweb installation-directoryfor-Common-Component/httpsd/sbin/httpsd /bin/sh installation-directory-for-Common-Component/ CC/web/containers/HiCommand/hcmdssso installation-directory-for-Common-Component/CC/web/ bin/cjstartweb P9000 Command View AE Suite common web service Multiple instances of this process might be run
installation-folder-for-Common-Component\bin\hcmdssrv /start In Linux: Log in as a root user, and then execute the following command: installation-directory-for-Common-Component/bin/hcmdssrv -start CAUTION: • Services of other P9000 Command View AE Suite products whose versions are 5.7 or later are started at the same time. For details about how to start services of P9000 Command View AE Suite products whose versions are earlier than 5.7, see the manual for your product version.
Checking the operating status of services This section describes how to check the status of P9000 Command View AE Suite product services. In Windows: Log in as a user with Administrator permissions, and then check the operating status of the Device Manager server and Common Component in either of the following ways: By using Windows functions: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Status.
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 71 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.
To back up a database, a directory for storing backup files is required. This directory requires space equal to the formula below. In addition to the estimate below, space is required for the temporary files created during backup.
Backing up a database in a cluster configuration To back up a databases when management servers are clustered, perform the procedure below. CAUTION: • Use the executing node (a machine that has online set for mode in the cluster.conf file) to make backups of databases. • In the cluster management application, specify the name registered when you specified the cluster resource settings for the resource name. To back up a database: 1. Log on to the management server as a user with Administrator permissions.
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.
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.
9. See the volume information of the tasks indicated in the message KATS50354-E and check whether those tasks are completed. Check for completion of not only migration tasks but also shredding tasks and locking tasks. 10. If a Tiered Storage Manager task is not completed, create and execute the task again as necessary. Restoring a database in a cluster configuration To restore a databases when management servers are clustered, perform the procedure below.
5. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below. 6.
8. In the cluster management application, bring online the resource group in which the P9000 Command View AE Suite product services are registered. 9. If you specified ALL or DeviceManager for the type option, refresh the storage system from the Device Manager GUI or CLI. 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.
the product is installed and overwritten to version 7.0 or later or when operation has started on the migration destination server, do not import the database of 6.x or earlier again. Notes on user information: • If there is user information on the migration destination server, this user information will be replaced with the user information from the migration source server. Therefore, do not perform a migration to a server on which user information for P9000 Command View AE Suite products already exists.
Exporting databases in a non-cluster configuration This section explains how to export the databases from the migration source server when the OS of the management server is not in a cluster configuration. To export databases from the migration-source server: 1. Log on to the management server as a user with Administrator permissions or root permissions. 2. Execute the hcmdsdbtrans command to export the databases.
2. Use the cluster management application to take the following services offline 3.
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.
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.
#: 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.
Importing databases (Microsoft Cluster Service or Microsoft Failover Cluster) 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. • In the cluster management application, specify the name registered when you specified the cluster resource settings for the resource name.
6. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below. 7.
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. If you want to use the archive file, the file option must be specified.
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.
11 Using and maintaining the Device Manager agent This chapter provides notes on managing host operations and explains Device Manager agent settings and operations. Before using the Device Manager agent This section provides notes on Device Manager agent operations and the settings required before using Device Manager agent.
2. Restart the host OS. 3. Execute the HiScan command. Reinstalling the Device Manager agent after a host OS upgrade 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.
To register the Java process as an SED exception: 1. Execute the following command to register the Java process to be used by the Device Manager agent as an SED exception: # sedmgr -c exempt installation-path-of-the-software-that-provides-a-Java-execution -environment-and-is-used-by-the-Device-Manager-agent/bin/java If this command execution succeeds, no execution results are output. 2.
If the following settings were not specified during a new installation of the Device Manager agent, execute the hdvmagt_setting command to specify the required settings.
• If the host that recognizes copy pairs is a virtual machine on VMware ESX 4.x or VMware ESXi 4.x: server.agent.rm.ignorePairStatus CAUTION: If you want to check the latest copy pair information by using the GUI or CLI, take either of the following actions depending on the copy pair management method. If local management is used: Refresh the storage systems. If central management is used: Refresh the pair management server.
Adjust this value as necessary, while running Replication Manager and checking for timeouts during processing. • server.agent.maxMemorySize property in the server.properties file Specify a value based on the number of pairs managed by a host (pair management server). By default, the heap runs in a 64-megabyte memory area. If the number of managed pairs exceeds 5,000, increase the memory heap size by 64 MB, and increase by another 64 MB for every 2,500 pairs above that.
6. From the Services window, select HBsA Service, and then start it. Property settings for hosts that manage 100 or more LUs If 100 or more LUs are managed by Device Manager and are recognized by a single host, the following problems might occur: • When the HiScan command is executed, the KAIC22009-E, KAIC22014-E, KAIC22019-E, or KAIC22048-E error message is output, and the host information cannot be registered in the Device Manager server.
In addition, to reduce the load of the Device Manager server, use the hdvmagt_setting command to set the execution period of the HiScan command so that multiple hosts do not execute the HiScan command at the same time. NOTE: • Depending on the environment, this issue might not be solved by setting the guide values. Make sure that you adjust the values to suit your environment. • In the following cases, set a value two to three times larger than the guide value.
Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) 88/20 750,000 or more 100/200 100/500 server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) server.agent. maxMemorySize (units: MB) 600 600,000 64 12,000,000 or more 600 600,000 128 30,000,000 or more 600 600,000 384 server.util. processTimeOut (units: milliseconds) server.agent.
Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) 250/500 15,000,000 or more 500/1,000 1,000/1,000 server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) server.agent. maxMemorySize (units: MB) 600 600,000 768 19,000,000 or more 600 600,000 768 38,000,000 or more 600 600,000 768 server.util. processTimeOut (units: milliseconds) server.agent.
Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) 100/256 3,600,000 or more 200/256 7,100,000 or more server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) server.agent. maxMemorySize (units: MB) 600 600,000 192 600 600,000 512 Device Manager agent operations This section explains Device Manager agent operations.
NOTE: Information about the host on which a Device Manager agent is installed is automatically reflected to the Device Manager server in the following cases: • When the HiScan command is automatically executed • When the host is started • When host information is updated from the Device Manager GUI Checking the version of the Device Manager agent Before you upgrade or restore the Device Manager agent, or when you want to find out which functions are supported in the Device Manager server, execute the hdvm_
• HORCM_CTQM# # 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_INSTP or 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_INSTP or HORCM_CTQM definitions to the configuration definition file, nor does it add a pair group to the existing definitions.
Item Version dev_name UNIX Only supports specification using a special file. Windows Supports description formats other than IPCMD and CMD format. UNIX Only supports specification using a special file. Windows Supports description formats other than IPCMD, CMD and GUID formats. UNIX Only supports specification using a special file. 05-00 01-00 to 01-10 Legend: Yes: Supports all description formats.
Item Version dev_group ip_address service 6.1 to 6.4 Yes Supports IP address and host name. Yes Earlier than 6.0 Yes Supports IP address and host name. Only supports port number specification. Legend: Yes: Supports all description formats. Table 86 Support status of HORCM_LDEVG parameter description format Item Version All parameters Earlier than 7.1 No Legend: No: Does not support any description formats.
The following tables show the contents and specified items in a configuration definition file for each parameter. For details about description rules for the content that can be specified, see “Detailed rules for configuration definition files” on page 225. Table 88 HORCM_MON parameter items and descriptions Item Description Specify the IP address (the Device Manager agent whose version is 5.9 or later supports the IPv6 protocol), host name, NONE, or NONE6.
Item Description 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. MU# Specify the mirror descriptor using a numeric value or h addition. You can omit this by leaving it blank.
Cluster virtual IP address Cluster virtual machine name NONE6 __NONE__ When the version of the Device Manager agent is 5.7 or earlier: Loopback IP address (from 127.0.0.1 to 127.255.255.254) Loopback host name (localhost) Cluster virtual IP address Cluster virtual machine name NONE NONE6 • For service, specify the port name using 1 to 15 single-byte characters. The environment must support the conversion of port names to port numbers.
254. When the version of the Device Manager agent is 5.5 or earlier, specify a value from 0 to 127. • The value that can be specified for MU# differs depending on the version and copy type of the Device Manager agent, as shown below. When the version of the Device Manager agent is 6.0 or later: Business Copy: 0 to 2 Snapshot 0 to 63 Continuous Access: Not specified Continuous Access Journal: 0#, h1, h2, or h3 #: When specified, multi-target configuration pairs cannot be created with Continuous Access.
Continuous Access: Not specified XP24000/XP20000: h1, h2, or h3 HORCM_INST parameter The following explains the description rules related to dev_group, ip_address, and service. • Specify dev_group using no more than 31 single-byte characters. A hyphen (-) cannot be specified at the beginning of the character string. • You cannot specify ip_address more than once for the same host for a single dev_group. • For ip_address, specify the information for the host managed by the Device Manager server.
Optimizing configuration definition files If true is specified for the server.agent.rm.optimization.userHorcmFile property of the server.properties file, when the Device Manager agent service starts, or when you operate copy pairs, the Device Manager agent optimizes the contents of the RAID Manager configuration definition file. In this case, note the following: Notes on backing up the configuration definition file In the optimization processing, the original configuration definition file horcmXX.
Device Manager agent commands This section explains the syntax of Device Manager agent commands. NOTE: • When using one of the following OSs on the host, execute Device Manager agent commands from the WOW64 command prompt: Windows Server 2003 (x64 and IPF) Windows Server 2003 R2 (x64) Windows Server 2008 (x64 and IPF) Windows Server 2008 R2 (x64 and IPF) The following shows an example of executing from the command prompt: C:\WINDOWS\SysWOW64\cmd.
hbsa_modinfo command The hbsa_modinfo checks the available agent functions (add-on modules). The hbsa_modinfo command is stored in the following locations: In Windows: installation-folder-for-Device-Manager-agent\bin\hbsa_modinfo.bat In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/bin/hbsa_modinfo In AIX: /usr/HDVM/HBaseAgent/bin/hbsa_modinfo The following table describes the hbsa_modinfo command syntax.
Centrally manages backup operations on a unit basis using the high-speed copy function of the storage system. hbsa_util command The hbsa_util command deletes the files and registry entries of the Device Manager agent when the host OS is Windows. The hbsa_util command is stored in the following locations: installation-folder-for-Device-Manager-agent\bin\hbsa_util.exe NOTE: The hbsa_util.
Item Details Starts or stops the service or daemon process of the Device Manager agent. Also, this command displays the status of the service or daemon process. Description This operation requires Administrator or superuser privileges. If the OS is Windows Server 2008 or Windows Server 2008 R2, the command must be executed from a command prompt started as an Administrator. start Starts the service or daemon process. stop [-f] Stops the service or daemon process. If any add-on module or version 5.
Item Details Description The hdvm_info command displays the version of the Device Manager agent in V.R1.R2MM format, where V is the version number, R1.R2 is the revision number, MM is the modified version.
Item Details You can select one of the following three automatic execution periods for the HiScan command: • Hourly Setting the execution period for the HiScan command • Daily • Weekly Note that any execution time can be specified. If you do not specify the execution time, for the hourly execution period, the HiScan command is executed at the 30th minute of every hour. For the daily or weekly period, the command is executed at 2:30 AM. In Windows, specifying an execution period registers exeHiScan.
Item Details Description This command allows you to send host information such as the host name, HBA WWN, file system, mount point, and information on the LU connected to the host to the Device Manager server. This operation requires Administrator or superuser privileges. If the OS is Windows Server 2008 or Windows Server 2008 R2, the command must be executed from a command prompt started as an Administrator. -s server-destination Specify the Device Manager server destination.
hldutil command The hldutil command is used to acquire information on storage system LDEVs, file systems, and other devices. It also allows you to output the acquired information to an execution log file and to view past execution log files. The hldutil command is stored in the following locations: In Windows: installation-folder-for-Device-Manager-agent\util\bin\hldutil.
Item Details -l ldev-number.serial-number If you want to view information about a specific LDEV, specify the LDEV number (LDEV#) and serial number (serial#) of the LDEV. The LDEV number and serial number must be specified in the indicated order. If you omit the LDEV number or serial number, the command does not output information about the LDEV. You cannot specify the -l option and the -d or -g option at the same time.
Item Details -hf [log-file-name] Specify this option to output the contents of a specific execution log file to the standard output. This processing involves no hardware access. If you omit the file name, the command waits for the entry of a file name. If the specified execution-result log file cannot be found, the command outputs an error message and then ends. You cannot specify the -hf option and the -k or -h option at the same time.
Sort key Descriptions iscsin iSCSI name for the iSCSI initiator ldev LDEV number lun LU number port Port number prod Product name rg Parity Group number rid Character string representing a storage system model ser Serial number of a storage system tid Target ID vend Vendor name wwnn Node WWN name wwnp Port WWN name 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.
Item Description RG# Parity Group number PortWWN#3 Port WWN NodeWWN#3 Node WWN iSCSIName iSCSI name for the iSCSI initiator #1: If the host is a virtual machine on VMware ESX 4.x or VMware ESXi 4.x and you execute the hldutil command after changing the configuration of the P-VOL or S-VOL, this information might not be displayed correctly. In this case, restart the virtualization server to display the information correctly.
The following table describes the javapath_setup command syntax. Table 104 javapath_setup command syntax Item Details Synopsis javapath_setup {-set [new|bundle|Java-execution-environment-installation-path]|-check} This command is used to switch the Java execution environment used on the Device Manager agent. Description This operation requires Administrator or superuser privileges.
The following table describes the TIC command syntax. Table 105 TIC command syntax Item Details In Windows: TIC.bat [-outdir location-of-resultDir-directory [-f] [-d [addonmodule-name, addon-module-name]]] Synopsis In UNIX: TIC.sh [-outdir location-of-resultDir-directory [-f]] Description This command lets you acquire Device Manager agent log files and system information for error analysis. This operation requires Administrator or superuser privileges.
Using and maintaining 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. For details on the machine requirements, see the Release Notes. Before you begin a Host Data Collector installation To facilitate the installation process, before starting the installation, determine the values to be specified in the installation wizard, such as the installation destination path and port number.
3. In the window that opens, click the Install button beside Host Data Collector. If the window does not open automatically, start the installer (setup.exe) directly. The installer is located in the following location: DVD-drive:\AGENTS\HHDC\Windows 4. Specify the necessary information on the installation wizard pages as directed by the wizard. After the installation successfully completes, the Installation Completed Successfully window appears.
2. In the dialog box that can be displayed by choosing Start, Settings, Control Panel, and then Add or Remove Programs, select Host Data Collector, and then click the Remove button. 3. Follow the instructions in the removal wizard. After Host Data Collector has been successfully removed, the Uninstall Complete window appears. Removing Host Data Collector (Solaris or Linux) To remove Host Data Collector in a Solaris or Linux environment: 1. Log on to the OS as the root user. 2.
Setting up 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. 2 250 Problem and cause PROBLEM: The GUI cannot be logged in to. CAUSE: The user account might have been locked.
No. Problem and cause Solution For a user without Admin (user management) permission: Ask a user with Admin (user management) permission to unlock the account. For a user with Admin (user management) permission: Ask another user with Admin (user management) permission to unlock the account. Alternatively, execute the hcmdsunlockaccount command to unlock your own account. To unlock the account by using the hcmdsunlockaccount command: 1.
No. Problem and cause Solution Also, if the user ID or password includes an ampersand (&), vertical bar (|), or caret (^), enclose each character with a double quotation mark ("), or use a caret (^) to escape the symbols. • In Linux: Use a backslash (\) to escape each character. Note that, if a password is not set for the target user, you cannot unlock the account by using the hcmdsunlockaccount command. 3 PROBLEM: The services of Common Component or the Device Manager server cannot be started.
No. Problem and cause PROBLEM: The Tiered Storage Manager server has not stopped. CAUSE: Possible causes are as follows: 2 • An error occurred in the Tiered Storage Manager server during processing to stop it. • The user who attempted the operation does not have administrator permissions.
No. Problem and cause 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. 5 6 9 Problem In a Windows environment, two copies of HBase Agent are displayed in the Add or Remove programs window of the computer on which the Device Manager agent or Hitachi Dynamic Link Manager is installed. In a Windows environment, HBaseAgent is displayed in the Add or Remove programs window even after you uninstall both the Device Manager agent and Hitachi Dynamic Link Manager.
No. Problem Solution 9 When executing the HiScan command in a Windows Server 2008 or Windows Server 2008 R2 environment, the KAIC22009-E, KAIC22014-E, KAIC22019-E, or KAIC22048-E error message is output, and host information cannot be registered on the Device Manager server. This occurs if there are 100 or more LUs managed by Device Manager recognized by a single host, and the Device Manager agent is upgraded from version 6.0.0-00 6.2.0-02 to version 6.4 or later via an overwrite installation.
Acquiring maintenance information on the management server If a management server failure occurs, acquire the maintenance information necessary for analyzing the cause of the failure, such as database files and log files. Maintenance information for the management server can be acquired by executing the command shown below. When you execute the command, maintenance information (log files and database files) is acquired, and four archive files (.jar, .hdb.jar, .db.jar, and .csv.jar) are created.
ager. For details on the other P9000 Command View AE Suite product names, see the documentation for each product. To specify multiple product names, separate them by a space. When specifying this option, also specify the log file type log for the logtypes option. If you omit the types option, maintenance information for all P9000 Command View AE Suite products installed on the management server is acquired. arc Specify the name of the archive files to be created.
Acquiring maintenance information on a server on which Host Data Collector is installed If hosts are managed by Host Data Collector and if Host Data Collector is installed on a different computer than the management server, you also need to acquire the maintenance information for the computer where Host Data Collector is installed.
Acquiring maintenance information on a host managed by Host Data Collector To acquire the maintenance information for a host where a failure occurred: 1. Copy the following file from the computer where Host Data Collector is installed to the host where the failure occurred: In Windows: installation-folder-for-Host-Data-Collector\bin\target\TLC.zip 2. In Solaris or Linux: installation-directory-for-Host-Data-Collector/bin/target/TLC.tar.gz Log in to the host where the failure occurred.
Acquiring the Java VM thread dump (Windows) This section describes how to acquire thread dumps of the HBase Storage Mgmt Common Service and the HCS Device Manager Web Service in a Windows environment. Acquiring a thread dump of the HBase Storage Mgmt Common Service (Windows) To acquire a Java VM thread dump: 1. In installation-folder-for-Common-Component\CC\web\containers\HiCommand, create a file called dump. 2. Access the Windows Services window. 3. Stop the HBase Storage Mgmt Common Service.
3. Start the P9000 Command View AE Suite product services. installation-directory-for-Common-Component/bin/hcmdssrv -start Acquiring a thread dump of the HCS Device Manager Web Service (Linux) To acquire a Java VM thread dump: 1. Execute the following command: # kill -3 PID PID is a process ID written in the installation-directory-for-Common-Component/ CC/web/containers/DeviceManagerWebService/logs/cjstdout.log file. The javacorexxx.xxxx.
The format of message-portion is as follows: uniform-identifier,unified-specification-revision-number, serial-number,message-ID,date-and-time,detected-entity,detected-location, audit-event-type,audit-event-result, audit-event-result-subject-identification-information, hardware-identification-information,location-information, location-identification-information,FQDN, redundancy-identification-information,agent-information, request-source-host,request-source-port-number,request-destination-host, request-dest
Item#1 Description request-source-host Host name of the request sender. request-source-port-number Port number of the request sender. request-destination-host Host name of the request destination. request-destination-portnumber Port number of the request destination. batch-operation-identifier#2 Serial number of operations through the program. log-data-type-information Fixed to BasicLog or DetailLog. application-identificationinformation Program identification information.
CELFSS,1.1,10,KAIC51000-I,2006-03-17T12:45:00.0+09:00,DvM_Srv, TestServer, ConfigurationAccess,Success,uid=system,,,,,,,from=12.228.23.124,,,,, BasicLog,DvM_GUI,,"123456789 ModPort" Message text in audit log data The format of message text in output audit log data varies from one audit event to another. This section describes the format of the message text for each audit event.
unique-ID error-message-ID Table 111 Information in message text when the Device Manager server receives a request or sends a response (for server processing) 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 ID is also output as audit log data on the SVP. message-details Detailed information on the request. For details, see “Message details for Device Manager server requests” on page 280.
Message text output when related products are started When the Device Manager server receives a request to launch a related product or sends a response for a 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.
The table below indicates the relationship between the presence of a launch session ID and the information contained in the launch target identifier for each type of the application to be launched.
Format of message text output when the Device Manager server sends a response (if an error occurred or if no error occurred): unique-ID return-code output-parameter Format of message text output when the Device Manager server sends a response (if a job is created through asynchronous processing): unique-ID return=4096 object-path CAUTION: If a job is created through asynchronous processing, no completion notification is output as audit log data.
"123456789 GetSupportedSizeRange inParams={ElementType=3,Goal=// 192.168.0.1/root/smis/current:HITACHI_StorageSetting.InstanceID='RAID5'} objectPath=/root/smis/current:HITACHI_StoragePool.InstanceID='AMS500.
Item operation-target (Res) Description Output format Type of resource for the operation: Res=(ResId,ResName) 1. Resource ID(ResId) 2. Resource name(ResName) For details about ResId and ResName, see Table 119. Table 116 Items output to the audit log message text (additional information) Item Description Output format failure-cause (RC) Error code indicating the cause of a failure event RC=KATSppmmm-Z When a single item exists: storage-domain-information (SD) 1. Storage domain ID (id) 2.
Item Description Output format When a single item exists: storage-tier-information (ST) 1. Storage tier ID (id) 2. Storage tier name (name) When multiple items exist: 1. Number of elements (n) 2. Storage tier ID (id) 3. Storage tier name (name) ST=(id,name) NumST=n, Start STs ST[1]=(id-1,name-1) ...
Item Description Output format When multiple items exist: 1. Number of elements (n) 2. Controller logical device number of the migration source volume (sdevnum) NumVP=n, Start VPs 3. Object ID of the migration source LDEV (sid) ... 4. Controller logical device number of the migration target volume (tdevnum) (sdevnum-n,sid-n,tdevnum-n,tid-n) 5.
Item Description Output format For a locking task: 1. Task ID (id) 2. Task type (type) = 2 3. Lock status (mode) TK=(id,2,mode,days) ReadOnly: Read only Protect: Protected 4. Lock period (days) For an unlocking task: 1. Task ID (id) 2. Task type (type) = 3 TK=(id,3) For a shredding task: 1. Task ID (id) 2. Task type (type) = 4 3. Shredding method (method) TK=(id,4,method) 0: Zero once 1: DOD For multiple types of task information: 1. Number of tasks NumTK=n, Start TKs 2.
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 119 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. Table 121 Commands output in message details Output character string Full name Operation Add Add Addition Del Delete Deletion Get Get Acquisition Mod Modify Modification Set Set Setting Targets in message details The table below provides information on the targets that can be output in message details.
Output character string Full name Operation HSD HostStorageDomain Host group configuration change JrnlPool JournalPool Pool configuration change JrnlPoolTier JournalPoolTier Smart pool tier information acquisition LDEVForVolMig LDEVForVolumeMigration LDEV VolumeMigration attribute setting or information acquisition LGrp LogicalGroup Logical group setting or reference LU LogicalUnit Logical unit configuration change LUFormat LogicalUnitFormat Formats of all LDEVs in the logical unit L
Output character string Full name Operation VVol VirtualVolume Virtual volume setting WWN WorldWideName WWN deletion WWNForHSD WWNForHostStorageDomain Change in the configuration of WWNs belonging to a host group WWNForLUN WWNForLUN LUN WWN configuration change ZPRVol ZeroPageReclaimVolume Information acquisition about the progress of a zero page reclaim task NOTE: Character strings that are not in the table might be output.
Output character string Operation 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 virtual volumes to be created (indicated by n). overwrite Deletes the current label and then sets a new label. • If the target is LogicalUnit Creates and quick-formats a logical unit. quickformat • If the target is LogicalUnitFormat Quick-formats a logical unit.
The following table describes the parameter information output in message details: Table 124 Parameter information output in message details Item Description element A character string that indicates the element name. For information on the elements that are output and their meanings, see Table 125. However, Table 125 might not contain some displayed characters. Format: info='...' Attribute values specified for the element are output.
Output character string Full name and content Sequence in which attribute values are output#1 ArrayValue Value specified in ArrayValue (Element for specifying a value if the type of the parameter specified in Param is array) ArrV value ChangedItem ChangedItem (Information about the data changed in Device Manager) ChangeInfo ChangeI CIMIvk (Version information of the storage system configuration) -- LDEV information version, port information version, LU information version, LUSE information ver
Output character string Full name and content Sequence in which attribute values are output#1 type, childID, volumeKind, host, source, hostType, clprNumber, assocID, poolFunction, THPPoolID, accessibleWWN, substance, targetArray, masterArrayType, masterSerialNumber ConfigurationChange ConfChange (Reports information about the configuration changes of the storage system to the Device Manager server) user ID, notification type, serial number, product name#2, occurrence date and time, IP address user, t
Output character string Full name and content Sequence in which attribute values are output#1 #3 , externalWWN, externalLun, portID, pathGroupID ExtS F ExternalStorage -- File Log file name (Information about the log file name) name Filter (Limits the results of the Get command) Filt -- FreeLUN FreeLUN (Information about availability of the LUN in the host group) FreeSpace FreeSpace (Information about the
Output character string Full name and content HostVolume HostVol (Volume information acquired from the Device Manager agent) Sequence in which attribute values are output#1 device file name, vendor name, model name#2, serial number, port number, device number#4, identification number, host name, , IP address, host IP address for IPv6, mount point, SCSI bus number, SCSI bus connection identification number, LU number, WWN of HBA node, WWN of HBA port, WWN of storage system port, file system type, file sy
Output character string Full name and content JournalPool JrnlPool (Journal group information) Sequence in which attribute values are output#1 , journal pool identifier, pool ID, THP pool usage threshold 1, THP pool usage threshold 2, THP pool usage threshold 2 mode, journal volume inflow limit, data overflow monitoring interval (seconds), unit of path monitoring interval, path monitoring interval, transfer of path monitoring interval, use
Output character string LicenseKey Full name and content Sequence in which attribute values are output#1 LicenseKey (Key code required to make the program available) LogicalUnit LU (Information that represents the LU) , 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 devi
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 Sequence in which attribute values are output#1 , name, portID, domainID, domainNickname, scsiID, lun, devNum#4, targetPortID, targetDomainID, targetDomainNickname, targetDevNum PDEV PDEV (Information about PDEV) Port Port (Information about the port) , drive type, drive size, form factor , diskType, diskModelSize, formFactor
Output character string Full name and content Sequence in which attribute values are output#1 , masterArrayType, masterSerialNumber,masterControllerID, remoteArrayFamily, remoteSerialNumber, remoteSSID, remoteControllerID, pairType, remotePathGroupID, bandwidth ReplicationGroup RepGrp (Information about the HORCM instance group) , name of copy group u
Output character string Full name and content Sequence in which attribute values are output#1 ResultObject RsltObj SA SIMI (A single row in a list displayed by the ListView elements) StorageArray (Storage system information) SIMInfo SIM ID of SIM information (SIM information of the storage system) SIMID SizeCondition SizeCond (Conditions for specifying the number within SearchCondition) SelectCondition SlctCond (Element for which the Sele
Output character string Full name and content Subscriber Subscrbr (Report plan topic) Sequence in which attribute values are output#1 -- Timestamp Timestamp Topic (Time when the message was created in the Device Manager server) Topic report information (Name of the message topic) name URLLink URLLink (Links between a P9000 Command View AE Suite object and an application) User (Account information of a single user of Device Manager) User -- , URL required to l
Output character string VolShred WritingPattern Full name and content Sequence in which attribute values are output#1 VolumeShredding shredding owner ID (Information about the shredding function) ownerID WritingPattern writing pattern used when shredding is specified (Writing pattern information for a single writing) pattern WritingPatterns WritingPatterns (All writing pattern information of a single VolumeShredding) WorldWideName WWN -- WorldWideName, nickname, operation target host group
Common output name Applicable storage system model R600 XP24000/XP20000 R700 P9500 Table 127 Common output names for replication operation type attributes Common output name Applicable product Local Copy Business Copy Remote Copy (Async) Continuous Access Asynchronous Remote Copy (Jrnl) Continuous Access Journal Remote Copy (Sync) Continuous Access Synchronous SnapShot Snapshot Correlation between user operations and Tiered Storage Manager audit log data This section describes what audit l
2. To determine the GUI operation used, compare the details of the audit log data with the contents of Table 128 and look for a matching pattern. Among the output audit log data, there will be evidence of many calls to Get-type operations. These are frequently called to refresh the screen and cannot be attributed completely to user actions. However, information that corresponds to operations such as creating, updating, and deleting various resources in Tiered Storage Manager also exists in the audit log.
GUI operation Key OpName# ResName# Additional information# Note Deleting a migration group M Delete MG MG -- Displaying a migration group list M Get MG SD, NumMG -- Displaying migration group detailed information M Get MG SD, MG -- MG, VL Information about the added volumes is output. Adding volumes to a migration group M Add VL M Remove VL MG, VL Information about the deleted volumes is output.
# For details, see Table 115 through Table 119. CLI operations and the corresponding audit log data To estimate the user-performed CLI commands 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). Audit log data created by executing CLI commands is output by Tiered Storage Manager and has the TSM_CLI application identifier information.
2. To determine the CLI command used, compare the details of the output audit log data with the contents of Table 129 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 Key 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 Key #1 #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 Key OpName ResName Additional information#2 M Modify ST SD, ST -- -- Get TK TK -- M Modify TK TK -- #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 When storage domain names have been specified M Change TK TK opt = 0x02040000 or 0x02050000 Legend: M: Main key --: Not applicab
Troubleshooting
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.
• By using Plug-in for Virtualization Server Provisioning, allocating volumes to a virtualization server is now possible from VMware vSphere Client. • Monitoring and migration of Smart pools can now be performed on a user-defined schedule. • A migration-target tier can now be selected for each Smart pool volume. • The monitoring interval for copy pairs (the poll value of the HORCM_MON parameter in the configuration definition file) can now be specified.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • Continuous Access Synchronous Continuous Access Synchronous • Continuous Access XP Synchronous • P9000 Continuous Access Synchronous • XP Continuous Access Synchronous Software This abbreviation is used when it is not necessary to distinguish the following products: LUN Manager • LUN Management • XP LUN Manager This abbreviation is used when it is not necessary to distingui
Support and other resources
A Device Manager server properties This section describes the property files of a Device Manager server. Overview of Device Manager server properties The following table describes the contents of property files of a Device Manager server. Table 131 Property files of a Device Manager server Property file Description This property file contains the Device Manager server configuration information. server.
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 default values are set during a new installation.
x.x.x.x (x: integer from 0 to 255) IPv6 format: Specify hexadecimal numbers by using colons (:). You can also use a short format. You can only use global IPv6 addresses. A value specified for the host name or IP address must be accessible from clients (GUI, CLI, and storage systems). CAUTION: • If multiple NICs are installed on the server computer on which Device Manager is installed, specify the IP address of the NIC that belongs to the network to which the clients (GUI, CLI, and storage systems) connect.
CAUTION: If you change the value of this property, you must also change the values of the Device Manager GUI client.rmi.port property and the Tiered Storage Manager hdvm.rmi.port property to the same value. Default: 23055 server.http.entity.maxLength This property sets the maximum length of an HTTP request entity in bytes. Under normal conditions, you do not need to change the default value of this property.
CAUTION: If this property is set to true, synchronization of the information will take several minutes. If you change the property and then log in to Device Manager right away, an error might occur. In such a case, wait until the synchronization has finished, and then log in. Default: false server.cim.agent This property allows you to specify the name of the host on which the Device Manager agent is installed when the function for acquiring storage system performance information is used.
Default: 5988 server.cim.https.port This property specifies the port for SSL transmission, for the CIM function. Default: 5989 server.configchange.enabled This property specifies whether to automatically update (refresh) storage system information in the database when the storage system configuration is changed by a storage management tool (Element Manager) launched from the GUI. If you specify true for this property, the database is automatically refreshed immediately after the configuration change.
server.mail.smtp.host This property specifies the host name or IP address of the SMTP server. To send alerts and events to users by email, you must specify this property. The IP address can be specified in either IPv4 or IPv6 format. CAUTION: If you do not specify this property, the email notification function will not be enabled even if you specify true for the server.mail.enabled property. Default: None server.mail.smtp.port This property specifies the port number of the SMTP server.
server.mail.alert.type This property specifies the type of alerts that are sent to users by email. The following values can be specified: • Trap: Reports only the alerts detected by SNMP traps. • Server: Reports only the alerts detected by the regular monitoring that Device Manager conducts. • All: Reports the alerts detected by both SNMP traps and the regular monitoring that Device Manager conducts.
Default: true server.agent.differentialrefresh.periodical.enabled This property specifies 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 This property specifies 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.
The n in the file name indicates the backup generation number of the file. When a log file reaches its maximum length, its filename is modified by appending a counter, as in access.log.1, for example. As more backup log files are created, their counters or version suffixes are incremented (for example, access.log.1 becomes access.log.2), until the specified number of backups have been created. After that, the oldest backup log file is deleted each time a new backup is created.
incremented (for example, HDvMtrace2.log becomes HDvMtrace3.log), until the specified number of backups have been created. After that, the oldest backup log file is deleted each time a new backup is created. Default: 10 logger.hbase.MaxFileSize In this property, you can 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.
server.dispatcher.daemon.pollingPeriod This property defines the polling interval (in minutes) for the background threads responsible for checking component status and the configuration version. A value of 0 will disable these polling threads. Default: 5 (minutes) server.dispatcher.traps.purgePeriod This property defines 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.
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.
H: Specify this format to automatically refresh the information at regular intervals. Specify the interval in the server.dispatcher.daemon.autoSynchro.interval property. D: Specify this format to automatically refresh the information once a day at a specific time. Specify the time in the server.dispatcher.daemon.autoSynchro.startTime property. W: Specify this format to automatically refresh the information once a week at a specific time on a specific day. Specify the day in the server.dispatcher.daemon.
If true is specified for this property, the storage system performance information is automatically refreshed at the time specified in the server.dispatcher.daemon.autoSynchro.performance.startTime property over the interval specified in the hppa.infoAcquirePeriod property. If false is specified for this property, the storage system performance information is not automatically refreshed.
installation-folder-for-the-Device-Manager-server\Server\config\ mime.properties • In Linux: installation-directory-for-the-Device-Manager-server/Server/config/ mime.properties This property file contains the translation/lookup table for all Multipurpose Internet Mail Extensions (MIME) file types recognized by the Device Manager web server. Each property in this lookup table maps a particular extension suffix to the MIME type for that file.
NOTE: When the client is accessing the server through a proxy server and the connection timeout of the proxy is shorter than the timeout of this property, the notification message might be lost because a timeout of the proxy server cuts the connection before the Device Manager server can send the response to the GUI. If this is the case, set the timeout for this property to a time shorter than the timeout of the proxy. Default: 300 (seconds) client.outputhorcmfunction.
Default: true client.rmi.port This property specifies the port number for the Device Manager RMI server. You must specify the same value as the one specified for the server.rmi.port property of the Device Manager server. Default: 23055 client.migration.use.legacymode This property specifies whether migrations that use migration groups created in version 7.1.0 or earlier can be executed from the Tiered Storage Manager GUI. To execute a migration that uses a migration group, specify true.
client.launch.HPPA.report.host This property specifies the host name or IP address included in the PA URL when launching the PA GUI. Default: None client.launch.HPPA.report.port This property specifies the port number included in the PA URL when launching the PA GUI. Default: None Device Manager security properties 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.
CAUTION: If you do not specify this property, the SNMP trap data will not be output to the log even if you specify true for the customizedsnmptrap.customizedSNMPTrapEnable property. Default: None Properties for connecting to P9000 mainframe agent (host.properties file) The host.properties file contains the properties for connecting to P9000 mainframe agent. • In Windows: installation-folder-for-the-Device-Manager-server\Server\config\ host.
IPv4-address-or-host-name:[port-number],IPv4-address-or-host-name:[port-number],... You can omit port numbers. If you omit port numbers, 23051 is assumed to be specified. If there are multiple computer where Host Data Collector is installed, you must specify the Host Data Collector information for computer. Default: If the management server OS is a prerequisite OS for Host Data Collector: 127.0.0.
When false is set: The Shredding check box is not selected. To prevent data leaks, we recommend that you delete the data on migration source volumes after migration. Default: false CAUTION: If you modify this property value, you must restart the services of P9000 Command View AE Suite products to enable the changes. migration.plan.candidateVolumeCountLimit This setting specifies 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-folder-for-the-Device-Manager-server/Server/config/ hppa.properties hppa.infoAcquirePeriod This setting specifies the period for which performance information, such as the parity group usage rate and IOPS, is collected and summarized.
B Tiered Storage Manager server properties This section describes the property files of the Tiered Storage Manager server. Overview of Tiered Storage Manager server properties The following table lists the Tiered Storage Manager server properties. These property files apply only to operations (processes) from the Tiered Storage Manager CLI or from the Tiered Storage Manager GUI in Legacy mode. Table 132 Tiered Storage Manager server properties Property file Description server.
If incorrect properties are specified, the loading of the properties will fail and the Tiered Storage Manager server will not start. Properties that are incorrect are output to the command log or message log. In a cluster configuration, use the same property files on both the executing and standby nodes unless there is a special reason not to. CAUTION: Before updating a property file, stop the P9000 Command View AE Suite product services. Tiered Storage Manager server operations properties (server.
server.rmi.security.port For configurations using SSL communication, this setting specifies the RMI port number used by Tiered Storage Manager to accept processing requests. The range of specifiable values is from 1 to 65535. Default: 24500 server.base.initialsynchro This setting specifies whether the Tiered Storage Manager configuration information contained in the navigation tree is synchronized with the Common Component database when the Tiered Storage Manager server starts.
server.mail.smtp.port This setting specifies the SMTP server port number to use when sending an event notification email. The range of specifiable values is from 1 to 65535. Default: 25 server.mail.smtp.auth This setting specifies whether to enable SMTP authentication when sending an event notification email. Specify a Boolean value for this property. Specifying true enables SMTP authentication. Specifying false disables SMTP authentication.
CAUTION: If you specify false, filter conditions will not be checked so make sure that you enter correct filter conditions. Normally, leave this property as the default value of true so that filter conditions are checked. server.migration.dataErase.defaultValue This setting specifies the status of the Erase remaining data on source volumes. check box when the Migration wizard is started, and the action to be taken when the erasedata parameter of the CreateMigrationTask command is omitted.
Default: 4 CAUTION: • If you specify a volume with a larger capacity than the migration source volume for the migration target volume, the migration target volume is deleted prior to migration, and then created again with the same capacity as the migration source volume. Therefore, the migration task will require more time than when migrating to a volume of the same capacity.
Tiered Storage Manager GUI properties (client.properties file) The client.properties file contains the GUI properties. • In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\conf\client.properties • In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/conf/client.properties client.ldev.rowsperpage.retain.enabled This property specifies whether to keep the setting when the number of lines displayed per page for a sortable table is changed.
Tiered Storage Manager database properties (database.properties file) The database.properties file contains properties related to databases. • In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\conf\database.properties • In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/conf/ database.properties dbm.traceSQL This setting specifies whether SQL should be output to a trace log. Specify a Boolean value for this property. Specifying true outputs SQL.
hdvm.timeout This setting specifies the timeout period (in milliseconds) for communications with the Device Manager server you are accessing. Specifying 0 disables the timeout function. The range of specifiable values is from 0 to 2,147,483,647. Default: 0 hdvm.rmi.port This setting specifies the port number for the Device Manager RMI server. You must specify the same value as the one specified for the server.rmi.port property of the Device Manager server.
Specify a value from 0 to 30. We recommend that the default value be used. Note that the same messages are output whether you specify 20 or 30, because there are no messages whose output level is 30. Default: 20 The output levels are based on the contents of the logged messages. The following table shows the output levels of message log data.
Type of message Output level Message descriptions Warning 20 An error occurred, but execution can continue with limitations. 0 Information has been produced about the actions of the management server and management client. 10 Information has been produced about exchanges with other programs or machines. 20 Information has been produced about the starting/stopping of a major method, or the creation/deletion of a major object. 30 Detailed information has been produced.
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. The log files are produced in accordance with the size specified by the logger.serverTraceMaxFileSize property, and are assigned names with a log number appended (for example, HTSMServerTrace1.log and HTSMServerTrace2.log). The log files are used and written to in the order of the log numbers.
CAUTION: If you have changed the property value, restart the services of P9000 Command View AE Suite products to enable the new value. 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.
CAUTION: If you have changed the property value, restart the services of P9000 Command View AE Suite products to enable the new value.
C Host Data Collector properties This section describes the Host Data Collector property file. Overview of Host Data Collector properties The following table describes the Host Data Collector properties. Table 135 Host Data Collector properties Property file Description alps.properties file This property file is related to the Host Data Collector configuration information. about.properties file This property file is related to the Host Data Collector product information. log4jconfig.
installation-directory-for-Host-Data-Collector/conf version The version number of Host Data Collector set by the Device Manager installer. Under normal conditions, you do not need to change the default value of this property. Default: Value set by the installer Host Data Collector logger properties (log4jconfig.properties file) The log4jconfig.properties file contains properties related to Host Data Collector log output.
D Device Manager agent properties This section describes the property files of a Device Manager agent. Overview of Device Manager agent properties The following table describes the Device Manager agent properties. Table 136 Device Manager agent properties Property file Description agent.properties file This property file is related to the connection between the Device Manager agent and the Replication Manager server. hldutil.
NOTE: The Device Manager agent uniquely creates and manages the configuration definition files and instances for monitoring to monitor the statuses of copy pairs in Replication Manager. The HORCM instance for monitoring is the instance of RAID Manager used by the Device Manager agent. The HORCM file for monitoring is the RAID Manager configuration definition file of that instance. agent.rm.
Do not set a value from 53,232 to 53,330 because Device Manager agent uses these values. Default: 54323 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.
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.
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. You can use the following formula to determine the log file output size: amount-of-information-output-to-log-file (MB/week) = 0.8 x number-of-copy-pairs + 25 Set the values of logger.MaxBackupIndex and logger.
Note that if the host OS is Windows and you have changed the port, you must use the firewall_setup command to specify the firewall exception settings again. Default: 24041 server.http.localPort Specify the port number for communication between the Device Manager agent's daemon process and the Web server process. Avoid specifying small port numbers because such numbers might conflict with other applications. The normal range is 1024 to 49151.
server.http.socket.bindAddress In situations in which the Device Manager agent runs on a platform on which two or more network interface cards (NICs) are installed, this property allows you to specify the NIC through which the Device Manager agent can accept requests. If you want to restrict the interface to be accepted, specify the IP address to be accepted with the Device Manager agent. For operation in an IPv6 environment, specify a global address.
CAUTION: • If the host OS is Windows or Linux and this property is omitted, the Java execution environment bundled with the Device Manager agent is used. • If Hitachi Dynamic Link Manager is installed on the host, use a 32-bit Java execution environment. server.http.entity.maxLength Specify the maximum size of HTTP request entities permitted by the Web server function of the Device Manager agent (in bytes). Normally, the default value of this property need not be changed.
For IPv6, specify the IP address using hexadecimal numbers with colons. Abbreviation can be used. The following example shows how to specify an IPv6 address: server.server.serverIPAddress=2001::214:85ff:fe02:e53b When specifying a host name: Use a character string of 50 bytes or fewer to specify the host name. The following characters can be used: a-z A-Z 0-9 - . @ _ Default: 255.255.255.255 server.server.
for the target copy pair command device (if a command device is set for the HORCM_CMD parameter in IPCMD format), LDEV numbers will be output in decimal format regardless of the value specified for this parameter. Default value: CULDEV server.agent.rm.exclusion.instance On the host where the Device Manager agent is installed, to exclude volume pairs already managed by RAID Manager from Device Manager operations, specify the applicable RAID Manager instance numbers.
server.agent.rm.horcm.poll Specify the value defined for poll of the HORCM_MON parameter in the configuration definition file (the monitoring interval for copy pairs) in hundredths of a second. If monitoring is not being performed, specify -1.
Default: HORCM_LDEV Table 137 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. Creating a pair for a new copy group.
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). When a command takes longer to execute than the specified value, the Device Manager agent concludes that an error occurred during command execution. This property should be changed only by a system administrator who has expert knowledge, when performance of the Device Manager agent's pair configuration functionality needs to be fine-tuned.
When P-VOLs and S-VOLs are assigned to the management server, this property must be specified.
Device Manager agent properties
E Commands Executed by Host Data Collector This appendix describes the commands executed by Host Data Collector.
Commands Executed by Host Data Collector
Acronyms and Abbreviations This manual uses the following abbreviations.
DCR Dynamic Cache Residency DER Distinguished Encoding Rules DHCP Dynamic Host Configuration Protocol DKC DisK Controller DMP Dynamic MultiPathing DMTF Distributed Management Task Force DN Distinguished Name DNS Domain Name System DoS Denial of Services DVD-ROM Digital Versatile Disk Read-Only Memory FC Fibre Channel FC-SP Fibre Channel - Security Protocol FQDN Fully Qualified Domain Name FTP File Transfer Protocol GUI Graphical User Interface HBA Host Bus Adapter HTML Hyper
J2SE Java 2 Standard Edition JAR Java ARchiver JCE Java Cryptography Extension LAN local-area network LBA Logical Block Addressing LDAP Lightweight Directory Access Protocol LDEV logical device LDKC Logical DisK Controller LU Logical Unit LUN Logical unit number LUSE Logical Unit Size Expansion MCU Main Control Unit MIME Multipurpose Internet Mail Extensions MOF Managed Object Format MU Multiple Unit NAS Network Attached Storage NIC Network Interface Card NPIV N Port ID Vi
RCU Remote Control Unit RDN Relative Distinguished Name RFC Request For Comments RMI Remote Method Invocation S-VOL Secondary VOLume SAN Storage Area Network SCSI Small Computer System Interface SED Stack Execution Disable SIM Service Information Message SLP Service Location Protocol SLPR Storage Logical PaRtition SMI-S Storage Management Initiative - Specification SMTP Simple Mail Transfer Protocol SNIA Storage Networking Industry Association SNIA-CTP SNIA Conformance Testing P
WMI Windows Management Instrumentation WWN Worldwide name XML eXtensible Markup Language Administrator Guide (Web Version) 373
Acronyms and Abbreviations
Index Symbols */tcp, 77 */udp, 79 1099/tcp, 74, 75 162/udp, 66, 73 1812/udp, 79 2001/tcp, 67, 73, 74, 76 20352/tcp, 67 22/tcp, 68, 77 23015/tcp, 65, 73 changing, 70 23016/tcp, 65, 73 changing, 70 23017/tcp, 65 changing, 71 23018/tcp, 66 changing, 71 23025/tcp, 66 changing, 71 23026/tcp, 66 changing, 72 23032/tcp, 66 changing, 72 23050/tcp, 68 23051/tcp, 68, 77 23052/tcp, 68 23055/tcp, 67 24041/tcp, 68, 76 24042/tcp, 68, 76 24043/tcp, 68 24220/tcp, 67 2443/tcp, 67, 73 25/tcp, 78 359/tcp, 79 427/tcp, 66, 78 4
audit log data checking, 264 Common Component, 267 correlation (Tiered Storage Manager CLI command), 301 correlation (Tiered Storage Manager GUI operation), 298 Device Manager server, 267 Device Manager server (using CIM), 270 environment settings file, 120 generating, 108 message details (Device Manager server requests), 280 message text, 267 related products, 269 syslog file, 108 Tiered Storage Manager, 272 auditlog.conf, 121 auditlog.
configuration definition file, 220 creating, 228 parameters and requirements, 220 prerequisites for using, 220 required operations when creating or changing, 229 configuring networks, 26 performance information acquisition, 152 service discovery, 149 copy pairs central management method, 47 configuration definition file, 220 deleting, 229 Device Manager agent requirements, 58 local management method, 47 managing, 212 notes on using Device Manager when copy pairs are already managed by RAID Manager, 62 stora
F firewall registering exceptions for P9000 Command View AE Suite in Linux environments, 79 setting for Device Manager agent, 210 settings, 72 firewall_setup command, 230 G generating audit log data, 108 GUI, 25 controlling, 97 H hbsa_modinfo command, 231 hbsa_util command, 232 hbsasrv command, 232 hcmdschgurl command, 87 hcmdsunlockaccount command, 251 hdvm.port, 342 hdvm.protocol, 342 hdvm.rmi.port, 343 hdvm.
logger.loglevel, 320, 355 logger.MaxBackupIndex, 320, 355 logger.MaxFileSize, 321, 355 logger.messagelogLevel, 343 logger.properties, 320 logger.properties file, 343, 354 logger.serverMessageFileCount, 345 logger.serverMessageMaxFileSize, 347 logger.serverTraceFileCount, 346 logger.serverTraceMaxFileSize, 347 logger.syslogLevel, 345 logger.
performance information configuring, 152 PA, 101 preparing, 154 system configuration, 153 ports changing, 69 registering exception, 72 settings, 65 used by Common Component, 65 used by Device Manager agent, 68 used by Device Manager server, 66 used by Host Data Collector, 68 used by storage systems, 68 used by Tiered Storage Manager server, 67 used CIM/WBEM, 147 preparing acquiring performance information, 154 prerequisites for using configuration definition file, 220 mainframe hosts, 45 normal hosts, 35 vi
server.agent.rm.location, 361 server.agent.rm.moduleTimeOut, 364 server.agent.rm.optimization.userHorcmFile, 361 server.agent.rm.pairDefinitionForm, 362 server.agent.shutDownTime, 358 server.base.home, 314 server.base.initialsynchro, 314, 337 server.checkOutVolumeRange, 338 server.cim.agent, 315 server.cim.http.port, 315 server.cim.https.port, 316 server.cim.support, 315 server.cim.support.job, 315 server.cim.support.protocol, 315 server.configchange.enabled, 316 server.dispatcher.daemon.autoSynchro.
settings IPv6, 81 number of trace log files of Common Component, 105 port, 65 properties for event notification, 132 size of trace log files of Common Component, 106 single home, 27 SLP service starting and stopping, 151 SMTP server setting up for email alerts, 124 SNMP traps information included in log files, 128 required settings for receiving, 124 sending to log files, 128 setting up Device Manager, 129 specifying included information, 129 specifying information to include in SNMP traps, 129 SMTP user au
