This section describes an example configuration procedure of the network shown in the diagram below.
For configuring the SURE, refer to the SURE 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 /etc/inet/hosts file.
192.168.70.1 host11 # HOST-A Virtual IP(mode:n) 192.168.71.1 host12 # HOST-A Virtual IP(mode:n) 192.168.70.2 host21 # HOST-B Virtual IP(mode:n) 192.168.71.2 host22 # HOST-B Virtual IP(mode:n) 192.168.80.1 hosta # HOST-A/B Virtual IP(mode:c, Takeover virtual IP) 192.168.80.254 virgw # Virtual gateway 192.168.70.3 sure11 # SURE-1 Physical IP(IP-1) 192.168.71.3 sure12 # SURE-1 Physical IP(IP-2) 192.168.70.4 sure13 # SURE-1 Physical IP(IP-3) 192.168.71.4 sure14 # SURE-1 Physical IP(IP-4) 192.168.81.1 surea # SURE-1 Virtual IP |
1-2) 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 192.168.81.0 255.255.255.0 |
2) Creation of virtual interface
2-1) For Solaris 10
# /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m n -i 192.168.70.1 -t fjgi0 # /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha2 -m n -i 192.168.71.1 -t fjgi1 # /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m c -i 192.168.80.1 -t sha1,sha2 |
2-1) For Solaris 11
# /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m n -i 192.168.70.1 -t net0 # /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha2 -m n -i 192.168.71.1 -t net1 # /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m c -i 192.168.80.1 -t sha1,sha2 |
3) Setting the virtual gateway
# /opt/FJSVhanet/usr/sbin/hanetgw create -n sha0 -g 192.168.80.254 |
4) Setting the Communication target monitoring function
# /opt/FJSVhanet/usr/sbin/hanetobserv create -n SURE-1 -i 192.168.81.1 -t 192.168.70.3:1,192.168.71.3:1,192.168.70.4:2,192.168.71.4:2 -m on -r on |
# /opt/FJSVhanet/usr/sbin/hanetobserv create -n HOST-B -i 192.168.80.1 -t 192.168.70.2,192.168.71.2 -m on -r on |
Note
When configuring standby node monitoring information, it is necessary to specify the takeover IP address for '-i' option.
5) Creation of takeover virtual interface
# /opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 |
[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) Define the subnet mask in /etc/inet/netmasks file. Defined content is same as HOST-A.
2) Creation of virtual interface
2-1) For Solaris 10
# /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m n -i 192.168.70.2 -t fjgi0 # /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha2 -m n -i 192.168.71.2 -t fjgi1 # opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m c -i 192.168.80.1 -t sha1,sha2 |
2-1) For Solaris 11
# /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m n -i 192.168.70.2 -t net0 # /opt/FJSVhanet/usr/sbin/hanetconfig create -n sha2 -m n -i 192.168.71.2 -t net1 # opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m c -i 192.168.80.1 -t sha1,sha2 |
3) Setting the virtual gateway
# /opt/FJSVhanet/usr/sbin/hanetgw create -n sha0 -g 192.168.80.254 |
4) Setting the Communication target monitoring function
# /opt/FJSVhanet/usr/sbin/hanetobserv create -n SURE-1 -i 192.168.81.1 -t 192.168.70.3:1,192.168.71.3:1,192.168.70.4:2,192.168.71.4:2 -m on -r on |
# /opt/FJSVhanet/usr/sbin/hanetobserv create -n HOST-A -i 192.168.80.1 -t 192.168.70.1,192.168.71.1 -m on -r on |
Note
When configuring active node monitoring information, it is necessary to specify the takeover IP address for '-i' option.
5) Creation of takeover virtual interface
# /opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0 |
[Configuration by Cluster Admin View]
After completing step 4) of both HOST-A and HOST-B, connect to the administration server using Cluster Admin View, then setup the cluster environment.
To create Gls resource, select the SysNode for HOST-A and HOST-B. Once Gls is created, register it 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.80.1".
After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.
