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

2.1.1 Before installing and setting up PFM - Agent for Platform

Before installing and setting up PFM - Agent for Platform, make sure that the requirements described below are satisfied.

Organization of this subsection

(1) Required OS

(2) Network environment setup

(3) OS user permission necessary for installation

(4) Prerequisite programs

(5) Environment configuration required for collecting performance data

(6) Notes

(1) Required OS

PFM - Agent for Platform can run on the following OSs:

• HP-UX
• Solaris
• AIX
• Linux (x86), Linux (x64),
• Linux (IPF)

(2) Network environment setup

The following explains the network environment that is necessary for Performance Management to operate.

(a) IP address setup

For the PFM - Agent host, you must set up an environment in which the IP address can be resolved using a host name. PFM - Agent cannot start in an environment in which the IP address cannot be resolved.

Actual host names or alias names can be used for a monitoring host name (the name used as the host name of a Performance Management system).

• When using an actual host name as a monitoring host name
  Execute the hostname command on a Windows system or uname -n command on a UNIX system to check the host name, and set up the environment so that it can resolve IP addresses. Note that on a UNIX system, the host name obtained by the hostname command can also be used.
  
• When using an alias name as a monitoring host name
  Set up the environment so that it can resolve the IP addresses for the set alias name.
  

For details about monitoring host name settings, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

Use one of the following methods to set up the host name and IP address:

• The host information settings file for Performance Management (jpchosts file)
• hosts file
• DNS (Domain Name System)
  

  Note

  • Performance Management can be run on a DNS environment, but does not support host names in the FQDN (Fully Qualified Domain Name) format. Accordingly, leave out the domain name when setting monitoring host names.
  • If PFM - Agent for Platform is to be used in multiple LAN environments, set up the IP address in the jpchosts file. For details, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.
  • Performance Management cannot be run on a host on which DHCP is used to assign dynamic IP addresses. Set fixed IP addresses on all hosts on which Performance Management is installed.

(b) Port number setup

The default port numbers shown in the table below are assigned to Performance Management program services. For any other services or programs, port numbers currently not in use in the system are automatically assigned when the service or program is started. When you are using Performance Management in an environment with a firewall, assign fixed port numbers. For details about how to fix port numbers, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

Table 2-1 Default port numbers and Performance Management program services (for UNIX)

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 in 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 communicating between a map manager and an object manager. This port number is set for hosts in 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 in which PFM - Manager and PFM - Base are installed.

Set up the network to enable these PFM - Agents to communicate using the assigned port numbers.

(3) OS user permission necessary for installation

When installing PFM - Agent for Platform, you must execute the installation procedure from an account that has the superuser permission.

(4) Prerequisite programs

This subsection explains the prerequisite programs that are necessary for installing PFM - Agent for Platform. The figure below shows the program configuration.

Figure 2-1 Program configuration diagram

(a) Monitoring target programs

PFM - Agent for Platform monitors the following programs:

• HP-UX
• Solaris
• AIX
• Linux (x86), Linux (x64)
• Linux (IPF)

These monitoring target programs and PFM - Agent for Platform must be installed on the same host.

(b) Performance Management programs

Install PFM - Agent and PFM - Base on the monitoring agent. PFM - Base is a prerequisite program for PFM - Agent. Even when installing multiple copies of PFM - Agent on the same host, you need only a single copy of PFM - Base.

However, if you are installing PFM - Manager and PFM - Agent on the same host, you do not need PFM - Base.

To use PFM - Agent for Platform to monitor operation of a UNIX server, you must also have PFM - Manager and PFM - Web Console.

(5) Environment configuration required for collecting performance data

The following describes the environment configuration required for collecting performance data.

(a) For collecting performance data in AIX

To collect performance data for the PI record in AIX 5L V5.3, you need to install the following optional packages:

• Performance Statistics Library (patch ID: bos.perf.libperfstat 5.3.0.0)^#
• Performance Statistics (patch ID: bos.perf.perfstat 5.3.0.0)^#

#: File set name. This package is installed by default when AIX is installed.

Note that you do not need to install an optional package when collecting performance data for records other than the PI record in AIX 5L V5.3 or collecting performance data in AIX V6.

(b) For collecting performance data in Linux

To collect performance data in Linux, you need to install the following RPM (Red Hat Package Manager) packages. Use the following command to check the installed RPM package:

/bin/rpm -qa

The following lists the RPM packages required for the performance data to be collected.

Table 2-2 RPM packages that must be installed in a Linux system

Record name	RPM package name		Default
	In Linux#	In Linux (IPF)#
CPU - Per Processor Detail (PI_CPUP)	kernel-smp-2.6.9-5.EL	N/A	Yes
Device Detail (PI_DEVD) Device Summary (PI_DEVS)	MAKEDEV-3.15-2	MAKEDEV-3.15-2	Yes
File System Detail - Local (PD_FSL) File System Detail - Remote (PD_FSR)	filesystem-2.3.0-1	filesystem-2.3.0-1	Yes
Network Interface Detail (PI_NIND) Network Interface Summary (PI_NINS)	net-tools-1.60-37	net-tools-1.60-37	Yes
System Summary Overview (PI)	net-snmp-5.1.2-11	net-snmp-5.1.2-11	Yes
User File System Storage (PD_UFSS)	N/A	N/A	Yes

Legend:

Yes: Installed by default when Linux is installed.

N/A: Not applicable

#

RPM packages need not be installed in Linux 5.1 or later.

(6) Notes

Note the following points when installing and setting up Performance Management.

(a) Precautions regarding environment variables

Because Performance Management uses JPC_HOSTNAME as an environment variable, do not set it as a user-specific environment variable, as this will prevent Performance Management from operating properly.

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

With Performance Management, you can install PFM - Manager, PFM - Web Console, and PFM - Agent on the same host. When doing so, note the following points:

• If you are installing PFM - Manager and PFM - Agent on the same host, you do not need PFM - Base. In this case, because the prerequisite program for PFM - Agent is PFM - Manager, install PFM - Manager first and then install PFM - Agent.
• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on the host on which PFM - Base and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. To install PFM - Base on the host on which PFM - Manager and PFM - Agent are 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 on which PFM - Manager is installed, PFM - Manager of the local host becomes PFM - Manager for the connection destination. In this case, you cannot change PFM - Manager for the connection destination to PFM - Manager of a remote host. To connect to PFM - Manager of a remote host, make sure that PFM - Manager is not installed on the host on which you want to install PFM - Agent.
• When you install PFM - Manager on a host on which PFM - Agent is installed, PFM - Manager for the connection destination of PFM - Agent is reset to the local host name. Check the setting results that are output to the common message log.
• To install PFM - Agent on a host on which PFM - Web Console is installed, close all browser windows before installing PFM - Agent.
• When a Performance Management program is newly installed, the status management function is enabled as the default. However, if you upgrade from version 07-00 to 08-00 or newer, the settings for the status management function remain the same as they were in the older version. For details about how to change the settings for the status management function, see the chapter explaining error detection in Performance Management in the manual Job Management Partner 1/Performance Management User's Guide.
  

  Hint

  To improve system performance and reliability, we recommend running PFM - Manager, PFM - Web Console, and PFM - Agent on separate hosts.

(c) Notes on version upgrade

Note the following points when upgrading PFM - Agent from an older version to a newer one:

For details about upgrading, see the appendix in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

• Before installing a Performance Management program, stop all Performance Management programs and services of the local host. For details about how to stop services, see the chapter explaining how to start and stop Performance Management in the manual Job Management Partner 1/Performance Management User's Guide.
• You cannot install PFM - Base and PFM - Manager on the same host. To install PFM - Manager on the host on which PFM - Base and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Manager, followed by PFM - Agent. To install PFM - Base on the host on which PFM - Manager and PFM - Agent are installed, first uninstall all Performance Management programs except PFM - Web Console, and then install PFM - Base, followed by PFM - Agent.
• In Performance Management programs of version 08-00 or later, the locations of the Store execution programs (jpcsto and stpqlpr) have been changed. When PFM - Agent is upgraded to version 08-00 or later, the Store execution modules in the previous locations are deleted.
• During upgrade installation, because the existing Store database is automatically upgraded, twice as much disk capacity as that needed for the Store database is temporarily required. Before performing an upgrade installation, make sure that the disk on which the Store database is stored has sufficient free space.

(d) Other notes

• When installing a Performance Management program, check whether any of the following security-related programs are installed. If they are installed, perform the measures explained.
  
  • Security monitoring programs
    Stop or change the settings for security monitoring programs so that installation of the Performance Management program is not prevented.
    
  • Virus detection programs
    We recommend that any virus detection programs be stopped before the Performance Management program is installed.
    If a virus detection program is running during installation of the Performance Management program, the installation speed may suffer, and installation might not be executed, or might not be performed correctly.
    
  • Process monitoring programs
    Stop or change the settings for any process monitoring programs, so that monitoring is not performed for Performance Management services or processes, and Common Component services or processes.
    If a process monitoring program starts or stops these services or processes during installation of the Performance Management program, installation might fail.
    
• If you install a new Performance Management program in an environment in which no Performance Management program is installed, make sure that there is no file or directory in the installation directory.
• If Installation failed appears in the status bar during installation and installation fails, obtain the installation log and store it in a file. You need to back up the log file as needed because this log file is overwritten the next time you install a program. For details about the default file name for the installation log, see 8.4.1(2) Performance Management information.
• When you install Performance Management programs by setting a link to the installation directory, some files and directories might remain in the linked directory even if you uninstall all of the Performance Management programs. Also, you must be careful when you install Performance Management programs in the linked directory, as files or directories having the same name in the linked directory are overwritten.
• When the PFM - Agent for Platform setup file exists in the /opt/jp1pc/setup directory, additional setup of a new PFM - Agent for Platform is executed. When additional setup of the new PFM - Agent for Platform is successful, the execution result message KAVE05908-I New agent setup ended successfully. is output to the common message log. Check the log.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.