Hitachi

JP1 Version 12 JP1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference

5.4.4 Setup procedure in a cluster system (for UNIX)

This subsection describes the setup needed for running Performance Management in a cluster system.

To run Performance Management in a cluster system, you must set up both the executing node and the standby node. Set up the executing node first, and then set up the standby node.

[Figure] indicates an item that is to be executed at the executing node, and [Figure] indicates an item that is to be executed at the standby node. [Figure] indicates the following setup items:

Important

Do not set JPC_HOSTNAME as an environment variable because it is used by Performance Management. If it is set as an environment variable by mistake, Performance Management will not function correctly.

Organization of this subsection

(1) Registering PFM - RM for Platform[Figure] [Figure] [Figure]

To achieve central management of PFM - RM for Platform in the Performance Management system, you must register PFM - RM for Platform into PFM - Manager and PFM - Web Console.

The conditions and procedure for registering PFM - RM for Platform are the same as when a cluster system is not used. For details about the conditions and procedure for registering PFM - RM for Platform, see 3.2.4(2) Registering PFM - RM for Platform.

To Page Top

(2) Mounting the shared disk[Figure]

Make sure that the shared disk is mounted.

If the shared disk is not mounted, use a program such as the cluster software or a volume manager to mount it.

To Page Top

(3) Setting up a logical host environment for PFM - RM for Platform[Figure]

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.

Note

Before you execute the command, stop all Performance Management programs and services in the entire Performance Management system. For details about how to stop services, see the chapter that describes the startup and termination of Performance Management in the JP1/Performance Management User's Guide.

To set up a logical host environment for PFM - RM for Platform:

  1. Execute the jpcconf ha setup command to create a logical host environment for PFM - RM for Platform.

    Execute the following command:

    jpcconf ha setup -key RMPlatform -lhost jp1-halrmp -d /jp1

    Use the -lhost option to specify the logical host name. This example specifies jp1-halrmp as the logical host name. If you employ DNS operations, specify the logical host name without the domain name.

    Specify in the -d option a directory name on the shared disk within the environment directory. For example, if -d /jp1 is specified, /jp1/jp1pc is created, and then files for the logical host environment are created.

  2. Execute the jpcconf ha list command to check the logical host settings.

    Execute the following command:

    jpcconf ha list -key all

    Make sure that the created logical host environment is correct.

To Page Top

(4) Setting the connection-target PFM - Manager[Figure]

Execute the jpcconf mgrhost define command to set the PFM - Manager that manages PFM - RM for Platform.

To set the connection-target PFM - Manager:

  1. Execute the jpcconf mgrhost define command to set the connection-target PFM - Manager.

    Execute the following command:

    jpcconf mgrhost define -host jp1-hal -lhost jp1-halrmp

    Specify in the -host option the host name of the connection-target PFM - Manager. If the connection-target PFM - Manager is to run on a logical host, specify in the -host option the logical host name of the connection-target PFM - Manager. 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 - RM for Platform. This example specifies jp1-halrmp as the logical host name of PFM - RM for Platform.

    The example above shows execution in the interactive mode, but you can also execute the jpcconf mgrhost define command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

To Page Top

(5) Setting up an instance environment[Figure]

Execute the jpcconf inst setup command to set up an instance environment for PFM - RM for Platform.

The setup procedure is the same as when a cluster system is not employed. However, in the case of a cluster system, you must specify the logical host name in the -lhost option when you execute the jpcconf inst setup command.

The following shows how to specify the jpcconf inst setup command for a cluster system: 

jpcconf inst setup -key RMPlatform -lhost logical-host-name -inst instance-name

This example shows execution in the interactive mode, but you can also execute the jpcconf inst setup command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

For details about the settings and procedure, see 3.2.4(3) Setting up an instance environment.

To Page Top

(6) Setting the monitoring target[Figure]

Execute the jpcconf target setup command to set information about the monitored host for PFM - RM for Platform.

The setting procedure is the same as when a cluster system is not employed.

However, in the case of a cluster system, you must specify the logical host name in the -lhost option when you execute the jpcconf target setup command.

The following shows how to specify the jpcconf target setup command for a cluster system: 

jpcconf target setup -key RMPlatform -lhost logical-host-name -inst instance-name -target monitoring-target-name

This example shows execution in the interactive mode, but you can also execute the jpcconf target setup command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

For details about the settings and procedure, see 3.2.4(4) Setting the monitored host.

To Page Top

(7) Setting up the logical host for other Performance Management programs[Figure] [Figure]

If you have other PFM - Manager, PFM - Agent, or PFM - RM programs to be set up on the same logical host in addition to PFM - RM for Platform, set them up at this stage.

For details about the setup procedure, see the chapter that describes the configuration and operation of cluster systems in the JP1/Performance Management User's Guide.

To Page Top

(8) Setting up a network[Figure] [Figure]

You specify network settings if you need to change the network environment settings as appropriate to the network configuration where Performance Management is used.

The two network environment settings are described below. Change these settings if necessary.

To Page Top

(9) Changing the log file size[Figure] [Figure]

The operation status of Performance Management is output to a log file unique to Performance Management. This log file is called the common message log. This setting is required only when you wish to change this file size.

For details, see the chapter that describes installation and setup in the JP1/Performance Management Planning and Configuration Guide.

To Page Top

(10) Changing the performance data storage locations[Figure] [Figure]

This setting is used to change the storage locations, backup directory, export directory, or import directory for the performance data that is managed by PFM - RM for Platform

For details about the setting method, see 3.6.1 Changing performance data storage locations.

To Page Top

(11) Action log output setting[Figure] [Figure]

This setting is required in order to output action logs in the event of an alarm.

An action log consists of log information about exceeded threshold values caused by factors such as system loading; its output is linked with the alarm function. For details about the setting method, see J. Outputting Action Log Data.

To Page Top

(12) Exporting the logical host environment definition file[Figure]

After you have created a logical host environment for PFM - RM for Platform, export the environment definition to a file.

This export process involves output of the definition information for the Performance Management program that has been 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 definition after all the setup processes are completed.

To export the logical host environment definition:

  1. Execute the jpcconf ha export command to export the logical host environment definition.

    Output the definition information for the logical host environment that has been created so far to an export file. You can assign any name to the export file.

    For example, to export the logical host environment definition to the lhostexp.txt file, execute the following command: 

    jpcconf ha export -f lhostexp.txt

    This example shows execution in the interactive mode, but you can also execute the jpcconf ha export command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

To Page Top

(13) Copying the logical host environment definition file to the standby node[Figure] [Figure]

Copy from the executing node to the standby node the logical host environment definition file exported in (12) Exporting the logical host environment definition file.

To Page Top

(14) Unmounting the shared disk[Figure] [Figure]

Unmount the file system and finish the procedure.

If you will be using the shared disk after you complete this procedure, there is no need to unmount the file system.

Note

If the shared disk is unmounted but the specified environment directory contains the jp1pc directory and that directory has files under it, the setup is performed without unmounting the shared disk.

In such a case, perform the following procedure:

  1. Use the tar command to archive the jp1pc directory that is located in the specified environment directory on the local disk.

  2. Mount the shared disk.

  3. If the specified environment directory does not exist on the shared disk, create an environment directory.

  4. Expand the tar file in the environment directory on the shared disk.

  5. Unmount the shared disk.

  6. Delete all files and directories under the jp1pc directory that is located in the specified environment directory on the local disk.

To Page Top

(15) Importing the logical host environment definition file[Figure]

Import to the standby node the export file that was copied from the executing node.

Use the jpcconf ha import command to specify settings for executing at the standby node the Performance Management program on the logical host that was created at the executing node. If multiple Performance Management programs have been set up on the same logical host, the settings for all the programs are imported in the batch mode.

When you execute this command, there is no need to keep the shared disk mounted.

To import the logical host environment definition file:

  1. Execute the jpcconf ha import command to import the logical host environment definition.

    Execute the following command:

    jpcconf ha import -f lhostexp.txt

    This example shows execution in the interactive mode, but you can also execute the jpcconf ha import command in the non-interactive mode. For details about this command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

    This command changes settings in such a manner that the environment for the standby node becomes the same as for the export file. As a result, the setup for starting PFM - RM for Platform on the logical host is performed.

    If a fixed port number has been set by the jpcconf port define command during the setup, it is also set in the same manner.

  2. Execute the jpcconf ha list command to check the logical host settings.

    Execute the following command:

    jpcconf ha list -key all

    Make sure that the displayed information is the same as when the jpcconf ha list command is executed at the executing node

To Page Top

(16) Registering PFM - RM for Platform into the cluster software[Figure] [Figure]

To run a Performance Management program in a logical host environment, you must register the program into the cluster software and set up the environment in such a manner that the Performance Management program is started and terminated from the cluster software.

For details about how to register PFM - RM for Platform into the cluster software, see the cluster software documentation.

This subsection describes the settings for registering PFM - RM for Platform into the cluster software.

When applications are registered into the UNIX cluster software, the following four items are typically required: Start, Stop, Operation monitoring, and Forced stop.

The following table shows how to set these items in PFM - RM for Platform.

Table 5‒4: How to control a PFM - RM for Platform that is registered into the cluster software

No.

Item

Description

1

Start

Execute the following commands in the order shown to start PFM - RM for Platform:

  1. jpcspm start -key AH -lhost logical-host-name

  2. jpcspm start -key RMPlatform -lhost logical-host-name -inst instance-name

The time to do this is after the shared disk and logical IP address become available.

2

Stop

Execute the following commands in the order shown to terminate PFM - RM for Platform:

  1. jpcspm stop -key RMPlatform -lhost logical-host-name -inst instance-name

  2. jpcspm stop -key AH -lhost logical-host-name

The time to do this is before the shared disk and logical IP address become unavailable.

If the service has stopped for a reason such as a failure, the jpcspm stop command returns a value of 3. In such a case, the processing is treated as a normal termination because the service has stopped.

If the cluster software uses the return value to determine the execution result, take appropriate action, such as setting the return value to 0.

3

Operation monitoring

Execute the ps command to check whether the indicated process is running:

  • ps -ef | grep "process-name logical-host-name" | grep -v "grep monitoring-target-process"

The monitoring-target processes are as follows:

  • jpcagt7, agt7/jpcsto, jpcah

For process names, see the chapter that describes planning and operation in a cluster system in the JP1/Performance Management User's Guide.

Note that a process might have been stopped temporarily during Performance Management operation for a reason such as the need to perform system maintenance. To prepare for this, we recommend that you provide a method for suppressing operation monitoring (for example, monitoring is not to be performed when the system detects a file that indicates that system maintenance is underway).

4

Forced stop

If forced termination is necessary, execute the following command:

  • jpcspm stop -key all -lhost logical-host-name -kill immediate

You can specify only all as the service key in the -key option.

Note

If you execute this command, all Performance Management processes in the specified logical host environment are terminated forcibly by SIGKILL transmission. In this case, the Performance Management processes are terminated forcibly in units of logical hosts, not services.

Specify the settings so that forced termination is used only when processes cannot be terminated by normal termination.
Notes:

  • The Performance Management programs registered in the cluster are started and terminated by the cluster. Therefore, do not set automatic startup at the time of OS startup.

  • If you execute Performance Management programs in a Japanese language environment, use the script registered in the cluster software to set up the LANG environment variable before executing Performance Management commands.

  • If the cluster software uses the return value of a command to determine the execution result, specify the settings so that the return value of the Performance Management commands is converted to a value that can be handled by the cluster software. For details about the return values of Performance Management commands, see each command reference.

  • The length of the text that can be displayed by the ps command depends on the OS. Set the text so that the total length of the logical host name and the instance name does not exceed 47 characters. If you want to use the ps command to monitor actions, execute the ps command in advance to make sure that the entire logical host name is displayed up to the end. Specify the settings so that if the displayed text is not complete, monitoring will apply based on the displayed characters. When you use the ps command to identify a specific process name and a logical host name, the command might fail to acquire a process name or a logical host name. If this occurs, the text might be displayed inside square brackets ([]). Check the reference for the ps command for your OS, and then re-execute the command.

  • Start the monitored host first, and then start PFM - RM for Platform. During termination, terminate PFM - RM for Platform first, and then terminate the monitored host.

To Page Top

(17) Checking start and stop from the cluster software[Figure] [Figure]

Make sure that the Performance Management programs function normally by starting and terminating the programs from the cluster software at each node.

To Page Top

(18) Setting up an environment in the cluster system[Figure] [Figure]

After you have finished setting up the Performance Management programs, set up an environment for them so that PFM - Web Console can be used to display the monitoring target's operation status as a report according to the operating procedures and can send notifications to the user in the event of problems at the monitoring target.

For details about how to set up an environment for the Performance Management programs, see the chapter that describes the configuration and operation of cluster systems in the JP1/Performance Management User's Guide.

To Page Top

Copyright (C) 2019, 2020, Hitachi, Ltd.

Copyright (C) 2019, 2020, Hitachi Solutions, Ltd.