-
HP P9000 Command View Advanced Edition Suite Software Administrator Guide (Web Version) Part number: TB581-96325 Eighth edition: November 2012
-
Legal and notice information © Copyright 2010, 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
-
Contents Preface .............................................................................................. 21 1 System configuration and requirements ............................................... 23 System configuration ................................................................................................................. Hardware configuration ...................................................................................................... Software configuration ......................
-
System configuration for managing copy pairs ....................................................................... System configuration for using the local management method to manage copy pairs ............ System configuration for using the central management method to manage copy pairs ......... System configuration for using a virtual command device server configuration to manage copy pairs ................................................................................................................
-
Deleting the message ........................................................................................................ Communication security mode .................................................................................................. Controlling management client access to the management server .................................................. Changing the password-encoding level in the Device Manager CLI and the Tiered Storage Manager CLI ................................................
-
OpenSLP service .............................................................................................................. Configuring performance information acquisition ........................................................................ Required system configuration for acquiring performance information ...................................... Settings required to acquire performance information of enterprise-class storage systems ............
-
Exporting databases in a non-cluster configuration ......................................................... Exporting databases in a cluster configuration ............................................................... Importing databases into the migration-destination server ...................................................... Importing databases in a non-cluster configuration ......................................................... Importing databases in a cluster configuration .......................
-
javapath_setup command .................................................................................................. 261 TIC command .................................................................................................................. 262 12 Setting up Host Data Collector ....................................................... 265 Installing Host Data Collector ...................................................................................................
-
Message text for Device Manager server processing using CIM ....................................... Message text for Tiered Storage Manager processing ..................................................... Message details for Device Manager server requests ............................................................ Commands in message details .................................................................................... Targets in message details .......................................................
-
dbm.traceSQL .................................................................................................................. dbm.startingCheck.retryCount ............................................................................................ dbm.startingCheck.retryPeriod ............................................................................................ Device Manager log output properties (logger.properties file) ....................................................... logger.loglevel .....
-
Properties for connecting to PA (hppa.properties file) ................................................................... hppa.infoAcquirePeriod ..................................................................................................... hppa.option .................................................................................................................... hppa.CLIClientPath ........................................................................................................... hppa.
-
logger.serverTraceMaxFileSize ........................................................................................... logger.guiMessageMaxFileSize .......................................................................................... logger.guiTraceMaxFileSize ............................................................................................... Tiered Storage Manager security properties ...............................................................................
-
logger.loglevel ................................................................................................................. logger.MaxBackupIndex ................................................................................................... logger.MaxFileSize ........................................................................................................... Device Manager agent properties for program information (programproductinfo.properties file) ........ veritas.volume.manager.
-
Figures 1 Basic system configuration ........................................................................................ 23 2 Most secure configuration: separate management LAN plus firewall .............................. 27 3 Second-most secure configuration: separate management LAN plus firewalled devices ..................................................................................................................
-
23 Configuration example using a server computer that has two NICs ................................ 93 24 CIM components for Device Manager ..................................................................... 154 25 Example of a system configuration in which performance information of a storage system is acquired ...........................................................................................................
-
Tables 1 Maximum number of management resources .............................................................. 30 2 Appropriate memory heap size for Common Component ............................................. 31 3 Appropriate memory heap size for the Device Manager server ..................................... 33 4 Hosts that can be managed by Device Manager ......................................................... 35 5 Host management software supported by Device Manager .................................
-
27 Port number that must be registered as a firewall exception between the Host Data Collector computer and a host ............................................................................................... 87 28 Port numbers that must be registered as firewall exceptions between the management server and an SMI-S provider ...................................................................................
-
58 Setup methods for various management server environments ....................................... 169 59 Settings for registering HiRDB as a resource (for Microsoft Cluster Service) .................... 179 60 Settings for registering the HBase Storage Mgmt Common Service as a resource (for Microsoft Cluster Service) .......................................................................................
-
87 Support status of HORCM_CMD parameter description format ................................... 242 88 Support status of HORCM_DEV parameter description format ..................................... 243 89 Support status of HORCM_LDEV parameter description format .................................... 245 90 Values that cannot be specified for the ip_address of HORCM_INST parameter ............ 246 91 Support status of HORCM_INST parameter description format ....................................
-
120 Items output to the audit log message text (message text, operation type and operation target) ................................................................................................................. 305 121 Items output to the audit log message text (additional information) ............................... 306 122 Messages output to the audit log ............................................................................ 310 123 Meanings of the operation types (OP) output to the audit log ....
-
Preface This manual explains how to configure HP StorageWorks P9000 Command View Advanced Edition (abbreviated hereafter as Device Manager), HP StorageWorks P9000 Tiered Storage Manager (abbreviated hereafter as Tiered Storage Manager), and HP StorageWorks P9000 Command View Advanced Edition Suite Common Component (abbreviated hereafter as Common Component), and also explains how to set up an environment as well as how to troubleshoot management servers.
-
Preface
-
1 System configuration and requirements This chapter describes the system configuration and system requirements for Device Manager and Tiered Storage Manager. System configuration The following figure shows a basic system configuration in which Device Manager and Tiered Storage Manager are used. Figure 1 Basic system configuration A TCP/IP network must be used to connect a management server to management clients, and the management server to storage systems.
-
Management server A management server is a computer that integrates and manages storage systems and host computers. P9000 Command View AE Suite is installed on this computer. The management server supports an active-standby type clustering configuration consisting of two computers. Management client A management client is a computer used to operate Device Manager and Tiered Storage Manager. Host (application server) A host (application server) is a computer that uses the volumes in a storage system.
-
NOTE: Only Host Data Collector can be installed on a separate computer. Device Manager agent The Device Manager agent component collects information about hosts or storage systems that it then reports to the Device Manager server.
-
WARNING! P9500, XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128 have a public LAN and a private LAN. Device Manager uses the public LAN to communicate with the SVP about the array and configuration changes. Do not under any circumstances attach the private LAN to an external network because this can cause serious problems on the array. Common security risks System administrators frequently separate production LANs from management LANs.
-
CAUTION: When a P9500, XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128 storage system is operated from Element Manager, the storage system communicates directly with Java Web Start and the Web browser on the management client. For this reason, if the storage system and the management client are on different networks, you must set up the networks so that the storage system and the management client can communicate directly with each other.
-
CAUTION: When a P9500, XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128 storage system is operated from Element Manager, the storage system communicates directly with Java Web Start and the Web browser on the management client. For this reason, if the storage system and the management client are on different networks, you must set up the networks so that the storage system and the management client can communicate directly with each other.
-
CAUTION: When a P9500, XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128 storage system is operated from Element Manager, the storage system communicates directly with Java Web Start and the Web browser on the management client. For this reason, if the storage system and the management client are on different networks, you must set up the networks so that the storage system and the management client can communicate directly with each other.
-
Figure 5 Least secure configuration: flat network Management server requirements This section describes the system requirements for the management server. 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. We recommend that you operate each product within these limits.
-
Number of paths = number of LDEVs x average number of paths per LDEV Related topics: • Changing Device Manager server properties, page 346 • server.cim.support.job, page 350 Setting the memory heap size of Common Component Use the hcmdschgheap command to set the memory heap size for Common Component. Set a size that is appropriate for the OS of the management server, the number of LDEVs to be managed, and the number of copy pairs to be managed.
-
-- : You cannot specify this memory heap size. # If you manage both open volumes and mainframe volumes, calculate the number of copy pairs by using the following formula: number-of-open-system-copy-pairs x 6 + number-of-mainframe-systemcopy-pairs To set the memory heap size: 1. Stop the P9000 Command View AE Suite product services. 2. In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop.
-
Information to collect in advance • Number of LDEVs to be managed Table 3 Appropriate memory heap size for the Device Manager server Memory heap size OS Managed resource Windows (x86 or IPF) OS other than Windows (x86 or IPF) 256 MB (Min: 128 MB) 512 MB (Min: 128 MB) 1,024 MB (Min: 128 MB) Number of LDEVs per storage system 2,000 or less 2,001 or more -- Number of LDEVs per storage system 2,000 or less 2,001 to 6,000 6,001 or more Legend: --: You cannot specify this memory heap size.
-
Changing the JDK After starting operations, to change the JDK used by P9000 Command View AE Suite products, execute the hcmdschgjdk command. P9000 Command View AE Suite products can be used with the following JDK versions: • • • • JDK 5 Update 03 (1.5.0_03) or later bundled with P9000 Command View AE Suite Oracle JDK 5 (1.5.0) Oracle JDK 6 (1.6.0) Oracle JDK 7 (1.7.0) To change the JDK: 1. Stop the services of P9000 Command View AE Suite products. 2.
-
NOTE: • If you perform an overwrite or upgrade installation of an Oracle JDK during operation of any P9000 Command View AE Suite product, re-register the JDK after the installation. • If you remove an Oracle JDK during operation of any P9000 Command View AE Suite product, make sure that you change to the JDK bundled with P9000 Command View AE Suite. • If the version of the P9000 Command View AE Suite products installed on the management server is 7.0 or earlier, you cannot change to an Oracle JDK.
-
• Prerequisites for virtualization servers, page 46 • Prerequisites for mainframe hosts, page 53 Host management software supported by Device Manager Device Manager centrally manages hosts by collecting information from them via the host management software.
-
NOTE: • Support for VMware ESX 3.x and VMware ESX Server 3.x ended with version 7.3.0. If VMware ESX 3.x or VMware ESX Server 3.x is installed on virtualization servers that are registered in Device Manager, unregister them from the Device Manager GUI or CLI. • Use vMA to manage virtualization servers in an environment in which Plug-in for Virtualization Server Provisioning is used.
-
Prerequisites for normal hosts managed by Host Data Collector (UNIX hosts) To use Host Data Collector to manage normal hosts, you need to specify the environment settings for each normal host to be managed. The environment settings that need be specified on the UNIX host differ according to the UNIX account used to register the host in Device Manager.
-
user-name-used-for-host-registration hosts-to-be-registered =(execution-user-name-alias)NOPASSWD:/tmp/FsDataGatherLauncher.Unix.sh For hosts-to-be-registered, specify the IP address, host name, or ALL. For execution-user-name-alias, specify ALL, or root. NOTE: If a general user account is used to register a host into Device Manager, do not use the root account to register the host a second time.
-
Figure 6 Environment settings on virtual machines (when Host Data Collector is used for management) Host Data Collector comes with P9000 Command View AE Suite, which is installed on the management server, but can also be installed on a computer other than the management server. Before you register virtual machines in Device Manager, the following environment settings must already be specified on the virtual machines: • Communication with virtual machines can be performed via the WMI protocol.
-
Related topics: • Chapter 12, page 265 • Operation workflow for allocating volumes to virtual machines, page 42 • How to register a virtualization server: HP P9000 Command View Advanced Edition Suite Software User Guide or HP P9000 Command View Advanced Edition Suite Software 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.
-
• Register the virtualization server that runs in the same physical environment in Device Manager. You can register virtualization servers in Device Manager from vMA or Host Data Collector. However, when you manage the virtualization servers using vMA, you must register virtual WWNs 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 9 Operation workflow for allocating volumes to virtual machines (when sharing an HBA by multiple virtual machines) 1. Register one of the virtual machines that share an HBA as a normal host in Device Manager. Do not register the virtualization server that runs in the same physical environment in Device Manager. 2.
-
Configuration in which a virtual HBA is allocated for each virtual machine (by using NPIV HBAs) Figure 10 Operation workflow for allocating volumes to virtual machines (when allocating a virtual HBA to each virtual machine) 1. 2. 3. 4. Register the virtualization servers that run the virtual machines whose volume status you want to manage in Device Manager. When you manage the virtualization servers from vMA, register the virtual WWN assigned to each virtual HBA in Device Manager.
-
• How to register a virtualization server: HP P9000 Command View Advanced Edition Suite Software User Guide or HP P9000 Command View Advanced Edition Suite Software CLI Reference Guide • Tasks required to change the virtual machine configuration, page 46 Registering virtual WWNs in Device Manager When using vMA to manage virtualization servers on which NPIV HBAs are used, execute the createnpivinfo command to register the virtual WWN assigned to each virtual machine in Device Manager.
-
• Operation workflow for allocating volumes to virtual machines, page 42 • How to register a virtualization server: HP P9000 Command View Advanced Edition Suite Software User Guide or HP P9000 Command View Advanced Edition Suite Software CLI Reference Guide 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
-
You can use Host Data Collector as a virtualization server management program if the target virtualization servers are VMware ESX 5.x or VMware ESX 4.x. Figure 11 Environment settings on virtualization servers (when Host Data Collector is used for management) • Make sure that you install Host Data Collector on a Windows computer. Host Data Collector comes with P9000 Command View AE Suite, which is installed on the management server, but can also be installed on a computer other than the management server.
-
Figure 12 Environment settings on virtualization servers (when vMA is used for management) • You must deploy vMA on a virtualization server, and then specify the virtualization server or VMware vCenter Server as the monitoring target of vMA. • IPv6 can also be used for communication between the Device Manager server and vMA.
-
Figure 13 System configuration in which vMA monitors VMware ESX that is in the same physical environment Figure 14 System configuration in which vMA monitors VMware ESX that is in a different physical environment To register a virtualization server in Device Manager, you need to specify vMA information such as the IP address and user account. When you specify the vMA information, the physical environment managed by vMA is registered as a virtualization server.
-
NOTE: • If a virtualization server is managed by Device Manager, do not make the virtual machines running on that virtualization server management targets of Device Manager, except when NPIV HBA is used in the configuration. • If you change vMA information such as the IP address and user account, you must re-register the vMA in Device Manager (but you do not need to delete it).
-
NOTE: • If a virtualization server is managed by Device Manager, do not make the virtual machines running on that virtualization server management targets of Device Manager, except when NPIV HBA is used in the configuration.
-
Figure 16 Operation workflow for managing virtualization server Related topics: • Prerequisites for virtualization servers managed by Host Data Collector, page 46 • Prerequisites for virtualization servers managed by vMA, page 47 • Notes on operating virtualization servers, page 52 Notes on operating virtualization servers Note the following when operating virtualization servers: • To check the most recent information about virtualization server volumes, perform either of the following operations from Devi
-
• Prerequisites for virtualization servers managed by vMA, page 47 Prerequisites for mainframe hosts From Device Manager or Tiered Storage Manager linked with P9000 mainframe agent, you can perform the following operations for mainframe volumes: • Checking the usage of mainframe volumes and the logical DKC serial numbers of storage systems (from Device Manager) • Migrating and shredding mainframe volumes (from Tiered Storage Manager) Operation workflow of managing a mainframe host To manage mainframe host
-
The Replication Manager GUI can be displayed from Device Manager GUI. The following table lists the versions of Replication Manager supported by Device Manager.
-
Legend: Y: Supported, N: Not supported Related topics: • System configuration for managing copy pairs, page 55 • Storage system requirements for managing copy pairs, page 66 System configuration for managing copy pairs Device Manager supports the following four types of system configurations to manage copy pairs. • Local management method In this configuration, copy pairs are managed for each host by connecting a command device to each application server via Fibre Channel.
-
CAUTION: A configuration definition file should exist as a prerequisite for managing copy pairs from Device Manager (except for copy pairs defined as a device group). If a copy pair is created by using Remote Web Console, SVP, or RAID Manager LIB, you cannot use Device Manager to operate these pairs because the configuration definition file does not exist.
-
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. • RAID Manager must be installed on hosts as follows: If there are multiple hosts that recognize the P-VOL and multiple hosts that recognize the SVOL, install RAID Manager on one of the hosts that recognize the P-VOL and one of the hosts that recognize the S-VOL.
-
Related topics: • How to install RAID Manager: RAID Manager documentation • Storage system requirements for managing copy pairs, page 66 • Prerequisite version of the Device Manager agent for managing copy pairs , page 68 System configuration for using the central management method to manage copy pairs Set up the management server, pair management server, and storage system so that the prerequisites are satisfied.
-
• The P-VOL and S-VOL must be managed by a single management server (Device Manager server). • The P-VOL and S-VOL must be recognized by the hosts (application servers). We recommend that P-VOL and S-VOL be assigned to separate application servers. • From the P-VOL and S-VOL, LUN security must be set for the host (application server). The pair management server does not need to recognize the P-VOL or S-VOL. Command device conditions: • The management server must recognize a command device.
-
Figure 20 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.
-
System configuration for using an SVP configuration to manage copy pairs (when copy pairs are defined in a configuration definition file) Set up the management server, pair management server, and storage system so that the prerequisites are satisfied.
-
Resource group requirements (when managing partitioned resources in P9500) • The volumes below must be registered in a resource group managed by the user. - P-VOL - S-VOL - All pool volumes that make up a pool (when managing Snapshot or Fast Snap pairs) - All journal volumes that make up a journal (when managing Continuous Access Journal pairs) Note that managing partitioned resources might slow the display for some Replication Manager GUI operations.
-
Figure 22 Example of a system configuration for managing copy pairs (when copy pairs are defined as a device group) Management server conditions: • The following computers must be registered as the Device Manager management resources: - A host that recognizes the P-VOL - A host that recognizes the S-VOL • • • • Device Manager agent version 7.1 or later must be installed on the management server. RAID Manager version 01-25-03/01 or later must be installed on the management server.
-
CAUTION: Do not install Replication Manager Application Agent on the management server. Copy pair (P-VOL and S-VOL) conditions: • The P-VOL and S-VOL must be managed by a single management server (Device Manager server). • 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).
-
Storage system requirements for managing copy pairs Use Element Manager to set up an environment appropriate for the storage system requirements. Table 8 Storage system requirements for managing copy pairs Storage system Function Requirements • Prerequisite software for Continuous Access Journal must be installed and the license must be enabled. • There must be a fibre-channel connection between the two ports used for an MCU-RCU path.
-
Storage system Function Requirements • Prerequisite software for Snapshot must be installed and the license must be enabled. Snapshot • To be used as an S-VOL, a V-VOL (a special LU) must be prepared in advance. Perform the preparations in the following order: • Create a pool. • Create a V-VOL. • Prerequisite software for Fast Snap must be installed and the license must be enabled. Fast Snap • To be used as an S-VOL, a V-VOL (a special LU) must be prepared in advance.
-
Prerequisite version of the Device Manager agent for managing copy pairs The prerequisite version of the Device Manager agent varies depending on the storage system to be managed and the program to be used. When using the GUI to manage copy pairs The prerequisite version of the Device Manager agent varies depending on the target storage system. Table 9 Device Manager agent requirements for managing copy pairs by using the GUI Storage system Device Manager agent version P9500 7.
-
The following table lists the Device Manager agent version required for each storage system model. Table 11 Device Manager agent version required for each storage system model when managing copy pairs by using the CLI Storage system model Device Manager agent version P9500 7.0 or later XP24000 5.7 or later XP20000 5.8 or later XP12000 XP10000 1.
-
• If you want to create a copy pair by using RAID Manager or if RAID Manager is already being used to manage copy pairs, you can use the Device Manager CLI to create a configuration definition file. • You cannot use Device Manager to create copy pairs from configuration definition files created in the Device Manager CLI. • To create copy pairs in RAID Manager from configuration definition files created in the Device Manager CLI, you must change the MU numbers to appropriate values.
-
2 Network configuration This chapter describes the settings for the P9000 Command View AE Suite products that are required in various network configurations. Port settings This section describes the port numbers and firewall settings used by the P9000 Command View AE Suite products. Ports used by P9000 Command View AE Suite products Avoid specifying port numbers used by other programs installed on the same computer for the port numbers used by P9000 Command View AE Suite products.
-
Port number Description 23018/tcp Used internally for Common Component communication (receiving a termination message from the Web server). This port number can be changed. Used internally for Common Component communication (communication with the Web server). 23025/tcp This port number can be changed. Used internally for Common Component communication (receiving a termination message from the Web server). 23026/tcp This port number can be changed.
-
Port number Description Used for communication with a CIM client (service discovery). 427/tcp You cannot change the settings by using Device Manager. If products using these ports are installed on the same computer, change the settings of those products. Used internally for Device Manager server communication, for communication with management clients (via the GUI or the CLI),for communication with storage systems, and for communication with hosts (Device Manager agents).
-
• Registering firewall exceptions , page 81 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 14 Ports used by the Tiered Storage Manager server Port number Description Used for communication with management clients (via the GUI or the CLI). 20352/tcp You can change the port by modifying the server.
-
Port number 22098/tcp 22099/tcp 22100/tcp 22104/tcp 22105/tcp 22106/tcp Description Used for non-SSL communication between the Device Manager server and the RMI registry when Host Data Collector is installed on a Windows computer. You can change the port by using the hdc.common.rmi.registryPort property in the hdcbase.properties file of Host Data Collector. Used for non-SSL communication between the Device Manager server and the RMI server when Host Data Collector is installed on a Windows computer.
-
Ports used by the Device Manager agent For the computer on which the Device Manager agent is installed, ensure that the port numbers specified for use by the Device Manager agent are different from the port numbers used by other programs installed on the same computer. Table 16 Ports used by Device Manager agent Port number Description Used for communication with the Device Manager server. 24041/tcp You can change the port by using the server.agent.port property in the server.
-
Target storage system Port number Description 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. 443/tcp Used for starting Element Manager by SSL from management clients (GUI) . This port number cannot be changed. XP24000 XP20000 1099/tcp Used for communication with the management server or management clients (GUI).
-
Note that port numbers used for storage systems cannot be changed. Changing ports used by Common Component To change the ports used by Common Component after installing the P9000 Command View AE Suite products, you need to edit the settings file for Common Component. To change the ports used by Common Component: 1. Stop the services of P9000 Command View AE Suite products. • In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop.
-
Default port number Settings files Location In Windows: installation-folder-for-Common-Component\conf\hsso.conf hsso.hostport In Linux: installation-directory-for-CommonComponent/conf/hsso.conf In Windows: 23016/tcp installation-folder-for-Common-Component\httpsd\conf\httpsd.conf In Linux: installation-directory-for-CommonComponent/httpsd/conf/httpsd.conf • VirtualHost hostname:port-number • Listen#1 In Windows: installation-folder-for-Common-Component\CC\web\redirector\workers.
-
Default port number Settings files Location In Windows: installation-folder-for-Common-Component\CC\web\containers\DeviceManagerWebService\usrconf\usrconf.properties In Linux: webserver.connector.ajp13.port installation-directory-for-CommonComponent/CC/web/containers/DeviceManagerWebService/usrconf/usrconf.properties In Windows: 23026/tcp installation-folder-for-Common-Component\CC\web\containers\DeviceManagerWebService\usrconf\usrconf.properties In Linux: webserver.shutdown.
-
This port number is used only if the OS of the management server is Windows. NOTE: If you change the port numbers for Common Component, you might have to review the following settings depending on the operating environment: • If management clients (GUI) use Internet Explorer 6 (23015/tcp and 23016/tcp): You need to change the pop-up blocking settings.
-
Port numbers that must be registered as firewall exceptions In an environment with firewalls set up in the network that connects the management server, management clients, and storage systems, you need to register ports used by P9000 Command View AE Suite products as firewall exceptions.
-
Originator Destination Remarks Port number Machine Port number Machine any/tcp Management server 443/tcp • P9500 - • P9500 • XP24000 • XP20000 any/tcp Management server 1099/tcp • XP12000 • XP10000 - • SVS200 • XP1024 • XP128 • XP24000 • XP20000 any/tcp • XP12000 2001/tcp# Management server • XP10000 • SVS200 Set up the firewall so that communication can be established from any port of the storage system to the 2001/tcp port of the management server.
-
This port number can be changed. Table 21 Port numbers that must be registered as firewall exceptions between the management client and storage systems Originator Destination Remarks Port number Machine Port number Machine • P9500 • XP24000 • XP20000 any/tcp Management client (GUI) 80/tcp • XP12000 • XP10000 - • SVS200 • XP1024 • XP128 • P9500 • XP24000 any/tcp Management client (GUI) 443/tcp • XP20000 • XP12000 This setting is required when using SSL for Element Manager.
-
-: Not applicable Table 22 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.
-
Originator Destination Remarks Port number Machine Port number Machine any/tcp Management server 5989/tcp VMware ESX This setting is required for SSL communication if the configuration does not use vMA.
-
Originator Destination Remarks Port number Machine Port number Machine any/tcp Management server 22104/tcp# Host Data Collector computer This setting is required when all the following conditions exist: any/tcp Management server 22105/tcp # Host Data Collector computer • Host Data Collector is installed on a computer other than the management server.
-
Originator Destination Remarks Port number Machine Port number Machine any/tcp Management server 5988/tcp# SMI-S provider This setting is required when non-SSL communication is used. any/tcp Management server 5989/tcp# SMI-S provider This setting is required when SSL communication is used. Legend: -: Not applicable #: This port number can be changed.
-
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: • A task executed from the Tiered Storage Manager CLI ends. any/tcp Management server (Tiered Storage Manager server) 25/tcp#1 Mail server#3 • A task executed from the legacy mode Tiered Storage Manager GUI (the Migration wizard) ends. • A volume lock period expires. • The period specified for a migration group elapses.
-
• Registering firewall exceptions in SUSE Linux Enterprise Server, page 92 Registering firewall exceptions in Windows To add the components that make up P9000 Command View AE Suite to the firewall exceptions list, execute the hcmdsfwcancel and netsh commands. To add the components to the firewall exceptions list: 1. Execute the following command to add the P9000 Command View AE Suite Common Web Service to the exceptions list: installation-folder-for-Common-Component\bin\hcmdsfwcancel.bat 2.
-
Component Name added to the exceptions list Path In Windows XP or Windows Server 2003 R2: installation-folder-for-Common-Component\ jdk\jre\bin\java.exe HBase(cmd) In Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2: installation-folder-for-Common-Component\ jdk5_0\jre\bin\java.exe# JDK In Windows XP or Windows Server 2003 R2: installation-folder-for-Common-Component\ jdk\bin\java.
-
5. After returning to the Firewall Configuration window, check that Security Level is Enabled, use the Tab key to move to the OK button, and then press Enter. Related topics: • Port numbers that must be registered as firewall exceptions, page 82 Registering firewall exceptions in SUSE Linux Enterprise Server To add the port numbers used by P9000 Command View AE Suite to the firewall exceptions list, edit the SuSEfirewall2 file. To add the port numbers to the firewall exceptions list: 1.
-
Figure 23 Configuration example using a server computer that has two NICs If you set up the configuration shown in Figure 23, set up routers, the management client, and the management server so that the following devices can communicate with each other as shown by the arrows in the figure: • XP12000/XP10000/SVS200 and the management client • XP12000/XP10000/SVS200 and the management server (the server computer whose IP address is 10.0.0.
-
#: The host name must be resolvable to the IPv6 address. CAUTION: If XP24000/XP20000 storage or XP12000/XP10000/SVS200 storage that is managed via an IPv4 address is also set up as a Device Manager management-target, IPv4 addresses must also be set for any NICs that have IPv6 addresses specified for the server.http.host property. Settings for migrating Device Manager to an IPv6 environment If Device Manager is used in an IPv4 environment and you then wish to use it in an IPv6 environment, edit the httpsd.
-
ServerName example.com : Listen 23015 Listen [::]:23015 SSLDisable : SSLSessionCacheSize 0 Listen 23016 #Listen [::]:23016 ServerName example.com SSLEnable : CAUTION: Do not delete or edit the default setting, Listen 23015. If you do this, communication using IPv4 will no longer be available. Settings to establish SSL communication when migrating Device Manager to an IPv6 environment Remove the hash mark (#) from the line that includes Listen [::]:23016 (the default setting).
-
Changing the IP address or host name of the management server If you change the IP address or host name of the management server because of changes to the network configuration, you also need to change the settings for P9000 Command View AE Suite products. Changing the host name of the management server To apply the changed host name to the P9000 Command View AE Suite products, edit the /etc/ hosts file (in Linux) , httpsd.conf file, and cluster.
-
4. Edit the httpsd.conf file. Change the value for the ServerName parameter to the new host name. • In Windows: installation-folder-for-Common-Component\httpsd\conf\httpsd.conf • In Linux: installation-directory-for-Common-Component/httpsd/conf/httpsd.conf If TLS/SSL is used for communication between the management server and management clients, you also need to change the following settings: • If a host name has been specified for the tag, change the host name to an asterisk (*). 5.
-
Changing the IP address of the management server To apply the changed IP address to the P9000 Command View AE Suite products, edit the httpsd.conf file, and then restart the computer. Information to collect in advance • Changed IP address of the management server CAUTION: Do not change the settings in the cluster configuration file (the cluster.conf file). To change the IP address of the management server: 1. Stop the P9000 Command View AE Suite product services.
-
6. Depending on the operating environment, review the P9000 Command View AE Suite product settings. 7. Back up the database. If you change the IP address, the data that you backed up can no longer be used.
-
Changing the URL for accessing P9000 Command View AE Suite products After starting P9000 Command View AE Suite operation, if a product URL is changed due to any of the following configuration changes, you must use the hcmdschgurl command to change the URL registered in the GUI for each product: • • • • Changing a port used by HBase Storage Mgmt Web Service Changing the host name or IP address of the management server Changing the settings for enabling or disabling SSL communication Migrating to a cluster e
-
CAUTION: • The specified URL must be a complete URL that contains protocols and a port number. You cannot use an IPv6 address. You must use a host name to specify the URL in an IPv6 environment, as shown in the following example: http://127.0.0.
-
Network configuration
-
3 User account management This chapter describes the settings required for managing user accounts of P9000 Command View AE Suite products. Password conditions for user accounts To prevent user passwords from being guessed by a third party, P9000 Command View AE Suite products allow you to specify password conditions. For example, you can specify a minimum number of characters and a required combination of character types. The password conditions are set in the security.
-
Item Description password.check.userID Specifies whether the password can be the same as the user ID. Specify true or false. If true is specified, passwords cannot be the same as the corresponding user ID. If false is specified, passwords can be the same as the corresponding user ID. Default: false When you change a setting in the security.conf file, the change takes effect immediately. The password conditions that you set in the security.
-
attempts is allowed. When you change a setting in the security.conf file, the change takes effect immediately. Unsuccessful attempts to log on to other products in the P9000 Command View AE Suite that use the Single Sign-On function count towards the number of unsuccessful logon attempts.
-
For value, specify true or false. If you specify true, the System account is subject to automatic and manual locking. If you specify false, the System account is not subject to automatic or manual locking. Note that you need to restart P9000 Command View AE Suite products services for the value set in the user.conf file to take effect. CAUTION: • If P9000 Command View AE Suite product versions 6.1 or later are installed and true is set in the user.
-
4 Security This chapter describes the security settings required to operate P9000 Command View AE Suite products. Login warning banner In version 5.1 or later of P9000 Command View AE Suite products, an optional message (warning banner) can be displayed as a security risk measure at login. Issuing a warning beforehand to third parties that might attempt invalid access can help reduce the risk of problems such as data loss or information leakage.
-
CAUTION: • When the message is registered, the HTML syntax is neither checked nor corrected. Edit the message correctly in accordance with HTML syntax rules because the edited message will be registered as is. If there is an error in the HTML syntax in the message, the message might not be displayed correctly in the Login panel. • There are no restrictions on the characters usable in the message, other than that the character encoding must be Unicode (UTF-8).
-
The locale for a warning banner displayed in the GUI is set, according to the priority of the language set for the web browser that is used. If the locale option is omitted, you can edit the registered contents from the GUI also. However, available HTML tags are limited when you edit from the GUI. Return values 0: Normal termination 253: The number of characters in the message exceeds 1,000 characters. 255: Failure Deleting the message You use the hcmdsbanner command to delete a registered message.
-
2. Open the httpsd.conf file. The httpsd.conf file is stored in the following location: • In Windows: installation-folder-for-Common-Component\httpsd\conf\httpsd.conf • In Linux: installation-directory-for-Common-Component/httpsd/conf/httpsd.conf 3. In the last line of the httpsd.conf file, register information about management clients that can be connected to the Device Manager server. The following shows how to specify the httpsd.
-
5. Start the services of P9000 Command View AE Suite product. • In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Start. • In Linux: installation-directory-for-Common-Component/bin/hcmdssrv -start CAUTION: If you log on to a P9000 Command View AE Suite product from a management client that is not registered in the httpsd.conf file, the GUI cannot be started from that P9000 Command View AE Suite product.
-
Security
-
5 Configuring Device Manager for use with related products This chapter describes the settings required for linking with related products. Linking with PA By linking Device Manager and Tiered Storage Manager to PA, you can check performance information, such as the parity group usage rate and the volume IOPS, and the PA GUI can be launched from Device Manager or Tiered Storage Manager.
-
4. Confirm that the settings are specified correctly by using either of the following methods: • When using the GUI: In the Refresh Storage Systems window, select the Refresh Performance data check box, and then refresh the storage system. After that, in the Data Collection Tasks tab, confirm that Completed is displayed for Status of the Refresh Storage Systems task. • When using the CLI: Execute the RefreshPerformanceData command, and confirm that the command finished successfully.
-
installation-folder-for-Common-Component\common In Linux: installation-directory-for-Common-Component/common In the StorageEssentials.conf file, specify the LaunchURL parameter in the following format: LaunchURL=Storage-Essentials-URL In Storage-Essentials-URL, specify the URL used to start HP Storage Essentials. For details about this URL, see the HP Storage Essentials documentation. For example, if the name of the HP Storage Essentials management server is computer-name, configure the StorageEssentials.
-
Configuring Device Manager for use with related products
-
6 Setting up logs and alerts This chapter describes the settings required to use the P9000 Command View AE Suite products to monitor the status of the system and errors. Setting up integrated log files Common Component provides a common library used for logging. P9000 Command View AE Suite products use this library to output trace log information to log files. Setting up trace log files (Windows) To change the number or size of Common Component trace log files, use the Windows HNTRLib2 utility.
-
Setting up trace log files (Linux) To change the number or size of Common Component trace log files, use the utility program (hntr2util). WARNING! Changing the common trace log settings affects other program products that use the common trace logs. Operations to complete in advance • Log in to the system as a root user. To set up Common Component trace log files: 1. Execute the utility program stored in the following location: /opt/hitachi/HNTRLib2/bin/hntr2util 2.
-
To collect Tiered Storage Manager CLI log files: • Set the necessary properties in the HtsmgetTI.properties file stored in the following location. In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\SupportTools\CollectTool\ In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/SupportTools/CollectTool/ Table 34 Properties set in the HtsmgetTI.properties file Property Description Specify the directory in which Tiered Storage Manager CLI is installed.
-
Categories Description Events indicating hardware or software failures: Failure • Hardware failures • Software failures (memory error, etc.
-
Categories Description Events indicating that abnormal communication occurred: • SYN flood attacks to a regularly used port, or protocol violations • Access to an unused port (port scanning, etc.) Different products generate different types of audit log data. For details on the contents of the output audit log data, see “Checking audit log data” on page 297.
-
Type description Automatic account lock Audit event Severity Message ID Failed login (to the external authentication server) 4 KAPM02451-W Successful logout 6 KAPM08009-I Automatic account lock (repeated authentication failure or expiration of account) 4 KAPM02292-W Table 38 Audit events that are output to audit logs (when the category is ConfigurationAccess) Type description Audit event Severity Message ID User registration Successful user registration 6 KAPM07230-I Failed user regist
-
Type description Audit event Severity Message ID Failed account lock release using the hcmdsunlockaccount command 3 KAPM07240-E Successful authentication method change 6 KAPM02452-I Failed authentication method change 3 KAPM02453-E Authorization group addition Successful addition of an authorization group 6 KAPM07247-I (GUI) Failed addition of an authorization group 3 KAPM07248-E Successful deletion of one authorization group 6 KAPM07249-I Authorization group deletion Failed deletio
-
Type description Audit event Severity Message ID User group deletion Successful deletion of a user group 6 KAPM07265-I Failed deletion of a user group 3 KAPM07266-E Successful update of a user group 6 KAPM07267-I Failed update of a user group 3 KAPM07268-E Successful registration of a role 6 KAPM07269-I Failed registration of a role 3 KAPM07270-E Successful deletion of a role 6 KAPM07271-I Failed deletion of a role 3 KAPM07272-E Successful update of a role 6 KAPM07273-I Faile
-
Type description Database input/output Database area creation or deletion Authentication data input/output Audit event Severity Message ID Successful data output using the hcmdsdbmove command 6 KAPM06543-I Failed data output using the hcmdsdbmove command 3 KAPM06544-E Successful data input using the hcmdsdbmove command 6 KAPM06545-I Failed data input using the hcmdsdbmove command 3 KAPM06546-E Successful database area creation using the hcmdsdbsetup command 6 KAPM06348-I Failed databas
-
Type description Device Manager server (via CIM) processing Acquisition of storage domain information#3 Acquisition of migration group information#3 126 Audit event Severity Message ID Response transmission (normal) 6 KAIC53100-I Response transmission (abnormal) 3 KAIC53300-E Request reception (normal) 6 Request reception (abnormal) 3 Response transmission (normal) 6 Response transmission (abnormal) 3 Successful acquisition of all storage domain information 6 KATS90000-I Failed acqu
-
Type description Acquisition of storage system information#3 Acquisition of task information#3 Acquisition of storage tier information#3 Acquisition of pool information#3 Audit event Severity Message ID Successful acquisition of migration group summary information 6 KATS90000-I Failed acquisition of migration group summary information 4 KATS90001-W Successful acquisition of storage system information 6 KATS90000-I Failed acquisition of storage system information 4 KATS90001-W Successful
-
Type description Acquisition of keystore file information#3 Acquisition of volume information#3 Acquisition of information about unused capacity of parity groups#3 Acquisition of external connection settings#3 Storage domain operations#3 128 Audit event Severity Message ID Failed acquisition of the number of pools returned from a search 4 KATS90001-W Successful acquisition of keystore file information 6 KATS90000-I Failed acquisition of keystore file information 4 KATS90001-W Successful a
-
Type description Migration group operations#3 Task operations#3 Audit event Severity Message ID Failed update of a storage domain 4 KATS90001-W Successful volume addition to a migration group 6 KATS90000-I Failed volume addition to a migration group 4 KATS90001-W Successful acquisition of the list of storage tiers that can be specified as migration destinations 6 KATS90000-I Failed acquisition of the list of storage tiers that can be specified as migration destinations 4 KATS90001-W Suc
-
Type description Storage tier operations#3 Audit event Severity Message ID Successful registration of a storage tier 6 KATS90000-I Failed registration of a storage tier 4 KATS90001-W Successful deletion of a storage tier 6 KATS90000-I Failed deletion of a storage tier 4 KATS90001-W Successful update of storage tier information 6 KATS90000-I Failed update of storage tier information 4 KATS90001-W #1: If an account is locked because the authentication method was changed for a user whose
-
Type description Audit event Severity Message ID No permission to stop a task 4 KATS90010-W Note: This information is output only by operations from the Tiered Storage Manager CLI or the Tiered Storage Manager GUI in Legacy mode.
-
Type description Acquisition of information from an external authentication server Audit event Severity Message ID Successful acquisition of user information from the LDAP directory server 6 KAPM10135-I Failed acquisition of user information from the LDAP directory server 3 KAPM10136-E Successful acquisition of the SRV record from the DNS server 6 KAPM10137-I Failed acquisition of the SRV record from the DNS server 3 KAPM10138-E For details about the output format of message text, see “Mess
-
Item Description Specify the audit event categories to be generated. When specifying multiple categories, use commas (,) to separate them. In this case, do not insert spaces between categories and commas. If Log.Event.Category is not specified, audit log data is not output. For information about the available categories, see Table 36 to Table 40. Log.Event.Category is not case-sensitive. If an invalid category name is specified, the specified file name is ignored. Log.Event.
-
Although you can specify this value, we do not recommend that you specify it. The table below shows the correspondence between the severity levels of audit events, the values indicating severity that are specified in the syslog.conf file, and the types of event log data. Table 43 Correspondence between the severity levels of audit events, the severity levels in syslog.conf, and the types of event log data Severity of audit events Severity in syslog.
-
By referencing alerts, you will be able to know the name and site of storage systems that errors have occurred in, and how to handle those errors. Information monitored by Device Manager Device Manager uses the following information to monitor the operating statuses of managed storage systems: • Status of each storage system site (default) Device Manager regularly monitors storage systems to determine if errors have occurred, and then outputs error information to the GUI or CLI.
-
Receiving email alerts You can set up Device Manager to automatically send the content of alerts to users by email. This enables users to be aware of failures that have occurred in storage systems without logging in to the management client. The settings required for sending alerts to users by email are described below. NOTE: • When an event notification email encounters a delivery error, an undeliverable notification email is sent to the address specified in server.mail.errorsTo or server.mail.from.
-
• The resource groups that correspond to the target storage systems are assigned. • Modify is set as the role in Device Manager for the assigned resource group. • Edit the profile of each user and register the email address.# #: This setting is necessary if user accounts have been registered in P9000 Command View AE Suite products. If user accounts are managed by an external authorization server, register, on the external authorization server, the user email addresses to be notified.
-
2. If SMTP authentication is enabled, use the hdvmmodmailuser command to register an SMTP authentication user account in Device Manager. The SMTP authentication user settings are also used for event notification . If an SMTP authentication user has already been set for event notification , then these settings are not required here. In Windows: installation-folder-for-the-Device-Manager-server\Server\tools\hdvmmodmailuser.
-
Subject:[DVM] Alert Notification The following alert occurred. MessageID: ${messageID} Alert Type: ${alertType} Source: ${source} Status: ${status} Component: ${component} Description: ${description} Recommended Action: ${recommendedAction} Additional Info: ${additionalInfo} Occurrence Time: ${occurrenceTime} This message was sent automatically by the Device Manager server. The mail-alert-detection.txt file consists of a header (by default, Subject:[DVM] Alert Notification) and the body of the email.
-
• Each line of the template file is no more than 1024 bytes in length, excluding the line feed character. • In the top line, the header is specified in the following format: Subject:email-title Only one header is specified. • In the second line from the top, a blank line is specified. • In the third line from the top until the bottom line, the contents are specified. • Parameters are specified in the following format: ${parameter-name} The parameter name is case sensitive.
-
Setting up Device Manager to output SNMP traps To set up Device Manager to receive SNMP traps and output them to log files, the following settings must be specified: • Settings required for Device Manager to receive SNMP traps • Device Manager must be able to use port 162/udp of the management server. • The management server information must be registered in SNMP related software as the target for trap notification. For example, to receive storage system SNMP traps, SNMP Agent settings must be specified.
-
Item Format Specify the content to be output by using the character strings (variables) below. You cannot use character strings other than the following: content-tobe-output Remarks Optional. If you omit this item, the $a$e$g$s content is output. If you specify Null for the severity, specification for this item is disabled.
-
Using event notification Tiered Storage Manager uses email to report to users the results of events that are not directly the result of user actions, such as the end of migration and shredding tasks. The following events can be reported by email: Table 47 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 • 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 48 Template files for event notification email Type Event Template file • For migration tasks created by using the Migrate data wizard#1 In Windows: installation-folder-for-theDevice-Manager-server\Server\config\mail-migrationtask-end.txt In Linux: installation-directory-for-theDevice-Manager-server/Server/config/mail-migrationtask-end.
-
Type Event Template file • In Windows: installation-folder-for-theTiered-Storage-Manager-server\ conf\mail-unlockingtask-end.txt Unlocking task ended#2 • In Linux: installation-directory-for-theTiered-Storage-Manager-server/ conf/mail-unlockingtask-end.txt • In Windows: Volume lock period expired#2 installation-folder-for-theTiered-Storage-Manager-server\ conf\mail-retention-term-expired.txt • In Linux: installation-directory-for-theTiered-Storage-Manager-server/ conf/mail-retention-term-expired.
-
The following shows how to create a template, using the template for the Migration task ended event (mail-migrationtask-end.txt) as an example. Set up template files using the following format: • Specify a header in the first line, nothing in the second line, and the email body in the third and following lines. • Specify a header in the format Subject: email-title. • Specify parameters in the format ${parameter-name}. • Use UTF-8 encoding to code the template file.
-
Parameter Description storageSystem Storage system name migrationSourceHost Migration source: Host migrationSourceLG Migration source: Logical Group migrationSourcePool Migration source: Pool migrationTargetTier Migration target: Tier migrationTargetPool Migration target: Pool options Options migratedVolumes Volume ID of the migrated volume Table 50 Parameters for events that occur when tasks end (tasks created via the Tiered Storage Manager CLI or the Tiered Storage Manager GUI in Legacy
-
Parameter Description moveToMigrationGroupName Name of the target migration group after task completion Note: For details, see the HP P9000 Tiered Storage Manager Software CLI Reference Guide.
-
installation-directory-for-the-Device-Manager-server/Server/tools/hdvmmodmailuser.sh -u Device-Manager-user-ID -p Device-Manager-password SMTP-authentication-user-ID [SMTP-authentication-password] Options -u Device-Manager-user-ID Specify the ID of a user for which All Resources has been assigned as a resource group and Admin has been set as the role in Device Manager.
-
Specify a logon password for the user ID used to log on to Tiered Storage Manager via the u option. SMTP-authentication-user-ID Specify a user ID for SMTP authentication. SMTP-authentication-password Specify a logon password for the user ID used to log on to the SMTP server.
-
Setting up logs and alerts
-
7 Configuring Device Manager for CIM/WBEM This chapter explains how to configure Device Manager for CIM/WBEM . Device Manager and CIM/WBEM Device Manager supports WBEM, which is defined by the standards-setting organization DMTF. WBEM is a standard proposed by the DMTF for managing networked devices, including hosts and storage systems, over the Internet.
-
Figure 24 CIM components for Device Manager From a CIM client, you can specify a namespace by using the follow procedure: • Specify the SMI-S version. Specify root/smis/smisxx (xx is an abbreviation for the version number). For example, to specify version 1.5.0, enter root/smis/smis15. The latest namespaces that complies with the specified SMI-S version is selected. • Specify the condition current. Enter root/smis/current. The current namespace is selected. • Specify interop. SMI-S 1.3.
-
Legend: --: N/A You can acquire information about CIM at: http://www.dmtf.org/ You can acquire information about SMI-S at: http://www.snia.
-
Enabling CIM/WBEM functions When P9000 Command View AE Suite has been installed as a new installation, the CIM/WBEM functions are enabled. If you want to enable the CIM/WBEM functions again after having disabled them, you need to specify environment settings as described below. To enable the CIM/WBEM functions: 1. Change the setting in the Device Manager server property file. In the server.properties property file, change the server.cim.support property from false to true. The server.
-
4. Restart the P9000 Command View AE Suite product services. In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop. Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Start.
-
• com.wbemsolutions.jserver.bindto #: This property is automatically set during a new installation of P9000 Command View AE Suite. Related topics: • • • • • • • • Changing Device Manager server properties, page 346 server.cim.agent, page 350 server.cim.support, page 350 server.cim.support.job, page 350 server.cim.support.protocol, page 350 server.cim.http.port, page 351 server.cim.https.port, page 351 com.wbemsolutions.jserver.
-
Unable to release the SLP service, but the removal will continue. After the removal, release the SLP service. To release the SLP service: 1. Log on as a member of the Administrator group. 2. Show the command prompt and move to the folder containing the OpenSLP executable file. 3. Release the SLP service from Windows services.
-
Starting and stopping the SLP service This section describes how to start and stop the SLP service. Starting and stopping the SLP service (Windows) To manually 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.
-
# /usr/sbin/rcslpd start To stop the SLP daemon, execute the following command: # /usr/sbin/rcslpd stop OpenSLP service The SLP service (or SLP daemon) of OpenSLP outputs operation logs to the following file: In Windows: %WINDIR%slpd.log# #: %WINDIR% is replaced by the value of the environment variable WINDIR in Windows. Normally, the value is C:\WINNT\. In Linux: installation-directory-for-the-Device-Manager-server/Server/wsi/cfg/ slp.
-
Required system configuration for acquiring performance information This section describes the system configuration required to acquire performance information of a storage system. The following figure shows an example system configuration when such information is acquired. Figure 25 Example of a system configuration in which performance information of a storage system is acquired Management server A management server is a server in which Device Manager server version 5.9 or later is installed.
-
We recommend that you use the hdvmagt_setting command to set the Device Manager agent central management method. Storage system This is a storage system whose performance information is to be acquired. The host that acquires performance information (the Device Manager agent) acquires the information of enterprise-class storage systems (P9500, XP24000/XP20000, and XP12000/XP10000/SVS200) by using the command device within the storage system, and then reports it to the Device Manager server.
-
3. Write the command device settings into the perf_cmddev.properties file. To write the settings into the file, execute the perf_findcmddev command or edit the file directly. CAUTION: • If you are using the Device Manager agent version 6.3 or earlier and you want to use a storage system in an SLPR environment, directly edit the perf_cmddev.properties file to define command devices for SLPRs. • If you upgrade the Device Manager agent from version 6.3 or earlier to version 6.
-
The following table describes values to be specified in the perf_cmddev.properties file. Table 55 Settings in the perf_cmddev.properties file Setting item Value Specify one of the following depending on the type of the target storage system: R700 for HP P9500 R600 for HP XP24000 RAID-ID R601 for HP XP20000 R500 for HP XP12000 R501 for HP XP10000 R502 for SVS200 Serial-number Specify the serial number of the storage system by using a decimal (base 10) number.
-
R600.44332.456: \\.\PhysicalDrive3 R500.14050.345: \\.\PhysicalDrive5 R500.14050.346: \\.\PhysicalDrive6 R500.14050.347: \\.\PhysicalDrive10 R501.89832.780: \\.\PhysicalDrive15 Format of the perf_findcmddev command The perf_findcmddev command allows you to specify a command device in the perf_cmddev.properties file. To execute this command, you must have Administrator permissions (for Windows) or root permissions (for Linux).
-
Item Description LDEV# Displays the CU:LDEV number of the command device by using a decimal (base 10) number. Device file name Displays the command device identifier (the physical drive number, VolumeGUID, or device file name) recognized by the host. If an unrecognizable value is defined in the perf_cmddev.properties file, that value is displayed as UNKNOWN. On lines where the definition does not follow the proper format, all information is displayed as UNKNOWN.
-
User account settings for using the CIM/WBEM functions Note that All Resources must be assigned for the users who use the CIM/WBEM functions. Also note that the CIM methods that can be executed differ depending on the role in Device Manager as described in the following table.
-
8 Setting up a cluster environment By clustering two P9000 Command View AE Suite product management servers together in an active-standby configuration, the availability of P9000 Command View AE Suite products can be improved. This chapter explains how to set up a cluster environment for P9000 Command View AE Suite products. Verifying the management server environment The setup procedure differs depending on the management server environment.
-
files for the corresponding products. For details about the sizes of other P9000 Command View AE Suite product databases, see the manuals for those products. CAUTION: • The disk configuration must be the same on all the nodes that make up a cluster. Furthermore, the installation destination for the P9000 Command View AE Suite products must also be the same (including the drive letter and path).
-
2. Remove the P9000 Command View AE Suite product services and resource group from the targets of the cluster management. For details about the services and resource group that need to be removed from the cluster management, see the manual for each relevant P9000 Command View AE Suite product. CAUTION: Do not remove the following resources from the cluster management • Shared disk • Cluster management IP address • Logical host name 3.
-
6. Use a text editor to create a cluster-configuration file. This step is not required if the cluster environment has been configured for other P9000 Command View AE Suite products. The items to be specified in the cluster-configuration file are as follows: mode=online virtualhost=logical-host-name onlinehost=executing-node-host-name standbyhost=standby-node-host-name Save the created file as cluster.conf in installation-folder-of-Common-Component\ conf.
-
9. Execute the following command to back up the database after the new installation. installation-folder-of-Common-Component\bin\hcmdsbackups /dir target-folder-for-storing-backup-files /auto dir Using an absolute path, specify the local disk folder for the database backup files. Verify that the folder for the dir option is empty. auto This option automatically changes the P9000 Command View AE Suite product services and the HiRDB service to the statuses required for backing up the database.
-
11. Execute the following command to migrate the database to the shared disk: installation-folder-of-Common-Component\bin\hcmdsdbclustersetup / createcluster /databasepath target-folder-for-re-creating-database / exportpath target-folder-for-storing-data /auto createcluster This option changes the P9000 Command View AE Suite product in a non-cluster configuration to a cluster configuration. databasepath Specify the folder in which you want to re-create the database.
-
14. Use the cluster management application to move the resource group in which the P9000 Command View AE Suite product services are registered to the standby node. If Microsoft Cluster Service is used: Right-click the resource group, and then select Move Group. If Microsoft Failover Cluster is used: Right-click the resource group, and then select Move this service or application to another node.
-
4. Open the server.properties file and make sure that the logical host name is specified in the server.http.host property. If the logical host name is not set, change the current value to the logical host name. installation-folder-of-the-Device-Manager-server\Server\config\ server.properties 5. Set the database on the shared disk as the database to be used. The procedure is described in steps 6 through 7.
-
8. Execute the following command to verify that the P9000 Command View AE Suite product services have stopped: installation-folder-of-Common-Component\bin\hcmdssrv /status 9.
-
To set up Microsoft Cluster Service: 178 Setting up a cluster environment
-
1. Add Device Manager and Tiered Storage Manager resources to the resource group. Select New, and then Resource. In each dialog box, specify the settings as shown in Table 59 to Table 64, and then select Finish. Table 59 Settings for registering HiRDB as a resource (for Microsoft Cluster Service) Dialog box name New Resource Setting Name: HiRDB/ClusterService _HD0 (optional) Resource type: Generic Service. Possible Owners Make sure that the executing and standby nodes have been added.
-
Dialog box name New Resource Setting Name: HCS Device Manager Web Service (optional) Resource type: Generic Service. Possible Owners Make sure that the executing and standby nodes have been added. Dependencies Register HBase Storage Mgmt Web Service. Generic Service Parameters Registry Replication Service name: DeviceManagerWebService Start parameters: Specify nothing. Specify nothing.
-
• Provide a cluster group (resource group), which is a group of services to be clustered (units of service failover). • Configure a resource group that includes the shared disks and client access points (cluster management IP addresses and network names) that can be inherited by the executing and standby nodes. • Make sure that Microsoft Failover Cluster can successfully control resource allocation, resource removal, and operation monitoring.
-
2. Click the resource name, and then choose Properties. Specify the settings shown in Table 65 through Table 70. Table 65 HiRDB/ClusterService _HD0 property settings (for Microsoft Failover Cluster) Tab name Setting General Startup parameters: Specify nothing (if a value is specified, delete it). Dependencies Register the shared disk and client access point. Advanced Policies Possible Owners: Make sure that the executing and standby nodes have been added. Registry Replication Specify nothing.
-
Tab name Setting General Startup parameters: Specify nothing (if a value is specified, delete it). Dependencies Register the HBase Storage Mgmt Web Service. Advanced Policies Possible Owners: Make sure that the executing and standby nodes have been added. Registry Replication Specify nothing. Table 70 HP StorageWorks XP Tiered Storage Manager property settings (for Microsoft Failover Cluster) 3. Tab name Setting General Startup parameters: Specify nothing (if a value is specified, delete it).
-
2. 3. Use the cluster management application on the executing node to take the following services offline: • HP StorageWorks XP Tiered Storage Manager • DeviceManagerServer • HCS Device Manager Web Service (if you are performing an upgrade or overwrite installation from version 7.
-
2. Perform an upgrade or overwrite installation of P9000 Command View AE Suite. For details about the installation procedure, see the HP P9000 Command View Advanced Edition Suite Software Installation and Configuration Guide. Back up or export the current database according to the installer's instructions.
-
3. If the P9000 Command View AE Suite product services are running, stop them as follows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop. 4. 5.
-
2. From the GUI, register licenses for the products you want to use. Access the IP address of the standby node. A license key must be entered for each product that is installed. 3. From the executing node, execute the following command to change the URL for starting the GUI to the logical host name. installation-folder-of-Common-Component\bin\hcmdschgurl /change http:/ /IP-address-or-host-name-of-the-executing-node:port-number http:// logical-host-name:port-number 4.
-
6. Execute the following command to back up the database at the executing node. installation-folder-of-Common-Component\bin\hcmdsbackups /dir target-folder-for-storing-backup-files /auto dir Using an absolute path, specify the local disk folder for the database backup files. Verify that the folder for the dir option is empty. auto This option automatically changes the P9000 Command View AE Suite product services and the HiRDB service to the statuses required for backing up the database.
-
8. From the executing node, execute the following command to migrate the database to the shared disk. installation-folder-of-Common-Component\bin\hcmdsdbclustersetup / createcluster /databasepath target-folder-for-re-creating-database / exportpath target-folder-for-storing-data /auto createcluster This option changes the P9000 Command View AE Suite product in a non-cluster configuration to a cluster configuration. databasepath Specify the folder in which you want to re-create the database.
-
11. On both the executing and standby nodes, change settings so that the following services start manually. • • • • • HBase Storage Mgmt Common Service HBase Storage Mgmt Web Service HCS Device Manager Web Service DeviceManagerServer HP StorageWorks XP Tiered Storage Manager In the Services panel, open the properties of each service, and then change Automatic to Manual in Startup Type. 12. Using the cluster software, register resources.
-
5. 6. If the services listed below are not being used by another application, delete the services using the cluster management application. • HP StorageWorks XP Tiered Storage Manager • DeviceManagerServer • HCS Device Manager Web Service • HBase Storage Mgmt Web Service • HBase Storage Mgmt Common Service • HiRDB/ClusterService _HD0 Use the cluster management application to suppress failover of the resource group.
-
16. To continue using the remaining resource group, enable failover. Specify the following settings for the resources whose failover was suppressed in step 6: If Microsoft Cluster Service is used: Right-click the resource name, and choose Properties, the Advanced tab, and then Restart.
-
9 Starting and stopping services This chapter explains how to start and stop the P9000 Command View AE Suite product services on the management server. Resident processes of P9000 Command View AE Suite P9000 Command View AE Suite (Device Manager, Tiered Storage Manager, and Replication Manager) operation requires that resident processes are running on the OS. The following table describes the resident processes of Device Manager, Tiered Storage Manager, and Replication Manager.
-
Process name Service name Function pdservice.exe#2 HiRDB/EmbeddedEdition _HD0 HiRDB process server control #1: Do not register it as a cluster resource. #2: This process must always be running. Do not stop it manually or register it as a cluster resource.
-
Starting services The following services are started whenever a P9000 Command View AE Suite product service is started: • • • • • • • • In HiRDB HBase Storage Mgmt Common Service HBase Storage Mgmt Web Service HBase Storage Mgmt Web SSO Service (Windows only) HCS Device Manager Web Service DeviceManagerServer HP StorageWorks XP Tiered Storage Manager All P9000 Command View AE Suite product services present on the same server Windows: Log in as a user with Administrator permissions, and then start the servi
-
Log in as a user with Administrator permissions, and then stop the services in either of the following ways: By using Windows functions: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop.
-
10 Managing the database This chapter describes how to back up and restore the database for P9000 Command View AE Suite products. Managing databases The following table describes backing up and restoring, as opposed to exporting and importing. Table 73 Backing up and restoring as opposed to exporting and importing Item Backing up and restoring Exporting and importing Restrictions on P9000 Command View AE Suite product versions No restrictions Version 5.
-
Required space: (total-size-of-all-P9000–Command-View-AE-Suite-product-databases-to-bebacked-up + 1 GB) x 2 As an example, in an environment in which Device Manager, Tiered Storage Manager, and Replication Manager are used, estimate the required space by taking into consideration the sizes of the following directories: • • • • The directory of the Device Manager database The directory of the Tiered Storage Manager database The directory of the Replication Manager database The directories of the Common Comp
-
2. Execute the hcmdsbackups command to back up the database. In Windows: installation-folder-for-Common-Component\bin\hcmdsbackups /dir folder-for-storing-backup-files /auto In Linux: installation-directory-for-Common-Component/bin/hcmdsbackups -dir directory-for-storing-backup-files -auto dir Specify the absolute path of the directory on the local disk in which the database backup files are stored. In Linux, do not specify a path that includes a space.
-
2. Use the cluster management application to take the following services offline: 3.
-
7. Execute the hcmdsbackups command to back up the database. installation-folder-of-Common-Component\bin\hcmdsbackups /dir folder-for-storing-backup-files dir Specify the absolute path of the directory on the shared disk in which the database backup files are stored. Make sure that no files or subfolders are in the directory specified for the dir option.
-
• IP address and host name of the computer • When a database is corrupted: The database can be restored by using a database exported via the hcmdsdbtrans command. The type, version, and revision of the installed P9000 Command View AE Suite products must be the same between the management server when the database was exported and the management server when the database is restored.
-
2. Execute the hcmdsdb command to restore the database. In Windows: installation-folder-for-Common-Component\bin\hcmdsdb.bat /restore backup-file /type name-of-the-P9000–Command-View-AE-Suite-productto-be-restored /auto In Linux: installation-directory-for-Common-Component/bin/hcmdsdb -restore backup-file -type name-of-the-P9000–Command-View-AE-Suite-productto-be-restored -auto restore Specify the absolute path to the database backup file (backup.hdb) that was created by using the hcmdsbackups command.
-
7. Change the value of the server.base.initialsynchro property on the Tiered Storage Manager server back to false. 8. If you specified ALL or DeviceManager for the type option, refresh the storage system from the Device Manager GUI or CLI. 9.
-
2. Use the cluster management application to take the following services offline: 3.
-
6. Execute the hcmdsdb command to restore the database. installation-folder-of-Common-Component\bin\hcmdsdb /restore backup-file /type name-of-the-P9000-Command-View-AE-Suite-product-to-be-restored restore Specify the absolute path to the database backup file (backup.hdb) that was created by using the hcmdsbackups command. Use a backup file saved on the shared disk. type As a rule, specify ALL.
-
11. On the executing node and standby node, change the value of the server.base.initialsynchro property on the Device Manager server back to false. 12. On the executing node and standby node, change the value of the server.base.initialsynchro property on the Tiered Storage Manager server back to false. 13. If you specified ALL or DeviceManager for the type option, refresh the storage system from the Device Manager GUI or CLI. 14.
-
3. Execute the hcmdsdbrepair command to restore the database. In Windows: installation-folder-for-Common-Component\bin\hcmdsdbrepair /trans exported-file In Linux: installation-directory-for-Common-Component/bin/hcmdsdbrepair -trans exported-file trans 4. Specify the absolute path to the archive file of the database exported via the hcmdsdbtrans command. In Linux, do not specify a path that includes a space. Specify true for the server.base.initialsynchro property on the Device Manager server. 5.
-
Restoring a database when it is corrupted (in a cluster configuration) To restore a database when management servers are clustered, perform the procedure below. CAUTION: • Use the executing node (a machine that has online set for mode in the cluster.conf file) to restore databases. • In the cluster management application, specify the name registered when you specified the cluster resource settings for the resource name. 1. Log on to the management server as a user with Administrator permissions. 2.
-
5. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below. 6.
-
12. On the executing node and standby node, change the value of the server.base.initialsynchro property on the Tiered Storage Manager server back to false. 13. Refresh the storage system from the Device Manager GUI or CLI. 14.
-
• 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. • Databases that are exported from an environment where Device Manager 6.
-
• Storage directory of the Common Component database (excluding the SYS directory and its subdirectories) CAUTION: • Databases are exported as archive files. If the total capacity of databases exceeds 2 GB, creation of the archive file fails when the database data is exported. In this case, instead of using the archive file, transfer the exported database data to the migration destination.
-
CAUTION: • Use the executing node (a machine that has online set for mode in the cluster.conffile) to export databases. • In the cluster management application, specify the name registered when you specified the cluster resource settings for the resource name. To export databases using Microsoft Cluster Service or Microsoft Failover Cluster: 1. Log on to the management server as a user with Administrator permissions. 2.
-
6. Start the P9000 Command View AE Suite product services. installation-folder-of-Common-Component\bin\hcmdssrv /start 7. Execute the hcmdsdbtrans command to export the databases. installation-folder-for-Common-Component\bin\hcmdsdbtrans /export / workpath working-folder /file archive-file workpath Specify the absolute path to the working folder where you want to temporarily store database data. Specify a folder on your local disk.
-
2. If you specified a value other than the default value for a property on the migration source management server, check and review the property value set on the migration destination server as required. The property file will not be migrated to the migration destination server even if the database is imported.
-
3. Execute the hcmdsdbtrans command to import the databases.
-
Product Value Other products Refer to the manual for each product. #1: When importing databases that were exported from an environment of version 7.0 or later, regardless of whether you have registered a Tiered Storage Manager license, import both the Device Manager and Tiered Storage Manager databases at the same time. #2: To import the Replication Manager database, you must also import the Device Manager database at the same time. auto 4.
-
Importing databases in a cluster configuration This section explains how to import the databases on the migration destination server when the OS of the management server is in a cluster configuration. CAUTION: • Use the executing node (a machine that has online set for mode in the cluster.conf file) to import databases. • In the cluster management application, specify the name registered when you specified the cluster resource settings for the resource name.
-
6. Use the cluster management application to suppress failover of the resource group. Change the settings of the resources listed below. 7.
-
8. Execute the hcmdsdbtrans command to import the databases. installation-folder-for-Common-Component\bin\hcmdsdbtrans /import / workpath working-folder [/file archive-file] /type {ALL|P9000-Command-View AE-Suite-products-whose-databases-will-be-migrated} workpath When using the archive file for the import: Specify the absolute path to the folder used to extract the archive file. Specify a folder on your local disk. If you want to use the archive file, the file option must be specified.
-
9. On the executing node and standby node, specify true for the server.base.initialsynchro property of the Device Manager server. Because, other than user information, the hcmdsdbtrans command does not migrate the Common Component repository, you need to synchronize the repository information with the imported Device Manager database data. 10. On the executing node and standby node, specify true for the server.base.initialsynchro of the Tiered Storage Manager server. 11.
-
18. Back up the databases. After resuming operations, you cannot import the archive file that was exported in version 6.4 or earlier. In preparation for a failure, we recommend that you back up the databases immediately after importing them. For details on how to back up the databases, see “Backing up a database in a cluster configuration” on page 199.
-
Managing the database
-
11 Using and maintaining the Device Manager agent This chapter provides notes on managing host operations and explains Device Manager agent settings and operations. Before using the Device Manager agent This section provides notes on Device Manager agent operations and the settings required before using Device Manager agent.
-
To change the priority of NICs: 1. Select Start, Settings, and then Network Connections. 2. From the Advanced menu, click Advanced Settings, and then click the Adapters and Bindings tab to change the priority of NICs. Applying storage system configuration changes to Device Manager server The OS might not recognize the modified contents immediately after the storage system configuration is changed (for example, when an LU is registered or deleted).
-
Device Manager agent in an AIX host environment This section provides notes that are specific to hosts using AIX. Registering Device Manager agent as a SED exception (AIX) The Java process to be used by the Device Manager agent must be registered as an SED exception by following the procedure below. To register the Java process as an SED exception: 1.
-
Device Manager agent in a Linux host environment If you attempt to display the Device Manager agent package information using the rpm -V command, the command will fail. This does not affect Device Manager agent operations. Setting up the Device Manager agent This section explains the settings required to start Device Manager agent operations.
-
For details about how to manually report the host information, see “Manually reporting host information to the Device Manager server” on page 236. Managing copy pairs To manage copy pairs in Device Manager or Replication Manager, you need to specify the following properties in the server.properties file as necessary.
-
Set the value to 100. • The hdvmagtif.PollingInterval property 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 • If you want to exclude a volume pair that is already managed by RAID Manager from Device Manager operations server.agent.rm.exclusion.
-
4. After upgrading from version 7.0.1 or earlier, if you changed the Java execution environment from the JRE bundled with the Device Manager agent to Oracle JDK or Oracle JRE, change the firewall settings. For details about how to change the firewall settings, see “Notes on when firewall settings are enabled (Windows)” on page 226. Changing the user who executes the Device Manager agent service A LocalSystem account is established for the user who executes the Device Manager agent service.
-
CAUTION: Depending on the load status of the Device Manager server, an OutOfMemory error might occur. If the following error message is output to the log file specified for the -t option of the HiScan command or the HiScan.msg file, change the memory heap size of the Device Manager server.
400 Bad request 400 Bad request
ServiceConnection#0: java.lang.
-
Number of LUs 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) 256 153,600 or more 600 600,000 512 307,200 or more 600 600,000 1,024 614,400 or more 1,200 1,200,000 Property settings for hosts that manage 100 or more LUs (with a volume manager) Table 80 to Table 84 list, for each host OS, the general setting values when using a volume manager.
-
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.
-
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 38,000,000 or more server.http. server.timeOut (units: seconds) server.util. processTimeOut (units: milliseconds) 600 server.agent. maxMemorySize (units: MB) 600,000 768 Table 83 Setting values when a volume manager is used (in HP-UX) Number of LUs and logical volumes managed by Device Manager and recognized by the host server. http.entity.
-
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. maxMemorySize (units: MB) 100/256 3,600,000 or more 600 600,000 192 200/256 7,100,000 or more 600 600,000 512 Device Manager agent operations This section explains Device Manager agent operations.
-
For details about how to automatically report host information, see “Automatically reporting host information to the Device Manager server” on page 228.
-
2. Specify the parameters according to the description conventions. 3. Use the Device Manager GUI or CLI to refresh the storage system that contains the copy pair volumes for which the configuration definition file was created. NOTE: • If a parameter not supported by Device Manager is used, the configuration definition file is assumed to be invalid and the system does not execute normal processing. Even though a parameter is supported, Device Manager might not support certain description formats.
-
# These parameters are supported by Device Manager agent version 6.2 or later. Note that when you create or use a copy pair, even if HORCM_INSTP or HORCM_CTQM information is defined in the configuration definition file, the Device Manager agent will operate while ignoring the definition. The Device Manager agent does not add the HORCM_INSTP or HORCM_CTQM definitions to the configuration definition file, nor does it add a pair group to the existing definitions.
-
HORCM_MON parameter description format Use the HORCM_MON parameter to specify the machine information for the local host and the interval for monitoring errors in copy pair volumes. • ip_address Specify the IP address (the Device Manager agent whose version is 5.9 or later supports the IPv6 protocol), host name, NONE, or NONE6.
-
• Specify the port name 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 86 Support status of HORCM_MON parameter description format Item Version ip_address service poll timeout 6.1 or later Yes Yes Yes Yes 5.9 to 6.
-
\\.\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. Table 87 Support status of HORCM_CMD parameter description format Item Version dev_name Windows 7.
-
• port# Specify the port name. If you specify the host group number immediately after specifying the port name for port#, the range of values that you can specify differs depending on the version of the Device Manager agent. When the version of the Device Manager agent is 5.6 or later, specify a value from 0 to 254. When the version of the Device Manager agent is 5.5 or earlier, specify a value from 0 to 127. • targetID Specify the target ID of SCSI/Fibre. • LU# Specify the LU number of SCSI/Fibre.
-
Item Version 01-00 to 0110 dev_group dev_name Yes Yes port# Yes targetID Yes LU# Yes MU# Yes Legend: Yes: Supports all description formats.
-
The value that can be specified for MU# differs depending on the version and copy type of the Device Manager agent, as shown below. When the version of the Device Manager agent is 7.4.0 or later: Business Copy: 0 to 2 Snapshot: 0 to 63 Fast Snap: 0 to 63 Continuous Access: Not specified Continuous Access Journal: 0#, h1, h2, or h3 #: When specified, multi-target configuration pairs cannot be created with Continuous Access. When the version of the Device Manager agent is from 6.0 to 7.3.
-
HORCM_INST parameter description format Use the HORCM_INST parameter to specify machine information for the remote host. • dev_group Specify the contents specified for dev_group of the HORCM_DEV parameter or HORCM_LDEV parameter. • You cannot specify ip_address more than once for the same host for a single dev_group. • Specify no more than 31 single-byte characters. A hyphen (-) cannot be specified at the beginning of the character string.
-
• Specify the port number as a numeric value from 0 to 65535. Table 91 Support status of HORCM_INST parameter description format Item Version dev_group ip_address service 7.0 or later Yes Yes 6.1 to 6.4 Yes Supports IP address and host name. Earlier than 6.0 Yes Supports IP address and host name. Yes Yes Only supports port number specification. Legend: Yes: Supports all description formats.
-
HORCM_ALLOW_INST parameter description format Use the HORCM_ALLOW_INST parameter to specify information about hosts for which the use of a virtual command device is restricted. Table 93 Support status of HORCM_ALLOW_INST parameter description format Item Version All parameters Earlier than 7.4.0 No Legend: No: Does not support any description formats.
-
- Do not change the contents of the comment because the Device Manager agent references it. - When you copy the P9000 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.
-
Item Details Registers the following ports used by the Device Manager agent in a Windows environment as firewall exceptions: • Port set for the server.agent.port property (default: 24041/tcp) • Port set for the server.http.port property (default: 24042/tcp) Description • Port set for the server.http.localPort property (default: 24043/tcp) This operation requires Administrator privileges.
-
Item Details name-of-the-addon-module Specifies the following abbreviations for add-on modules whose availability you wish to check: hdlm: Hitachi Dynamic Link Manager agent Options hdvm: Device Manager agent hrpm: Replication Manager agent hrpmap: Replication Manager Application agent The following describes add-on modules that can be checked by the hbsa_modinfo command and provides a functional overview.
-
hbsasrv command The hbsasrv command starts and stops the Device Manager agent service and displays the status of the service. The hbsasrv command is stored in the following locations: In Windows: installation-folder-for-Device-Manager-agent\bin\hbsasrv.exe In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/bin/hbsasrv In AIX: /usr/HDVM/HBaseAgent/bin/hbsasrv The following table describes the hbsasrv command syntax.
-
In Windows: installation-folder-for-Device-Manager-agent\bin\hdvm_info.exe In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/bin/hdvm_info In AIX: /usr/HDVM/HBaseAgent/bin/hdvm_info The following table describes the hdvm_info command syntax. Table 98 hdvm_info command syntax Item Details Synopsis hdvm_info Description The hdvm_info command displays the version of the Device Manager agent in V.R1.R2MM format, where V is the version number, R1.R2 is the revision number, MM is the modified version.
-
Item Details IP address or host name Enter the IP address or host name of the Device Manager server. If you specify the IP address, you can use either an IPv4 or IPv6 address. Abbreviation can be used. The host name must satisfy the following conditions: Host name length: 50 bytes or less Available characters: A to Z a to z 0 to 9 - _ . @ Setting the Device Manager server information Port number Specify the port number of the Device Manager server. You can check this value by using the server.http.
-
installation-folder-for-Device-Manager-agent\bin\HiScan.bat In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/bin/HiScan In AIX: /usr/HDVM/HBaseAgent/bin/HiScan The following table describes the HiScan command syntax.
-
Item Details -t output-file-name Specify a file name if you want to output host information sent to the Device Manager server to an XML file. The file is output to the current directory. The following characters cannot be used in the file name: \ / : , ; * ? " < > | $ % & ' ` ^ Caution: The -t option can be specified in addition to the -s option. If both options are specified, the information sent from the Device Manager agent and the messages received from the Device Manager server are output to the file.
-
Item Details -d [device-number-or-device-file-name] To view information about a specific LDEV, specify the drive number (in Windows) or device special file name (in UNIX) of the LDEV. If you omit this option, the command displays information about all currently recognized LDEVs. You cannot specify the -d option and the -g or -l option at the same time. -g [drive-group-name] If you want to view information about a specific drive group, specify the name of the drive group.
-
Item Details -serdec Specify this option to display the serial number of the storage system in decimal format. -k Specify this option to send the contents of the latest execution log file to the standard output. This processing involves no hardware access. Note that if no drive information is recorded in an execution log file, the drive information is acquired and then output to the standard output and an execution log file. You cannot specify the -k option and the -h or -hf option at the same time.
-
Item Details -history number-of-log-file-generations Specify this option to change the number of generations of execution log files to be kept. The execution-result log files are created when the device information display function is used. Specify a number from 1 to 64. The default value is 32. The specified value takes effect when the next execution log file is created. You cannot specify the -history option together with any other option.
-
Item Description Vend. Vendor name Prod.
-
RaidID Model R700 P9500 javapath_setup command The javapath_setup command is used to switch the Java execution environment used on the Device Manager agent when the host OS is Windows or Linux. The javapath_setup command is stored in the following location: In Windows: installation-folder-for-Device-Manager-agent\bin\javapath_setup.exe In Linux: /opt/HDVM/HBaseAgent/bin/javapath_setup.sh The following table describes the javapath_setup command syntax.
-
TIC command The TIC command is used to acquire error information on Device Manager agents. The TIC command is stored in the following locations: In Windows: installation-folder-for-Device-Manager-agent\bin\TIC.bat In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/bin/TIC.sh In AIX: /usr/HDVM/HBaseAgent/bin/TIC.sh The following table describes the TIC command syntax. Table 106 TIC command syntax Item Details In Windows: TIC.
-
Item Details -d [addon-module-name] 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.
-
Using and maintaining the Device Manager agent
-
12 Setting up Host Data Collector This chapter explains how to set up Host Data Collector. Installing Host Data Collector This section explains how to install Host Data Collector on a computer other than the management server. For details on the machine requirements, see the Release Notes. Prerequisites for installing Host Data Collector (Windows) The items that you can specify during installation of Host Data Collector, such as the installation path and port number, have default values.
-
Item Description Port number for class loader Port number for connecting information The non-SSL communication port number of the class loader. Default: 22100/tcp The port number of the Web server. You cannot use 5001/tcp, 23050/ tcp, or 23052/tcp. Default: 23051/tcp Related topics: • Installing Host Data Collector (Windows), page 266 Installing Host Data Collector (Windows) Install Host Data Collector from the integrated installation media.
-
NOTE: • If you performed an upgrade installation, you need to restart the services of the P9000 Command View AE Suite product on the management server. • To use Host Data Collector on multiple computers, the same version of Host Data Collector must be installed on all the computers.
-
Operations to complete in advance • Checking server requirements and prerequisite programs. For details, see Release Notes. • Logging in as a root user Information to collect in advance • Installation path (for a new installation) • Port number used by Host Data Collector (for a new installation) To install Host Data Collector in a Solaris or Linux environment: 1. Insert the integrated installation media. If the media is not mounted automatically, manually mount it onto the /mnt/dvdrom directory. 2.
-
Registering a Host Data Collector computer on the management server If Host Data Collector is installed on a computer other than the management server, you need to add the information for that computer to the properties in the hostdatacollectors.properties file on the Device Manager server. When the information for the Host Data Collector computer is registered on the management server, you can register hosts and check the volume usage on each host.
-
2. Add the information for the computer where Host Data Collector is installed to the following properties in the hostdatacollectors.properties file on the Device Manager server: To use Host Data Collector to manage normal hosts or virtual machines: hdc.connectinfo To use Host Data Collector to manage virtualization servers: hdc.rmiregistry hdc.rmiserver hdc.classloader 3. Start the services of P9000 Command View AE Suite product.
-
Process name Service name Function HdcProcessController.exe Host Data Collector Base Service Host Data Collector Base service Table 110 Resident processes of the Host Data Collector (Solaris or Linux) Process name Function /opt/CVXPAE/HostDataCollector/jre/bin/java Host Data Collector service NOTE: In a cluster configuration, the Host Data Collector service and Host Data Collector Base service must always be running in the standby node even if the executing node is being used.
-
To stop the Host Data Collector service: • Perform the following. In Windows: In the Services window, right-click Host Data Collector, and then choose Stop from the menu. In Solaris or Linux: Execute the following command: /opt/CVXPAE/HostDataCollector/tomcat/bin/shutdown.
-
• Checking the operating status of the Host Data Collector Base service, page 273 Checking the operating status of the Host Data Collector Base service Use the controlservice command to check the operating status of the Host Data Collector Base service. Operations to complete in advance • Logging in with administrator permissions To check the operating status of the Host Data Collector Base service: • Execute the following command: Host-Data-Collector-installation-destination\HDC\Base\bin\ controlservice.
-
2. Restart the Host Data Collector service to enable the settings. In the Services window, right-click Host Data Collector, and then choose Stop from the menu. In the Services window, right-click Host Data Collector, and then choose Start from the menu.
-
Registering an exception for the Host Data Collector Base service (for SSL communication) Use the netsh command to register a firewall exception for SSL communication ports used by the Host Data Collector Base service. Operations to complete in advance • Logging in with administrator permissions Information to collect in advance • Port number set for the hdc.common.rmi.ssl.registryPort property (Default value: 22104/tcp) • Port number set for the hdc.common.rmi.ssl.
-
Changing the JDK used by Host Data Collector To change the JDK used by Host Data Collector uses in a Windows environment, add the path to the desired JDK to the javapathlocation property in the javaconfig.properties file for Host Data Collector. The following JDKs are available for Host Data Collector: • JDK 5 (1.5.0) that comes with Host Data Collector • Oracle JDK 5 (1.5.0)# • Oracle JDK 6 (1.6.0)# • Oracle JDK 7 (1.7.0)# #: Use a 32-bit JDK.
-
Removing Host Data Collector You can remove Host Data Collector if it is no longer being used for host management. Removing Host Data Collector deletes all property files, log files, and other related files. Removing Host Data Collector (Windows) You can remove Host Data Collector if it is no longer needed for host management. From the Windows menu, choose Add or Remove Programs to remove Host Data Collector.
-
Setting up Host Data Collector
-
13 Troubleshooting This chapter describes how to resolve problems that occur during Device Manager and Tiered Storage Manager operation, and how to read log files. Common problems and solutions This section describes problems that might occur while setting the environments of or operating Device Manager and Tiered Storage Manager, and the causes of and solutions to these problems.
-
Problems and solutions in the management server Problems and solutions in Device Manager The following table lists common problems that occur in Device Manager and describes how to resolve them. Table 111 Common problems and solutions in Device Manager No. 1 280 Problem and cause PROBLEM: The GUI cannot be logged in to. CAUSE: The user account might have been locked.
-
No. Problem and cause Solution For a user without Admin (user management) permission: Ask a user with Admin (user management) permission to unlock the account. For a user with Admin (user management) permission: Ask another user with Admin (user management) permission to unlock the account. Alternatively, execute the hcmdsunlockaccount command to unlock your own account. To unlock the account by using the hcmdsunlockaccount command: 1.
-
No. Problem and cause Solution If the user ID or password ends with a backslash (\), use another backslash (\) to escape that backslash (\). Also, if the user ID or password includes an ampersand (&), vertical bar (|), or caret (^), enclose each character with a double quotation mark ("), or use a caret (^) to escape the symbols. • In Linux: Use a backslash (\) to escape each character.
-
No. Problem and cause PROBLEM: The Tiered Storage Manager server has not stopped. CAUSE: Possible causes are as follows: 2 • An error occurred in the Tiered Storage Manager server during processing to stop it. • The user who attempted the operation does not have administrator permissions.
-
No. Problem and cause PROBLEM: An inconsistency exists between the database information and the storage system status. CAUSE: Possible causes are as follows: 3 • The Tiered Storage Manager server terminated abnormally due to a forced termination or an unexpected error. • A failover occurred in a cluster environment.
-
No. Problem and cause Solution Perform the following procedure to restore the consistency between the database information and the storage system status: 1. After restarting the P9000 Command View AE Suite product services, refresh all storage systems by using Device Manager. 2. If a migration task was being created or canceled during an abnormal termination of the Tiered Storage Manager server, perform the creation or cancellation again.
-
No. Problem and cause Solution 3. 4 PROBLEM: Tiered Storage Manager operations cannot be performed because an error occurred in the database. If there are LDEVs that have not been migrated yet, remove the cause of the error, and then re-create and execute the migration task. Restore a backed up database. CAUSE: The repository cannot be accessed because an error occurred in the database.
-
No. 5 6 7 Problem In a Windows environment, two copies of HBase Agent are displayed in the Add or Remove programs window of the computer on which the Device Manager agent or Hitachi Dynamic Link Manager is installed. In a Windows environment, HBaseAgent is displayed in the Add or Remove programs window even after you remove both the Device Manager agent and Hitachi Dynamic Link Manager.
-
No. Problem Solution 9 When executing the HiScan command in a Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012 environment, the KAIC22009-E, KAIC22014-E, KAIC22019-E, or KAIC22048-E error message is output, and host information cannot be registered on the Device Manager server. This occurs if there are 100 or more LUs managed by Device Manager recognized by a single host, and the Device Manager agent is upgraded from version 6.0.0-00 6.2.0-02 to version 6.
-
• Maintenance information for the management server • Maintenance information for Host Data Collector • Maintenance information for the host • Java VM thread dump If any of the following problems occurs, you need to acquire the thread dumps of HBase Storage Mgmt Common Service and HCS Device Manager Web Service to locate the cause of the problem. • The Device Manager logon window is not displayed when you start the GUI. • The Device Manager main window is not displayed after logging on to Device Manager.
-
To acquire maintenance information on the management server: 290 Troubleshooting
-
• Execute the cvxpaegetlogs command. In Windows: installation-folder-for-Common-Component\bin\cvxpaegetlogs /dir folder-name [/types P9000-Command-View-AE-Suite-product-name[ P9000Command-View-AE-Suite-product-name ...]] [/arc archive-file-name] [/logtypes log-file-type[ log-file-type ...]] In Linux: installation-directory-for-Common-Component/bin/cvxpaegetlogs -dir directory-name [-types P9000-Command-View-AE-Suite-product-name[ P9000-Command-View-AE-Suite-product-name ...
-
For the file name, you can specify any printable ASCII character excluding certain special characters. You cannot specify the following characters: \ / : , ; * ? " < > | $ % & ' ` In Linux, you cannot specify a space character in a file name. logtypes Specify the types of log files to acquire when log files of a particular type cannot be collected due to a failure. log: Specify this to acquire .jar files and .hdb.jar files only. db: Specify this to acquire .db.jar files only. csv: Specify this to acquire .
-
2. Execute the SLC command. In Windows: SLC.bat [/dir output-destination-of-maintenance-information] [/o] [/help] In Solaris or Linux: SLC.sh [-dir output-destination-of-maintenance-information] [-o] [-help] • dir Specify an output destination for the maintenance information. If you omit this option, a directory named slcResult is created in the current directory. • o Specify this option to forcibly overwrite the directory if the directory specified for the dir option already exists.
-
Acquiring maintenance information on a host (for a host managed by Host Data Collector) Execute the TLC command to acquire maintenance information on a normal host or virtual machine managed by Host Data Collector. Operations to complete in advance • Copying the TLC file Copy the following file from the computer where Host Data Collector is installed to the host where the failure occurred: In Windows: Host-Data-Collector-installation-destination\Host Data Collector\ bin\target\TLC.
-
Operations to complete in advance • Logging in with Administrator permissions (for Windows) or as a root user (for UNIX) To acquire maintenance information for a host managed by the Device Manager agent: • Execute the TIC command. If the OS is Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012, execute the command in the command prompt window you activated as the administrator.
-
installation-folder-for-Common-Component\CC\web\containers\ DeviceManagerWebService If you are using the Oracle JDK, the DeviceManagerWebService.log file is overwritten each time it is output. We recommend saving the file by using a different name after the file is output. Acquiring a thread dump of the HBase Storage Mgmt Common Service (Linux) To acquire a thread dump of HBase Storage Mgmt Common Service, execute the kill command, and then restart the P9000 Command View AE Suite product services.
-
3. Start the P9000 Command View AE Suite product services. installation-directory-for-Common-Component/bin/hcmdssrv -start The javacorexxx.xxxx.txt file is output to installation-directory-for-Common-Component/CC/web/containers/ DeviceManagerWebService. Checking audit log data Audit log data has the following format. • In Windows: When you open an event by selecting Event Viewer and then Application, the following is displayed in the Description area in Event Properties.
-
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-destination-port-number,batch-operation-identifier
-
Item#1 Description 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. reserved-area Not output. This is a reserved space.
-
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 116 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 313.
-
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 124. Table 121 Items output to the audit log message text (additional information) Item Description Output format failure-cause (RC) Error code indicating the cause of a failure event RC=KATSppmmm-Z When a single item exists: storage-domain-information (SD) 1. Storage domain ID (id) 2.
-
Item Description Output format When a single item exists: storage-tier-information (ST) 1. Storage tier ID (id) 2. Storage tier name (name) When multiple items exist: 1. Number of elements (n) 2. Storage tier ID (id) 3. Storage tier name (name) ST=(id,name) NumST=n, Start STs ST[1]=(id-1,name-1) ...
-
Item Description Output format When multiple items exist: 1. Number of elements (n) 2. Controller logical device number of the migration source volume (sdevnum) NumVP=n, Start VPs 3. Object ID of the migration source LDEV (sid) ... 4. Controller logical device number of the migration target volume (tdevnum) (sdevnum-n,sid-n,tdevnum-n,tid-n) 5.
-
Item Description Output format For a locking task: 1. Task ID (id) 2. Task type (type) = 2 3. Lock status (mode) TK=(id,2,mode,days) ReadOnly: Read only Protect: Protected 4. Lock period (days) For an unlocking task: 1. Task ID (id) 2. Task type (type) = 3 TK=(id,3) For a shredding task: 1. Task ID (id) 2. Task type (type) = 4 3. Shredding method (method) TK=(id,4,method) 0: Zero once 1: DOD For multiple types of task information: 1. Number of tasks NumTK=n, Start TKs 2.
-
Item Description Output format When changing a task: 1. Task status after the change (status) 0x01020600: Executing a task 0x02030000: Erased 0x02040000: Stopped 0x02050000: Stopping mid-task 2.
-
Message (Specific application information) Message ID Description If the audit log data contains multiple lines, this message appears immediately following the KATS90000-I message. Outputs the subsequent lines of the KATS90000-I message. KATS90020-I This message occurs when, due to successful access to the resources managed by Tiered Storage Manager, an audit event for the Configuration Access type occurred.
-
OpId OpName Meaning 20 Create Create 30 Delete Delete 40 Modify Update 50 Add Add 60 Remove Remove 70 Change Change status 80 Execute Execute 90 Refresh Refresh 100 Cancel Cancel 110 Stop Stop 120 Choose Select 130 Check Check Table 124 Meanings of the operation targets (Res) output to the audit log ResId ResName Formal name Meaning 10 LC License License information 20 SD Storage Domain Storage domain 21 RS Refresh Status Storage refresh status 30 MG
-
ResId ResName Formal name Meaning 150 FSR Free Space Range Free space range to be searched for 160 EXM External Mapping External connection settings 170 PG Path Group Path group 180 EM Emulation Emulation The following are examples of audit log data output: TSMgr[00000974]:CELFSS,1.1,1,KATS90000-I,2006-11-09T19:58:45.4+09:00, TSM_Srv, Hostname1,ConfigurationAccess,Success,uid=user01,,,,,,,,,,,, BasicLog,,,"The operation requested by the client has completed.
-
Commands in message details The table below lists the commands that can be output in message details.
-
Output character string Full name Operation HostRef HostRefresh HostInfo update HostScan HostScan Automatic host setup HostVol HostVolume Host volume information notification to the Device Manager server HSD HostStorageDomain Host group and iSCSI target configuration change ISCSIForHSD ISCSINameForHostStorageDomain Change of iSCSI names that belong to iSCSI targets JrnlPool JournalPool Pool configuration change LDEVForVolMig LDEVForVolumeMigration LDEV VolumeMigration attribute settin
-
Output character string Full name Operation TrngPlcy TieringPolicy Tiering policy change URLLink URLLink URL Link information configuration change User User User setting or reference VolFmtPrgrss VolumeFormatProgress Acquisition of the progress of normal formatting of volumes VolMig VolumeMigration Migration plan setting or information acquisition VolShred VolumeShredding Shredding function execution requests or information acquisition VVol VirtualVolume THP/Smart volume setting WWN
-
Output character string Operation bulk Creates the specified number of volumes or multiple volumes of the specified size. 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. delete • If the target is ReplicationControllerPair Deletes a logical path from an existing RCU. dividebycap Creates multiple volumes of the specified size.
-
Output character string Operation • If the target is Host Hosts with the same name are overwritten. overwrite • If the target is ObjectLabel Deletes the current label and then sets a new label. • If the target is LogicalUnit Creates and quick-formats a logical unit. quickformat • If the target is LogicalUnitFormat Quick-formats a logical unit. refreshable Returns only storage systems for which the Modify role has been set in responses.
-
[parameter-1 parameter-2...parameter-n] The parameters that depend on the element are output between the start and end tags of element. If no relevant parameters exist, no parameters are output. Parameter format 2 (non-nested): The following table describes the parameter information output in message details: Table 129 Parameter information output in message details Item Description element A character string that indicates the element name.
-
Output character string ArrGrp Full name and content Sequence in which attribute values are output#1 ArrayGroup , number of chassis containing the parity group, parity group number, parity group RAID level, CLPR number, emulation mode, optional information for external parity group, type (Information about the array group of the storage system) , chassis, number, raidType, clprNumber, emulatio
-
Output character string Full name and content Sequence in which attribute values are output#1 Component Comp (Information about the storage system configuration) Condition Cond (Limits the results of the Get command by using the Filter elements at the same time) ConfigurationChange ConfChange (Reports information about the configuration changes of the storage system to the Device Manager server) -- LU type, element identifier of an LDEV, LDEV type, host storage status, alert source, host type, CL
-
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 ExternalPathInfo ExtPathI (Access information of the external storage system) #3 WWN of the port in the external storage system, LU
-
Output character string Full name and content HostInfo HostI (Information about accesses between the LU and host) Sequence in which attribute values are output#1 , 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, port ID, domain ID of host group or iSCSI target, device number of logic
-
Output character string Full name and content Sequence in which attribute values are output#1 , portID, domainID, hostMode, hostMode2, hostModeOption, name, nickname, targetNickname, targetPortID, domainType, iSCSIName IPAddress IPAddress ISCSIName (The IP address of the port controller) -- ISCSIName iSCSI name of iSCSI initiator, nickname of iSCSI initiator, nickname of operation target iSCSI initiator (iSCSI name information) JournalPool JrnlPool (Journa
-
Output character string LDEV Full name and content Sequence in which attribute values are output#1 LDEV , LBA of the LDEV, CLPR number, stripe size, tier allocation policy for Smart volumes#5, number of chassis containing the parity groups to be used to expand the DM-LUs, number of parity groups to be used to expand the DM-LUs, whether the tier of a Smart volume#5 has been relocated (Information about the LDEV) , lba
-
Output character string MFRepI Full name and content MFReplicationInfo(Information about replication of mainframe volumes) Sequence in which attribute values are output#1 , P-VOL storage system type#2, serial number of the storage system to which P-VOL belongs, P-VOL device number#4, port number in the HORCM configuration file that manages P-VOL paths, SVOL storage system type#2, serial number of the storage system to whi
-
Output character string PairedPortController Full name and content PairedPortController (CHIP paired on the NAS configuration) PairedVolume PairedVol Para Part (Information about the volume that is paired with HostVolume) -- Replication operation type#6, volume type, serial number of volume device, model of volume device#2, logical device number of volume#4, pair status, fence level, MU number of P-VOL corresponding to paired S-VOL replicationFunction#6, otherPairType, otherPairSerialNumber, otherPai
-
Output character string Full name and content Sequence in which attribute values are output#1 , fibreAddress, topology, lunSecurityEnabled, portOption, channelSpeed, ipAddress, subnetMask, gateway, portNumber, keepAliveTime, portRole, ipv6SettingMode, linklocalSettingMode, linklocalAddress, globalSettingMode, globalAddress1, globalAddress2, gatewayForIPv6, mtu, vlanSettingMode, vlanId PortCtrl PortController , mode (Infor
-
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, ID of pool that contains P-VOL, type of S-VOL storage system#2,
-
Output character string Full name and content 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) Sequence in which attribute values are output#1 number of records to be skipped from the beginning, number of records to be acquired offset, size conditional operator used to concatenate conditions represented by
-
Output character string Full name and content Sequence in which attribute values are output#1 Timestamp Timestamp Topic (Time when the message was created in the Device Manager server) Topic report information (Name of the message topic) name TieringPolicy TrngPlcy (Tiering policy information for Smart volume#5) URLLink URLLink (Links between a P9000 Command View AE Suite object and an application) User User -- (Account information of a single user of Device Manager)
-
Output character string VolGrp Full name and content Sequence in which attribute values are output#1 VolumeGroup type, name, volume group capacity, number of drives that belong to the volume group (Volume group information) VolumeMigration VolMig VolShred WritingPattern (Information about the migration plan) type, name, size, numberOfDisk , owner ID of the user who performs migration, source device number#4, target device n
-
#5: The virtual volume is created from the Smart pool (associated with Smart pool). #6: The replication operation type attribute is represented by the common output name indicated in Table 132 when it is output.
-
2. To determine the GUI operation used, compare the details of the audit log data with the contents of Table 133 and look for a matching pattern. Among the output audit log data, there will be evidence of many calls to Get-type operations. These are frequently called to refresh the screen and cannot be attributed completely to user actions. However, information that corresponds to operations such as creating, updating, and deleting various resources in Tiered Storage Manager also exists in the audit log.
-
GUI operation Key OpName# ResName# Additional information# Note Deleting a migration group M Delete MG MG -- Displaying a migration group list M Get MG SD, NumMG -- Displaying migration group detailed information M Get MG SD, MG -- MG, VL Information about the added volumes is output. Adding volumes to a migration group M Add VL M Remove VL MG, VL Information about the deleted volumes is output.
-
# For details, see Table 120 through Table 124. CLI operations and the corresponding audit log data To estimate the user-performed CLI commands by examining the output audit log data: 1. Extract the audit log data output by Tiered Storage Manager (data where the program name is TSMgr). Audit log data created by executing CLI commands is output by Tiered Storage Manager and has the TSM_CLI application identifier information.
-
2. To determine the CLI command used, compare the details of the output audit log data with the contents of Table 134 and look for a matching pattern. Except for commands starting with Get, you can identify user-executed commands by examining the audit log data that has an M in the key column.
-
CLI command CreateStorageDomain OpName ResName Additional information#2 -- Get TK TK M Create SD SD, SS -- -- Get SD SD -- M Create ST SD, ST -- M Create TK TK, SD, MG, NumVL, VLs TK=(id,3,...
-
CLI command GetMigrationGroups GetPools #1 Key #2 OpName #2 ResName Note M Get FS SS, NumFS Only acquires the number of storage systems specified in the subsystemname parameter M Get MG SD, NumMG, [MGs] -- -- Get_num PO NumPO -- -- Get SD SD -- M Get PO SD, NumPO -- M Get SD NumSD, [SDs] -- -- Get RS NumSD, SDs -- M Get ST SD, NumST, [STs] -- -- Get SD SD -- M Get TK {TK | NumTK} -- -- Get_num VL NumVL -- GetStorageDomains GetStorageTiers Ge
-
CLI command OpName ResName Additional information#2 M Modify ST SD, ST -- -- Get TK TK -- M Modify TK TK -- Key #1 #2 #2 Note ModifyTask -- Get_summary SD NumSD M Refresh SD SD -- -- Get_summary SD SD -- -- Get MG SD, MG -- -- Get VL SD, NumVL -- M Remove VL SD, MG, VL -- Refresh RemoveVolumeFromMigrationGroup StopTask M Change TK Legend: M: Main key --: Not applicable #1 Indicates key audit log data for determining the command.
-
14 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
-
Conventions This guide follows the conventions shown in Table 135 to refer to HP P9000 products.
-
Product reference Full name or meaning This abbreviation is used when it is not necessary to distinguish the following products: • P9000 Snapshot Snapshot • Snapshot • Snapshot XP • XP Snapshot Administrator Guide (Web Version) 343
-
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.
-
CAUTION: • For ordinary use, you do not need to change the values set in the property files of a Device Manager server. Use extreme caution when you are modifying the values, because you can cause the server to fail or to function incorrectly. Do not modify the values unless you have sufficient expertise. • The default values are set during a new installation.
-
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 \. • If two or more entries in a property file have the same property name, the value of the last such property specified in the file will take effect. • If a line ends with a backslash (\), the next line is a continuation of the current line.
-
The conventional port number used for a standard web server is 80, but there might already be an intranet server running on this port. Moreover, you should avoid low-numbered ports because these could conflict with other services installed on the server. As a general rule, you can pick any port between 1024 and 49151. Default: 2001 80 is used for the port number when this property is set to a space character.
-
You should avoid low-numbered ports because these could conflict with other services installed on the server. As a general rule, you can pick any port between 1024 and 65535. Default: 23055 CAUTION: If you change the value of this property, you must also change the values of the Device Manager server client.rmi.port property and the Tiered Storage Manager hdvm.rmi.port property to the same value. Related topics: • client.rmi.port, page 365 • hdvm.rmi.port, page 384 server.http.entity.
-
server.base.initialsynchro Specify whether to synchronize the management information database and the displayed information (Common Component repository) when you start Device Manager. A setting of true will synchronize the information. A setting of false will not synchronize the information. Default: false CAUTION: If this property is set to true, synchronization of the information will take several minutes. If you change the property and then log in to Device Manager right away, an error might occur.
-
1: The non-SSL communication ports are open, and the SSL communication ports are closed. 2: The non-SSL communication ports are closed and the SSL communication ports are open. 3: Both the non-SSL communication ports and the SSL communication ports are open. Default: 3 Related topics: • server.cim.http.port, page 351 • server.cim.https.port, page 351 server.cim.http.port Specify the port for non- SSL transmission for the CIM function. Default: 5988 Related topics: • server.cim.support.
-
To enable this email notification function, set this property to true. To disable this function, set this property to false. Default: true CAUTION: If this property is set to true, set the server.mail.smtp.host property. Related topics: • server.mail.smtp.host, page 352 server.mail.from Specify the email address of the notification source (sender) used to send alerts and events to users by email.
-
server.mail.smtp.auth Specify whether to use SMTP authentication to send alerts and events to users by email. To use SMTP authentication, set this property to true. To not use SMTP authentication, set this property to false. Default: false server.mail.errorsTo Specify the address to which an undeliverable notification email will be sent when alert email notifications and event email notifications cannot be delivered.
-
server.subsystem.ssid.availableValues Specify the range of the SSIDs that can be assigned automatically to storage systems registered in Device Manager. This property is valid for P9500, XP24000/XP20000, XP12000/XP10000/SVS200 and XP1024/XP128. The values that can be specified for this property are as follows: • Hexadecimal numbers in the range from 4 to FFFD: To specify consecutive numbers, use a hyphen (-) to specify the range. To specify non-consecutive numbers, use commas as separators.
-
Specify false to update all storage system resource information in the database regardless of whether the configuration has changed. Default: true Device Manager database properties (database.properties file) The database.properties file contains the database properties. • In Windows: installation-folder-for-the-Device-Manager-server\Server\config\database.properties • In Linux: installation-directory-for-the-Device-Manager-server/Server/config/ database.
-
Device Manager log output properties (logger.properties file) The logger.properties file contains the log output properties. • In Windows: installation-folder-for-the-Device-Manager-server\Server\config\logger.properties • In Linux: installation-directory-for-the-Device-Manager-server/Server/config/ logger.
-
of backups have been created. After that, the oldest backup log file is deleted each time a new backup is created. Specifiable values are from 1 to 20. Default: 10 Related topics: • logger.MaxFileSize, page 357 logger.MaxFileSize Specify the maximum size for the access.log.n, cim_access.log.n, error.log.n, service.log.n, stdout.log.n, stderr.log.n, statuscheck.log.n, trace.log.n, CIMOMTracen.log, and SMISClientTracen.log (the n in the file name indicates the backup generation number of the file).
-
When a log file reaches its maximum length, its filename is modified by increasing a counter (for example, HDvMtrace2). As more backup log files are created, their counters or version suffixes are incremented (for example, HDvMtrace2.log becomes HDvMtrace3.log), until the specified number of backups have been created. After that, the oldest backup log file is deleted each time a new backup is created. Valid values are from 1 to 16. Default: 10 logger.hbase.
-
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 polling threads. Default: 5 (minutes) server.dispatcher.traps.purgePeriod Specify the purging interval for stale SNMP traps or alerts (in minutes). A value of 0 will disable the purging of traps from the server. Default: 5 (minutes) server.dispatcher.daemon.
-
CAUTION: • If the GUI displays a warning message, manually refresh the corresponding storage system information. You can also specify the settings so that information in the database is automatically updated in case a user forgets to perform a manual refresh after changing the storage system configuration. To do so, set up the following properties: server.dispatcher.daemon.autoSynchro.doRefresh property server.dispatcher.daemon.autoSynchro.
-
CAUTION: If you specify true, only the information about the P9500 or XP24000/XP20000 is updated in the database. The information in the configuration file of a host that recognizes the command device of P9500 or XP24000/XP20000 is not updated in the database. Related topics: • server.dispatcher.daemon.autoSynchro.type, page 361 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 363 server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh Specify whether to automatically update logical group information when any of the operations below occur. If this property is set to true, logical group information is automatically updated each time one of the events below occurs.
-
Device Manager client properties (client.properties file) The client.properties file contains the client properties. • In Windows: installation-folder-for-the-Device-Manager-server\Server\config\client.properties • In Linux: installation-directory-for-the-Device-Manager-server/Server/config/ client.properties This property file contains the settings related to display and operation of Device Manager GUI. client.rmi.port Specify the port number for the Device Manager RMI server.
-
CAUTION: If this property is set to false, any migration tasks created via migration groups cannot be referenced or operated on from Tasks under the Task & Alerts tab. As such, make sure that there are no incomplete migration tasks when changing the value of this property from true to false. If there are any incomplete tasks, end the tasks via one of the following methods: • Execute the tasks immediately.
-
customizedsnmptrap.customizedSNMPTrapEnable Specify whether to output SNMP traps received by Device Manager to log files. To output SNMP traps to log files, set this property to true. To not output SNMP traps to log files, set this property to false. Default: false NOTE: If the server.dispatcher.daemon.receiveTrap property is set to true, SNMP traps from storage systems might be output to log files two times for the same event. Related topics: • server.dispatcher.daemon.
-
Valid values are 0 and from 30 to 3600 (seconds). If you specify 0, no timeout applies. Modify this property only if you are an expert system administrator and you want to fine-tune the performance of P9000 mainframe agent. Default: 300 host.agent.access.timeoutForRpm Specify the communication timeout value (in minutes) for the Replication Manager server obtaining the host information from the Device Manager agent via the Device Manager server. Valid values are from 1 to 1440 (minutes).
-
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 Related topics: • process.timeout.limit.sec, page 398 hdc.
-
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.common.rmi.ssl.serverPort of Host Data Collector. If you omit the port number, it is assumed to be 22099 if the value of the hdc.usessl property is false, and 22105 if the value is true.
-
CAUTION: You need to set the information of the computer where Host Data Collector is installed for the properties hdc.rmiregistry, hdc.rmiserver, and hdc.classloader. The IP addresses or host names of these properties must all be the same. Related topics: • • • • • hdc.common.http.serverPort, page 393 hdc.common.https.serverPort, page 395 hdc.usessl, page 371 hdc.rmiregistry, page 369 hdc.rmiserver, page 369 hdc.
-
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. When migration finishes, Tiered Storage Manager requests that the storage system splits the source volume and migration target volume 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.
-
hppa.option Specify whether to acquire performance information by linking with PA. Specify a Boolean value for this property. Specify true to acquire the performance information. Specify false if you do not want to acquire this information. Default: false hppa.CLIClientPath Specify the installation directory of the PA CLI by using an absolute path. Use slash (/) as the delimiter. Note that the delimiter / cannot be used at the end of the path.
-
B Tiered Storage Manager server properties This section describes the property files of the Tiered Storage Manager server. Tiered Storage Manager server property files There is a Tiered Storage Manager server property file for Tiered Storage Manager server operations and another property file for accessing the Device Manager server. These property files apply only to operations (processes) from the Tiered Storage Manager CLI or from the Tiered Storage Manager GUI in Legacy mode.
-
Operations to complete in advance • Log in to the system as a member of the Administrators group (in Windows) or as a root user (in Linux). To change Tiered Storage Manager server properties: 1. Stop the services of P9000 Command View AE Suite product. 2. In Windows: Select Start > All Programs > HP P9000 Command View Advanced Edition Suite > Manage Services > Stop.
-
• If a line ends with a backslash (\), the next line is a continuation of the current line. Tiered Storage Manager server operations properties (server.properties file) The server.properties file contains properties related to Tiered Storage Manager server operations. • In Windows: installation-folder-for-the-Tiered-Storage-Manager-server\conf\server.properties • In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/conf/ server.properties server.rmi.
-
Related topics: • server.rmi.secure, page 377 server.rmi.security.port For configurations using SSL communication, specify the RMI port number used by Tiered Storage Manager to accept processing requests. The range of specifiable values is from 1 to 65535. This property takes effect when 2, 3, or 4 is specified for the server.rmi.secure property. Default: 24500 CAUTION: If you change the value of this property, you also need to change the following settings: • The htsmserver.
-
Default: htsmserver server.mail.errorsTo Specify the address to which an undeliverable notification email will be sent when an event notification email cannot be delivered. If this property is not specified, the undeliverable notification email is sent to the email address specified in server.mail.from. Note that the conditions for sending undeliverable notification emails vary according to the SMTP server settings. Make sure to review these settings. Default: None Related topics: • server.mail.
-
server.migration.multiExecution Specify the number of migration pairs that can be simultaneously executed in a storage system. The range for specifiable values is from 1 to 64. Default: 8 server.checkOutVolumeRange Specify whether filter conditions used for searching volumes or defining storage tiers have their values checked for validity. Specify a Boolean value for this property. If you specify true, values will be checked. If you specify false, values will not be checked.
-
server.migrationPlan.candidateVolumeCountLimit Specify whether to limit the number of candidate volumes that are displayed when creating a migration plan. Specify a Boolean value for this property. If you specify true, the number of displayed candidate volumes will be limited. If you specify false, there will be no limit imposed on the number of displayed candidate volumes. Default: true server.migrationPlan.
-
You can specify a value from 0 to 1,440. Default: 3 server.migration.remainTimeForDeletePairInMinute Specify the number of minutes to wait after an individual migration finishes until the storage system splits that migration pair during a migration of multiple volumes,. When migration finishes, Tiered Storage Manager requests that the storage system splits the source volume and migration target volume pair.
-
client.launch.HPPA.report.protocol Specify the protocol included in the PA URL when launching the PA GUI from the Tiered Storage Manager GUI in Legacy mode. Specify http or https in lower case. Default: None client.launch.HPPA.report.host Specify the host name or IP address included in the PA URL when launching the PA GUI from the Tiered Storage Manager GUI in Legacy mode. Default: None client.launch.HPPA.report.
-
installation-folder-for-the-Tiered-Storage-Manager-server\conf\devicemanager.properties • In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/conf/ devicemanager.properties hdvm.protocol Specify the protocol to be used when accessing the Device Manager server. Default: http hdvm.port Specify the port number of the Device Manager server you are accessing. You must specify the same value as the one specified for the server.http.port property of the Device Manager server.
-
installation-folder-for-the-Tiered-Storage-Manager-server\conf\logger.properties • In Linux: installation-directory-for-the-Tiered-Storage-Manager-server/conf/logger.properties The following figure shows the relationship between the threshold value of the output levels and the output messages. Figure 26 Relationship between the threshold value of the output levels and the output messages logger.messagelogLevel Specify a threshold output level for the messages logged by Tiered Storage Manager.
-
CAUTION: If you have changed the property value, restart the services of P9000 Command View AE Suite products to enable the new value. logger.tracelogLevel Specify a threshold output level for the trace logging by Tiered Storage Manager. This property applies to the Tiered Storage Manager server trace log (HTSMServerTracen.log) and the GUI trace log (HTSMGuiTracen.log). Output levels are based on the contents of the logged messages.
-
Default: 0 CAUTION: If you have changed the property value, restart the services of P9000 Command View AE Suite products to enable the new value. logger.serverMessageFileCount Specify the number of message log files used by the Tiered Storage Manager server. The range of specifiable values is from 2 to 16. When a log file reaches the maximum size specified in the logger.serverMessageMaxFileSize property, the file is renamed by adding a counter to the file name (for example, HTSMServerMessage2.log).
-
HTSMGuiMessage2.log). The log files are used and written to in the order of the counter. A round robin method is applied, meaning that, after the end of the last file has been reached, the first file is overwritten. After the Tiered Storage Manager server starts, writing continues to the file to which the last log data was written, regardless of whether the server stopped normally last time.
-
logger.serverTraceMaxFileSize Specify the maximum size of trace log files used by the Tiered Storage Manager server (HTSMServerTracen.log). The range of specifiable values is from 32,768 bytes (32 KB) to 2,147,483,647 bytes (2,048 MB). When specifying this property, use KB to represent the size in kilobytes, and MB to represent the size in megabytes. If a unit is not specified, it is assumed that the value is specified in bytes. Default: 5,242,880 (5 MB) logger.
-
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 140 Host Data Collector property files Property file Description hdcbase.properties file This property file is related to Host Data Collector operation.
-
3. Start the Host Data Collector Base service. Host-Data-Collector-installation-destination\HDC\Base\bin\ controlservice.exe start Changing Host Data Collector properties (for alps.properties file, about.properties file, and log4jconfig.properties file) Use a text editor to edit the property files of Host Data Collector. Operations to complete in advance • Logging in with administrator permissions (for Windows) or as a root user (for Solaris or Linux) To change the Host Data Collector properties: 1.
-
Specifiable range: 1 to 65535. Default: 22098 NOTE: • If you changed the port to be used, you must use the firewall_setup command to set the new firewall exception. • If you change the value of this property in an environment that uses non-SSL communication between Host Data Collector and the Device Manager server, you must also change the hdc.rmiregistry property on the Device Manager server to the same value.
-
NOTE: • If you changed the port to be used, you must use the firewall_setup command to set the new firewall exception. • If you change the value of this property in an environment that uses non-SSL communication between Host Data Collector and the Device Manager server, you must also change the hdc.classloader property on the Device Manager server to the same value. Related topics: • Registering an exception for the Host Data Collector Base service (for non-SSL communication), page 274 • hdc.
-
NOTE: • If you changed the port to be used, you must use the netsh command to set the new firewall exception. • If you change the value of this property in an environment that uses SSL communication between Host Data Collector and the Device Manager server, you must also change the hdc.rmiserver property on the Device Manager server to the same value. Related topics: • Registering an exception for the Host Data Collector Base service (for SSL communication), page 275 • hdc.rmiserver, page 369 • hdc.ssl.
-
Specifiable range: 1 to 3. The value specified for this property determines whether to open or close the non-SSL communication ports (default: 22098/tcp, 22099/tcp, and 22100/tcp) and SSL communication ports (default: 22104/tcp, 22105/tcp, and 22106/tcp). 1: The non-SSL communication ports are open, and the SSL communication ports are closed. 2: Both the non-SSL communication ports and the SSL communication ports are open.
-
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. If a log file reaches the maximum number specified in the logger.trace.maxFileSize property, the file is renamed by adding a counter (which represents the version) to the file name.
-
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. The javaconfig.properties file exists only when Host Data Collector is installed on a Windows computer. Host-Data-Collector-installation-destination\HDC\Base\config\ javaconfig.
-
Host-Data-Collector-installation-destination\Host Data Collector\conf\ about.properties • In Solaris or Linux: Host-Data-Collector-installation-destination/HostDataCollector/conf/ about.properties version The version number of Host Data Collector set by the Device Manager installer. Under normal conditions, you do not need to change the default value of this property. Default: Value set by the installer Host Data Collector logger properties (log4jconfig.properties file) The log4jconfig.
-
Default: 9 Related topics: • log4j.appender.A1.
-
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 142 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. The hbsasrv command is stored in the following locations: In Windows: installation-folder-for-Device-Manager-agent\bin\hbsasrv.exe In Solaris, Linux, or HP-UX: /opt/HDVM/HBaseAgent/bin/hbsasrv 2. In AIX: /usr/HDVM/HBaseAgent/bin/hbsasrv Use a text editor to set appropriate values in the Device Manager agent property files. 3.
-
agent.rm.everytimeShutdown Specify whether to stop the HORCM instance for monitoring every time. Specify true or false. If true is specified, the instance stops every time. If false is specified, the instance does not stop. 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).
-
TIP: The UDP port numbers for use by the Device Manager agent can be changed by using the server.agent.rm.temporaryPort property in the server.properties file. Related topics: • server.agent.rm.temporaryPort, page 414 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.
-
amount-of-information-output-to-log-file (MB/week) = 0.75 x number-of-copy-pairs + 4 Set the values of agent.logger.MaxBackupIndex and agent.logger.MaxFileSize taking into account the amount of information that is output and the retention period. To check the number of copy pairs managed by the target host (pair management server), use Replication Manager's copy-group-name subwindow. Related topics: • agent.logger.
-
/opt/HDVM/HBaseAgent/agent/config/logger.properties • In AIX: /usr/HDVM/HBaseAgent/agent/config/logger.properties 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.
-
Related topics: • logger.MaxFileSize, page 407 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.
-
installation-folder-for-Device-Manager-agent\agent\config\server.properties • In Solaris, Linux, or HP-UX: /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.
-
server.http.socket.agentAddress Specify the IP address at which the Device Manager agent transmits notifications to the Device Manager server. In order to limit the IP addresses notified to the Device Manager server from the Device Manager agent, specify the IP address to be notified. 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.
-
CAUTION: If you are using both Device Manager and Replication Manager, for each product, specify the required memory size. Related topics: • For details on the required memory size for Device Manager: “Property settings for hosts that manage 100 or more LUs” on page 231 • For details on the required memory size for Replication Manager: “Managing copy pairs” on page 229 server.agent.
-
server.http.security.clientIP Specify an IPv4 or IPv6 address that can be used to connect to the Device Manager agent. 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.
-
Related topics: • server.http.port, page 347 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 143 Conditions on which the Device Manager agent decides which format should be used in the configuration definition file Which format is used in the existing configuration definition file Format to be used in the configuration definition file Pair operation If a format is specified in the property: No format is used.
-
CAUTION: Do not specify HORCM_LDEV in an environment where RAID Manager 01-17-03/04 or later is not installed. If you do this, the message An attempt to create a pair has failed. Error detail, host "host-name" : "error-detail" is displayed, and the attempt to create pairs fails. server.agent.rm.moduleTimeOut Specify a timeout value for receiving command execution results when the Device Manager agent executes a RAID Manager command (in seconds).
-
server.agent.rm.ignorePairStatus Specify whether to omit copy pair information when sending host information from the Device Manager agent to the management server. Specify true to omit copy pair information. Specify false if you do not want to omit the information. In the following environments, make sure that you always specify true: • Virtual machine for which a copy pair is assigned • An SVP is used as a virtual command device to manage copy pairs defined as a device group.
-
Device Manager agent properties
-
E Commands executed by Host Data Collector This appendix describes the commands executed by Host Data Collector.
-
Commands executed by Host Data Collector
-
Acronyms and abbreviations This manual uses the following abbreviations.
-
DCR Dynamic Cache Residency DER Distinguished Encoding Rules DHCP Dynamic Host Configuration Protocol DKC DisK Controller DM-LU Differential Management LU DMP Dynamic MultiPathing DMTF Distributed Management Task Force DN Distinguished Name DNS Domain Name System DoS Denial of Services DVD-ROM Digital Versatile Disk Read-Only Memory FC Fibre Channel FC-SP Fibre Channel - Security Protocol FQDN Fully Qualified Domain Name FTP File Transfer Protocol GUI Graphical User Interface
-
iSCSI Internet Small Computer System Interface J2SE Java 2 Standard Edition JAR Java ARchiver JCE Java Cryptography Extension LAN local-area network LBA Logical Block Addressing LDAP Lightweight Directory Access Protocol LDEV logical device LDKC Logical DisK Controller LU Logical Unit LUN Logical unit number LUSE Logical Unit Size Expansion MCU Main Control Unit MIME Multipurpose Internet Mail Extensions MOF Managed Object Format MU Multiple Unit NAS Network Attached Storage
-
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 Storage Area Network SCSI Small Computer System Interface SED Stack Execution Disable SIM Service Information Message SLP Service Location Protocol SLPR Storage Logical PaRtition SMI-S Storage Management Initiative - Specification SMTP Simple Mail Transf
-
WAN Wide Area Network WBEM Web - Based Enterprise Management WMI Windows Management Instrumentation WWN Worldwide name XML eXtensible Markup Language Administrator Guide (Web Version) 425
-
Acronyms and abbreviations
-
Index Symbols */tcp, 86 1099/tcp, 76, 77, 83, 84 162/udp, 72, 82 1812/udp, 89 2001/tcp, 73, 82, 83, 85 20352/tcp, 74, 82 22/tcp, 87 22098/tcp, 75, 86 22099/tcp, 75, 86 22100/tcp, 75, 86 22104/tcp, 75, 87 22105/tcp, 75, 87 22106/tcp, 75, 87 23015/tcp, 71, 82 23016/tcp, 71, 82 23017/tcp, 71 23018/tcp, 72 23025/tcp, 72 23026/tcp, 72 23031/tcp, 72 23032/tcp, 72 23050/tcp, 74 23051/tcp, 74, 87 23052/tcp, 74 23055/tcp, 73 24041/tcp, 76, 85 24042/tcp, 76, 85, 86 24043/tcp, 76 24220/tcp, 73 2443/tcp, 73, 82 24500/t
-
auditlog.conf, 132 auditlog.
-
correlation audit log (Tiered Storage Manager CLI command), 336 audit log (Tiered Storage Manager GUI operation), 333 creating warning banner message, 107 customizedsnmptrap.customizedSNMPTrapEnable, 367 customizedsnmptrap.customizelist, 367 customizedsnmptrap.properties, 366 customizing email alert templates, 138 event notification email, 144 cvxpaegetlogs command, 289 D database backing up, 197 exporting, 212 importing, 215 migrating, 211 restoring, 201 database.properties file, 355, 383 dbm.
-
GUI, 25 controlling, 109 H hbsa_modinfo command, 250 hbsa_util command, 251 hbsasrv command, 252 hcmdsunlockaccount command, 281 hdc.adapter.adapterProcessNum, 392 hdc.adapter.esx.timeout, 395 hdc.classloader, 370 hdc.common.http.serverPort, 393 hdc.common.https.serverPort, 395 hdc.common.rmi.registryPort, 392 hdc.common.rmi.serverPort, 393 hdc.common.rmi.ssl.registryPort, 394 hdc.common.rmi.ssl.serverPort, 394 hdc.request.timeout, 368 hdc.rmiregistry, 369 hdc.rmiserver, 369 hdc.ssl.secure, 395 hdc.
-
IPv6 global address, 93 global-unique local address, 93 limitations, 93 link-local address, 93 linking with storage systems that support IPv6, 93 migrating Device Manager server, 94 site-local address, 93 J Java changing (Device Manager agent), 230 javaconfig.properties file, 398 javapath_setup command, 261 javapathlocation, 398 JDK changing, 34 Host Data Collector, 276 jserver.
-
N network adapter IP address of Device Manager agent, 225 network settings for management servers with multiple NICs, 92 new installation P9000 Command View AE Suite, 170 node, 288 normal host, 35 prerequisites (Device Manager agent), 39 prerequisites (Host Data Collector), 37, 38 npivmapping.
-
property files about.properties, 398 agent.properties, 402 alps.properties, 398 client.properties, 365, 382 customizedsnmptrap.properties, 366 database.properties, 355, 383 Device Manager agent, 401 Device Manager server, 345 devicemanager.properties, 383 dispatcher.properties, 358 hdcbase.properties, 392 hldutil.properties, 405 Host Data Collector, 391 hostdatacollectors, 368 hppa.properties, 373 javaconfig.properties, 398 log4jconfig.properties, 399 logger.properties, 356, 384, 396, 405 migration.
-
server.dispatcher.daemon.autoSynchro.dayOfWeek, 361 server.dispatcher.daemon.autoSynchro.doRefresh, 360 server.dispatcher.daemon.autoSynchro.interval, 362 server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh, 364 server.dispatcher.daemon.autoSynchro.performance.doRefresh, 363 server.dispatcher.daemon.autoSynchro.performance.startTime, 363 server.dispatcher.daemon.autoSynchro.startTime, 362 server.dispatcher.daemon.autoSynchro.type, 361 server.dispatcher.daemon.configUpdate.detection.
-
SNMP traps information included in log files, 140 required settings for receiving, 135 sending to log files, 140 setting up Device Manager, 141 specifying included information, 141 specifying information to include in SNMP traps, 141 SMTP user authentication information for event notification, 149 starting Host Data Collector Base service, 272 Host Data Collector service, 271 P9000 Command View AE Suite product service, 195 SLP service, 160 stopping Host Data Collector Base service, 272 Host Data Collector
-
