6.3.2 Before installation

(a) 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 the PFM - Agent for Service Response running on logical hosts.

• Both the executing and standby systems are configured to suppress error reporting to Microsoft.

Notes:

• In Windows, a dialog box for reporting an error to Microsoft is displayed when an application error occurs. This dialog box may cause failover to fail; therefore, reporting of the error must be suppressed. For details about the suppression procedure, see the documentation that comes with the OS.

• In Windows, if an application error occurs, a dialog box will be displayed to report the error to Microsoft. If this dialog box is displayed, a failover could not occur. Therefore, you must disable error reporting. If the nodes have not been set up to disable error reporting, take the following steps.

In Windows Server 2008

1. Choose Control Panel > System and Security > Action Center > Maintenance.

2. In Check for solutions to problem reports, click Settings.

3. In the Choose when to check for solutions to problem reports dialog box, choose Never check for solutions (not recommended).

4. Click the OK button.

In Windows Server 2012

1. Choose Control Panel > System and Security > Action Center > Maintenance.

2. In Check for solutions to unreported problems, click Settings.

3. In the Windows Error Reporting Configuration dialog box, choose I don't want to participate, and don't ask me again.

4. Click the OK button.

In Windows Server 2016

1. Right-click the Windows Start menu and then choose Run from the displayed menu.

2. Enter gpedit.msc, and then click the OK button.

   The Local Group Policy Editor appears.

3. Click Computer Configuration, Administrative Templates, Windows Components, and then Windows Error Reporting.

4. In the right pane, right-click Disable Windows Error Reporting, and then from the displayed menu, choose Edit.

   The setting window appears.

5. In the setting window, select the Enabled check box.

6. Click the OK button.

• If you upgrade from a version 08-00 of PFM - Agent for Service Response to a newer one while it is operating in a cluster system, you must copy the measurement condition registration file on the shared disk in advance. For details about, see 6.3.4 Setup.

(b) Shared disk

Make sure that the following conditions are satisfied:

• A shared disk is available to 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 by means of a Fibre Channel or SCSI.

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

• In the event of a failover, the shared disk can be forced offline (for example, by the cluster software) to achieve failover even if some processing using the shared disk continues due to a problem.

• Each instance of Performance Management programs on the same logical host uses the same directory on the shared disk.

  Note that you can change the location of the Store database to another folder on the shared disk.

(c) Logical host names and 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 operation 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 throughout the system.

Notes:

• Do not specify a physical host name (that is, a host name displayed by the hostname command) as a logical host name. If it is specified, normal communication processing may not be achieved.

• A logical host name must consist of 1 to 32 bytes of alphanumeric characters. None of the following symbols or the space character can be used:

  / \ : ; * ? ' " < > | & = ,.

• A logical host name cannot begin with localhost, an IP address, or the hyphen (-).

(d) Settings when IPv6 used

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 - Agent for Service Response 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 communication in the 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 - Agent host by using the jpcconf ipv6 enable command.

In addition, before installing PFM - Agent for Service Response, you need to enable the use of IPv6 on the PFM - Agent for Service Response host. You have to execute the jpcconf ipv6 enable command to enable this setting. If this setting is already enabled, however, you do not need to execute the command. If you want to check whether the use of IPv6 is enabled, execute the jpcconf ipv6 display 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

Execute the jpcconf ipv6 enable command on both the executing node and the standby node. For details about the conditions or occasions for executing the jpcconf ipv6 enable command and the jpcconf ipv6 display command, see the chapter that describes network configuration examples in an environment that includes IPv6 in the JP1/Performance Management Planning and Configuration Guide.