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

3.3.2 NIC switching mode

The procedure to add the configuration information using NIC unused in the other virtual interfaces is as follows:

  1. Setup a subnet mask to a virtual IP address using the "hanetmask create" command. For information, see "7.5 hanetmask Command".

  2. Set up a virtual interface using the "hanetconfig create" command. For information, see "7.1 hanetconfig Command".

  3. Set up the standby patrol function using the "hanetconfig create" command (only if the standby patrol function is used). For information, see "7.1 hanetconfig Command".

  4. Set up the HUB monitoring function using the "hanetpoll create" command. For information, see "7.7 hanetpoll Command".

The procedure to share NIC used in a virtual interface of the already defined NIC switching mode and to add the configuration information is as follows (when using a NIC sharing function):

  1. Set a virtual interface with "hanetconfig copy" command. See "7.1 hanetconfig Command" for the detail.

  2. Set standby patrol with "hanetconfig create" command. (Only when using a standby patrol function.) It is not necessary to set if a standby patrol function is already set in a virtual interface that already shares NIC. See "7.1 hanetconfig Command" for the detail.

  3. Set a HUB monitoring function with "hanetpoll copy" command. See "7.7 hanetpoll Command" for the detail.

Note

  • When setting the definition information of NIC switching mode, if virtual interfaces of the other NIC switching modes are already working, already working, it is necessary to stop them once to make the added information valid. Therefore, deactivate GLS temporarily using "stphanet" command and then execute "strhanet" command to restart it. In cluster operation, reactivate a userApplication of NIC switching mode.

  • In NIC switching mode, physical interfaces are activated or deactivated when switching over the transfer path. However, these logs might not be recorded according to the state of the definition. Please refer to "3.2.3 Setting up the system log" for the method of recording these logs.

  • In the cluster environment other than physical IP takeover II, ensure to specify the same IP address configured in "/etc/sysconfig/network-scripts/ifcfg-ethX" when specifying physical IP address by "hanetconfig" command using '-i' or '-e' option. If you specify different physical IP address, it disturbs communication using physical interface because this IP address will overwrite the physical IP address specified with "hanetconfig" command when activating the virtual interface. Do not set any value to IPADDR (IP address) in ifcfg-ethX in the cluster environment with physical IP takeover II.

  • If your HUB is using STP (Spanning Tree Protocol), NIC switching occurs while a failure does not occur on a transmission route. In such a case, it is necessary to tune a monitoring parameter of the HUB monitoring function. See "7.7 hanetpoll Command" or "F.3.3 Switching takes place in NIC switching mode regardless of failure at the monitoring end".

  • It only has to set only one standby patrol function at the composition to which two or more virtual interfaces bundle the same physical interface when tagged VLAN interface is used.

  • When tagged VLAN interface is used, it is not possible to compose like sharing only one from among the bundled physical interface.