If you loose all network connections at the same time, then from a node running VCS it cannot distinguish this from the other node dying, so you can increase timeouts, but this will mean if you loose a node, it will take longer for VCS on the other node to take action. The time you need to change is the LLT peer inactive timeout. I think by fault this is set to 16 seconds, so if you want to change to 20 say, then you would add the following line to %VCS_HOME%\comms\llt\llttab.txt file on each node (set in ms):
set-timer peerinact:20000
and then need to restart LLT - this means stopping VCS, but you can leave apps up:
hastop -all force (on one node)
net stop llt (on all nodes - this will stop all dependent services - gab and VCSComms)
net start had (on all nodes - this will start dependent services - llt, gab and VCSComms)
On VCS for UNIX you can run:
lltconfig -T peerinact: 20000
lltconfig -T query (to check peerinact is set
and this sets it straight away and you add to ltttab so that it is persistent, so this may work in Windows too, but couldn't find this in the Windows VCS admin guide, but it is worth trying if the command works.
I would not advise setting this timeout to 5 mins, as this will effect failover time when a node dies as mentioned earlier - you should instead investigate why all networks can go down together as they should be independent.
Regarding splitbrain, do you mean VMDg depends on IP (IP comes up first) as oppose to IP depends on VMDg - only the former we help to protect against split brain, although if network is down, then online of IP may succeed, even though IP is up on the other node as the IP can't be seen on the network.
Mike