This section outlines how to organize some of the Systemwalker Operation Manager server subsystems into a cluster configuration.
The following cluster systems support this operation mode:
Solaris version of PRIMECLUSTER
Linux version of PRIMECLUSTER
MC/ServiceGuard
HACMP
1:1 active/standby
The following diagram shows an example of a system in which only Subsystem 1 is used in a cluster configuration, with Node 1 used as the active node and Node 2 used as the standby node. Subsystem 0 is not placed in a cluster configuration and operates on both Node 1 and Node 2. The example in the following diagram illustrates what happens when an error occurs on Node 1. When the error occurs on Node 1, business on Subsystem 1 is transferred to the standby node. Because the business on Subsystem 0 is not in a cluster configuration, it is not affected by the change in the business on Subsystem 1. As long as Subsystem 0 is able to operate on Node 1, it will continue to do so.
When multiple subsystems are operating and only some are organized into a 1:1 active/standby cluster configuration, the configuration is referred to as follows:
1:1 active/standby (with subsystems and partial cluster operation)
The term "1:1 active/standby configuration" includes 1:1 active/standby configurations with subsystems and partial cluster operation as well as the 1:1 active/standby configurations without subsystems and active/standby configurations with subsystems described earlier.
