Define all host names and IP addresses used in a Redundant line Control Function in the /etc/hosts files of the local system.
The length of MTU cannot be modified.
Multicast IP addresses cannot be used.
An IPv6 over IPv4 tunneling interface (sitX) is not supported.
If a user individually activates or deactivates virtual interfaces registered in the cluster, the interface status monitoring feature restores them to their original state on the operation.
It is not possible to use DHCP (a server function and a client function) as the upper application.
If you use GS linkage mode, be sure to set up the remote host monitoring function. For information on how to do this, see "7.15 hanetobserv Command".
If you use GS linkage mode, be sure to set up the virtual gateway. For information on how to do this, see "7.14 hanetgw Command".
GS linkage mode is not available for communications between a Linux server and a Solaris server.
Do not set the same virtual IP address on GS for the communication target, if you set multiple GLS's takeover virtual IP addresses within the same cluster. You can do this between different clusters.
Set a different network address from the virtual IP address of the communication target GS for a virtual IP address in GS linkage mode.
Set the virtual IP addresses used in GS linkage mode to have different network addresses.
When communicating between GLS and GS via router, make sure that the router neighboring GLS is RIPv1 and the path to GS's virtual IP address is broadcast.
When using the remote network communication (communication via router) in GS linkage mode, set the same netmask for the virtual IP addresses of GS and GLS, and physical IP addresses.
When using the neighboring communication (communication without router) in GS linkage mode, setting the same netmask for the virtual IP addresses of GS and GLS, and physical IP addresses is recommended. Use the different netmask for each IP address only under the following conditions:
Length of the netmask of all the physical IPs is consistent.
Length of the netmask of the virtual IP is consistent between the host and the server, and longer than the length of the physical IP.
In GS linkage mode, the tagged VLAN function is not available.
If GS is in the hot-standby configuration, the node that received the down notification by the TNOTIFY command from GS is recognized as the communication target.
If a TNOTIFY command is executed to GLS from GS, GLS returns the processing result 80.
When using the logical virtual IP address of GS linkage mode as a source, it is necessary to fix the logical virtual IP address to be the source on the application side with the bind function.
The interface created by SR-IOV cannot be used.
If the firewalld service is enabled, the virtual interface works in the default zone after the OS is restarted, depending on the OS version.
Check the zone where the virtual interface works by using the firewall-cmd --get-active-zones command.
In a cluster configuration, in order to prevent a failover when all the GSs of communication targets stopped, the information of operation node and standby nodes and neighboring switches needs to be created as the monitoring destination information of the remote host. For information on the creation, see "7.15 hanetobserv Command".
In GS linkage mode, a message is exchanged between the host and the server by using "Fujitsu Hot Standby Protocol". This is the protocol of UDP communication that uses the port number 1807. Set the firewall to allow the communication by this protocol.
