Skip to main content
Hitachi Vantara Knowledge

Install Hitachi Ops Center products by using the OVA file

 

You can install Hitachi Ops Center products on a virtual machine by deploying the Hitachi Ops Center OVA file on a VMware ESXi server.

Workflow for deploying and setting up Hitachi Ops Center

 
The following figure shows the workflow for installing and setting up the Hitachi Ops Center products by using the OVA file:
Workflow showing the steps for constructing an environment for Hitachi Ops Center products. The steps are: Prepare a virtualization server. Deploy the OVA. Run the setup tool. Set up SSL communications. Register the products to Common Services. Log in to the portal. Register a license. Set up Active Directory. Set up a password policy. Finally, set up access controls.

For a complete list of Hitachi Ops Center system requirements, go to the Ops Center documentation site and select Get Started with Ops Center Hitachi Ops Center system requirements.

For details on preparing the virtualization server, see the VMware documentation.

After configuring access control, configure the settings for each product as necessary. For details on how to configure settings, see the documentation for each product.

System configuration of the Hitachi Ops Center virtual machine

 
This section describes the virtual machine system configuration that is created by using the Hitachi Ops Center OVA file.
Guest operating system

Oracle Linux is installed as the guest operating system.

Installed products

The following products, which are components of the management server, are installed:

  • Hitachi Ops Center Automator
  • Hitachi Ops Center Analyzer
  • Hitachi Ops Center Analyzer detail view
  • Hitachi Ops Center Administrator
  • Hitachi Ops Center Protector
  • Hitachi Ops Center API Configuration Manager
  • Hitachi Ops Center Common Services
Note
  • The installation directory is /opt/hitachi.
  • The installation destination for Common Services is /opt/hitachi/CommonService.
  • User data for Common Services is stored in the following user data directory:

    /var/opt/hitachi/CommonService

Hitachi Ops Center API Configuration Manager requires Command Control Interface, so it is also installed as part of the installation. The installation directory is /opt/hitachi/ConfManager/HORCM.

Note
  • For products not included in this OVA, install each product by using the separate installer or OVA provided for that product.
  • Hitachi Ops Center does not support installing other software products on the management server, but allows for installing software required by corporate policy such 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.

Default settings for the virtual machine and the guest operating system

 
The OVA deployment sets the virtual machine and operating system settings that Hitachi Ops Center requires by default.

When you deploy the OVA file, a virtual machine with the following default settings is created. Confirm whether the virtualization server has enough resources to create the virtual machine.

 

Item

Settings

CPU

16 cores

Memory

48 GiB

Disk size

900 GiB

The default settings assume that you are managing 10 storage systems. For larger-scale systems, change the settings for memory, disk size, and virtual memory, or increase the number of virtual machines.

For details on how to change the settings of virtual machines, go to the Ops Center documentation site and select Get Started with Ops Center Hitachi Ops Center system requirements.

The following table lists the items that are set by default for the guest operating system. To change the settings for Hitachi Ops Center products after the deployment, change the operating system settings as needed.

 

Item

Settings

Operating system version

Oracle Linux

For details about the latest operating system version, see the Hitachi Ops Center System Requirements.

Installed libraries

Prerequisite libraries required for the Hitachi Ops Center products included in the OVA.

Kernel parameters

Values required for the Hitachi Ops Center products included in the OVA.

Registering firewall exceptions

In addition to the ports that are registered as exceptions by the operating system, the ports that must be registered as exceptions for each of the products.

Deploying Hitachi Ops Center

 
By deploying the Hitachi Ops Center OVA file, you can create a virtual machine on which the products are installed.
  1. From a VMware vSphere client, log in to the VMware ESXi server.

  2. From the VMware vSphere client, deploy the Hitachi Ops Center OVA (OpsCenterVM_version.ova) by selecting File Deploy OVF Template, and then following the prompts.

  3. To avoid IP address conflicts when the virtual machine starts, change the settings so that the machine does not connect to the network.

    You can skip this step if you are sure that the IP addresses will not conflict.

    When deployment is complete, the following network settings are set by default for the virtual machine:

    • IP address: 172.30.197.92
    • Network mask: 255.255.0.0
    • Default gateway: 172.30.0.1
    1. Right-click the new virtual machine, and select Edit Settings.

    2. In the Hardware tab, select Network adapter 1, and then clear the Connect at power on check box.

  4. Start the virtual machine.

  5. If you changed the settings in step 3 so that the virtual machine does not connect to the network when it starts, reselect the Connect at power on check box.

    1. Right-click the virtual machine, and select Edit Settings.

    2. In the Hardware tab, select Network adapter 1, and then check the Connect at power on check box.

Running the setup tool (opsvmsetup)

 
After you complete the OVA deployment, run the setup tool (opsvmsetup) to complete the initial setup.

You can use the setup tool to specify the following settings:

  • Network settings

     

    • Host name (or FQDN)
    • IP address
    • Default gateway
    • Network mask
    • DNS server (up to two servers)
  • Time settings

     

    • Time zone
    • NTP server

When you run the initial setup, the following settings are specified: the network and time settings for the guest OS, the single sign-on settings for the selected product, the settings to enable SSL communications, and the firewall settings for service ports.

Note
  • You can run the setup tool only once. To change the settings after running the setup tool, use the operating system commands.
  • This setup tool is stored in the /opt/OpsVM/vmtool directory but you can run the tool from any directory.
  • The setup tool specifies an IPv4 address.
  • The host name (or FQDN) and 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.
  • You cannot specify uppercase characters in the host name (or FQDN). If you do, they are converted to lowercase characters and then registered.
  • Specify the time zone in the area/location format. If you do not know the required values, use the following command to check the time zone values before running the setup tool:

    timedatectl list-timezones

Procedure

  1. From the VMware vSphere client, log in to the guest operating system.

    When you log in for the first time, use the following user ID and password:

    User ID: root

    Password: manager

    After logging in, you must change the root password.

  2. Run the setup tool: opsvmsetup.

  3. Specify the values as indicated in the prompts.

    After you finish all items, a list of the settings is displayed.
  4. Check the settings, enter y, and then apply the settings.

    After applying the settings, the guest operating system restarts automatically.

  5. If you changed the settings so that the virtual machine is not connected to the network when deployed, complete the following steps to enable the network adapter:

    1. Log in to the guest operating system, and then stop the virtual machine by using the shutdown command.

    2. From the VMware vSphere client, click Power On the virtual machine.

Installing the Ops Center Analyzer separately using an OVA

 
In a large system configuration with multiple Ops Center Analyzer servers, you can use the Analyzer OVA to deploy only the Ops Center Analyzer and analyzer detail view. This enables you to use a separate server or add another instance of Ops Center Analyzer. For information on installing the Analyzer OVA, see the Ops Center Analyzer installation documentation.

Installing the Analyzer probe server and Protector Client (VMware vSphere Client)

 

By deploying the OVA file (Analyzer probe OVA), you can create a virtual machine on which the Analyzer probe server and Protector Client are installed.

Before you begin

  • Review the Analyzer probe server requirements (hardware and software).
  • Make sure that the ports you specify are available for communication. The default port is 8443. The default port for SSH is 22.
  • If you use the Analyzer probe server in a DNS environment, exclude the domain name when specifying the host name because the Analyzer probe server does not support FQDN.
  • Specify a static IP address for Analyzer probe server because the RAID Agent cannot run on hosts the use DHCP to assign IP addresses.
  • When you run RAID Agent in a virtual environment:
    • Before setting up the RAID Agent, you must specify C for the LANG environment variable on the Analyzer probe server host.

      At startup, RAID Agent is subject to the system LANG environment variable. If the LC_ALL environment variable differs from the LANG environment variable, either unset LC_ALL or change the value to match the LANG value. Use the following example as a reference when setting the LANG value for RAID Agent. The last line is an example of coding that unsets the LC_ALL value.

      • Example settings:

         

        ## Set Environment-variables
        PATH=/sbin:/bin:/usr/bin:/opt/jp1pc/bin
        SHLIB_PATH=/opt/hitachi/common/lib
        LD_LIBRARY_PATH=/opt/hitachi/common/lib
        LIBPATH=/opt/hitachi/common/lib
        HCCLIBCNF=/opt/jp1/hcclibcnf
        LANG=C
        export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF LANG
        unset LC_ALL
    • If you want to monitor VSP family or HUS VM, you must enable access from a guest OS to the command device. For details, see the documentation for your virtual system.
      NoteIf you do not want to collect performance information using a command device, skip these settings.

      Use a VMware vSphere Client file to add a device to the guest OS. By doing so, if you designate a command device as the device to add, the command device can be accessed from the guest OS.

      When configuring settings to add a device, make sure that the following requirements are met:

      • Device type: Hard disk
      • Disk selection: Raw device mapping
      • Compatibility mode: Physical
      • Virtual disks (including VMware VVols) are not used for the command device.
    • When you use a virtualization system to replicate an OS environment in which the RAID Agent is running, do not apply the replicated environment to any other host. The RAID Agent startup might fail in the replicated environment.

Procedure

  1. From a VMware vSphere client, log on to the VMware ESXi server.

  2. Deploy the Analyzer probe OVA (dcaprobe_version.ova) by selecting File Deploy OVF Template, and then following the prompts.

    From the VMware vSphere client, select File Deploy OVF Template, and then follow the on-screen instructions.

    TipWe recommend selecting Thick Provision Lazy Zeroed in the window for selecting the disk provisioning method.
  3. Change the settings so that the virtual machine does not connect to the network when started.

    This operation is not required if you are sure that the IP addresses will not conflict.

    When deployment is complete, the following default network settings are used for the virtual machine:

    • IP address172.30.197.101
    • Net mask255.255.0.0
    • Default gateway172.30.0.1
    1. Right-click the virtual machine that you want to edit, and then select Edit Settings.

    2. In the Hardware tab, select Network adapter 1, and then clear the Connect at power on check box.

  4. Start the virtual machine.

    When you log in for the first time, use the following user ID and password:

    User ID: root

    Password: manager

    After you log in, you must change the root password.

  5. Confirm that the network setting is correct.

Next steps

Run the setup tool on the guest OS, and then specify the guest OS initial settings.

NoteWhen running the Analyzer probe server, Ops Center API Configuration Manager, and Protector Client on the same VM, all components share the same command device, but Ops Center API Configuration Manager and Protector Client must access the storage systems using different credentials. This means they must use different user accounts when accessing the storage system.
TipThe Analyzer probe server and Protector Client are installed in the following directory on the virtual machine.
  • Analyzer probe server: /home
  • Protector Client: /opt/hitachi/protector

Initial setup of the guest OS or VMs

 

After deploying the virtual appliance, run the setup tool (opsvmsetup) to specify the guest OS initial settings. If you want to use Protector, specify settings for Protector.

  1. From the VMware vSphere Client, log on to the guest OS.

  2. Run the opsvmsetup command.

    Note
    • You can run the setup tool only once. To change the settings after running the setup tool, use the operating system commands.
    • This setup tool is stored in /opt/OpsVM/vmtool but you can run the tool from any location.
  3. In the setup tool, you can specify the following settings:

    • Network settings
      • Host name: The Analyzer probe server does not support FQDNs. Omit the domain name when specifying the host name.
      • DHCP: RAID Agent does not support the use of DHCP. If you are using RAID Agent, specify n.
      • IP address: The setup tool specifies an IPv4 address.
      • Default gateway
      • Network mask
      • DNS server (2 servers maximum)
    • Time settings
      • Time zone
        • Specify the time zone in the area/location format. If you do not know the specifiable values, use the following command in advance to check the available time zone values:
          timedatectl list-timezones
        • The times and time zones of the following servers must be synchronized:
          • Analyzer server
          • Analyzer detail view server
      • NTP server
    • Security setting
      • Server certificate
    • Protector settings
      • Whether to use Protector
      • Protector master host name
      • Protector master IPv4 address
  4. Check the contents of the list that displays your specified settings, and then apply the settings.

    After the settings are applied, the guest OS restarts automatically.

  5. If the virtual machine is not connected to the network when deployed, complete the following steps to enable the network adapter:

    1. Log on to the guest OS.

    2. Stop the virtual machine by running the shutdown command.

    3. Right-click the virtual machine that you want to stop, and then select Edit Settings.

    4. In the Hardware tab, select Network adapter 1, and then select the Connect at power on check box.

    5. Run the Power On the virtual machine.

Installing OS updates and other products after deployment

 
The following table outlines the installation tasks for an operating system patch or for Hitachi Ops Center products in an environment in which the OVA is deployed.

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

The OVA is for new installations only. For an upgrade installation or overwrite installation, use the individual product installers.

Upgrade of OSS

Python3, Requests, and OpenSSL incorporated in the VM image is set for the sample code of Hitachi Ops Center API Configuration Manager. If a vulnerability is found in Python3, Requests, and OpenSSL, upgrade all of them. For details, see the Hitachi Ops Center API Configuration Manager Release Notes.

Install additional Hitachi Ops Center products

To install other Hitachi Ops Center products that are not installed on a virtual machine to which the OVA is deployed, install the products by using the installation media. 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.

Upgrading after an OVA installation

 
The OVA is for new installations only. For an upgrade or overwrite installation, use the individual product installers.

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.

Registering products in Common Services

 
To use the functions provided by Common Services, you must register products in Common Services. When you deployed the Hitachi Ops Center OVA file, each product is already registered in Common Services.

In the following cases, you need to run the setupcommonservice command for the relevant products to register the products in Common Services.

  • If you want to use a product that was installed by using a method other than the Ops Center OVA, register the product in Common Services.
  • If you deployed the Ops Center OVA to multiple management servers, decide which management server to use as the Common Services host, and then reregister the products installed on the other management servers to the central Common Services instance.

Registering Ops Center products with Common Services (setupcommonservice)

 

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

Before you begin

  • 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.
  • The Ops Center product server and the Common Services server must be running.
  • You must use a Common Services account with the "Application Administrator" role to run setupcommonservice.
NoteProducts 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.

setupcommonservice 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://myopscenter.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://myopscenter.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://myopscenter.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://myopscenter.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://myopscenter.com/portal -appPort 22016 -appHostname 192.0.2.10 -appName MyAnalyzer1  
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://myopscenter.com 

Logging in to the Hitachi Ops Center Portal

 
Log in to the Hitachi Ops Center Portal from your browser.

Before you begin

To avoid issues with windows not displaying correctly, configure your browser settings as follows:

  • Accept cookies, or register the portal URL as a trusted site.
  • Enable active scripting in the security settings.

Procedure

  1. In a web browser, access the following URL:

    https://host-name-or-IP-address-of-Portal:port-number/portal/

    The default port number is 443.

    TipBy default, you can access the Hitachi Ops Center Portal by using both the host name and IP address. To change the settings so that users can only access the Portal by using the host name, or to change the host name or IP address used to access the Hitachi Ops Center Portal, use the cschgconnect command. For details about the cschgconnect command, see Changing the management server host name, IP address, or port number.
  2. Use the following built-in account to log in:

    User name: sysadmin

    Password: sysadmin

    The Hitachi Ops Center Portal main window opens.

    Note
    • For security, be sure to change the password of the built-in account.
    • If you want to log in to the Portal by using the IP address, specify the settings so that the management server host name can also be resolved from client machines.

 

  • Was this article helpful?