3.3.2 Registering into the cluster software (in UNIX)

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.