HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide (web version) Reference number: T1780-96078 Tenth edition: February 2008
Legal notices © Copyright 2005, 2008 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 Contents Figures and Tables Figures ................................................................................................................................................................. 9 Tables................................................................................................................................................................... 9 About this guide Revision history ...............................................................................................
Contents 3-1-2-2 Setting memory heap size of the Device Manager server.......................................................... 46 3-1-2-3 Setting memory heap size when using CIM/WBEM ................................................................... 47 3-1-3 Executing a command with administrator privileges from the command prompt ................................ 47 3-2 Installing Device Manager in a Windows standard environment..................................................................
Contents 4-2-1-1 Checking port numbers .............................................................................................................. 99 4-2-1-2 Checking the time of a machine and the functions that adjust the time ................................... 100 4-2-1-3 Checking other programs related to security............................................................................ 101 4-2-1-4 Checking other programs .............................................................................
Contents 5-8-1 Editing the message .......................................................................................................................... 152 5-8-2 Registering the message................................................................................................................... 153 5-8-3 Deleting the message........................................................................................................................ 154 5-9 Generating audit logs ........................
Contents 8-2-35 server.mail.smtp.port ....................................................................................................................... 198 8-2-36 server.mail.smtp.auth ...................................................................................................................... 198 8-2-37 server.mail.alert.type ....................................................................................................................... 198 8-2-38 server.mail.alert.status ............
Contents 10-3-3 Configuring the Device Manager server .......................................................................................... 230 10-3-4 SMTP authentication user information setting command ................................................................ 231 10-3-5 The template file used by the email notification function ................................................................. 233 Appendix A Overview of CIM/WBEM A-1 Device Manager and CIM/WBEM...................................
Figures and Tables Figures and Tables Figures Figure 2-1 Incorrect XP series disk arrays LAN connection..................................................................................... 31 Figure 2-2 Most secure configuration: separate management LAN with firewall ..................................................... 33 Figure 2-3 Second-most secure configuration: separate management LAN with firewalled devices.......................
Figures and Tables Table 3-2 Recommended specifications for the machine where the Device Manager server is to be installed ....... 43 Table 3-3 Installation folders and required disk space ............................................................................................. 44 Table 3-4 Maximum value of the number of resources that can be managed by the Device Manager server ........ 45 Table 3-5 Data storage destination folder and required disk space for the backup and export operations............
Figures and Tables Table A-3 Table A-4 Table A-5 Table A-6 Setting values for server.cim.support.protocol....................................................................................... 239 Properties you must set for Device Manager server when executing CIM ............................................ 240 Values you need to specify in the perf_cmddev.properties file.............................................................. 248 User permissions for using CIM/WBEM features .......................
About this guide About this guide This guide provides information about: • Installing HP StorageWorks XP Command View Advanced Edition Device Manager server software • Installing Java™2 Java Runtime Environment (JRE) Revision history Table 1 Revisions Date Edition Revision July 2005 First Initial release October 2005 Second • You are now able to add the Device Manager to the Windows® Firewall exceptions list during installation. • server.cim.http.
About this guide Table 1 Revisions Date Edition Revision November 2006 Fifth • A database migration function has been added. • Remote desktop installation is now supported for Windows Server 2003 x64 Edition, Windows Server 2003 R2, Windows Server 2003 R2 x64 Edition, and Windows XP SP2. • The Open or close status of the ports used by CIM/WBEM can now be set. • Windows Server 2003 R2 is now supported as a new OS. • Commands and procedures used for setting up a cluster environment have been changed.
About this guide Table 1 Revisions Date Edition Revision June 2007 Seventh • XP24000 is now supported as a storage subsystem. • Windows Server 2003 SP2 and Windows Server 2003 R2 SP2 are now supported. • The services of XP Command View AE Suite and Common Component can now be stopped automatically when installation or uninstallation starts in a non-cluster configuration.
About this guide Table 1 Revisions Date Edition Revision September 2007 Eighth • The Device Manager Core CLI/SMI-S license, which provides functionality specialized for physically managing storage subsystems, is now supported. • A microcode version has been added that is used for obtaining information about the copy pairs created using mainframe volumes. • The XP20000 is now supported as a new storage subsystem.. • Red Hat Enterprise Linux AS 4.0 and ES 4.0 Update4 are now supported as new OSs.
About this guide Table 1 Revisions Date Edition Revision January 2008 Ninth • IP addresses in the IPv6 format can now be used in Windows and Linux. Note, however, that VDS Provider does not support IPv6. • The CIM interface can now be used to acquire storage subsystem performance information. • Information for the THP function of XP24000/XP20000 is now included in audit log data. • XP Provisioning Manager is now installed when Device Manager is installed.
About this guide Prerequisites Prerequisites for installing this product include: • • • Reading through the user's guide Meeting all the minimum installation requirements Reviewing the Release Notes on the CD for any last-minute announcements Document conventions and symbols Table 2 Document conventions Convention Element Convention Element Blue text Cross-reference links and e-mail addresses Blue, underlined text Web site addresses Bold text • Keys that are pressed • Text typed into a GUI elemen
About this guide Table 3 Conventions: Abbreviations Abbreviation Full name or meaning XP Continuous Access Asynchronous Software This abbreviation is used when it is not necessary to distinguish the following products: • XP Continuous Access Asynchronous Software • Continuous Access XP Asynchronous • Continuous Access XP Extension XP Continuous Access Journal Software This abbreviation is used when it is not necessary to distinguish the following products: • XP Continuous Access Journal Software • Co
About this guide HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support. Collect the following information before calling: • • • • • • Technical support registration number (if applicable) Product serial numbers Product model names and numbers Error messages Operating system type and revision level Detailed questions For continuous quality improvement, calls may be recorded or monitored.
Introduction to XP Command View AE Device Manager 1 Introduction to XP Command View AE Device Manager HP StorageWorks XP Command View AE Device Manager (called Device Manager in this guide) is another name for HP StorageWorks XP Command View Advanced Edition software. The Device Manager provides a consistent, easy-to-use interface for managing storage systems (also called disk arrays and subsystems).
Introduction to XP Command View AE Device Manager • Server The Device Manager server communicates with HP StorageWorks storage systems. In addition, the Device Manager server manages client connections with the Device Manager web client and Device Manager agents using the http protocol. The Device Manager agent and Device Manager server can be installed on the same host machine.
Introduction to XP Command View AE Device Manager Table 1-1 Differences in functions between the Core CLI/SMI-S license and a full license Item Functions Available with the Core CLI/SMI-S License Web client Only the functions listed below can be used. The functions that are unavailable with the Core CLI/SMI-S license are not displayed in the Explorer menu.
Introduction to XP Command View AE Device Manager Enter the Device Manager URL in a web browser, and then, on the Login screen, register the Core CLI/SMI-S license. For details on how to register a license key, see the manual HP StorageWorks XP Command View Advanced Edition software Device Manager user guide. 3. Create a user if necessary. To execute CLI, a user who has Device Manager permissions is required.
Introduction to XP Command View AE Device Manager 1-4 Related software 1-4-1 Required and optional storage system software Other management tools and application program interfaces (APIs) are required or optional for using the Device Manager to manage storage subsystems. CAUTION: When you replace the microcode for a storage subsystem that is already registered as a Device Manager management target, you need not stop the Device Manager server.
Introduction to XP Command View AE Device Manager IMPORTANT: Do not use DHCP (Dynamic Host Configuration Protocol) if you use Device Manager to manage the storage subsystem. XP12000, XP10000, and SVS200 only: The following table lists the prerequisite firmware versions and software products for using the Device Manager to manage XP12000 and XP10000 disk arrays, and the HP 200 Storage Virtualization System.
Introduction to XP Command View AE Device Manager • For more information on installing and configuring other software, see XP Remote Web Console User's Guide. IMPORTANT: Do not use DHCP if you use Device Manager to manage the storage subsystem. XP1024 and XP128 only: Table 1-4 describes the prerequisite firmware versions and software products for using the Device Manager to manage HP XP1024 and XP128 disk arrays.
Introduction to XP Command View AE Device Manager Table 1-5 Prerequisite firmware versions and software products for XP512 and XP48 Prerequisite firmware versions Prerequisite software products • SVP microcode : 01-19-99-00/02 or later • HP SNMP API • XP LUN Manager To set up security for LUNs: • XP Virtual LVI/LUN (VLL) and Volume Shredder To use functions for creating a LUSE or LDEV (CVS): • HP StorageWorks XP LUN Expansion To use the copy pair functionality: • HP StorageWorks XP Business Copy Soft
Introduction to XP Command View AE Device Manager Table 1-6 Supported of Dynamic Link Manager versions Host machine platform Dynamic Link Manager version Solaris 5.0 or later AIX 5.4.1 or later • HP StorageWorks XP Provisioning Manager automates the operations of assigning volumes to the storage server and expanding file systems. This XP Command View Advanced Edition plug-in selects the appropriate storage, creates device files on the server, and creates and mounts file systems.
Introduction to XP Command View AE Device Manager Table 1-9 shows the versions of mainframe agent that the Device Manager supports. Table 1-9 Supported mainframe agent versions Mainframe host platform Mainframe agent version OS/390 (version: 2.10) 5.1 or later z/OS (version: 1.4, 1.5, 1.6, or 1.7) 5.1 or later • XP RAID Manager, which is installed on a host, manages HP StorageWorks XP disk arrays from a command line.
Introduction to XP Command View AE Device Manager Table 1-10 Versions of HP SIM supported by Device Manager Platform HP SIM version Windows HP-UX Linux HP SIM5.0 with SP4 or later HP SIM5.0 with Update1 or later HP SIM5.
Device Manager network configuration 2 Device Manager network configuration HP StorageWorks XP disk arrays come equipped with a service processor known as the SVP. The SVP has two Ethernet adapters. The first adapter is for a private (internal) Ethernet LAN, which is intended for intra-array communications only. Only two devices can access the internal LAN: the SVP and, for XP512/XP48, the Remote Console. The second adapter is used for other applications to talk to the SVP.
Device Manager network configuration production network and reduces the risk of security-related threats. If a management controller such as the SVP coexists on a production LAN, it is left open for any entity on the IP network to access. Whether the access is intentional or not, the resulting security risks can lead to actual outages characterized as denial of service (DoS).
Device Manager network configuration Figure 2-2 Most secure configuration: separate management LAN with firewall This configuration is the most secure but least flexible implementation, because it requires overhead to manage the various network components, servers, and managed devices. Adding further security to this configuration requires that the underlying management application OS be hardened to the maximum possible. This hardening includes disabling services such as Telnet, FTP, SMTP, or IIS.
Device Manager network configuration CAUTION: When Physical View of XP24000/XP20000 or XP12000/XP10000/SVS200, or XP Remote Web Console of XP1024/XP128 is launched, Java Web Start and the web browser on the web client machine directly communicate with the storage subsystem. For this reason, if the web client machine and the storage subsystem exist on different networks, you must set up the networks so that the machine and the storage subsystem can communicate directly with each other.
Device Manager network configuration Figure 2-4 illustrates dual-homed management servers with a separate management LAN. Figure 2-4 Third-most secure configuration: dual-homed management servers plus separate management LAN 2-2-4 Least secure configuration: Flat network Here, the management application servers, managed devices, and managed clients all coexist on the same network. This configuration is the least secure, though it is the most flexible.
Device Manager network configuration 2-3 Working with a network that uses a firewall If a firewall is set up between the management server and other objects (such as the management client, managed host, storage subsystem, or CIM [Common Information Module] client), set the firewall to allow communication through each port, as detailed in Table 2-1 to Table 2-4.
Device Manager network configuration Table 2-3 Ports used for communication between the management server and storage subsystems Port number Originator Destination 161/udp Management server XP512/XP48 - 162/udp • • • • Management server - 1099/tcp Management server • XP1024/XP128 • XP12000/XP10000/SVS200 • XP24000/XP20000 - 51099/tc Management server p • XP1024/XP128 • XP12000/XP10000/SVS200 • XP24000/XP20000 - 51100/tc Management server p • XP24000/XP20000 XP512/XP48 Remarks XP1024/XP
Device Manager network configuration Table 2-6 Ports used for communication between the management client and a storage subsystem Port number Originator Destination Remarks 1099/tcp Management client (web client) • XP1024/XP128 • XP12000/XP10000/SVS200 • XP24000/XP20000 - Management client (web client) • XP1024/XP128 • XP12000/XP10000/SVS200 • XP24000/XP20000 - 51099/tc Management client p (web client) • XP1024/XP128 • XP12000/XP10000/SVS200 • XP24000/XP20000 - 80/tcp 2-4 Registering firewall
Device Manager network configuration 2-5 Setting up the environment of a server machine that has multiple NICs If the server machine on which Device Manager has been installed has multiple NICs, when you specify an IP address in the Device Manager settings, specify the IP address of the NIC that belongs to the network to which web client is connected. Do not specify the host name. This section describes the network settings required for the configuration shown in Figure 2-6.
Device Manager network configuration 2-6 Operating in an IPv6 environment Device Manager has supported IPv6 environments since version 5.9. For details about the OSs that support Device Manager server operations in IPv6 environments, see section 3-1 for Windows, and section 4-1 for Linux. 2-6-1 Limitations on operations in an IPv6 environment Note the following limitations when you use Device Manager in an IPv6 environment: • Device Manager does not support IPv6-only environments.
Device Manager network configuration Listen 23016 Listen [2001::99]:23016 CAUTION: Do not delete or edit the existing Listen line. If you do this, communication using IPv4 will no longer be available. 2-6-2-3 Settings when using a loopback address If you use a loopback address, in addition to the Listen line for IPv6, add a Listen line for the loopback address by using the following syntax below. Specify the same port number as specified in the Listen line for IPv4.
Windows systems installation 3 Windows systems installation This chapter provides instructions for installing the Device Manager server software on a single central server system. For instructions on installing and using the web client software, see HP StorageWorks XP Command View Advanced Edition software Device Manager user guide. NOTE: The Device Manager does not support web client operations that use Windows terminal service.
Windows systems installation Table 3-1 List of Windows versions on which Device Manager server runs Abbreviated name and architecture Edition name Service Cluster pack environment support IPv6 environment support Prerequisite program Windows 2000 Professional Server Advanced Server Datacenter Server SP4 Y (Except the Professional edition) -- J2SE Java Runtime Environment 5.0.
Windows systems installation • Installation folders and required disk space: The following table describes the default installation folders and the required disk space for installation. Table 3-3 Installation folders and required disk space Item Default installation folder Required disk space (GB) Installation destination for the Device Manager server C:\Program 1.
Windows systems installation CAUTION: Depending on the language (such as German or Spanish) of the OS on the installation destination Windows machine, the installation files and folders of the Device Manager server can be viewed, deleted, and operated by users who do not have Administrator privileges. (This problem does not occur in an English environment.) Regardless of the language of the installed OS, after installing the Device Manager, do not manually delete or operate files or folders.
Windows systems installation • You can only increase the heap size that has been set. If you want to decrease it, uninstall the Device Manager server, re-install the Device Manager server, and then change the heap size to the size you want. • In an environment in which multiple XP Command View AE Suite products are installed, the largest heap size of the sizes for the products takes effect. To set the memory heap size of HBase Storage Mgmt Web Service: 1.
Windows systems installation memory-heap-size = number-of-LDEVs x 0.03 + total-number-of-paths x 0.03 + 140 2. Restart the Device Manager server as follows: Select Start, Programs, XP Command View AE, Device Manager, and then Stop Server. After the Device Manager server has stopped, select Start, Programs, XP Command View AE, Device Manager, and then Start Server.
Windows systems installation If you attempt to execute a command from the ordinary command prompt, a message dialog box requesting that you elevate privileges appears. Note that, in this case, the execution result is displayed in a new command prompt window that is different from the command prompt window from which the command was executed. What is worse, the new window automatically closes when the entire execution result has been displayed.
Windows systems installation 3-2-1-1 Checking port numbers Check whether the port numbers required to use Device Manager are being used by another product on the machine on which the Device Manager server is to be installed by using the netstat command. Example: Check whether another program is using the port 162/udp. Execute the following command: > netstat -anp UDP In the command execution results, if there are no lines in which UDP for Proto, and 162 for Local Address appear, the port is not being used.
Windows systems installation 3-2-1-2 Checking the time of a machine and the functions that adjust the time If the time of a machine is changed while the services of Common Component and XP Command View AE Suite are running, Device Manager might not operate correctly. If you need to change this time, do so before installation.
Windows systems installation The Performance Options dialog box is displayed. 5. Choose the Data Execution Prevention tab, and then select the radio button for Turn on DEP for all programs and services except those I select. 6. Click the Add button. The dialog box for choosing a file is displayed. 7. Choose setup.exe in the root folder of the CD-ROM drive, and then click the Open button. 8. Click the OK button.
Windows systems installation If the above conditions are not satisfied, an attempt to install the Device Manager server might fail or the Device Manager server might not work properly. Also, do not change the setting for automatically generating short names even after the installation has completed.
Windows systems installation 3-2-2 Performing a new installation of the Device Manager server and Common Component NOTE: If you cancel the installation, the installation folder might remain. Delete the folder manually if you do not need it. CAUTION: Before starting installation, make sure that no processing is in progress in other XP Command View AE Suite products. If any processing is in progress, installation might fail. To perform a new installation of the Device Manager server: 1.
Windows systems installation ○ ○ ○ ○ ○ If you change the default, make sure that you can write to that folder. The path cannot contain consecutive spaces. Folder names must not end with a period or space. Do not use parentheses, except when referring to the Program Files (x86) folder. Do not specify a symbolic link and junction for the installation folder. 10. In the Install Folder Information screen, click Next to continue. 11.
Windows systems installation If you chose YES. Automatically enable the function after installation, the processing continues. If you chose NO, the processing continues from step 20. You can set up the SMI-S Provider service after installation. For details, see Appendix A Overview of CIM/WBEM. 16. The Setting for the SMI-S SSL screen is displayed. To enable SSL for the SMI-S Provider service, select YES. To disable SSL, select NO.
Windows systems installation cancel the installation, manually stop the services of XP Command View AE Suite Common Component and XP Command View AE Suite Products, and then re-execute the installation. 21. The Secure Socket Certificates Note screen is displayed. If you plan to run secure socket communications, note the information in this screen for later use, and then click Next to continue. 22. When the Install Complete screen is displayed, click Finish to complete the installation. 23.
Windows systems installation If there are multiple password keys: All password keys and their values in the old hdvmcli.properties file are written to the new file as is. The following shows an example: • The password keys and their values in the old file: password=AAA password=BBB • The password keys and their values written to the new file: password=AAA password=BBB If there are duplicate keys other than password: The name and value of the most recent duplicate key in the old hdvmcli.
Windows systems installation 3. Release the SLP service registration. 4. Re-register the SLP service. In version 5.0 or later, user information is managed by using the user management functionality of XP Command View AE Suite Common Component. The registered user information is migrated to the XP Command View AE Suite Common Component repository when the Device Manager server program is started for the first time after the upgrade installation.
Windows systems installation If you attempt to install Device Manager whose version or revision is earlier than the already installed Device Manager, the installer displays the Device Manager Upgrade Error panel and the installation will be canceled. 7. The Do you want to back up the database? or Do you want to export the database? dialog box appears. If you want to back up or export the database, select Yes. If you do not want to back up or export the database, select No.
Windows systems installation 10. The Pre-Installation Summary screen is displayed. The product name, version, installation folder, options, and other information that you specified during installation are displayed. Verify that the information is correct, and then click Install to begin. If you select Install, the Installing Device Manager dialog box appears. The progress of the processing is displayed. While the Installing Device Manager dialog box is displayed, you cannot cancel the installation.
Windows systems installation 3-3-1 System requirements for a cluster service The requirements for a cluster environment are as follows: • • • • Platform: See Table 3-1. Cluster software: Microsoft® cluster service (MSCS) Number of nodes: 2 Cluster configuration: Active-standby configuration NOTE: On all nodes that make up a cluster, the disk configuration must be the same, and the installation folder for the Device Manager server must have the same name (including the drive letter and path name).
Windows systems installation 5. In Cluster Administrator, switch, to the executing node, each group in which the XP Command View AE Suite service has been registered. In the Cluster Administrator, for each group where an XP Command View AE Suite product service has been registered, right click the group and then choose Move Group. 6.
Windows systems installation Specify the folder in which you want to re-create the database. After this option name, specify the absolute path of an already created folder on a local disk. Note that the path name must not exceed 63 bytes. The characters that can be used to specify the path are shown below. In addition to these characters, a backslash (\), colon (:), or forward slash (/) can be used as path delimiters.
Windows systems installation 3-3-3 Performing a new installation CAUTION: While performing cluster configuration, do not access Device Manager. CAUTION: Before starting installation, perform the following steps: • If the cluster management IP address and shared disk are not enabled on the executing node, perform steps 1 to 5 in 3-3-3-3 below to place the resources of the cluster management IP address and shared disk online.
Windows systems installation server.http.host = hcmdserver 6. If XP Command View AE Suite products whose versions are earlier than 5.7 have been installed, stop their services. For details about how to stop these services, see the manual for your product version. 7. If Common Component is running, stop the services of Common Component and all XP Command View AE Suite, and then start HiRDB.
Windows systems installation of XP Command View AE Suite products whose versions are earlier than 5.7 are not stopped automatically. CAUTION: You must not execute multiple instances of this command concurrently. Also, you must not execute this command and the cvxpaegetlogs command concurrently. CAUTION: For details about how to set the port that HiRDB uses, see subsection 5-4-2 . 10.
Windows systems installation You cannot specify an IP address for virtualhost, onlinehost, or standbyhost. Confirm that the IP address can be resolved from the host name. The following example shows sample entries in a cluster configuration file: mode = standby virtualhost = hcmdserver onlinehost = hcmdserver_1 standbyhost = hcmdserver_2 4. Save the created file as cluster.conf in \conf. 5. Open the server.
Windows systems installation CAUTION: You must not execute multiple instances of this command concurrently. Also, you must not execute this command and the cvxpaegetlogs command concurrently. IMPORTANT: For details about how to set the port that HiRDB uses, see subsection 5-4-2 . 8.
Windows systems installation ○ Dependencies: Register HiRDB. ○ Generic Service Parameters: − Service name: HBaseStgMgmtComService − Start parameters: Specify nothing. ○ Registry Replication: Specify nothing. ○ Select Finish. 5. Settings for Registering the HBase Storage Mgmt Web Service as a resource: ○ Select New > Resource. ○ New Resource: − Name: Mgmt Web Service (optional) − Resource type: Generic Service ○ Possible Owners: Make sure that the executing and standby nodes have been added.
Windows systems installation ○ In the Preferred Owners dialog box, move the executing node and standby node from Available nodes to Preferred owners. ○ Select Finish. 3. Register the IP address of the Device Manager server to that resource group. If that address has already been used to register another resource group, move the IP address to the resource group created or selected in step 2.
Windows systems installation − Service name: HBaseStgMgmtComService − Start parameters: Specify nothing. ○ Registry Replication: Specify nothing. ○ Select Finish. 7. Register the Device Manager server as a resource. Right-click on the left side of the Cluster Administrator window, and select New > Resource. Specify the following settings: ○ New Resource. − Name: DeviceManagerServer − Resource type: Generic Service ○ Possible Owners: Make sure that the executing and standby nodes have been added.
Windows systems installation Select Start, Programs, XP Command View AE, Device Manager, and then Stop Server with Common Services. 6. In Cluster Administrator, place the HiRDB service offline. The above service is represented by the resource name registered in subsection 3-3-3-3 . 7.
Windows systems installation Select Start > Programs > XP Command View AE > Device Manager > Stop Server with Common Services. NOTE: Do not stop the Common Component services while another XP Command View AE Suite program is running. 5. In the Services screen, open the properties for the following services, and then change Startup Type from Automatic to Manual: ○ HBase Storage Mgmt Common Service ○ HBase Storage Mgmt Web Service ○ DeviceManagerServer 6.
Windows systems installation 4. Save the created file as cluster.conf in \conf. 5. On the executing or standby node, if XP Command View AE Suite products whose versions are earlier than 5.7 have been installed, stop their services. For details about how to stop these services, see the manual for your product version. 6.
Windows systems installation of XP Command View AE Suite products whose versions are earlier than 5.7 are not stopped automatically. CAUTION: You must not execute multiple instances of this command concurrently. Also, you must not execute this command and the cvxpaegetlogs command concurrently. CAUTION: For details about how to set the port that HiRDB uses, see subsection 5-4-2 . 9. On the standby node, change the setting so that the database on the shared disk is to be used.
Windows systems installation If all of these services can be started, the installation was successful. If one or more of these services either does not appear in the Windows Services screen, or cannot be started, the installation has failed. 1. Use a text editor to open the following file and verify that Common Component is installed: \sample\conf\build 2. If Common Component is installed, you will see an eight-digit build number (for example, 05010038) in this file.
Windows systems installation 3-5-3 The Device Manager server fails to start If the Device Manager server fails to start, the installation may have failed. Examine the trace log at \Server\logs\HDvMtrace*.log, review the error codes, and follow the recommended action. For more information about error codes, contact your HP support representative for assistance.
Windows systems installation • To stop the Device Manager server and XP Command View AE Suite Common Component: Select Start > Programs > XP Command View AE > Device Manager > Stop Server with Common Services. ○ Services of other XP Command View AE Suite products whose versions are 5.7 or later are also stopped at the same time. For details, see CAUTION below. ○ If XP Replication Monitor 5.6 or earlier is installed, you cannot stop the Device Manager server by selecting Stop Server with Common Services.
Windows systems installation • To stop the Device Manager server and XP Command View AE Suite Common Component, execute the following command: \bin\hcmdssrv /stop ○ Services of other XP Command View AE Suite products whose versions are 5.7 or later are also stopped at the same time. For details, see CAUTION below. ○ If XP Replication Monitor 5.6 or earlier is installed, you cannot stop the Device Manager server by executing the hcmdssrv /stop command.
Windows systems installation Table 3-6 Resident processes of the Device Manager server and Common Component (In Windows) Process name Service name Function hntr2mon.exe Hitachi Network Objectplaza Trace Monitor 2 XP Command View AE Suite common trace information collection (collects integrated trace information.) hntr2srv.exe XP Command View AE Suite common trace service (processes events from the Services screen.
Windows systems installation Table 3-7 Backing up and restoring verses exporting and importing Item Backing up and restoring Conditions for the machine used for The following must be the same in the restore destination or the import the backup source machine and destination the restore destination machine: • Types, versions, and revisions of the installed XP Command View AE Suite Products Exporting and importing • The XP Command View AE Suite products whose databases are to be imported must be installe
Windows systems installation NOTE: The backup will be written to the following folders: C:\TMP\backup\base and C:\TMP\backup\database NOTE: This example used the C:\TMP folder as the backup location. In a production environment, you should create a permanent folder for the backup location.
Windows systems installation NOTE: Do not use the Windows Services screen to start and stop Device Manager services 1. If XP Command View AE Suite products whose versions are earlier than 5.7 have been installed, stop their services. For details about how to stop these services, see the manual for your product version. 2. Execute the hcmdsdb command from the command prompt: \bin\hcmdsdb.
Windows systems installation CD C:\Program Files\CVXPAE\Base\bin hcmdsdb /restore C:\TMP\backup\database\backup.hdb /type ALL Figure 3-2 Sample batch command restoring database 3-7-3 Migrating the server database If XP Command View AE Suite is used for an extended period of time, you may need a higher performance machine in order to accommodate product version upgrades and the increased number of objects to be managed.
Windows systems installation • You cannot perform migration to integrate the XP Command View AE Suite that was running on multiple management servers on to one management server because user information will be overwritten with each successive migration. 3-7-3-2 Procedure for migrating databases To migrate databases: 1. Install, on the migration destination server, the XP Command View AE Suite products whose databases will be migrated. 2.
Windows systems installation The auto option can be specified only when XP Command View AE Suite products whose versions are 5.
Windows systems installation installation-folder-for-Common-Component\bin\hcmdsdbtrans The format of the command is as follows: hcmdsdbtrans /import /workpath working-folder [/file archive-file] /type {ALL | Commnad-View-XP-AE-Suite-whose-database-will-be-migrated} /auto The following shows an example of executing the command: C:\Program Files\CVXPAE\Base\bin\hcmdsdbtrans /import /workpath D:\trans_work /file D:\trans_file\db_arc /type ALL /auto In the hcmdsdbtrans command, you can specify the following opt
Windows systems installation CAUTION: If XP Replication Monitor version 1.1 is installed on the migration source machine, you cannot migrate the database. Therefore, upgrade XP Replication Monitor on the migration source and migration destination machines to version 5.0 or later, and then perform migration. If XP Replication Monitor cannot be upgraded to version 5.
Windows systems installation installation-folder-for-the-Device-Manager-server\database.bat initialize The following shows an example of executing the command: C:\Program Files\CVXPAE\DeviceManager\database initialize 5. Specify true for the server.base.initialsynchro property in the server.properties file. For details, see subsection 8-2-23 . 6. Start the Device Manager server: Select Start > Programs > XP Command View AE > Device Manager > Start server (see 36-1 ). 7. In the server.
Windows systems installation CAUTION: Check whether the following programs are installed. If they are installed, take action by following the explanation below: • A program that monitors security Stop the program that monitors security, or change its settings so that Device Manager can be uninstalled normally. • A program that detects viruses We recommend that you stop programs that detect viruses, and then uninstall Device Manager.
Windows systems installation CAUTION: The services of XP Command View AE Suite products whose versions are earlier than 5.7 are not stopped. Stop the services manually, and then continue the uninstallation. For details about how to stop these services, see the manual for your product version. CAUTION: Clicking Cancel treminates the installation. 7. In a non-cluster environment, the Set Services to Start after Uninstallation screen is displayed.
Windows systems installation 3-8-2 Uninstalling the Device Manager server in a cluster environment This subsection describes uninstallation of the Device Manager server when a cluster environment has been set up using Microsoft Cluster Service. 1. Back up the database of the Device Manager server. For details about how to back up the database, see section 3-7-1 . 2. Open the cluster administrator: Select Start > Settings > Control Panel > Administrative Tools > Cluster Administrator. 3.
Windows systems installation In the Cluster Administrator, right-click the group to which the Device Manager service has been registered, and then select Move Group. 13. On the standby node, uninstall the Device Manager server. For details about how to uninstall the Device Manager server, see subsection 3-8-1 . 14. On the standby node, uninstall the Device Manager server: Select Start > Programs > XP Command View AE > Device Manager > Uninstall Device Manager. 15.
Linux systems installation 4 Linux systems installation This chapter explains how to install the Device Manager server on a Linux system.
Linux systems installation When using the Device Manager server in a time zone of the United States or Canada, set the OS of the machine on which the Device Manager server will be installed so that the OS is compatible with the new Daylight Saving Time (DST) rules. If the OS is not compatible with the new DST rules, the Device Manager server will also not be compatible with the new rules.
Linux systems installation ○ gzip • LAN cables, connections to the storage subsystem, and a 10/100 Ethernet LAN card that has TCP/IP installed and available. (If the machine and the LAN cable are compatible with Gigabit Ethernet, you can use a Gigabit-class card.) • When using one Device Manager server, it is not possible to use separate storage partitions with different storage administrator accounts.
Linux systems installation After the memory heap size is set, if number-of-managed-resources increases from 50,000 or less to 50,001 or greater, only set the memory heap size of the Device Manager server if the memory heap size of HBase Storage Mgmt Web Service has already been set. The set value is valid until the Device Manager server is uninstalled.
Linux systems installation 4-1-2-2 Setting memory heap size of the Device Manager server To set the memory heap size of the Device Manager server: 1. Use a text editor to open the following file: installation-directory-for-the-Device-Manager-server/hdvm.sh 2.
Linux systems installation Example of changing the value (when the new-setting-value is calculated to be 512 MB): Before: java -Xmx256m -classpath ... After: java -Xmx512m -classpath ... 3.
Linux systems installation In the command execution results, if there are no lines in which Local Address is 162, the port is not being used. The following shows the ports required to use Device Manager. For details about the intended use of each port, see section 2-3 and subsection 5-4-1 . Port numbers that must be checked • From 23015 to 23018, and 23032: If another product is using any of these ports, change the settings of that product, or change the settings of Device Manager.
Linux systems installation 4-2-1-3 Checking other programs related to security • Check whether the following programs are installed. If they are installed, take action by following the explanation below: ○ A program that monitors security Stop the program that monitors security, or change its settings so that Device Manager can be installed normally. ○ A program that detects viruses We recommend that you stop programs that detect viruses, and then install Device Manager.
Linux systems installation • Grant all users read and execution permissions for the directory to be specified as the installation directory and all the directories above that directory. Note that, in Linux, if you specify an existing directory as the installation directory, the permissions of the installation directory is set to 775. If you do not want the permissions of the existing directory to be changed to 775, specify another directory as the installation directory.
Linux systems installation 4-2-2 Performing a new installation NOTE: If you cancel the installation, the installation directory might remain. If this directory is not necessary, delete it manually. WARNING: Before starting installation, make sure that no processing is in progress in other XP Command View AE Suite products. If any processing is in progress, installation might fail. To perform a new installation of the Device Manager server: 1. Log in to the Linux system as the root user.
Linux systems installation CAUTION: If you enter y, the properties for the SNMP Trap reception function are automatically changed to disable the function. You must reset these properties to the default values manually. For details about these properties, see subsection 8-5-8 . 10. In Linux, a message appears prompting you to specify the installation directory. To accept the default directory, press the Enter key.
Linux systems installation 15. A message about the settings for the SMI-S Provider service appears. If you want the SMI-S Provider service to start automatically when Device Manager starts, select 1. If you do not want it to start automatically, select 2. If you selected 1, go to the next step. If you selected 2, go to step 18. NOTE: You can set up the SMI-S Provider service after installation. For details, see Appendix A Overview of CIM/WBEM. 16. A message about the SSL settings for SMI-S appears.
Linux systems installation Command View AE Suite will then be started after installation is complete. If you do not want to start the services after installation is complete, choose n. CAUTION: The services of XP Command View AE Suite products whose versions are earlier than 5.7 are not started by choosing y. If you want to start the services of XP Command View AE Suite after installation is complete, manually start the services.
Linux systems installation SNMP Trap note Settings for the SNMP Trap reception function Entering the installation directory Installation directory confirmation message Specifying the Common Component database files Specifying the Device Manager database files Entering IP address and port number 107
Linux systems installation Settings for the SMI-S Provider service SSL settings for SMI-S Changing the port number Two-way authentication for object operations and event indications Settings for SMI-S agent Specifying the host name for SMI-S agent 108
Linux systems installation Specifying the SLP daemon settings Setting services to start after installation (appears during installation) Installation package confirmation message Secure Socket certificates note 4-2-3 Performing an upgrade installation or a reinstallation WARNING: Do not cancel in the middle of an upgrade installation or re-installation, as doing so could corrupt the files.
Linux systems installation same directory. The previous TIA.properties file is saved as TIA.properties.old in the same directory. IMPORTANT: If the hdvmcli.properties file contains multiple entries of the same key with different values, the value of the most recently specified key overrides the others. Although key duplication does not affect Device Manager CLI operations, we do not recommend that you specify the same key more than once with different values.
Linux systems installation In version 5.0 or later, user information is managed by using the user management functionality of XP Command View AE Suite Common Component. The registered user information is migrated to the XP Command View AE Suite Common Component repository when the Device Manager server program is started for the first time after the upgrade installation.
Linux systems installation If you attempt to install Device Manager whose version or revision is earlier than the already installed Device Manager, an upgrade error message for Device Manager is displayed, and the installation is interrupted. 7. When the Common Component services are running in a non-cluster environment, a message indicating that the installer will stop these services is displayed. If you want to stop the installation, enter n. If you want to continue the installation, enter y.
Linux systems installation CAUTION: If you manually perform a backup or export operation, you can specify the directory in which the backup or export data will be stored. If a backup or export operation during installation fails, the installation stops. If the installation has stopped under these circumstances, confirm that the backup or export operation can be performed manually, and then perform the installation again.
Linux systems installation Upgrade error message for Device Manager Selection message for backing up the database Selection message for exporting the database Confirmation message for backup directory deletion Confirmation message for export directory deletion 4-3 Verifying Device Manager installation This section describes the procedure for verifying that the Device Manager server and XP Command View AE Suite Common Component have been installed correctly.
Linux systems installation CAUTION: Even if installation of Device Manager fails, the GO menu command for starting Device Manager might appear in the Dashboard of other XP Command View AE Suite products. To remove GO, a user with User Management permissions must execute the following command. When this command is executed, the XP Command View AE Suite Common Component services must be running.
Linux systems installation /bin/hcmdssrv -start server HBase If Common Component still does not start, stop Common Component and the XP Command View AE Suite services again: /bin/hcmdssrv -stop Delete the files: # /usr/bin/rm -rf /var/ /tmp/*.pid Start Common Component: /bin/hcmdssrv -start server HBase 4.
Linux systems installation installation-directory-for-the-Device-Manager-server/suitesrvcntl status_hdvm • To start the Device Manager server and Common Component, execute the following command: /bin/hcmdssrv -start Services of other XP Command View AE Suite products whose versions are 5.7 or later are also started at the same time. For details, see CAUTION below.
Linux systems installation Table 4-6 Resident processes of the Device Manager server and Common Component (In Linux) Process name Function webcont.sh XP Command View AE Suite servlet service installation-directory-for-CommonComponent/CC/web/containers/HiCommand/webcont.sh installation-directoryfor-CommonComponent/httpsd/sbin/http sd XP Command View AE Suite common web service Multiple processes of this might be started.
Linux systems installation Table 4-7 Backing up and restoring verses exporting and importing Item Backing up and restoring Exporting and importing Conditions for the machine The following must be the same in • used for the restore the backup source machine and the destination or the import restore destination machine: destination • Types, versions, and revisions • of the installed XP Command View AE Suite • Installation locations for each XP The XP Command View AE Suite products whose databases are to
Linux systems installation dir Specify the absolute path of the directory, on the local disk, that stores backup files of the Device Manager server database. Do not specify a path that includes a space. CAUTION: Make sure that no files or subdirectories are in the directory specified for the dir option. If there are any files or subdirectories in the directory, the backup processing will be aborted.
Linux systems installation type Specify the name of the XP Command View AE Suite product to be restored. To restore the Device Manager database only, specify DeviceManager. To restore all the XP Command View AE Suite product databases at once, specify ALL. To restore the databases when you are uninstalling and then reinstalling all the XP Command View AE Suite products, specify ALL.
Linux systems installation 4-5-3-1 Notes when migrating the database The following are notes for the databases, types, versions, and user information of the XP Command View AE Suite on the migration source and migration destination servers. Notes for databases, types, and versions of the XP Command View AE Suite products: • The database of an XP Command View AE Suite product that is not installed on the migration destination server cannot be migrated.
Linux systems installation 4-5-3-4 Exporting the database at the migration source server To export the database of Device Manager, a directory for temporarily storing the information of the database, and a directory for storing the archive file are required. Each of these directories requires the as much capacity as the total size of the following two directories: • • The directory storing the Device Manager database.
Linux systems installation Specify this option to stop the XP Command View AE Suite services and to start HiRDB automatically as preparation for processing the database. After the command is executed, the XP Command View AE Suite services and HiRDB are started. Note that the services of XP Command View AE Suite products whose versions are earlier than 5.7 are not started and stopped automatically. 4. Transfer the exported file to the migration destination server.
Linux systems installation manual for each product. To specify multiple product names, use a comma as the delimiter between the names. To migrate the databases of all the installed XP Command View AE Suite products at a time, specify ALL. The databases of the XP Command View AE Suite installed on the migration destination server are automatically selected and migrated.
Linux systems installation 2. Enter the following command to make sure that Device Manager server is not running: installation-directory-for-the-Device-Manager-server/suitesrvcntl status_hdvm This command outputs the following messages: The status_hdvm request was accepted. The Device Manager server is stopped. This indicates that Device Manager is not running. 3.
Linux systems installation 4-6 Uninstalling the Device Manager server and related products This section describes how to uninstall Device Manager and its related products. CAUTION: You must restore the kernel parameters after uninstalling the Device Manager server. To restore the kernel parameters that have been set, see section 4-7 .
Linux systems installation 2. Back up the database of the Device Manager server. For details about how to back up the database, see subsection 4-5-1 . 3. Enter the Device Manager package removal command: Move the current directory to the root (/), and then execute the following command: installation-directory-for-the-Device-Managerserver/Uninstall/uninstall.sh 4. A message indicating that uninstallation will start appears. Press the Enter key to continue. 5.
Linux systems installation Uninstallation start message Message that confirms stopping of services (appears during uninstallation) Setting services to start after uninstallation (appears during uninstallation) Uninstallation completion message 4-7 Setting kernel parameters and shell restrictions Before installing the Device Manager server, you must set the OS parameters (kernel parameters and shell restrictions). If the kernel parameters have not been set correctly, installation fails.
Linux systems installation Max {currently-set-value-for-the-kernel-parameter*, recommended-value-for-XP-Command View-AE-Suite-Common Component + recommended-value-for-the-Device-Manager-server, recommended-value-for-HiRDB} • kernel.
Linux systems installation Table 4-9 Recommended values for kernel parameters (/etc/sysctl.conf) Kernel parameter Recommen ded value for HiRDB Recommended value for XP Command View AE Suite Common Component Recommended value for the Device Manager server kernel.msgmn i 32 32 0 48 kernel.sem 1024 9 1 1024 7200 80 44 32124 kernel.shmma x 200000000 11542528 74022920 200000000 kernel.shmmn i 2000 0 0 4096 kernel.
XP Command View AE Suite Common Component 5 XP Command View AE Suite Common Component XP Command View AE Suite Common Component provides features that are used by all XP Command View AE Suite products. Each XP Command View AE Suite product will bundle Common Component.
XP Command View AE Suite Common Component • If the previously installed Common Component version is newer than the installing Common Component version, the previously installed version is left intact. Whether Common Component is uninstalled or left in place during Device Manager uninstallation is determined by the following factors: • If any other XP Command View AE Suite products are using Common Component, Common Component will not be uninstalled.
XP Command View AE Suite Common Component KAPM05007-I Already started service. service-name=HBase Storage Mgmt Common Service 5-2-2 Stopping Common Component To stop Common Component in a Windows environment: • • • HBase Storage Mgmt Web Service HBase Storage Mgmt Common Service HiRDB When you stop the above services, you must also stop the services of XP Command View AE Suite at the same time.
XP Command View AE Suite Common Component NOTE: When stopping XP Command View AE Suite Common Component in a Linux environment, do not execute the stop command (hcmdssrv -stop) before Common Component has completed startup. Regardless of whether a resident process for the service is running, the service status displayed by the status option may indicate that the service has stopped, and the service may not be stoppable by the stop option. In such cases, reboot the system.
XP Command View AE Suite Common Component Table 5-2 Integrated log output Log Type Log Name Description Location (Windows) Location (Linux) Device Manager log file version installationfolder-for-theDevice-Managerserver\Server\lo gs installationdirectory-forthe-DeviceManagerserver/Server/lo gs Device Manager trace log file (Common Component) HDvMtrace* Trace log information output .log by Common Component and used by the Device Manager server.
XP Command View AE Suite Common Component Figure 5-1 Hitachi Network Objectplaza Trace Utility 2 screen 3. Type the desired number of trace log files, and then click OK. In Linux: The utility program is stored in the following path: /opt/hitachi/HNTRLib2/bin/hntr2util To specify the number of trace log files: 1. Log in to the system as root. 2. Execute hntr2util. A menu appears. 3. From the menu, select Number of log files. The submenu appears.
XP Command View AE Suite Common Component The utility program is stored in the following path: /opt/hitachi/HNTRLib2/bin/hntr2util To change the size of the trace log files: 1. Log in to the system as root. 2. Execute hntr2util. A menu appears. 3. From the menu, select Size of a log file. The submenu appears. Hitachi Network Objectplaza Trace Library 2 - Configuration Utility Rel 1.0 Type new file size [8-4096] (Type '!' to return) Current Size(KB): 256 New Size(KB): 4.
XP Command View AE Suite Common Component Table 5-3 The Device Manager server and Common Component ports Component Network Port Device Manager agent 24041/tcp Description Used for the Device Manager agent's daemon process (or service). You can change the port after installation using the server.agent.port property. NOTE: For more information see HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide.
XP Command View AE Suite Common Component /bin/hcmdssrv -stop The following shows an example of executing the command: # /opt/CVXPAE/Base/bin/hcmdssrv -stop 3. Edit the setup file, and change the port number. For details about each port's setup file, see sections 5-4-2-1 to 5-4-2-5 below. 4. Start the service of the Device Manager server, the services of other XP Command View AE Suite, and Common Component.
XP Command View AE Suite Common Component in /httpsd/conf/httpsd.conf 5-4-2-3 23017/tcp (used for HBase Storage Mgmt Common Service through an AJP connection) To change the port used for the HBase Storage Mgmt Common Service through an AJP connection, you must change the port number written in the following files: • Windows ○ worker.worker1.port in \CC\web\redirector\workers.properties, and ○ webserver.connector.ajp13.
XP Command View AE Suite Common Component in /HDB/conf/emb/HiRDB.ini ○ pd_name_port in /HDB/conf/pdsys ○ pd_name_port in /database/work/def_pdsys 5-5 Setup for starting a web application from web client This section describes how to change access information that is required to start web client, and how to register web applications that can be started from web client.
XP Command View AE Suite Common Component pass: Specifies the password for the user ID used to register or delete the user-defined application link. nolog: Suppresses outputting messages to the command line. However, even when this option is specified, messages for option errors are displayed. User-defined application file (the following shows coding examples in the user-defined application file): CAUTION: To code the user-defined application file, use ASCII code only.
XP Command View AE Suite Common Component • When adding a link for an application: C:\Program Files\CVXPAE\Base\bin\hcmdslink /add /file C:\SampleLink.txt /user system /pass manager • When deleting a link for an application: C:\Program Files\CVXPAE\Base\bin\hcmdslink /delete /file C:\SampleLink.txt /user system /pass manager Command execution examples (in Linux) • When adding a link for an application: # /opt/CVXPAE/Base/bin/hcmdslink -add -file /opt/SampleLink.
XP Command View AE Suite Common Component 253: Restoration failure 254: Backup failure 255: Abnormal termination For details about the errors, see the contents of the following log files. ○ In Windows: \log\hcmdsChangeURLn.log ○ In Linux: /var//log/hcmdsChangeURLn.log Procedure for and examples of executing the hcmdschgurl command To execute the hcmdschgurl command: 1.
XP Command View AE Suite Common Component 5-6 Settings when changing the network settings for the management server or when performing maintenance You first need to edit several settings files when you disconnect the network (to which the management server is connected) in order to change the network settings or to perform maintenance, or when you change the name of the management server. This section describes how to edit the settings files.
XP Command View AE Suite Common Component 4. Edit the pdutsys file and the def_pdutsys file. Change the value for the pd_hostname parameter to the loopback address 127.0.0.1. If the pd_hostname parameter does not exist, add the pd_hostname parameter to set a loopback address.
XP Command View AE Suite Common Component CAUTION: The host name must satisfy the following conditions: • Number of characters: no more than 32 bytes • Characters that are used: A to Z, a to z, 0 to 9, hyphens (-) Note that the host name cannot start with and end with a hyphen (-).
XP Command View AE Suite Common Component /HDB/conf/pdsys /database/work/def_pdsys 7. Edit the pdutsys file and the def_pdsys file. Change the value for the pd_hostname parameter to the loopback address 127.0.0.1. If the pd_hostname parameter does not exist, add the pd_hostname parameter, specifying the loopback address. The following describes the storage destinations for the pdutsys file and def_pdutsys file.
XP Command View AE Suite Common Component Security settings can also be specified from web client. However, if the system is in a cluster configuration, the settings from web client are only applied to the executing node. To apply the settings to the standby node, switch the nodes, and then specify the same settings. For details on how to operate web client, see the HP StorageWorks XP Command View Advanced Edition software Device Manager user guide. CAUTION: When installing version 5.
XP Command View AE Suite Common Component 5-7-4 password.min.numeric Specifies the minimum number of numeric characters the password must contain. Specify a value in the range from 0 to 256. If you specify 0, no restriction applies. Default: 0 (no restriction) 5-7-5 password.min.symbol Specifies the minimum number of symbols the password must contain. Specify a value in the range from 0 to 256. If you specify 0, no restriction applies. Default: 0 (no restriction) 5-7-6 password.check.
XP Command View AE Suite Common Component When setting up a message, you must log in as a user who has the Administrator permissions in Windows, or as the root user in Linux. Warning banner settings can also be specified from web client. However, if the system is in a cluster configuration, the settings from web client are only applied to the executing node. To apply the settings to the standby node, switch the nodes, and then specify the same settings.
XP Command View AE Suite Common Component 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 screen. CAUTION: There are no restrictions on the characters usable in the message, other than that the character encoding must be Unicode (UTF-8).
XP Command View AE Suite Common Component If the locale option is omitted, you can edit the registered contents from web client also. However, available HTML tags are limited when you edit from web client. Return values 0: Normal termination 253: The number of characters in the message exceeds 1,000 characters. 255: Failure For details about errors, see the contents of the following log files. ○ In Windows: \log\hcmdsbannern.
XP Command View AE Suite Common Component business standards. The following table lists and describes the categories of audit log data that can be generated from HP XP products. Table 5-4 Categories and descriptions Categories StartStop Description Events indicating starting or stopping of hardware or software.
XP Command View AE Suite Common Component Table 5-4 Categories and descriptions Categories Description AnomalyEvent Events indicating that anomalies such as a threshold excess occurred. • Excess over network traffic threshold • Excess over CPU load threshold • Over-limit pre-notification or wraparound of audit log data temporarily saved internally Events indicating that abnormal communication occurred.
XP Command View AE Suite Common Component Table 5-5 Categories of information output to audit logs, and audit events Category Type Description Audit Event Severit y User deletion Successful single user deletion Failed single user deletion Successful multiple user deletion Failed multiple user deletion Successful password change by the administrator Failed password change by the administrator Failed in authentication processing for verifying old password Successful change of login user's own password (
XP Command View AE Suite Common Component Table 5-5 Categories of information output to audit logs, and audit events Category Type Description Audit Event Severit y Database area creation or deletion Successful database area creation using the hcmdsdbsetup command Failed database area creation using the hcmdsdbsetup command Successful database area deletion using the hcmdsdbsetup command Failed database area deletion using the hcmdsdbsetup command Successful data output using the hcmdsdbauthmove comma
XP Command View AE Suite Common Component The following describes the storage destination for the auditlog.conf file. • For Windows: \conf\sec\auditlog.conf • For Linux: /conf/sec/auditlog.conf The table below shows the items that are set for the auditlog.conf file. Table 5-6 Items set for auditlog.conf Item Description Log.
XP Command View AE Suite Common Component Table 5-7 Log.Facility values and the corresponding values in syslog.conf Facility 18 19 20 21 22 23 Corresponding Values in syslog.conf local2 local3 local4 local5 local6 local7 * 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.
XP Command View AE Suite Common Component NOTE: In message-portion, a maximum of 953 single-byte characters are displayed.
XP Command View AE Suite Common Component Example of message-portion output for the Login audit event: CELFSS,1.1,0,KAPM01124-I,2006-05-15T14:08:23.1+09:00,HBaseSSO,managementhost,Authentication,Success,uid=system,,,,,,,,,,,,BasicLog,,,"The login process has completed properly." 5-9-4 Audit log message ID The following two types of audit log message IDs are output: 1.
XP Command View AE Suite Common Component "The login process has completed properly." 5-9-5-2 When output as processing results of Device Manager server When a request for server processing, such as changing the configuration or obtaining information, is received or a response is transmitted, information on the request or response is output in the message text. The message text format is described below, followed by a detailed description of the information contained in the message text.
XP Command View AE Suite Common Component Request reception (normal): unique-ID[ launch-session-ID][ launch-target-identifier] Response transmission (normal): unique-ID[ launch-session-ID] Request reception or response transmission (abnormal): unique-ID[ launch-session-ID] error-message-ID Table 5-12 Information output when a launch request is received or a response is transmitted Item Description Unique ID A unique request identifier. For response transmission, the unique ID of the request is output.
XP Command View AE Suite Common Component The IP address is displayed only when XP1024/XP128 is launched from Physical View (output example: loid=10.208.110.110). 2 The following examples show message text output when the server receives a launch request (when no error has occurred) or sends a response to a launch request (when no error has occurred).
XP Command View AE Suite Common Component "1183371423687 GetSupportedSizeRange inParams={ElementType=3,Goal=//192.168.0.1/root/smis/current:HITACHI_St orageSetting.InstanceID='RAID5'} objectPath=/root/smis/current:HITACHI_StoragePool.InstanceID='XP12000.
XP Command View AE Suite Common Component Table 5-16 Information output in detail message parameters Item Description Element A character string that indicates the element name. For information on the elements that are output and their meanings, see Table 5-20. However, Table 5-20 might not contain some displayed characters Format: info='...' Attribute values specified for the element are output. When two or more attribute values are output, they are separated by a comma (,).
XP Command View AE Suite Common Component Table 5-18 Targets output in detail messages Output Character String Full Name Operation JrnlPool LDEVForVolMi g ListView JournalPool LDEVForVolumeMigration LogF LGrp LU LUFormat LUN LUNGrp LunScan LogFile LogicalGroup LogicalUnit LogicalUnitFormat LUN LUNGroup LunScan LUSE Msgs ObjForLGrp LUSE Messages ObjectForLogicalGroup ObjName Port PortCtrl Rep RepCtrlPair ReqStatus Rule SrvI SpareDrive SA ObjectName Port PortController Replication ReplicationContro
XP Command View AE Suite Common Component Table 5-19 List of options of detail messages Output Character String Operation exist force Creates a virtual volume in an existing virtual volume group. • If the target is LUSE Creates an LUSE in the logical unit that already has paths. • If the target is Virtual Volume suspend lusekeep noformat numOfLUs:n split resync restore remainMigraion unassign The virtual volume associated with a pool is disassociated from the pool and deleted.
XP Command View AE Suite Common Component Table 5-20 Attribute output sequence for each element of a detail message Output Character String Full Name and Content Attribute Value Output Sequence1 CommandComplet e CommandComplete (Information required by clients when the Get Request Status command is issued) CommParameters (Information about how to access the storage subsystem) Component (Information about the storage subsystem configuration) Condition (Limits the results of the Get command by using the
XP Command View AE Suite Common Component Table 5-20 Attribute output sequence for each element of a detail message Output Character String Filt FreeLUN FreeSpace3 Full Name and Content Attribute Value Output Sequence1 (Information about the log file name) name Filter (Limits the results of the Get command) FreeLUN (Information about availability of the LUN in the host storage domain) FreeSpace (Information about the free space in the array group of the storage subsystem) -- Host Host (Host info
XP Command View AE Suite Common Component Table 5-20 Attribute output sequence for each element of a detail message Output Character String IPAddress JrnlPool Full Name and Content IPAddress (The IP address of the port controller) JournalPool (Journal group information of XP Continuous Access Journal Software) LDEV LDEV (Information about the LDEV) LDKC LogicalDKC (Logical DKC of the storage subsystem) LogicalGroup (Groups hosts, host storage domains, or other logical groups) LGrp LicenseKey Lis
XP Command View AE Suite Common Component Table 5-20 Attribute output sequence for each element of a detail message Output Character String Full Name and Content Attribute Value Output Sequence1 MFRepI MFReplicationInfo (Information about replication of mainframe volumes) MFVolI MFVolumeInfo (Access information between the main frame host and LDEV) Message (Asynchronous message) Messages (Groups the Message elements) ObjectName (Sets the object name of the Device Manager server)
XP Command View AE Suite Common Component Table 5-20 Attribute output sequence for each element of a detail message Full Name and Content Attribute Value Output Sequence1 (A pair of the name and value) name, value2 Path Path (Information about the path) PDEV PDEV (Information about PDEV) Port (Information about the port) , name, port ID, domain ID of host storage domain, SCSI ID, LUN assigned to 4 path, device number for logica
XP Command View AE Suite Common Component Table 5-20 Attribute output sequence for each element of a detail message Output Character String ReqStatus RSIMI RsltObj Rule SA SIMI SizeCond SlctCond SlctItem SortCond SortItem SrchCond SrvI Subscrbr Full Name and Content RequestStatus (Returns the status of the preceding request) RSIMInfo (RSIM information of the storage subsystem) ResultObject (A single row in a list displayed by the ListView elements) Rule (ACL rule of the Device Manager serve
XP Command View AE Suite Common Component Table 5-20 Attribute output sequence for each element of a detail message Output Character String Full Name and Content Attribute Value Output Sequence1 Timestamp Timestamp (Time when the message was created in the Device Manager server) Topic (Name of the message topic) UserGroup (Groups users according to their permissions) URLLink (Links between a HP object and an application) -- Topic UGrp URLLink User (Account information of a single user of Device Ma
XP Command View AE Suite Common Component 1 The lower field of each element indicates the output order represented with the names used within Device Manager. This information is output as the storage subsystem model, and represented by the common output name indicated in the table below.
Setup for managing copy pairs 6 Setup for managing copy pairs This chapter discusses the following setup requirements: • • • • Server requirements for managing copy pairs Host requirements for managing copy pairs Disk array requirements for managing copy pairs Creating configuration definition files for XP RAID Manager 6-1 Server requirements for managing copy pairs This section describes the requirements for the Device Manager server to manage copy pairs.
Setup for managing copy pairs Figure 6-1 Example of pair operations when local management is used When local management is used: • From the P-VOL or S-VOL, LUN security must be set for the host. LUN security from the P-VOL and S-VOL must be set for at least one host, although the host to which LUN security from the P-VOL is assigned and the host to which LUN security from the SVOL is assigned do not need to be the same. • The host must recognize the P-VOL or S-VOL.
Setup for managing copy pairs • If there are multiple NICs on the host, the Device Manager agent and XP RAID Manager must use the same IP address. • XP RAID Manager must have fewer than 32 running instances. Figure 6-2 shows a configuration example of operating copy pairs when central management is used. Figure 6-2 Example of pair operations when central management is used When central management is used: • From the P-VOL or S-VOL, LUN security must be set for the host.
Setup for managing copy pairs • If there are multiple NICs on the host that centrally manages copy pairs, the Device Manager agent and XP RAID Manager must use the same IP address. • XP RAID Manager must have fewer than 32 running instances. CAUTION: When central management is used, copy pairs of a host that uses a platform on which the Device Manager agent cannot be installed can be recognized.
Setup for managing copy pairs Table 6-2 Disk array requirements Disk Array Function Requirements XP24000/XP200 00 XP12000/XP100 00/SVS200 XP1024/XP128 XP512/XP48 XP Continuous Access Journal Software (available for XP24000/X P20000 and XP12000/X P10000/SV S200) XP Continuous Access Journal Software must be enabled. There must be a fibre-channel connection between the two ports used for an MCU-RCU path.
Setup for managing copy pairs 6-4 Creating configuration definition files for XP RAID Manager This section describes copy pair management in conjunction with Device Manager when XP RAID Manager or XP Protection Manager is already being used for copy pair management. 6-4-1 Using Device Manager when XP RAID Manager manages existing copy pairs If a copy pair is already managed by XP RAID Manager, the copy pair can be managed by Device Manager once Device Manager is installed.
Setup for managing copy pairs CAUTION: You cannot use the configuration definition file created by this function to create copy pairs using Device Manager. • You cannot use Device Manager to delete an invalid configuration file if the file was created by this function. Either delete this configuration file from the host, or edit it on the host.
Device Manager server security 7 Device Manager server security This information is under export control and is not available on the web. To view the contents of this chapter, see the manual that is shipped with the product.
Device Manager server properties 8 Device Manager server properties This chapter discusses the following: • • • • • • • • • • • Overview of Device Manager server properties Server configuration properties Database properties Logger properties Dispatcher properties MIME properties Client properties SNMP trap log output function properties Mainframe host agent properties Report function properties Restrictions on web clients connected to the Device Manager server 8-1 Overview of Device Manager server pro
Device Manager server properties CAUTION: You should not undertake the task of optimizing these attributes unless you are an expert, since minor changes could severely impact the performance of the Device Manager server. • Logger properties (see section 8-4 ) include directives that configure the Device Manager server's logging module, including the names, locations and verbosity levels of the various operation and error log files.
Device Manager server properties Table 8-1 Summary of Device Manager property files Property Description Location server.https.port Assigns the port used for the Device Manager secure HTTP server. 3 subsection 8-2- server.http.default Sets the name of the default index page for the Device Manager web server. 4 server.http.request Sets the read-blocking timeout of the HTTP socket .timeout connection (in milliseconds). 5 server.http.
Device Manager server properties Table 8-1 Summary of Device Manager property files Property Description Location server.base.initial This property allows you to specify whether to synchronize subsection 8-2synchro the management information database and the displayed 23 information (XP Command View AE Suite Common Repository) when you start Device Manager. server.cim.agent server.cim.
Device Manager server properties Table 8-1 Summary of Device Manager property files Property Description dbm.startingCheck.r Specifies the number of times the Device Manager server etryCount retries the checking whether DBMS has started. dbm.startingCheck.r Specifies the interval (in seconds) at which the Device etryPeriod Manager server retries the checking whether DBMS has started.
Device Manager server properties Table 8-1 Summary of Device Manager property files Property Description server.dispatcher.e Defines the end time of the interval for stopping SNMP ndTimeOfIgnoringCon communication alerts. nectionAlert server.dispatcher.d Determines whether or not port 162 is used as an SNMP aemon.receiveTrap trap.
Device Manager server properties 8-2-1 server.http.host This property designates either the host name or IP address for the host on which the Web server function of Device Manager operates. To specify the IP address, use one of the following formats: IPv4 format: x.x.x.x (x: integer from 0 to 255) IPv6 format: Specify hexadecimal numbers by using colons (:). You can also use a short format. You can only use global IPv6 addresses.
Device Manager server properties 8-2-5 server.http.request.timeout This property sets the read-blocking timeout of the HTTP socket connection (in milliseconds). It can be used to enable or disable the SO_TIMEOUT setting for client-connection sockets. Reading from the input stream associated with a socket will block for only this amount of time before the socket expires. Its default value is 5000 (5 seconds).
Device Manager server properties 8-2-10 server.http.socket.linger This Boolean property toggles whether the SO_LINGER socket attribute is enabled for client connections with the Device Manager server. Setting this flag to its default value means a linger-onclose timeout of 60 seconds is applied to socket connections. You should only modify this property if you are an expert System Administrator seeking to fine-tune the server's performance. Default: true 8-2-11 server.http.socket.
Device Manager server properties assigned domain name, so some logged requests might still be recorded as a numeric IP address, even with this flag turned on. NOTE: While translation of the IP address to a domain name can assist analysis of the server's access logs, reverse-DNS lookups are expensive in terms of resources, and this feature may significantly degrade the server's performance, especially on a slow network. You should keep the setting at the default value for better performance.
Device Manager server properties 8-2-20 server.installTime This property contains the Device Manager installation date. Format: dd/mm/yyyy:HH:MM:SS ZZZZ (dd:day, mm:month, yyyy:year, HH:hour, MM:minute, SS:second ZZZZ (TimeZone). Default: dd/mm/yyyy:HH:MM:SS ZZZZ (Install date) 8-2-21 server.base.home This property contains the installation directory of Common Component, which is set by the Device Manager installer. You should not change this property under normal circumstances.
Device Manager server properties 8-2-26 server.cim.support.job This property specifies whether a method for creating or deleting a volume, setting or releasing a path, setting or canceling security for a LUN, or creating or deleting a LUSE volume is executed asynchronously or synchronously. If you set this property to true, the method is executed asynchronously. If you set this property to false, the method is executed synchronously.
Device Manager server properties 8-2-32 server.mail.enabled This property determines whether to report an alert that has occurred in a storage subsystem to the user by email. To enable the email notification function, set this property to true. Default: true 8-2-33 server.mail.from This property changes the mail address of the notification source (sender). If no value is specified or the specified value is invalid, the default value is set. Default: hdvmserver 8-2-34 server.mail.smtp.
Device Manager server properties 8-2-38 server.mail.alert.status This property specifies the severity of alerts to be reported by the email notification function of the Device Manager server. The Device Manager server reports alerts whose severity is higher than the severity specified for this property. The following values (listed in ascending order of importance) can be specified: Normal, Service, Moderate, Serious, Acute Default: Moderate 8-2-39 server.subsystem.ssid.
Device Manager server properties 8-3-3 dbm.startingCheck.retryPeriod This property specifies the interval (in seconds) the Device Manager server will retry whether DBMS has started when the server is launched. The specifiable values range from 0 to 60 (seconds) As a general rule, you do not need to change this setting. Default: 10 seconds 8-4 Logger properties Logger properties are contained in the logger.properties file.
Device Manager server properties 8-4-4 logger.hbase.loglevel In this property, you can specify the verbosity level for each operation (trace) log file and error log file written by Common Component. The log files are HDvMtracen.log, HDvMGuiTracen.log, and HDvMGuiMessagen.log,where n is an integer that represents the backup number for the file. Each logging event has its own importance level independent from its type (error, warning, and information).
Device Manager server properties 8-5-1 server.dispatcher.agent.priority This property assigns the priority for Device Manager agent threads. Valid values are between 1 and 10 (1 = minimum priority; 5 = normal priority; 10 = maximum priority). You should change the default value only if you need to fine-tune the agent dispatcher's performance.
Device Manager server properties 8-5-8 server.dispatcher.daemon.receiveTrap This property determines whether or not port 162 is used as an SNMP Trap listener. The Device Manager can use SNMP to detect command completion and hardware issues. If port 162 is in use, Device Manager can use polling to determine these issues, but using SNMP is preferred.
Device Manager server properties NOTE: When the client is accessing the server through a proxy server and the connection timeout of the proxy is shorter than the timeout of this property, the notification message may be lost, because the timeout of the proxy server cuts the connection before the Device Manager server can send the response to web client. If this is the case, please set the timeout for this property to a time shorter than the timeout of the proxy. Default: 300 seconds 8-7-3 client.
Device Manager server properties Before changing this property, stop HBase Storage Mgmt Common Service. After changing this property, restart HBase Storage Mgmt Common Service. For details about how to start and stop HBase Storage Mgmt Common Service, see section 5-2 . Default: true 8-7-6 client.report.csv.format.escaped This property enables you to switch the format of the CSV report for information of the storages and users that are managed by Device Manager.
Device Manager server properties ○ XP Command View AE Suite common trace log file ○ Event log (Application log) file / syslog file • The output destinations for log messages related to system startup processes: ○ Trace log file ○ Error log file* * This file is output only when the severity is Error, Critical, or Alert. For details on the severity, see Table 8-2. By setting the customizedsnmptrap.customizelist property and by setting the customizedsnmptrap.
Device Manager server properties The following shows an example of a customized log configuration: customizedsnmptrap.customizelist = \ .1.2.3:6:1:Information:$a$e$g$s$1$2, \ .1.3.6.1.4.1.2854:6:1:Warning:$e$a$s$3$2$1$g, \ .1.3.6.1.4.1.116.3.11.4.1.1:6:1:ERROR:$a$s, \ .1.3.6.1.4.1.116.3.11.4.1.1:6:100:Information:$a$s Figure 8-1 Sample Log Customization 8-9-1 customizedsnmptrap.customizedSNMPTrapEnable This property allows you to enable the SNMP trap log output function.
Device Manager server properties Default: Device-Manager-server-installation-directory/DvMReport/CSV 8-12 Restrictions on web clients connected to the Device Manager server To restrict web clients that can connect to the Device Manager server: 1. If XP Command View AE Suite products whose versions are earlier than 5.7 are installed, stop their services. For details about how to stop these services, see the manual for your product version. 2. Stop the XP Command View AE Suite services and Common Component.
Device Manager server properties The following shows an example of registering hosts in the httpsd.conf file: order allow,deny allow from 127.0.0.1 10.0.0.1 2001::123:4567:89ab:cdef allow from 10.1.0.0/16 2001:0:0:1230::/64 Figure 8-3 Example of host registration 5. Register hosts to the server.http.security.clientIP property. For details on how to set the server.http.security.clientIP property. 6. Start the XP Command View AE Suite services and Common Component.
Linking Device Manager with other products 9 Linking Device Manager with other products This chapter discusses the following: • • • Linking with XP External Storage Software Settings for starting Storage Essentials from the dashboard Settings for starting XP Command View AE Suite Product from HP SIM 9-1 Linking with XP External Storage Software IMPORTANT: The XP External Storage Software function is available only for the XP12000, XP10000, and SVS200.
Linking Device Manager with other products /common In the StorageEssentials.conf file, specify the LaunchURL parameter in the format shown as follows: Format of the StorageEssentials.conf File LaunchURL= Storage-Essentials-URL In Storage-Essentials-URL, specify the URL used to start Storage Essentials. For details about this URL, see the Storage Essentials documentation.
Linking Device Manager with other products \bin\hcmdshpsimcert /import /host host-name-of-HP-SIM-server The following shows an example of executing the command: C:\Program Files\CVXPAE\Base\bin\hcmdshpsimcert /import /host host01 ○ In Linux: /bin/hcmdshpsimcert import -host host-name-of-HP-SIM-server The following shows an example of executing the command: # /opt/CVXPAE/Base/bin/hcmdshpsimcert -import -host host01 CAUTION: For h
Linking Device Manager with other products Console will be domain-name?HP-SIM-user-name. 7. Using the GUI of HP SIM, add permission for users who are to use XP Command View AE Suite. Add tool No. 1 (essential) and any of the tools from No. 2 to No. 4, shown in the following table, to the toolbox. Permissions used when users operate XP Command View AE Suite Products are determined by the tools to be added. The correspondence between tool names and permissions of Device Manager is shown in the table below.
Linking Device Manager with other products 9-3-2 User account and permission HP SIM users operate Device Manager by using a temporary account. For this account, you cannot perform any operations related to an account such as changing a profile, assigning a resource group, or locking an account. Even if the same user name as the HP SIM user name is registered in an XP Command View AE Suite, the user ID is handled as another account.
Linking Device Manager with other products 4. Choose Run Now to start web client of Device Manager. Possible causes and actions to be taken when an authentication error occurs: The following table lists and describes the possible causes and actions to be taken when an authentication error occurs during startup of the Device Manager web client. Table 9-4 Possible causes and actions to be taken when authentications error occurs Cause Action Upper limit of single sign-on requests was exceeded.
Troubleshooting 10 Troubleshooting This chapter discusses the following: • • • Problems and solutions Collecting maintenance information Obtaining alert information by using the email notification function 10-1 Problems and solutions Table 10-1 lists the common problems and solutions after installing Device Manager on a Windows or Linux platform. For a listing of Device Manager Error Codes, contact your HP support representative for assistance. Table 10-1 General troubleshooting information No.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 4 DESCRIPTION: The installation or uninstallation of the Device Manager server failed and the message KAPM04156-E Service is running. service=service-name was output to the following log files: In Windows: installation-folder-forCommonComponent\log\hcmdswebn.log installation-folder-forCommonComponent\log\hcmdsweb2n.log In Linux: /var/installation-directoryfor-CommonComponent/log/hcmdswebn.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 5 DESCRIPTION: An error occurs during Device Manager server installation. CAUSE: There is an error in the environment or settings on the installation destination machine. SOLUTION: If an error occurs during the Device Manager server installation, take one or more of the following actions. If you cannot resolve the problem, contact maintenance personnel.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 1 For details about collecting maintenance information, see section 10-2 . 2 For details about performing backup manually, see subsection 3-2-3 for Windows, or subsection 4-2-3 for Linux. For details about using commands to back up a database, see subsection 3-7-1 for Windows, or subsection 45-1 for Linux.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 6 DESCRIPTION: In Windows, reports are not displayed when the HTML button is clicked in the Storage Utilization by Host Reports subwindow or Storage Utilization by Logical Group - Reports subwindow in the web client. CAUSE: Either too many storage subsystems have been selected, or the size of the memory heap used by the Device Manager server is too small.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 7 DESCRIPTION: In Linux, reports are not displayed when the HTML button is clicked in the Storage Utilization by Host - Reports subwindow or the Storage Utilization by Logical Group - Reports subwindow in the web client. CAUSE: Either too many storage subsystems have been selected, or the size of the memory heap used by the Device Manager server is too small.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 8 DESCRIPTION: Database registration SOLUTION: Perform the following procedures in attempts fail when the Device Manager the order given to restore the system. server is installed in a Windows cluster environment. If the database has been backed up: CAUSE: The termination code of the 1 Perform recovery from the database backup. hcmdsdbclustersetup command is 250 For details, see subsection 3-7-2 .
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 10 DESCRIPTION: The service discovery feature is not available, because the SLP service (or the SLP daemon) failed to start during Device Manager server installation. CAUSE: An unexpected error occurred during the SLP service (or the SLP daemon) startup. SOLUTION: Set the service discovery feature. For details about how to do this, see section A-5.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 14 DESCRIPTION: Internal Server Error is displayed in the web client, and logon and operations cannot be performed. CAUSE: Either HBase Storage Mgmt Common Service is stopped or the Web container of Device Manager that runs on HBase Storage Mgmt Common Service is stopped. SOLUTION: Perform the procedure shown below.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution 1 Make sure that the javacoreprocessID.occurrence-date(YYMMDD)occurrence-time(HHMMSS).txt files are output to the directory below. If no file is output, the cause of the error might not be insufficient memory heap size. In such a case, contact maintenance personnel.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution If the description java.lang.OutOfMemoryError occurred. exists in the file: Perform the following in order: ○ Open the newest javacoreprocessID.occurrence-date(YYMMDD)occurrence-time(HHMMSS).txt file that you found in step 2. In the file, find the text Heap Status. In the Heap Status section, each heap area is recorded as follows: DefNew::Eden:60979K/69952K(87.2 %) Max:69952K(87.2%) DefNew::Survivor:0K/8704K(0.
Troubleshooting Table 10-1 General troubleshooting information No. Problem Solution If the description An unexpected exception has been detected in native code outside the VM. exists in the file: Perform the following in order: ○ Make sure the javalog01.log file is output to the directory below. If the file is not output, the cause of the error might not be insufficient memory heap size. In such a case, contact maintenance personnel.
Troubleshooting The cvxpaegetlogs command has the following format: In Windows: \bin\cvxpaegetlogs /dir directoryname [/type application-name] [/arc archive-file-name] In Linux: /bin/cvxpaegetlogs -dir directory-name [-type application-name] [-arc archive-file-name] You can specify the following options for the cvxpaegetlogs command: dir Specify the name of the directory on a local disk that stores maintenance information.
Troubleshooting # /opt/CVXPAE/Base/bin/cvxpaegetlogs -dir /opt/logs_work -type DeviceManager An example of collecting maintenance information for XP Command View AE Suite is shown below. In this example, the archive file named arc_log is created under the logs_work directory.
Troubleshooting 10-3 Obtaining alert information by using the email notification function The email notification function notifies users, by email, of the contents of alerts that occurred in the storage subsystem and were detected by the Device Manager server. To use this function, you need to configure the SMTP server, a Device Manager user, and the Device Manager server.
Troubleshooting ○ ○ ○ ○ ○ ○ ○ server.mail.enabled(see subsection 8-2-32 ) server.mail.from (see subsection 8-2-33 ) server.mail.smtp.host (see subsection 8-2-34 ) server.mail.smtp.port (see subsection 8-2-35 ) server.mail.smtp.auth (see subsection 8-2-36 ) server.mail.alert.type (see subsection 8-2-37 ) server.mail.alert.
Troubleshooting To execute the hdvmmodmailuser command, the following conditions must be satisfied: • A user who executes the hdvmmodmailuser command has the Administrator permission for Windows, or the root permission for Linux • A user who is specified when executing the hdvmmodmailuser command has the Admin permission of Device Manager • • The Device Manager server service is stopped. The Common Component services are running.
Troubleshooting 10-3-5 The template file used by the email notification function The contents of the email sent to users by the email notification function are set in the template file mail-alert-detection.txt. If necessary, you can edit this file to customize the contents of the email. The mail-alert-detection.
Troubleshooting Table 10-2 Parameters that can be set in the template file Parameter Name Description occurrenceTime Time at which the Device Manager server obtained alert information Display format: yyyy/mm/dd hh:mm:ss hh is displayed by using 24-hour display. Set the mail-alert-detection.txt file so that all of the conditions shown below are satisfied.
Appendix A Overview of CIM/WBEM Appendix A Overview of CIM/WBEM This appendix gives an overview of CIM/WBEM provided by Device Manager, and explains how to set up CIM/WBEM. A-1 Device Manager and CIM/WBEM Device Manager supports WBEM defined by the standards-setting organization DMTF. WBEM is a standard proposed by the DMTF for managing networked devices, including hosts and storage subsystems, over the Internet.
Appendix A Overview of CIM/WBEM NOTE: If you need to specify the namespace dmxx (xx is an abbreviation for the version number) that was supported by Device Manager 5.8 or earlier versions, contact maintenance personnel. The following table lists and describes the correspondence between the namespaces supported by Device Manager and SMI-S versions. Table A-1 Correspondence between namespaces and SMI-S versions Namespace SMI-S current smisxx smis10 -- 1.0.2 smis11 -- 1.1.0 smis12 current 1.2.
Appendix A Overview of CIM/WBEM Service discovery feature Device Manager provides the service discovery feature based on the Service Location Protocol (SLP). The SLP is undergoing standardization by IETF and provides a way to discover desired services available in a network. For details on the SLP, see RFC2608. Just by specifying the type of service, SLP clients can obtain information (such as URLs) about how to access the available services, and information about service attributes.
Appendix A Overview of CIM/WBEM If any service program using the same port is running, change the port number for the service program. If any service program is running (normally, another WBEM service program) that is using the same port to be used by an object operation feature, the object operation feature is not available.
Appendix A Overview of CIM/WBEM ProxyPass / http://127.0.0.1:5988/ ProxyPassReverse / http://127.0.0.1:5988/ A-3-2 Setting up the ports used by CIM/WBEM features A-3-2-1 Opening and closing ports according to the communication type Ports can be opened or closed according to the communication type used by CIM/WBEM features. Security can be enhanced by closing unused ports. To open or close the port: 1. Using the server.cim.support.protocol property in the property file (server.
Appendix A Overview of CIM/WBEM 1. Change the port number set in the Device Manager server property file (server.properties). For details on the Device Manager server property file, see subsection A-4-1. To change the HTTP port number: Change the port number set in server.cim.http.port. To change the HTTPS port number: Change the port number set in server.cim.https.port. 2. Restart the Device Manager server. In Windows: Select Start, Programs, XP Command View AE, Device Manager, and then Stop Server.
Appendix A Overview of CIM/WBEM A-4-1 The server.properties file When executing CIM, set up the following properties in addition to the regular settings. A-4-1-1 server.cim.support This property specifies whether to use the CIM interface. Set the server.cim.support property to true. The default is false, which specifies that the CIM interface is not used. # whether the server supports CIM interface or not server.cim.support={true | false} A-4-1-2 server.cim.support.
Appendix A Overview of CIM/WBEM A-4-2-1 classpath This property sets classpath required for operating the WBEM Service. Do not change the value of this property. A-4-2-2 BaseDir This property specifies the name of the base directory of classpath required for operating the WBEM Service. Do not change the value of this property. A-4-2-3 propdir This property specifies the directory containing the cimom.properties file. Do not change the value of this property.
Appendix A Overview of CIM/WBEM To register the SLP service: 1. Install Device Manager, and then log in as a member of the Administrator group. 2. Display the command prompt and move to the folder containing the OpenSLP executable file. OpenSLP is installed in the following folder: installation-folder-for-the-Device-Managerserver\Server\wsi\bin\windows 3. Register the SLP service as a Windows service.
Appendix A Overview of CIM/WBEM Execute the following command: # chkconfig --level 01345 slpd off # chkconfig --del slpd # rm -f /etc/init.d/slpd A-5-2 Starting and stopping the service discovery feature A-5-2-1 In Windows To manually start the SLP service, perform either of the following procedures: • From Administrative Tools, choose Services and then Service Location Protocol to start the SLP service.
Appendix A Overview of CIM/WBEM A-6 The performance information acquisition feature Device Manager can acquire performance information of a storage subsystem by using the CIM interface. The performance information that Device Manager can acquire is shown below.
Appendix A Overview of CIM/WBEM Figure A-2 System configuration example when performance information of a storage subsystem is collected Management server A management server is a server in which Device Manager server version 5.9 or later is installed. You must set the management server so that CIM/WBEM can be used. For details on how to set up CIM/WBEM, see section A-3.
Appendix A Overview of CIM/WBEM supported by the Device Manager agent, see the HP StorageWorks XP Command View Advanced Edition software Device Manager agent installation and configuration guide Storage subsystem This is a storage subsystem whose performance information is to be acquired. For details on the microcode versions that can use the performance information acquisition feature, see subsection 1-4-1 .
Appendix A Overview of CIM/WBEM For the server.cim.agent property in the server.properties file of the Device Manager server, specify the name of the host where the Device Manager agent is installed. After specifying the host name, restart the Device Manager server. NOTE: Make sure that the host name specified for the server.cim.agent property matches the host name registered in Device Manager for the host that acquires performance information.
Appendix A Overview of CIM/WBEM A-6-2-5 Format of the perf_findcmddev command The perf_findcmddev command allows you to set the command device in the perf_cmddev.properties file. To execute this command, a user must have Administrator permissions (for Windows) or root permissions (for Linux).
Appendix A Overview of CIM/WBEM You can use the -file option to specify the desired file name. To specify the file name, you can use an absolute or relative path. If the specified file already exists, a message asking if you want to overwrite that file appears. If you do not specify the -file option, the perf_cmddev.properties file will automatically be overwritten.
Glossary Glossary Glossary term Definition ACL Address Control List AJP Apache JServ Protocol CHA Channel Adapter CIDR Classless Inter-Domain Routing CIM Common Information Model CIMOM CIM Object Manager CLI Command Line Interface CSR Certificate Signing Request CTP Conformance Testing Program DNS Domain Name Server DST Daylight Saving Time GB gigabyte(s) IEEE Institute of Electrical and Electronics Engineers JDK Java Development Kit KB kilobyte(s) LAN local-area network L
Glossary Glossary term Definition SVP The service processor on an XP24000/XP20000, XP12000/XP10000/SVS200 or XP1024/XP128 or XP512/XP48 disk array. This is the laptop mounted on the front of the unit (inside the cabinet).
Index Index A account.lock.num, 151 administrator privileges: executing command with, 47 alert information: obtaining by using email notification function, 216, 230 audit log: format of output data, 160; message ID, 162 B backing up server database: Windows, 81 C categories of information output to audit logs in Device Manager, 156 changing network settings for management server, 146 CIM: overview, 235 CIM properties: cimom.properties file, 242; jserver.properties file, 241; server.
Index microsoft cluster service environment: registering Device Manager™ services, 69 migrating server database, 84 MIME properties, 203 report function, 207 restoring server database, 120; Linux, 120 server.mail.smtp.host, 198 server.mail.smtp.port, 198 server.subsystem.ssid.
Index start, 77; server not in Services screen, 77 X XP Business Copy Software, 181 XP Continuous Access Journal Software, 181 XP Continuous Access Software, 181 XP Snapshot, 181 255
