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

G.1 Checkpoint list

Table G.1 Common to all modes

NO

Checkpoint

Description

Check field

1

Network configuration

Check that multiple, non-redundant NICs are not are not connected to the same network.

OK/NG

2

VLAN

Check that the port VLAN and tagged VLAN are connected correctly to network devices.

OK/NG

3

Redundant network configuration

Check whether unnecessary network groups have been created.

OK/NG

4

Firewall settings

If there is a firewall, check whether the filtering has been set correctly.

OK/NG

5

IP address settings

Check that IP addresses are not duplicated on each node. In a cluster configuration, check that the same takeover virtual IP addresses are set on each node.

OK/NG

6

Subnet mask settings

Check that the subnet mask has been set using the "hanetmask" command for the IP address used by GLS.

OK/NG

7

Hotplug settings

Check that the NICs used by GLS have been set to disable the operating system's hotplug function.

OK/NG

8

Hostname settings

If GLS is set using the hostname rather than an IP address, enable the "hostname translation function".

OK/NG

9

Distribution procedure after settings change

If you have changed the GLS settings, you need to distribute the reboot and other settings for operations. Check that the distribution procedure has been performed.

OK/NG

10

Procedure for network device maintenance

If you stop the ping monitoring destination network device for maintenance, GLS may detect a network failure. Also, if a cluster configuration is in use, node failures may occur. When you perform network device maintenance, be sure to check with other persons in charge when you temporarily stop monitoring.

OK/NG

11

Network device rate settings

Check that the rate settings for network devices or server's NICs have been set correctly. If you set auto negotiation and fixed full duplex, any half-duplex and full-duplex communications are mixed, resulting in an unstable communication state.

OK/NG

12

Application

Check that the application to be used is the TCP/IP application using TCP and UDP.

OK/NG

Table G.2 Fast switching mode

NO

Checkpoint

Description

Check field

1

Network address

Check that the network address has been set correctly. The virtual IP addresses of the local system and the target should be the same network addresses.

OK/NG

2

Node configuration

In a cluster configuration, three or more nodes using Fast switching mode are required.

OK/NG

Table G.3 NIC switching mode

NO

Checkpoint

Description

Check field

1

Monitoring destination selection

Check whether the monitoring destination in NIC switching mode is correct. Frequently rebooted servers are not suitable for monitoring destinations.

OK/NG

2

Monitoring time adjustment

If you want to shorten the monitoring time, check that the settings have been made with consideration to the state of applications and monitoring destinations.

OK/NG

3

Network cable

Check that the cables of the primary monitoring destination and secondary monitoring destination are connected to the right switch as monitoring destinations in NIC switching mode.

OK/NG

4

Static route settings

When you set the static route for the NIC switching mode, check that the settings have been made so that the static route is set for both of the interfaces bound by the virtual interface.

OK/NG

Table G.4 Virtual NIC mode

NO

Checkpoint

Description

Check field

1

Interface setting file

Check that the IP addresses or subnet masks are defined in the interface setting file (/etc/sysconfig/network-scripts/ifcfg-shaX) for the virtual interface.

OK/NG

2

Monitoring destination selection

Check whether the monitoring destination in Virtual NIC mode is correct. Frequently rebooted servers are not suitable for monitoring destinations.

OK/NG

3

Monitoring time adjustment

If you want to shorten the monitoring time, check that the settings have been made with consideration to the state of applications and monitoring destinations.

OK/NG

4

Network cable

Check that the cables of the primary monitoring destination and secondary monitoring destination are connected to the right switch as monitoring destinations in Virtual NIC mode.

OK/NG

Table G.5 GS linkage mode

NO

Checkpoint

Description

Check field

1

Network address

Check that the network address has been set correctly. The virtual IP addresses of the local system and the communication target should be different network addresses.

OK/NG

2

Communication target setting

Check that the "hanetobserv" command has been set correctly.

OK/NG

3

Network device settings

When you connect to GS through from GLS via router or LANC2, you need to set the gateway for the virtual IP address of GLS. Also, check that whether the settings have been made so that the device connected to the server used by GLS sends RIPv1.

OK/NG

4

Monitoring time adjustment

If you are monitoring communications for virtual IP addresses with high level applications, adjust the monitoring time so that an error is not detected in less time than GLS needs to switch the network.

OK/NG

5

Maintenance procedure performed while the communication target is stopped

Check the maintenance procedure for shutting down the communication target completely when GLS is used in a cluster configuration. If you restart one cluster node, the other node determines that all networks have failed and a node failure occurs.

OK/NG

6

PTF of the communication target

Check that the PTF needed to connect to GLS has been applied to the GS of the communication target.

OK/NG