Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Installation by using the virtual appliances

Install Hitachi Ops Center Analyzer using a virtual appliance by preparing your environment, installing all components, and performing initial setup.

To install the Analyzer server, the Analyzer detail view server, and the Analyzer probe server using the stand-alone OVA installers, first verify the system requirements and then deploy the software.

You can also install the Analyzer server and Analyzer detail view server using the consolidated Ops Center virtual appliance. For details, see the Hitachi Ops Center Installation and Configuration Guide.

https://knowledge.hitachivantara.com/Documents/Management_Software/Ops_Center

Workflow for installing and using a virtual appliance

The following figure shows the workflow for creating an Ops Center Analyzer system by using a virtual appliance.

If you use the Ops Center consolidated OVA, Ops Center Analyzer is automatically registered in Common Services on the same host. However, in the following cases, you must manually register Ops Center Analyzer in Common Services after the installation:

  • When you use Common Services on a different host
  • When you install Analyzer using a stand-alone OVA
The workflow diagram to configure an Ops Center Analyzer system using virtual appliances         is shown. First, confirm the system requirements and configure the Analyzer server and the         Analyzer detail view server. Next, configure the Analyzer probe server, and then configure         any options.

Installing Ops Center Analyzer and Analyzer detail view servers (VMware vSphere Client)

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

Before you begin

Review the requirements for the Analyzer server and the Analyzer detail view server (hardware and software).

Procedure

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

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

  3. To avoid IP address conflicts when the virtual machine starts, you must 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 are set by default for the virtual machine:

    • IP address: 172.30.197.99
    • 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, perform the following steps:

    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 set the following:

  • Network settings

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

    • Time zone
    • NTP server

During initial setup, firewall settings for the service port are configured in addition to the network and time settings for the guest OS, and SSL settings. If you want to use Common Services, you must manually register Analyzer in Common Services.

Note
  • You can run the setup tool only once. Afterwards, you must change the settings manually.
  • The setup tool only supports IPv4 addresses.
  • Specify the time zone in the area/location format. If you do not know the proper 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 using the following user ID and temporary password:

    User ID: root

    Password: manager

    After logging in, you must change the root password.

  2. Run the setup tool: opsvmsetup.

    Note

    This setup tool is stored in /opt/OpsVM/vmtool but you can run the tool from any location.

  3. Specify the values as prompted.

    When you are finished, a list of the settings is displayed.
  4. Check the settings, enter y, and then apply 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, 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.

Default settings for the guest operating system

When you deploy the OVA file (Analyzer OVA), the necessary settings for the Analyzer server and the Analyzer detail view server are specified for the virtual machine and guest OS.

The following table lists the defaults for the guest operating system. To change the settings for the Analyzer server and the Analyzer detail view server after deployment, change the operating system settings as needed.

Item

Settings

Operating system version

Oracle Linux

For details about the latest operating system version, see Requirements for the Analyzer OVA.

Installed libraries

Prerequisite libraries required for the Analyzer server and the Analyzer detail view server included in the Analyzer OVA.

Kernel parameters

Values required for the Analyzer server and the Analyzer detail view server included in the Analyzer 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.

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.