PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Linux)

B.4.8 Example of the Cluster system in Takeover physical IP address (pattern II)

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 the network configuration other than GLS, refer to "3.2.2 Network 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.

[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) Configure /etc/sysconfig/network-scripts/ifcfg-ethX (X is 0,1) file as follows.

- Contents of /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
BOOTPROTO=static
HWADDR=XX:XX:XX:XX:XX:XX
HOTPLUG=no
BROADCAST=192.168.70.255
IPADDR=192.168.70.1
NETMASK=255.255.255.0
NETWORK=192.168.70.0
ONBOOT=yes
TYPE=Ethernet

- Contents of /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
HWADDR=XX:XX:XX:XX:XX:XX
HOTPLUG=no
ONBOOT=no
TYPE=Ethernet

1-3) On the /etc/sysconfig/network file, define a statement which enables the network configuration.

NETWORKING=yes
NETWORKING_IPV6=no

2) Reboot

Run the following command to reboot the system. After rebooting the system, verify eth0 is enabled using ifconfig command.

/sbin/shutdown -r now

3) Setting a subnet mask

/opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.70.0 -m 255.255.255.0

4) Creating of virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m e -i 192.168.70.1 -t eth0,eth1

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

6) Setting up the Standby patrol monitoring function

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -t sha0

7) Creating of takeover virtual interface

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

8) Starting the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll on

9) 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 content is same as HOST-A.

1-2) Configure /etc/sysconfig/network-scripts/ifcfg-ethX (X is 0,1) file as follows.

- Contents of /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
HWADDR=XX:XX:XX:XX:XX:XX
HOTPLUG=no
ONBOOT=no
TYPE=Ethernet

- Contents of /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
HWADDR=XX:XX:XX:XX:XX:XX
HOTPLUG=no
ONBOOT=no
TYPE=Ethernet

1-3) On the /etc/sysconfig/network file, define a statement which enables the network configuration.

NETWORKING=yes
NETWORKING_IPV6=no

2) Reboot

Run the following command to reboot the system.

/sbin/shutdown -r now

3) Setting a subnet mask

/opt/FJSVhanet/usr/sbin/hanetmask create -i 192.168.70.0 -m 255.255.255.0

4) Creating of virtual interface

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha0 -m e -i 192.168.70.1 -t eth0,eth1

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

6) Setting up the Standby patrol monitoring function

/opt/FJSVhanet/usr/sbin/hanetconfig create -n sha1 -m p -t sha0

7) Creating of takeover virtual interface

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

8) Starting the HUB monitoring function

/opt/FJSVhanet/usr/sbin/hanetpoll on

9) Starting the Standby patrol monitoring function

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

[Configuration by RMS Wizard]

1) Configuration of userApplication

After configuring HOST-A and HOST-B, register the created takeover virtual interface as a Gls resource to create a cluster application. Use RMS Wizard to set up the cluster configuration. For details, see "PRIMECLUSTER Installation and Administration Guide 4.1".

2) Starting of userApplication

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