5.3.4 Setup procedure in a cluster system
This subsection describes the setup required to operate Performance Management in a cluster system.
There are setup procedures for the executing node and for the standby node. Set up the executing node first, and then set up the standby node.
Note that the icon indicates an item that must be performed for the executing node, and the icon
indicates an item that must be performed for the standby node. The icon
indicates either of the following setup items:
-
A setup item that is required depending on the environment that is used
-
A setup item that is used for changing the default setting
- Organization of this subsection
(1) Registering PFM - Agent for Platform
![[Figure]](GRAPHICS/ZUI02001.GIF)
The procedure for registering PFM - Agent for Platform is the same as for a non-cluster system. For details about this procedure, see 4. Installation and Setup in Windows.
(2) Setting up a logical host of PFM - Agent
You must set up a logical host environment for PFM - Agent for Platform on the executing node.
- Note:
-
Before starting this setup, stop all services of Performance Management programs in the entire Performance Management system. For details about how to stop services, see the chapter that describes startup and termination of Performance Management in the JP1/Performance Management User's Guide.
(a) Bringing the shared disk online ![[Figure]](GRAPHICS/ZUI03001.GIF)
Make sure that the shared disk is online. If it is not online, bring it online by using a cluster software operation or volume manager operation.
(b) Setting up a logical host of PFM - Agent for Platform ![[Figure]](GRAPHICS/ZUI03001.GIF)
Execute the jpcconf ha setup command to create a logical host environment. This command creates a logical host environment by copying necessary data to the shared disk and setting definitions for a logical host.
To set up a logical host of PFM - Agent for Platform:
-
Execute the jpcconf ha setup command to create a logical host environment for PFM - Agent for Platform.
Execute the command as follows:
jpcconf ha setup -key Windows -lhost jp1-halaop -d S:\jp1
Use the -lhost option to specify the logical host name. This example specifies jp1-halaop as the logical host name. If you use DNS, specify the logical host name without the domain name.
Specify the folder name on the shared disk in the environment folder name of the -d option. For example, if -d S:\jp1 is specified, S:\jp1\jp1pc is created and then files for the logical host environment file are created.
-
Execute the jpcconf ha list command to check the logical host settings.
Execute the command as follows:
jpcconf ha list -key all
Make sure that the created logical host environment is valid.
(c) Setting up the connection-target PFM - Manager ![[Figure]](GRAPHICS/ZUI03001.GIF)
Execute the jpcconf mgrhost define command to set up the PFM - Manager that manages PFM - Agent for Platform.
To set up the connection-target PFM - Manager:
-
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-halaop
Specify the host name of the connection-target PFM - Manager in the -host option. If the connection-target PFM - Manager runs on a logical host, specify the logical host name of the connection-target PFM - Manager in the -host option. This example specifies jp1-hal as the PFM - Manager's logical host name.
Use the -lhost option to specify the logical host name of PFM - Agent for Platform. This example specifies jp1-halaop as the logical host name of PFM - Agent for Platform.
Although the above example shows interactive execution, you can also execute the jpcconf mgrhost define command non-interactively. For details about the jpcconf mgrhost define command, see the chapter that explains the commands in the manual JP1/Performance Management Reference.
(d) Setting up the logical hosts of other Performance Management programs
![[Figure]](GRAPHICS/ZUI02001.GIF)
If you have other PFM - Manager or PFM - Agent programs to be set up on the same logical host in addition to PFM - Agent for Platform, set them up at this stage.
For details about the setup procedure, see the chapter that describes operations in a cluster system in the JP1/Performance Management User's Guide or in the applicable PFM - Agent manual.
(e) Setting up a network
![[Figure]](GRAPHICS/ZUI02001.GIF)
You must set up the network when Performance Management programs run in a network environment that uses a firewall.
The two items below are specified in the network environment settings. Change the settings if necessary.
-
IP addresses
You must specify IP addresses if you use Performance Management in a network connected to multiple LANs. To specify the IP addresses, directly edit the contents of the jpchosts file.
After editing the jpchosts file, copy it from the executing node to the standby node.
For details about how to set IP addresses, see the chapter that describes installation and setup in Windows in the JP1/Performance Management Planning and Configuration Guide.
-
Port numbers
If you establish communication between Performance Management programs via a firewall, use the jpcconf port define command to set the port numbers.
For details about how to set port numbers, see the chapter that describes installation and setup in Windows, and the chapter that describes construction and operations in a cluster system, in the JP1/Performance Management Planning and Configuration Guide.
(f) Changing the log file size
![[Figure]](GRAPHICS/ZUI02001.GIF)
The operating status of Performance Management is output to a log file unique to Performance Management. This log file is called the common message log. The common message log consists of two files with a default size of 8,192 kilobytes each. This setting is required only when you wish to change this file size.
For details, see the chapter that describes installation and setup in Windows in the JP1/Performance Management Planning and Configuration Guide.
(g) Changing the performance data storage destination
![[Figure]](GRAPHICS/ZUI02001.GIF)
This setting is required only when you want to change the folder where the database of performance data managed by PFM - Agent is saved, backed up, exported, or imported. For details about how to specify the setting, see 4. Installation and Setup in Windows.
(h) Setting up the action log output
![[Figure]](GRAPHICS/ZUI02001.GIF)
This setting is required to output action log data when an alarm occurs. Action log data is history information that is output in cooperation with the alarm function related to exceeded thresholds, such as for system load.
For details about how to set up the action log, see I. Outputting Action Log Data.
(i) Exporting the logical host environment definition file ![[Figure]](GRAPHICS/ZUI03001.GIF)
After you have created a logical host environment for PFM - Agent for Platform, you must export the environment definition to a file. This export processing involves output of the definition information for the Performance Management program set up on the logical host to a file in the batch mode. If you are setting up other Performance Management programs on the same logical host, export the environment definitions after all setup processes have been completed.
To export the logical host environment definition:
-
Execute the jpcconf ha export command to export the logical host environment definition.
Output to an export file the definition information that has been created so far for the logical host environment. You can assign any name to the export file.
For example, to export the logical host environment definitions to the lhostexp.txt file, execute the following command:
jpcconf ha export -f lhostexp.txt
Although the above example shows interactive execution, you can also execute the jpcconf ha export command non-interactively. For details about the jpcconf ha export command, see the chapter that explains the commands in the manual JP1/Performance Management Reference.
(j) Copying the logical host environment definition file to the standby node
![[Figure]](GRAPHICS/ZUI03002.GIF)
Copy the logical host environment definition file exported in (i) Exporting the logical host environment definition file from the executing node to the standby node.
(k) Taking the shared disk offline
![[Figure]](GRAPHICS/ZUI02001.GIF)
Take the shared disk offline by using a cluster software operation or volume manager operation, to complete the task. If you plan to continue using the shared disk, there is no need to take it offline.
(3) Setting up a logical host environment for the standby node ![[Figure]](GRAPHICS/ZUI03002.GIF)
Set up a logical host environment for PFM - Agent for Platform on the standby node.
(a) Importing the logical host environment definition file ![[Figure]](GRAPHICS/ZUI03002.GIF)
Import the export file that was copied from the executing node, to the standby node.
To specify settings for executing (on the standby node) the Performance Management program of the logical host created on the executing node, use the jpcconf ha import command. If multiple Performance Management programs have been set up for a single logical host, the settings for all the programs are imported in batch mode.
When executing this command, there is no need to keep the shared disk in online status.
To import the logical host environment definition file:
-
Execute the jpcconf ha import command to import the logical host environment definition.
Execute the command as follows:
jpcconf ha import -f lhostexp.txt
Although the above example shows interactive execution, you can also execute the jpcconf ha import command non-interactively. For details about the jpcconf ha import command, see the chapter that explains the commands in the manual JP1/Performance Management Reference.
This command changes settings to make the environment for the standby node the same as in the export file. As a result, setup is performed for starting PFM - Agent for Platform on the logical host.
If fixed port numbers were set by the jpcconf port define command during setup, they are also set in the same manner.
-
Execute the jpcconf ha list command to check the logical host settings.
Execute the command as follows:
jpcconf ha list -key all
Make sure that the displayed information is the same as when the jpcconf ha list command is executed on the executing node.
(4) Registering PFM - Agent in the cluster software
![[Figure]](GRAPHICS/ZUI03002.GIF)
To run Performance Management programs in a logical host environment, you must register them in the cluster software, and set up the environment so that the Performance Management programs start and terminate from the cluster software.
This subsection describes the settings for registering PFM - Agent for Platform in the cluster software.
For PFM - Agent for Platform, register the services listed in the following table in the cluster software.
No. |
Name |
Service name |
Dependency |
---|---|---|---|
1 |
PFM - Agent Store for Windows [logical host name] |
JP1PCAGT_TS [logical host name] |
IP address resource Physical disk resource |
2 |
PFM - Agent for Windows [logical host name] |
JP1PCAGT_TA [logical host name] |
Cluster resources shown in no. 1 above |
3 |
PFM - Action Handler [logical host name] |
JP1PCMGR_PH [logical host name] |
IP address resource Physical disk resource |
If the logical host name is jp1-halaop, the service is PFM - Agent for Platform [jp1-halaop], and the service name is JP1PCAGT_TS [jp1-halaop].
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 5-3 PFM - Agent for Platform services to be registered in the cluster software.
-
Do not set Startup parameters or Registry Replication.
-
Set the Policies tab in Properties according to 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 Platform, 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:
-
A service registered in the cluster is started and stopped from the cluster. Therefore, make sure that Startup type is set to Manual so that the service will not start automatically during OS startup. Immediately after setup is performed by the jpcconf ha setup command, the service is set to Manual.
For dependency settings specified if PFM - Agent for Platform is on the PFM - Manager logical host, see the chapter that describes construction and operation in a cluster system in the JP1/Performance Management User's Guide.
(5) Checking startup and stop from the cluster software
![[Figure]](GRAPHICS/ZUI03002.GIF)
Make sure that Performance Management programs function normally by starting and terminating the programs from the cluster software on each node.
(6) Setting up an environment in a cluster system
![[Figure]](GRAPHICS/ZUI03002.GIF)
When you have finished setting up Performance Management programs, set up their environment so that PFM - Web Console can display operating status reports for monitored programs as appropriate to the operations. You must also set up the environment so that notifications can be sent to the user in the event of a problem in a monitored program.
For details about how to set up an environment for the Performance Management programs, see the chapter that describes construction and operation in a cluster system in the JP1/Performance Management User's Guide.
To transfer an environment used in a physical environment to a logical environment, change the settings to prevent unnecessary records from being collected in each of the physical and logical environments.