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

3.4.4 GS linkage mode

This section describes how to change the settings for GS linkage mode. After changing the settings, you need to reflect the changes in the operations following some procedures. Note that the change distribution procedures vary depending on the command used for changing the settings, and whether the settings were changed in a single system configuration (no cluster is used), or a cluster configuration.

Reflection Procedure

hanetconfig command

Single

Cluster

IP address to be assigned for the virtual (-i)

1

2

Virtual interface (-n)

1

2

Physical interface (-t)

1

2

hanetgw command

Single

Cluster

IP address for the virtual gateway (-g)

1

2

hanethvrsc command

Single

Cluster

Gateway address for the takeover virtual interface (-e)

-

2

hanetmask command

Single

Cluster

Subnet mask. (-m)

1

1

hanetoberv command

Single

Cluster

Virtual IP address of the communication target (-i)

3

2

Physical IP address of the communication target (-t)

3

2

Monitoring period (-s)

4

4

The number of monitoring (-c)

4

4

Monitoring period for recovery (-b)

4

4

Cluster switching (-f)

-

4

Link up waiting period (-p)

4

4

hanetparam command

Single

Cluster

Hostname resolution (-h)

4

4

Network configuration of OS

Single

Cluster

Network configuration file (/etc/sysconfig/network-scripts/ifcfg-ethX, /etc/sysconfig/network), hosts file(/etc/hosts) etc.

5

5


Procedure 1

Perform one of the following procedures after changing settings.

Procedure 2

Perform one of the following procedures after changing settings.

Procedure 3

Perform one of the following procedures after changing settings.

Procedure 4

Changed settings are immediately reflected to the operation after executing the command to change settings. No reflection procedure is required.


Procedure 5

If you modified the network configuration file for the operating system, you must reboot the system instead of manually restarting the network service (/etc/init.d/network restart, service network restart).

Changing Procedure

The following shows the procedure for changing configuration information for GS linkage mode:

  1. Inactivate the target virtual interface using the "stphanet" command. For detail, see Section "7.3 stphanet Command".

  2. Change the configuration information.

  3. Reboot the system.
    (Note: restarting the HUB monitoring function with "hanetpoll off/on" enables a change made on the monitoring interval, the number of times for monitoring, the monitoring recovery interval, the waiting time for a link up, or the waiting time for cluster switching.)

The following is a list of the information that can be changed for GS linkage mode. No information can be changed besides the information listed below. Delete the concerned definition and add it again.

[Example 1]

The following shows the procedure for changing the IP address of the communication target of the virtual interface in cluster operation.

  1. Check the setting.

    # /opt/FJSVhanet/usr/sbin/hanetobserv print
     interval(s)        =   5 sec
     times(c)           =   5 times
     idle(p)            =  60 sec
     repair_time(b)     =   5 sec
     fail over mode(f)  = YES
     Destination Host Virtual Address     (Router Address+)NIC Address
    +----------------+-------------------+--------------------------------+
     GS               192.168.110.10      192.168.10.10,192.168.20.10
                                          192.168.10.11,192.168.20.11
     PQ               192.168.100.20      192.168.10.20,192.168.20.20
  2. Stop the cluster operation.

  3. Change the IP address of the communication target.

    # /opt/FJSVhanet/usr/sbin/hanetobserv delete -n GS -i 192.168.110.10
    # /opt/FJSVhanet/usr/sbin/hanetobserv create -n GS -i 192.168.110.10 -t 192.168.10.20,192.168.20.20
    # /opt/FJSVhanet/usr/sbin/hanetobserv create -n GS -i 192.168.110.10 -t 192.168.10.21,192.168.20.21
  4. Distribute the changes. Because the "IP address of the remote host monitoring" was changed in a cluster configuration, perform a "reboot the system" procedure, or "execute the resethanet -s command" procedure according to Procedure 2. The following is an execution example in which the system is rebooted.

    # /sbin/shutdown -r now