14.3.7 Configuration for operation in a cluster system
- Organization of this subsection
(1) Configuration for operating JP1/IM - Manager on a cluster system
JP1/IM supports cluster systems. When used in a cluster system, JP1/IM - Manager is failed over to the secondary node when a problem occurs on the primary node, and system monitoring continues without interruption.
An example of a system configuration for using JP1/IM - Manager in a cluster system is shown below.
|
|
![[Figure]](GRAPHICS/CS071100.GIF)
In this configuration, there is a primary server and a secondary server.
JP1/IM - Manager executes on the primary server. The secondary server stands by in case a failure occurs on the primary server. In normal circumstances, JP1/IM - Manager on this server is in stopped state.
For details, see Chapter 7. Operation and Environment Configuration in a Cluster System (for Windows) or Chapter 8. Operation and Environment Configuration in a Cluster System (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide.
(a) Notes
-
When using JP1/IM in a cluster system, do not set up JP1/IM - Manager to restart after abnormal termination. If you need to restart JP1/IM - Manager, do so under the control of the cluster software.
-
When a process management process is activated on a logical host in a cluster configuration, if the logical host's conf folder does not contain an extended startup process definition file, the extended startup process definition file on the physical host is copied.
(2) Configuration for operating JP1/IM - Agent on a cluster system
JP1/IM - Agent supports clustere systems. The following cluster configurations are supported:
-
Shared Disk and Mirror Disk Types
-
Multiple Logical Host Configurations (Active/Active Configuration)
-
Concurrent Operation of Physical Hosts and Logical Hosts
Make sure that JP1/IM - Agent is compatible with the cluster software you are using.
JP1/IM - Agent logical hostname can contain from 1 to 63 characters. Allowed characters are alphanumeric characters, hyphens (-), and periods (.). It can also be specified in FQDN format.
Also, the cluster soft logical host name restrictions must be met. For cluster software limitations, see the cluster software documentation.
Install JP1/IM - Agent on a physical host. For logical hosts, place only definition files, data destinations, and so on, on the shared disk. However, some files are located on the physical host, even for logical hosts.
If you upload a definition file using the definition file manipulation function, JP1/IM - Agent might restart the service after the new definition file is placed. If the contents of the uploaded definition file are invalid, the service will fail to start. If so, restore the definition file and start the service.
To prevent the cluster software from failing over when JP1/IM - Agent service is temporarily stopped, you must set the cluster software service abnormal outage detection time to 1 minute. Please refer to the documentation of the cluster software for the setting method.