Hitachi Command Suite Global Link Manager Installation and Configuration Guide (Web Version) Document Organization Product Version Getting Help Contents MK-92HC215-00
© 2014 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use.
Contents Preface.................................................................................................. ix Intended audience..................................................................................................... x Product version..........................................................................................................x Release notes............................................................................................................ x Document revision level..
Upgrade Installation of Global Link Manager..................................................... 2-12 Performing an Unattended Installation of Global Link Manager........................... 2-19 Unattended Installation..........................................................................2-20 Contents of the Installation-Information Settings File............................... 2-21 About the Log File.................................................................................
Changing the Port Number Used for the Internal Communication (Single Sign-on) of Hitachi Command Suite Common Component................................................... 3-49 Changing Port Numbers for Accessing HiRDB.................................................... 3-49 Editing the HiRDB.ini file........................................................................ 3-49 Editing the pdsys file............................................................................. 3-49 Editing the def_pdsys file..
5 Security Settings for Communication...................................................... 5-1 Security Settings for Communication Between a Server and Clients............................ 5-2 Security Settings for Communication Between a Server and an LDAP Directory Server. 5-2 Advanced security mode..........................................................................................5-2 6 Using Global Link Manager with Other Products......................................
A Notes on Using HDLM Version 5.8 or Later, DMP, or HP-UX Multipathing.. A-1 Hitachi Command Suite Common Agent Component..................................................A-2 Changing Firewall Settings for HDLM or for DMP....................................................... A-3 Windows host where HDLM version is from 5.8 or later to 6.5 or earlier............... A-3 Windows host where HDLM version 5.8 or later or DMP ..................................... A-4 HDLM for Linux................................
viii Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
Preface This manual describes the installation, setup, and server operation of the Hitachi Global Link Manager program (abbreviated hereafter to Global Link Manager).
Intended audience This document is intended for storage administrators who use Global Link Manager to operate and manage storage systems, and assumes that readers have: • Knowledge of how to set up an environment for multipath management software and how to operate it • Knowledge of the server OS (Windows) Product version This document revision applies to Hitachi Global Link Manager version 8.0.0 or later. Release notes Read the release notes before installing and using this product.
Chapter/Appendix Description Chapter 5, Security Settings for Communication on page 5-1 Describes how to set up security for communication between a server and clients, and between a server and an LDAP directory server. Chapter 6, Using Global Link Manager with Other Products on page 6-1 Describes the settings for linking Global Link Manager with other products.
Convention Description Bold Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Italic Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Note: Angled brackets (< >) are also used to indicate variables. Monospace Indicates text that is displayed on screen or entered by the user.
Logical capacity unit Value 1 TB 1,024 GB or 1,0244 bytes 1 PB 1,024 TB or 1,0245 bytes 1 EB 1,024 PB or 1,0246 bytes Accessing product documentation The Global Link Manager user documentation is available on the Hitachi Data Systems Portal: https://portal.hds.com. Check this site for the most current documentation, including important updates that may have been made after the release of the product.
xiv Preface Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
1 Global Link Manager System Configuration and Requirements This chapter describes the Global Link Manager system configuration and requirements.
Global Link Manager Overview Global Link Manager uses multipath management software path control functionality to provide integrated path management for large-sized system configurations. While multipath management software manages paths for a host, Global Link Manager batch-manages paths for multiple hosts.
Figure 1-1 Example of a Global Link Manager System Configuration Global Link Manager includes the following features: Collective Management of Path Information of Multiple Hosts By using remote operations from the Global Link Manager GUI, you can collectively set up multiple hosts and collect information from the multipath management software on multiple hosts. Operations can be managed from one console without having to log in to each host.
Summarizing the Path Statuses for the Whole System Global Link Manager can also display a summary of path statuses (the number of paths in each status). You can check path availability in the entire system without having to check the status of each host individually. Support for Path Bandwidth Control Global Link Manager enables you to specify the format for viewing path information, such as by storage system or by CHA port.
Figure 1-2 Basic Global Link Manager System Configuration The system components in this figure are explained below. Global Link Manager server The machine on which the Global Link Manager program is installed. The Global Link Manager server collects system configuration information from each host and then provides the information to the Global Link Manager client.
Manager, Device Manager, Tuning Manager, and other Hitachi Command Suite server products, and is always updated to the latest version. Global Link Manager client A machine on which the Global Link Manager GUI is used. The Global Link Manager GUI provides a user interface for managing hosts by using Global Link Manager. Remote management client A Hitachi Command Suite Common Agent Component instance or the computer the instance is installed on that connects to and controls a host via a LAN.
SNMP transfer destination server A machine that receives alert information transferred from the Global Link Manager server by means of SNMP traps. You must set up the Global Link Manager server to transfer alert information to the SNMP transfer destination server. For details about the setup for transferring alert information, see Setting Up Alert Transfer on page 3-71. SMTP server A machine that sends email about alert information received by the Global Link Manager server.
Table 1-2 Requirements for the Machine on Which the Global Link Manager Server Program Is Installed Item Applicable OSs#1 Requirements • Windows Server 2008 R2 (x64) (SP1)#2 (Datacenter, Enterprise, Standard) • Windows Server 2012 (x64) #2 (Datacenter, Essentials, Standard) • Windows Server 2012 R2 (x64) #2 (Datacenter, Essentials, Standard) Free disk space 5 GB or more#3 (for a new installation) Cluster software (when a cluster One of the cluster services of the following OSs: system is to be crea
If you want to specify different drives as the installation location of Global Link Manager and the storage location of the database files, the following free space is required: Disk on which Global Link Manager is to be installed: 1.5 GB or more Disk on which the database files are to be stored: 4 GB or more The guidelines for the maximum number of hosts, multipath LUs, and paths that can be managed are described in the following table.
Table 1-4 Guide to maximum numbers when using DMP or HP-UX multipathing Multipath management software Maximum Number of Paths Maximum Number of Multipath LUs DMP (Solaris) 1024 512 DMP (Windows) 1024 256 HP-UX multipathing 1024 512 Notes: 1-10 • If the Global Link Manager version is earlier than 8.0, Global Link Manager cannot coexist with a Hitachi Command Suite product whose version is earlier than 4.0.
Global Link Manager Client Requirements The following table describes the system requirements for using the Global Link Manager GUI. Table 1-5 Requirements of the Client System for Using the Global Link Manager GUI Applicable OSs and other items Windows • Windows Server 2008 (x64) (no SP)#1 Applicable Web browsers and requirements • Internet Explorer 9.0 • Internet Explorer 9.0 Windows Server 2008 R2 (x64) (SP1)#1 • Internet Explorer 9.
Applicable OSs and other items Applicable Web browsers and requirements (Enterprise 64-bit Edition, Professional 64-bit Edition, Ultimate 64-bit Edition) • • Internet Explorer 10.0 • Internet Explorer 11.0#2 • Firefox ESR 17.0.x • Firefox ESR 24.1.x Red Hat Enterprise Linux 5.2 • Firefox ESR 17.0.x Red Hat Enterprise Linux 5.6 • Firefox ESR 17.0.x Red Hat Enterprise Linux 5.8 • Firefox ESR 17.0.x Red Hat Enterprise Linux 6.2 • Firefox ESR 17.0.x • Firefox ESR 24.1.
Notes: • If you are using version 9 or later of Internet Explorer, do not enable ActiveX Filtering. Host Requirements To use Global Link Manager to manage hosts, installation and environment setup of multipath management software must be completed on the hosts. You can use IPv4 or IPv6 to connect to Global Link Manager if the host HDLM version is 6.0 or later, or if you are using DMP or HP-UX multipathing.
the HDLM documentation. To manage a VMware version of HDLM, a remote management client is required. For more information about remote management clients, see the documentation regarding the VMware versions of HDLM. Note that some OSs are not supported for Global Link Manager even if they are supported for HDLM. The following table lists OSs that are not supported for Global Link Manager.
Applicable OS DMP version Prerequisite program Windows Server 2003 R2 (x86) (SP2) (Datacenter Edition, Enterprise Edition, Standard Edition) Windows Server 2008 (IPF) (no SP) Windows Server 2008 (x64) (no SP) (Datacenter, Enterprise, Standard) Windows Server 2008 (x86) (no SP) (Datacenter 32-bit, Enterprise 32bit, Standard 32-bit) Solaris9 (SPARC) DMP 5.0 (MP3) Solaris10 (SPARC)# • Global Link Manager agent 6.2 or later • JRE 1.4.2 or JRE 5.
Limitations on Operations in an IPv6 Environment Note the following limitations when you use Global Link Manager in an IPv6 environment: • Global Link Manager does not support IPv6-only environments. Set up the OS such that both IPv4 and IPv6 can be used. • You can only use global addresses as IPv6 addresses. Global-unique local addresses (site-local addresses), and link-local addresses cannot be used.
The following shows an example of how to specify these settings: Listen 22015 Listen [::]:22015 Caution: Do not delete or edit the existing Listen line. If you do this, communication using IPv4 will no longer be available. Settings When Establishing SSL Communication Remove the hash mark (#) at the beginning of the line Listen [::]:22016 (when the default setting is used). Specify the same port number as specified in the Listen line for IPv4.
Figure 1-3 Flow of Global Link Manager Tasks Installing multipath management software and setting up its environment Set up multipath management software on all hosts that are integrated and managed by Global Link Manager. For details about the requirements for installing the multipath management software on a host, see Host Requirements on page 1-13.
procedures, see the Hitachi Command Suite Installation and Configuration Guide. Note: If you are installing a Device Manager agent solely to use Global Link Manager, you must configure the host information necessary for Global Link Manager, instead of the Device Manager server information, when you install or set up the Device Manager agent. For details about how to configure the host information necessary for Global Link Manager, see Help. ¢ ¢ When the HDLM version of a host is 5.
1-20 Global Link Manager System Configuration and Requirements Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
2 Installing Global Link Manager This chapter describes Global Link Manager installation. When installing Global Link Manager in a cluster environment, see Chapter 4, Installing Global Link Manager Clusters on page 4-1.
Types of Global Link Manager Installations This section explains how to install Global Link Manager. The following types of installation are available: • New installation# • Reinstallation# • Upgrade installation# • Removal # An unattended installation is also available. An unattended installation allows a user to install Global Link Manager without needing to respond to instructions in dialog boxes.
• Products other than Hitachi Command Suite products are not using port numbers 22015, 22016, 22017, 22018, 22032, and 45001 to 49000#. If other products are using these ports, you cannot start Global Link Manager, even if the installation of Global Link Manager has finished normally. Make sure that no other products are using these ports, and then begin the installation. You can change the port numbers 22015 to 22018, and 22032 after the installation.
the product might not work properly if another user connects to the console session. • Dialog boxes used for operating Windows services, such as Computer Management or Services, are not displayed. • If a Hitachi Command Suite product has already been installed, HiRDB/ EmbeddedEdition _HD1 is already running. To use Hitachi Command Suite products, HiRDB/EmbeddedEdition _HD1 must be always running. In the list in the Services panel, make sure that HiRDB/EmbeddedEdition _HD1 is running.
4. Click the Add button, and then specify the Global Link Manager installer (setup.exe). The Global Link Manager installer (setup.exe) is added to the list. 5. Select the check box next to the Global Link Manager installer (setup.exe), and then click the OK button. Installing Global Link Manager for the First Time If other Hitachi Command Suite products have already been installed in a cluster configuration, remove the cluster configuration before installing Global Link Manager.
If any services of Hitachi Command Suite Common Component or of another Hitachi Command Suite product are running, the Stopping the Services of Hitachi Command Suite Products dialog box appears. Click the Next button to stop those services. If the cluster configuration has not been removed, the installation is canceled. Remove the cluster configuration, and then install Global Link Manager. 3. Click the Next button. The Setup of the Installation Folder dialog box appears.
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\HiCommand Base 64\InstallPath 4. Click the Next button. The Setup of the Storage Destination for Database Files of Hitachi Global Link Manager dialog box appears. If you do not want to accept the default folder, specify another folder. The rules for specifying a folder are as follows: ¢ ¢ ¢ ¢ Do not specify a storage destination folder for database files that is directly under a drive letter (such as C:\ or D:\). The maximum length of an absolute path is 64 bytes.
¢ The path name must not contain any names reserved by the OS (CON, AUX, NUL, PRN, CLOCK$, COM1 to COM9, and LPT1 to LPT9). The following is the default database storage destination for the Hitachi Command Suite products: specified-installation-folder-for-Hitachi-Global-Link-Manager\databackup 6. Click the Next button. The Setup of Information about the Server of Hitachi Global Link Manager dialog box appears.
When specifying an IPv6 address, enclose the IP address in square brackets ([ ]). Note: When you install Global Link Manager on a server on which Device Manager is installed, specify a port number other than 162 for the port that receives SNMP traps. When the reception of SNMP traps is being used in Device Manager, if you specify 162 for the port that receives SNMP traps during the installation of Global Link Manager, you will no longer be able to start Device Manager. 8. Click the Next button.
12. Click the Finish button to finish the installation. The operating status of the Hitachi Command Suite Common Component services varies depending on the setup status specified during installation. To log in to Global Link Manager and start operations, you must set up the initial license information. See Setting Up License Information During Initial Login on page 2-26. When Using Report Output of Path Availability Information For the hosts running HDLM version 5.
The Confirmation of Setup Status of Common Component Database of Hitachi Command Suite dialog box appears. Check the setup status. The three setup statuses are: ¢ Non-cluster configuration ¢ Executing node of cluster configuration ¢ Standby node in a cluster configuration 4. Click the Next button. If Windows Firewall is installed, the Windows Firewall dialog box appears. Check the settings in the dialog box, and then click the Next button.
¢ For details on how to change the port number of HBase 64 Storage Mgmt Web Service, see Changing Port Numbers for Accessing the HBase 64 Storage Mgmt Web Service on page 3-47. 7. Click the Next button. When installation has been completed normally, the Installation Complete dialog box appears. 8. Click the Finish button to finish the installation. The operating status of the Hitachi Command Suite Common Component service varies depending on the setup status specified during installation.
• Upgrading to a later release of the same major version • Upgrading from version 6 or version 7 to version 8.0 or later • Migrating the data of the currently-installed Global Link Manager to a different server and then upgrading to version 8.0 or later ¢ ¢ Using Global Link Manager version 6 or 7 on an OS that is not supported by Global Link Manager version 8.
Note: If you register Global Link Manager as an exception in the Windows Firewall exceptions list, it might take approximately 15 minutes more to install Global Link Manager. If you enabled Windows Firewall after installing Global Link Manager, you must manually add Global Link Manager to the exceptions list. For details on how to manually add Global Link Manager to the exception list, see Settings for Windows Firewalls on page 3-54. 5.
Upgrading from version 6 or version 7 to version 8.0 or later To upgrade from version v6 or v7 to v8.0 or later, perform the following steps: 1. Insert the Global Link Manager installation DVD-ROM. In the displayed window, click the Install button next to Hitachi Global Link Manager Software. If the window does not appear, directly execute the installer (setup.exe). The installer is stored in drive-where-installation-DVD-ROM-is-set:\HGLM.
Note that a space character cannot be used at the beginning or end of a folder name. ¢ The path name must not contain any names reserved by the OS (CON, AUX, NUL, PRN, CLOCK$, COM1 to COM9, and LPT1 to LPT9). The following is the default database storage destination for the Hitachi Command Suite products: specified-installation-folder-for-Hitachi-Global-Link-Manager\databackup 5. Click the Next button.
When you click the Yes or No button, the Confirmation Before Installation dialog box appears. 8. Confirm that the displayed installation settings are correct, and then click the Install button. Installation starts. During the installation, dialog boxes indicating the processing status appear. The Global Link Manager database is updated by running an upgrade installation (except when the database files are damaged).
• The storage destination for the database files changes to the following: original-storage-destination-path-for-database-files\x64 • If you upgrade from v6 or v7 to v8, maintenance information is deleted. Therefore, collect any necessary maintenance information before upgrading to v8. For details on how to collect maintenance information, see Hitachi Global Link Manager Help for the version that will be upgraded.
Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64dbsrv /start 3. Execute the following command to update the Global Link Manager database: Global-Link-Manager-installation-folder\bin\hglamdbupdate The following confirmation message appears. Enter Y to continue. "Are you sure to execute the database update command? (Y/N)" You can specify the following options in the hglamdbupdate command.
file, see Contents of the Installation-Information Settings File on page 2-21. 2. Execute the installation command (installhglm)# to start the installation. 3. The necessary responses are automatically determined based on the installation-information settings file. 4. Installation is completed. Log data about the progress and result of installation is output.
Item Description You can also use a backslash (\), and colon (:) as the path delimiter. If you do not specify this option, the default location for the installation-information settings file is used. For details on this file, see Contents of the Installation-Information Settings File on page 2-21. /s Specify this option to suppress the output of a message asking for confirmation of the requested operation. Executing the command starts the installation.
Define the responses for an unattended installation in the [INSTALLATION_SETTINGS] section. Note the following when you define the responses: • A line that begins with a hash mark (#) is treated as a comment line. If you specify # at the beginning of the section name, all the properties defined in this section will be treated as comments, and the default values will be applied. • Any line feed is ignored.
Key name HGLM_IPADDRESS Description • %SystemRoot%\SysWOW64\ • %SystemRoot%\system32\ • %ProgramFiles%\WindowsApps\ Key is specifiable for: Specify the IP address or host name of the New installation Global Link Manager server. When specifying an IPv6 address, enclose the IP address in square brackets ([ ]). The default is IP-address-of-the-Global-LinkManager-server. HGLM_PORT HGLM_SNMPTRAP Specify the port number of the Global Link Manager server. The default is 22015.
Key name Description Key is specifiable for: The default is usually C:\Program Files \HiCommand\databackup . About the Log File For an unattended installation, the results of the installation processing are output to the log file installhglm_yyyy-mm-dd_hh-mm-ss.log. The installhglm_yyyy-mm-dd_hh-mm-ss.log file will be output to the following location: system-drive:\installhglm_yyyy-mm-dd_hh-mm-ss.
Double-click DLMManager from the list of services, and then click the Stop button. c. Delete all folders and files in the following folder: HDLM-installation-folder\host d. Start the HDLM manager. Choose Start, Control Panel, Administrative Tools, and Services. Double-click DLMManager from the list of services, and click the Start button.
3. Click the Next button. The Confirmation of Setup Status of Common Component Database of Hitachi Command Suite dialog box appears. Check the setup status. The three setup statuses are: ¢ Non-cluster configuration ¢ Executing node of cluster configuration ¢ Standby node in a cluster configuration 4. Click the Next button.
http://IP-address-or-host-name-of-the-Global-Link-Managerserver:port-number-for-HBase-Storage-Mgmt-Web-Service-of-theGlobal-Link-Manager-server/GlobalLinkAvailabilityManager/ Example: http://127.0.0.1:22015/GlobalLinkAvailabilityManager/ When specifying an IPv6 address, enclose the IP address in square brackets ([ ]).
2-28 Installing Global Link Manager Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
3 Setting Up Global Link Manager This chapter describes how to set up Global Link Manager, including how to start and stop Global Link Manager, and how to back up and restore the Global Link Manager database. Some Windows Server 2012 terms refer to items that are assigned different names in other Windows server OSs, but which have similar functions. This chapter uses the names that appear in OSs that are not Windows Server 2012 unless otherwise indicated.
□ Setting a Warning Banner □ Generating Audit Logs □ Setting Up Alert Transfer □ Settings Required to Authenticate Users by Using an External Authentication Server 3-2 Setting Up Global Link Manager Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
Notes When Executing Commands This section describes notes when executing commands that are required for specifying Global Link Manager settings. Login Users To execute the commands described in this manual, you must log in as a member of the Administrators group. Elevating to Administrator Privileges If the UAC feature is enabled in a Windows OS, when you execute a command, you might be asked to elevate your current privileges to Administrator privileges.
Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /start If other Hitachi Command Suite products have been installed on the same machine, the services of these Hitachi Command Suite products are started along with Global Link Manager. Note, however, that the services are not started in the following cases: • When Hitachi Command Suite Common Component has already been started In these cases, see the manual for each product to start the services.
Mgmt Common Service Resident Processes of Hitachi Command Suite Common Component The following table shows the resident processes of Hitachi Command Suite Common Component. Table 3-1 Resident Processes of Hitachi Command Suite Common Component Process name hcmdssvctl.exe Function Hitachi Command Suite servlet service.
products are already installed. This section also describes how to change the time, if necessary, after installing Global Link Manager. Note: If the machine time is changed while Hitachi Command Suite Common Component is running, Hitachi Command Suite products including Global Link Manager might not operate correctly. We recommend that you change the machine time before installing Global Link Manager.
• Migrating (exporting and importing) the database • Changing the storage location of the database To perform database operations, you need to execute a backup and restore of the Global Link Manager property files and the path availability information (path status log). The property files to be backed up and restored are as follows: • server.properties • logger.properties • database.
Backing Up the Global Link Manager Database Hitachi recommends that you back up the database of Global Link Manager and the databases of Hitachi Command Suite products regularly.
Global-Link-Manager-installation-folder\bin\hglambackup /dir backup-destination-folder-name Use an absolute path to specify backup-destination-folder-name. When you specify an existing folder, it should be an empty folder. The following characters can be used for backup-destination-folder-name: A to Z, a to z, 0 to 9, period (.), and underscore (_). You can also use a backslash (\), colon (:), and forward slash (/) as the path delimiter.
Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64backups /dir backup-destination-folder-name For backup-destination-folder-name, specify the absolute path of a folder on the local disk. When you specify an existing folder, it should be an empty folder. When you execute the above command, a backup file (backup.hdb) will be created for the databases of the Hitachi Command Suite products installed on the server on which the above command is executed.
Right-click the resource name and choose Properties. In the Policies tab, select If resource fails, attempt restart on current node and If restart is unsuccessful, fail over all resources in this service or application. If you use Microsoft Failover Cluster (for Windows Server 2012): Right-click the resource name and choose Properties. In the Policies tab, select If resource fails, attempt restart on current node and If restart is unsuccessful, fail over all resources in this Role. 3.
3. Execute the following command to restore the property files and the path availability information (path status log): Global-Link-Manager-installation-folder\bin\hglamrestore /dir name-of-the-folder-for-storing-the-backup-data For name-of-the-folder-for-storing-the-backup-data, specify an absolute path for the folder in which the data backed up using the hglambackup command is to be stored. 4.
Note: If you restore the databases by specifying /type ALL, the states of other Hitachi Command Suite products return to the states that existed when backup data was acquired. When you execute the command, make sure there will be no problems in having those states return to the ones that existed when backup data was acquired. 6.
replacement process. In Hitachi Command Suite products, you can migrate the database by using the hcmds64dbtrans command. The hcmds64dbtrans command migrates all information stored in the database of each Hitachi Command Suite product as well as user information managed by the Hitachi Command Suite Common Component.
¢ ¢ The database can be migrated when the database configuration (Small or Medium) is the same on both the migration source and the destination server, or when the database configuration on the migration destination server becomes much larger than that on the source server. In the database configuration on the migration source server, if the number of the management target resources exceeds 70% of the management limit, the database cannot be migrated to a database that has the same configuration.
Exporting the Database at the Migration Source Server To export the database of Global Link Manager, a folder for temporarily storing the information of the database, and a folder for storing the archive file are required.
For work-folder, specify an absolute path for the folder that temporarily stores the database information. Specify an empty folder on the local disk. If you do not specify an empty folder, export processing will be interrupted, in which case you will need to specify an empty folder and then re-execute the hcmds64dbtrans command. For archive-file, specify an absolute path for the archive file of the database to be exported.
4. Use the cluster software to suppress failover of the resource group. If you use Microsoft Failover Cluster: Right-click the resource name and choose Properties. In the Policies tab, select If resource fails, do not restart. 5. Execute the following command to start the Hitachi Command Suite product services: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /start 6.
Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 2. Use the cluster software to enable failover of the following resources: ¢ HBase 64 Storage Mgmt Web Service ¢ HBase 64 Storage Mgmt Common Service ¢ Other Hitachi Command Suite product resources If you use Microsoft Failover Cluster (for OSs other than Windows Server 2012): Right-click the resource name and choose Properties.
Execute the following command: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64dbsrv /start 3. Execute the following command to import the database: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64dbtrans /import /workpath work-folder /file archivefile /type HGLAM For work-folder, specify an absolute path for the folder in which the archive file will be expanded. Specify an empty folder on the local disk.
have to be migrated, use the /type option and specify all products other than Replication Monitor when you execute the command. 4.
Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64dbtrans /import /workpath work-folder /file archivefile /type HGLAM For work-folder, specify an absolute path for the folder in which the archive file will be expanded. Specify an empty folder on the local disk. If you do not specify an empty folder, import processing will be interrupted, in which case you will need to specify an empty folder and then reexecute the hcmds64dbtrans command.
Global-Link-Manager-installation-folder\bin\hglamimport /dir name-of-folder-for-storing-exported-data For name-of-folder-for-storing-exported-data, specify an absolute path for the folder that stores the data exported by the hglamexport command. After the import processing is complete, the Global Link Manager database is updated. Caution: The property files will not be imported because the environments on the migration-source and migration-destination servers might be different.
Files: • server.properties (Global Link Manager server settings file) • logger.properties (Global Link Manager log file settings file) • database.properties (Global Link Manager database settings file) File format: property-name=value #comment • Separate the property name and the value by using an equal sign (=). • When inserting a comment line, begin the line by using a hash mark (#). To edit the property file: 1. 2.
• Specify ASCII code characters. • For a value for which true or false is to be specified, if you specify another value, false is assumed. • To specify a folder, enter two consecutive path delimiters (\). Coding example: server.pathreport.log_location=C:\\Program Files\\HiCommand\ \HGLAM\\pathreport The following table describes the properties that are used to change the Global Link Manager server settings. Table 3-3 Global Link Manager Server Properties (server.properties) No.
No. 5 Property Name server.dbms.sweep_init Description Specifies the time from server startup until free-page collection starts. Specifiable value: 1 to 60 (minutes) Default: 5 6 server.dbms.sweep_interval Specifies the interval between freepage collections. Specifiable value: 60 to 100000 (minutes) Default: 10080 7 server.agent.max_retry_count Specifies the maximum number of retries for checking whether Hitachi Command Suite Common Agent Component has finished processing.
No. Property Name Description Default: 10000 13 server.snmp.auto_set Specifies whether to automatically configure alert notification for a host when the host is added or host information is updated. Specify true to automatically configure alert notification. Specify false not to automatically configure alert notification. Note: To configure alert notification for each host, specify false. Specifiable value: true or false Default: true 14 server.snmp.trap_community Specifies the SNMP Community value.
No. Property Name Description Manager is installed is changed, reception of SNMP traps becomes unavailable. Specifiable value: String of 39 characters or less Default: --#1 17 gui.indicator.auto_refresh_interval Specifies the automatic refresh interval for the Dashboard menu in the Global Link Manager GUI. Specifiable value: 1 to 10000 (minutes) Default: 1 18 server.snmp_transfer.enable Specifies whether to enable alert transfer. Specify true to enable alert transfer. Specify false to disable it.
No. Property Name Description Default: None 20 server.snmp_transfer.port_num Specifies the port number of the alert transfer destination server. If a firewall is set up between the Global Link Manager server and the destination server, be sure to set the IP address and port number of the destination server for the firewall. Specifiable value: Number from 1 to 65535 Default: 162 21 server.snmp_transfer.critical_enable Specifies whether to transfer Critical level alerts during alert transfer.
No. 26 Property Name server.snmp_transfer.host_enable Description Specifies whether to transfer alerts whose category is Host during alert transfer. Specify true to transfer alerts of the Host category. Specify false not to transfer them. Specifiable value: true or false Default: true#2 27 server.snmp_transfer.hdlm_enable Specifies whether to transfer alerts whose category is HDLM during alert transfer. Specify true to transfer alerts of the HDLM category. Specify false to not transfer them.
No. Property Name Description this value and the value of server.network_scan.thread_num is less than the value of server.thread.max_size. Specifiable value: 1 to 50 Default: 5 33 server.pathreport.enable Specifies whether to allow Global Link Manager to acquire the path availability information (path status log) from HDLM for output in a report. Specify true to allow Global Link Manager to acquire the information.
No. Property Name Description CSV file is output to that subfolder in the following format: PathStatusLog_host-IPaddress_date.csv For the IPv6 format, (:) is changed to (-) in host-IP-address. When the path availability information (path status log) has already been output and you want to change the folder in which the information is stored, you need to move the output path availability information (path status log) to a new folder.
No. Property Name Description has the oldest date. Therefore, if needed, back up those files. For a large-scale configuration, the default value is the approximate size of the information for about 90 days. Specifiable value: 10 to 1024 (MB) Default: 100 36 server.network_scan.thread_num Specifies the maximum number of hosts that can be added concurrently for network scanning. Note: When you change this value, specify a value so that the sum of this value and the value of server.auto_refresh.
No. Property Name Description Default: None (Reports are output using the format of the latest version.) 41 gui.ham.view If gui.export.version is version 7.6 or earlier, specifies whether to export the following information to a CSV file when paths obtained from managed hosts are in the HAM configuration: • Original LDEV ID of the secondary volume • Original storage system name of the secondary volume Specifiable value: true or false Default: true 42 gui.id_take_over.view If gui.export.
No. Property Name Description also output. Specify false to not output the physical information. Specifiable value: true or false Default: true 44 getlogs.pathreport.get_mode Specifies the method of acquiring the path availability information (path status log), as the Global Link Manager diagnostic information#5. Specifiable value: 0 to 3 0: Does not acquire the path availability information (path status log). 1: Acquires, for all hosts, logs from the 90 days preceding the current date.
No. Property Name Description Specifiable value: Character string Default: None (The information is acquired in the order of the date in the file name from oldest to newest.) 47 getlogs.pathreport.endDate Specifies the end date for acquisition of the path availability information (path status log), as the Global Link Manager diagnostic information#5. Specify a date in the yyyymmdd format. This value takes effect only when the value set for getlogs.pathreport.get_mode is 2.
No. Property Name Description This value takes effect only if the value set for server.hdvm.ldevlabel.acquisiti on.enable is true. Specifiable value: Character string Default: None 50 server.hdvm.ldevlabel.acquisition.en Specifies whether to enable able acquisition of LDEV label information. Specify true to enable it. Specify false to disable it. Specifiable value: true or false Default: false #1 These values are replaced with the values that are specified during the installation.
accounts other than the Windows local system account (SYSTEM) and Global Link Manager administrator. #5 For details on how to acquire Global Link Manager diagnostic information, see Diagnostic Batch Collection about the Global Link Manager Server on page 8-7. #6 For details about the port numbers used by Device Manager servers, see the Hitachi Command Suite Configuration Reference Guide.
Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 2. Export the path availability information (path status log). Execute the following command: Global-Link-Manager-installation-folder\bin\hglamexport /dir export-destination-folder-name Use an absolute path to specify export-destination-folder-name. When you specify an existing folder, make sure that the folder is empty. The following characters can be used for export-destination-folder-name: A to Z, a to z, 0 to 9, period (.
Table 3-4 Global Link Manager Log File Properties (logger.properties) No. 1 Property Name Description logger.max_backup_index Specifies the maximum number of log file backups. Specifiable value: 1 to 16 Default: 10 2 logger.max_file_size Specifies the maximum log file size. Specifiable value: 4096 to 2147483647 bytes (4 KB to approximately 2 GB) Default: 16777216 bytes (approximately 16 MB) 3 logger.syslog_level Specifies the logging level (threshold) for output to the OS event log or syslog.
No. 3 Property Name database.connection_ret ry_times Description Specifies the maximum number of connection retries. Specifiable value: 18 to 180 Default: 30 4 database.connection_ret ry_interval Specifies the connection retry interval. Specifiable value: 10 to 100 (seconds) Default: 30 5 database.connectionpool _retry_times Specifies the maximum number of retries for acquiring a connection from the connection pool. Specifiable value: 0 to 5 Default: 3 6 database.
Option description Table 3-6 hcmds64dbuser Command Options Option /newpass password Description Specify the password to be used for authentication when Global Link Manager accesses the database. The value specified for this option becomes the new authentication password. If this option is omitted, you will be prompted to enter a password.
• If you have changed the IP address of the management server before changing the settings files of Hitachi Command Suite products, write down the new IP address. • Do not change the settings in the cluster configuration file (the cluster.conf file). If other Hitachi Command Suite products have already been installed on the same machine, the services of these products are also started or stopped at the same time when you start or stop Hitachi Command Suite Common Component.
• The host name must be no more than 32 bytes. You can use the following characters: A to Z a to z 0 to 9 Note that the host name cannot start or end with a hyphen (-). If other Hitachi Command Suite products have already been installed on the same machine, the services of these products are also started or stopped at the same time when you start or stop Hitachi Command Suite Common Component. To change the host name of the management server: 1. Before changing the host name, write down the host name.
6. Change the host name for the management server, and then restart the computer. If you have changed the host name for the management server before changing the settings file for Hitachi Command Suite Common Component, restart the computer. 7. Execute the following command to make sure that Hitachi Command Suite Common Component is running: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /status 8.
Table 3-7 Ports Used by Hitachi Command Suite Common Component Network Port Description 22015/tcp#1 This port is used to access non-SSL HBase 64 Storage Mgmt Web Service. If you want to change this port number after installation, see Changing Port Numbers for Accessing the HBase 64 Storage Mgmt Web Service on page 3-47. 22016/tcp This port is used by Web browsers to access SSL HBase 64 Storage Mgmt Web Service.
the same time when you start or stop Hitachi Command Suite Common Component. To change the Hitachi Command Suite Common Component port numbers after installing the Global Link Manager server: 1. Execute the following command to stop Hitachi Command Suite Common Component: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 2. Change the port numbers. The method used depends on which port number you want to change.
To change the port number: 1. Open the user_httpsd.conf file at the following location: Hitachi-Command-Suite-Common-Component-installation-folder\uCPSB \httpsd\conf\user_httpsd.conf 2. If you want to change the port number for HTTP communication, change the port number in the Listen directive where 22015 is specified by default.
Changing the Port Number Used to Stop the HBase 64 Storage Mgmt Common Service To set the port that receives a stop request for HBase 64 Storage Mgmt Common Service, specify the port number in the usrconf.properties file. To specify the port used to stop HBase 64 Storage Mgmt Common Service: 1. Open the usrconf.properties file at the following location: Hitachi-Command-Suite-Common-Component-installation-folder\uCPSB \CC\web\containers\HiCommand64\usrconf\usrconf.properties 2.
Editing the def_pdsys file 1. Open the def_pdsys file at the following location: Hitachi-Command-Suite-Common-Component-installation-folder \database\work\def_pdsys 2. Change the port number in the entry pd_name_port=22032. Setting Up the Global Link Manager Server to Use the Global Link Manager GUI This section describes the settings for changing the URL used for starting the Global Link Manager GUI, and the settings for adding the Go menu and the Links menu item to the Global Link Manager GUI.
Adding the Go and Links Menus By using the Global Link Manager GUI, you can register links to any Web application or Web page. After you register links, the Go menu and its Links menu item are added to the Global task bar area in the Global Link Manager GUI.
Item Description using alphanumeric characters (maximum 256 bytes). This item is mandatory. @URL startup-URL Specify the URL to be started from the Global Link Manager GUI (maximum 256 bytes). IPv6 addresses cannot be used. Specify a host name for an IPv6 environment. @DISPLAYNAME display-in-linksdialog-box Specify the link name to be displayed in the Links dialog box (maximum 80 bytes). You can specify a Unicode code point in the range from U+10000 to U +10FFFF.
Table 3-12 Port Numbers Required for Communications between a Management Server and Management Client Port Number Source of Communication Destination of Communication 22015/tcp# Management client Management server This setting is required for non-SSL communications. 22016/tcp# Management client Management server This setting is required for SSL communications. Remarks #: The port number is changeable.
server.snmp.trap_port_num property in Changing Global Link Manager Server Settings on page 3-24. Settings for Windows Firewalls If you enable Windows Firewall after installing Global Link Manager, you must register Hitachi Command Suite Common Component and a port number that receives SNMP traps as an exception in the Windows Firewall exceptions list. To register Hitachi Command Suite Common Component and a port number as an exception: 1.
• When you install Hitachi Command Suite Common Component version 5.1 or later, the user account log function and password complexity check function will be enabled. These functions are enabled for users of all Hitachi Command Suite products, so the following problems might occur in operations of Hitachi Command Suite products that are version 5.0 or earlier: ¢ ¢ A user is unable to log in even with a correct user ID and password. The user account might be locked.
No. Property Name Description Specifiable value: 0 to 256 (characters) Default: 0 (no restriction) 3 password.min.lowercase Specifies the minimum number of lowercase letters the password must contain. If you specify 0, no restriction applies. Specifiable value: 0 to 256 (characters) Default: 0 (no restriction) 4 password.min.numeric Specifies the minimum number of numeric characters the password must contain. If you specify 0, no restriction applies.
How users are affected when the number of unsuccessful login attempts is changed If you change the value for the number of unsuccessful login attempts, the new value does not apply to users who have already failed to log in more times than the new value for the number of unsuccessful login attempts or to users with a locked user account. Security Settings Using the user.conf File The built-in account (user ID: System) is not automatically or manually locked by default.
Unlocking Accounts You use Global Link Manager GUI to unlock user accounts. For details about how to unlock user accounts, see online Help. If all user accounts are locked or all user accounts with Admin permissions for User Management are locked, Global Link Manager GUI cannot unlock the accounts. Follow the procedure below to unlock a user account with Admin permissions for User Management. To unlock a user account: 1. Make sure that Hitachi Command Suite Common Component is running.
After you unlock the user account with Admin permissions for User Management, use this account to log into Global Link Manager GUI, then unlock the other user accounts. Setting a Warning Banner In version 5.1 or later of Hitachi Command Suite products, an optional message (warning banner) can be displayed as a security risk measure at login. Issuing a warning beforehand to third parties that might attempt invalid access can help reduce the risk of problems such as data loss or information leakage.
including criminal investigations. Such information includes sensitive data encrypted to comply with confidentiality and privacy requirements. Access or use of this computer system by any person, whether authorized or unauthorized, constitutes consent to these terms. There is no right of privacy in this system. Caution: When the message is registered, the HTML syntax is neither checked nor corrected.
For locale-name, specify the locale for the message you want to delete (e.g., en for English, or ja for Japanese). If you do not specify a locale, the default locale will be assumed. Generating Audit Logs You can generate audit logs for Global Link Manager and other Hitachi storage-related products to prove to auditors and evaluators the compliance with regulations, security evaluation standards, and other business standards.
Log Type ConfigurationAccess Maintenance AnomalyEvent Description • Access to an important file on NAS or to content when HTTP is supported • Access to an audit log file Events indicating that an administrator performed a permitted operation and whether the operation terminated normally or failed: • Referencing or updating configuration information • Updating account settings, including addition and deletion of accounts • Setting security • Referencing or updating the audit log settings Even
The following table lists the audit events for each category. Table 3-16 StartStop Audit Events Description Audit Event Starting and stopping software Severity Message ID The SSO server was started successfully. 6 KAPM00090-I The SSO server could not be started. 3 KAPM00091-E The SSO server stopped. 6 KAPM00092-I Table 3-17 Authentication Audit Events Description Administrator or end user authentication Automatic locking of an account Audit Event Severity Message ID Login succeeded.
Description User deletion (GUI and CLI) Severity Message ID User deletion succeeded. 6 KAPM07245-I User deletion failed. 3 KAPM07246-E User information update Successful user information update. (GUI and CLI) Failed user information update. 6 KAPM07243-I Changing the password (from the administrator window) The administrator changed the password successfully. 6 KAPM07232-I The administrator could not change the password.
Description Input and output of data on the database Input and output of authentication data Placing paths online or offline Setting up a multipath LU Audit Event Severity Message ID Partial restoration by the hcmds64db command succeeded. 6 KAPM05565-I Partial restoration by the hcmds64db command failed. 3 KAPM05566-E Data output by the hcmdsdbmove command succeeded. 6 KAPM06543-I Data output by the hcmdsdbmove command failed. 3 KAPM06544-E Data input by the hcmdsdbmove command succeeded.
Description Setting up HDLM Setting up alerts Audit Event Severity The HDLM setting was received successfully. 6 KAIF50200-I The HDLM setting could not be received. 3 KAIF50201-E HDLM was set up successfully. 6 KAIF50202-I HDLM setup partially failed. 4 KAIF50203-W HDLM could not be set up. 3 KAIF50204-E Alert settings were received successfully. 6 KAIF50200-I Alert settings could not be received. 3 KAIF50201-E The alerts were set up successfully.
If an account is locked because the authentication method was changed for a user whose password is not set, this information is not recorded in the audit log. #2 If an account is unlocked because a password was set for a user, this information is not recorded in the audit log. Editing the Environment Settings File for Audit Logs To generate Global Link Manager audit logs, you must edit the environment settings file (auditlog.conf).
Item Description • Warning: 4 • Information: 6 Specifiable value: 0 to 7 (Severity) Default: 6 The table below shows the correspondence between the severity levels of audit events and the types of event log data. Table 3-20 Correspondence Between the Severity Levels of Audit Events and the Types of Event Log Data Severity of Audit Events Type of Event Log Data 0 Error 1 2 3 4 Warning 5 Information 6 7 The following shows an example of the auditlog.conf file: # Specify an integer for Facility.
Event output format: date time type user computer source category event-ID explanation Table 3-21 Information Output to the Windows Event Log (Audit Log) Item Description date The date this entry was logged is output here in yyyy/mm/dd format. time The time this entry was logged is output here in hh:mm format. type One of the following strings is output here to indicate the type of message: • Information • Warning • Error user N/A is always output here.
Item#1 3-70 Output Information unified-specificationrevision-number 1.1 is output. serial-number The serial number of the message in the audit log is output. message-ID#2 The message ID is output. date-and-time The date and time that the message was logged is output in the format yyyy-mm-ddThh:mm:ss.stime-zone. detected-entity The component name or process name is output. detected-location The host name is output. audit-event-type The event type is output.
Item#1 Output Information The Command ID contained in message-text is used to identify a single operation performed from the Global Link Manager GUI. If multiple messages contain the same command ID, this means that those messages were output for a single operation. #1: Some items might not be output, depending on the audit event. #2: For details on the message IDs corresponding to audit events, see Categories of Information Output to Audit Logs in Global Link Manager, and Audit Events on page 3-62.
3-72 Setting Up Global Link Manager Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
4 Installing Global Link Manager Clusters This chapter describes how to set up Global Link Manager to run in a cluster environment. Some Windows Server 2012 terms refer to items that are assigned different names in other Windows server OSs, but which have similar functions. This chapter uses the names that appear in OSs that are not Windows Server 2012 unless otherwise indicated.
Global Link Manager Cluster System Configuration The management server for Hitachi Command Suite products supports activestandby failover in clusters. In a cluster, the server system executing system operations is called the primary node. The server system that is on standby to take over operations if a failure occurs in the executing system is called the secondary node. If a failure occurs, failover clustering switches servers from the primary node to the secondary node to continue operation.
Types of Global Link Manager Cluster Installations This section describes the types of Global Link Manager installations in a cluster environment.
• While specifying cluster settings, do not access Global Link Manager. • Before performing the procedure, make sure that the following conditions are satisfied: ¢ ¢ ¢ Resource groups have been created in the cluster software. The primary and secondary nodes have been registered for a resource group.
¢ For the SNMP trap destination IP address, specify the logical IP address of the cluster. 2. Enter the license key from the Global Link Manager GUI. Use the logical IP address or logical host name of the cluster to access Global Link Manager. For details on how to specify the license, see Setting Up License Information During Initial Login on page 2-26. 3. Use a text editor to create a cluster-configuration file.
When the /auto option is used, the system automatically stops Hitachi Command Suite Common Component and starts HiRDB. After the command is executed, both Hitachi Command Suite Common Component and HiRDB are stopped. Depending on the machine performance, the command is executed before HiRDB has completely started, and then the KAPM06587-E message appears indicating that the export processing has failed.
In Failover Cluster Management, right-click the resource group to which the services used by Global Link Manager have been registered, and then choose Move this service or application to another node. For Microsoft Failover Cluster (on Windows Server 2012): In Failover Cluster Manager, right-click the role to which the services used by Global Link Manager have been registered, choose Move and then, Select Node. Installing Global Link Manager on the Secondary Node 1.
4. Stop Hitachi Command Suite Common Component. Execute the following command: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 5. Change the setting so that the database on the shared disk is to be used.
8. ¢ HBase 64 Storage Mgmt SSO Service ¢ HBase 64 Storage Mgmt Web Service ¢ HBase 64 Storage Mgmt Web SSO Service ¢ HiRDB/ClusterService _HD1 If the port number that HiRDB uses has already been changed and is being used, reset the port number. When the hcmds64dbclustersetup command is executed, the default (22032) is set to the port number that HiRDB uses. Therefore, reset the port number. Setting Up Microsoft Failover Cluster 1. Display Failover Cluster Management.
Table 4-3 HBase 64 Storage Mgmt Common Service Property Settings Tab name Setting General Setup parameters: Specify nothing (if a value is specified, delete it). Dependencies Register HiRDB/ClusterService _HD1. Advanced Policies Possible Owners: Make sure that the executing and standby nodes have been added. Registry Replication Specify nothing. Not displayed in Windows Server 2012.
Tab name Setting Not displayed in Windows Server 2012. 4. Select Start, Control Panel, Administrative Tools, and then Failover Cluster Management to place the resource group created in step 2 online. Caution: In the case you use Microsoft Failover Cluster, if HBase 64 Storage Mgmt Web Service is not started, start HBase 64 Storage Mgmt Web Service by in the Services panel, and place the service online by Failover Cluster Management.
uses. Therefore, if you are using a port number other than the default to perform operations, you need to reset the port number later. Write down the port number you are using so that you can set the port number again.
3. 4. Place the following services offline: ¢ HBase 64 Storage Mgmt Common Service ¢ HBase 64 Storage Mgmt SSO Service ¢ HBase 64 Storage Mgmt Web Service ¢ HBase 64 Storage Mgmt Web SSO Service Stop Hitachi Command Suite Common Component. Execute the following command: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 5. In Cluster Administrator, place the following service offline: ¢ 6.
For server.pathreport.log_location, specify an absolute path (maximum of 150 bytes) for the folder that stores reports. Deploy this folder on the shared disk. To use a backslash (\) as the path delimiter, you must use two consecutive backslashes. The following shows a coding example: server.pathreport.log_location=E:\\HGLAM\\pathreport For details about the settings in the property file for path availability information, see Changing Global Link Manager Server Settings on page 3-24. 10.
Before executing the command, either delete target-folder-forrecreating-the-database and target-folder-for-storing-data or make surethat the two folders are empty. On the shared disk, deploy the folder in which the database is to be recreated. On the local disk, deploy the folder that stores data. Specify an absolute path (maximum of 63 bytes) for target-folder-forrecreating-the-database and target-folder-for-storing-data.
If Microsoft Failover Cluster is used (on Windows Server 2012): In Failover Cluster Manager, right-click the role to which the services used by Global Link Manager have been registered, choose Move and then Select Node. Reinstallation or Version Upgrade Installation of Global Link Manager on the Secondary Node 1. Perform a reinstallation or version upgrade installation of Global Link Manager. See the following subsection before installing Global Link Manager: ¢ ¢ 2.
An IP address cannot be specified for virtualhost, onlinehost, or standbyhost. Make sure that the IP address can be resolved from the host name. The following shows a coding example in the cluster-configuration file: mode = standby virtualhost = hicommand_cluster onlinehost = hicommand_1 standbyhost = hicommand_2 Save the created file as cluster.conf in Hitachi-Command-SuiteCommon-Component-installation-folder\conf. ¢ Migrate the database to the shared disk.
set to the port number that HiRDB uses. Therefore, reset the port number. ¢ Please refer to next for the setting procedure of the cluster. If the resources that registered version earlier than v8 is not in use by other applications, you may want to delete this resources. If Microsoft Failover Cluster is used: Setting Up Microsoft Failover Cluster on page 4-9 5. Switch the group to which the services used by Global Link Manager have been registered to the executing system.
7. In Cluster Administrator, place online the group to which the services used by Global Link Manager have been registered. Caution: In the case you use Microsoft Failover Cluster, if HBase 64 Storage Mgmt Web Service is not started, start HBase 64 Storage Mgmt Web Service by in the Services panel, and place the service online by Failover Cluster Management.
(including the Global Link Manager database) If execution of the hcmds64dbclustersetup command fails because there is not enough space for database-re-creation-destination-folder, increase the space for the folder, and then re-execute the command. • Do not disconnect the shared disk from the executing node until the hcmds64dbclustersetup command execution terminates normally.
4. Use a text editor to create a cluster-configuration file. The items to be specified in the cluster-configuration file are as follows: mode: Specify online. virtualhost: Specify the logical host name. onlinehost: Specify the host name of the primary node. standbyhost: Specify the host name of the secondary node. An IP address cannot be specified for virtualhost, onlinehost, or standbyhost. Make sure that the IP address can be resolved from the host name.
Note: Do not execute two or more hcmds64dbclustersetup commands concurrently. Do not execute the hcmds64dbclustersetup command and the hcmds64getlogs command at the same time. 6. If you have been using the function that outputs path availability information in a report, move the output path availability information (path status log) to a shared disk. If you have not used the function, steps 6 to 8 are not necessary. Go to step 9.
9. In the Services panel, open the properties for the following services, and if Startup Type is Automatic, change it to Manual: ¢ HBase 64 Storage Mgmt Common Service ¢ HBase 64 Storage Mgmt SSO Service ¢ HBase 64 Storage Mgmt Web Service ¢ HBase 64 Storage Mgmt Web SSO Service ¢ HiRDB/ClusterService _HD1 10. If the port number that HiRDB uses has already been changed and is being used, reset the port number.
virtualhost = hicommand_cluster onlinehost = hicommand_1 standbyhost = hicommand_2 Save the created file as cluster.conf in Hitachi-Command-SuiteCommon-Component-installation-folder\conf. 4. Change the settings so that the database on the shared disk is used.
¢ HBase 64 Storage Mgmt Web Service ¢ HBase 64 Storage Mgmt Web SSO Service ¢ HiRDB/ClusterService _HD1 7. If the port number that HiRDB uses has already been changed and is being used, reset the port number. When the hcmds64dbclustersetup command is executed, the default (22032) is set to the port number that HiRDB uses. Therefore, reset the port number. 8. Configure cluster. Please refer to next for the setting procedure of the cluster.
For more information about how to stop a Hitachi Command Suite product, see the corresponding manual for that product. 3. Stop Hitachi Command Suite Common Component in both the primary and secondary nodes. Execute the following command: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 4. Start HiRDB on the primary node. Execute the following command: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64dbsrv /start 5. Back up the database.
Note: Do not execute two or more hcmds64dbclustersetup commands concurrently. Do not execute the hcmds64dbclustersetup command and the hcmds64getlogs command at the same time. 7. In Cluster Administrator, switch each group in which the Hitachi Command Suite product service has been registered to the standby system.
Note: Do not execute two or more hcmds64dbclustersetup commands concurrently. Do not execute the hcmds64dbclustersetup command and the hcmds64getlogs command at the same time. When Performing a New Installation of Global Link Manager in a Cluster Configuration 1. Display cluster software. Select Start, Control Panel, Administrative Tools, and then Failover Cluster Management.
restart on current node and If restart is unsuccessful, fail over all resources in this service or application. If Microsoft Failover Cluster is used (on Windows Server 2012): Right-click the resource, and choose Properties, the Policies tab, then If resource fails, attempt restart on current node and If restart is unsuccessful, fail over all resources in this Role.
3. 4. Place the following services offline: ¢ HBase 64 Storage Mgmt Common Service ¢ HBase 64 Storage Mgmt SSO Service ¢ HBase 64 Storage Mgmt Web Service ¢ HBase 64 Storage Mgmt Web SSO Service On the primary node, stop Hitachi Command Suite Common Component. Execute the following command: Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 5. Place the following service offline: ¢ 6.
13. If other Hitachi Command Suite products have already been installed on the same machine and the group was not deleted in step 12, stop Hitachi Command Suite Common Component. Hitachi-Command-Suite-Common-Component-installation-folder\bin \hcmds64srv /stop 14. Enable failover on the services, on which failover was suppressed in step 7, in the cluster software.
4-32 Installing Global Link Manager Clusters Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
5 Security Settings for Communication This chapter describes how to set up security for communication between a server and clients, and between a server and an LDAP directory server.
Security Settings for Communication Between a Server and Clients 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. Security Settings for Communication Between a Server and an LDAP Directory Server 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.
6 Using Global Link Manager with Other Products This chapter describes the Global Link Manager settings for linking with other products.
Overview of Single Sign-on and User Management Integration for Hitachi Command Suite Products Single sign-on functionality and integrated user management are available when linkage with other Hitachi Command Suite products, such as Device Manager, has been set up. By using single sign-on functionality, you no longer need to specify a user ID and password when starting other Hitachi Command Suite products from the Dashboard menu in the Global Link Manager GUI. For details about the Dashboard menu, see Help.
Note: Single sign-on functionality and integrated user management are available for Hitachi Command Suite products of version 5.0 or later (excluding Tuning Manager 5.0) that are installed on the same server. They are not available for Hitachi Command Suite products whose version is earlier than version 5.0, or for Hitachi Command Suite products that are installed on other servers.
4. In the Device Manager server, register the user to be used by Global Link Manager. For details on the information to register, see Registering an Account for Use by Global Link Manager on page 6-4. 5. Make sure that HDLM hosts are managed by Global Link Manager. If the hosts are not managed, register them in Global Link Manager. For details on how to register a host in Global Link Manager, see the Hitachi Global Link Manager GUI Help. 6. Refresh the host information in Global Link Manager.
In the StorageServicesManager.conf file, specify the LaunchURL parameter in the format shown as follows: Format of the StorageServicesManager.conf File LaunchURL=HSSM-URL In HSSM-URL, specify the URL used to start HSSM. For details about this URL, see the HSSM documentation. For example, if the name of the HSSM management server is machinename, configure the StorageServicesManager.
6-6 Using Global Link Manager with Other Products Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
7 Settings for Using DMP or HP-UX Multipathing This chapter describes the installation and setup required for the Global Link Manager agent to use DMP or HP-UX multipathing. For details about the settings for Hitachi Command Suite Common Agent Component, which is included with the Global Link Manager agent, see Appendix A, Notes on Using HDLM Version 5.8 or Later, DMP, or HP-UX Multipathing on page A-1.
Requirements for Installing Global Link Manager Agent To use DMP or HP-UX multipathing as a management-target of Global Link Manager, you need to install the Global Link Manager agent on the host. Before starting to install the Global Link Manager agent, make sure that DMP or HP-UX multipathing is running. The subsequent sections describe how to perform installation and removal. Hitachi Command Suite Common Agent Component is included with the Global Link Manager agent.
Table 7-3 Storage Destinations for the Global Link Manager Agent (in Windows) Storage destination#1 Usage Installation destination for the Global Link Manager agent system-drive:\Program Files\HITACHI \HGLMAgent system-drive:\Program Files\HDVM \HBaseAgent\mod\hglm#2 Log output destination for the Global Link Manager agent system-drive:\Program Files\HITACHI \HGLMAgent #1 For an x64 machine, the Program Files (x86) folder is used instead of the Program Files folder.
Note: While installing the Global Link Manager agent, make sure that no other application is operated. Using the GUI for Installation To install the Global Link Manager agent: 1. Log in as an Administrator or a user who is a member of the Administrators group. 2. Make sure that the prerequisite JRE (Java runtime environment) is installed. For details about the JRE version, see When Using DMP on page 1-14. 3. Insert the Global Link Manager installation DVD-ROM.
9. To specify an installation information settings file, click Enable button, and then click the Browse button to specify the location of the installation information settings file. For details about the installation information settings file, see Information Settings File for Global Link Manager Agent Installation on page 7-15. 10. Click the Next button. The Confirmation Before Installation dialog box appears. 11. Check the installation information, and then click the Install button.
6. Execute the following command: drive-in-which-the-installation-DVD-ROM-is-set:\HGLM\Agent \Windows\HGLMAgent_tools\setup.exe [/s] [/fname-of-theinstallation-information-settings-file] [/h] [INSTALL_PATH=pathname] You can specify the following options in the installhglm command. Table 7-5 setup.exe Command Options Item Description /s Specify this option to suppress the output of a message asking for confirmation of the requested operation.
Installing the Global Link Manager Agent in Solaris or HP-UX Environments By specifying options for the Global Link Manager agent installation command, you can perform the following operations: • Unattended installation Installation is performed without the user needing to respond to prompts.
4. Execute the following command to start installation. In Solaris: # /cdrom/cdrom0/HGLM/Agent/Solaris/install.sh In HP-UX: # /cdrom/cdrom0/HGLM/Agent/HPUX/install.sh By specifying the following command options, you can select either of the following installations: ¢ Unattended installation (-s option) ¢ Automatic properties file setup (-f option) To execute unattended installation, specify the -s option.
Editing the Global Link Manager agent properties files If necessary, edit the Global Link Manager agent properties files after installing the Global Link Manager agent. If the value specified for the property that specifies the DMP storage destination (agent.dmp.location) or the value specified for the property that specifies the HP-UX multipathing storage destination (agent.mps.location) does not match the execution environment, change the value. Change other items in the properties files as required.
Removing the Global Link Manager Agent from Solaris or HP-UX Environments By specifying an option for the Global Link Manager agent removal command, you can perform an unattended removal, where you do not need to respond to prompts during the removal. To remove the Global Link Manager agent: 1. Login with root permissions. 2. Execute the following command to start removal. # Global-Link-Manager-Agent-installation-directory/ bin/.uninstall.
Table 7-6 Types and Storage Locations of the Properties Files Used by the Global Link Manager Agent Type agent.properties logger.properties host.
Table 7-7 Properties File for Global Link Manager Agent Settings (agent.properties) No. 1 Property name agent.dmp.location Contents Specifies the DMP storage destination. Specifiable value: Character string Default (in Windows): None Default (in Solaris): /opt/VRTS/bin 2 agent.dmp.time_out Specifies the timeout time for communication processing between the Global Link Manager agent and DMP.
In Solaris or HP-UX: /opt/HDVM/HBaseAgent/bin/amc_activate -d hglm /opt/HDVM/HBaseAgent/bin/amc_activate -a hglm Table 7-8 Properties File for Global Link Manager Agent Log File Output (logger.properties) No. 1 Property name agent.logger_log_level Contents Specifies the output level (threshold value) for Global Link Manager agent log files. Specifiable value: 0, 10, 0, or 30 (in order of importance from left to right)# Default: 20 2 agent.logger.
Table 7-9 Properties File for DMP Host Settings or HP-UX Multipathing Host Settings (host.properties) No. 1 Property name snmp.shutdown_port_num Contents Specifies a port number to which a stop request for canceling an alert generation processing is sent. Specifiable value: 1 to 65535 Default: 23036 This value is used to stop the HGLM SNMP daemon. Therefore, do not modify the value while the daemon is running.
Information Settings File for Global Link Manager Agent Installation To install a Global Link Manager agent on multiple hosts, you can perform an unattended installation, which offers a simplified installation procedure. You can also use an installation settings file for the Global Link Manager agent to simplify the property setup procedure that you have to perform after the installation. In this file, all of the necessary properties can be predefined.
No. Property name Property file name Reference es) on page 7-13 9 snmp.shutdown_port_num host.properties Table 7-9 Properties File for DMP Host Settings or HPUX Multipathing Host Settings (host.properties ) on page 7-14 10 snmp.logger.log_level snmplogger.properties 11 snmp.logger.max_backup_index 12 snmp.logger.max_file_size Table 7-10 Properties File for SNMP Trap Log File Output on a DMP Host or an HP-UX Multipathing Host (snmplogger.
8 Troubleshooting Global Link Manager This chapter explains how to troubleshoot problems that might occur during Global Link Manager operation. If you need technical support, see Getting help on page xiii.
Procedure for Troubleshooting Global Link Manager To troubleshoot when an error occurs: 1. Check the output messages. If no messages have been output, check for similar errors in the examples provided in Global Link Manager Troubleshooting Examples on page 8-2. 2. If you cannot determine the cause of the error after checking the output messages and checking for similar errors in the troubleshooting examples, collect the diagnostic information.
Setting Up Global Link Manager Table 8-2 Troubleshooting Examples (During Global Link Manager Environment Setup) Problem Cause The specified settings were not applied to the property file. Action Global Link Manager was not Restart Global Link restarted after the property Manager. file was updated. Default values were used See Changing Global Link because incorrect values Manager Environment were set in the property file.
Problem Cause Action version is earlier than 7.0, or execute the hdvmagt_setting command for Device Manager agents whose version is 7.0 or later, in order to set up the Device Manager server information or host information. For details on how to do this, see Help. The host information cannot be updated. Hitachi Command Suite Common Agent Component is not running. Start Hitachi Command Suite Common Agent Component.
Problem Cause • Packets are blocked by packet filtering such as firewalls. • Communication is poor due to IP address collision. • The specified IP address or subnet mask of the default gateway is invalid. Action • Reconfigure packet filtering so that packets for HDLM and Global Link Manager can go through. • Reset the IP addresses. • Revise the settings for the IP address or subnet mask of the default gateway.
Problem Cause Action information. For details on how to do this, see Help. On an AIX host, no paths have been set. Check the operating environment of HDLM on the host, add necessary paths, and then perform the operation again. For details on how to change the configuration of the HDLM operating environment, see the HDLM manual. Hitachi Command Suite Common Agent Component is not running. Start Hitachi Command Suite Common Agent Component.
information about the Global Link Manager server. If an error occurs while you are using the single sign-on function, you must collect a thread dump. The following sections describe how to collect diagnostic information and a thread dump. Diagnostic Batch Collection about the Global Link Manager Server To collect diagnostic information about Global Link Manager, use the hcmds64getlogs command. Note that you can use the hcmds64getlogs command only when an error has occurred.
When Acquiring the Path Availability Information (Path Status Log) When an error occurs during addition or update of a host or during output of a report, and you need diagnostic information, acquire the path availability information (path status log) listed in No.11 of Table 8-4 Information Collected by the hcmds64getlogs Command on page 8-7. When acquiring the path availability information (path status log), change the property file (server.properties).
Options and arguments /type HGLAM or GlobalLinkAvailabilityManager /arc archive-file-name Description • When the /type option is specified: 13 bytes • When the /type option is not specified: 71 bytes Specifies that only Global Link Manager diagnostic information be collected. If this option is not specified, the command also collects diagnostic information about the other Hitachi Command Suite products installed on the same server.
Batch Collection of Diagnostic Information about the Host If the output error is caused by a host, you need to collect diagnostic information about the host. The collection procedure for the host diagnostic information differs depending on the version of the multipath management software installed on the host. When the version of HDLM is 5.8 or later Use the DLMgetras utility to collect diagnostic information. For details on the DLMgetras utility, see the HDLM manual.
When you are using DMP (Solaris) or HP-UX multipathing Use the installgetras command or hglmagtgetras command of the Global Link Manager agent to collect diagnostic information. If an error occurs during Global Link Manager agent installation or removal, use the installgetras command. If an error occurs in other situations, use the hglmagtgetras command. Use root permissions when executing the installgetras command and hglmagtgetras command.
This command is stored in the following location: /opt/HGLMAgent/bin Options Table 8-8 Options and Arguments for the hglmagtgetras Command Option/Argument directory-name Description Specify the directory for storing collected diagnostic information. You can use either a relative or absolute path. You can use ASCII code characters other than the following special characters to specify a path: , ; * ? " < > | $ % & ' `. You can use forward slashes (/) as path delimiters.
¢ You cannot specify the root directory. Thread Dump Collection of Diagnostic Information If any of the following problems occur while the single sign-on function is being used, collect a Java VM thread dump to check for the cause of the problem: • An attempt was made to start Global Link Manager, but the User Login window did not appear. • An attempt to log on to Global Link Manager was successful, but the main window did not appear.
Log File Description The event log file also stores operations performed by the user and information about Global Link Manager as audit logs. This log file should be checked to audit accesses to Global Link Manager and operations performed by the user. Message log file (HGLAM_Messagen.log) Stores the messages output while Global Link Manager is starting, stopping, and being operated. This log file should be checked if an error occurs while Global Link Manager is starting, stopping, or being operated.
Item Description program-name [process-ID]: message-ID message-text For details on the cause and what action to take for each message, see the manual Global Link Manager Messages. A message beginning with program-name [process-ID]: CELFSS is an audit log message. For details on the audit logs, see Generating Audit Logs on page 3-61. Output Format of the Message Log Files This section shows the format of entries output to the Global Link Manager message log file, and describes the contents of each entry.
Output Format of the Installer and Removal function Trace Log Files Output format: *** begin Hitachi Global Link Manager (Windows) setup process Trace Log date-and-time : (level) trace-information [ supplementary-information ] *** end Hitachi Global Link Manager (Windows) setup process Trace Log Table 8-12 Information Output to the Installer Trace Log and the Removal function Trace Log Files Item 8-16 Description date-and-time The date and time this entry was logged is output here in yyyy/mm/dd hh:mm:s
A Notes on Using HDLM Version 5.8 or Later, DMP, or HP-UX Multipathing This appendix provides notes on operating Global Link Manager and the items that have to be configured in advance when the multipath management software used on the host is HDLM 5.8 or later, DMP, or HP-UX multipathing. This appendix also explains how to start the Hitachi Command Suite Common Agent Component.
Hitachi Command Suite Common Agent Component Hitachi Command Suite Common Agent Component refers to the component included in version 5.8 or later of HDLM, or the Global Link Manager agent#. # The Global Link Manager agent is required when DMP or HP-UX multipathing is used. For details about the installation and environment settings of the Global Link Manager agent, see Chapter 7, Settings for Using DMP or HP-UX Multipathing on page 7-1.
Changing Firewall Settings for HDLM or for DMP On a Windows host where HDLM or DMP has been installed, if Windows Firewall is active, you need to add Hitachi Command Suite Common Agent Component to the Windows Firewall exceptions list so that you can add hosts on the Global Link Manager server. Windows host where HDLM version is from 5.8 or later to 6.5 or earlier Registering an exception To register Hitachi Command Suite Common Agent Component as an exception: 1.
netsh firewall show all Make sure of the following from the command execution results: • That HBase Agent is displayed. • That Mode is Enable. • That the paths to hbsa_service.exe and java.exe are correct. Deactivating the setting for an exception If you removed HDLM from the host, deactivate the above setting. Execute the following commands to deactivate the setting.
Note: If the port number of the service port in Table A-1 Properties for Changing the Settings of Hitachi Command Suite Common Agent Component (server.properties) on page A-6 was changed after registering the exception, retry an execution of the firewall_setup command. HDLM for Linux If the host OS is Linux, register in the Firewall exceptions list by the manual procedure.
Contents of property files: The following tables list the properties that are used for changing the settings of Hitachi Command Suite Common Agent Component. Table A-1 Properties for Changing the Settings of Hitachi Command Suite Common Agent Component (server.properties) No. Property Name Description Settings for the ports used by the service (or daemon process) and the Web server function 1 server.agent.
No. Property Name Description If the host on which HDLM version 5.8 or later or the Global Link Manager agent is installed has multiple network interface cards and is connected to the same network, specify the IP address of one of the installed network interface cards. If this setting is not configured, the host might not be added properly.
No. 9 Property Name server.agent.JRE.location Description Specify the installation destination of the Java program used by the Hitachi Command Suite Common Agent Component. Default for Windows or Linux: None Default for Solaris, AIX, or HP-UX Installation path for the Java program that had been installed on the host when you installed the Hitachi Command Suite Common Agent Component Caution: • The following Java execution environments can be used on a Hitachi Command Suite Common Agent Component.
No. Property Name Description are disregarded without any errors for IP addresses using decimal numbers with dots. In the following example, the specification permits 191.0.0.2 and 192.168.0.0 to 192.168.255.255 to connect to the Hitachi Command Suite Common Agent Component: server.http.security.clientIP=191.0.0 .2, 192.168.*.*. The following gives an example for permitting 2001::203:baff:fe36:109a and 2001::203:baff:fe5b:7bac: server.http.security.
No. 2 Property Name logger.MaxBackupIndex Description Specifies the maximum number of log file backups. If more log files are generated than specified, the Hitachi Command Suite Common Agent Component writes over the oldest one. If a log file reaches the maximum size, the file is renamed by adding a counter (which represents the version) to the file name. For example, access.log becomes access.log.1.
2. Restart Hitachi Command Suite Common Agent Component. Stop Hitachi Command Suite Common Agent Component, and then start the component again. For details on how to start and stop Hitachi Command Suite Common Agent Component, see Starting and Stopping Hitachi Command Suite Common Agent Component on page A-11. Starting and Stopping Hitachi Command Suite Common Agent Component When you add a host of HDLM version 5.
/opt/HDVM/HBaseAgent/bin/hbsasrv start In AIX: /usr/HDVM/HBaseAgent/bin/hbsasrv start Stopping Hitachi Command Suite Common Agent Component To stop Hitachi Command Suite Common Agent Component, execute the following command, corresponding to the host OS. This operation requires Administrator or root privileges. In Windows: installation-folder-for-Hitachi-Command-Suite-Common-AgentComponent\bin\hbsasrv.
Table A-3 hbsasrv Command Syntax Item Description Synopsis hbsasrv [start | stop [-f] | status] Description Starts or stops the service (or daemon process) of the Hitachi Command Suite Common Agent Component. Also, this command displays the status of the service (or daemon process). Options start: Starts the service (or daemon process). stop [-f]: Stops the service (or daemon process).
Options Table A-4 Options and Arguments of the javapath_setup Command Item Description -set Specify this option to switch the Java execution environment. If you do not specify an argument for this option, the command assumes that you have specified "new " as an argument. new Specify this argument to select the latest version of the Java execution environment from Oracle Sun JDK 6 and Oracle Sun JRE 6 installed on the host.
If HDLM GUI has already been booted, reboot HDLM GUI. When the DMP for Windows: If the host has been added to HGLM, reboot "HGLM Agent SNMP Service" from the Windows [Service] window. Note: • If you re-install or update the Java program, the command must be reexecuted because the installation destination of the Java program is changed. • If you remove the running Java program that was changed, HDLM for Windows or DMP for Windows cannot be removed.
A-16 • If you remove the Java program that was changed, Global Link Manager cannot be removed. Remove Global Link Manager after changing back the Java program. • If the user authentication was conducted with the LDAP server, the certification must be imported again. Notes on Using HDLM Version 5.
Acronyms and abbreviations The following acronyms and abbreviations might be used in this guide.
D DEP Data Execution Prevention DHCP Dynamic Host Configuration Protocol DNS Domain Name System E EM64T Extended Memory 64 Technology EUC Extended UNIX Code F FC-SP Fibre Channel Security Protocol G GUI Graphical User Interface H HBA Host Bus Adapter HTTP Hypertext Transfer Protocol # A B C D E F G H I J K L M N O P Q R S T U V W X Acronyms-2 Hitachi Global Link Manager Installation and Configuration Guide (Web Version) Y Z
I IA32 Intel Architecture 32 IP Internet Protocol IPF Itanium Processor Family IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 L LAN Local Area Network LDAP Lightweight Directory Access Protocol LDEV Logical Device LU Logical Unit M MIB Management Information Base MP Maintenance Pack # A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Acronyms-3 Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
N NAS Network Attached Storage NTP Network Time Protocol O OS Operating System R RADIUS Remote Authentication Dial In User Service S SAN Storage Area Network SMTP Simple Mail Transfer Protocol SNMP Simple Network Management Protocol SP Service Pack SSL Secure Sockets Layer SSO Single Sign-on # A B C D E F G H I J K L M N O P Q R S T U V W X Acronyms-4 Hitachi Global Link Manager Installation and Configuration Guide (Web Version) Y Z
Index Numerics C 22015/tcp 22016/tcp 22017/tcp 22018/tcp 22019/tcp 22030/tcp 22031/tcp 22032/tcp 22033/tcp 22034/tcp 45001/tcp 49000/tcp changing database settings 3-40 Global Link Manager database password 3-41 Global Link Manager server host name 3-43 Global Link Manager server IP address 3-42 Global Link Manager server settings 3-24 log file settings 3-39 port number 3-45 port number for receiving SNMP trap 3-26 checking Global Link Manager status 3-4 Hitachi Command Suite Common Agent Component opera
thread dump 8-13 command hcmds64unlockaccount checking status 3-4 client 1-6 installing 2-1 migrating database 3-13 removing Global Link Manager cluster restoring database 3-11 server 1-5 settings 3-1 starting 3-3 3-58 D Data Execution Prevention 2-4 database backing up 3-8 changing setting 3-40 migrating 3-13 restoring 3-11 updating failed 2-18 database.
stopping 3-4 host log file collecting 8-10 host name for Global Link Manager server, changing host.
P password Global Link Manager database, changing 3-41 path availability information 3-31 permanent license key 2-27 port number for receiving SNMP trap 2-2, 3-26 Hitachi Command Suite Common Component, changing 3-45 R registering warning banner message 3-60 reinstalling Global Link Manager in cluster environment 4-11 reinstalling Global Link Manager 2-10 removing Global Link Manager agent 7-9 Global Link Manager cluster 4-29 removing Global Link Manager 2-24 requirements for Global Link Manager GUI client
T tasks, flow of 1-18 temporary license key 2-27 thread dump, collecting 8-13 troubleshooting 8-1 Global Link Manager GUI 8-3 Global Link Manager installation 8-2 Global Link Manager setup 8-3 U UAC 3-3 unattended installation Global Link Manager agent 7-8 upgrade installation 2-12 URL changing for Global Link Manager login 3-50 user integrated user management 6-2 using Global Link Manager with other products 6-1 V version upgrade installation Global Link Manager in cluster environment 4-11 W warning ban
Index-6 Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
Hitachi Global Link Manager Installation and Configuration Guide (Web Version)
Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com Regional Contact Information Americas +1 408 970 1000 info@hds.com Europe, Middle East, and Africa +44 (0)1753 618000 info.emea@hds.com Asia Pacific +852 3189 7900 hds.marketing.apac@hds.
