Does anyone have experience configuring drbd with heartbeat between 2 virtual linux machines (VMWare Infrastructure)?
The problem I am running into is that heartbeat likes multiple data paths to see its peer node. For instance, it likes to have a network connection to the peer, maybe one to it's gateway, and a serial cable to its peer - improving the likelihood that when it detects a peer outage, it's actually down, and not due to network congestion or something.
On a virtual machine however, the serial port and ethernet port (and all other ports) are virtual - so really, there's only one data path (correct?)
(I know that VMWare supports physical serial cables between devices, but our vm's are hosted remotely, and physical cables would prevent host migrations, which is not acceptable.)
In our case we are seeing timeouts between the heartbeat peers, even though they are running on the same host machine.
How can I configure drbd / heartbeat to be more robust when running on virtual machines