B.7.4 Example of the Cluster system (Mutual 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 the /etc/hosts file.

192.168.80.1    hosta    # HOST-A Virtual IP
192.168.80.2    hostb    # HOST-B Virtual IP
192.168.80.3    host1    # HOST-A/B Virtual IP (Takeover virtual IP)
192.168.80.4    host2    # HOST-A/B Virtual IP (Takeover virtual IP)
192.168.80.100  swhub1   # Primary HUB IP
192.168.80.101  swhub2   # Secondary HUB IP

1-2) Edit the /etc/sysconfig/network-scripts/ifcfg-ethX (X is 0,1) file as follows.

For RHEL7

Contents of /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
BOOTPROTO=static
HOTPLUG=no
ONBOOT=yes
DEVICETYPE=hanet

Contents of /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
BOOTPROTO=static
HOTPLUG=no
ONBOOT=yes
DEVICETYPE=hanet

For RHEL8 or later
- Contents of /etc/sysconfig/network-scripts/ifcfg-eth0
  TYPE=Ethernet BOOTPROTO=none DEVICE=eth0 ONBOOT=yes
- Contents of /etc/sysconfig/network-scripts/ifcfg-eth1
  TYPE=Ethernet BOOTPROTO=none DEVICE=eth1 ONBOOT=yes

2) Creating a virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m v -t eth0,eth1

3) Setting an IP address and a subnet mask

Define an IP address or a subnet mask in the /etc/sysconfig/network-scripts/ifcfg-sha0 file.

For RHEL7

Contents of /etc/sysconfig/network-scripts/ifcfg-sha0

DEVICE=sha0
IPADDR=192.168.80.1
NETMASK=255.255.255.0
BOOTPROTO=static
ONBOOT=yes
DEVICETYPE=sha
HOTPLUG=no

For RHEL8 or later

Contents of /etc/sysconfig/network-scripts/ifcfg-sha0

DEVICE=sha0
IPADDR=192.168.80.1
PREFIX=24
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet

4) Setting the network monitoring function

/opt/FJSVhanet/usr/sbin/hanetpathmon target -n sha0 -p 192.168.80.100,192.168.80.101

5) Setting a subnet mask of the takeover virtual interface

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

6) Creating takeover virtual interfaces

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

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

7) 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 the /etc/hosts file. Defined content is same as HOST-A.

1-2) Edit the /etc/sysconfig/network-scripts/ifcfg-ethX (X is 0,1) file. Defined content is same as HOST-A.

2) Creating a virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m v -t eth0,eth1

3) Setting an IP address and a subnet mask

Define an IP address or a subnet mask in the /etc/sysconfig/network-scripts/ifcfg-sha0 file.

For RHEL7

Contents of /etc/sysconfig/network-scripts/ifcfg-sha0

DEVICE=sha0
IPADDR=192.168.80.2
NETMASK=255.255.255.0
BOOTPROTO=static
ONBOOT=yes
DEVICETYPE=sha
HOTPLUG=no

For RHEL8 or later

Contents of /etc/sysconfig/network-scripts/ifcfg-sha0

DEVICE=sha0
IPADDR=192.168.80.2
PREFIX=24
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet

4) Setting the network monitoring function

/opt/FJSVhanet/usr/sbin/hanetpathmon target -n sha0 -p 192.168.80.100,192.168.80.101

5) Setting a subnet mask of the takeover virtual interface

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

6) Creating takeover virtual interfaces

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

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

7) 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.