A Quick Start Training for Hitachi Ops Center Suite

This course, which is free to registered Hitachi Vantara Hitachi Vantara users, provides training on how to install and use Hitachi Ops Center Suite. You will learn how to quickly implement the software in your data center and familiarize yourself with basic capabilities of the main Ops Center products.

Additionally, this course will teach you how to provision storage systems with Ops Center Administrator, protect data with Ops Center Protectorand analyze performance with Ops Center Analyzer and Analyzer detail view.

Overview

The Hitachi Ops Center product enables you to optimize your data center operations through integrated configuration, analytics, automation, and copy data management. These features enable you to administer, automate, optimize, and protect your Hitachi storage infrastructure.

Hitachi Ops Center is a system consisting of multiple products. The following provides an overview of the Hitachi Ops Center product components and an overview of the system configuration.

Overview of the Hitachi Ops Center products

A Hitachi Ops Center system consists of the following software products:

Hitachi Ops Center Common Services

Hitachi Ops Center Common Services provides infrastructure functions common to Hitachi Ops Center that enable you to launch products, manage users, and enable single sign-on (SSO).

Hitachi Ops Center Automator

Hitachi Ops Center Automator provides the tools to automate and simplify end-to-end processes, such as storage provisioning, for storage and data center administrators. The building blocks of the product are prepackaged automation templates known as service templates.

Hitachi Ops Center Analyzer

Hitachi Ops Center Analyzer provides a comprehensive application service-level and storage performance management solution that enables you to quickly identify and isolate performance problems, determine the root cause, and provide solutions.

Hitachi Ops Center Analyzer collects the data to analyze from Hitachi Ops Center Analyzer detail view, which processes performance and configuration data received from probes that connect to monitoring targets.

Hitachi Ops Center Analyzer viewpoint

Hitachi Ops Center Analyzer viewpoint consolidates information from multiple instances of Hitachi Ops Center Analyzer and provides functions for monitoring a system that spans multiple data centers.

Hitachi Ops Center Administrator

Hitachi Ops Center Administrator is a unified software management tool that reduces the complexity of managing storage systems by simplifying the setup, management, and maintenance of storage resources.

Hitachi Ops Center Protector

Hitachi Ops Center Protector provides a modern, holistic approach to data protection, recovery, and retention.

Hitachi Ops Center API Configuration Manager

Hitachi Ops Center API Configuration Manager provides APIs for obtaining information from and performing operations on storage systems.

Overview of Hitachi Ops Center Common Services

Common Services is a component that provides single sign-on functionality and a portal site for Hitachi Ops Center products.

When you log in to the Hitachi Ops Center Portal, the portal shows a list of registered Hitachi Ops Center products. When you click a product-name link, the product UI opens. Because user authentication is centralized, you can access each product without additional logins.

The Hitachi Ops Center products that support the single sign-on functionality are as follows:

Hitachi Ops Center Automator (version 10.0.1 or later)
Hitachi Ops Center Analyzer
Hitachi Ops Center Analyzer detail view (version 10.8.2 or later)
Hitachi Ops Center Analyzer probe (version 10.8.2 or later)
Hitachi Ops Center Analyzer viewpoint
Hitachi Ops Center Administrator (version 10.1.0 or later)
Hitachi Ops Center Protector (version 7.0 or later)

The single sign-on user information is managed by Common Services, so you can create, delete, and modify user accounts from the portal site.

Tip: You can also use Hitachi Ops Center products without single sign-on. For the installation and setup procedures to use in this case, see the documentation for the specific Hitachi Ops Center products that you are using.

Linking with an Active Directory or LDAP server

By linking Common Services with an external Active Directory or LDAP server, you can consolidate actions related to authenticating Hitachi Ops Center users. You can link Common Services with an Active Directory or LDAP server from the Hitachi Ops Center Portal.

You can link Common Services with one of the following authentication servers:

Active Directory server
LDAP server that supports LDAPv3 and LDAPS

You can link Common Services with an Active Directory server or an LDAP server. You cannot link Common Services with both types of servers.

The following conditions apply when you link Common Services with an Active Directory server or LDAP server.

Active Directory server:

You can link to a maximum of four Active Directory servers.
Both LDAP(S) and Kerberos are supported as authentication protocols.
When using Kerberos authentication, you can set only one realm.
You can register Common Services users for objects that are located under the User base DN and with an objectclass of person.
To log in to the Hitachi Ops Center Portal, use the Active Directory sAMAccountName as the user name.
You can specify groups under the Group base DN to import.
If you link to multiple Active Directory servers, make sure that usernames and email addresses are not duplicated among servers.

LDAP server:

You can set only one LDAP server.
Only LDAP(S) is supported as an authentication protocol.
You can import a maximum of 100 user accounts.

To narrow down the users to import, you can filter the search conditions by using LDAP attributes.
Synchronizing user groups between the LDAP server and Common Services is not supported.

Note:

To use Analyzer viewpoint, you must specify an email address for the mail attribute.
A user who has the same user name or email address as a local user of Common Services cannot log in to the Hitachi Ops Center Portal.

Before setting up the linkage, you must delete the local user in the Hitachi Ops Center Portal or change the email address of the local user.
If the LDAP server certificate has expired, all users (including local users of Common Services) will be unable to log in to the Hitachi Ops Center Portal.

To avoid this, you must update the LDAP server certificate before it expires, and import the certificate into the Common Services truststore.

For details on how to set up a link with an Active Directory or LDAP server and details on users and user groups, see Configuring a link to an Active Directory or LDAP server.

Linking with an identity provider

By linking Common Services with an external identity provider, you can use the identity provider to centrally authenticate Hitachi Ops Center users. You can also use the Multi Factor Authentication (MFA) functionality provided by the identity provider.

By linking with an identity provider, you can authenticate a user who logs in to the Hitachi Ops Center Portal on the identity provider side. If the identity provider successfully authenticates the user, the user is imported as a local user of Common Services.

Common Services supports linking with Active Directory Federation Services (AD FS). To link with AD FS, configure the settings on both the AD FS server and the Hitachi Ops Center Portal. For details, see Configuring a link to an AD FS identity provider

Note:

You cannot link one Active Directory server to both a directory service and AD FS.
Identity provider user accounts must have a unique username and email address. If an identity provider user account conflicts with a local user ID or email address, the identity provider user cannot log in. You must remove the local user from the Hitachi Ops Center Portal or change their email address before proceeding.

Installation methods for Hitachi Ops Center

You can use one of the following methods to install Hitachi Ops Center:

Installation by using the Express installer

Use this method when you want to install or upgrade multiple Hitachi Ops Center products at the same time. The Express installer includes the Server Express installer and the Client Express installer, each of which installs different products. You can select specific products to install.
The Server Express installer installs the following products and registers them with Common Services:
- Hitachi Ops Center Common Services
- Hitachi Ops Center Administrator
- Hitachi Ops Center API Configuration Manager
- Hitachi Ops Center Protector
- Hitachi Ops Center Automator
- Hitachi Ops Center Analyzer
- Hitachi Ops Center Analyzer detail view
- Hitachi Ops Center Analyzer viewpoint
You can use the Client Express installer to install the following products:
- Hitachi Ops Center API Configuration Manager
- Hitachi Ops Center Protector Client
- Hitachi Ops Center Analyzer probe server
Installation by using the individual installer
Use this method when you want to install or upgrade Hitachi Ops Center products individually. Use the installation media for each product to perform installation.

For details on the installation method, see the following descriptions:

Hitachi Ops Center system configurations

A Hitachi Ops Center system consists of one or more management servers, depending on the software you are using and the scope of resources to manage. Common Services runs on one management server, and products register with Common Services so that they can use common infrastructure functions.

The following provides basic system configuration examples and the recommended installation method for each.

Example configuration running on one management server

The following shows an example system configuration in which Hitachi Ops Center product runs on one management server.

Figure showing an example of a system configuration where Hitachi Ops Center is operated at a single data center. In this example, one management server and one Analyzer probe server are installed.

When using an individual installer, you use the installer specific to the product. If you want to use the single sign-on functionality, you must also install Common Services.

Example configuration running on multiple management servers

When managing resources in a large-scale data center, you can use a configuration that uses multiple management servers. The following shows this type of configuration.

Figure showing an example of a system configuration where Hitachi Ops Center is operated at two data centers. In this example, one management server and one Analyzer probe server are installed at each data center, and an Analyzer viewpoint server is installed outside of the data centers.

Even if you use multiple management servers, the system only uses one instance. In this example configuration, the system uses the Common Services instance on the management server running in Data Center 1.

Using an individual installer, you can also manually install optional Hitachi Ops Center products. In this example configuration, Automator, Administrator, and Common Services are installed.

Figure showing an example of a system configuration where Hitachi Ops Center is operated at two data centers. In this example, Hitachi Ops Center Automator and Common Services are installed on the management server at Data Center 1, and Hitachi Ops Center Administrator is installed on the management server at Data Center 2.

Note: If the Hitachi Ops Center system configuration contains multiple management servers and the system times of the management servers are not the same, you cannot start the products from the Hitachi Ops Center Portal. To keep the time synchronized, we recommend that you use NTP to correct the time automatically.

Installing or upgrading Hitachi Ops Center products by using the Express installer

You can simultaneously install or upgrade multiple Hitachi Ops Center products by using the Express installers.

Depending on which products you want to install, you can use the Server Express installer and the Client Express installer. For details, see Using the Server Express installer or Using the Client Express installer.

Workflow for installing and setting up Hitachi Ops Center (Express installer)

The following figure shows the workflow for using the Server Express installer and the Client Express installer.

Tip: You use the Client Express installer only when the environment requires it. For example, you use the Client Express installer when you want to configure a separate server to run the Protector Client or Analyzer probe server.

Workflow showing the steps for constructing an environment for Hitachi Ops Center products. The steps are: Prepare a management server. Install Common Services and each product. Prepare a server. Install each product. Configure SSL communications. Register the products in Common Services. Register a license. Set up access controls.Set up Active Directory, LDAP, or identity provider server. Set up a password policy. Finally, set up Hitachi Remote Ops.

When the setup is complete, configure the settings for each product as required. For details, see the documentation for each product.

If you are upgrading, the previous settings are preserved. If you upgrade Hitachi Ops Center products that were registered in Common Services, you do not need to configure SSL communication or perform the subsequent steps.

Using the Server Express installer

Using the Server Express installer, you can simultaneously install or upgrade the following products:

Hitachi Ops Center Common Services
Hitachi Ops Center Administrator
Hitachi Ops Center API Configuration Manager
Hitachi Ops Center Protector
Hitachi Ops Center Automator
Hitachi Ops Center Analyzer
Hitachi Ops Center Analyzer detail view
Hitachi Ops Center Analyzer viewpoint

To use API Configuration Manager or Protector, the prerequisite program Command Control Interface is required. If you use the Server Express installer to install API Configuration Manager or Protector, Command Control Interface will also be installed. Do not use this instance of Command Control Interface for other purposes.

Note: If Command Control Interface has already been installed by using one of the following methods, upgrade it by using the Server Express installer:

Installation by the Server Express installer
Individual installation of API Configuration Manager

If the currently installed instance of Command Control Interface is a newer version, it will be left in place.

If Command Control Interface was individually installed by using a different method, it will not be upgraded. If necessary, you can upgrade it manually.

If you do not want to use an individually installed instance of Command Control Interface and want to replace it with an instance of Command Control Interface installed by the Server Express installer, or if you want to replace an instance of Command Control Interface installed by the Server Express installer with an individually installed instance of Command Control Interface, see Replacing Command Control Interface.

Preparing the management server

Make sure that the management server on which you plan to install Hitachi Ops Center products meets the system requirements.

For the Common Services system requirements, see the Hitachi Ops Center Release Notes.
For the system requirements of other Hitachi Ops Center products, see the documentation or Release Notes for each product.
For a complete list of Hitachi Ops Center system requirements, go to the Ops Center documentation site and select Hitachi Ops Center System Requirements.

Note: For a list of supported software for all products, including versions, see the Product Compatibility Guide.

Note:

Hitachi Ops Center does not support installing other software products on the management server, but allows for installing software required by corporate policy such as anti-virus programs and third-party monitoring agents. Note that Hitachi Vantara does not take responsibility for or support any interactions between the third-party programs and the Hitachi Ops Center software.
When Common Services is installed, the following RPM packages are installed:
- Amazon Corretto 21
- PostgreSQL 15
Common Services starts the Common Services service by using the postgres user and postgres group created on the management server.

The postgres user and postgres group must reside on the management server. If the users on the management server are managed by an external authentication server, the Common Services service cannot start when the OS starts.

Make sure that you complete the following actions on the installation destination management server:

To install prerequisite packages, the Server Express installer requires the repository settings for the yum command. Specify the yum repository settings in advance, or specify the settings by following the message displayed when you run the Server Express installer.
Administrator requires Podman as a container runtime.
For Podman-related software (podman, containers-common, conmon, runc), make sure that versions supported by Administrator are installed on the management server.
If they are not installed, install them by using the following methods:
- Installation by using the Server Express installer
  When you install by using the Server Express installer, the yum command is run during the Administrator installation and the Podman-related software is installed. Configure the yum repository settings in advance or when running the Server Express installer so that a supported version of the Podman-related software can be installed.
- Installation by using the OS media
  If the yum repository does not contain a supported version of the Podman-related software, install a supported version of the Podman-related software by using the OS media.
For details on supported versions and how to install them, see the Hitachi Ops Center Administrator Getting Started Guide.

Note: If you run the Server Express installer, the iptables and firewalld settings are changed so that required communications can be established. If you use nftables, you must make the changes manually.

Installing or upgrading Common Services and additional products

To install or upgrade Common Services and one or more products, use the Server Express installer.

Note: If you install Common Services, Amazon Corretto 21 and PostgreSQL 15 are installed. If you upgrade Common Services, Amazon Corretto 8 (version 10.6.0 and earlier), Amazon Corretto 11 (versions 10.6.1 to 10.9.1), Amazon Corretto 17 (versions 10.9.2 to 11.0.2), and PostgreSQL 11 (version 10.9.2 and earlier) that were installed with the previous version are not removed. If you do not need these programs, remove them by using the rpm command. If you cannot remove the programs by using this command, use the rpm command with the --nopreun option specified.

The package names are as follows:

Amazon Corretto 8: java-1.8.0-amazon-corretto-devel
Amazon Corretto 11: java-11-amazon-corretto-devel
Amazon Corretto 17: java-17-amazon-corretto-devel
PostgreSQL 11: postgresql11, postgresql11-server, postgresql11-libs

For best results, close all other programs, including:
- Security-monitoring programs
- Virus-detection programs
- Process-monitoring programs
If the Services window is open, close it.
If you are logged in to the Hitachi Ops Center Portal, close the web browser before beginning the upgrade. If you upgrade Common Services while logged in to the Hitachi Ops Center Portal, an internal server error might occur. If this error occurs, restart the web browser.
In Common Services version 10.9.1 and later, a special group named support-services has been added as a default user group. This group is used for support services, so it cannot be used for standard purposes. For this reason, if you want to upgrade from version 10.9.0 or earlier, first make sure that the support-services group does not exist.
- If the support-services group was imported by linking with an Active Directory server, delete the group. In addition, on the User directories window of the Hitachi Ops Center Portal, click the Edit user directory service icon for the Active Directory server, and then change the Group entry list setting so that the support-services group will not be imported.
- If the system administrator created the support-services group using a method other than linking with an Active Directory server, delete or rename the group before upgrading from version 10.9.0 or earlier.
Note: If you upgrade Common Services from version 10.9.0 or earlier while the support-services group exists, you must delete or rename the group and then perform an overwrite installation of Common Services.
Before performing an upgrade installation of Common Services in an environment integrated with an Active Directory or LDAP server: on the Active Directory or LDAP server editing window of Hitachi Ops Center Portal, run a Test connection and Test authentication to ensure that they are successful. For details, see Configuring Active Directory as a directory service for Ops Center or Configuring a non-AD directory service for Ops Center (LDAP server).
If you perform an upgrade installation without a proper connection or authentication, Active Directory users might be unable to log in to the Hitachi Ops Center Portal.

Note: If Active Directory users cannot log in to the Hitachi Ops Center Portal in an environment integrated with an Active Directory server, check the connection and authentication with the Active Directory server. After that, log in to Hitachi Ops Center Portal, and click Sync groups on the User directories window to synchronize Active Directory groups with Common Services.
For details on the prerequisites for installing each product, see the respective manual.

Log in to the management server as the root user.
If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
To start the Server Express installer, run install.sh, which is in the root directory of the installation media.

Note: If one or more products cannot be installed in the same environment as a currently installed product, the Server Express installer will not install the applicable products and a warning message is displayed.
If the yum repository settings are not configured or cannot be used, a message appears asking if you want to run the Yum Setup Helper tool. Follow the displayed message to configure the settings.
1. To configure the settings, enter y. The Yum Setup Helper window is displayed.
2. From Content in Current Dir, use the cursor keys and then the Enter key to select the directory that includes the OS media file (ISO file).
  
  Note: The Yum Setup Helper tool uses the OS media file to configure the yum repository settings, so the OS media file must be stored on the management server. If the OS media file does not exist, get it from the distribution website. Click Help to see information about the corresponding OS media file.
3. Select the ISO file. The file name is displayed for Selected Item.
4. Click OK. Configuration of the yum repository settings starts, and a processing window is displayed.
  
  Tip: You can also use the tab key to move the cursor between items in the window.
5. When configuration of the yum repository settings is complete, a message is displayed. Select OK. If the configuration fails, an error message is displayed. If you select OK, the window where you can select an OS media file is displayed again.
Choose the product you want to install, and then press Enter.
If you select 1 All, the products listed within the parentheses are installed.
To select multiple products, separate the numbers with commas. (Example: 2,3)

Note: You cannot select products that have ** displayed for the product number.
For new Analyzer, Analyzer detail view, or Analyzer viewpoint installations, set the scale of the resources to be managed by the product by choosing one of the following scale values:
- 1: Small-scale configuration
- 2: Medium-scale configuration
- 3: Large-scale configuration
Note:
- For details on the system requirements for each product based on scale, see Hitachi Ops Center System Requirements.
- Depending on the physical memory size of the management server to be installed, some scales might not be displayed.

Follow the prompts and specify the required information.

For Common Services:

Setting items	Description
Install directory	For a new installation: Specify the directory in which to install Common Services. It will be installed in the following location: `specified-directory`/CommonService The default location is as follows: /opt/hitachi/CommonService Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: /usr /usr/local /var root directory (/)
Host name or IP address	For a new installation: You can specify a host name in FQDN format. The host name (or FQDN) or IP address specified in this step is used in the URL for accessing the Hitachi Ops Center Portal. To change the host name (or FQDN) or IP address that is used to access the Hitachi Ops Center Portal, run the cschgconnect command after installation. For details about the cschgconnect command, see Changing the management server host name, IP address, or port number. The management server where Common Services and other relevant products are installed and the web browser used to access the Hitachi Ops Center Portal must be able to resolve and reach the host name (or FQDN) and IP address. If you specify a host name (or FQDN), specify a value using no more than 128 characters. You cannot specify uppercase characters in the host name (or FQDN). If you do, they are converted to lowercase characters and then registered.
Port number	For a new installation: Specify a value in the range 1 - 65535. Default: 443 If you install the following products on the same management server, there will be conflicts with the default port number 443: Protector Administrator Change the port number so that it does not conflict between the products. If you want to change the port number for Common Services to a number other than 443, we recommend using port number 20950.
Do you want to access to Hitachi Ops Center Portal by using both host name and IP address ?	For a new installation where a host name or FQDN is specified: Specify y or n. Default: n
Do you want to back up the Common Services database first ?	For an upgrade or overwrite installation: Specify y or n. Default: y
Database backup location	For an upgrade or overwrite installation where you want to back up the database: Specify a directory by using 150 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the root directory (/). Default: /var/`installation-directory`/backup
Admin user name	For a new installation of another product when Common Services has already been installed: Specify the username of the Common Services administrator. Specify a user who belongs to the user group to which the opscenter-system-administrator or the opscenter-security-administrator role is assigned.
Password	For a new installation of another product when Common Services has already been installed: Specify the password of the Common Services administrator.

For Administrator:

Setting items	Description
IP address	For a new installation: Specify a value in IPv4 format. Default: IP address of the system
Port number	For a new installation: Specify a value in the range 1 - 65535. Default: 20961
User name	For an upgrade installation: Default: sysadmin
Password	For an upgrade installation: Default: None
Network mode	Specify the container network mode by using either of the following: bridge: Uses the container bridge network. host: Uses the container host network. Use this mode if you must disable the kernel parameter net.ipv4.ip_forward. For a new installation: Specify 1 (bridge) or 2 (host). Default: 1 For an upgrade installation: If you want to change the current network mode, specify 1 (bridge) or 2 (host).

For API Configuration Manager:

Setting items	Description
Install directory	For a new installation: Specify the directory in which to install API Configuration Manager. It will be installed in the following location: `specified-directory`/ConfManager The default location is as follows: /opt/hitachi/ConfManager Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: /usr /usr/local /var root directory (/)
Do you want to back up the API Configuration Manager database first ?	For an upgrade installation: Specify y or n. Default: y
Database backup location	For an upgrade installation where you want to back up the database: Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: /usr /usr/local /var root directory (/) Default: `specified-directory`/backup/bak_CONFIG_MGR

Setting items

Description

Install directory

For a new installation:

Specify the directory in which to install API Configuration Manager.
It will be installed in the following location:

specified-directory/ConfManager

The default location is as follows:

/opt/hitachi/ConfManager
Specify a directory by using 64 or fewer bytes and the following characters:
A-Z, a-z, 0-9, underscores (_), and forward slashes (/)
You cannot specify the following paths:
- /usr
- /usr/local
- /var
- root directory (/)

Do you want to back up the API Configuration Manager database first ?

For an upgrade installation:

Specify y or n.
Default: y

Database backup location

For an upgrade installation where you want to back up the database:

Specify a directory by using 64 or fewer bytes and the following characters:
A-Z, a-z, 0-9, underscores (_), and forward slashes (/)
You cannot specify the following paths:
- /usr
- /usr/local
- /var
- root directory (/)
Default: specified-directory/backup/bak_CONFIG_MGR

For Protector:

Setting items	Description
Install directory	For a new installation: Specify the directory in which to install Protector. It will be installed in the following location: `specified-directory`/protector The default location is as follows: /opt/hitachi/protector
Node name	For a new installation: Default: Node name of the operating system
User account on the local system	For a new installation: Default: root
Port number	For a new installation: Default: 20964

For Automator:

Setting items	Description
Install directory	For a new installation: Specify the directory in which to install Automator. It will be installed in the following location: `specified-directory`/Automation The default location is as follows: /opt/hitachi/Automation Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: /usr /usr/local /var root directory (/)
Host name or IP address	For a new installation: If you specify a host name specify a value using no more than 128 characters.
Database directory	For a new installation: Specify a directory by using 90 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the root directory (/). Default: /var/`specified-directory`/database
Do you want to back up the Automator database first ?	For an upgrade or overwrite installation: Specify y or n. Default: y
Database backup location	For an upgrade or overwrite installation where you want to back up the database: Specify a directory by using 150 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the root directory (/). Default: /var/`specified-directory`/Automation_backup

For Analyzer:

Setting items	Description
Install directory	For a new installation: Specify the directory in which to install Analyzer. It will be installed in the following location: `specified-directory`/Analytics The default location is as follows: /opt/hitachi/Analytics If you specify a directory other than the default, refer to the product manual for the requirements.

Setting items

Description

Install directory

For a new installation:

Specify the directory in which to install Analyzer.
It will be installed in the following location:

specified-directory/Analytics

The default location is as follows:

/opt/hitachi/Analytics
If you specify a directory other than the default, refer to the product manual for the requirements.

For Analyzer detail view:

Setting items	Description
Installation-destination device	For a new installation: A list of devices on the management server is displayed. Default: Devices with enough free space for the installation are displayed. If you want to use a device other than the default, specify a device name from the displayed list.
Directory for storing application data	For a new installation: Specify the directory where the application data will be stored. The default location is as follows: /data If you specify a directory other than the default, refer to the product manual for the requirements.
HTTP access port for internal communication	For a new installation: If port number 8080 is being used by another program, specify a value from 10000 to 65530.
HTTPS access port	For a new installation: If port number 8443 is being used by another program, specify a value from 10000 to 65530.
Password for the megha and meghadata users	For a new installation: Specify the password for the megha and meghadata users. The specified password will be set for both the megha and meghadata users.

For Analyzer viewpoint:

Setting items	Description
HTTPS access port for internal communication	If port number 25442 is being used by another program, specify a value from 1 to 65535.

For Command Control Interface:

Setting items	Description
Install directory	For a new installation (when installing API Configuration Manager or Protector): Specify the directory in which to install Command Control Interface. It will be installed in the following location: `specified-directory`/HORCM The default location is as follows: /opt/hitachi/HORCM Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: Paths containing /ConfManager/ Root directory (/)

Setting items

Description

Install directory

For a new installation (when installing API Configuration Manager or Protector):

Specify the directory in which to install Command Control Interface.
It will be installed in the following location:

specified-directory/HORCM

The default location is as follows:

/opt/hitachi/HORCM
Specify a directory by using 64 or fewer bytes and the following characters:
A-Z, a-z, 0-9, underscores (_), and forward slashes (/)
You cannot specify the following paths:
- Paths containing /ConfManager/
- Root directory (/)

Check the information you entered and the message that appears.

If both API Configuration Manager and Protector are included as products to install, a message related to Command Control Interface might appear. Check the message and then continue.

If there are no problems, press y to begin the installation.
When the installation is complete, the results are displayed:
- If all installation tasks finished successfully, Completed successfully. is displayed.
- If any task fails, Failed. is displayed.
If Common Services registration displays a Failed. status, you must register the product manually after installing all the products and completing the SSL communications configuration.

Note: When it takes a long time to install Automator, a KNAE04747-E message might be shown on the console even if the installation is successful. If "Hitachi Ops Center Automator installation completed successfully." is output after the KNAE04747-E message, the installation processing might have completed successfully. Wait several minutes, check whether the Automator service is running, and if the service is running, log in to Automator. If the Automator service is stopped, start the Automator service, and log in to Automator. If the login is successful, the installation processing is done, and you can ignore the KNAE04747-E message.
If you are upgrading from Common Services version 10.9.2 or earlier using the SAML protocol to link with AD FS, you must register the metadata re-acquired from Common Services in AD FS when the upgrade is complete.
For the registration procedure, see:
- Exporting Common Services metadata (AD FS)
- Registering Common Services in AD FS as a relying party
If you are upgrading Common Services from version 10.9.3 or earlier and Common Services is linked with an Active Directory server, after upgrading check the settings of Add all users under User base DN to opscenter-users group in the Hitachi Ops Center Portal Edit user directory service window.
Note: Active Directory users are displayed in the Hitachi Ops Center Portal Users window. If there are a large number of users, it might take time to display the screen. If necessary, specify a search filter in Custom user LDAP filter to narrow down the Active Directory users to display. The search-filter syntax must conform to RFC 2254.
- If Enable is specified, all Active Directory users under the User base DN are retrieved. Specify a search filter in Custom user LDAP filter.
- If Disable is specified, the value of Group entry list is automatically specified in Custom user LDAP filter when you upgrade. Change the setting as needed.

Proceed as follows:

If you are installing API Configuration Manager, Protector Client, or Analyzer probe server on a server other than Common Services, go to Using the Client Express installer.
If you are not installing these products or plan to install them later, go to Configuring SSL communications.

Installing OS updates and other products after installation

The following table outlines the installation tasks for operating system patches and Hitachi Ops Center updates where the installer is used.

Task	Implementation method
Apply operating system patches	Apply as needed.
Update the operating system	You can update the OS as described in Applying Linux security updates using yum.
Upgrade Hitachi Ops Center products	For an upgrade installation or overwrite installation, use the Express installer or individual installers.
Install additional Hitachi Ops Center products	Confirm the system requirements of the products, install prerequisite packages, and reconfigure kernel parameters as necessary. For details on the product system requirements, see the documentation or Release Notes for each product.

Using the Client Express installer

Using the Client Express installer, you can simultaneously install or upgrade the following products:

Hitachi Ops Center API Configuration Manager
Hitachi Ops Center Protector Client
Hitachi Ops Center Analyzer probe server

To use API Configuration Manager or Protector Client, the prerequisite program Command Control Interface is required. If you use the Client Express installer to install API Configuration Manager or Protector Client, Command Control Interface is also installed. Do not use this instance of Command Control Interface for other purposes.

Note: If Command Control Interface was already installed by using one of the following previous installations, upgrade it by using the Client Express installer:

Client Express installer
API Configuration Manager individual installer

If the currently installed Command Control Interface instance is a newer version, it will be left in place.

If Command Control Interface was individually installed by using a different method, it will not be upgraded. If necessary, you can upgrade it manually.

If you do not want to use an individually installed instance of Command Control Interface and want to replace it with an instance of Command Control Interface installed by the Client Express installer, or if you want to replace an instance of Command Control Interface installed by the Client Express installer with an individually installed instance of Command Control Interface, see Replacing Command Control Interface.

Preparing the server

Make sure that the server on which you plan to install Hitachi Ops Center products meets the system requirements that are described in the documentation or Release Notes for each product.

Make sure that you complete the following actions on the installation destination:

To install prerequisite packages, the Client Express installer requires the repository settings for the yum command. Specify the yum repository settings in advance, or specify the settings by following the message displayed when you run the Client Express installer.
When performing a new installation of the Analyzer probe server, do not install Analyzer detail view on the same server.

Note: If you run the Client Express installer, the iptables and firewalld settings are changed so that required communications can be established. If you use nftables, you must make the changes manually.

Installing or upgrading each product

To install or upgrade each product, use the Client Express installer.

For best results, close all other programs, including:

Security-monitoring programs
Virus-detection programs
Process-monitoring programs

If the Services window is open, close it.

Log in to the server as the root user or use the sudo command.
To start the Client Express installer, run install.sh, which is in the root directory of the installation media.

Note: If one or more products cannot be installed in the same environment as a currently installed product, the Client Express installer will not install the applicable products and a warning message is displayed.
If the yum repository settings are not configured or cannot be used, a message appears asking if you want to run the Yum Setup Helper tool. Follow the displayed message to configure the settings.
1. To configure the settings, enter y. The Yum Setup Helper window is displayed.
2. From Content in Current Dir, use the cursor keys and then the Enter key to select the directory that includes the OS media file (ISO file).
  
  Note: The Yum Setup Helper tool uses the OS media file to configure the yum repository settings, so the OS media file must be stored on the management server. If the OS media file does not exist, get it from the distribution website. Click Help to see information about the corresponding OS media file.
3. Select the ISO file. The file name is displayed for Selected Item.
4. Click OK. Configuration of the yum repository settings starts, and a processing window is displayed.
  
  Tip: You can also use the tab key to move the cursor between items in the window.
5. When configuration of the yum repository settings is complete, a message is displayed. Select OK. If the configuration fails, an error message is displayed. If you select OK, the window where you can select an OS media file is displayed again.
Choose the product you want to install, and then press Enter.
If you select 1 All, the products listed within the parentheses are installed.
To select multiple products, separate the numbers with commas. (Example: 2,3)

Note: You cannot select products that have ** displayed for the product number.
For new Analyzer probe server installations, set the scale of the resources to be managed by the product by choosing one of the following scale values:
- 1: Small-scale configuration
- 2: Medium-scale configuration
- 3: Large-scale configuration
Note:
- For details on the system requirements for each product based on scale, see Hitachi Ops Center System Requirements.
- Depending on the physical memory size of the server to be installed, some scales might not be displayed.

Follow the prompts and specify the required information.

For API Configuration Manager:

Setting items	Description
Install directory	For a new installation: Specify the directory in which to install API Configuration Manager. It will be installed in the following location: `specified-directory`/ConfManager The default location is as follows: /opt/hitachi/ConfManager Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: /usr /usr/local /var root directory (/)
Whether backup is required	For an upgrade installation: Specify y or n. Default: y
Backup directory	If you selected y for the setting "Whether backup is required" for an upgrade installation: Specify the directory for the backup of API Configuration Manager. It will be backed up in the following location: `specified-directory`/backup/bak_CONFIG_MGR The default location is as follows: /opt/hitachi/backup/bak_CONFIG_MGR Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: /usr /usr/local /var root directory (/)

Setting items

Description

Install directory

For a new installation:

Specify the directory in which to install API Configuration Manager.
It will be installed in the following location:

specified-directory/ConfManager

The default location is as follows:

/opt/hitachi/ConfManager
Specify a directory by using 64 or fewer bytes and the following characters:
A-Z, a-z, 0-9, underscores (_), and forward slashes (/)
You cannot specify the following paths:
- /usr
- /usr/local
- /var
- root directory (/)

Whether backup is required

For an upgrade installation:

Specify y or n.
Default: y

Backup directory

If you selected y for the setting "Whether backup is required" for an upgrade installation:

Specify the directory for the backup of API Configuration Manager.
It will be backed up in the following location:

specified-directory/backup/bak_CONFIG_MGR

The default location is as follows:

/opt/hitachi/backup/bak_CONFIG_MGR
Specify a directory by using 64 or fewer bytes and the following characters:
A-Z, a-z, 0-9, underscores (_), and forward slashes (/)
You cannot specify the following paths:
- /usr
- /usr/local
- /var
- root directory (/)

For Protector Client:

Setting items	Description
Install directory	For a new installation: Specify the directory in which to install Protector Client. It will be installed in the following location: `specified-directory`/protector The default location is as follows: /opt/hitachi/protector Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: /usr /usr/local /var root directory (/)
Node name	For a new installation: Default: Node name of the operating system
Master node name	For a new installation: Specify the node name or IP address of the master OS.
Internet connected	For a new installation: Select whether to install a client node as a node connected to the internet. Specify y or n. Default: n

For Analyzer probe server:

Setting items	Description
Application data path	For a new installation: Specify the directory where the application data will be stored. The default location is as follows: /home If you specify a directory other than the default, refer to the product manual for the requirements.
HTTP access port for internal communication	For a new installation: If port number 8080 is being used by another program, specify a value from 10000 to 65530.
HTTPS access port	For a new installation: If port number 8443 is being used by another program, specify a value from 10000 to 65530.
Port used for the on-demand real time monitoring module	For a new installation: If port number 24262 is being used by another program, specify a value from 10000 to 65530.
Password for megha user	For a new installation: Specify the password for megha user.
Do you want to install the Virtual Storage Software Agent?	If the Virtual Storage Software Agent is not installed: When you want to monitor VSP One SDS Block storage systems, you need to install the Virtual Storage Software Agent. Specify y or n. Default: n
Installation destination directory for the Virtual Storage Software Agent	When installing the Virtual Storage Software Agent: Specify the installation destination directory for the Virtual Storage Software Agent: It will be installed in the following location: `specified-directory`/VirtualStorageSoftwareAgent The default location is as follows: /opt/hitachi/VirtualStorageSoftwareAgent If you specify a directory other than the default, refer to the product manual for the requirements.
IP address of the Analyzer server	When installing the Virtual Storage Software Agent: The IP address specified here is used when configuring the firewall. Specify a value in IPv4 format. Default: IP address of the system

For Command Control Interface:

Setting items	Description
Install directory	For a new installation (when installing API Configuration Manager or Protector Client): Specify the directory in which to install Command Control Interface. It will be installed in the following location: `specified-directory`/HORCM The default location is as follows: /opt/hitachi/HORCM Specify a directory by using 64 or fewer bytes and the following characters: A-Z, a-z, 0-9, underscores (_), and forward slashes (/) You cannot specify the following paths: Paths containing /ConfManager/ Root directory (/)

Setting items

Description

Install directory

For a new installation (when installing API Configuration Manager or Protector Client):

Specify the directory in which to install Command Control Interface.
It will be installed in the following location:

specified-directory/HORCM

The default location is as follows:

/opt/hitachi/HORCM
Specify a directory by using 64 or fewer bytes and the following characters:
A-Z, a-z, 0-9, underscores (_), and forward slashes (/)
You cannot specify the following paths:
- Paths containing /ConfManager/
- Root directory (/)

Check the information you entered and the message that appears.
If both API Configuration Manager and Protector Client are included as products to install, a message related to Command Control Interface might appear. Check the message and then continue.

If there are no problems, press y to begin the installation.
Note: If you are installing Analyzer probe server, the following message might appear, but you can ignore it.
```
root@localhost's password:
```
When the installation is complete, the results are displayed:
- If all installation tasks finished successfully, Completed successfully. is displayed.
- If any task fails, Failed. is displayed.
Note: To use single sign-on or other features provided by Common Services on the installed Analyzer probe server, register the Analyzer probe server in Common Services after configuring SSL communications.

Configuring SSL communications

Configure SSL on the Hitachi Ops Center products to ensure secure communications. Hitachi Ops Center products use a self-signed certificate or a valid server certificate to perform SSL/TLS communications. The self-signed certificate is used when operation checks are performed, so configure SSL communications using a valid server certificate.

To configure SSL communications, use the SSL Setup tool (cssslsetup command) or configure the settings manually. For details, see Configuring SSL communications. Note that you cannot use the SSL Setup tool to configure SSL communications for Protector clients. For details on how to configure SSL communications for Protector clients, see the Protector documentation.

After you finish configuring SSL communications, if there is product that must be registered with Common Services, go to Registering Hitachi Ops Center products with Common Services. If you do not need to register a product, go to Initial setup using the Hitachi Ops Center Portal.

Registering Hitachi Ops Center products with Common Services

If you want to use the functions provided by Common Services, such as the Portal window, user management, or single sign-on, run the setupcommonservice command to register each product with Common Services.

If you use the Server Express installer, the products are automatically registered in Common Services. However, in the following cases, you must use the setupcommonservice command to manually register each product.

If the product that you installed by using the Server Express installer fails to register in Common Services
If the result of product registration in Common Services is displayed as Failed., the product registration fails.
If you are registering the Analyzer probe server installed by using the Client Express installer.

If you do not need to register products in Common Services, go to Initial setup using the Hitachi Ops Center Portal.

Note: You cannot unregister a Hitachi Ops Center product using the setupcommonservice command. To delete products, use the Hitachi Ops Center Portal.

After installing Common Services, change the initial password for the built-in account (the sysadmin user) on the Hitachi Ops Center Portal. If you use the initial password to log in to the Hitachi Ops Center Portal, the Change password window is displayed. Specify a new password. For details, see Logging in to the Hitachi Ops Center Portal.
Ensure that each product can resolve the host name where Common Services is installed. If you want to use a host name that is not a fully qualified domain name (FQDN), set the IP address and the host name in the /etc/hosts file for name resolution. If you want to use an IP address instead of a host name, log in to the management server where Common Services is installed and run the cschgconnect.sh command.
Ensure that the Hitachi Ops Center product server and the Common Services server are running.
For the Common Services account to be specified for the setupcommonservice command, specify a user who belongs to the opscenter-administrators group.

Note: If you change the Common Services host name, IP address, or server port number changes, you must register each product again.

The location of the setupcommonservice command, command syntax, and command examples for each product are as follows:

Administrator

Default location: /opt/rainier/bin

Command syntax:

setupcommonservice --csUri CommonService_URL --applicationPort port_number --applicationHostAddress ip_address --applicationName app_name [--appDescription app_description] [--csUsername CommonService_Username] [--tlsVerify --csUriCACert Certificate_FileName]

Command example:

setupcommonservice --csUri https://example.com/portal --csUsername sysadmin --tlsVerify --csUriCACert certificate.cer --applicationPort 20961 --applicationHostAddress 192.0.2.11 --applicationName MyAdministrator1

Protector

Default location: /opt/hitachi/protector/bin/

Command syntax:

setupcommonservice --cs-uri CommonService_URL [--cs-username CommonService_Username] --app-scheme protocol --app-hostname host_name --app-port port_number

Command example:

setupcommonservice --cs-uri https://example.com/portal --cs-username sysadmin --app-scheme https --app-hostname MyHost --app-port 20964

Automator

Default location: /opt/hitachi/Automation/bin/

Command syntax:

setupcommonservice {[-csUri CommonService_URL | -csUri CommonService_URL -csUsername CommonServiceUsername] [-appName app_name] [-appDescription app_description] [-auto] | -help}

Command example:

setupcommonservice -csUri https://example.com/portal -appName MyAutomator1

Analyzer

Default location: /opt/hitachi/Analytics/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL [-csUsername CommonService_Username] [-appPort port_number] [-appHostname ip_address_or_host_name] [-appName app_name] [-appDescription app_description] [-auto]

Command example:

setupcommonservice -csUri https://example.com/portal -appPort 22016 -appHostname 192.0.2.10 -appName MyAnalyzer1

Analyzer detail view

Default location: /usr/local/megha/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerdetailview1 -appDescription ""

Analyzer probe

Default location: /usr/local/megha/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerprobe1 -appDescription ""

Analyzer viewpoint

Default location: /opt/hitachi/analyzer_viewpoint/bin/

Command syntax:

setupcommonservice --csUri CommonService_URL [--csUsername CommonServiceUsername] [--applicationName app_name]

Command example:

setupcommonservice --csUri https://example.com

When the Hitachi Ops Center products are registered in Common Services, go to Initial setup using the Hitachi Ops Center Portal.

Installing OS updates and other products after installation

The following table outlines the installation tasks for operating system patches and Hitachi Ops Center updates where the installer is used.

Task	Implementation method
Apply operating system patches	Apply as needed.
Update the operating system	You can update the OS as described in Applying Linux security updates using yum.
Upgrade Hitachi Ops Center products	For an upgrade installation or overwrite installation, use the Express installer or individual installers.
Install additional Hitachi Ops Center products	Confirm the system requirements of the products, install prerequisite packages, and reconfigure kernel parameters as necessary. For details on the product system requirements, see the documentation or Release Notes for each product.

Installing or upgrading Hitachi Ops Center products by using the individual installer

To install or upgrade, or to create a new Hitachi Ops Center system without using the Express installer, install the products by using the Common Services installer first and then additional products using the individual installer.

Workflow for installing and setting up Hitachi Ops Center (individual installers)

The general workflow for using the individual installer for each product is as follows:

After setting up access control, configure the settings for each product as necessary. For details, see the documentation for each product.

Preparing the management server

Make sure that the management server on which you plan to install Hitachi Ops Center products meets the system requirements.

For the Common Services system requirements, see the Hitachi Ops Center Release Notes. For the system requirements of other Hitachi Ops Center products, see the documentation or Release Notes for each product.

For a complete list of Hitachi Ops Center system requirements, go to the Ops Center documentation site and select Hitachi Ops Center System Requirements.

Note:

Hitachi Ops Center does not support installing other software products on the management server, but allows for installing software required by corporate policy such as anti-virus programs and third-party monitoring agents. Note that Hitachi Vantara does not take responsibility for or support any interactions between the third-party programs and the Hitachi Ops Center software.
When Common Services is installed, the following RPM packages are installed:
- Amazon Corretto 21
- PostgreSQL 15
Common Services starts the Common Services service by using the postgres user and postgres group created on the management server.

Configurations where postgres users and postgres groups do not exist on the management server are not supported.

If the users on the management server are managed by an external authentication server, the Common Services service cannot start when the OS starts.

Make sure there are no conflicts among the following port numbers.

Port number used to access Common Services:

443/tcp (default)

Port numbers used for internal communication:

20951/tcp
20952/tcp
20954/tcp
20955/tcp
20956/tcp

If necessary, register the port number that is used to access Common Services in the firewall exceptions. For details on how to register firewall exceptions, see the OS documentation.

Installing or upgrading Common Services

To install or upgrade Common Services in an existing environment or to create a Hitachi Ops Center system without using the Express installer, install Common Services by using the individual installer.

Note:

If you install Common Services, Amazon Corretto 21 and PostgreSQL 15 are installed. If you upgrade Common Services, Amazon Corretto 8 (version 10.6.0 and earlier), Amazon Corretto 11 (versions 10.6.1 to 10.9.1), Amazon Corretto 17 (versions 10.9.2 to 11.0.2), and PostgreSQL 11 (version 10.9.2 and earlier) that were installed with the previous version are not removed. If you do not need these programs, remove them by using the rpm command. If you cannot remove the programs by using this command, use the rpm command with the --nopreun option specified.
The package names are as follows:
- Amazon Corretto 8: java-1.8.0-amazon-corretto-devel
- Amazon Corretto 11: java-11-amazon-corretto-devel
- Amazon Corretto 17: java-17-amazon-corretto-devel
- PostgreSQL 11: postgresql11, postgresql11-server, postgresql11-libs

Confirm that one of the following settings is configured on the management server installation destination:
- The management server can access your DNS server.
- The host name is set in the hosts file.
If the system cannot resolve the management server host name, it might take a long time for Common Services to start.
If you are logged in to the Hitachi Ops Center Portal, close the web browser before beginning the upgrade. If you upgrade Common Services while logged in to the Hitachi Ops Center Portal, an internal server error might occur. If this error occurs, restart the web browser.
In Common Services version 10.9.1 and later, a special group named support-services has been added as a default user group. This group is used for support services, so it cannot be used for standard purposes. For this reason, if you want to upgrade from version 10.9.0 or earlier, first make sure that the support-services group does not exist.
- If the support-services group was imported by linking with an Active Directory server, delete the group. In addition, on the User directories window of the Hitachi Ops Center Portal, click the Edit user directory service icon for the Active Directory server, and then change the Group entry list setting so that the support-services group will not be imported.
- If the system administrator created the support-services group using a method other than linking with an Active Directory server, delete or rename the group before upgrading from version 10.9.0 or earlier.
Note: If you upgrade Common Services from version 10.9.0 or earlier while the support-services group exists, you must delete or rename the group and then perform an overwrite installation of Common Services.
Before performing an upgrade installation of Common Services in an environment integrated with an Active Directory or LDAP server: on the Active Directory or LDAP server editing window of Hitachi Ops Center Portal, run a Test connection and Test authentication to ensure that they are successful. For details, see Configuring Active Directory as a directory service for Ops Center or Configuring a non-AD directory service for Ops Center (LDAP server).
If you perform an upgrade installation without a proper connection or authentication, Active Directory users might be unable to log in to the Hitachi Ops Center Portal.

Note: If Active Directory users cannot log in to the Hitachi Ops Center Portal in an environment integrated with an Active Directory server, check the connection and authentication with the Active Directory server. After that, log in to Hitachi Ops Center Portal, and click Sync groups on the User directories window to synchronize Active Directory groups with Common Services.

Log in to the management server as the root user.
If you log on as an ordinary user, use the sudo command to complete the following procedure as the root user.
Run install.sh, which is in the following directory on the installation media:
root-directory-of-installation-media/COMSERV
To install Common Services, follow the prompts and specify the required information as follows:
For new installations of Common Services:
- Installation destination for Common Services
  
  The default installation destination for Common Services is as follows:
  /opt/hitachi/CommonService
  
  User data for Common Services is stored in the following user data directory:
  /var/installation-directory-of-Common-Services
- Host name (or FQDN) or IP address
  
  The host name (or FQDN) or IP address specified in this step is used in the URL for accessing the Hitachi Ops Center Portal. To change the host name (or FQDN) or IP address that is used to access the Hitachi Ops Center Portal, run the cschgconnect command after installation. For details about the cschgconnect command, see Changing the management server host name, IP address, or port number.
  
  The management server on which Common Services and other relevant products are installed and the web browser used to access the Hitachi Ops Center Portal must be able to resolve and reach the host name (or FQDN) and IP address.
  
  If you specify a host name (or FQDN), specify a value using no more than 128 characters.
  
  You cannot specify uppercase characters in the host name (or FQDN). If you do, they are converted to lowercase characters and then registered.
- Port number of the access URL
  If you install the following products on the same management server, there will be conflicts with the default port number 443. Change the port number so that it does not conflict between the products. If you want to change the port number for Common Services to a number other than 443, the best practice is to use port number 20950.
  
  Protector
  
  Administrator
- Whether access is possible by using an IP address
  Specify whether an IP address can be used to access the Hitachi Ops Center Portal when a host name or FQDN is specified in the access URL.
  
  To maintain the default setting of not permitting access by using an IP address, specify y.
  
  To permit access by using an IP address, specify n.
  An IP address acquired from the system is automatically set for the access URL.
For overwrite or upgrade installations of Common Services:
- Whether to back up the existing Common Services database
- If yes, the database backup destination
- If you are upgrading from version 10.9.1 or earlier, whether to continue or interrupt the installation when there is not enough free space on the disk
Check the information you entered and any messages displayed. If there are no problems, press y to begin the installation.
Check the message that appears when installation is complete.
Change the initial password for the built-in account (the sysadmin user) on the Hitachi Ops Center Portal.
If you use the initial password to log in to the Hitachi Ops Center Portal, the Change password window is displayed. Specify a new password. For details, see Logging in to the Hitachi Ops Center Portal.
If you are upgrading from Common Services version 10.9.2 or earlier using the SAML protocol to link with AD FS, you must register the metadata re-acquired from Common Services in AD FS when the upgrade is complete.
For the registration procedure, see:
- Exporting Common Services metadata (AD FS)
- Registering Common Services in AD FS as a relying party
If you are upgrading Common Services from version 10.9.3 or earlier and Common Services is linked with an Active Directory server, after upgrading check the settings of Add all users under User base DN to opscenter-users group in the Hitachi Ops Center Portal Edit user directory service window.
Note: Active Directory users are displayed in the Hitachi Ops Center Portal Users window. If there are a large number of users, it might take time to display the screen. If necessary, specify a search filter in Custom user LDAP filter to narrow down the Active Directory users to display. The search-filter syntax must conform to RFC 2254.
- If Enable is specified, all Active Directory users under the User base DN are retrieved. Specify a search filter in Custom user LDAP filter.
- If Disable is specified, the value of Group entry list is automatically specified in Custom user LDAP filter when you upgrade. Change the setting as needed.

Installing or upgrading each product

You install other products after you install Common Services. For details on the installation procedure, see the documentation for the individual product.

If you complete an upgrade or overwrite installation of an existing product, the installation destination is the same as the current installation destination.

Note:

If the password for the built-in account (the sysadmin user) for the Hitachi Ops Center Portal is set to the initial password, you must change it before installing any products. If you use the initial password to log in to the Hitachi Ops Center Portal, the Change password window is displayed. Specify a new password. For details, see Logging in to the Hitachi Ops Center Portal.
If you upgrade Automator or Analyzer from a version earlier than 10.0, verify that SSL communication is configured.

Configuring SSL communications

By default, Common Services uses SSL/TLS communications. Immediately after installation, the system uses SSL communication by using a self-signed certificate. However, you must set up SSL communications to use a valid server certificate before any of the products can communicate with Common Services and the Hitachi Ops Center Portal.

For details on how to configure SSL communications, see Configuring SSL communications.

When you finish configuring SSL communications, go to Registering Hitachi Ops Center products with Common Services.

Registering Hitachi Ops Center products with Common Services

If you used an individual installer to install each product, run the setupcommonservice command to register each product in Common Services.

If you do not need to register products in Common Services, go to Initial setup using the Hitachi Ops Center Portal.

Note: You cannot unregister a Hitachi Ops Center product using the setupcommonservice command. To delete products, use the Hitachi Ops Center Portal.

After installing Common Services, change the initial password for the built-in account (the sysadmin user) on the Hitachi Ops Center Portal. If you use the initial password to log in to the Hitachi Ops Center Portal, the Change password window is displayed. Specify a new password. For details, see Logging in to the Hitachi Ops Center Portal.
Ensure that each product can resolve the host name where Common Services is installed. If you want to use a host name that is not a fully qualified domain name (FQDN), set the IP address and the host name in the /etc/hosts file for name resolution. If you want to use an IP address instead of a host name, log in to the management server where Common Services is installed and run the cschgconnect.sh command.
Ensure that the Hitachi Ops Center product server and the Common Services server are running.
For the Common Services account to be specified for the setupcommonservice command, specify a user who belongs to the opscenter-administrators group.

Note: If you change the Common Services host name, IP address, or server port number changes, you must register each product again.

The location of the setupcommonservice command, command syntax, and command examples for each product are as follows:

Administrator

Default location: /opt/rainier/bin

Command syntax:

setupcommonservice --csUri CommonService_URL --applicationPort port_number --applicationHostAddress ip_address --applicationName app_name [--appDescription app_description] [--csUsername CommonService_Username] [--tlsVerify --csUriCACert Certificate_FileName]

Command example:

setupcommonservice --csUri https://example.com/portal --csUsername sysadmin --tlsVerify --csUriCACert certificate.cer --applicationPort 443 --applicationHostAddress 192.0.2.11 --applicationName MyAdministrator1

Protector

Default location: /opt/hitachi/protector/bin/

Command syntax:

setupcommonservice --cs-uri CommonService_URL [--cs-username CommonService_Username] --app-scheme protocol --app-hostname host_name --app-port port_number

Command example:

setupcommonservice --cs-uri https://example.com/portal --cs-username sysadmin --app-scheme https --app-hostname MyHost --app-port 443

Automator

For Linux:

Default location: /opt/hitachi/Automation/bin/

Command syntax:

setupcommonservice {[-csUri CommonService_URL | -csUri CommonService_URL -csUsername CommonServiceUsername] [-appName app_name] [-appDescription app_description] [-auto] | -help}

Command example:

setupcommonservice -csUri https://example.com/portal -appName MyAutomator1

For Windows:

Default location: Program-Files-folder\hitachi\Automation\bin

Command syntax:

setupcommonservice {[/csUri CommonService_URL | /csUri CommonService_URL /csUsername CommonServiceUsername] [/appName app_name] [/appDescription app_description] [/auto] | /help}

Command example:

setupcommonservice /csUri https://example.com/portal /appName MyAutomator1

Analyzer

Default location: /opt/hitachi/Analytics/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL [-csUsername CommonService_Username] [-appPort port_number] [-appHostname ip_address_or_host_name] [-appName app_name] [-appDescription app_description] [-auto]

Command example:

setupcommonservice -csUri https://example.com/portal -appPort 22016 -appHostname 192.0.2.10 -appName MyAnalyzer1

Analyzer detail view

Default location: /usr/local/megha/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerdetailview1 -appDescription ""

Analyzer probe

Default location: /usr/local/megha/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerprobe1 -appDescription ""

Analyzer viewpoint

Default location: /opt/hitachi/analyzer_viewpoint/bin/

Command syntax:

setupcommonservice --csUri CommonService_URL [--csUsername CommonServiceUsername] [--applicationName app_name]

Command example:

setupcommonservice --csUri https://example.com

When the Hitachi Ops Center products are registered in Common Services, go to Initial setup using the Hitachi Ops Center Portal.

Registering Ops Center products with Common Services (setupcommonservice)

Use the setupcommonservice command to register Ops Center products with Common Services.

Ensure that each product can resolve the host name where Common Services is installed. If you want to use a host name that is not a fully qualified domain name (FQDN), set the IP address and the host name in the /etc/hosts file for name resolution. If you want to use an IP address instead of a host name, log in to the management server where Common Services is installed and run the cschgconnect.sh command.
Ensure that the Ops Center product server and the Common Services server are running.
Use a Common Services account with the "Application Administrator" role to run setupcommonservice command.

Note: Products deployed by using the Ops Center OVA are already registered in Common Services.

If you change the Common Services host name, IP address, or server port number changes, you must register each product again.

The setupcommonservice command also sets each Ops Center product as an authentication server that uses Common Services. You can then access the application from the portal using the Ops Center credentials.

Administrator

Default location: /opt/rainier/bin

Command syntax:

setupcommonservice --csUri CommonService_URL --applicationPort port_number --applicationHostAddress ip_address --applicationName app_name [--appDescription app_description] [--csUsername CommonService_Username] [--tlsVerify --csUriCACert Certificate_FileName]

Command example:

setupcommonservice --csUri https://example.com/portal --csUsername sysadmin --tlsVerify --csUriCACert certificate.cer --applicationPort 443 --applicationHostAddress 192.0.2.11 --applicationName MyAdministrator1

Protector

Default location: /opt/hitachi/protector/bin/

Command syntax:

setupcommonservice --cs-uri CommonService_URL [--cs-username CommonService_Username] --app-scheme protocol --app-hostname host_name --app-port port_number

Command example:

setupcommonservice --cs-uri https://example.com/portal --cs-username sysadmin --app-scheme https --app-hostname MyHost --app-port 443

Automator

For Linux:

Default location: /opt/hitachi/Automation/bin/

Command syntax:

setupcommonservice {[-csUri CommonService_URL | -csUri CommonService_URL -csUsername CommonServiceUsername] [-appName app_name] [-appDescription app_description] [-auto] | -help}

Command example:

setupcommonservice -csUri https://example.com/portal -appName MyAutomator1

For Windows:

Default location: Program-Files-folder\hitachi\Automation\bin

Command syntax:

setupcommonservice {[/csUri CommonService_URL | /csUri CommonService_URL /csUsername CommonServiceUsername] [/appName app_name] [/appDescription app_description] [/auto] | /help}

Command example:

setupcommonservice /csUri https://example.com/portal /appName MyAutomator1

Analyzer

Default location: /opt/hitachi/Analytics/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL [-csUsername CommonService_Username] [-appPort port_number] [-appHostname ip_address_or_host_name] [-appName app_name] [-appDescription app_description] [-auto]

Command example:

setupcommonservice -csUri https://example.com/portal -appPort 22016 -appHostname 192.0.2.10 -appName MyAnalyzer1

Analyzer detail view

Default location: /usr/local/megha/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerdetailview1 -appDescription ""

Analyzer probe

Default location: /usr/local/megha/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerprobe1 -appDescription ""

Analyzer viewpoint

Default location: /opt/hitachi/analyzer_viewpoint/bin/

Command syntax:

setupcommonservice --csUri CommonService_URL [--csUsername CommonServiceUsername] [--applicationName app_name]

Command example:

setupcommonservice --csUri https://example.com

Installing OS updates and other products after installation

The following table outlines the installation tasks for operating system patches and Hitachi Ops Center updates where the installer is used.

Task	Implementation method
Apply operating system patches	Apply as needed.
Update the operating system	You can update the OS as described in Applying Linux security updates using yum.
Upgrade Hitachi Ops Center products	For an upgrade installation or overwrite installation, use the Express installer or individual installers.
Install additional Hitachi Ops Center products	Confirm the system requirements of the products, install prerequisite packages, and reconfigure kernel parameters as necessary. For details on the product system requirements, see the documentation or Release Notes for each product.