Top
PRIMECLUSTER Global Link Services Configuration and AdministrationGuide 4.6Redundant Line Control Function
FUJITSU Software
Appendix B Examples of configuring system environments > B.10 Example of configuring GS linkage mode > B.10.6 Example of the Cluster system on remote network(1:1 Standby)
PreviousNext

B.10.6 Example of the Cluster system on remote network(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 the GS configuration, refer to GS manual.
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.70.1    host11   # HOST-A Physical IP
192.168.71.1    host12   # HOST-A Physical IP
192.168.70.2    host11   # HOST-B Physical IP
192.168.71.2    host12   # HOST-B Physical IP
192.168.70.12   host111  # HOST-A/B Logical IP
192.168.71.12   host121  # HOST- A/B Logical IP
192.168.90.1    hosta    # HOST-A/B Virtual IP(Takeover virtual IP)
192.168.90.254  virgw    # Virtual gateway
192.168.70.254  rt11     # Router1
192.168.71.254  rt21     # Router2
192.168.80.3    gs11    # GS-1 Physical IP(IP-1)
192.168.81.3    gs12    # GS-1 Physical IP(IP-2)
192.168.80.4    gs21    # GS-1 Physical IP(IP-3)
192.168.81.4    gs22    # GS-1 Physical IP(IP-4)
192.168.82.5    gs31    # GS-1 Physical IP(IP-5)
192.168.83.5    gs32    # GS-1 Physical IP(IP-6)
192.168.82.6    gs41    # GS-1 Physical IP(IP-7)
192.168.83.6    gs42    # GS-1 Physical IP(IP-8)
192.168.91.2    gsa      # GS-1 Virtual IP

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

1-3) Set the route information of the virtual gateway for the remote host's virtual IP address and the route information for the physical IP address in the /etc/sysconfig/network-scripts/route-"interface name" file.

2) Reflecting system setting

3) Setting a subnet mask

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

4) Creating a virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m c -i 192.168.90.1 -t eth0,eth1

5) Setting the Communication target monitoring function

Setting the Remote host monitoring information:

/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.80.3,192.168.71.254+192.168.81.3
/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.80.4,192.168.71.254+192.168.81.4
/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.82.5,192.168.71.254+192.168.83.5
/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.82.6,192.168.71.254+192.168.83.6

Setting the destination cluster node monitoring information and the switches monitoring information:

/opt/FJSVhanet/usr/sbin/hanetobserv create -n HOST-B -i 192.168.90.1 -t 192.168.70.2,192.168.71.2,192.168.70.100,192.168.71.100
Note
When you set the destination cluster node monitoring information and the switches monitoring information, be sure to specify the takeover IP address with the "-i" option.
6) Setting a virtual gateway
/opt/FJSVhanet/usr/sbin/hanetgw create -n sha0 -g 192.168.90.254
7) Creating a takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 -e 192.168.70.12,192.168.71.12
Note
In the cluster configuration, if you want to connect via routers (including LANC2), specify the gateway IP address for the takeover virtual IP address in the "-e" option. Additionally, use the hanetmask command to check that the subnet mask for the gateway IP address has been set.
For RHEL8 or later (not required for RHEL7)
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 the /etc/hosts file. Defined information is the same as for HOST-A.
1-2) Configure the /etc/sysconfig/network-scripts/ifcfg-ethX (X is 0,1) file as follows.
1-3) Set the route information of the virtual gateway for the remote host's virtual IP address and the route information for the physical IP address in the /etc/sysconfig/network-scripts/route-"interface name" file. The information is set in the same way as for HOST-A.
2) Reflecting system setting
3) Setting a subnet mask
/opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.70.0 -m 255.255.255.0
/opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.71.0 -m 255.255.255.0
/opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.90.0 -m 255.255.255.0
4) Creating a virtual interface
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m c -i 192.168.90.1 -t eth0,eth1
5) Setting the Communication target monitoring function
Setting the Remote host monitoring information:
/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.80.3,192.168.71.254+192.168.81.3
/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.80.4,192.168.71.254+192.168.81.4
/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.82.5,192.168.71.254+192.168.83.5
/opt/FJSVhanet/usr/sbin/hanetobserv create -n GS-1 -i 192.168.91.2 -t 192.168.70.254+192.168.82.6,192.168.71.254+192.168.83.6
Setting the destination cluster node monitoring information and the switches monitoring information:
/opt/FJSVhanet/usr/sbin/hanetobserv create -n HOST-A -i 192.168.90.1 -t 192.168.70.1,192.168.71.1,192.168.70.100,192.168.71.100
Note
When you set the destination cluster node monitoring information and the switches monitoring information, be sure to specify the takeover IP address with the "-i" option.
6) Setting a virtual gateway
/opt/FJSVhanet/usr/sbin/hanetgw create -n sha0 -g 192.168.90.254
7) Creating a takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 -e 192.168.70.12,192.168.71.12
Note
In the cluster configuration, if you want to connect via routers (including LANC2), specify the gateway IP address for the takeover virtual IP address in the "-e" option. Additionally, use the hanetmask command to check that the subnet mask for the gateway IP address has been set.
For RHEL8 or later (not required for RHEL7)
8) Reboot
Run the following command to reboot the system.
/sbin/shutdown -r now
[Configuration by RMS Wizard]


1) Configuration of userApplication
After completing the procedure 7) for HOST-A and HOST-B, use the RMS Wizard to set up the cluster environment.
Select the SysNode for HOST-A and HOST-B when creating GLS resources, and then register the created GLS resources with cluster applications.
When registering the GLS resources with the cluster applications, select the SysNode for HOST-A and HOST-B in order of the operation node and the standby node, and then register the takeover IP address "192.168.90.1".
2) Starting of userApplication
After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.
[Router setting]


Set the route information as follows for the virtual IP addresses for Route 1 and Route 2. Make sure that the router neighboring GLS is RIPv1 and the path to GS's virtual IP address is broadcast. How to set the route information depends on the type of router, so read the manual for your router for information on how to set it.
Route1
Destination: 192.168.90.1
Gateway address: 192.168.70.12
Route2
Destination: 192.168.90.1
Gateway address: 192.168.71.12
[GS-1]


Set the information for HOST-A's physical IP address and virtual IP address. For information on how to do this, see the GS manual.
PreviousNext
Copyright FUJITSU LIMITED 2019-2022