3.3.1 Preparation for installation and setup

(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 - RM for Virtual Machine running on logical hosts.

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

  Important

  If the occurrence of an error causes a dialog box for reporting the error to Microsoft to be displayed. Because this dialog box can prevent a failover from occurring, you need to suppress error reporting. If error reporting is currently enabled, suppress it by specifying the following setting:

  Windows Server 2012:

  1. Select Control Panel, System and Security, Action Center, and then Maintenance.

  2. Under Check for solutions to problem reports, select Settings.

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

  4. Click the OK button.

  Windows Server 2016 or later:

  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.

(b) Shared disk

Make sure that the following conditions are satisfied:

• Each logical host must have a shared disk, and it must be possible to switch from the executing node to a standby node.

• The shared disk must be physically connected to each node via Fibre Channel or SCSI. Performance Management does not support a configuration in which a network drive or a disk replicated via a network is used as a shared disk.

• Even if a problem causes a process that is using the shared disk to remain when a failover occurs, it must be possible to forcibly take the shared disk offline and enable a failover using a means such as cluster software.

• If multiple PFM products are used on a single logical host, the folder name of the shared disks must be the same. You can change the storage destination of the Store database and store it in a different folder on the shared disk.

(c) Logical host names and logical IP addresses

Make sure that the following conditions are satisfied:

• Each logical host must have a logical host name, and each logical host name must have a corresponding logical IP address, and it must be possible to switch from the executing node to a standby node.

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

• If DNS is used, a host name excluding the domain name, not the FQDN name, must be used as the logical host name.

• Physical host names and logical host names must be unique within the system.

  Important

  • Do not specify a physical host name (host name displayed by the hostname command) for the logical host name. Otherwise, communication may not be processed correctly.

  • A logical host name can use from 1 through 32 bytes of alphanumeric characters. Spaces and the following symbols cannot be specified:

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

  • You cannot specify a logical host name that begins with the character string localhost, an IP address, or a hyphen (-).

(d) Settings for using IPv6

Performance Management supports network configurations in IPv4 and IPv6 environments. Performance Management is able to operate with a network configuration in which IPv4 and IPv6 environments coexist.

PFM - RM for Virtual Machine can communicate with PFM - Manager via IPv6.

Note that for Performance Management to operate with that network configuration, the OS of the host on which PFM - Manager is installed must be Windows or Linux.

For information about the applicable scope of communications in IPv4 and IPv6 environments, see K. About Communication in IPv4 Environments and IPv6 Environments.

To make it possible to communicate via IPv6, the setting for using IPv6 must be enabled on both the PFM - Manager host and the PFM - RM host. This setting can be enabled by using the jpcconf ipv6 enable command. However, there are cases in which execution of this command is necessary and others where it is unnecessary.

Cases in which 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 in which 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

Make sure that you 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 describes 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.

When you use IPv6 for communication between a monitored host and PFM - RM for Virtual Machine, specify the name of a monitored host where name resolution can be performed.

Communication between PFM - RM for Virtual Machine and a monitoring target is performed with an IP address that can be resolved. Also, if an IPv4 environment and an IPv6 environment are both used, and communication between PFM - RM for Virtual Machine and the monitoring target fails with an IP address that can be resolved, the communication is not retried by using another IP address.

For example, if communication fails when IPv4 is used, IPv6 is not used to retry communication. Similarly, if communication fails when IPv6 is used, IPv4 is not used to retry communication. Make sure that a connection can be established beforehand.