Job Management Partner 1/Performance Management - Agent Option for Virtual Machine Description, User's Guide and Reference

2.1.1 Before installation and setup

This subsection explains the items you must check before you install and set up PFM - Agent for Virtual Machine.

Organization of this subsection

(1) Prerequisite OS

(2) Setting up the network environment

(3) OS user permissions necessary for installation

(4) Prerequisite programs

(5) Tools that must be started on the virtual environment side when VMware is monitored

(6) Installation and setup in a cluster system

(7) Notes

(1) Prerequisite OS

PFM - Agent for Virtual Machine runs under the following OS:

Windows Server 2003

Windows Server 2008

(2) Setting up the network environment

The following explains the network environment necessary to run Performance Management.

(a) Setting IP addresses

For the PFM - Agent host, set up an environment in which an IP address can be resolved using a host name. PFM - Agent 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 (Domain Name System)

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.

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

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

(c) SSL utilization setup

PFM - Agent 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 - Agent 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 - Agent for Virtual Machine you need to specify whether to use SSL, in accordance with the virtual environment configuration. You specify SSL usage when you set up the instance environment. For details, see 2.1.4(2) Setting up an instance environment.

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.

(3) OS user permissions necessary for installation

When you install PFM - Agent for Virtual Machine, you must perform the installation from an account that has Administrator permissions.

(4) Prerequisite programs

This subsection explains the programs required for installing PFM - Agent for Virtual Machine. The following figure shows the program configuration diagram.

Figure 2-1 Program configuration diagram

(a) Performance Management programs

The table below shows the required Performance Management programs.

Table 2-2 Required Performance Management programs

Target host Required Performance Management programs Prerequisite version

Monitoring manager PFM - Manager^#1 08-00 or later

Monitoring agent (for Windows Server 2003) PFM - Agent for Virtual Machine 09-01

PFM - Manager^#2 09-00 or later

PFM - Base^{#1, #3} 09-00 or later

Monitoring agent (for Windows Server 2008) PFM - Agent for Virtual Machine 09-01

PFM - Manager^#2 09-00 or later

PFM - Base^{#1, #3} 09-00 or later

Monitoring console server PFM - Web Console^#4 08-00 or later

PFM - View^#4 07-00 or later

#1

This program is required when the monitoring manager host and the monitoring agent host are configured on different hosts.

#2

This program is required when the monitoring manager host and the monitoring agent host are configured on the same host.

#3

Even when multiple PFM - Agents are installed on the same host, only one PFM - Base is required.

#4

Install either of these programs.

(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 ESX V4.1

VMware ESXi V4.1 Embedded

VMware ESXi V4.1 Installable

For Hyper-V:

Hyper-V 1.0

Hyper-V 2.0

Target host	Required Performance Management programs	Prerequisite version
Monitoring manager	PFM - Manager^#1	08-00 or later
Monitoring agent (for Windows Server 2003)	PFM - Agent for Virtual Machine	09-01
PFM - Manager^#2	09-00 or later
PFM - Base^{#1, #3}	09-00 or later
Monitoring agent (for Windows Server 2008)	PFM - Agent for Virtual Machine	09-01
PFM - Manager^#2	09-00 or later
PFM - Base^{#1, #3}	09-00 or later
Monitoring console server	PFM - Web Console^#4	08-00 or later
PFM - View^#4	07-00 or later

(5) Tools that must be started on the virtual environment side when VMware is monitored

Before you monitor the information of a virtual machine running on VMware, start VMware Tools on the virtual machine you intend to monitor.

When the OS of the monitored virtual machine is Windows
During installation of VMware Tools, a dialog box for selecting program functions opens. In this dialog box, leave all default settings intact when you install VMware Tools. The following items are selected as the default settings:

SCSI driver

SVGA driver

Mouse driver

VMXNET NIC driver

Memory control driver

FileSystem Sync Driver

VMWCI-Driver

When the OS of the monitored virtual machine is Linux
During installation of VMware Tools, a dialog box for selecting program functions is not displayed. Follow the normal installation procedure.

When the OS of the monitored virtual machine is neither Windows nor Linux
For instructions on how to install VMware Tools, contact VMware Corporation.

(6) Installation and setup in a cluster system

When you install and set up PFM - Agent for Virtual Machine in a cluster system, the prerequisite network environment and program configurations are different from those used to set up a normal configuration. Tasks at the executing node and standby node are also required. For details, see 3. Operations in a Cluster System.

(7) Notes

This subsection provides notes related to the installation and setup of Performance Management.

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

(b) 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 - Agent, 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 - Agent on separate hosts.

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

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 - Agent installed, you must first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. Likewise, to install PFM - Base on a host that has PFM - Manager and PFM - Agent installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - Agent.

When you install PFM - Agent 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 - Agent does not have PFM - Manager installed.

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

To install PFM - Agent 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.

(c) Notes on version upgrading

Note the following when you upgrade from an earlier version of PFM - Agent 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 - Agent on a host that has Performance Management programs installed, the installation path for PFM - Agent 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 - Agent installed, you must first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. Likewise, to install PFM - Base on a host that has PFM - Manager and PFM - Agent installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - Agent.

When you install an upgraded version, the existing Store database is automatically upgraded, and as a result the disk space it occupies temporarily doubles. Therefore, before you install an upgraded version, make sure that the disk that stores the Store database has sufficient free space.

In the case of PFM - Agent for Virtual Machine 09-01, the following items have been added to the instance information:
Domain
HostUserID
HostUserPassword
HostDomain
These items are not set when you upgrade PFM - Agent for Virtual Machine from 09-00 to 09-01 or later. In this case, you must set HostUserID, HostUserPassword, and HostDomain for each instance. For details about the setting method for each monitoring target, see 2.6.1 For VMware or 2.6.2 For Hyper-V. When you monitor VMware, there is no need to set Domain.

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

You can install PFM - Agent 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 - Agent for Virtual Machine will stop if the virtual environment stops. Therefore, we recommend that you install PFM - Agent for Virtual Machine in an environment that is different from the monitored virtual environment.

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.

[Contents][Back][Next]

[Trademarks]