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 IP1) 192.168.70.2 host11 # HOST-A Physical IP 192.168.70.3 host21 # HOST-B Physical IP 192.168.71.1 hostb # HOST-A/B Virtual IP (Takeover IP2) 192.168.71.2 host12 # HOST-A Physical IP 192.168.71.3 host22 # HOST-B Physical IP 192.168.70.100 swhub1 # Primary HUB IP 192.168.70.101 swhub2 # Secondary HUB IP 192.168.71.100 swhub3 # Primary HUB IP 192.168.71.101 swhub4 # Secondary HUB IP |
1-2) Configure /etc/sysconfig/network-scripts/ifcfg-ethX (X is 0,1,2,3) file as follows.
For RHEL7
Contents of /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0 BOOTPROTO=static HOTPLUG=no IPADDR=192.168.70.2 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1 BOOTPROTO=static HOTPLUG=no ONBOOT=yes TYPE=Ethernet |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2 BOOTPROTO=static HOTPLUG=no IPADDR=192.168.71.2 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth3
DEVICE=eth3 BOOTPROTO=static HOTPLUG=no ONBOOT=yes TYPE=Ethernet |
For RHEL8 or later
Contents of /etc/sysconfig/network-scripts/ifcfg-eth0
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.70.2
PREFIX=24
DEVICE=eth0
ONBOOT=yes |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth1
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.70.2
PREFIX=24
DEVICE=eth1
ONBOOT=no |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth2
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.71.2
PREFIX=24
DEVICE=eth2
ONBOOT=yes |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth3
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.71.2
PREFIX=24
DEVICE=eth3
ONBOOT=no |
Note
In RHEL8 or later, for the settings (the "/etc/sysconfig/network-scripts/ifcfg-ethX" file) of the physical interfaces bundled by GLS, the definition "HWADDR=<MAC address>" is required.
2) Reflecting system setting
For RHEL7
Run the following command to reboot the system. After rebooting the system, verify eth0 and eth2 are enabled using the ip command.
/sbin/shutdown -r now
For RHEL8 or later
Run the following command and reload the connection profile. After reloading the profile, verify eth0 and eth2 are 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 /opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.71.0 -m 255.255.255.0
4) Creating of 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 /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m d -i 192.168.71.1 -e 192.168.71.2 -t eth2,eth3
Note
Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth2. 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 /opt/FJSVhanet/usr/sbin/hanetpoll create -n sha1 -p 192.168.71.100,192.168.71.101 -b off
6) Setting up the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha2 -m p -t sha0 /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha3 -m p -t sha1
7) Creating of takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 /opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha1
8) Starting the HUB monitoring function
/opt/FJSVhanet/usr/sbin/hanetpoll on
9) Starting the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/strptl -n sha2 /opt/FJSVhanet/usr/sbin/strptl -n sha3
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.
1-2) Configure /etc/sysconfig/network-scripts/ifcfg-ethX (X is 0,1,2,3) file as follows.
For RHEL7
Contents of /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0 BOOTPROTO=static HOTPLUG=no IPADDR=192.168.70.3 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1 BOOTPROTO=static HOTPLUG=no ONBOOT=yes TYPE=Ethernet |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2 BOOTPROTO=static HOTPLUG=no IPADDR=192.168.71.3 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth3
DEVICE=eth3 BOOTPROTO=static HOTPLUG=no ONBOOT=yes TYPE=Ethernet |
For RHEL8 or later
Contents of /etc/sysconfig/network-scripts/ifcfg-eth0
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.70.3
PREFIX=24
DEVICE=eth0
ONBOOT=yes |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth1
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.70.3
PREFIX=24
DEVICE=eth1
ONBOOT=no |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth2
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.71.3
PREFIX=24
DEVICE=eth2
ONBOOT=yes |
Contents of /etc/sysconfig/network-scripts/ifcfg-eth3
HWADDR=<MAC address>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.71.3
PREFIX=24
DEVICE=eth3
ONBOOT=no |
Note
In RHEL8 or later, for the settings (the "/etc/sysconfig/network-scripts/ifcfg-ethX" file) of the physical interfaces bundled by GLS, the definition "HWADDR=<MAC address>" is required.
2) Reflecting system setting
For RHEL7
Run the following command to reboot the system. After rebooting the system verify eth0 and eth2 are enabled using the ip command.
/sbin/shutdown -r now
For RHEL8 or later
Run the following command and reload the connection profile. After reloading the profile, verify eth0 and eth2 are 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 /opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.71.0 -m 255.255.255.0
4) Creating of 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 /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m d -i 192.168.71.1 -e 192.168.71.3 -t eth2,eth3
Note
Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth2. 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 /opt/FJSVhanet/usr/sbin/hanetpoll create -n sha1 -p 192.168.71.100,192.168.71.101 -b off
6) Setting up the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha2 -m p -t sha0 /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha3 -m p -t sha1
7) Creating of takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 /opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha1
8) Starting the HUB monitoring function
/opt/FJSVhanet/usr/sbin/hanetpoll on
9) Starting the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/strptl -n sha2 /opt/FJSVhanet/usr/sbin/strptl -n sha3
8) Reboot
Run the following command to reboot the system.
/sbin/shutdown -r now
[Configuration by RMS Wizard]
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".
After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.
