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
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.
Function to be registered |
Description |
---|---|
Start |
Starts JP1/IM - EG for NNMi.
|
Stop |
Terminates JP1/IM - EG for NNMi.
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.
|
Forced stop |
Forcibly terminates JP1/IM - EG for NNMi and releases the current resources.
|
- About restart of JP1
-
In the case of cluster operation, do not restart JP1 by JP1 process management. Restart JP1 by the cluster software.
(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, NNMi and JP1/IM - EG for NNMi, in this order.
-
-
When the logical host terminates
-
Terminate JP1/IM - EG for NNMi, NNMi and JP1/Base, in this order.
-
Release allocation of the shared disk and logical IP address.
-