3.3.4 Setup procedure
This subsection describes how to set up Performance Management to run in a cluster system.
When you want to operate Performance Management in a cluster system, setup is needed on both the executing node and the standby node. You must perform setup on the executing node before performing the setup on the standby node.
indicates a task to be performed on the executing node.
indicates a task to be performed on the standby node.
indicates a setup item that is required depending on the environment or an optional setup item used when the default is to
be changed.
- Organization of this subsection
-
-
(3) Set up the logical host environment for PFM - Agent for Microsoft SQL Server
-
(6) Registering the A4QHITACHIPROCSPDATABASES Stored Procedure
-
(7) Set up the logical host environment for other Performance Management programs
-
(13) Copy the logical-host environment definition file to the standby node
-
(16) Register PFM - Agent for Microsoft SQL Server in the cluster software
-
(17) Check whether services can be started and stopped from the cluster software
(1) Register PFM - Agent for Microsoft SQL Server
![[Figure]](GRAPHICS/ZU12001.GIF)
To perform integrated management of PFM - Agent using PFM - Manager and PFM - Web Console, you must register PFM - Agent for Microsoft SQL Server with PFM - Manager and PFM - Web Console.
You will need to register PFM - Agent for Microsoft SQL Server in the following cases:
-
You add a new instance of PFM - Agent for Microsoft SQL Server to the Performance Management system.
-
You update the data model version of an instance of PFM - Agent for Microsoft SQL Server that is already registered.
Registration is performed separately for PFM - Manager and PFM - Web Console. The registration procedure is the same as in the registration procedure in a non-cluster system.
For details about the procedure, see 2.1.4(1) Registering PFM - Agent for Microsoft SQL Server.
(2) Bring the shared disk online ![[Figure]](GRAPHICS/ZU12002.GIF)
Make sure that the shared disk is online. If the shared disk is not online, use the cluster software or the volume manager to bring it online.
(3) Set up the logical host environment for PFM - Agent for Microsoft SQL Server ![[Figure]](GRAPHICS/ZU12002.GIF)
Execute the jpcconf ha setup command to set up the logical host environment. When you execute the command, the necessary files are copied to the shared disk, the logical host definition is set up, and the logical host environment is created.
- Note:
-
Before you execute the command, stop all Performance Management programs and services throughout the Performance Management system. For details about how to stop services, see the chapter on starting and stopping Performance Management in the JP1/Performance Management User's Guide.
To set up the logical host environment:
-
Execute the jpc conf ha setup command to create the logical host environment for PFM - Agent for Microsoft SQL Server.
Execute the command as follows:
jpcconf ha setup -key SQL -lhost jp1-halSQL -d S:\jp1
Use the -lhost option to specify the logical host name. In the example above, the logical host name is jp1-halSQL. For DNS operation, specify a logical host name with the domain name portion removed.
Specify the name of the shared disk directory as the environment directory name of the -d option. For example, if you specify -d S:\jp1, the directory S:\jp1\jp1pc is created, and the files for the logical host environment are created in that directory.
-
Execute the jpcconf ha list command to check the logical host settings.
Execute the command as follows:
jpcconf ha list -key all
Confirm that the logical host environment you created has been set up correctly.
(4) Set the connection-target PFM - Manager ![[Figure]](GRAPHICS/ZU12002.GIF)
Execute the jpcconf mgrhost define command to specify which PFM - Manager is to manage PFM - Agent for Microsoft SQL Server.
-
Execute the jpcconf mgrhost define command to set the connection-target PFM - Manager.
Execute the command as follows:
jpcconf mgrhost define -host jp1-hal -lhost jp1-halSQL
Use the -host option to specify the host name of the connection-target PFM - Manager. If that PFM - Manager is running in a logical host environment, specify the logical host name of the PFM - Manager in the -host option. In the example above, the logical host name of PFM - Manager is jp1-hal.
Use the -lhost option to specify the logical host name of PFM - Agent for Microsoft SQL Server. In the example above, the logical host name of PFM - Agent for Microsoft SQL Server is jp1-halora.
Although an example of interactive command execution is shown here, the jpcconf mgrhost define command can be also executed non-interactively. For details about the jpcconf mgrhost define command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
(5) Set up an instance environment ![[Figure]](GRAPHICS/ZU12002.GIF)
Execute the jpcconf inst setup command to set up an instance environment for PFM - Agent for Microsoft SQL Server.
The setup procedure is the same as the setup procedure in a non-cluster system, except that, in a cluster system, you must specify the logical host name in the -lhost option when executing the jpcconf inst setup command.
In a cluster system, the jpcconf inst setup command is executed in the following format:
jpcconf inst setup -key SQL -lhost logical-host-name -inst instance-name
As the agent log output folder (the value of log_path), specify the path of a folder that is on the shared disk.
Although an example of interactive command execution is shown here, the jpcconf inst setup command can be also executed non-interactively. For details about the jpcconf inst setup command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
For details about other settings and procedures, see 2.1.4(2) Setting up an instance environment.
(6) Registering the A4QHITACHIPROCSPDATABASES Stored Procedure
![[Figure]](GRAPHICS/ZU12001.GIF)
Register the stored procedure in order for PFM - Agent for Microsoft SQL Server to obtain the names and the sizes of the databases from Microsoft SQL Server
The registering procedure is the same as that of the non-cluster-system. For details, see 2.1.4(3) Registering the A4QHITACHIPROCSPDATABASES Stored Procedure.
(7) Set up the logical host environment for other Performance Management programs
![[Figure]](GRAPHICS/ZU12001.GIF)
At this point, set up any other Performance Management programs, such as PFM - Manager or PFM - Agent, on the same logical host.
For details about how to set up these products, see the chapters on setup and operation in a cluster system in the JP1/Performance Management User's Guide, and the chapter on operation in a cluster system in the manuals for the applicable version of PFM - Agent.
(8) Specify network settings
![[Figure]](GRAPHICS/ZU12001.GIF)
This setup task is necessary only when you change the network settings to match the configuration in which Performance Management is used.
The following are the two network setting items:
-
IP addresses
To specify the IP address used by Performance Management in a network environment where multiple LANs are connected, directly edit the contents of the jpchosts file.
After editing the file, copy it from the executing node to the standby node.
For details about how to set IP addresses, see the chapter on installation and setup in the JP1/Performance Management Planning and Configuration Guide.
-
Port numbers
If Performance Management programs will communicate with each other through a firewall, use the jpcconf port command to set the port numbers.
For details about how to set port numbers, see the chapter on installation and setup and the chapters on setup and operation in a cluster system in the JP1/Performance Management Planning and Configuration Guide.
(9) Change the size of log files
![[Figure]](GRAPHICS/ZU12001.GIF)
Performance Management outputs its operating status to a set of proprietary log files called a common message log. By default, the common message log consists of two 2,048 KB files. Perform this setting if you want to change the default file size.
For details, see the chapter on installation and setup in the JP1/Performance Management Planning and Configuration Guide.
(10) Change the storage location of performance data
![[Figure]](GRAPHICS/ZU12001.GIF)
Perform this setting only if you want to change the folders where the database of performance data managed by PFM - Agent for Microsoft SQL Server is saved, backed up, exported, or imported.
For details, see 2.4.1 Changing the storage location of performance data.
(11) Setting up the action log
![[Figure]](GRAPHICS/ZU12001.GIF)
This setting is required to output action log when alarm occur. The action log stores history information that is output in conjunction with the alarms for thresholds related to system load and other conditions.
For details about how to set up the action log, see J. Outputting Action Log Information.
(12) Export the logical-host environment definition file ![[Figure]](GRAPHICS/ZU12002.GIF)
Once you have created the logical host environment for PFM - Agent for Microsoft SQL Server, export the environment definition as a file. In the export process, a file containing the collective definition information for all Performance Management programs set up on that logical host is output. Export the environment definition only after you have set up all additional Performance Management programs on the logical host.
To export the environment definition of the logical host:
-
Execute the jpcconf ha export command to export the environment definition of the logical host.
The definition information for the logical host environment you created is output to an export file. You can give this file any name you wish.
For example, execute the command as follows to output the logical host environment definition to the file lhostexp.txt:
jpcconf ha export -f lhostexp.txt
Although an example of interactive command execution is shown here, the jpcconf ha export command can be also executed non-interactively. For details about the jpcconf ha export command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
(13) Copy the logical-host environment definition file to the standby node
![[Figure]](GRAPHICS/ZU12003.GIF)
Copy the file you exported in (12) Export the logical-host environment definition file from the executing node to the standby node.
(14) Take the shared disk offline
![[Figure]](GRAPHICS/ZU12001.GIF)
Use the cluster software or the volume manager to take the shared disk offline. Note that if you intend to continue using the shared disk, you do not need to take it offline at this point.
(15) Import the logical-host environment definition file ![[Figure]](GRAPHICS/ZU12003.GIF)
On the standby node, import the exported file you copied from the executing node.
Use the jpcconf ha import command to set up the environment definition for the Performance Management programs of the logical host that you created on the executing node so that they run on the standby node. If more than one Performance Management program was installed on the logical host, the definition information for all of the programs is imported in batch form.
Note that the shared disk does not need to be online when you execute this command.
To import the logical-host environment definition file:
-
Execute the jpcconf ha import command to import the environment definition of the logical host.
Execute the command as follows:
jpcconf ha import -f lhostexp.txt
Although an example of interactive command execution is shown here, the jpcconf ha import command can be also executed non-interactively. For details about the jpcconf ha import command, see the chapter that describes commands in the manual JP1/Performance Management Reference.
When you execute the command, the settings on the standby node are changed to reflect the environment described in the export file. This sets up the standby node to run PFM - Agent for Microsoft SQL Server as a logical host.
If you used the jpcconf ha import command to assign fixed port numbers during setup, the same port numbers will take effect on the standby node.
-
Execute the jpcconf ha list command to check whether the logical host is set up correctly.
Execute the command as follows:
jpcconf ha list -key all
Check whether the same output is displayed as when you executed jpcconf ha list on the executing node.
(16) Register PFM - Agent for Microsoft SQL Server in the cluster software
![[Figure]](GRAPHICS/ZU12003.GIF)
If you intend to use Performance Management programs in a logical host environment, make sure that the programs are registered in the cluster software. Also, set up the environment so that the Performance Management programs are started and stopped based on instructions from the cluster software.
For details about how to register PFM - Agent for Microsoft SQL Server in the cluster software, see your cluster software documentation.
For the dependency settings specified if PFM - Agent for Microsoft SQL Server is on the PFM - Manager logical host, see the chapter on cluster system setup and operation in the JP1/Performance Management User's Guide.
This subsection describes how to register PFM - Agent for Microsoft SQL Server in your cluster software, using the settings for Windows WSFC as an example.
Register the following services of PFM - Agent for Microsoft SQL Server in the cluster software:
No. |
Name |
Service name |
Dependencies |
---|---|---|---|
1 |
PFM - Agent Store for Microsoft(R) SQL Server instance-name [LHOST] |
JP1PCAGT_QS_instance-name [LHOST] |
IP address resource Physical disk resource |
2 |
PFM - Agent for Microsoft(R) SQL Server instance-name [LHOST] |
JP1PCAGT_QA_instance-name [LHOST] |
Cluster resource in No. 1 |
3 |
PFM - Action Handler [LHOST] |
JP1PCMGR_PH [LHOST] |
IP address resource Physical disk resource |
Replace LHOST with the logical host name. For example, if the instance name is SQL1 and the logical host name is jp1-halSQL, the display name of the service will be PFM - Agent Store for Microsoft(R) SQL Server SQL1 [jp1-halSQL], and the service name will be JP1PCAGT_QS_SQL1 [jp1-halSQL].
For WSFC, register these services as WSFC resources. Set each resource as follows:
-
In Resource type, register the resource as Generic Service.
-
Set Dependencies as shown in Table 3-3.
-
Do not set Startup parameters or Registry Replication#.
- #
-
This tab is displayed only in a Windows Server 2008 R2 environment.
-
Set the Policies tab in Properties by taking into account whether you want a failover to occur in the event of a Performance Management program failure.
For example, to trigger a failover when a failure occurs in PFM - Agent for Microsoft SQL Server, set the Policies tab as follows:
-
Select the If resource fails, attempt restart on current node radio button.
-
Select the If restart is unsuccessful, fail over all resources in this service or application check box#.
-
-In principle, set Maximum restarts in the specified period: to 3.
#
In the case of Windows Server 2012 or later, the If restart is unsuccessful, fail over all resources in this Role check box is used instead.
-
- Note:
-
The cluster software is responsible for starting and stopping the services that have been registered in it. Set Startup type for those services to Manual to prevent them from starting automatically when the OS starts. When you set up a service using the jpcconf ha setup command, Startup type for the service will be set to Manual.
-
When registered PFM - Agent for Microsoft SQL Server and PFM - Agent Store for Microsoft SQL Server in a cluster system, do not set dependencies between PFM - Agent for Microsoft SQL Server and Microsoft SQL Server. Setting the dependencies might result in delayed failover.
-
When linked with the integrated management product (JP1/IM), specify the dependency settings so that the service of JP1/Base stops after the service of PFM - Agent for Microsoft SQL Server stops.
-
(17) Check whether services can be started and stopped from the cluster software
![[Figure]](GRAPHICS/ZU12003.GIF)
Check whether the cluster software is operating correctly by using it to issue start and stop requests to Performance Management programs on each node.
(18) Set up the environment in the cluster system
![[Figure]](GRAPHICS/ZU12003.GIF)
After setting up the Performance Management programs, use PFM - Web Console to set up the environment for the programs. You will then be able to display reports on the operating status of monitoring targets, and notify users whenever a problem occurs.
For details about setting up the environment for Performance Management programs, see the chapters on setup and operation in a cluster system in the JP1/Performance Management User's Guide.