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

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

This section describes an example configuration procedure of the network shown in the diagram below.

The xx, yy in the figure below are assigned automatically by the automatic address 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.

If the Standby patrol monitoring function is not used, omit 5) and 8) in the procedure for setting up on each host.

When using IPv6 address as a takeover virtual interface, it may take around 30 seconds to recover the communication after switching the node. In order to hold a communication instantly, start IPv6 routing daemon beforehand on both operating and standby nodes. For details on this issue, refer to "D.2 Trouble shooting".

An example of configuring /etc/inet/ndpd.conf to use Solaris server as an IPv6 router is described below:
For details on /etc/inet/ndpd.conf, refer to the Solaris manual.

ifdefault AdvSendAdvertisements true  # Every interface sends a router advertisement.
prefix fec0:1::0/64 hme0              # hme0 sends Prefix "fec0:1::0/64".

[HOST-A]

1) Setting up the system

1-1) Create /etc/hostname6.hme0 file as an empty file.

1-2) Define IP addresses and hostnames in /etc/inet/ipnodes file.

fec0:1::1       v6hosta         # HOST-A/B Takeover virtual IP
fec0:1::100     swhub1          # Primary HUB IP
fec0:1::101     swhub2          # Secondary HUB IP

2) Reboot

Run the following command to reboot the system. Make sure hme0 are enabled as IPv6 interfaces after rebooting the system.

/usr/sbin/shutdown -y -i6 -g0

3) Creation of virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create inet6 -n sha0 -m d -i fec0:1::1/64 -t hme0,hme1

4) Setting up the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll create -n sha0 -p fec0:1::100,fec0:1::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) Create /etc/hostname6.hme0 file as an empty file.

1-2) Define takeover virtual IP addresses and hostnames in /etc/inet/ipnodes file. Defined information is the same as for HOST-A.

2) Reboot

Run the following command to reboot the system. Make sure hme0 are enabled as IPv6 interfaces after rebooting the system.

/usr/sbin/shutdown -y -i6 -g0

3) Creation of virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create inet6 -n sha0 -m d -i fec0:1::1/64 -t hme0,hme1

4) Setting up the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll create -n sha0 -p fec0:1::100,fec0:1::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 Cluster Admin View]

1) Configuration of userApplication

After completing step 8) 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 compliant with 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 "fec0:1::1".

2) Starting of userApplication

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