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

Ops Center Installation and Configuration Guide
Version
11.0.x
Audience
anonymous
Part Number
MK-99OPS001-23

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

  • 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 One B20 or VSP family, you must enable access from a guest OS to the command device. For details, see the documentation for your virtual system.
      Note: If you do not want to collect performance information using a command device, skip these settings.

      Use a VMware vSphere Client 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.
  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.

    Tip: For best results, select 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
    • Network 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.
Run the setup tool on the guest OS, and then specify the guest OS initial settings.
Note: When 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.
Tip: The 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