3.2.1 Issues to consider before installing the UNIX edition

(a) Setting IP addresses

You must set up the environment for PFM - RM for Platform in such a manner that an IP address can be determined from the host name. PFM - RM for Platform will not start in an environment in which IP addresses cannot be resolved.

You use one of the following methods to set host names and IP addresses:

• jpchosts file (Performance Management's host information configuration file)

• hosts file

• DNS

For the monitoring host name, use either the real host name or the alias name.

• Using the real host name

  In a UNIX environment, specify the name in such a manner that the IP address can be resolved from the host name that is obtained from the result of executing the uname -n command. You can also use the host name that is acquired by the hostname command.

  Note that Performance Management supports DNS, but not FQDN. This means that when you set the IP address, you must use the host name obtained by the uname -n command without the domain name.

• Using an alias name

  Set the environment in such a manner that the IP address can be resolved from the specified alias name.

For details about setting the name of the monitoring host, see the chapter that describes changing the system configuration in the JP1/Performance Management Planning and Configuration Guide.

Note that the IP address specified in the jpchosts file is not used for IP address resolution with the monitored host.

Notes about setting IP addresses

• If you use Performance Management in multiple LAN environments, use the jpchosts file to set IP addresses. For details about using the jpchosts file to set IP addresses, see the chapter that describes installation and setup in the JP1/Performance Management Planning and Configuration Guide.

• Performance Management will not run on a host where IP addresses are assigned dynamically by DHCP. You must set fixed IP addresses for all monitoring hosts.

(b) Settings for using IPv6

Performance Management supports both IPv4 and IPv6 network environments. Therefore, you can run Performance Management even in a network environment where IPv4 and IPv6 coexist.

PFM - RM for Platform can use IPv6 to communicate with PFM - Manager. However, this applies only when the OS of the host on which PFM - RM for Platform and PFM - Manager are installed is Windows or Linux. For details about the applicable scope of communication in the IPv4 and IPv6 environments, see M. Communication in IPv4 and IPv6 Environments.

To communicate using IPv6, you must enable the use of IPv6 on both the PFM - Manager host and the PFM - RM host. Before installing PFM - RM for Platform, you must also enable the use of IPv6 on the PFM - RM host. To configure this setting, execute the jpcconf ipv6 enable command. If the use of IPv6 is already enabled, there is no need to configure this setting. To check whether the use of IPv6 is enabled, execute the jpcconf ipv6 display command.

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

When PFM - RM for Platform will use IPv6 to communicate with monitored hosts, specify a monitored host name that can be resolved.

PFM - RM for Platform uses a resolvable IP address to communicate with a monitoring target. When PFM - RM for Platform communicates with a monitoring target in an environment where IPv4 and IPv6 coexist, PFM - RM for Platform will not try to communicate using another IP address if communication using a resolvable IP address fails.

For example, if a connection attempt using IPv4 fails, PFM - RM for Platform will not retry using IPv6. Conversely, if a connection attempt using IPv6 fails, PFM - RM for Platform will not retry using IPv4. Therefore, make sure that connection can be established beforehand.

(c) Setting port numbers

You must assign a port number to each service of the programs used in Performance Management. Set up the network in such a manner that the port numbers assigned to PFM - RM for Platform can be used for communication.

The table below lists and describes the default port numbers assigned to various services. For other services, an unused port number is assigned automatically each time the service starts.

Table 3‒19: Default port numbers for services (for Windows)

No.	Supported function	Service name	Parameter	Port number	Description
1	Service configuration information management function	Name Server	jp1pcnsvr	22285	Port number used by PFM - Manager's Name Server service. This port number is set at all hosts of Performance Management.
2	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 at the host where PFM - Manager and PFM - Base are installed.
3	Monitoring console communication function	View Server	jp1pcvsvr	22286	Port number used by the View Server service of PFM - Manager. This port number is set at the host where PFM - Manager is installed.
4	Web service function	Web Service	--	20358	Port number used by the Web Service service of PFM - Web Console.
5	Web container function	Web Console	--	20359 20360	Port number used by the Web Console service of PFM - Web Console.
6	JP1/SLM linkage facility	JP1/ITSLM	--	20905	Default port number specified in JP1/SLM.

When you use Performance Management in an environment that includes a firewall, you must use fixed port numbers. For details about how to use fixed port numbers, see the chapter that describes installation and setup in the JP1/Performance Management Planning and Configuration Guide.

(a) Prerequisite OSs for monitored hosts

A monitored host must be using one of the following OSs:

• HP-UX

• Solaris

• AIX

• Linux (including Linux 8)

Note that health check monitoring can monitor hosts and hardware equipment, even not running the prerequisite OSs listed above, that support the ICMP protocol (can communicate through ping command).

(b) Prerequisite programs for Performance Management

PFM - Manager or PFM - Base must be available on the host where PFM - RM for Platform is installed.

If you install PFM - RM for Platform on a host where PFM - Manager is available, PFM - Base is not required. If you install multiple PFM - RMs on a host where PFM - Base is available, you need only one PFM - Base.

You also need PFM - Web Console in order to use PFM - RM for Platform to monitor the operation of monitored hosts.

(a) Installing packages

(b) SSH connection settings

Specify the SSH connection settings at both the PFM - RM host and the monitored hosts. For details about the SSH connection settings, see 3.2.5 SSH (for UNIX) connection setting method.

(c) User of a monitored host

If the OS of a monitored host is AIX and a user other than root is to collect information, that user must belong to both the adm group and the system group; otherwise, some information will not be collected.

To ensure that the user belongs to both groups (adm and system), execute the following command at the connection-target monitored host:

$ id
uid=xxx(xxx) gid=x(xxx) groups=0(system),4(adm)

For details about the information that will not be collected, see 7. Records. If the OS of the monitored host is not AIX, this user limitation is not applicable.

(a) Setting the connection-target PFM - Manager

The health check function must be enabled on the connection-target PFM - Manager.

For details about the setting method of the health check function, see the chapter that describes the settings of the health check function in the JP1/Performance Management User's Guide.

(b) Setting at the PFM - RM host

The PFM - RM host must have the following settings enabled:

• Status management function

  For details about the setting method of the status management function, see the chapter that describes the settings of the status management function in the JP1/Performance Management User's Guide.

• Monitored host polling

  Set the Health Check for Target Hosts property for the Remote Monitor Collector service of PFM - RM for Platform to Yes.

(c) Setting health check monitoring

Set the TargetType property for the PFM - RM for Platform remote agent to icmp. Health check monitoring can monitor the operating statuses of hosts and hardware equipment that support the ICMP protocol (can communicate through ping command).

For details about the settings of health check monitoring, see 3.2.4(4) Setting the monitored host.