PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System) |
Contents
Index
![]() ![]() |
Chapter 2 Feature description | > 2.1 Overview of Functions | > 2.1.3 NIC switching mode |
The ping command is issued periodically to the HUB connected to the NIC currently operating and its response is monitored. Optionally, HUB-to-HUB communication can be monitored.
If a failure is detected in the NIC currently operating, the system switches to the standby NIC and similar monitoring starts from the standby NIC side. Then, if a failure is also detected with the standby NIC, line monitoring stops.
When using a standby patrol function, monitoring starts automatically at the recovery of all transfer routes.
The switching time of a line is represented by [monitoring interval (sec) X monitoring count (count)] (for HUB-to-HUB communication monitoring, this is represented by [monitoring interval (sec) X monitoring count (count) X 2]). The monitoring interval can be set in the range of 1 to 300 seconds and the monitoring count can be set in the range of 1 to 300 times. By default, they are 5 seconds and 5 times respectively.
Even if the ping command failed immediately after started monitoring, it does not regard as a communication line failure until the waiting time (sec) for the Ethernet linkup passed. It is possible to set the waiting time for linkup in a range of 1 to 300 seconds and a default value is 60 seconds. However, if a value is smaller than [monitoring interval (sec) X monitoring count (count)], the time set for linkup is ignored and the time set by this [monitoring interval (sec) X monitoring count (count)] is adopted.
The following failures can be detected:
Because the failures in (1) to (3) appear to be the same failure, it is not possible to determine under which of the four failure types these failures should be classified. Each device has to be checked to make this determination.
The line monitoring in NIC switching mode is automatically started when the system is activated and is automatically stopped when the system is stopped. In cluster operation, the line monitoring of each node is started and stopped independently. It is also possible to start or stop the line monitoring manually using the operational command (hanetpoll command).
Contents
Index
![]() ![]() |