10.1.3 Cluster configurations supported by JP1/AJS3 - Web Console

(1) Prerequisites for a cluster system

The following are the prerequisites for using JP1/AJS3 - Web Console in a cluster system.

1. The cluster software must be able to control prerequisites 2 to 4 below.

2. A shared disk that enables data to pass from the primary node to the secondary node must be available.

   The details are as follows:

   • The shared disk must be allocated before JP1/AJS3 - Web Console start.

   • The shared disk must not be deallocated while JP1/AJS3 - Web Console are running.

   • The shared disk must be deallocated after JP1/AJS3 - Web Console stop.

   • The shared disk must be locked so that it is accessible only from the primary node.

   • The files must be protected by the journal functionality of a file system so that they will not be lost if the system goes down or another problem occurs.

   • In a failover, the integrity of the information written to the files must be assured and that information must be inherited.

   • Forced failover must be possible if a process is using the shared disk.

   • If an error is detected on the shared disk, the cluster software must control recovery measures, which must be transparent to JP1/AJS3 - Web Console. If JP1/AJS3 - Web Console need to be started or stopped in extended recovery measures, the cluster software must issue the start and stop requests to JP1/AJS3 - Web Console.

3. The IP address used in cluster operation must meet the following conditions:

   • Communication must be possible using the IP address used in cluster operation, which can be inherited.

   • The IP address used in cluster operation must be uniquely identified from the host name used in cluster operation.

   • The IP address used in cluster operation must have been assigned before JP1/AJS3 - Web Console is started.

   • The IP address used in cluster operation must not be deleted during execution of JP1/AJS3 - Web Console.

   • The mapping between the host name and IP address used in cluster operation must not be changed during execution of JP1/AJS3 - Web Console.

   • The IP address used in cluster operation must be deleted after JP1/AJS3 - Web Console is stopped.

   • When a network error is detected, the cluster software must control recovery measures, which must be transparent to JP1/AJS3 - Web Console. If JP1/AJS3 - Web Console need to be started or stopped in extended recovery measures, the cluster software must issue the start and stop requests to JP1/AJS3 - Web Console.

4. The host name used in cluster operation must be set in the hosts file or on the name server so that TCP/IP communication is possible.

If the above prerequisites are not satisfied, a problem may occur during operation of JP1/AJS3 - Web Console. For example, the following problems may occur.

• If data written on the primary node is damaged when a failover occurs:

  A problem such as an error, data loss, or start failure occurs and JP1/AJS3 - Web Console cannot operate normally.

• If recovery is not performed even when an error occurs in the NIC:

  A communication error occurs and JP1/AJS3 - Web Console does not operate normally until the cluster software switches over the NIC or performs a failover to the other server occurs.

To Page Top

(2) Supported system configurations

The following are examples of cluster configurations:

If a cluster system is set up for JP1/AJS3 - Web Console and for JP1/AJS3 - Manager independently, they will fail over without affecting each other if a failure occurs.

Therefore, we recommend that you set up JP1/AJS3 - Web Console and JP1/AJS3 - Manager on different cluster systems.

Figure 10‒2: If you set up a cluster by installing JP1/AJS3 - Web Console and JP1/AJS3 - Manager on different hosts

Figure 10‒3: If you separately set up clusters by installing JP1/AJS3 - Web Console and JP1/AJS3 - Manager on the same host

Cautionary note

JP1/AJS3 - Web Console supports active-standby configuration in a cluster configuration, but does not support active-active configuration.

To Page Top