This section describes an example configuration procedure of the network shown in the diagram below. (Network configuration for not enabling physical interface on a standby node.)
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.
If the Standby patrol monitoring function is not used, omit 4) and 7) in the procedure for setting up on each host.
[HOST-A]
1) Setting up the system
1-1) Define IP addresses and hostnames in /etc/inet/hosts file.
192.168.70.1 hosta # HOST-A/B Virtual IP (Takeover IP) 192.168.70.100 swhub1 # Primary HUB IP 192.168.70.101 swhub2 # Secondary HUB IP |
1-2) Check that nothing is written in /etc/hostname.hme0 file.
1-3) Define the subnet mask in /etc/inet/netmasks file.
192.168.70.0 255.255.255.0 |
2) Creation of virtual interface
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m e -i 192.168.70.1 -t hme0,hme1
Note
Create /etc/hostname.hme0 as an empty file.
If the physical IP address (takeover IP address) is written in /etc/hostname.hme0 to be specified for the option 'i', IP addresses may duplicate when switching the cluster.
3) 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
4) Setting up the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -a 02:00:00:00:00:00 -t sha0
5) Creation of takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0
6) Starting the HUB monitoring function
/opt/FJSVhanet/usr/sbin/hanetpoll on
7) Starting the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/strptl -n sha1
[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) Check that nothing is written in /etc/hostname.hme0 file. Defined information is the same as for HOST-A.
1-3) Define the subnet mask in /etc/inet/netmasks file. Defined content is same as HOST-A.
2) Creation of virtual interface
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m e -i 192.168.70.1 -t hme0,hme1
Note
Create /etc/hostname.hme0 as an empty file.
If the physical IP address (takeover IP address) is written in /etc/hostname.hme0 to be specified for the option 'i', IP addresses may duplicate when switching the cluster.
3) 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
4) Setting up the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -a 02:00:00:00:00:01 -t sha0
5) Creation of takeover virtual interface
/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0
6) Starting the HUB monitoring function
/opt/FJSVhanet/usr/sbin/hanetpoll on
7) Starting the Standby patrol monitoring function
/opt/FJSVhanet/usr/sbin/strptl -n sha1
[Configuration by RMS Wizard]
After completing step 7) of both HOST-A and HOST-B, connect to the administration server using RMS Wizard, then setup the cluster environment.
To create Gls resources, select the SysNode compliant with HOST-A and HOST-B. Once Gls is created, register the two Gls resources on the userApplication.
When registering on the userApplication, select the SysNode compliant with HOST-A and HOST-B in the order of operation node followed by standby node. Then, register the takeover address "192.168.70.1".
After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.
