Hitachi

JP1 Version 12 for UNIX Systems JP1/Performance Management - Agent Option for Platform Description, User's Guide and Reference


6.3.2 Items to be checked before installation in a cluster system

This subsection describes the prerequisites, required information, and notes you must confirm before you start installation and setup.

Organization of this subsection

(1) Prerequisites

To use PFM - Agent for Platform in a cluster system, the following prerequisites must be satisfied.

(a) Performance Management version

To use PFM - Agent for Platform in a cluster system, JP1/Performance Management - Base 11-01 or later or JP1/Performance Management - Manager 11-01 or later is required in devices where PFM - Agent for Platform is installed.

(b) Cluster system

Confirm that the following conditions are met:

  • The cluster system is controlled by the cluster software.

  • The cluster software is configured to control the startup and termination of PFM - Agent for Platform running on logical hosts.

(c) Shared disk

Make sure that the following conditions are satisfied:

  • A shared disk is available for each logical host, and information can be inherited from the executing node to the standby node.

  • The shared disk is physically connected to each node via Fibre Channel or SCSI.

    Performance Management does not support configurations in which a disk replicated by a network drive or via a network is used as a shared disk.

  • The shared disk can be forcibly unmounted (for example, by the cluster software) to achieve failover even if some processes using the shared disk continue due to a problem.

  • Instances of Performance Management programs on the same logical host use the same directory name on the shared disk. Note that you can change the location of the Store database to another directory on the shared disk.

(d) Logical host names and logical IP addresses

Make sure that the following conditions are satisfied:

  • Each logical host has a logical host name and a corresponding logical IP address, and this information can be inherited from the executing node to the standby node.

  • The logical host names and logical IP addresses are set in the hosts file and name server.

  • If DNS is used, the host name without the domain name is used as the logical host name, not the FQDN name.

  • All physical and logical host names are unique within the system.

Important
  • Do not specify a physical host name (that is, a host name displayed by the uname -n command) as a logical host name. If one is specified, normal communication processing might not be achieved.

  • The logical host name must consist of 1 to 32 characters.

  • The logical host name must consist of alphanumeric characters, hyphens (-), and underscores (_) only.

  • For the logical host name, you cannot specify localhost, an IP address, or a host name beginning with a hyphen (-).

(e) Settings when IPv6 is used

Because Performance Management supports IPv6 network configurations in addition to IPv4 environments, you can use Performance Management in a network configuration that contains both IPv4 and IPv6 environments. PFM - Agent for Platform 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.

For details about the scope of application for communication in IPv4 and IPv6 environments, see L. Communication in IPv4 and IPv6 Environments.

To use IPv6 for communication, you need to enable the use of IPv6 on the PFM - Agent host before installing PFM - Agent for Platform. If you want to check whether the use of IPv6 is enabled, execute the jpcconf ipv6 display command. After confirming that IPv6 is enabled on the PFM - Agent host, you need to enable the use of IPv6 on both the PFM - Manager host and the PFM - Agent 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 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 both IPv4 and IPv6 environments are used and PFM - Manager operates in an IPv6 environment

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

jpcconf ipv6 enable

Execute the jpcconf ipv6 enable command on both the executing node and the standby node.

For details about the jpcconf ipv6 enable command, see the chapter that explains the 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.

(2) Information required to set up PFM - Agent for Platform for logical host use

To operate PFM - Agent for Platform on a logical host, you must provide the information in the following table, in addition to the environment information that is needed for normal setup of PFM - Agent for Platform.

Table 6‒2: Information required to set up PFM - Agent for Platform for logical host use

No.

Item

Example

1

Logical host name

jp1-halaop

2

Logical IP address

172.16.92.100

3

Shared disk

/jp1

When multiple Performance Management programs are installed on a single logical host, the programs share the same directory on the shared disk.

For details about the capacity required on the shared disk, see the Release Notes.

(3) Note on making the logical host subject to failover by PFM - Agent for Platform

If you employ a system configuration in which PFM - Agent for Platform operates on a logical host, you must evaluate whether the entire logical host is subject to failover if a PFM - Agent for Platform failure occurs.

If failover of the entire logical host occurs, other job applications running on the same logical host also fail over, which might affect the job.

We recommend that you use one of the following cluster software settings so that errors on PFM - Agent for Platform do not affect the operations of other job applications:

(4) Note on version upgrading in a logical host environment

To upgrade the version of PFM - Agent for Platform in a logical host environment, you need to mount the shared disk on either the executing node or the standby node.