HP XP7 Command View Advanced Edition Administrator Guide (Web Version) Part number: TK981-96004 First edition: April 2014
Legal and notice information © Copyright 2014 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 .............................................................................................. 19 1 System configuration and requirements ............................................... 21 System configuration ................................................................................................................. Network security configuration ................................................................................................... Common security risks ..................
2 Network configuration ...................................................................... 63 Port settings .............................................................................................................................. Ports used by HP XP7 Command View Advanced Edition products ............................................ Ports used by Common Component ................................................................................ Ports used by the Device Manager server ................
Changing the password-encoding level in the Device Manager CLI and the Tiered Storage Manager CLI ........................................................................................................................................ 106 5 Configuring Device Manager for use with related products .................. 107 Linking with Performance Advisor ..............................................................................................
7 Configuring Device Manager for CIM/WBEM ................................... 149 About CIM/WBEM ................................................................................................................. CIM/WBEM functions in Device Manager ................................................................................. Specifying a namespace ..........................................................................................................
Installing HP XP7 Command View Advanced Edition on the migration-destination server ............ Exporting databases from the migration-source server ........................................................... Exporting databases in a non-cluster configuration ......................................................... Exporting databases in a cluster configuration ............................................................... Importing databases into the migration-destination server ........................
Generating audit log files ........................................................................................................ Information included in audit logs ....................................................................................... Editing the audit log environment settings file ....................................................................... Checking audit log data ..........................................................................................................
13 Support and other resources .......................................................... 311 Contacting HP ........................................................................................................................ HP technical support ......................................................................................................... Subscription service .......................................................................................................... Documentation feedback .....
logger.hbase.MaxFileSize ................................................................................................. Device Manager dispatcher properties (dispatcher.properties file) ................................................. server.dispatcher.message.timeout ...................................................................................... server.dispatcher.message.timeout.in.processing ................................................................... server.dispatcher.daemon.
server.dispatcher.daemon.replication.config.offset ................................................................. server.dispatcher.daemon.replication.config.minute ............................................................... server.dispatcher.daemon.replication.performance.rpm.updateInterval ..................................... server.dispatcher.daemon.replication.performance.pa.updateInterval ...................................... server.dispatcher.daemon.replication.performance.pa.offset .........
logger.serverMessageMaxFileSize ...................................................................................... logger.serverTraceMaxFileSize ........................................................................................... logger.guiMessageMaxFileSize .......................................................................................... logger.guiTraceMaxFileSize ...............................................................................................
Device Manager agent operations properties (server.properties file) .............................................. server.agent.port .............................................................................................................. server.http.localPort ........................................................................................................... server.http.port ................................................................................................................. server.
Figures 1 Basic system configuration ........................................................................................ 21 2 Separate management LAN with a firewall configuration ............................................. 24 3 Environment settings on virtual machines (when Host Data Collector is used for management) .........................................................................................................
Tables 1 Maximum number of management resources .............................................................. 25 2 Appropriate memory heap size for the Device Manager server ..................................... 26 3 Hosts that can be managed by Device Manager ......................................................... 28 4 Host management software supported by Device Manager .......................................... 29 5 Storage systems that can use Device Manager to manage copy pairs .....................
26 Port numbers that must be registered as firewall exceptions between the management server and an SMI-S provider ................................................................................... 80 27 Port numbers that must be registered as firewall exceptions between the management server and a CIM client ...........................................................................................
57 Values to specify for the type option when migrating databases (For a cluster configuration) ....................................................................................................... 193 58 Recommended property values for a host that will manage 100 or more LUs (when the host is not using a volume manager) ........................................................................
88 Information in message-portion ............................................................................... 252 89 Information in message text when the Device Manager server receives a request or sends a response (for server processing) ........................................................................... 255 90 Information in message text output when the Device Manager server receives a request or sends a response (for launching a product) .......................................................
Preface This manual explains how to configure HP XP7 Command View Advanced Edition (abbreviated hereafter as Device Manager), HP XP7 Tiered Storage Manager (abbreviated hereafter as Tiered Storage Manager), and XP7 Command View AE 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 Management client The computer used to operate Device Manager, Tiered Storage Manager, and Replication Manager.
The computer that centrally manages storage systems and hosts. HP XP7 Command View Advanced Edition is installed on this computer. The management server supports an active-standby type clustering configuration consisting of two computers.
• Use one management server to manage one storage system. Do not configure a system such that multiple management servers manage a single storage system. • On a single Device Manager server, you cannot use multiple storage administrator accounts to manage multiple storage partitions. If you want to manage storage partitions individually, you must provide a Device Manager server for each storage partition.
Security configuration recommended for Device Manager The computer hosting Device Manager server must either be dual-homed or have two NICs, and every other management application must be of a similar configuration. The first NIC for each computer is attached to a LAN dedicated to manage traffic between the management computer and managed storage systems. A second NIC is attached to a LAN where access is governed by a firewall.
Maximum number of resources that can be managed There are upper limits to the number of resources that can be managed by Device Manager, Tiered Storage Manager, and Replication Manager. HP recommends that you operate each product within these limits.
Information to collect in advance • Number of LDEVs to be managed Table 2 Appropriate memory heap size for the Device Manager server Memory heap size Managed resource Number of LDEVs per storage system 512MB 1,024 MB 2,048 MB 2,000 or less 6,000 or less 6,001 or more To change the memory heap size: 1. Use a text editor to open the following file. In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\ DeviceManager\Server\Server.ini 2.
To change the JDK: 1. Stop the services of HP XP7 Command View Advanced Edition products. 2. Execute the command below, and in the window that opens, select the JDK you want to use. In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ bin\hcmds64chgjdk 3.
Information to collect in advance Installation path of the Java execution environment to be used. To change the Java execution environment used by Host Data Collector: 1. Stop the Host Data Collector service. 2. Use the absolute path to set the installation path of the Java execution environment to the javapathlocation property in the javaconfig.properties file for Host Data Collector. 3. Start the Host Data Collector service.
NOTE: The names of the hosts managed by Device Manager must be 50 bytes or less. Host management software supported by Device Manager Device Manager centrally manages hosts by collecting information from them via the host management software.
Prerequisites for normal hosts To manage normal hosts by using Host Data Collector or the Device Manager agent, you must perform environment setup of the normal hosts before registering them in Device Manager. NOTE: If you use Host Data Collector or the Device Manager agent to register Linux hosts that recognize 256 or more logical unit numbers in a storage system, the KAIC03006-E error message is output and the operation fails.
• The user account used when the host is registered has been created specifically for Host Data Collector (recommended). • When the OS of a normal host to be managed is AIX, the ODMDIR environment variable is set. • Update permissions (rwx) are set for the /tmp directory. • Settings have been specified in the PATH environment variable so that the sudo command can be executed. • Settings have been specified in the /etc/sudoers file so that the sudo command can be executed.
Prerequisites for normal hosts managed by Device Manager agent To use the Device Manager agent to manage normal hosts, install the Device Manager agent on each normal host. After installation, specify the environment settings such as the management server information and the execution interval of the HiScan command. In addition, on normal hosts running the AIX OS, set the ODMDIR environment variable.
Figure 3 Environment settings on virtual machines (when Host Data Collector is used for management) Host Data Collector comes with HP XP7 Command View Advanced Edition, which is installed on the management server, but can also be installed on a computer other than the management server. Before you register virtual machines in Device Manager, the following environment settings must already be specified on the virtual machines.
• Installing VMware Tools on each of the virtual machines to be managed (When VMware ESX is used as the virtualization software) When managing a UNIX host (When information about the host is collected by using the root account) • SSH is enabled. • Settings have been performed so that you can log in as root via a remote SSH login with password authentication.
Related topics • Chapter 12, page 295 • How to register a virtualization server: HP XP7 Command View Advanced Edition User Guide or HP XP7 Command View Advanced Edition CLI Reference Guide Prerequisites for virtual machines managed by Device Manager agent To use the Device Manager agent to manage virtual machines, install the Device Manager agent on each virtual machine.
• When VMware ESX is used as the virtualization software, install a VMware Tools on each virtual machine. • Register the virtualization server that runs in the same physical environment in Device Manager. • For virtual machines running the AIX OS, set the ODMDIR environment variable.
Configuration in which an HBA is shared by multiple virtual machines Figure 6 Operation workflow for allocating volumes to virtual machines (when sharing an HBA by multiple virtual machines) 1. Register one of the virtual machines that share an HBA as a normal host in Device Manager. Do not register the virtualization server that runs in the same physical environment in Device Manager. 2.
Configuration in which a virtual HBA is allocated for each virtual machine (by using NPIV HBAs) Figure 7 Operation workflow for allocating volumes to virtual machines (when allocating a virtual HBA to each virtual machine) 1. 2. 3. Register the virtualization servers that run the virtual machines whose volume status you want to manage in Device Manager. Register the virtual machines whose volume usage you want to manage in Device Manager as normal hosts.
Tasks required to change the virtual machine configuration In a configuration in which a virtual HBA is allocated (an NPIV HBA is used) for each virtual machine, any changes to the configuration of virtual machines must also be applied to Device Manager. If you move a virtual machine from one virtualization server to another : You need to update (refresh) the information of the source and destination virtualization servers in Device Manager.
Figure 8 Environment settings on virtualization servers (when Host Data Collector is used for management) • Host Data Collector comes with HP XP7 Command View Advanced Edition, which is installed on the management server, but can also be installed on a computer other than the management server. To install multiple Host Data Collector computers, make sure that the same Host Data Collector version and revision are installed on all computers.
Figure 9 Operation workflow for managing virtualization server Notes on operating virtualization servers Note the following when operating virtualization servers: • To check the latest volume information of virtualization servers, manually refresh information for each virtualization server by using Device Manager.
Figure 10 Operation workflow of managing a mainframe host Related topics • How to specify environment settings from the Device Manager CLI: HP XP7 Command View Advanced Edition CLI Reference Guide • How to specify environment settings for XP7 mainframe agent: HP XP7 Command View Advanced Edition Mainframe Agent Installation and Configuration Guide Related products This section describes the products related to Device Manager and Tiered Storage Manager.
• CLI You can use the Device Manager CLI to define copy pairs or change pair statuses. Storage systems that can use Device Manager to manage copy pairs The storage systems that can use Device Manager to manage copy pair differ depending on whether you use the GUI or CLI.
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.
CAUTION: The requirements for defining or managing copy pairs by using a volume in a virtual storage machine on HP XP7 are as shown below: • If you want to operate virtual volumes by using physical IDs, copy pairs must be configured in such a way that they are managed with the central management method. • The configuration definition file must be recreated to match the new environment after migration.
- If there is one host that recognizes the P-VOL and one host that recognizes the S-VOL, install a Device Manager agent on each of the hosts. - If there are multiple hosts that recognize the P-VOL and multiple hosts that recognize the SVOL, install a Device Manager agent on one of the hosts that recognize the P-VOL and one of the hosts that recognize the S-VOL.
CAUTION: Before you manipulate the copy pair from the Device Manager GUI or CLI, check whether authentication mode is enabled for the command device that is connected to the host (application server). If so, you must execute the raidcom -login command on the host to authenticate yourself. • If the OS of the host is Windows, you must be authenticated as the user who executes the Device Manager agent service (HBsA Service).
CAUTION: When the Device Manager agent is running, do not perform logout processing of user authentication for the storage system by directly executing a RAID Manager command. If you do so, processing performed from the Device Manager GUI or CLI might not finish properly. If you need to log out, stop the Device Manager agent service first.
• A host that recognizes the S-VOL • Pair management server Pair management server conditions: • Device Manager agent must be installed on the 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). • RAID Manager must be installed on the pair management server.
- P-VOL - S-VOL - All pool volumes that make up a pool (when managing Snapshot or Fast Snap pairs) - All journal volumes that make up a journal (when managing Continuous Access Journal pairs) • A resource group in which a command device has been registered must be created and assigned to each user.
Figure 13 Example of a system configuration for managing copy pairs (virtual command device server configuration) Management server conditions: The following computers must be registered as the Device Manager management resources: • A host that recognizes the P-VOL • A host that recognizes the S-VOL Host (application servers) conditions: • Device Manager agent version 7.1 or later must be installed on the application servers.
CAUTION: • If the HORCM_ALLOW_INST parameter is specified in the configuration definition file on the virtual command device server, the default port number (34000+instance-number+1) must be used for the RAID Manager initiator port of the application server. • Before you manipulate the copy pair from the Device Manager GUI or CLI, check whether authentication mode is enabled for the command device that is connected to the host (virtual command device server).
and the information of the command devices is defined in the rgcmddev.properties file of the Device Manager agent. • The authentication mode is enabled for the command device, and the raidcom -login command is used for user authentication for all the command devices whose storage system resource group ID is 0 (resource pools of the default virtual storage machine in HP XP7). If the OS of the host is Windows, you must be authenticated as the user who executes the Device Manager agent service (HBsA Service).
Figure 14 Example of a system configuration for managing copy pairs (when copy pairs are defined in a configuration definition file) Management server conditions: The following computers must be registered as the Device Manager management resources: • A host that recognizes the P-VOL • A host that recognizes the S-VOL Pair management server conditions: • Device Manager agent version 7.1 or later must be installed on the pair management server.
- All journal volumes that make up a journal (when managing Continuous Access Journal pairs) Note that managing partitioned resources might slow the display for some Replication Manager GUI operations. If a virtual command device is to be used, HP recommends that you allocate the resource group for each storage system (default resource group) to users. When a virtual storage machine is created to manage resources in HP XP7: • The volumes below must be registered in a virtual storage machine by the user.
Figure 15 Example of a system configuration for managing copy pairs (when copy pairs are defined as a device group) Management server conditions: • The following computers must be registered as the Device Manager management resources: - A host that recognizes the P-VOL - A host that recognizes the S-VOL • • • • Device Manager agent version 7.1 or later must be installed on the management server. RAID Manager version 01-25-03/01 or later must be installed on the management server.
• From the P-VOL and S-VOL, LUN security must be set for the host (application server). The management server does not need to recognize the P-VOL or S-VOL. • The P-VOL and S-VOL must be recognized by the hosts (application servers). HP recommends that P-VOL and S-VOL be assigned to separate application servers. Resource group requirements (when managing partitioned resources in HP XP7 or P9500): • The volumes below must be registered in a resource group managed by the user.
Storage system requirements for managing copy pairs Set up the environment in accordance with the storage system requirements. Table 6 Storage system requirements for managing copy pairs Storage system Function Requirements • Prerequisite software for Continuous Access Journal must be installed and the license must be enabled. • There must be a fibre-channel connection between the two ports used for an MCU-RCU path.
Storage system Function Requirements • Prerequisite software for Snapshot must be installed and the license must be enabled. Snapshot • To be used as an S-VOL, a V-VOL (a special LU) must be prepared in advance. Perform the preparations in the following order: • Create a pool. • Create a V-VOL. • Prerequisite software for Fast Snap must be installed and the license must be enabled.
• System configuration for using an SVP configuration to manage copy pairs (when copy pairs are defined in a configuration definition file), page 53 • System configuration for using an SVP configuration to manage copy pairs (when copy pairs are defined as a device group), page 55 Prerequisite version of the Device Manager agent for managing copy pairs The prerequisite version of the Device Manager agent varies depending on the storage system to be managed and the program to be used.
To create a configuration definition file, Device Manager agent version 3.1 or later must be installed on each host. #: The following table lists the Device Manager agent version required for each storage system model. Table 9 Device Manager agent version required for each storage system model when managing copy pairs by using the CLI Storage system model Device Manager agent version HP XP7 8.0 or later P9500 7.0 or later XP24000 5.7 or later XP20000 5.8 or later XP12000 XP10000 1.
• If you want to use Device Manager to control copy pairs managed by RAID Manager, the configuration definition file on the host that manages the P-VOL of the copy pair and the configuration definition file on the host that manages the S-VOL of the copy pair must have the same group name and the same pair name. If different names are specified, Device Manager cannot control that copy pair.
2 Network configuration This chapter describes the settings for the HP XP7 Command View Advanced Edition products that are required in various network configurations. Port settings This section describes the port numbers and firewall settings used by the HP XP7 Command View Advanced Edition products.
Port number Description 22018/tcp Used internally for Common Component communication (receiving a termination message from the Web server). This port number can be changed. Used internally for Common Component communication (communication with the Web server). 22025/tcp This port number can be changed. Used internally for Common Component communication (receiving a termination message from the Web server). 22026/tcp This port number can be changed.
Port number Description Used internally for Device Manager server communication, for communication with management clients (via the GUI or the CLI),for communication with storage systems, and for communication with hosts (Device Manager agents). 2001/tcp# Note that the Device Manager server cannot start if this port is being used by another product. You can change this port number by modifying the server.http.port property in the server.properties file of the Device Manager server.
Ports used by the Tiered Storage Manager server For the management server, ensure that the port numbers specified for use by the Tiered Storage Manager server are different from the port numbers used by other programs installed on the same computer. Table 12 Ports used by the Tiered Storage Manager server Port number Description Used for communication with management clients. 20352/tcp You can change the port by modifying the server.rmi.port property in the server.
Port number 22105/tcp 22106/tcp Description Used for SSL communication between the Device Manager server and the RMI server. You can change the port by using the hdc.common.rmi.ssl.serverPort property in the hdcbase.properties file of Host Data Collector. Used for SSL communication between the Device Manager server and the class loader. You can change the port by using the hdc.common.https.serverPort property in the hdcbase.properties file of Host Data Collector.
Port number Description Used internally for Device Manager agent communication. 24043/tcp You can change the port by using the server.http.localPort property in the server.properties file of the Device Manager agent. Related topics • • • • Changing Device Manager agent properties, page 377 server.agent.port, page 384 server.http.localPort, page 384 server.http.
Target storage system Port number Description 51099/tcp Used for communication with the management server or management clients (GUI). This port number cannot be changed. 51100/tcp Used for communication with the management server or management clients (GUI). This port number cannot be changed. 80/tcp Used for communication with management clients (GUI). This port number cannot be changed. XP12000 443/tcp Used for starting Element Manager by SSL from management clients (GUI).
4. If you change the following port numbers, you need to change the URLs of all HP XP7 Command View Advanced Edition products that are installed on the management server: • 22015/tcp (used for accessing HBase 64 Storage Mgmt Web Service) You need to change the URLs if you use non-SSL for communication between the management server and management clients.
Default port number Settings files Location In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ uCPSB\CC\web\containers\HiCommand64\ usrconf\usrconf.properties webserver.connector.ajp13.port In Linux: installation-directory-for-HP-XP7Command-View-Advanced-Edition/ Base64/uCPSB/CC/web/containers/ HiCommand64/usrconf/usrconf.properties In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ uCPSB\CC\web\containers\HiCommand64\ usrconf\usrconf.
Default port number Settings files Location In Windows: 22026/tcp installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ uCPSB\CC\web\containers\DeviceManagerWebService\usrconf\usrconf.properties In Linux: webserver.shutdown.port installation-directory-for-HP-XP7Command-View-Advanced-Edition/ Base64/uCPSB/CC/web/containers/ DeviceManagerWebService/usrconf/usrconf.properties 22031/tcp installation-folder-for-HP-XP7-CommandView-Advanced-Edition\Base64\uCPSB\httpsd\conf\user_hsso_httpsd.
Default port number Settings files Location In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ uCPSB\CC\web\redirector\workers.properties In Linux: worker.HBase64StgMgmtSSOService.port installation-directory-for-HP-XP7Command-View-Advanced-Edition/ Base64/uCPSB/CC/web/redirector/ workers.properties 22033/tcp In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ uCPSB\CC\web\containers\HBase64StgMgmtSSOService\usrconf\usrconf.
Registering firewall exceptions for Device Manager and Tiered Storage Manager When the ports or processes used by HP XP7 Command View Advanced Edition products are registered as firewall exceptions, connection to the registered ports or processes from outside the network is permitted.
Originator Destination Remarks Port number Machine Port number Machine 24500/tcp# Management server Management client any/tcp (Tiered Storage Manager CLI) This setting is required when SSL communication is used. #: This port number can be changed.
Originator Destination Remarks Port number Machine Port number Machine • HP XP7 • P9500 • XP24000 • XP20000 any/tcp Management server 51099/tcp • XP12000 - • XP10000 • SVS200 • XP1024 • XP128 any/tcp Management server 51100/tcp any/tcp Management server 51100/tcp • XP24000 • XP20000 • HP XP7 • P9500 This setting is required when you perform an upgrade installation to a Device Manager server version 6.0.0-00 or later. - Legend: -: Not applicable #: This port number can be changed.
Originator Destination Remarks Port number Machine Port number Machine • HP XP7 • P9500 • XP24000 any/tcp Management client (GUI) • XP20000 1099/tcp • XP12000 - • XP10000 • SVS200 • XP1024 • XP128 • HP XP7 • P9500 • XP24000 any/tcp Management client (GUI) • XP20000 51099/tcp • XP12000 - • XP10000 • SVS200 • XP1024 • XP128 • HP XP7 any/tcp Management client (GUI) 51100/tcp • P9500 • XP24000 - • XP20000 any/tcp any/tcp any/tcp any/tcp Management client (GUI) Management client (GUI)
-: Not applicable Table 20 Port numbers that must be registered as firewall exceptions between the management server and a normal host Originator Destination Remarks Port number Port number Machine • Virtual machine 2001/tcp# Management server any/tcp Management server 24041/tcp# any/tcp Management server 24042/tcp# any/tcp Machine • Normal host • Normal host • Virtual machine • Normal host • Virtual machine - - - Legend: -: Not applicable #: This port number can be changed.
This port number can be changed.
Originator Destination Remarks Port number Machine Port number Machine • VMware ESX any/tcp Host Data Collector computer 80/tcp any/tcp Host Data Collector computer 139/tcp • VMware vCenter Server that manages VMware ESX Normal host • VMware ESX any/tcp Host Data Collector computer 443/tcp • VMware vCenter Server that manages VMware ESX This setting is required when non-SSL communication with a management-target virtualization server is used.
Legend: -: Not applicable #: This port number can be changed. Table 28 Port numbers that must be registered as firewall exceptions between the management server and a mail server Originator Destination Remarks Port number Machine Port number Machine This setting is required to send an email to a user when the following events occur: any/tcp Management server (Device Manager server) 25/tcp#1 Mail server#2 • An alert occurs in a storage system.
Originator Destination Remarks Port number Machine Port number Machine any/tcp Management server 1812/udp# RADIUS server - Legend: -: Not applicable #: This port number is generally used. However, a different port number might be used for an external authentication server.
Component Name added to the exceptions list Device Manager HBase64(java) Path installation-folder-for-HP-XP7-Command-ViewAdvanced-Edition\Base64\uCPSB\hjdk\jdk\jre\bin\ java.exe# JDK Tiered Storage Manager HBase64(java) installation-folder-for-HP-XP7-Command-ViewAdvanced-Edition\Base64\uCPSB\hjdk\jdk\bin\ java.exe# #: If you want to use a JDK other than the one that comes with HP XP7 Command View Advanced Edition, specify the absolute path to the java.
Related topics • Port numbers that must be registered as firewall exceptions for Device Manager and Tiered Storage Manager, page 74 Registering firewall exceptions for Device Manager and Tiered Storage Manager in SUSE Linux Enterprise Server To add the port numbers used by HP XP7 Command View Advanced Edition to the firewall exceptions list, edit the SuSEfirewall2 file. To add the port numbers to the firewall exceptions list: 1.
Operations to complete in advance Log in with administrator permissions. Command format firewall_setup.bat {add|del} Location of the command installation-folder-for-Host-Data-Collector\HDC\Base\bin Options add Adds firewall exceptions. del Removes firewall exceptions. Related topics • • • • Registering an exception for the Host Data Collector service (for SSL communication), page 85 hdc.common.rmi.registryPort, page 368 hdc.common.rmi.serverPort, page 369 hdc.common.http.
Related topics • • • • • • Starting the Host Data Collector service, page 169 Stopping the Host Data Collector service, page 169 Registering an exception for the Host Data Collector service (for non-SSL communication), page 84 hdc.common.rmi.ssl.registryPort, page 370 hdc.common.rmi.ssl.serverPort, page 370 hdc.common.https.serverPort, page 371 Network settings with multiple IP addresses This section describes communication settings for multiple network configurations.
CAUTION: An IP address on the network to which the management client is connected (10.0.0.100 in Figure 16) must be specified for the HP XP7 Command View Advanced Edition product settings below. Do not specify a host name. • The setting for the computer on which the Device Manager Web server function is running (the server.http.host property) Related topics • Changing Device Manager server properties, page 316 • server.http.
To migrate Device Manager to an IPv6 environment: 1. Stop the HP XP7 Command View Advanced Edition product services. 2. Open the user_httpsd.conf file. The user_httpsd.conf file is stored in the following locations: • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ uCPSB\httpsd\conf\user_httpsd.conf • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ Base64/uCPSB/httpsd/conf/user_httpsd.conf 3.
To link with storage systems that support IPv6: • On the Device Manager server, open the server.properties file, and set either of the following items for the server.http.host property: • The IPv6 address of the computer on which the Device Manager server is installed • The host name of the computer on which the Device Manager server is installed The host name must be resolvable to the IPv6 address.
2. 3. If SSL/TLS is used for communication between the following components, re-create a server certificate of the management server by using the new host name: • Between a management server and a management client (GUI) • Between a management server and a management client (Device Manager CLI) • Between a Device Manager server and Replication Manager server • Between a management server and a CIM client If the OS is Linux, edit the /etc/hosts file.
10. Back up the database. If you change the host name, the data that you backed up can no longer be used.
4. Make sure that the HP XP7 Command View Advanced Edition product services are running properly. 5. If the IP address is used in the URLs of HP XP7 Command View Advanced Edition products, change the settings of all HP XP7 Command View Advanced Edition products that are installed on the management server. 6. Depending on the operating environment, review the HP XP7 Command View Advanced Edition product settings. 7. Back up the database.
• Stopping the HP XP7 Command View Advanced Edition services, page 166 • Setting the Device Manager server's information, HiScan command's execution period, and RAID Manager's information (hdvmagt_setting command), page 213 • Changing Device Manager server properties, page 316 • server.http.
2. In Windows, change the URL in the shortcut file. In Windows Server 2008 R2: Select Start, All Programs, HP XP7 Command View Advanced Edition, and then right-click Login - Command View AE. In Properties, change the URL on the Web Document tab. In Windows Server 2012 or Windows Server 2012 R2: From the Start window, display the list of applications, then under HP XP7 Command View Advanced Edition, right-click Login - Command View AE. In Properties, change the URL on the Web Document tab.
3 User account management This chapter describes the settings required for managing user accounts of HP XP7 Command View Advanced Edition products. About password policies A password policy is a set of conditions related to the number of characters or combinations of character types that can be used in passwords for user accounts. By setting a password policy, you can prevent users from setting easily guessed passwords, and reduce the risk of unauthorized access from third parties.
To set a password policy: • Edit the security.conf file. The security.conf file is stored in the following locations: • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ conf\sec\security.conf • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ Base64/conf/sec/security.conf The following table shows the password policies that can be set in the security.conf file. Table 31 Password policies that can be set in the security.
CAUTION: • In all HP XP7 Command View Advanced Edition products, set password policies apply only to user accounts that are added and passwords that are changed after the policy was set. New password policies do not apply to existing user accounts, so users of such accounts can log in to the system even if their passwords do not satisfy the set conditions. • You can also set password policies from the GUI.
of consecutive failed login attempts to 3 and a user fails to log in to Device Manager once, Tiered Storage Manager once, and then Replication Manager once, the user account is automatically locked. Setting account locking policies You can set an account locking policy for HP XP7 Command View Advanced Edition products in the security.conf file. To set an account locking policy: • Edit the security.conf file. The security.
To apply account locking to System accounts: 1. Stop the HP XP7 Command View Advanced Edition product services. 2. Open the user.conf file. The user.conf file is stored in the following locations: • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ conf\user.conf • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ Base64/conf/user.conf If the user.conf file does not exist, create it. 3. Use the following format to specify the account.lock.
To unlock a locked account: • Execute the hcmds64unlockaccount command to unlock the account.
4 Security This chapter describes the security settings required to operate HP XP7 Command View Advanced Edition products. Login warning banners A warning banner is a field for security messages displayed in the Login panel of HP XP7 Command View Advanced Edition products. HP XP7 Command View Advanced Edition products can display an optional message (warning banner), as a security risk measure at login.
To create and register a message displayed on a warning banner: 1. Use a text editor to create a message. Sample messages in English (bannermsg.txt) and Japanese (bannermsg_ja.
2. Execute the hcmds64banner command to register the message : • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\bin\hcmds64banner /add /file file-name [/locale localename] • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ Base64/bin/hcmds64banner -add -file file-name [-locale locale-name] file-name Using an absolute path, specify the file that stores the message. In Linux, do not specify a path that includes a space.
Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux). Information to collect in advance The locale of the message to be deleted (en for English or ja for Japanese).
• The domain name (example: hp.com) • Part of the domain name (example: hp) • The IPv4 or IPv6 address (example: 10.1.2.3 127.0.0.1 2001::123:4567:89ab:cdef) • Part of the IPv4 address (example: 10.1 which, in this case, means 10.1.0.0/16) • IPv4 Network/Netmask format (dot notation) (example: 10.1.0.0/255.255.0.0) • IPv4 or IPv6 Network/c (CIDR notation: c is a decimal integer that indicates the number of bits for identifying a network) (example: 10.1.0.
3. Add information about the management clients to the server.http.security.clientIP property or the server.http.security.clientIPv6 property in the server.properties file for the Device Manager server. 4. Start the services of HP XP7 Command View Advanced Edition product. CAUTION: If you log on to an HP XP7 Command View Advanced Edition product from a management client that is not registered in the user_httpsd.conf file, the GUI cannot be started from that HP XP7 Command View Advanced Edition product.
5 Configuring Device Manager for use with related products This chapter describes the settings required for linking with related products. Linking with Performance Advisor Linking Device Manager or Tiered Storage Manager to Performance Advisor will allow you to use the Mobility tab to check performance information, such as the parity group usage and the volume IOPS. It will also let you launch the Performance Advisor GUI.
Related topics • Starting the HP XP7 Command View Advanced Edition services, page 165 • Stopping the HP XP7 Command View Advanced Edition services, page 166 • Properties for connecting to Performance Advisor (hppa.properties file), page 345 Launching the Performance Advisor GUI Before you can launch the Performance Advisor GUI, you must set up the client.properties file on the Device Manager server. Operations to complete in advance • Set up Performance Advisor.
performance information such as the ratios of storage system processor usage and data in storage system cache memory that is waiting to be written. System configuration for analyzing the performance of Continuous Access Journal To analyze the performance of Continuous Access Journal, either an open system that is configured to manage Continuous Access Journal copy groups or an open system that uses Performance Advisor is required.
Related topics • About the maintenance mode of Replication Manager: HP XP7 Replication Manager Configuration Guide Settings on Device Manager for analyzing Continuous Access Journal performance To analyze Continuous Access Journal performance, specify the properties in the replication.properties file and the rpmlib.rpm.port property in the rpmlib.properties file of the Device Manager server. You can periodically collect information required for analysis from Replication Manager and Performance Advisor.
• In the Replication Manager base.properties file, the base.rmi.enabled property is set to true. Related topics • Settings on Replication Manager: HP XP7 Replication Manager User Guide • About the base.rmi.enabled property in the Replication Manager base.properties file: HP XP7 Replication Manager Configuration Guide Settings necessary to launch Storage Essentials Before you can launch Storage Essential from the Device Manager GUI, you must create the StorageEssentials.conf file.
Settings for using the storage administration functionality of SCVMM 2012 When using the storage administration functionality of SCVMM 2012, from SCVMM 2012, register the Device Manager server as the SMI-S provider. Operations to complete in advance • Register the storage system to the Device Manager server • Set the LUN path from the volume in the managed pool to the host • Set the server.cim.request.queue.
• When changing the configuration from the Device Manager server or the storage system, follow the procedure shown below: • When changing the configuration from the Device Manager server: Rescan the SMI-S provider. • When changing the configuration from the storage system: Refresh the storage system from the Device Manager server, and then rescan the SMI-S provider. When a path is set, after taking the above procedure, also follow the procedure shown below: 1.
When the initial settings are complete, use Command View Advanced Edition Suite to configure the storage system. To log in to a Remote Web Console: 1. In your web browser, specify the following URL: https://IP-address-or-host-name-of-SVP/ 2. The following actions might be required to open the login dialog box, depending on your environment: 3. • If a message indicates that the enhanced security configuration is enabled on the computer, select In the future, do not show this message and click OK.
To change your user account password: 1. Log in to Remote Web Console with the user ID and password given to you by the administrator. 2. Click Settings > User Management > Change Password to change your password. Related topics • Normal login, page 113 Adding your SVP to the trusted sites zone - for Windows server If you are using Remote Web Console on a Windows Server 2003/2008 computer, the following message may appear during login. If it does, you must add the SVP to the trusted sites zone.
Prerequisites You must have the Storage Administrator (Initial Configuration) role to perform this task. To set time periods: 1. Start a web browser and enter the following URL to open the tool panel. http://IP-address-or-host-name-of-SVP/cgi-bin/utility/toolpanel.cgi 2. Click Control Panel to open the Control Panel. 3. Enter the user ID and password and click Login. 4. Click the Set Env. tab to open the Set Env. dialog box. 5. Specify the Remote Web Console parameters as required. 6.
Remote Web Console environment parameters are described in the following table: Table 33 Environment parameters Item Description If the user cannot access the SVP for a certain period of time because of a network error, the RMI time-out logs the user out of the SVP. • The value of the RMI time-out period must be greater than the value set for the smallest polling period, either for checking exclusive lock or for checking obstacles (see below for those parameters).
You must have one of the following roles, depending on the configuration you are backing up or restoring. Table 34 Roles required to back up and restore configuration files Configuration file Description Required role to back up a file Required role to restore a file User Account Information User account information registered to the Remote Web Console. Security Administrator (View Only) Security Administrator (View & Modify) Environment Parameter List The parameters settings in the Set Env.
3. Enter the user ID and password and click Login. 4. Click the Download tab to open the Download file window. 5. Click the files to be downloaded. You can download only the files for which you have permission. 6. Click Submit. The Download File dialog box shows the list of the files to be downloaded. 7. Click Download. The File Download dialog box opens. 8. Click Save. The Save As dialog box opens. 9.
Downloading dump files using the Dump tool Use the Dump tool to download dump files onto a web client. The downloaded dump files can be used for the following reasons: • For troubleshooting purposes. Use the Dump tool to download dump files from SVP and give it to the HP service personnel. • For checking configuration. First click File > Refresh All to refresh the configuration information, and then use the Dump tool to download dump files.
4. Select a file that you want to download. • Existing Dump Files indicates the last dump file that you downloaded. Select this when you want to re-download a previously downloaded dump file. If you have not downloaded any dump files from the Tool Panel, this item does not display even if you have acquired a dump file via SVP. • Normal Dump includes all information about the SVP and the minimum information about the storage system. Select this when you have a less serious problem such as incorrect display.
Configuring Device Manager for use with related products
6 Setting up logs and alerts This chapter describes the settings required to use the HP XP7 Command View Advanced Edition products to monitor the status of the system and errors. Setting up integrated log files Common Component provides a common library used for logging. HP XP7 Command View Advanced Edition products use this library to output trace log information to log files.
Setting up trace log files (Linux) To change the number or size of Common Component trace log files, use the utility program (hntr2util). WARNING! Changing the common trace log settings affects other program products that use the common trace logs. Operations to complete in advance Log in to the system as a root user. To set up Common Component trace log files: 1. Execute the utility program stored in the following location: /opt/hitachi/HNTRLib2/bin/hntr2util 2.
To collect Tiered Storage Manager CLI log files: • Set the necessary properties in the HtsmgetTI.properties file stored in the following location. In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\ TieredStorageManager\SupportTools\CollectTool\ In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ TieredStorageManager/SupportTools/CollectTool/ Table 35 Properties set in the HtsmgetTI.
The alerts that Device Manager can display differ by storage system. The table below lists the alerts that are supported by each storage system.
1. Setting up the SMTP server Set the SMTP server so that the Device Manager server can connect to the SMTP server. Follow the procedure for setting the SMTP server to be used. 2. Registering recipients of email alerts In the Device Manager GUI, register the users who will receive emails. 3. Setting properties for reporting alerts Set the SMTP server information and the email address from which alerts are reported as properties of the Device Manager server. 4.
NOTE: • When there are multiple SMTP authentication methods that the SMTP server specifies, the Device Manager server selects an authentication method (LOGIN or PLAIN in that priority order), and then sends an email. If LOGIN or PLAIN is not specified, the Device Manager server will send an email without using the SMTP authentication.
• server.mail.alert.status Related topics • • • • • • • • • • Changing Device Manager server properties, page 316 server.mail.enabled.storagesystem, page 323 server.mail.from, page 323 server.mail.smtp.host, page 323 server.mail.smtp.port, page 324 server.mail.smtp.auth, page 324 server.mail.errorsTo, page 324 server.eventNotification.mail.to, page 324 server.mail.alert.type.storagesystem, page 324 server.mail.alert.
CAUTION: • If SMTP authentication is enabled on the Device Manager server, but an SMTP authentication user is not registered, email will be sent without using SMTP authentication. • Only one SMTP authentication user can be set on the Device Manager server. The set SMTP authentication user information will be updated each time you execute the command. • You cannot delete the SMTP authentication user information that you set on the Device Manager server.
• Specify a header in the first line, nothing in the second line, and the email body and parameters in the third and following lines. • Specify a header in the format Subject: email-title. • Specify parameters in the format ${parameter-name}. The parameter name is case sensitive. • Use UTF-8 encoding to code. • The file size must not exceed 64 KB. • The length of each line must not exceed 1024 bytes, excluding linefeed characters.
Output only if the severity level is Error, Critical, or Alert. The severity levels for SNMP traps are specified for the customizedsnmptrap.customizelist property in the customizedsnmptrap.properties file.
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 38 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.enabled.storagesystem • 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 39 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-HP-XP7Command-View-Advanced-Edition\ DeviceManager\Server\config\mailmigrationtask-end.
Type Event Template file • In Windows: installation-folder-for-HP-XP7Command-View-Advanced-Edition\ TieredStorageManager\conf\mailunlockingtask-end.txt Unlocking task ended#2 • In Linux: installation-directory-for-HP-XP7Command-View-Advanced-Edition/ TieredStorageManager/conf/mailunlockingtask-end.txt • In Windows: Volume lock period expired#2 installation-folder-for-HP-XP7Command-View-Advanced-Edition\ TieredStorageManager\conf\mailretention-term-expired.
installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ TieredStorageManager/template By specifying, within the template files, parameters that will automatically be filled in with event information at the time of an event, you can add useful information to the email notifications. The following shows how to create a template, using the template for the Migration task ended event (mail-migrationtask-end.txt) as an example.
Parameter Description user The user ID of the user who created the task.
Parameter Description retentionDays Retention period (days) lockedVolumes Device numbers of locked volumes unlockedVolumes Device numbers of unlocked volumes moveToMigrationGroupName Name of the target migration group after task completion Table 42 Parameters for time-lapse events Parameter Description storageDomainName Storage domain name migrationGroupName Migration group name expiredVolumes Device numbers of expired volumes remindAt Scheduled time when an "elapsed time" event will occu
In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\DeviceManager\Server\tools\hdvmmodmailuser.bat -u Device-Manager-user-ID -p Device-Manager-password SMTP-authentication-user-ID [SMTP-authentication-password] In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ DeviceManager/Server/tools/hdvmmodmailuser.
The following shows the syntax of the htsmmodmailuser command: Format htsmmodmailuser -u Tiered-Storage-Manager-user-ID -p Tiered-Storage-Manager-password SMTP-authentication-user-ID SMTP-authentication-password Options -u Tiered-Storage-Manager-user-ID Specify the ID of a user for whom All Resources has been assigned as a Device Manager resource group and who has Admin permission for Tiered Storage Manager.
Requirements of the new Syslog protocol (TLS1.2/RFC5424) The new Syslog protocol (TLS1.2/RFC5424) requires the following: • Operation confirmed Syslog server (rsyslog version 4.6.2) • Syslog server certificate. The IP address of the Syslog server in "Subject Alternative Name: IP Address" of the Syslog server certificate. • Client certificate. Upload the following: Certificate type Format Notes Syslog server root certificate X.509 Obtain the Syslog server root certificate from the server administrator.
Setting and configuring syslog notification for SIMs You can be notified in syslog format when storage system failures occur. Prerequisites • You must have the Storage Administrator (Initial Configuration) role to perform this task. • You must have a server that supports syslogs. • If a firewall is used, a port must be opened to transfer syslogs. To configure settings for syslog notification: 1. Click Settings > Environmental Settings > Edit Alert Settings. 2.
The following SIMs are reported by email: Table 43 SIM reference codes reported by email Reference code Description Alert level xx Expiration. SERIOUS F8 xx Exceeded the licensed capacity. 7F F9 xx Software invalidated by the expiration of the prerequisite software. 60 00 xx Exceeded the pool usage threshold. Failure with paired volumes MODERATE 60 2x xx Pool blockade. Snapshot Pool or Fast Snap Pool MODERATE 62 0x xx Exceeded the pool usage warning threshold.
4. In the Email Settings table, set the email destination address and attributes (To, Cc, Bcc). • To add an email address, click Add. On the Add Address window, set the email address and attributes. • To change an email address and attributes, select the line for the email address to be changed, and click Change. In the Change Settings window, change the email address and attributes. You can select more than one email address. When you selected more than one email address, you can change only attributes.
Reply-To: xxxx@itg.hitachi.com Subject: XP7 Report Date : 25/10/2013 Time : 10:09:30 Machine : XP7(Serial# 64019) RefCode : 7FFFFF Detail: This is Test Report. The field definitions in the test email are listed in the following table: Table 44 Email details for system failures notice # Item Description 1 Date Date and time when the email was sent. This time stamp is set by the mail server. 2 To Email address of the receiver. 3 From Email address of the sender.
To set system options: 1. Click Settings > Environmental Settings > Edit System Options. 2. Select the system option to set and click Enable. 3. • Hide alert information. If you enable this system option, the Alert window does not open. • Refresh forcibly after Apply. If you enable this system option, after settings changes are applied to the storage system, the configuration information for the storage system is forcibly updated. • Disable data polling. If you enable this system option, polling stops.
Setting up logs and alerts
7 Configuring Device Manager for CIM/WBEM This chapter explains how to configure Device Manager for CIM/WBEM . About CIM/WBEM Device Manager supports CIM and WBEM, which have been defined by the DMTF standards group. CIM is a method of managing systems in a network environment. WBEM is a standard for managing network devices, such as hosts and storage systems, over the Internet. The CIM model that Device Manager uses complies with the SMI-S specifications advocated by SNIA, and is compatible with SNIA-CTP.
The SMI-S specifications, which Device Manager conforms to, define the interfaces for devices that make up a storage network, such as storage systems, virtual storage systems, switches, and hosts. The functions that need to be provided by the management service to manage the devices are grouped in a profile for each device. The profiles used by the CIM/WBEM functions of Device Manager are the Array profile and its subprofiles. The Array profile defines the interfaces for storage systems.
Specify root/smis/smisxx (xx is an abbreviation for the version number). For example, to specify version 1.5.0, enter root/smis/smis15. The latest namespaces that complies with the specified SMI-S version is selected. • Specify the condition current. Enter root/smis/current. The current namespace is selected. • Specify interop. SMI-S 1.3.0 or a later version supports the namespace interop.
Legend: Y: These CIM methods can be executed. --: These CIM methods cannot be executed. Enabling CIM/WBEM functions When HP XP7 Command View Advanced Edition 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.
Related topics • • • • • Ports used by the Device Manager server, page 64 Starting the HP XP7 Command View Advanced Edition services, page 165 Stopping the HP XP7 Command View Advanced Edition services, page 166 server.cim.support, page 321 server.logicalview.initialsynchro, page 323 Changing CIM/WBEM port numbers To change the port numbers used by CIM/WBEM functions, edit the relevant property files on the Device Manager server.
Required system configuration for acquiring performance information The system configuration in which the performance information of a storage system is acquired by using the CIM/WBEM functions differs depending on the model of the storage system. Figure 21 Example of a system configuration in which performance information of a storage system is acquired Storage system This is a storage system whose performance information is to be acquired.
Settings required to acquire performance information of storage systems This section describes the settings required to acquire performance information for storage systems (P9500, XP24000/XP20000, or XP12000/XP10000/SVS200).
Related topics • Defining the command device (perf_findcmddev command), page 156 • Setting the Device Manager server's information, HiScan command's execution period, and RAID Manager's information (hdvmagt_setting command), page 213 • How to install Device Manager agent :HP XP7 Command View Advanced Edition Installation and Configuration Guide Preparing the Device Manager server to acquire performance information On the Device Manager server, in the server.properties file, set the server.cim.
If no command device recognized by the host is detected, nothing is output to the perf_cmddev.properties file. verify This option compares the settings for the command devices defined in the perf_cmddev.properties file to the settings for the command devices recognized by the host. If the host recognizes multiple command devices, the execution result is output for each. • If the information of a command device defined in the perf_cmddev.
/opt/HDVM/HBaseAgent/mod/hdvm/config Format of the perf_cmddev.properties file Define one command device per line, using the following format. When using the Device Manager agent version 6.4 or later: RAID-ID.serial-number.[SLPR-number.]LDEV-number: deviceFileName When using the Device Manager agent version 6.3 or earlier: RAID-ID.serial-number.LDEV-number: deviceFileName The following table describes values to be specified in the perf_cmddev.properties file. Table 48 Settings in the perf_cmddev.
if you specify this item using the volume GUID, the setting is not affected even if you restart the OS. • If you are using the Device Manager agent version 6.3 or earlier and you want to acquire performance information of all SLPRs in an SLPR environment, you need to define SLPR0 command device in the perf_cmddev.properties file. To define command devices for different SLPRs that belong to the same storage system, define the SLPR0 command device in the first line of the storage system.
To start the SLP service: • Perform either of the following procedures: • From Administrative Tools, select Services and then Service Location Protocol to start the SLP service. • Show the command prompt, move to the folder containing the OpenSLP executable file, and execute the following command: slpd -start To stop the SLP service: • Perform either of the following procedures: • From Administrative Tools, select Services and then Service Location Protocol.
Starting and stopping the SLP service (SUSE Linux Enterprise Server) Operations to complete in advance Log in as a user with root user. To start the SLP daemon: • Execute the following command: # /usr/sbin/rcslpd start To stop the SLP daemon: • Execute the following command: # /usr/sbin/rcslpd stop Releasing the SLP service You might need to release the SLP service (or SLP daemon) when uninstalling HP XP7 Command View Advanced Edition products.
Releasing the SLP daemon (Linux) Operations to complete in advance Log in as a user with root user. To release the SLP daemon: 1. Stop the SLP daemon. 2. If /etc/init.d/slpd exists, delete it. # chkconfig --level 01345 slpd off # chkconfig --del slpd # rm -f /etc/init.
8 Starting and stopping services This chapter explains how to start and stop the HP XP7 Command View Advanced Edition product services. Starting and stopping services of HP XP7 Command View Advanced Edition This section explains how to start and stop the services of Device Manager, Tiered Storage Manager, and Replication Manager.
Process name Service name Function hcmdssvctl.exe HCS Device Manager Web Service Device Manager servlet service Hitachi Network Objectplaza Trace Monitor 2 HP XP7 Command View Advanced Edition common trace information collection (Integrated trace information is collected.) cjstartweb.exe hntr2mon.exe hntr2srv.exe pdservice.
Process name Function HP XP7 Command View Advanced Edition common web service for single sign-on.
To start the services: • Perform the following operations. In Windows: Start the services in either of the following ways: In Windows Server 2008 R2 Select Start > All Programs > HP XP7 Command View Advanced Edition > Manage Services > Start - Command View AE. In Windows Server 2012 or Windows Server 2012 R2 From the Start window, open the application list window, select HP XP7 Command View Advanced Edition, and then Start - Command View AE.
To stop the services: • Perform the following operations: In Windows: Stop the services in either of the following ways: In Windows Server 2008 R2 Select Start > All Programs > HP XP7 Command View Advanced Edition > Manage Services > Stop - Command View AE. In Windows Server 2012 or Windows Server 2012 R2 From the Start window, open the application list window, select HP XP7 Command View Advanced Edition, and then Stop - Command View AE.
To check the operating status of the services: • Perform the following operations: In Windows: Check the operating status of the services in either of the following ways: In Windows Server 2008 R2 Select Start > All Programs > HP XP7 Command View Advanced Edition > Manage Services > Status - Command View AE. In Windows Server 2012 or Windows Server 2012 R2 From the Start window, open the application list window, select HP XP7 Command View Advanced Edition, and then Status - Command View AE.
Process name Function Java-execution-environment-installation-path/ bin/java JavaVM (Adapter)# Java-execution-environment-installation-path/ bin/java JavaVM (Service) Java-execution-environment-installation-path/ bin/java JavaVM (RMI) #: There are as many resident Adapter processes as the value specified for the hdc.adapter.adapterProcessNum property in the hdcbase.properties file for Host Data Collector.
Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux). To stop the Host Data Collector service: • Execute the following command: In Windows: installation-folder-for-Host-Data-Collector\HDC\Base\bin\controlservice.exe stop In Linux: installation-directory-for-Host-Data-Collector/HDC/Base/bin/controlservice.
9 Managing the database This chapter describes how to back up and restore the database for HP XP7 Command View Advanced Edition products. Managing databases The following table describes backing up and restoring, as opposed to exporting and importing. Table 53 Backing up and restoring as opposed to exporting and importing Item Backing up and restoring Exporting and importing Restrictions on HP XP7 Command View Advanced Edition product versions No restrictions Version 5.
Required space: (total-size-of-all-HP-XP7-Command-View-Advanced-Edition-product-databases-to-be-backed-up + 4.
2. Execute the hcmds64backups command to back up the database. In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\bin\hcmds64backups /dir folder-for-storing-backup-files /auto In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ Base64/bin/hcmds64backups -dir directory-for-storing-backup-files -auto dir Specify the absolute path of the directory on the local disk in which the database backup files are stored.
3. Execute the hcmds64srv /stop command to stop the HP XP7 Command View Advanced Edition product services. Then, execute the hcmds64srv /statusall command to make sure that the services have stopped or that the return code of the command is 0. 4. Use the cluster management application to take the following service offline: 5. • HiRDBClusterService _HD1 Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below.
8. Use the cluster management application to enable failover of the resource group. Change the settings of the resources listed below.
Restoring a database when a data inconsistency occurs If a database inconsistency occurs, execute the hcmds64db command to restore the database by using a database backed up via the hcmds64backups command. CAUTION: • The hcmds64db command, which is used in the procedure below, creates temporary files during execution. Make sure that the directory to which the backup file is to be restored satisfies the following conditions: - The write permission is granted to the user who executes the hcmds64db command.
2. Execute the hcmds64db command to restore the database.
10. Check the status of Device Manager tasks from the Device Manager GUI. If a Device Manager task is not completed or has failed, re-create the task or change the execution schedule of the task as necessary. 11. See the message log of Tiered Storage Manager. When Tiered Storage Manager is started for the first time after a database is restored, make sure that the message KATS50354-E is output to a log file.
5. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below.
9. Use the cluster management application to enable failover of the resource group. Change the settings of the resources listed below.
Restoring a database when a database is corrupted If a database is corrupted, execute the hcmds64dbrepair command to restore the database by using a database that was exported via the hcmds64dbtrans. CAUTION: During database restoration, HP XP7 Command View Advanced Edition services stop. Therefore, do not access HP XP7 Command View Advanced Edition while restoration is in progress.
12. See the message log of Tiered Storage Manager. When Tiered Storage Manager is started for the first time after a database is restored, make sure that the message KATS50354-E is output to a log file. The task IDs of Tiered Storage Manager tasks whose status was changed to Failure are output to KATS50354-E. 13. See the volume information of the tasks indicated in the message KATS50354-E and check whether those tasks are completed.
5. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below.
14. If you restored the management server database at the Replication Manager secondary site, refresh the configuration information by using the Replication Manager GUI to synchronize the Replication Manager database at the primary site and the Device Manager database at the secondary site. 15. 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. 16.
Notes on databases, product types, and versions of HP XP7 Command View Advanced Edition products: • If Replication Monitor 5.x or earlier is already installed on the migration source server, before exporting the database, upgrade the product to version 6.0 or later on both the migration source and destination servers. If Replication Monitor cannot be upgraded to version 6.0 or later or if migrating the database is not required, remove Replication Monitor from the products whose databases are to be imported.
Exporting databases from the migration-source server To export the databases of HP XP7 Command View Advanced Edition products, a directory for temporarily storing the database data and a directory for storing archive files are required. For each directory, ensure that a comparable capacity to the total size of the following directories is available.
3. Transfer the exported files to the migration destination server. If the archive file cannot be created, transfer all the files created in the directory specified by the workpath option. In this case, do not change the structure of the files. Exporting databases in a cluster configuration This section explains how to export the databases on the migration destination server when the OS of the management server is in a cluster configuration.
7. Execute the hcmds64dbtrans command to export the databases. installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\bin\hcmds64dbtrans /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.
Importing databases in a non-cluster configuration This section explains how to import the databases on the migration destination server when the OS of the management server is not in a cluster configuration. To import databases into the migration-destination server in a non-cluster configuration: 1. Log on to the management server as a user with Administrator permissions or root permissions. 2.
3. Execute the hcmds64dbtrans command to import the databases.
Product Value Other products Refer to the manual for each product. #1: When importing databases that were exported from an environment of version 7.0 or later, regardless of whether you have registered a Tiered Storage Manager license, import both the Device Manager and Tiered Storage Manager databases at the same time. #2: To import the Replication Manager database, you must also import the Device Manager database at the same time. auto 4.
Importing databases in a cluster configuration This section explains how to import the databases on the migration destination server when the OS of the management server is in a cluster configuration. CAUTION: Use the executing node (a machine that has online set for mode in the cluster.conf file) to import databases. To import databases into the migration-destination server in a cluster configuration: 1. Log on to the management server as a user with Administrator permissions. 2.
8. Execute the hcmds64dbtrans command to import the databases. installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\bin\hcmds64dbtrans /import /workpath working-folder [/file archive-file] /type {ALL|HP-XP7-Command-View-Advanced-Edition-products-whose-databases-will-be-migrated} workpath When using the archive file for the import: Specify the absolute path to the folder used to extract the archive file. Specify a folder on your local disk.
9. On the executing node and standby node, specify true for the server.base.initialsynchro property of the Device Manager server. Because, other than user information, the hcmds64dbtrans 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.
Related topics • Starting the HP XP7 Command View Advanced Edition services, page 165 • Stopping the HP XP7 Command View Advanced Edition services, page 166 • Backing up a database in a cluster configuration, page 173 Administrator Guide (Web Version) 195
Managing the database
10 Using the Device Manager agent This chapter explains the settings that must be specified to run the Device Manager agent. This chapter also explains Device Manager agent operations. Prerequisites for running the Device Manager agent This section provides the prerequisites for running the Device Manager agent. This section also provides notes on using the Device Manager agent.
• If the OS of the host is Windows, the Device Manager agent will not acquire data from devices assigned the drive letter A or B. Assign a drive letter from C to Z for a device managed by the Device Manager agent. • If you change a device file name by using the rendev command on a host whose OS is AIX 7.1 or AIX 6.1 TL6 or later, the new device name must be specified by using printable ASCII characters only.
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.
-check Specify this option to check the latest version of the Java execution environment from Oracle JDK and Oracle JRE installed on the host. CAUTION: • After you execute this command, you must restart the Device Manager agent service.
-unset Removes firewall exceptions. Related topics • server.agent.port, page 384 • server.http.localPort, page 384 • server.http.port, page 384 Registering a Java process in SED as an exception (AIX) If the OS of the host is AIX and you change the SED mode to all after installing the Device Manager agent, you must execute the sedmgr command to register the Java process used by the Device Manager agent in SED as an exception.
Managing copy pairs If you use Device Manager or Replication Manager to manage copy pairs, depending on the environment, you must change property settings on the Device Manager agent or the Replication Manager server. • If RAID Manager is installed in a location other than the default location, or if the host OS is Windows and the RAID Manager installation drive is different from the Device Manager agent installation drive: server.agent.rm.location property in the server.
Set the value to 1800 or greater. • hdvmagtif.MaxPollingCount property in the agentif.properties file of the Replication Manager server Set the value to 100. • hdvmagtif.PollingInterval property in the agentif.properties file of the Replication Manager server Set the value to 60 or greater. • If you want to unify the coding format of pair volume information into the HORCM_DEV or HORCM_LDEV format when creating pairs: server.agent.rm.pairDefinitionForm property in the server.
• About the hdvmagtif.MaxPollingCount property and the hdvmagtif.PollingInterval property in the Replication Manager server agentif.properties file: HP XP7 Replication Manager Configuration Guide Settings required for a host to manage 100 or more LUs If you want a host to manage 100 or more LUs, you must change the property settings (such as the length of data that can be received by the Device Manager server and the timeout value for the Device Manager agent) according to the number of LUs to be managed.
Recommended property values to be set for a host that will manage 100 or more LUs (when the host is not using a volume manager) The following table lists the recommended property values for hosts that do not use a volume manager. Table 58 Recommended property values for a host that will manage 100 or more LUs (when the host is not using a volume manager) Number of LUs managed by Device Manager, and recognized by the host server.http. entity.maxLength (units: bytes) server.http. server.
shown in the tables is not recommended: It will take more than one hour for the HiScan operation to complete, and the operation might fail. Table 59 Recommended property values for a host that will manage 100 or more LUs (when the host is using a volume manager in Windows) Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) server.http. server.timeOut (units: seconds) server.util.
Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) 1,000/1,000 72,000,000 or more server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) 1,200 server.agent.
Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity. maxLength (units: bytes) server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) server.agent.
The following describes the resident processes of the Device Manager agent. Table 64 Resident processes of the Device Manager agent (Windows) Process name Service name Function hbsa_service.exe HBsA Service Device Manager agent service Table 65 Resident processes of the Device Manager agent (UNIX) Process name Function hbsa_service Device Manager agent service Immediately after Device Manager agent installation is completed, the Device Manager agent service is enabled.
Specify this option to start the Device Manager agent service. stop Specify this option to stop the Device Manager agent service. If the -f option is also specified, the command forces the Device Manager agent service to stop. In such a case, all processing is forced to terminate, thus ongoing processing of jobs is not guaranteed. status Specify this option to check the operating status of the Device Manager agent service.
Device Manager agent operations This section explains Device Manager agent operations. Checking the available agent functions (hbsa_modinfo command) Use the hbsa_modinfo command to display the names and versions of available add-on modules. The names and versions of add-on modules are displayed in V.R1.R2-MM format (V: version number, R1 and R2: revision number, MM: modification version number).
• Replication Manager agent Monitors the status of storage system replication. • Replication Manager Application agent Centrally manages backup operations on a unit basis using the high-speed copy function of the storage system. Deleting the Device Manager agent's registry entries and files (hbsa_util command) If the OS of the host is Windows, you can use the hbsa_util command to delete the Device Manager agent's registry entries and files.
In AIX: /usr/HDVM/HBaseAgent/bin Setting the Device Manager server's information, HiScan command's execution period, and RAID Manager's information (hdvmagt_setting command) Use the hdvmagt_setting command to set the Device Manager server's information, the HiScan command's automatic execution period, and the information necessary for using RAID Manager. This command lets you interactively set the items listed in the following table.
Information to collect in advance • IP address or host name of the Device Manager server • Port number of the Device Manager server You can check this value by using the server.http.port property (for non-SSL communication with the Device Manager server) or the server.https.port property (for SSL communication with the Device Manager server) in the server.properties file for the Device Manager server.
If the configuration of the host's storage systems or file system is changed, the change can be applied to the Device Manager server by executing the HiScan command manually. Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for UNIX).
-c Specifies the interval (in seconds) at which host information is sent to the Device Manager server. Host information is continuously sent to the Device Manager server at the specified interval, until a forced termination occurs. Values of less than ten seconds are recognized as invalid. Specify a value in the range from 10 to 2147483647. -t Specify this option if you want to output the host information that was sent to the Device Manager server to an XML file. The file is output to the current directory.
hldutil {-h log-number -hb log-file-name | -hrm {log-number | all } | -history number-of-log-file-generations } Location of the command In Windows: installation-folder-for-Device-Manager-agent\util\bin In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/util/bin In AIX: /usr/HDVM/HBaseAgent/util/bin Options -d Specify this option to display information about the LDEV specified as an argument of this option. (The argument is either a drive number (in Windows) or device special file name (in UNIX).
When specifying multiple sort keys, place a one-byte space between sort keys. If you specify multiple sort keys, the command sorts information using the sort keys in the order in which they are specified. If you specify the file system name as the sort key, the command sorts LDEV information using the file system name that is included in each logical device and assigned the lowest ASCII code.
Information displayed by the hldutil command The following table lists and describes the information output when you execute the hldutil command. The information items are output in the order shown in the table. The items displayed differ depending on the OS and the specified options.
Storage system models corresponding to RaidID values displayed by the hldutil command The RaidID values displayed by the hldutil command are strings that indicate storage system models. The following table shows the correspondence between RaidID values and storage system models.
Sort key Descriptions ser Serial number of a storage system tid Target ID vend Vendor name wwnn Node WWN name wwnp Port WWN name Configuration definition file for managing copy pairs In Device Manager, you can use a user-created RAID Manager configuration definition file to manage copy pairs. Prerequisite environment for using the configuration definition file To use the configuration definition file, you need to set up the environment as follows on the host on which RAID Manager is installed.
3. Use the Device Manager GUI or CLI to refresh the storage system that contains the copy pair volumes for which the configuration definition file was created. NOTE: • If a parameter not supported by Device Manager is used, the configuration definition file is assumed to be invalid and the system does not execute normal processing. Even though a parameter is supported, Device Manager might not support certain description formats.
• HORCM_CTQM#2 #1 This parameter is supported by Device Manager agent version 8.0 or later. However, the definition of the HORCM_VCMD property cannot be changed from a Device Manager agent. #2 This parameter is supported by Device Manager agent version 6.2 or later. Note that when you create or use a copy pair, even if HORCM_CTQM information is defined in the configuration definition file, the Device Manager agent will operate while ignoring the definition.
• HORCM_INST parameter description format, page 230 • HORCM_INSTP parameter description format, page 232 HORCM_MON parameter description format Use the HORCM_MON parameter to specify the machine information for the local host and the interval for monitoring errors in copy pair volumes. • ip_address Specify the IP address (the Device Manager agent whose version is 5.9 or later supports the IPv6 protocol), host name, NONE, or NONE6.
• service Specify the port name or port number. • Specify the port name using 1 to 15 single-byte characters. The environment must support the conversion of port names to port numbers. • Specify the port number as a numeric value from 0 to 65535. • poll Specify a value (in ten millisecond units) or -1. • timeout Specify the timeout period in ten millisecond units. Table 71 Support status of HORCM_MON parameter description format Item Version ip_address service poll timeout 6.
For the Device Manager agent 1.1 or earlier, this item is case sensitive. GUID format \\.\Volume{GUID} CMD format \\.\CMD-serial-number[-logical-device-number[-port-name[-host-groupnumber]]] You must use base-10 numbers to specify the serial number and logical device number. For the host group number, if the version of the Device Manager agent is 5.6 or later, specify a value from 0 to 254. If the version of the Device Manager agent is 5.5 or earlier, specify a value from 0 to 127.
Legend: Yes: Supports all description formats. Related topics • Editing the configuration definition file, page 221 • Description conventions for the configuration definition file, page 223 • Notes on using the configuration definition file, page 234 HORCM_DEV parameter description format Use the HORCM_DEV parameter to specify information about the storage system that contains volumes to be used as copy pairs. • dev_group Specify the group name.
#: If no value is specified or 0 is specified, multi-target configuration pairs cannot be created with Continuous Access. When the version of the Device Manager agent is from 6.0 to 7.3.1: Business Copy: 0 to 2 Snapshot: 0 to 63 Continuous Access: Not specified Continuous Access Journal: Not specified#, 0#, h1, h2, or h3 #: If no value is specified or 0 is specified, multi-target configuration pairs cannot be created with Continuous Access. When the version of the Device Manager agent is 5.
• The same dev_name value must not be duplicated in a configuration definition file. • Specify no more than 31 single-byte characters. A hyphen (-) cannot be specified at the beginning of the character string. • Serial# Specify the system number of the storage system using the decimal number or serial-number:journal-ID format. • CU:LDEV(LDEV#) Specify the LDEV number using the decimal number, hexadecimal number, or CU:LDEV format.
Continuous Access Journal: h1, h2, or h3 Table 74 Support status of HORCM_LDEV parameter description format Item Version dev_group 6.2 or later Yes dev_name Serial# Yes CU:LDEV(LDEV#) MU# Yes Yes Yes Yes No 6.1 to 05-60 Yes Yes Yes Supports description formats other than the serial-number:journal-ID format. Earlier than 05-50 No No No No Legend: Yes: Supports all description formats. No: Does not support any description formats.
• The table below lists the values that can be specified for ip_address. Note that some formats cannot be specified for ip_address because they cannot identify a host. Table 75 Values that can be specified for the ip_address of HORCM_INST parameter Device Manager agent version Value 05-80 or later 05-70 or earlier IP address Yes Yes Host name Yes Yes Loopback IP addresses (127.0.0.1 to 127.255.255.
• • • • HORCM_MON parameter description format, page 224 HORCM_DEV parameter description format, page 227 HORCM_LDEV parameter description format, page 228 Notes on using the configuration definition file, page 234 HORCM_INSTP parameter description format Use the HORCM_INSTP parameter to specify the machine information and path group ID of the remote host. • dev_group Specify the contents specified for dev_group of the HORCM_DEV parameter or HORCM_LDEV parameter.
Specify the port name or port number. • Specify the port name using 1 to 15 single-byte characters. The environment must support the conversion of port names to port numbers. • Specify the port number as a numeric value from 0 to 65535. • pathID Specify the path group ID as a decimal number from 1 to 255. • You cannot specify multiple path group IDs for a single copy group.
To change the storage location of the configuration definition file: 1. Execute the hbsasrv command to stop the Device Manager agent service. 2. Execute a RAID Manager command to stop all HORCM instances that were manually started by users. 3. Change the storage location of the configuration definition file. 4. Specify the new storage location that was changed in step 3 in the server.agent.rm.horcmSource property of the server.properties file of the Device Manager agent. 5.
- When you copy the RAID Manager configuration definition file that the Device Manager agent is already managing, and then create a new RAID Manager configuration definition file, delete this comment. When deleting copy pairs: When you delete copy pairs from a management client, if all the definitions of the copy pairs in a configuration definition file are deleted, that configuration definition file will also be deleted.
Using the Device Manager agent
11 HP XP7 Command View Advanced Edition audit logs This chapter describes the settings that are necessary for collecting audit log data for Device Manager and Tiered Storage Manager, and the information that you can check in the audit log data. Generating audit log files In the HP XP7 Command View Advanced Edition products, user operations can be recorded in audit logs to retain proof for auditors and evaluators of compliance with regulations, security evaluation standards, and other business standards.
Categories Description Events indicating that a device, administrator, or end user succeeded or failed in connection or authentication: • Fibre Channel login Authentication • Device authentication (Fibre Channel - Security Protocol 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
• 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 80 to Table 84 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 HP XP7 Command View Advanced Edition 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 hcmds64backups command
Type description Authentication data input/output Audit event Severity Message ID Successful data output using the hcmds64authmove command 6 KAPM05832-I Failed data output using the hcmds64authmove command 3 KAPM05833-E Successful data input using the hcmds64authmove command 6 KAPM05834-I Failed data input using the hcmds64authmove command 3 KAPM05835-E KAIC51000-I Request reception (normal) 6 KAIC51200-I KAIC51201-I Request reception (common/abnormal) Device Manager server processing 3
Type description Acquisition of migration group information#3 Acquisition of storage system information#3 Acquisition of task information#3 Acquisition of storage tier information#3 Acquisition of pool information#3 244 Audit event Severity Message ID Failed acquisition of storage domain information 4 KATS90001-W Successful acquisition of all storage domain summary information 6 KATS90000-I Failed acquisition of all storage domain summary information 4 KATS90001-W Successful acquisition o
Type description Audit event Severity Message ID Acquisition of keystore file information#3 Successful acquisition of keystore file information 6 KATS90000-I Failed acquisition of keystore file information 4 KATS90001-W Successful acquisition of volume information 6 KATS90000-I Failed acquisition of volume information 4 KATS90001-W Successful acquisition of the number of volumes returned from a search 6 KATS90000-I Failed acquisition of the number of volumes returned from a search 4 KA
Type description Task operations#3 Storage tier operations#3 Audit event Severity Message ID Successful task cancellation 6 KATS90000-I Failed task cancellation 4 KATS90001-W Successful task status change 6 KATS90000-I Failed task status change 4 KATS90001-W Successful registration of a migration task 6 KATS90000-I Failed registration of a migration task 4 KATS90001-W Successful task registration 6 KATS90000-I Failed task registration 4 KATS90001-W Successful task deletion 6
Type description Storage tier operation failure Migration group operation failure Task operation failure Audit event Severity Message ID No permission to create a storage tier 4 KATS90010-W No permission to delete a storage tier 4 KATS90010-W No permission to change a storage tier 4 KATS90010-W No permission to create a migration group 4 KATS90010-W No permission to delete a migration group 4 KATS90010-W No permission to change a migration group 4 KATS90010-W No permission to add vo
Type description User authentication on an external authentication server Acquisition of information from an external authentication server Audit event Severity Message ID Failed TLS negotiation with the LDAP directory server 3 KAPM10125-E Successful authentication of the user for an information search on the LDAP directory server 6 KAPM10126-I Failed authentication of the user for an information search on the LDAP directory server 3 KAPM10127-W Successful user authentication on the LDAP dire
• In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\ conf\sec\auditlog.conf • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/Base64/ conf/sec/auditlog.conf The following table shows the items you can set in the auditlog.conf file. Table 85 Items set in auditlog.conf file Item Log.Facility Description Specify (by using a number) the facility to be used when the audit log messages are output to the syslog file. Log.
The table below shows the values that can be set for Log.Facility and the corresponding values specified in the syslog.conf file. Table 86 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, HP does 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.
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 89 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 267.
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 97. Table 94 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 multiple types of task information: 1. Number of tasks NumTK=n, Start TKs 2. Task ID (id) TK[1]=(id-1,type-1) 3. Task type (type) ...
Item Description Output format When changing a task: 1. Task status after the change (status) 0x01020600: Executing a task 0x02030000: Erased 0x02040000: Stopped 0x02050000: Stopping mid-task 2.
Message (Specific application information) Message ID Description If the audit log data contains multiple lines, this message appears immediately following the KATS90000-I message. Outputs the subsequent lines of the KATS90000-I message. KATS90020-I This message occurs when, due to successful access to the resources managed by Tiered Storage Manager, an audit event for the Configuration Access type occurred.
OpId OpName Meaning 20 Create Create 30 Delete Delete 40 Modify Update 50 Add Add 60 Remove Remove 70 Change Change status 80 Execute Execute 90 Refresh Refresh 100 Cancel Cancel Table 97 Meanings of the operation targets (Res) output to the audit log ResId ResName Formal name Meaning 20 SD Storage Domain Storage domain 21 RS Refresh Status Storage refresh status 30 MG Migration Group Migration group 40 ST Storage Tier Storage tier 50 MP Migration Plan Mi
Message details for Device Manager server requests This section describes the output format of message details that are output when the Device Manager server receives a request. The item enclosed by square brackets ([ ]) might not be output.
Output character string Full name Operation 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 LU LogicalUnit Logical unit configuration change LUFormat LogicalUnitFormat Formats of all LDEVs in the logical unit LUN LUN LUN path configuration change LUSE LUSE Expanded LDEV configuration change Msgs Messages Message ObjLabel ObjectLabel LDEV label setting or deletion ObjName ObjectName Name assignment to objects used in Device Manager Port Port Port configuration change PortCtrl PortController Port controller configuration change
Output character string Full name Operation VolShred VolumeShredding Shredding function execution requests or information acquisition VRpu VResourcePartitionUnit Changes to the configuration of the virtual resource group VSA VStorageArray Acquisition of the configuration information of a virtual storage machine VVol VirtualVolume THP/Smart volume setting WWN WorldWideName WWN deletion WWNForHSD WWNForHostStorageDomain Change in the configuration of WWNs belonging to a host group WWNForL
Output character string Operation changerank Changes the tier rank of an external volume. datastore Updates only the information about the data store capacity on the virtualization server. • If the target is Replication Deletes a copy pair. • If the target is ReplicationControllerPair delete Deletes a logical path from an existing RCU. • If the target is VResourcePartitionUnit Delete a virtual LDEV from a virtual resource group. dividebycap Creates multiple volumes of the specified size.
Output character string Operation • If the target is PResourcePartitionUnit Moves the resources of a resource group to another resource group. move • If the target is VResourcePartitionUnit Moves a virtual LDEV to another virtual resource group. • If the target is JournalPool Does not apply the THP/Smart pool name to storage systems. nameSync:false • If the target is ObjectLabel Does not apply the volume label to storage systems.
Output character string Operation • If the target is ObjectName Makes the name of the SMI-S enabled storage system the target. • If the target is StorageArray smi-s Makes only the SMI-S enabled storage system the target. • If the target is URLLink Makes only the URL of the management server for the SMI-S enabled storage system the target. split Splits the pair. suspend Creates a 3DC pair by using Continuous Access Journal.
The following table describes the parameter information output in message details: Table 102 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 103. However, Table 103 might not contain some displayed characters. Format: info='...' Attribute values specified for the element are output.
Output character string ArrV 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) 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 Condition (Limits the results of the Get command by using the Filter elements at the same time) Cond Sequence in which attribute values are output#1 LU type, element identifier of an LDEV, LDEV type, host storage status, alert source, host type, CLPR number of a journal volume, element identifier of a host, journal pool identifier, THP/Smart pool volume ID, volume accessible from the specified WWN or iSCSI name, type of LDEV, object ID of a target storage sy
Output character string ErrList Full name and content Sequence in which attribute values are output#1 ErrorList number of ErrorInfo elements (A list including the ErrorInfo elements) errorCount ExternalDevice ExternalDevice (External volume information) ExternalPathInfo ExtPathI (Access information of the external storage system) -
Output character string Full name and content Sequence in which attribute values are output#1 , name, ipAddress, ipv6Address, hostType, targetName, osType HostInfo HostI (Information about accesses between the LU and host) , type (model) of storage system connected to host#2, serial number of storage system connected to host, display name of HostInfo object, host IP address, host IP address for IPv6, LUN mount point, po
Output character string Full name and content HostStorageDomain HSD (Information about a host group or an iSCSI target) Sequence in which attribute values are output#1 , port ID, domain ID, new host connection mode for host group or iSCSI target, list of new host connection modes, host connection mode options, host group name or iSCSI target name, nickname of host group or iSCSI target, name of the host group or iSCSI target to be operated on, port ID
Output character string Full name and content Sequence in which attribute values are output#1 , name, poolFunction, poolID, threshold, threshold2, threshold2mode, inflowControl, dataOverflowWatch, unitOfPathWatchTime, pathWatchTime, forwardPathWatchTime, useOfCache, speedOfLine, deltaResyncFailure, raidLevel, overProvisioningWarning, overProvisioningLimit, volumeThresholdFlag, tierControl, autoMigration, migrationInterval, monitorStartTime, monitorEndTime, moni
Output character string 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 Msgs ObjLabel Full name and content Sequence in which attribute values are output#1 Messages Wait time (seconds) (Groups the Message elements) timeToWait 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
Output character string Full name and content Path Path (Information about the path between the host and host group ) Sequence in which attribute values are output#1 , name, port ID, domain ID of host group or iSCSI target, name of the host group or iSCSI target to be operated on, SCSI ID, LUN assigned to the path between the host and host group , device number for logical unit identification#4, port ID of the host group or iSCS
Output character string PPort Full name and content Sequence in which attribute values are output#1 PPort port ID (Information about the port of a resource group) Param (Element for specifying the parameter for the method specified by CIMInvoker) Prm PResourcePartitionUnit (Resource group configuration change) PRpu RDArrGrp RepCon name, type, value -- ReplicationConnection MCU-side port na
Output character string Full name and content ReplicationInfo RepI (Information about replication) Sequence in which attribute values are output#1 , name of copy pair used by RAID Manager, type of P-VOL storage system#2, serial number of storage system containing P-VOL, P-VOL device number#4, port number in the HORCM configuration file that manages P-VOL paths, serial number of storage system containing P-VOL in the HORCM c
Output character string SIMI Full name and content Sequence in which attribute values are output#1 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 SelectItem elements were collected) SelectItem SlctItem SmrtFldr (Filtering conditions within SearchCondition) number of records to be skipped from the beginning, number of records to b
Output character string Full name and content SnapshotGroup SsGrp (Information about the snapshot group) Sequence in which attribute values are output#1 , storage system type, serial number, snapshot group ID, snapshot group name, type of operation to be performed on the copy pair#6, consistency group ID , arrayType, serialNumber, groupID, groupName, replicationFunction#6, ctGrp StorageSystemOption SSOpt (Information a
Output character string Full name and content User (Account information of a single user of Device Manager) User Sequence in which attribute values are output#1 user ID, password, name of the resource group that is associated with the user, permissions for the resource group that is associated with the user, user name, description loginID, password, groupName, role, fullName, description VirtualDisk (Virtual drive information) VD - VHostStorageDomain (Information about the virtual host storage domain
Output character string VolShred Full name and content Sequence in which attribute values are output#1 VolumeShredding shredding owner ID (Information about the shredding function) ownerID VPort VPort (Virtual port information) VResourcePartitionUnit VRpu (Information about the virtual resource group) VStorageArray VSA (Configuration information of the virtual storage machine) WritingPattern WritingPattern (Writing pattern information for a single writing) --
For HP XP7, P9500 and XP24000/XP20000 storage systems, a numerical value that is a combination of the LDKC, CU, and LDEV numbers (LDKC x 65536 + CU x 256 + LDEV) is output. For XP1024/XP128, and XP12000/XP10000/SVS200, a numerical value that combines the CU and LDEV numbers (= CU x 256 + LDEV) is output. #5: The virtual volume is created from the Smart pool (associated with Smart pool).
2. To determine the CLI command used, compare the details of the output audit log data with the contents of Table 106 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 Y in the key column.
CLI command CreateStorageDomain OpName ResName Additional information#2 -- Get TK TK Y Create SD SD, SS -- -- Get SD SD -- Y Create ST SD, ST -- Y Create TK TK, SD, MG, NumVL, VLs TK=(id,3,...
CLI command GetMigrationGroups GetPools #1 Key #2 OpName #2 ResName Note Y Get FS SS, NumFS Only acquires the number of storage systems specified in the subsystemname parameter Y Get MG SD, NumMG, [MGs] -- -- Get_num PO NumPO -- -- Get SD SD -- Y Get PO SD, NumPO -- Y Get SD NumSD, [SDs] -- -- Get RS NumSD, SDs -- Y Get ST SD, NumST, [STs] -- -- Get SD SD -- Y Get TK {TK | NumTK} -- -- Get_num VL NumVL -- GetStorageDomains GetStorageTiers Ge
CLI command OpName ResName Additional information#2 Y Modify ST SD, ST -- -- Get TK TK -- Y Modify TK TK -- Key #1 #2 #2 Note ModifyTask -- Get_summary SD NumSD Y Refresh SD SD -- -- Get_summary SD SD -- -- Get MG SD, MG -- -- Get VL SD, NumVL -- Y Remove VL SD, MG, VL -- Refresh RemoveVolumeFromMigrationGroup StopTask Y Change TK Legend: Y: Main key --: Not applicable #1 Indicates key audit log data for determining the command.
12 Troubleshooting This chapter describes how to resolve problems that occur during Device Manager and Tiered Storage Manager operation, and how to collect maintenance information. 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.
Countermeasure Edit the registry to change the area of the desktop heap.
Countermeasure If Device Manager or Common Component has not started: Start Device Manager and Common Component. If the user who attempted the operation does not have administrator permissions: Perform the operation again as a user who has administrator permissions for the OS. If the property file is invalid: Revise the property file in accordance with the command logs or the message logs.
3. If a migration task that is being executed has failed, refresh the storage system again. After that, take action as described below according to the task status. If the task status is DATA ERASURE FAILURE: The migration is complete, and the LDEV numbers of the migration source and destination have been reversed. Check the status of the source volume that has the destination volume LDEV number, and then take the appropriate action depending on the status.
Countermeasure Restore a backed up database. Related topics: • Restoring databases, page 175 How to troubleshoot problems on a host This section describes how to troubleshoot problems that occur due to Device Manager agent. The HiScan command cannot add host information to the Device Manager server If the HiScan command fails to add host information to the Device Manager server and causes an error message to be output, take the action appropriate for the cause.
Countermeasure Wait a few minutes, and then retry the operation. Two copies of HBase Agent are displayed in the Programs and Features window In a Windows environment, two instances of HBase Agent are sometimes displayed in the Programs and Features windows on machines where the Device Manager agent or Hitachi Dynamic Link Manager is installed. If two instances of HBase Agent are displayed, execute the hbsa_util command to delete the registry entries and files for the Device Manager agent.
Cause • This problem might occur if a host recognizes 100 or more LUs that are managed by Device Manager. • This problem might occur due to high load on the Device Manager server. If so, the following error message will have been output to the log file specified by the -t option of the HiScan command or to the HiScan.
Countermeasure To check the correspondence between the file system and LUN, use VxVM version 4.0 or later. Changes to the storage system configuration are not applied to the Device Manager server If changes to the storage system configuration are not applied to the Device Manager server, use the hldutil command or the HiScan command to apply the latest information to the Device Manager server.
• The rpm -V command executed in a Linux environment fails. Maintenance information that must be collected if a failure occurs If you cannot identify the cause of a failure or recover from a failure, collect the maintenance information, and then contact our support center.
Operations to complete in advance Log in as a user with Administrator permissions (for Windows) or as a root user (for Linux). Command format In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\Base64\bin\cvxpae64getlogs /dir folder-name [/types HP-XP7-CommandView-Advanced-Edition-product-name[ HP-XP7-Command-View-Advanced-Edition-product-name ...]] [/arc archive-file-name] [/logtypes log-filetype[ log-file-type ...
Product Value Other products Refer to the manual for each product. When specifying this option, also specify the log file type log for the logtypes option. If this option is not specified, the maintenance information for all HP XP7 Command View Advanced Edition products installed on the same management server is collected. arc Specify the name of the archive files to be created. If you do not specify this option, the default file name is cvxpae_logs_64.
In Linux: installation-directory-for-Host-Data-Collector/HDC/Base/bin/ hdc_getras.sh -o directory-name [-f] • o Use the absolute path or a relative path from the current directory to specify the output destination for the maintenance information.
You can specify any printable ASCII character other than the following special characters: \ / : , ; * ? " < > | $ % & ' ` ^ However, you can specify backslashes (\), colons (:), and forward slashes (/) in Windows, or forward slashes (/) in UNIX as a path delimiter. • f Use this option to forcibly overwrite the directory if the directory specified by the o option already exists.
Specify this option to forcibly overwrite the directory specified by the -outdir option if the specified directory already exists. -d Specify the following abbreviations for add-on modules whose error information you wish to remove from the acquisition target: hrpmap: Replication Manager Application agent If the name of the add-on module is omitted, the error information for the Replication Manager Application agent is not acquired.
The javacorexxx.xxxx.txt file is output when using JDK bundled with HP XP7 Command View Advanced Edition, or the DeviceManagerWebService.log file is output when using Oracle JDK, to the following folder: installation-folder-for-Common-Component\uCPSB\CC\web\containers\ DeviceManagerWebService If you are using the Oracle JDK, the DeviceManagerWebService.log file is overwritten each time it is output. HP recommends saving the file by using a different name after the file is output.
To acquire a thread dump of HCS Device Manager Web Service: 1. Execute the following command: # kill -3 PID PID is a process ID written in the installation-directory-for-Common-Component/ uCPSB/CC/web/containers/DeviceManagerWebService/logs/cjstdout.log file. Multiple process IDs are written to the cjstdout.log file. Specify the last process ID written to the file. 2. Stop the HP XP7 Command View Advanced Edition product services. 3. Start the HP XP7 Command View Advanced Edition product services.
13 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This guide follows the conventions shown in Table 108 to refer to HP XP7 products.
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • RAID Manager RAID Manager • RAID Manager XP • XP RAID Manager • XP7 RAID Manager This abbreviation is used when it is not necessary to distinguish the following products: • P9000 Snapshot Snapshot • Snapshot • Snapshot XP • XP Snapshot Administrator Guide (Web Version) 313
Support and other resources
A Device Manager server properties This section describes the property files of a Device Manager server. Device Manager server property files Device Manager server property files include property files related to Device Manager configuration information and the Device Manager database. The following table describes the contents of property files of a Device Manager server.
Property file Description hppa.properties file This property file is related to the connection to Performance Advisor. • jserver.properties file • cimxmlcpa.properties file This property file is related to the CIM/WBEM functions. • cimxmlscpa.properties file CAUTION: • For ordinary use, you do not need to change the values set in the property files of a Device Manager server. Use extreme caution when you are modifying the values, because you can cause the server to fail or to function incorrectly.
• The backslash (\) is reserved as an escape character. Since absolute path names in Windows include backslashes, you must add an escape character before every backslash in a Windows path name. For example, the path name of the file C:\CVXPAE\docroot\foo.bar should be entered as C:\\CVXPAE\\docroot\\foo.bar. When you specify properties, there is no need to precede other characters with the escape character \.
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. Do not specify the host name. • In a cluster environment, the IP address of the cluster manager should be specified.
between 1024 and 49151 for a specialized (middleware) HTTP server. Make sure that it has a different value than the port designated for the HTTP listener.
server.base.home This property contains the installation directory of Common Component, which is 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 server.horcmconfigfile.hostname Specify whether to use the IP address (ipaddress) or the host name (hostname) when Device Manager edits the configuration definition file.
server.cim.support Specify whether CIM support is enabled. If you want to execute CIM, you must set this property to true. Default: true server.cim.support.job Specify whether a method for creating or deleting a volume, setting or releasing a LUN path, setting or canceling security for a LUN, or creating or deleting a LUSE volume is executed asynchronously or synchronously. If you set this property to true, the method is executed asynchronously.
Related topics • server.cim.support.protocol, page 321 • HTTPPort, page 351 server.cim.https.port Specify the port for SSL transmission, for the CIM function. Default: 5989 CAUTION: If you change the value of this property, also change the HTTPSPort property of the Device Manager server to the same value. Related topics • server.cim.support.protocol, page 321 • HTTPSPort, page 351 server.cim.request.queue.
If you specify true for this property, the database is automatically refreshed immediately after the configuration change. If you specify false, it is not automatically refreshed. This property is valid for XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128. Default: true server.logicalview.initialsynchro Specify whether to forcibly synchronize the storage system information in the database with the information displayed in the GUI or CIM/WBEM functions when Device Manager server is started.
CAUTION: If you set this property, specify true for the server.mail.enabled.storagesystem property. Related topics • server.mail.enabled.storagesystem, page 323 server.mail.smtp.port Specify the port number of the SMTP server. To send alerts and events to users by email, you must specify this property. Specifiable range: 0 to 65535. Default: 25 server.mail.smtp.auth Specify whether to use SMTP authentication to send alerts and events to users by email.
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. Alerts are reported from both SNMP traps and Device Manager even if these alerts refer to the same error information. Default: Trap server.mail.alert.
This property is valid only for HP XP7 or 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. Specify false to update all storage system resource information in the database regardless of whether the configuration has changed. Default: true server.agent.differentialrefresh.periodical.
The specifiable values are from 0 to 100. Under normal conditions, you do not need to change the default value of this property. Default: 18 dbm.startingCheck.retryPeriod Specify the interval (in seconds) that the Device Manager server (at startup) retries checking of whether the DBMS has started. The specifiable values are from 0 to 60 (seconds). Under normal conditions, you do not need to change the default value of this property. Default: 10 (seconds) Device Manager log output properties (logger.
Default: 10 Related topics • logger.MaxFileSize, page 328 logger.MaxFileSize Specify the maximum size for the access.log, cim_access.log, error.log, service.log, stdout.log, stderr.log, statuscheck.log, trace.log, CIMOMTrace.log, and SMISClientTrace.log. If the maximum size is exceeded, a new log file is created. Unless KB is specified for kilobytes or MB for megabytes, the specified size is interpreted to mean bytes. Specifiable range: from 512 KB to 32 MB Default: 1 MB logger.hbase.
Default: 10 Related topics • logger.hbase.MaxFileSize, page 329 logger.hbase.MaxFileSize Specify the maximum size of each operation (trace) log file and error log file that is written by Common Component. The log files are HDvMtracen.log, HDvMGuiTracen.log, and HDvMGuiMessagen.log (the n in the file name indicates the backup generation number of the file). The specified size is assumed to be in bytes unless you specify KB for kilobytes, MB for megabytes or GB for gigabytes.
server.dispatcher.daemon.pollingPeriod Specify 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 pollings. Default: 5 (minutes) server.dispatcher.traps.purgePeriod Specify the purging interval for stale SNMP traps or alerts (in minutes). A value of 0 will disable the purging of traps from the server. Default: 5 (minutes) server.dispatcher.daemon.
CAUTION: • If the GUI displays a warning message, manually refresh the corresponding storage system information. You can also specify the settings so that information in the database is automatically updated in case a user forgets to perform a manual refresh after changing the storage system configuration. To do so, set up the following properties: server.dispatcher.daemon.autoSynchro.doRefresh property server.dispatcher.daemon.autoSynchro.
CAUTION: If you specify true, only the information about the HP XP7, P9500 or XP24000/XP20000 is updated in the database. The information in the configuration file of a host that recognizes the command device of HP XP7, P9500 or XP24000/XP20000 is not updated in the database. Related topics • server.dispatcher.daemon.autoSynchro.type, page 332 server.dispatcher.daemon.autoSynchro.
server.dispatcher.daemon.autoSynchro.startTime Specify the time at which storage system information is automatically refreshed (updated) in the database starts in the format hh:mm. Specify a value from 00 to 23 for hh, and 00 to 59 for mm. This property is enabled only if the server.dispatcher.daemon.autoSynchro.type property is set to D or W. In addition, storage system information is automatically refreshed (updated) according to the time zone setting for the management server.
• A • • • • change in the maximum reservation amount of the following volumes: THP pool Smart pool Data pool of Snapshot Data pool of Fast Snap • A change in the monitoring mode for the Smart pool • A change in the settings regarding performance monitoring and hierarchical relocation of the Smart pool • A change in the settings regarding tiering policy for the Smart volume. The Smart volume is a virtual volume created from the Smart pool (associated with the Smart pool).
Default:00:10 Related topics • server.dispatcher.daemon.autoSynchro.performance.doRefresh, page 334 server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh Specify whether to automatically update logical group information when any of the operations below occur. If this property is set to true, logical group information is automatically updated each time one of the events below occurs.
Device Manager client properties (client.properties file) The client.properties file contains the client properties. • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\DeviceManager\Server\config\client.properties • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ DeviceManager/Server/config/client.properties This property file contains the settings related to display and operation of Device Manager GUI. client.rmi.
Device Manager SNMP trap log output properties (customizedsnmptrap.properties file) The customizedsnmptrap.properties file contains the SNMP trap log output properties. • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\DeviceManager\Server\config\customizedsnmptrap.properties • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ DeviceManager/Server/config/customizedsnmptrap.properties customizedsnmptrap.
customizedsnmptrap.customizelist = \ enterprise-ID-1:generic-trap-number-1:specific-trap-number-1: severity-1:content-to-be-output-1, \ enterprise-ID-2:generic-trap-number-2:specific-trap-number-2: severity-2:content-to-be-output-2, \ ... enterprise-ID-n:generic-trap-number-n:specific-trap-number-n: severity-n:content-to-be-output-n Table 110 Items specified in the customizedsnmptrap.customizelist property Item Format Remarks enterpriseID Specify by using dots (for example, .1.3.6.1.4.116.3.11.1.
The following shows an example of specifying the customizedsnmptrap.customizelist property: customizedsnmptrap.customizelist = \ .1.2.3:6:1:Information:$a$e$g$s$1$2, \ .1.3.6.1.4.1.2854:6:1:Warning:$e$a$s$3$2$1$g, \ .1.3.6.1.4.1.116.3.11.4.1.1:6:1:Error:$a$s, \ .1.3.6.1.4.1.116.3.11.4.1.1:6:100:Information:$a$s Default: None 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.
launchapp.elementmanager.usehostname Specify whether a host name is to be displayed in the Remote Web Console URL when you are using Remote Web Console from the Device Manager GUI to connect to an enterprise-class storage system. If you specify true, when you register a storage system in Device Manager by specifying a host name, the host name is displayed in the Remote Web Console URL. If you specify false, an IP address is displayed in the Remote Web Console URL.
installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ DeviceManager/Server/config/hostdatacollectors.properties hdc.request.timeout Specify the timeout value for request processing from the Device Manager server to Host Data Collector (in milliseconds). You can specify a value from 1000 to 86400000. If the Device Manager server communicates with multiple Host Data Collectors, the timeout value will be applied to communication with all the Host Data Collectors. Default: 1800000 hdc.
hdc.rmiserver Specify the IP address or host name of the computer where Host Data Collector is installed and the port number of the RMI server in the following format: IP-address-or-host-name:[port-number],IP-address-or-host-name:[port-number],... For the IP address, you can use either an IPv4 address or IPv6 address. If you use an IPv6 address, you must enclose the IP address with square brackets ([ and ]). The port number must match the value specified for the property hdc.common.rmi.serverPort or hdc.
If there are multiple computers with Host Data Collector installed, you must specify the Host Data Collector information for all the computers. Default: If the management server OS is a prerequisite OS for Host Data Collector: 127.0.0.1:22100 If the management server OS is not a prerequisite OS for Host Data Collector: None CAUTION: The IP address or host name of the computer where Host Data Collector is installed must be the same for the properties hdc.rmiregistry, hdc.rmiserver, and hdc.classloader.
Storage systems refresh themselves after a migration on them finishes. Specify this value to make sure that a migration pair is not split on a storage system while that storage system is refreshing. You can specify a value from 0 to 1,440. Default: 3 migration.remainTimeForDeletePairInMinute Specify during a migration of multiple volumes, the number of minutes to wait after an individual migration finishes until the storage system splits that migration pair.
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.
• day: Collects and summarizes performance information on a daily basis. • week: Collects and summarizes performance information on a weekly basis. In Performance Advisor, a week is from Monday to Sunday. • month: Collects and summarizes performance information on a monthly basis. In Performance Advisor, a month is from the first day to the last day of the month. The information displayed is the performance information from when summarization was last completed.
server.dispatcher.daemon.replication.config.doUpdate Specify whether to periodically collect configuration information for primary site and secondary site storage systems, copy groups, copy pairs, and pair management servers. If you specify true, configuration information is periodically collected. By default, configuration information is collected every day at 2:00.
If you specify 8 or 12 for the server.dispatcher.daemon.replication.config.updateInterval property, configuration information is collected multiple times a day, so you must specify the first collection start time of the day. For example, if you specify 3 for this property, configuration information is collected as follows: • If you specified 8 for the server.dispatcher.daemon.replication.config.updateInterval property: Information is collected every day, at 3:00, 11:00, and 19:00.
server.dispatcher.daemon.replication.performance.pa.updateInterval Specify a time period for the interval at which to collect performance information from Performance Advisor, such as the ratios of storage system processor usage or data in storage system cache memory that is waiting to be written. You can specify the values 4, 8, 12, or 24 (hours). Default: 4 (hours) server.dispatcher.daemon.replication.performance.pa.
Default: 5 (minutes) dvm.replication.disabled Specify whether to hide the Replication tab. To hide the Replication tab, specify true. To display the tab, specify false. Default: true Properties for connecting to Replication Manager (rpmlib.properties file) The rpmlib.properties file contains properties for connecting to Replication Manager. • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\DeviceManager\Server\config\rpmlib.
• In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\DeviceManager\Server\wsi\server\jserver\bin • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ DeviceManager/Server/wsi/server/jserver/bin com.wbemsolutions.jserver.bindto Specify the IP address to be registered in the SLP, when multiple IP addresses are assigned to one management server. IP addresses that can be accessed from a CIM client must be specified. Specify this property in the jserver.
CAUTION: • Be sure to also specify the Ciphers property in the cimxmlscpa.properties file. • If you change the value of this property, you must also change the values of the Device Manager server server.cim.https.port property to the same value. • The cimxmlscpa.properties file is deleted when the service for the Device Manager server starts. Create a new cimxmlscpa.properties file every time the port is changed. Related topics • server.cim.https.
B Tiered Storage Manager server properties This section describes the property files of the Tiered Storage Manager server. Tiered Storage Manager server property files There is a Tiered Storage Manager server property file for Tiered Storage Manager server operations and another property file for accessing the Device Manager server. These property files apply only to operations (processes) from the Tiered Storage Manager CLI. The following table lists the Tiered Storage Manager server property files.
2. Use a text editor to set appropriate values in the Tiered Storage Manager server property files. 3. Start the services of HP XP7 Command View Advanced Edition product. TIP: To reset the Tiered Storage Manager server properties to the default values, use the template stored in the following location.
installation-folder-for-HP-XP7-Command-View-Advanced-Edition\TieredStorageManager\conf\server.properties • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ TieredStorageManager/conf/server.properties server.rmi.port For configurations not using SSL communication, specify the RMI port number used by Tiered Storage Manager to accept processing requests. The range of specifiable values is from 1 to 65535. This property takes effect when 1 is specified for the server.rmi.
server.mail.smtp.host Specify the host name or IP address of the SMTP server to access when sending an event notification email. When entering an IPv6 address, enclose it with [ and ]. Default: None server.mail.from Specify the email address of the sender of event notification emails. Depending on the operating environment, users might not receive email from an address that does not include a domain name. In this case, change the value of this property or the SMTP server environment settings.
server.eventNotification.mail.to Specify the send destination address for an event notification email. Notification emails for all events are sent to the email address specified in this property. Default: None server.eventMonitoringIntervalInMinute Specify the monitoring interval in minutes for checking whether the volume lock period or the specified time limit for volume locks has passed. The range of specifiable values is from 1 to 35,791. Default: 720 server.migration.
The Migration wizard starts with the Erase remaining data on source volumes. check box cleared in the initial display. Also, if the erasedata parameter of the CreateMigrationTask command is omitted, the command is executed assuming that No is specified. To prevent data leaks, HP recommends that you delete the data on migration source volumes after migration. Default: false server.migrationPlan.
server.migration.waitForPairDeleteInMinute Specify the number of minutes to wait after a migration finishes until a storage system will split a migration pair. Storage systems refresh themselves after a migration on them finishes. Specify this value to make sure that a migration pair is not split on a storage system while that storage system is refreshing. You can specify a value from 0 to 1,440. Default: 3 server.migration.
Tiered Storage Manager properties for accessing Device Manager server (devicemanager.properties file) The devicemanager.properties file contains properties related to access to the Device Manager server. • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\TieredStorageManager\conf\devicemanager.properties • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ TieredStorageManager/conf/devicemanager.properties hdvm.
Related topics • server.rmi.port, page 319 Tiered Storage Manager log output properties (logger.properties file) The logger.properties file contains properties related to log output. • In Windows: installation-folder-for-HP-XP7-Command-View-Advanced-Edition\TieredStorageManager\conf\logger.properties • In Linux: installation-directory-for-HP-XP7-Command-View-Advanced-Edition/ TieredStorageManager/conf/logger.
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 the GUI. 20 Information has been produced about the processing for an operation. Information logger.tracelogLevel Specify an output level for the log data that is output to theHTSMServerTracen.log file and the HTSMGuiTracen.log file.
logger.serverMessageFileCount Specify the maximum number of backups of the HTSMServerMessagen.log file. The range of specifiable values is from 2 to 16. When a log file reaches the maximum size specified in the logger.serverMessageMaxFileSize property, the file is renamed by adding a counter to the file name (for example, HTSMServerMessage2.log). The log files are used and written to in the order of the counter.
Related topics • logger.guiMessageMaxFileSize, page 364 logger.guiTraceFileCount Specify the maximum number of backups of the HTSMGuiTracen.log file. The range of specifiable values is from 2 to 16. When a log file reaches the maximum size specified in the logger.guiTraceMaxFileSize property, the file is renamed by adding a counter to the file name (for example, HTSMGuiTrace2.log). The log files are used and written to in the order of the counter.
logger.guiTraceMaxFileSize Specify the maximum size of the HTSMGuiTracen.log file. The range of specifiable values is from 32,768 bytes (32 KB) to 2,147,483,647 bytes (2,048 MB). When specifying this property, use KB to represent the size in kilobytes, and MB to represent the size in megabytes. If a unit is not specified, it is assumed that the value is specified in bytes.
Tiered Storage Manager server properties
C Host Data Collector properties This section describes the Host Data Collector property file. Host Data Collector property files The Host Data Collector property files include a property file related to Host Data Collector operation and a property file related to log output. The following table describes the Host Data Collector property files . Table 114 Host Data Collector property files Property file Description hdcbase.properties file This property file is related to Host Data Collector operation.
Properties related to Host Data Collector operation (hdcbase.properties file) The hdcbase.properties file contains properties related to Host Data Collector operation. • In Windows: installation-folder-for-Host-Data-Collector\HDC\Base\config\hdcbase.properties • In Linux: installation-directory-for-Host-Data-Collector/HDC/Base/config/hdcbase.properties hdc.service.
NOTE: If you changed the value of this property, the following settings must be performed: • Use the firewall_setup command to reset the firewall exemptions (when the value of the hdc.ssl.secure property is 1 or 2). • Set the same value as the hdc.rmiregistry property of the Device Manager server (when non-SSL communication is used by Host Data Collector and the Device Manager server). Related topics • Registering an exception for the Host Data Collector service (for non-SSL communication), page 84 • hdc.
NOTE: If you changed the value of this property, the following settings must be performed: • Use the firewall_setup command to reset the firewall exemptions (when the value of the hdc.ssl.secure property is 1 or 2). • Set the same value as the hdc.classloader property of the Device Manager server (when non-SSL communication is used by Host Data Collector and the Device Manager server). Related topics • Registering an exception for the Host Data Collector service (for non-SSL communication), page 84 • hdc.
NOTE: If you changed the value of this property, the following settings must be performed: • Use the netsh command to reset the firewall exemptions (when the value of the hdc.ssl.secure property is 2 or 3). • Set the same value as the hdc.rmiserver property of the Device Manager server (when SSL communication is used by Host Data Collector and the Device Manager server). Related topics • Registering an exception for the Host Data Collector service (for SSL communication), page 85 • hdc.
Default: None# #: If you do not specify an IP address, the IP address acquired by Host Data Collector will be used. Related topics: • hdc.rmiregistry, page 341 • hdc.rmiserver, page 342 • hdc.classloader, page 342 hdc.service.fileCleanup.startTime Specify the time at which host information files that Host Data Collector collected from managed hosts are deleted, in the format hhmm. Specify a value from 00 to 23 for hh, and 00 to 59 for mm. Default: 2300 hdc.adapter.esx.
hdc.ssl.secure property value 3 Port numbers to be opened (Default) RMI server 22099/tcp, 22105/tcp Class loader 22100/tcp, 22106/tcp RMI registry 22098/tcp, 22104/tcp RMI server 22105/tcp Class loader 22106/tcp # The non-SSL communication port for the RMI registry (22098/tcp by default) is always open because it is also used for internal communication by Host Data Collector. Default: 1 Related topics • • • • • • hdc.common.rmi.registryPort, page 368 hdc.common.rmi.serverPort, page 369 hdc.
Message type Output level Description INFO 30 information - 40 debug You can specify 0, 10, 30, or 40. Default: 30 logger.trace.maxFileSize Specify the maximum size of the Host Data Collector trace log. The specified size is assumed to be in bytes unless you specify KB for kilobytes, MB for megabytes or GB for gigabytes. Specifiable range: 4096 to 2147483647. Default: 5242880 logger.trace.numOfFiles Specify the maximum number of backup files for the Host Data Collector log.
generated. After the specified number of backup log files is created, each time a new backup file is created, the oldest backup file is deleted. Specifiable range: 2 to 16. Default: 10 Related topics • logger.iotrace.maxFileSize, page 374 Properties related to the Host Data Collector's Java environment (javaconfig.properties file ) The javaconfig.properties file contains properties related to the Java environment of the Host Data Collector.
Host Data Collector properties
D Device Manager agent properties This section describes the property files of a Device Manager agent. Device Manager agent property files There is a Device Manager agent property file for Device Manager agent operations and a property file for settings related to the connection between the Device Manager agent and the Replication Manager server. The following table describes the Device Manager agent property files. Table 117 Device Manager agent property files Property file Description agent.
To change Device Manager agent properties: 1. Execute the hbsasrv command to stop the Device Manager agent service. 2. Use a text editor to set appropriate values in the Device Manager agent property files. 3. Execute the hbsasrv command to start the Device Manager agent service.
Default: false Normally, the values set for these parameters do not need to be changed. To change their values, you need expert knowledge of the Device Manager agent. agent.rm.shutdownWait Specify the wait time when stopping the HORCM instance for monitoring (in seconds). Specify a value from 1 to 60. Default: 5 agent.rm.horcmInstance Specify the instance number of the HORCM file for monitoring. Specify a value from 0 to 4,094.
agent.logger.loglevel Specify the output level of the log file for the Replication Manager agent functionality. Log data that has a level equal to or higher than the specified value is output. Specify one of the following values (listed in ascending order of importance): DEBUG, INFO, WARN, ERROR, FATAL Default: INFO agent.logger.MaxBackupIndex Specify the maximum number of log files for the Replication Manager agent functionality. Specify a value from 1 to 20.
Device Manager agent properties for hldutil command operations (hldutil.properties file) The hldutil.properties file contains properties related to hldutil command operations. • In Windows: installation-folder-for-Device-Manager-agent\util\bin\hldutil.properties • In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/util/bin/hldutil.properties • In AIX: /usr/HDVM/HBaseAgent/util/bin/hldutil.properties agent.util.hpux.
NOTE: The files access.log, error.log, service.log, and trace.log are output to the following locations: In Windows: installation-folder-for-the-Device-Manager-agent\agent\logs\ In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/agent/logs/ In AIX: /usr/HDVM/HBaseAgent/agent/logs/ logger.loglevel Specify the minimum level of log data that the Device Manager agent outputs to the files error.log and trace.log.
logger.MaxFileSize Specify the maximum size of the files access.log, error.log, service.log, and trace.log. If a log file becomes larger than this value, the Device Manager agent creates a new file and writes log data to it. Unless KB is specified for kilobytes or MB for megabytes, the specified size is interpreted to mean bytes. Specify a value from 512 KB to 32 MB. Default: 5 MB The size of an output log file depends on the number of copy pairs managed by Replication Manager.
/opt/HDVM/HBaseAgent/agent/config/server.properties • In AIX: /usr/HDVM/HBaseAgent/agent/config/server.properties server.agent.port Specify the port number for the Device Manager agent's daemon process (or service). Avoid specifying small port numbers because such numbers might conflict with other applications. The normal range is 1024 to 49151. If a version of Hitachi Dynamic Link Manager earlier than 5.8 is installed, specify 23013.
For operation in an IPv6 environment, specify a global address. If you specify a site-local address or link-local address, the IPv4 address will be used. It is necessary to match the IP address version to the one specified in server.http.socket.bindAddress. The IP address that you specified in this property can also be used when creating or editing the RAID Manager configuration definition file.
Related topics • For details on the required memory size for Device Manager: “Settings required for a host to manage 100 or more LUs” on page 204 • For details on the required memory size for Replication Manager:“Managing copy pairs” on page 202 server.agent.shutDownTime Specify the period to shutdown the Device Manager agent's Web server after it receives or sends the last HTTP/XML message (in milliseconds). Specify a value from 1 to 9223372036854775807.
This setting limits the IP addresses permitted for connection, thus preventing denial-of-service attacks or other attacks that intend to overflow buffers. You can use an asterisk (*) as a wildcard character when you use IPv4 addresses. To specify multiple IP addresses, separate them with commas (,). In the following example, the specification permits the address 191.0.0.2 and addresses from 192.168.0.0 to 192.168.255.255 to connect to the Device Manager agent: server.http.security.clientIP=191.0.0.2, 192.
Related topics • server.http.port, page 318 • server.https.port, page 318 server.agent.rm.centralizePairConfiguration Specify whether to manage copy pairs for each host or to centrally manage all copy pairs on a single host. disable Specify this value to manage copy pairs for each host when the system uses the local management method. To use the local management method, you need to install the Device Manager agent and RAID Manager on each host.
The volume pairs excluded from Device Manager operations are also excluded from Replication Manager operations. To specify multiple instance numbers, separate the individual numbers with commas (,). From the Device Manager agent, you cannot operate a RAID Manager whose instance number is specified in this property. Default: None server.agent.rm.
Default: None# #: In a newly created configuration definition file, poll is set to 1000. When a pair is added to an existing configuration definition file or when a configuration definition file is optimized, the existing settings are used. server.agent.rm.temporaryInstance Specify the instance number of the configuration definition file that the Device Manager agent temporarily uses to acquire copy pair information. Specify a value from 0 to 3997.
The following table describes the conditions under which the Device Manager agent decides whether to use the HORCM_DEV or HORCM_LDEV format in the configuration definition file. Table 118 Conditions on which the Device Manager agent decides which format should be used in the configuration definition file Which format is used in the existing configuration definition file Format to be used in the configuration definition file Pair operation If a format is specified in the property: No format is used.
CAUTION: Before you specify HORCM_LDEV, make sure that RAID Manager 01-17-03/04 (or later) has been installed. If you specify HORCM_LDEV when RAID Manager is a version earlier than 01-17-03/04, volume pair creation will fail. If this happens, the following error message will be displayed: An attempt to create a pair has failed. Error detail, host "host-name" : "error-detail" server.agent.rm.userAuthentication Specify whether to check that the authentication mode for command devices is enabled.
#: If you do not specify a path, the path for the following default storage location is used: In Windows: System folder (represented by the environment variable %windir%) In UNIX: /etc directory Related topics • Changing the storage location of the configuration definition file, page 233 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).
server.agent.evtwait.timeout Specify the waiting time until the status becomes pair when a remote pair is restored (in seconds). If the specified time has elapsed, the processing ends with an error. Specify a value from 1 to 1999999. Default:3600 Properties for command devices connected to Device Manager agent (rgcmddev.properties file) If the storage system is HP XP7 or P9500, and resources in the storage system are partitioned, in the rgcmddev.
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
DoS Denial of Services FQDN Fully Qualified Domain Name FTP File Transfer Protocol GUI Graphical User Interface HBA Host Bus Adapter HTTP HyperText Transfer Protocol HTTPS HyperText Transfer Protocol Secure I/O Input/Output ID IDentifier IETF Internet Engineering Task Force IOPS Input Output Per Second IP Internet Protocol IPF Itanium Processor Family IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 iSCSI Internet Small Computer System Interface JAR Java ARc
NIC Network Interface Card NPIV N Port ID Virtualization NTP Network Time Protocol OS Operating System P-VOL Primary VOLume PAP Password Authentication Protocol PDEV Physical Device PEM Privacy Enhanced Mail PID Process ID PP Program Product RADIUS Remote Authentication Dial-In User Service RAID Redundant Array of Independent Disks RCU Remote Control Unit RDN Relative Distinguished Name RFC Request For Comments RMI Remote Method Invocation S-VOL Secondary VOLume SAN Storag
SSH Secure SHell SSID Storage Subsystem ID SSL Secure Sockets Layer SSO Single Sign - On SVP Service Processor TCP Transmission Control Protocol TLS Transport Layer Security UDP User Datagram Protocol URL Uniform Resource Locator V-VOL Virtual VOLume WAN Wide Area Network WBEM Web - Based Enterprise Management WWN Worldwide name XML eXtensible Markup Language 398 Acronyms and abbreviations
Index A account.lock.num, 98 acquiring maintenance information on management server, 303 adding SVP to trusted zone, 115 agent.logger.loglevel, 380 agent.logger.MaxBackupIndex, 380 agent.logger.MaxFileSize, 380 agent.properties file, 378 agent.rm.everytimeShutdown, 378 agent.rm.horcmInstance, 379 agent.rm.horcmService, 379 agent.rm.shutdownWait, 379 agent.rm.TimeOut, 378 agent.util.hpux.
copy pairs central management method, 43 local management method, 43 managing (Device Manager agent), 202 system requirements, 42 virtual command device server method, 43 customizedsnmptrap.customizedSNMPTrapEnable, 337 customizedsnmptrap.customizelist, 337 customizedsnmptrap.properties, 337 cvxpae64getlogs command, 303 D database backing up, 171 exporting, 186 importing, 188 migrating, 184 restoring, 175 database.properties file, 326, 359 dbm.startingCheck.retryCount, 326 dbm.startingCheck.
hdc.request.timeout, 341 hdc.rmiregistry, 341 hdc.rmiserver, 342 hdc.service.fileCleanup.startTime, 372 hdc.service.localport, 368 hdc.service.rmi.registryIPAddress, 371 hdc.ssl.secure, 372 hdc.usessl, 343 hdcbase.properties file, 368 hdvm.port, 360 hdvm.protocol, 360 hdvm.rmi.port, 360 hdvm.
logger.hbase.sysloglevel, 328 logger.iotrace.maxFileSize, 374 logger.iotrace.numOfFiles, 374 logger.loglevel, 327, 382 logger.MaxBackupIndex, 327, 382 logger.MaxFileSize, 328, 383 logger.messagelogLevel, 361 logger.properties, 327, 373 logger.properties file, 361, 381 logger.serverMessageFileCount, 363 logger.serverMessageMaxFileSize, 364 logger.serverTraceFileCount, 363 logger.serverTraceMaxFileSize, 364 logger.syslogLevel, 362 logger.trace.level, 373 logger.trace.maxFileSize, 374 logger.trace.
prerequisites normal host (Device Manager agent), 32 normal host (Host Data Collector), 30 virtual machine (Device Manager agent), 35 virtual machine (Host Data Collector), 32 virtualization server, 39 programproductinfo.properties file, 383 properties changing (Host Data Collector), 367 Device Manager server, changing, 316 properties (Device Manager agent) changing, 377 properties (Tiered Storage Manager server) changing, 353 property files agent.properties, 378 client.properties, 336 customizedsnmptrap.
server.cim.support.job, 321 server.cim.support.protocol, 321 server.configchange.enabled, 322 server.dispatcher.daemon.autoSynchro.dayOfWeek, 332 server.dispatcher.daemon.autoSynchro.doRefresh, 331 server.dispatcher.daemon.autoSynchro.interval, 333 server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh, 335 server.dispatcher.daemon.autoSynchro.performance.doRefresh, 334 server.dispatcher.daemon.autoSynchro.performance.startTime, 334 server.dispatcher.daemon.autoSynchro.startTime, 333 server.dispatcher.
storage location configuration definition file, changing, 233 storage system, 22 acquiring performance information (by using CIM/WBEM functions), 153 copy pair, 43 requirements for managing copy pairs, 58 storage systems ports, 68 SVP, 23 SVP, adding to trusted sites, 115 System account automatically lock, 98 system configuration, 21 central management method, 48 for acquiring performance information, 154 local management method, 45 managing copy pairs, 43 SVP configuration, 53, 55 virtual command device se
