Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Event Gateway for Network Node Manager i


3.3.1 Registering into the cluster software (in Windows)

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

The following table shows the information to be registered into the cluster software.

Table 3‒2: Information to be registered into the cluster software

No.

Name

Service name

Dependency

1

JP1/Base Event logical-host-name

JP1_Base_Event logical-host-name

IP address resource

Physical disk resource

2

JP1/Base logical-host-name

JP1_Base_logical-host-name

Cluster resource of No. 1

3

JP1/IM - EG for NNMi logical-host-name

JP1_IM-EG_for_NNMi_logical-host-name

Cluster resources of NNMi and Nos. 1 and 2

For details about cluster resources of NNMi, see the NNMi manuals.

Organization of this subsection

(1) Registering into the cluster software

Notes
  • About restart of JP1

    In the case of cluster operation, do not restart JP1 by JP1 process management. Restart JP1 by the cluster software.

(a) In MSCS

Register the services of JP1/IM - EG for NNMi and JP1/Base as MSCS resources. Set each resource as described below. Bold typeface indicates the MSCS setting items.

  • For Resource Types, register as Generic Service.

  • Set Name, Dependencies, and Service name as shown in Table 3-2 Information to be registered into the cluster software. Name is used to display the service, and Service name is used to specify the service that is controlled from MSCS.

  • Do not set Start parameters and Registry Replication.

  • Set the Advanced properties page for properties according to whether failover is to occur in the event of a JP1/IM - EG for NNMi failure.

    For example, to set failover to occur in the event of a JP1/IM - EG for NNMi failure, select the Restart and Affect the group check boxes and specify Threshold for the restart retry count, using a value of 3 (times) as a guideline.

(b) When registering the service start and stop commands

Register into the cluster software the services of JP1/IM - EG for NNMi and JP1/Base to be started and stopped. For example, specify the settings so that the services shown in the Name column in Table 3-2 Information to be registered into the cluster software are to be started and stopped by the net command.

You can use the following commands to check the operation of JP1/IM - EG for NNMi and JP1/Base:

  • jegn_spmd_status

    Checks the operation of JP1/IM - EG for NNMi.

  • jbs_spmd_status

    Checks the operation of JP1/Base.

  • jevstat

    Checks the operation of the JP1/Base event service.

For details about the jegn_spmd_status command, see jegn_spmd_status in 7. Commands. For details about the jbs_spmd_status and jevstat commands, see the JP1/Base User's Guide.

(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.