ExpressCluster X 2.0 for Windows Reference Guide - Nec

Section II Resource details
Monitor resources
Additional Information
When the status of the monitor resource becomes normal from an error, the reactivation count
and failover count are reset to zero (0). When an error is detected next time, the process will be
exactly the same as what has been described up to here. (The description up to here assumed the
interconnect LANs are working properly.)
If all interconnect LANs are disconnected, internal communications with other servers are
blocked. As a result, even if an error is detected on a monitor target, failover of groups fails. To
fail over a group when all interconnect LANs are disconnected, you can choose to shut down the
server where an error is detected. This will allow other servers to detect the server is shut down
and to start failover of the group.
The following is an example of the process when an error is detected while all interconnect
LANs are disconnected.
Configuration example
Interval 30 seconds
Timeout 30 seconds
Retry Count 3 times
Recovery Object Failover Group A
Reactivation Threshold 3 times
Failover Threshold 1
Final Action Stop cluster service and shutdown OS
Reactivation for the recovery target is same as the situation when the interconnect LANs are
working properly. The description begins from the failover on server1, which requires
interconnect LANs.
server1: IP monitor resource 1
Reactivation count 3 times
Failover count zero
Public LAN
(working also as
interconnect)
server1 Interconnect
LAN
server2
Monitor resource
IP monitor
resource 1
FailoverGroup A
Disk resource 1
Application resource 1
Floating IP
resource 1
Shared
disk
When the reactivation count exceeds its
threshold
Monitor resource
IP monitor
resource 1
Disk
Heartbeat
Gateway
Failover of the failover group
A starts but fails because
interconnect LANs are
disconnected, which means
internal communication is
blocked.
“Failover threshold” is a
failover count on a server
basis.
The first failover in server1.
server1: IP monitor resource 1
Reactivation count
times
3
Failover count 1
server2: IP monitor resource 1
Reactivation count Zero
Failover count Zero
When the failover count exceeds its threshold on server1
567