3.3.1 Preparation for installation and setup

This subsection describes the prerequisites for installation and setup, and provides cautionary notes and other information you should know before installing and setting up PFM - RM for Microsoft SQL Server.

Organization of this subsection
(1) Prerequisites
(2) Information required to set up PFM - RM for Microsoft SQL Server to run on a logical host
(3) Cautionary notes on failing over a logical host with PFM - RM for Microsoft SQL Server
(4) Cautionary notes on upgrading when Microsoft SQL Server runs on a logical host

(1) Prerequisites

The following are the prerequisites for running PFM - RM for Microsoft SQL Server in a cluster system.

(a) Cluster system

Make sure that the following conditions are satisfied:

Notes:
  • Failover may not take place if Dr. Watson encounters an application error and displays a message box. For this reason, you must disable error notification that displays a message box. For details about the procedure, see the documentation for your OS. Note that disabling error notification may affect data collection when an application error occurs.
  • When an application error occurs in Windows Server 2003, a dialog box giving you the option of reporting the problem to Microsoft appears. Because the dialog box can interfere with failover, you must disable error reporting. For details about disabling error reporting, see the documentation for the OS.
(b) Shared disk

Make sure that the following conditions are satisfied:

(c) Logical host names and logical IP addresses

Make sure that the following conditions are satisfied:

Notes:
  • Do not specify the physical host name (the host name displayed by the hostname command) as the name of the logical host. If you do so, normal communication may not be possible.
  • Logical host names can consist of 1 to 32 alphanumeric characters. A logical host name cannot include space characters or any of the following characters:
    / \ : ; * ? ' " < > | & = , .
  • You cannot specify localhost, an IP address, or a host name beginning with a hyphen (-) as a logical host name.
(d) Settings when IPv6 used

Performance Management supports IPv6 environments as well as IPv4 environments as a network configuration. Therefore, Performance Management can operate even in a network configuration in which both an IPv4 environment and an IPv6 environment are used.

PFM - RM for Microsoft SQL Server can communicate with PFM - Manager via IPv6.

Note that this explanation applies only when the OS of a host on which PFM - RM for Microsoft SQL Server is installed is Windows Server 2008 R2 or Windows Server 2012, and the OS of a host on which PFM - Manager is installed is Windows Server 2008 R2, Windows Server 2012 or Linux.

For details about the scope of communication in an environment with both IPv4 and IPv6, see L. About Communication in IPv4 Environments and IPv6 Environments.

When you want to use IPv6 for communication, the settings for using IPv6 need to be enabled on both the PFM - Manager host and the PFM - RM host. You can specify the settings by executing the jpcconf ipv6 enable command. The following describes when the command needs to be executed and when it does not need to be executed.

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 separately on the executing node and on the standby node.

For details about the jpcconf ipv6 enable command, see the chapter that describes commands in the manual Job Management Partner 1/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 Job Management Partner 1/Performance Management Planning and Configuration Guide.

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

Communication between PFM - RM for Microsoft SQL Server 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 Microsoft SQL Server 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 beforehand that a connection can be established.

(2) Information required to set up PFM - RM for Microsoft SQL Server to run on a logical host

When you set up PFM - RM for Microsoft SQL Server to run in a logical host environment, you must specify the information shown in the following table, in addition to the environment information required for PFM - RM for Microsoft SQL Server setup.

Table 3-2 Information required to set up PFM - RM for Microsoft SQL Server to run on a logical host

ItemExample
Logical host namejp1-halSQL
Logical IP address172.16.92.100
Shared diskS:\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 how much shared disk capacity is needed, see A. Estimating System Requirements.

(3) Cautionary notes on failing over a logical host with PFM - RM for Microsoft SQL Server

In a system configuration in which PFM - RM for Microsoft SQL Server runs on a logical host, consider whether you want the entire logical host to fail over when an error occurs in PFM - RM for Microsoft SQL Server.

If the entire logical host is failed over when an error occurs in PFM - RM for Microsoft SQL Server, business applications on the same logical host will also be failed over. Failover of these applications may affect any business operations that are in progress.

(4) Cautionary notes on upgrading when Microsoft SQL Server runs on a logical host

When you upgrade PFM - RM for Microsoft SQL Server that runs on a logical host, you need to bring the shared disk on either the executing node or the standby node online.