Notes on setting a configuration:
The minimum and maximum number of virtual and logical virtual interface can be defined is 1 to 64 in total.
The number of physical interfaces can be used for redundancy on a single virtual interface is within 1 to 8 for Fast switching mode and GS linkage mode. For NIC switching mode, the range is within 1 to 2.
The number of logical virtual interfaces that can be defined to a single logical virtual interface is within 1 to 63.
The maximum character of physical interface names (VLAN ID is included for tagged VLAN interface) can be bundled by the virtual interface is 11. When using the name of the interface that exceeds 11 characters, shorten the physical interface name. For details on changing the interface name, see "Linux documentation."
The tagged VLAN interface name is available only by "interface name.VLAN-ID" format, such as eth0.1.
Notes on the operation:
Do not operate physical interfaces that a virtual interface bundles with a command such as the ifconfig command or the ip command.
On the system that makes the transfer route redundant by the Redundant line control function, the user must not start, stop, and restart the network service.
The following messages may be output to the console and system log during system startup. This does not disrupt ongoing operation.
For RHEL7
kernel: sha: module license 'Proprietary' taints kernel. kernel: Disabling lock debugging due to kernel taint kernel: sha: module verification failed: signature and/or required key missing - tainting kernel
or
kernel: Request for unknown module key 'FUJITSU Software: Fujitsu BIOS DB FJMW Certificate: Hexadecimal, forty-digit' err -11 kernel: sha: module verification failed: signature and/or required key missing - tainting kernel
For RHEL6
kernel: sha: module license 'Proprietary' taints kernel. kernel: Disabling lock debugging due to kernel taint
Notes on upper applications:
When using TCP in a working application, the data lost when an error occurred in a transfer route is guaranteed by resending from TCP and reaches the other system in the end. Therefore, TCP connection is not disconnected and there is no error in communication. However, it is necessary to set a timer value longer than the time to finish disconnecting/switching a transfer route when an application monitors a response by such as a timer. When TCP connection is disconnected by the reason such as not possible to change a timer value, reestablish the TCP connection and recover the communication.
The data lost at the time of an error in a transfer route is not guaranteed when a working application uses the UDP. It is necessary to execute a recovery process such as sending the data by the application itself.
When using NTP as an upper application, it is necessary to activate an IP address that a Redundant Line Control Function controls before activating an NTP daemon. No special operation is required when activating a system because a Redundant Line Control Function is activated before an NTP daemon. However, when manually activated an IP address with an operation command or when running cluster operation, reactivate an NTP daemon after an IP address is activated. In addition, when using NTP on GLS, a NTP daemon has to be defined to be able to communicate using a logical IP address.
