7.1.2 Physical configuration of the SSO cluster system
The SSO cluster system is based on a two-node cluster consisting of active and standby nodes.
In the SSO cluster system, definition files, database files, and log files are stored on a shared disk. Data is stored in directories on both nodes, and symbolic links are created in these directories. The SSO running on the active node can access the shared disk via the symbolic links.
However, the shared disk cannot be accessed from the standby node. Therefore, SSO cannot be activated on the standby node.
When failover (node switchover) occurs, the SSO that was running on the failed node, which was working as the active node, stops. This node is no longer able to access the shared disk. At this time, the other node becomes the active node and can access the shared disk, and the SSO on this node is activated.
Note that in a cluster system configured by using the default procedure, failover is not triggered by abnormal termination of the SSO process. The setting for using abnormal termination of the SSO process as a trigger to perform failover can be specified in the cluster control script that you create while configuring a cluster system, or in the cluster software. The cluster control script monitors the SSO process.
The subsections below show examples of cluster systems in the following configurations:
-
Basic configuration in an IPv4 network environment
-
Basic configuration in an IPv6 network environment
-
Basic configuration in an IPv4 and IPv6 mixed network environment
-
Distributed configuration in which NNMi is in a cluster configuration and SSO is not
-
Distributed configuration in which NNMi and SSO are in a cluster configuration
- Organization of this subsection
(1) Basic configuration in an IPv4 network environment
The following figure shows an example of a cluster system that is configured with a basic configuration in an IPv4 network environment.
|
|
![[Figure]](GRAPHICS/SS110110.GIF)
In the above configuration, the logical IP address to be specified for the -construction -primary option of the ssoclustersetup command is the IPv4 address of the logical host. When the ssoclustersetup command is executed, values are set for keys in action definition files as shown in the table below. For details about the keys in the action definition files, see 6. Definition Files.
|
Action definition file |
Key name |
Value to be set |
|---|---|---|
|
ssoapmon.def |
change-my-address: |
IPv4 address of the logical host |
|
snmp-address: |
||
|
ssocolmng.def |
change-my-address: |
|
|
ssocollectd.def |
snmp-address: |
|
|
snmp-address-v6: |
(No value is set.) |
|
|
ssorptd.def |
default-disp-address: |
IPv4 address of the logical host |
(2) Basic configuration in an IPv6 network environment
The following figure shows an example of a cluster system that is configured with a basic configuration in an IPv6 network environment.
|
|
![[Figure]](GRAPHICS/SS110112.GIF)
The physical hosts of active and standby nodes must be in an IPv4 and IPv6 dual-stack configuration. In addition, because linkage (communication) with NNMi is based on IPv4, those hosts must have a logical IP address in IPv4 format.
In the above configuration, specify the IPv4 address of the logical host as the logical IP address for the -construction -primary option of the ssoclustersetup command. Specify the IPv6 address of the logical host as the logical IP address for the -defset option of the ssoclustersetup command. When the ssoclustersetup command is executed, values are set for keys in action definition files as shown in the table below. For details about the action definition files, see 6. Definition Files.
|
Action definition file |
Key name |
Value to be set |
|---|---|---|
|
ssoapmon.def |
change-my-address: |
IPv4 address of the logical host |
|
snmp-address: |
||
|
ssocolmng.def |
change-my-address: |
|
|
ssocollectd.def |
snmp-address: |
|
|
snmp-address-v6: |
IPv6 address of the logical host |
|
|
ssorptd.def |
default-disp-address: |
IPv4 address of the logical host |
(3) Basic configuration in an IPv4 and IPv6 mixed network environment
The following figure shows an example of a cluster system that is configured with a basic configuration in an IPv4 and IPv6 mixed network environment.
|
|
![[Figure]](GRAPHICS/SS110114.GIF)
The physical hosts of active and standby nodes must be in an IPv4 and IPv6 dual-stack configuration. In addition, because linkage (communication) with NNMi is based on IPv4, those hosts must have a logical IP address in IPv4 format.
In the above configuration, specify the IPv4 address of the logical host as the logical IP address for the -construction -primary option of the ssoclustersetup command. Specify the IPv6 address of the logical host as the logical IP address for the -defset option of the ssoclustersetup command. When the ssoclustersetup command is executed, values are set for keys in action definition files as shown in the table below. For details about the action definition files, see 6. Definition Files.
|
Action definition file |
Key name |
Value to be set |
|---|---|---|
|
ssoapmon.def |
change-my-address: |
IPv4 address of the logical host |
|
snmp-address: |
||
|
ssocolmng.def |
change-my-address: |
|
|
ssocollectd.def |
snmp-address: |
|
|
snmp-address-v6: |
IPv6 address of the logical host |
|
|
ssorptd.def |
default-disp-address: |
IPv4 address of the logical host |
(4) Distributed configuration in which NNMi is in a cluster configuration and SSO is not
The following figure shows an example of a distributed configuration in which NNMi is in a cluster configuration and SSO is not.
|
|
![[Figure]](GRAPHICS/SS110116.GIF)
When specifying the NNMi connection settings, specify the logical IP address or logical host name for the -host option of the ssonnmsetup command.
In this configuration, the SSO host (monitoring manager) is not clustered. Therefore, you do not need to execute the ssoclustersetup command.
In an IPv6 network environment or an IPv4 and IPv6 mixed network environment, the SSO host (monitoring manager) must also be in an IPv4 and IPv6 dual-stack configuration.
(5) Distributed configuration in which NNMi and SSO are in a cluster configuration
The following figure shows an example of a distributed configuration in which NNMi and SSO are in a cluster configuration.
|
|
![[Figure]](GRAPHICS/SS110117.GIF)
When you execute the ssonnmsetup command to set NNMi connection information, specify the logical IP address or logical host name of NNMi for the -host option.
In a configuration such as the one shown in the preceding figure, the logical IP address to be specified for the -construction -primary option of the ssoclustersetup command is the IP address of the SSO logical host. When the ssoclustersetup command is executed, values are set for keys in action definition files as shown in the table below. For details about the action definition files, see 6. Definition Files.
|
Action definition file |
Key name |
Value to be set |
|---|---|---|
|
ssoapmon.def |
change-my-address: |
IP address of the SSO logical host |
|
snmp-address: |
||
|
ssocolmng.def |
change-my-address: |
|
|
ssocollectd.def |
snmp-address: |
|
|
snmp-address-v6: |
(No value is set.) |
|
|
ssorptd.def |
default-disp-address: |
IP address of the SSO logical host |
In an IPv6 network environment or an IPv4 and IPv6 mixed network environment, the executing (active) and standby monitoring managers must be in an IPv4 and IPv6 dual-stack configuration. Because NNMi cooperation (communication) uses IPv4, a logical IPv4 IP address is required. The logical IP address to be specified for the -defset option of the ssoclustersetup command is the IPv6 logical IP address of SSO. When the ssoclustersetup command is executed, the IPv6 logical IP address of SSO is set for the snmp-address-v6: key in the action definition file (ssocollectd.def).