Top
PRIMECLUSTER Global Link Services Configuration and AdministrationGuide 4.7Redundant Line Control Function

B.2.8 Example of the Cluster system (1:1 Standby)

This section describes an example configuration procedure of the network shown in the diagram below.

For the network configuration other than GLS, refer to "3.2.2 Network configuration".
For configuring the cluster system, refer to the Cluster system manual.
In this section, description of private LAN is omitted.
The dotted line indicates that the interface is inactive.

[HOST-A]

1) Setting up the system

1-1) Define IP addresses and hostnames in /etc/hosts file.

192.168.70.1    hosta   # HOST-A/B Virtual IP (Takeover IP address)
192.168.70.2    host11  # HOST-A Physical IP
192.168.70.3    host21  # HOST-B Physical IP
192.168.70.100  swhub1  # Primary HUB IP
192.168.70.101  swhub2  # Secondary HUB IP

2) Reflecting system setting

Run the following command and reload the connection profile. After reloading the profile, verify eth0 is enabled using the ip command.

/usr/bin/nmcli connection reload

3) Setting a subnet mask

/opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.70.0 -m 255.255.255.0

4) Creating a virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m d -i 192.168.70.1 -e 192.168.70.2 -t eth0,eth1

Note

Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/sysconfig/network-scripts/ifcfg-ethX in RHEL8 or in the "nmcli connection modify" command in RHEL9. In RHEL8 or later, to correct mismatch of IP addresses, GLS automatically rewrites the configuration of the connection profile based on the IP address specified in the GLS command.

5) Setting up the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll create -n sha0 -p 192.168.70.100,192.168.70.101 -b off

6) Setting up the Standby patrol monitoring function

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -t sha0

7) Creating a takeover virtual interface

/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0

8) Reboot

Run the following command to reboot the system.

/sbin/shutdown -r now 

[HOST-B]

1) Setting up the system

1-1) Define IP addresses and hostnames in /etc/hosts file. Defined content is same as HOST-A.

2) Reflecting system setting

Run the following command and reload the connection profile. After reloading the profile, verify eth0 is enabled using the ip command.

/usr/bin/nmcli connection reload

3) Setting a subnet mask

/opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.70.0 -m 255.255.255.0

4) Creating a virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m d -i 192.168.70.1 -e 192.168.70.3 -t eth0,eth1

Note

Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/sysconfig/network-scripts/ifcfg-ethX in RHEL8 or in the "nmcli connection modify" command in RHEL9. In RHEL8 or later, to correct mismatch of IP addresses, GLS automatically rewrites the configuration of the connection profile based on the IP address specified in the GLS command.

5) Setting up the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll create -n sha0 -p 192.168.70.100,192.168.70.101 -b off

6) Setting up the Standby patrol monitoring function

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -t sha0

7) Creating a takeover virtual interface

/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0

8) Reboot

Run the following command to reboot the system.

/sbin/shutdown -r now

[Configuration by RMS Wizard]

1) Configuration of userApplication

After configuring HOST-A and HOST-B, register the created takeover virtual interface as a Gls resource to create a cluster application. Use RMS Wizard to set up the cluster configuration. For details, see "PRIMECLUSTER Installation and Administration Guide".

2) Starting of userApplication

After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.