2.1.1 Before 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 Job Management Partner 1/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 note

• 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 Job Management Partner 1/Performance Management Planning and Configuration Guide.

• Set up the virtual environment so that IP addresses can be resolved when host names are used.

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 Job Management Partner 1/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 Server 2008 R2 or Windows Server 2012 runs on a host with PFM - RM for Virtual Machine installed and Windows Server 2008 R2, Windows Server 2012 or Linux runs on a host with PFM - Manager installed.

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. The following describes when you need to execute this command.

Cases when the jpcconf ipv6 enable command needs to be executed:

• When switching from an IPv4 environment to an IPv6 environment on each host

• When switching the PFM - Manager environment from IPv4 to IPv6 in an environment in which both IPv4 and IPv6 are used

Cases when the jpcconf ipv6 enable command does not need to be executed:

• When each host already operates in an IPv6 environment

• When PFM - Manager operates in an IPv6 environment in an environment in which both IPv4 and IPv6 are used

The following shows an example of executing the jpcconf ipv6 enable command:

jpcconf ipv6 enable

For details about the jpcconf ipv6 enable command, see the chapter that describes commands in the manual Job Management Partner 1/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 Job Management Partner 1/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 Job Management Partner 1/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.
OpenView linkage facility	NNM Object Manager	jp1pcovsvr	22292	Port number used by the OpenView linkage facility of PFM - Manager and PFM - Base for communication between the map manager and the object manager. This port number is set for hosts on which PFM - Manager and PFM - Base are installed.
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/ITSLM linkage facility	JP1/ITSLM	--	20905	The port number set by JP1/ITSLM.

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 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, you can use SSL to encrypt communications between PFM - RM for Virtual Machine and the virtual environment.

The virtual environment side specifies whether to enable communications that use SSL. For details about setup, see the documentation for the virtual environment software.

Additionally, during setup of PFM - RM for Virtual Machine you need to specify whether to use SSL, in accordance with the virtual environment configuration. The settings for enabling SSL communication are specified during instance environment setup and monitoring target setup. For details, see 2.1.4(3) Setting up an instance environment and 2.1.4(4) Setting up monitoring targets.

(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 VMware:

• VMware ESX V3.0

• VMware ESX V3.5

• VMware ESXi V3.5 Embedded

• VMware ESXi V3.5 Installable

• VMware ESX V4.0

• VMware ESXi V4.0 Embedded

• VMware ESXi V4.0 Installable

• VMware ESXi V4.1 Embedded

• VMware ESXi V4.1 Installable

• VMware vSphere ESXi V5.0

• VMware vSphere ESXi V5.1

• VMware vSphere ESXi V5.5

For Hyper-V:

• 2008 Hyper-V

• 2008 R2 Hyper-V

• 2012 Hyper-V

• 2012 R2 Hyper-V

For KVM:

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

(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.

Tip:

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 Job Management Partner 1/Performance Management User's Guide.

(d) Notes on version upgrading

Note the following when you upgrade from an earlier version of PFM - RM for Virtual Machine to a later version.

For details about version upgrading, see the appendix section of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

• Before you install Performance Management programs, stop all Performance Management programs and services on local hosts. Stop all services on both physical hosts and logical hosts. For details about how to stop services, see the chapter that explains startup and termination of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

• When you install PFM - RM for Virtual Machine on a host that has Performance Management programs installed, the installation path for PFM - RM for Virtual Machine is the same as the installation path for all previously installed Performance Management programs except PFM - Web Console. To change the installation path, you must first delete all previously installed Performance Management programs except PFM - Web Console, and then reinstall them.

• 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 upgrade, if the data model version of the Store database will change, the current Store database is automatically updated with the result that twice the disk space for the Store database is temporarily required. Before upgrading, make sure that there is enough free space on the disk where the Store database is stored. Estimate the necessary free space based on the total size of the current Store database. For example, if the total size of the current Store database is 100 gigabytes, at least 200 gigabytes of free space will be required for installation. If you change the disk where the Store database is stored, take into consideration the amount of disk space that will be needed on the disk after the switch.

(e) Note on linkage with other systems

• Before you install Performance Management programs in an environment that is linked with NNM, stop the OpenView linkage facility and ovw.

(f) 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.

• After you have performed a new installation of a Performance Management program, you must restart the system to complete the installation process. When you perform overwrite installation or upgrade installation, a message asking the user to restart the system may be displayed. In this case also, restart the system as instructed by the message, and then complete the installation process.

• 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 have it monitor other virtual machines. 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.

(a) Settings in Windows Server 2003

To enable a memory dump:

1. In Control Panel, double-click System.

2. Open the Advanced page. Under Startup and Recovery, click the Settings button.

3. From the Write debugging information drop-down list, select Complete memory dump, and then, specify the output destination file.

   Important note

   The size of a memory dump differs depending on the size of actual memory. The greater the installed physical memory, the greater the memory dump size. Accordingly, make sure you have enough disk space to collect the memory dumps. For details, see the OS documentation.

To enable a crash dump:

1. From the Start menu, select Run.

2. In the text box, enter drwtsn32, and then click the OK button.

   The Dr. Watson dialog box opens.

3. Select the Create Crash Dump File check box. Then, in the Crash Dump text box, specify the output destination file.

4. Click the OK button.

   Important note

   Not only JP1 information, but also the error information for other application programs is output in crash dumps, with potential adverse effects on available disk space. If you specify that crash dumps are to be output, make sure that you have enough disk space for them.

(b) Setting method for Windows Server 2008, and Windows Server 2012

Settings for outputting user mode process dumps:

You can use the following registry setting to obtain user mode process dumps of data that you can investigate for troubleshooting when an application program terminates:

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

Specify the following registry key values:

• DumpFolder: REG_EXPAND_SZ dump-output-folder-name

  Permission to write to the output destination folder is needed.

• DumpCount: REG_DWORD Number-of-dumps-to-be-saved

• DumpType: REG_DWORD 2

  Important note

  • When you set the registry to output user mode process dumps, user mode process dumps are output for not only JP1 programs, but also for other application programs. Make sure you keep this in mind when you specify that user mode process dumps are to be output.

  • When user mode process dumps are output, available disk space can be adversely affected. Make sure that you specify a dump output folder that has enough disk space for the dumps.