Notes on setting a configuration:
The minimum and maximum number of virtual and logical virtual interface can be defined is 1 to 64.
The number of physical interfaces can be used for redundancy on a single virtual interface is within 1 to 8 for Fast switching, RIP, and GS/SURE 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.
To use all host names and IP addresses used in a Redundant Line Control function, they must be defined in /etc/inet/ipnodes files of the local system.
The system automatically determines the length of MTU for an interface. Nonetheless, it is possible to change the length of MTU using user command execution function. For changing MTU length, refer to "3.6.11 Setting User command execution function". Note that the length of MTU cannot be modified in other redundant modes.
Notes on the operation:
It is not possible to use a multicast IP address in a Redundant Line Control function.
Do not execute a DR linkage function in a machine that runs the cluster operation.
It is not possible to use a Redundant Line Control function under the subnet environment of the variable length. It is not possible to get the route information dynamically under the subnet environment of the variable length because in.routed of Solaris 8 does not support RIP Version2. Set a default gateway and a static route under the subnet environment of the variable length not to activate in.routed. It is not possible to operate under the subnet environment of the variable length in RIP mode and GS/SURE linkage mode because in.routed is used.
Do not operate physical interfaces that a virtual interface bundles with an ifconfig command.
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, 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. Necessary to execute a recovery process such as sending the data by the application itself.
It is not possible to use DHCP (a server function and a client function) as the upper application in a Redundant Line Control function.
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.
Notes on Solaris container
If a zone is activated, an interface in the zone cannot be deactivated.
If you want to change or delete the redundant line control function settings, it is necessary to stop the zone first.
If a virtual interface does not exist in a zone, the zone cannot be activated.
Before starting the zone, activate the virtual interface.
If the zone is started after NIC is switched from the primary interface to the secondary interface in NIC switching mode, it might take up to 20 seconds to enable communication in the zone.
If the zone is set to use the secondary interface in NIC switching mode, a network interface in the zone will automatically be switched to the primary interface when a virtual interface is activated.
An IP address specified for a zone and that for a virtual interface must be different.
If the same IP is specified for both, zone startup or virtual interface activation will fail.
