Top
PRIMECLUSTER Global Link Services Configuration and AdministrationGuide 4.3Redundant Line Control Function

D.6.4 Setup example for creating a highly reliable network of guest domains on KVM hosts in a cluster system

This section describes a configuration setup example for the following network configuration.

Make a redundant network on KVM hosts. To link up with the cluster system, install GLS on KVM guests. In addition to the cluster system, select this configuration when consolidating various servers to KVM guests.

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.

[Setting up the KVM host1 and KVM host2]

Setting up GLS is the same as for "D.6.1 Setup example for creating a highly reliable network of guest domains on KVM hosts (Untagged VLAN)". Set up virtual bridges (br0 and br1) on virtual interfaces (sha0 and sha1) on KVM host1.

[Setting up the KVM host1 and KVM host2]

Setting up GLS is the same as for "B.4.13 Example of the Cluster system (NIC non-redundant)". However, you need to change parameters for HUB monitoring. This is to prevent NIC switching mode in KVM guests from detecting an error of the entire communication path before Virtual NIC mode in KVM hosts switches the communication.

The longest detection time in Virtual NIC mode (Link up waiting period of HUB monitoring) < The shortest detection time in NIC switching mode (Error detection time of HUB monitoring)

The table below shows the default values for each mode.

Mode

Item

Setting value

Error detection time

Virtual NIC mode

Link up waiting period

45

47 sec

(3 sec x 15 times + 2 sec)

NIC switching mode

Error detection time

5 x 5

22 sec

(5 x (5 - 1) + 2 sec)

For parameters for HUB monitoring, set the values so that the shortest detection time in NIC switching mode (22 seconds) becomes longer than the longest detection time (47 seconds) in Virtual NIC mode.

For example, to change the parameters for NIC switching mode to 52 seconds, set as follows:

/opt/FJSVhanet/usr/sbin/hanetpoll off
/opt/FJSVhanet/usr/sbin/hanetpoll on -c 11

Mode

Item

Setting value

Error detection time

Virtual NIC mode

Link up waiting period

45

47 sec

(3 sec x 15 times + 2 sec)

NIC switching mode

Error detection time

5 x 11

52 sec

(5 x (11 - 1) + 2 sec)

Point

In Virtual NIC mode, the network monitoring is performed by 5 times at intervals of 3 seconds after starting the operation. However, just after the monitoring started, error detection will be pended until the waiting time for linkup (45 seconds) elapses. Therefore, the longest detection time in Virtual NIC mode is required to be estimated by the linkup waiting time.

[Configuration by RMS Wizard]

1) Configuration of userApplication

After configuring KVM host1 and KVM host2, 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".

2) Starting of userApplication

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