This section describes an example configuration procedure of the network shown in the diagram below.
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/inet/hosts file.
192.168.70.1 host11 # HOST-A Physical IP (1) 192.168.71.1 host12 # HOST-A Physical IP (2) 192.168.80.1 hosta # HOST-A Virtual IP 192.168.70.2 host21 # HOST-B Physical IP (1) 192.168.71.2 host22 # HOST-B Physical IP (2) 192.168.80.2 hostb # HOST-B Virtual IP 192.168.70.3 host31 # HOST-C Physical IP (1) 192.168.71.3 host32 # HOST-C Physical IP (2) 192.168.80.3 hostc # HOST-C Virtual IP 192.168.80.4 hosta1 # Takeover virtual IP |
1-2) Write the hostnames defined above in /etc/hostname."interface-name" files. If a file does not exist, create a new file.
Contents of /etc/hostname.hme0
host11 |
Contents of /etc/hostname.hme1
host12 |
1-3) Define the subnet mask in /etc/inet/netmasks file.
192.168.70.0 255.255.255.0 192.168.71.0 255.255.255.0 192.168.80.0 255.255.255.0 |
2) Reboot
Run the following command to reboot the system. Make sure hme0 and hme1 are enabled as IPv4 interfaces after rebooting the system.
/usr/sbin/shutdown -y -i6 -g0
3) Creation of virtual interface
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m t -i 192.168.80.1 -t hme0,hme1
4) Creation of takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 -i 192.168.80.4
[HOST-B]
1) Setting up the system
1-1) Define IP addresses and hostnames in /etc/inet/hosts file. Defined information is the same as for HOST-A.
1-2) Write the hostnames defined above in /etc/hostname."interface-name" files. If a file does not exist, create a new file.
Contents of /etc/hostname.hme0
host21 |
Contents of /etc/hostname.hme1
host22 |
1-3) Define the subnet mask in /etc/inet/netmasks file. Defined content is same as HOST-A.
2) Reboot
Run the following command to reboot the system. Make sure hme0 and hme1 are enabled as IPv4 interfaces after rebooting the system.
/usr/sbin/shutdown -y -i6 -g0
3) Creation of virtual interface
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m t -i 192.168.80.2 -t hme0,hme1
4) Creation of takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 -i 192.168.80.4
[HOST-C]
1) Setting up the system
1-1) Define IP addresses and hostnames in /etc/inet/hosts file. Defined information is the same as for HOST-A.
1-2) Write the hostnames defined above in /etc/hostname."interface-name" files. If a file does not exist, create a new file.
Contents of /etc/hostname.hme0
host31 |
Contents of /etc/hostname.hme1
host32 |
1-3) Define the subnet mask in /etc/inet/netmasks file. Defined content is same as HOST-A.
2) Reboot
Run the following command to reboot the system. Make sure hme0 and hme1 are enabled as IPv4 interfaces after rebooting the system.
/usr/sbin/shutdown -y -i6 -g0
3) Creation of virtual interface
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m t -i 192.168.80.3 -t hme0,hme1
4) Creation of takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 -i 192.168.80.4
[Configuration by RMS Wizard]
After completing step 4) of both HOST-B and HOST-C, connect to the administration server using RMS Wizard, then setup the cluster environment.
To create Gls resources, select the SysNode compliant with HOST-A, HOST-B, and HOST-C. Once Gls is created, register the two Gls resources on the userApplication.
When registering on the userApplication, select the SysNode compliant with HOST-A, HOST-B, and HOST-C in the order of operation node followed by standby node. Then, register the takeover address "192.168.80.4".
After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.
