PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System)

B.6.7 Example of the Cluster system (1:1 Standby)

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.

If the Standby patrol monitoring function is not used, omit 5) and 8) 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.2    host11  # HOST-A Physical IP
192.168.70.3    host21  # HOST-B Physical IP
192.168.70.100  swhub1  # Primary HUB IP
192.168.70.101  swhub2  # Secondary HUB 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

1-3) Define the subnet mask in /etc/inet/netmasks file.

192.168.70.0    255.255.255.0

2) Reboot

Run the following command to reboot the system. Make sure hme0 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 d -i 192.168.70.1 -e 192.168.70.2 -t hme0,hme1

Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/hostname.hme0.

4) 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

5) 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

6) Creation of takeover virtual interface

/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0

7) Starting the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll on

8) 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) 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

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 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 d -i 192.168.70.1 -e 192.168.70.3 -t hme0,hme1

Ensure that the physical IP address specified using option '-e' is the same IP address configured in /etc/hostname.hme0.

4) 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

5) 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

6) Creation of takeover virtual interface

/opt/FJSVhanet/usr/sbin/hanethvrsc create -n sha0

7) Starting the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll on

8) Starting the Standby patrol monitoring function

/opt/FJSVhanet/usr/sbin/strptl -n sha1

[Configuration by RMS Wizard]

1) Configuration of userApplication

After completing step 8) of both HOST-A and HOST-B, connect to the administration server using RMS Wizard, 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.70.1".

2) Starting of userApplication

After completing the configuration, start the userApplication to activate the takeover virtual interface on the operation node.