2.1.1 Preparation for installation and setup

(a) Setting IP addresses

For the PFM - RM for Virtual Machine host, set up an environment in which an IP address can be resolved using a host name. PFM - RM for Virtual Machine cannot start in an environment in which an IP address cannot be resolved.

For the monitoring host name (the name used as the host name of a Performance Management system), you can use either a real host name or an alias name.

• When a real host name is used for the monitoring host name

  Set up the environment such that the host name that can be confirmed using the execution result of the hostname command can be used to resolve the IP address.

• When an alias name is used for the monitoring host name

  Set up the environment such that the alias name that has been set can be used to resolve the IP address.

For details about how to set up a monitoring host name, see the chapter that explains installation and setup in the JP1/Performance Management Planning and Configuration Guide.

Use one of the following to set a host name and an IP address:

• The host information setting file (jpchosts file) of Performance Management

• The hosts file

• DNS

Note that IP addresses set in the jpchosts file are not used to resolve the IP address of a monitoring-target host.

Important

• Performance Management can operate in a DNS environment, but it does not support host names in FQDN format. Therefore, specify a monitoring host name without a domain name.

• Performance Management cannot operate on a host to which a dynamic IP address is assigned by DHCP. Therefore, set fixed IP addresses for all hosts on which Performance Management will be installed.

• If Performance Management is being used in multiple LAN environments, set IP addresses in the jpchosts file. For details, see the chapter that explains installation and setup in the JP1/Performance Management Planning and Configuration Guide.

  When the virtual environment to be monitored is provided by VMware, Hyper-V, KVM, Docker environment, or Podman environment, set up the virtual environment so that an IP address can be resolved using the host name.

• When the virtual environment to be monitored is one with logical partitioning feature, its host name is not used for management, and therefore, it does not have to be resolved to an IP address. Specify the IP address that is set when the environment with logical partitioning feature is configured at the time of instance generation during setup. However, if you want to use the host name for management, you can use HVM ID, which was defined during the configuration of the environment with logical partitioning feature, as a host name. In this case, configure your system so that HVM ID can be resolved to the IP address. HVM ID must also be unique in the system. Set HVM ID and the IP address by using either of the following methods:

  - hosts file

  - DNS

To learn how to change the network configuration or rename host names in a Performance Management system, see the chapter on changing the Performance Management system configuration in the JP1/Performance Management Planning and Configuration Guide.

(b) Settings for using IPv6

Because Performance Management supports network configurations for IPv4 environments and IPv6 environments, you can use Performance Management in a network configuration that contains both IPv4 and IPv6 environments.

PFM - RM for Virtual Machine can communicate with PFM - Manager by using IPv6.

Note, however, that this applies only when Windows or Linux runs on a host with PFM - Manager installed.

PFM - RM for Virtual Machine can communicate with monitored VMware, Hyper-V, KVM, Docker environment and Podman environment with IPv6. In addition, communication with Logical partitioning feature to be monitored uses IPv4, it can not be monitored in IPv6 only environment.

For details about the scope of communication in IPv4 and IPv6 environments, see K. About Communication in IPv4 Environments and IPv6 Environments.

To use IPv6 for communication, IPv6 must be enabled on both the PFM - Manager host and the PFM - RM host by using the jpcconf ipv6 enable command.

In addition, before installing PFM - RM for Virtual Machine, you need to enable the use of IPv6 on the PFM - RM for Virtual Machine host. You have to execute the jpcconf ipv6 enable command to enable this setting. If this setting is already enabled, however, you do not need to execute the command. If you want to check whether the use of IPv6 is enabled, execute the jpcconf ipv6 display command.

For details about the jpcconf ipv6 enable command and the jpcconf ipv6 display command, see the chapter that describes commands in the manual JP1/Performance Management Reference. For details about the conditions or occasions for executing the jpcconf ipv6 enable command, see the chapter that describes network configuration examples in an environment that includes IPv6 in the JP1/Performance Management Planning and Configuration Guide.

When you use IPv6 for communication between a monitored host and PFM - RM for Virtual Machine, specify the name of a monitored host where name resolution can be performed.

Communication between PFM - RM for Virtual Machine and a monitoring target is performed with an IP address that can be resolved. Also, if an IPv4 environment and an IPv6 environment are both used, and communication between PFM - RM for Virtual Machine and the monitoring target fails with an IP address that can be resolved, the communication is not retried by using another IP address.

For example, if communication fails when IPv4 is used, IPv6 is not used to retry communication. Similarly, if communication fails when IPv6 is used, IPv4 is not used to retry communication. Make sure beforehand that a connection can be established.

(c) Setting port numbers

The services of Performance Management programs are assigned to the default port numbers shown in the table below. Port numbers that are not being used in the system are automatically assigned to all other services or programs every time a service is started. If you are using Performance Management in a firewall environment, assign fixed port numbers. For details about how to assign fixed port numbers, see the chapter that explains installation and setup in the JP1/Performance Management Planning and Configuration Guide.

Table 2‒1: Default port numbers and Performance Management program services

Service explanation	Service name	Parameter	Port number	Remarks
Service configuration information management function	Name Server	jp1pcnsvr	22285	Port number used by the Name Server service of PFM - Manager. This port number is set for all hosts of Performance Management.
Service status management function	Status Server	jp1pcstatsvr	22350	Port number used by the Status Server service of PFM - Manager and PFM - Base. This port number is set for hosts on which PFM - Manager and PFM - Base are installed.
Monitoring console communication facility	View Server	jp1pcvsvr	22286	The port number used by the View Server service of PFM - Manager. This port is set up on the hosts on which PFM - Manager is installed.
Web service facility	Web Service	--	20358	The port number used by the Web Service service of PFM - Web Console.
Web container facility	Web Console	--	20359 20360	The port number used by the Web Console service of PFM - Web Console.
JP1/SLM linkage facility	JP1/ITSLM	--	20905	The port number set by JP1/SLM.

Legend:

--: None

Configure the network in such a way that these port numbers used by PFM - RM for Virtual Machine can be used for communications.

(d) SSL/TLS utilization setup

PFM - RM for Virtual Machine acquires the performance data of a virtual environment through a network. If the virtual environment to be monitored is VMware and Docker environment, SSL/TLS must be enabled on the RM host and the monitoring target because communication between PFM - RM for Virtual Machine and the virtual environment is encrypted by SSL/TLS.

When the virtual environment to be monitored is one with VMware, see 2.5.1 For VMware.

When the virtual environment to be monitored is one with Docker environment, see 2.5.4 For Docker environment.

(a) Performance Management programs

Before you can install PFM - RM for Virtual Machine on a host, PFM - Manager or PFM - Base must be installed on that host as a prerequisite program for Performance Management.

If you want to install PFM - RM for Virtual Machine on a host on which PFM - Manager is installed, you do not need to install PFM - Base. If you want to install multiple PFM - RM instances on a host on which PFM - Base is installed, only one instance of PFM - Base is required.

In addition, PFM - Web Console is required to monitor the operating status of monitoring targets by using PFM - RM for Virtual Machine.

(b) Virtual environments supported as the monitoring target

The following virtual environments are supported as the monitoring target.

For details about virtual environments that can be monitored, see the Release Notes.

For VMware:

• VMware vSphere ESXi 5

• VMware vSphere ESXi 6

For Hyper-V:

• 2012 Hyper-V

• 2012 R2 Hyper-V

• 2016 Hyper-V

• 2019 Hyper-V

For KVM:

• KVM (Red Hat Enterprise Linux 6 (64-bit x86_64))

• KVM (Red Hat Enterprise Linux(R) Server 7)

• KVM (Red Hat Enterprise Linux(R) Server 8)

For Docker environment

• Red Hat Enterprise Linux(R) Server 7

• Windows Server 2016

• Windows Server 2019

For Podman environment

• Red Hat Enterprise Linux(R) Server 8

For logical partitioning feature:

• Hitachi Compute Blade 320

• Hitachi Compute Blade 500

• Hitachi Compute Blade 2000

• Hitachi Compute Blade 2500

  Important

  Logical partitioning feature supports only IPv4 networks.

(c) Hardware running logical partitioning feature that is supported as the monitoring target

PFM - RM for Virtual Machine can monitor the following sets of hardware running logical partitioning feature:

For details about hardware running logical partitioning feature that can be monitored, see the Release Notes.

• Hitachi Compute Blade 320

• Hitachi Compute Blade 500

• Hitachi Compute Blade 2000

• Hitachi Compute Blade 2500

(d) LPAR Manager management command for logical partitioning feature

For the HvmSh command that is necessary for PFM - RM for Virtual Machine to collect information about logical partitioning feature, use the LPAR Manager management command from the management tool for logical partitioning feature provided with the feature.

If you have more than one version of the HvmSh command, use the latest version.

For details about the HvmSh command for hardware running logical partitioning feature, see the Release Notes.

Important

The user authentication function of the HvmSh command is non-support.

(a) Note on the registry

Operation of PFM - RM for Virtual Machine is supported only in an OS environment with standard settings. Performance data might not be collected correctly if special OS settings are specified in some way, such as using the registry editor to edit the registry directly. This is also true if the special settings have been published in the Microsoft Knowledge Base.

(b) Note on the environment variable

Performance Management uses JPC_HOSTNAME as the environment variable; therefore, the user must not specify it as an environment variable. If it is specified as an environment variable, Performance Management will not operate correctly.

(c) Notes on installing and setting up multiple Performance Management programs on the same host

You can install multiple Performance Management programs; that is, PFM - Manager, PFM - Web Console, and PFM - RM for Virtual Machine, on the same host. When you do so, note the following.

• To maximize system performance and reliability, we recommend that you run PFM - Manager, PFM - Web Console, and PFM - RM for Virtual Machine on separate hosts.

• If you install PFM - Manager and PFM - RM for Virtual Machine on the same host, you do not need PFM - Base. In this case, since the prerequisite program for PFM - RM for Virtual Machine is PFM - Manager, first install PFM - Manager and then install PFM - RM for Virtual Machine.

• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on a host that has PFM - Base and PFM - RM for Virtual Machine installed, you must first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - RM for Virtual Machine. Likewise, to install PFM - Base on a host that has PFM - Manager and PFM - RM for Virtual Machine installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - RM for Virtual Machine.

• When you install PFM - RM for Virtual Machine on a host that has PFM - Manager installed, the PFM - Manager of the local host becomes the PFM - Manager at the connection destination. In this case, you cannot change the PFM - Manager at the connection destination to the PFM - Manager of a remote host. To connect to the PFM - Manager of a remote host, make sure that the host on which you intend to install PFM - RM for Virtual Machine does not have PFM - Manager installed.

• When you install PFM - Manager on a host that has PFM - RM for Virtual Machine installed, the PFM - Manager at the connection destination of PFM - RM for Virtual Machine is reset to the local host name. Check the setting result that is output to the common message log.

• To install PFM - RM for Virtual Machine on a host that has PFM - Web Console installed, close all browser windows before you perform installation.

• When you perform a new installation of a Performance Management program, the status management function is enabled by default. However, when you perform an upgrade installation from a version earlier than 08-00 to version 08-00 or a later version, the status management function settings remain as they were in the earlier version. For details about how to change the settings for the status management function, see the chapter that explains Performance Management error detection in the JP1/Performance Management User's Guide.

(d) Notes on version upgrading

For details about notes on upgrading the versions of Performance Management programs, see the section describing the notes on version upgrading in the chapter that explains installation and setup in the JP1/Performance Management Planning and Configuration Guide.

Observe the following precautions when upgrading the version of PFM - RM for Virtual Machine:

• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on a host that has PFM - Base and PFM - RM for Virtual Machine installed, you must first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - RM for Virtual Machine. Likewise, to install PFM - Base on a host that has PFM - Manager and PFM - RM for Virtual Machine installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - RM for Virtual Machine.

(e) Other notes

• Before you perform new installation of Performance Management programs in an environment that does not yet have any of these programs installed, make sure that the target folder does not contain any files or folders.

• If you install a Performance Management program while another program (e.g., Windows Event Viewer) that references a Performance Management program, service, or file is running, a message asking the user to restart the system may be displayed. In this case, restart the system as instructed by the message, and then complete the installation process.

• If you install a Performance Management program while another program (e.g., Windows Event Viewer) that references a Performance Management program, service, or file is running, file expansion may fail if there is a disk space shortage, or if you do not have the proper folder permissions. If other programs are running that reference a Performance Management program, service, or file, stop them all, and then reinstall the Performance Management program. If there is a disk space shortage, or if you do not have the proper folder permissions, solve these problems first, and then reinstall the Performance Management program.

• Before you install a Performance Management program, check whether any of the security-related programs are installed. If one is installed, take the necessary steps explained below.

  • For a security-monitoring program

    Either stop the security-monitoring program or change its settings so that it will not prevent installation of Performance Management programs.

  • For a virus-detection program

    We recommend that you first stop the virus-detection program and then install Performance Management programs.

    If a virus-detection program is running while you are trying to install a Performance Management program, it may slow down or prevent installation, or it may result in an incorrect installation.

  • For a process-monitoring program

    Either stop the process-monitoring program or change its settings so that it will not monitor any Performance Management service or process, or any service or process of a shared component.

    If a process-monitoring program starts or stops these programs or services during the installation of a Performance Management program, the installation process may fail.

• You can install PFM - RM for Virtual Machine on one of the virtual machines in a virtual environment, and monitor the virtual environment with the virtual machine installed PFM - RM for Virtual Machine. However, in this operating mode, PFM - RM for Virtual Machine will stop if the virtual environment stops. Therefore, we recommend that you install PFM - RM for Virtual Machine in an environment that is different from the monitored virtual environment.

• Precautions when installing this product as an overwrite installation.

  • An overwrite installation of PFM - RM for Virtual Machine may require a restart.

  • If you open the files of this product or display the Event Viewer, close the files or the dialog to release before installation.

• Before you install this product, make sure you stop any Performance Management programs or services that are running, by using the jpcspm stop command. You must also stop any Performance Management services that are running on any logical host that has been set up.

• Attempting to extract the file necessary for installation sometimes fails, depending on the system conditions. If installation fails, please try again. If the problem persists, acquire the following files in the %WINDOWS%\TEMP\HCDINST folder, and contact the system administrator.

  • HCDMAIN.LOG or HCDMAIN#.LOG (# is a numeric character.)

  • HCDINST.LOG or HCDINST#.LOG (# is a numeric character.)

  • P-CC2A2C-5VCL.LOG

• When you upgrade the OS to Windows Server 2012 or later version from Windows Server 2003 or earlier version, uninstall all Performance Management products before upgrading.

• You must restart your computer when prompted to do so at completion of an installation.

• This software is a Hitachi program product that conforms to the disk copy installation of JP1/ServerConductor/Deployment Manager and Hitachi Compute Systems Manager Deployment Manager Plug-in, or the copy functionality using conversion to image files that is provided by a virtual platform. About the disk copy installation, see notes on installing replicated disks in the manual JP1/Performance Management Planning and Configuration Guide.

(a) Setting method in Windows

• Output settings for user-mode process dump

  By entering the following registry, you can instantly collect user-mode process dump for investigation purposes if an application program terminates abnormally:

  \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

  Specify the following registry values in the registry key:

  • DumpFolder : REG_EXPAND_SZ <dump-output-destination-folder-name>

    (You must have permissions to write data to the output destination folder.)

  • DumpCount : REG_DWORD <number-of-dumps-to-be-saved>

  • DumpType : REG_DWORD 2

    Important

    • Setting up this registry entry enables you to output user-mode process dumps in JP1 as well as other application programs. Be aware of this point when deciding to output user-mode process dump.

    • When a user-mode process dump is output, it uses disk space. Therefore, when you decide to output user-mode process dump, make sure that sufficient disk space is allocated to the specified dump output destination folder.