Job Management Partner 1/Integrated Management - Event Gateway for Network Node Manager i Description, User's Guide and Reference

3.3.2 Registering into the cluster software (in UNIX)

This subsection describes how to register JP1/IM - EG for NNMi and JP1/Base on the logical host into the cluster software in a UNIX environment.

Organization of this subsection

(1) Creating scripts to be registered into the cluster software

(2) Setting the resource start and stop sequence

(1) Creating scripts to be registered into the cluster software

When you use UNIX cluster software, you normally create a tool to control applications by a method such as scripts and then you register the scripts into the cluster software. In general, you need scripts to provide the Start, Stop, Operation monitoring, and Forced stop functions.

This subsection describes the JP1/IM - EG for NNMi information that is needed for designing scripts. Use this information to create scripts that control JP1/IM - EG for NNMi according to the cluster software specifications and then register the scripts into the cluster software.

Table 3-3 Detailed information needed for designing scripts for cluster registration

Function to be registered Description

Start Starts JP1/IM - EG for NNMi.

Command to be used
jegn_start.cluster logical-host-name

Command termination timing
The start command waits until JP1/IM - EG for NNMi has started before it terminates itself. However, if startup processing is not completed within the timeout period (60 seconds is the default), the command terminates without completing the startup processing. In such a case, the command terminates with the startup processing still underway (the command does not cancel the startup processing).

Checking the command execution result
You can determine the JP1/IM - EG for NNMi startup result by means of the operation monitoring method described below. Normally, the result is determined by the cluster software's operation monitoring. The return values of the start command are 0 (normal termination) and 1 (argument error); therefore, result details cannot be determined from the return value.

Stop Terminates JP1/IM - EG for NNMi.

Command to be used
jegn_stop.cluster logical-host-name

Command termination timing
The stop command waits until JP1/IM - EG for NNMi has terminated before it terminates itself. However, if stop processing is not completed within the timeout period (60 seconds is the default), the command terminates without completing the stop processing. In such a case, the command terminates with the stop processing still underway (the command does not cancel the stop processing).

Checking the command execution result
You can determine the JP1/IM - EG for NNMi termination result by means of the operation monitoring method described below. The return values of the stop command are 0 (normal termination) and 1 (argument error); therefore, result details cannot be determined from the return value.

We recommend that you execute the forced termination command described below after the stop command has terminated. This enables you to terminate the process and prevent a failover error even in the event of a problem.

Operation monitoring^# Monitors normal operation of JP1/IM - EG for NNMi.
To determine whether JP1/IM - EG for NNMi is running normally, check the return value of the jegn_spmd_status command. This command determines the status from the operating status of each process.
Note that some cluster software does not provide the operation monitoring function. If there is no need to perform failover in the event of a JP1/IM - EG for NNMi failure, you need not register this function.

Command to be used
jegn_spmd_status -h logical-host-name

Checking the result of operation monitoring
The following describes how to interpret the return value:
Return value = 0 (all running):
JP1/IM - EG for NNMi is running normally.
Return value = 1 (error):
An unrecoverable error has occurred. Treat this as an error.
Note:
If you execute the jegn_spmd_status command on the standby server whose shared disk is offline, the return value will be 1 because the shared disk is not available.
Return value = 4 (partially stopped):
Some JP1/IM - EG for NNMi processes are stopped due to a problem. Treat this as an error.
Return value = 8 (all stopped):
The JP1/IM - EG for NNMi processes have all stopped due to a problem. Treat this as an error.
Return value = 12 (retriable error):
While the jegn_spmd_status command was checking the operating status, an error that can be recovered by retries has occurred. Retry checking of the operating status as many times as specified.

Forced stop Forcibly terminates JP1/IM - EG for NNMi and releases the current resources.

Command to be used
The jegn_killall.cluster command forcibly terminates each process without performing JP1/IM - EG for NNMi termination processing.

Note:

Before you execute forced stop, use the stop command to terminate JP1/IM - EG for NNMi.

#

With respect to JP1 operation checking, the same commands are used in both UNIX and Windows, but they function differently.

Windows operation differs from UNIX operation due to its association with Windows service control. In Windows, when any process terminates, JP1 process management automatically terminates all processes and places the service in stopped status. Assume such a service stop is the result of an error or assume an error has occurred when a command such as jegn_spmd_status returns a value of 8.

About restart of JP1

When a JP1 failure is detected during cluster operation, restart of JP1 might be attempted on the same server before failover to the standby server is executed. In such a case, do not allow JP1 process management to attempt restart.

The cluster software attempts restart after detection of a JP1 failure. Depending on the nature of the failure, JP1's restart function might be affected and normal operation might not be achieved. To restart JP1 successfully, use the cluster software to restart JP1.

Function to be registered	Description
Start	Starts JP1/IM - EG for NNMi. Command to be used jegn_start.cluster logical-host-name Command termination timing The start command waits until JP1/IM - EG for NNMi has started before it terminates itself. However, if startup processing is not completed within the timeout period (60 seconds is the default), the command terminates without completing the startup processing. In such a case, the command terminates with the startup processing still underway (the command does not cancel the startup processing). Checking the command execution result You can determine the JP1/IM - EG for NNMi startup result by means of the operation monitoring method described below. Normally, the result is determined by the cluster software's operation monitoring. The return values of the start command are 0 (normal termination) and 1 (argument error); therefore, result details cannot be determined from the return value.
Stop	Terminates JP1/IM - EG for NNMi. Command to be used jegn_stop.cluster logical-host-name Command termination timing The stop command waits until JP1/IM - EG for NNMi has terminated before it terminates itself. However, if stop processing is not completed within the timeout period (60 seconds is the default), the command terminates without completing the stop processing. In such a case, the command terminates with the stop processing still underway (the command does not cancel the stop processing). Checking the command execution result You can determine the JP1/IM - EG for NNMi termination result by means of the operation monitoring method described below. The return values of the stop command are 0 (normal termination) and 1 (argument error); therefore, result details cannot be determined from the return value. We recommend that you execute the forced termination command described below after the stop command has terminated. This enables you to terminate the process and prevent a failover error even in the event of a problem.
Operation monitoring^#	Monitors normal operation of JP1/IM - EG for NNMi. To determine whether JP1/IM - EG for NNMi is running normally, check the return value of the jegn_spmd_status command. This command determines the status from the operating status of each process. Note that some cluster software does not provide the operation monitoring function. If there is no need to perform failover in the event of a JP1/IM - EG for NNMi failure, you need not register this function. Command to be used jegn_spmd_status -h logical-host-name Checking the result of operation monitoring The following describes how to interpret the return value: Return value = 0 (all running): JP1/IM - EG for NNMi is running normally. Return value = 1 (error): An unrecoverable error has occurred. Treat this as an error. Note: If you execute the jegn_spmd_status command on the standby server whose shared disk is offline, the return value will be 1 because the shared disk is not available. Return value = 4 (partially stopped): Some JP1/IM - EG for NNMi processes are stopped due to a problem. Treat this as an error. Return value = 8 (all stopped): The JP1/IM - EG for NNMi processes have all stopped due to a problem. Treat this as an error. Return value = 12 (retriable error): While the jegn_spmd_status command was checking the operating status, an error that can be recovered by retries has occurred. Retry checking of the operating status as many times as specified.
Forced stop	Forcibly terminates JP1/IM - EG for NNMi and releases the current resources. Command to be used The jegn_killall.cluster command forcibly terminates each process without performing JP1/IM - EG for NNMi termination processing. Note: Before you execute forced stop, use the stop command to terminate JP1/IM - EG for NNMi.

(2) Setting the resource start and stop sequence

To execute JP1/IM - EG for NNMi and JP1/Base on the logical host, the shared disk and logical IP address must be available for use.

Set the start and stop sequence or dependencies in such a manner that they are controlled by the cluster software as described below.

When the logical host starts

Allocate the shared disk and logical IP address and make them available for use.

Start JP1/Base and JP1/IM - EG for NNMi, in this order.

When the logical host terminates

Terminate JP1/IM - EG for NNMi and JP1/Base, in this order.

Release allocation of the shared disk and logical IP address.

[Contents][Back][Next]

[Trademarks]