I noticed that when MSCS failover to its standby cluster member,
ping only timed out for 1 sec (just like MS NLB).
However, sometimes when active / primary member fails over
to the standby node, the active/primary node may not crash nor
So is there certain MSCS related services / processs being stopped
on the primary node & then being started up on the standby node?
If there is, let me know so that we can use Tivoli to monitor.
Tivoli monitoring for ping timeout is not feasible as my client's
Tivoli currently will only alert if there's ping timeout of more
than 5 mins