TOPIC:

Just curious if this looks correct.



I'm creating a new VM on the cluster, and it appears on my second host. (not that it matters to me)

Is it correct to appear like this?

What is a good way for me to test that the cluster is functional? Just pull the management nic on xenserver-two and see if the VM get's migrated?

If you don't choose a home server during VM creation then it could end up on either server (two in your case)
This does not affect anything. There are no restrictions on where to run VMs. You can have VMs running on both hosts at the same time.

Regarding tests, here are a few things to try:

- live migrate the VM
- gracefully shutdown the VM (it should restart within a few seconds after being shut down)
- Pull the power on the host running the VM. There are 2 scenarios here
(1) pull power on slave - VM starts on Master
(2) pull power on master - slave becomes master and starts VM. When former master returns to the pool, it becomes a slave.

Make sure HA is enabled before running your tests.

So I tested this on my Slave, and powered up the second host. It's connected, but doesn't appear in the XenPool as being available.

Management interfaces show as inactive as well.

What am I missing here?

To Clarify, I've cloned the bootable USB to a second USB and tested the boot with that.

The system booted, but the NICs don't appear as being present to XS at all.

OK so after ~5 minutes the original boot device came back with the management NICs and the BOND, and the system shows back up in XenCenter (and Xen Orchestra).

Is there something I've messed up that it takes this long to check the connection?

The bond is a pair of 1-foot Cat 5e cables.

Posting here as well to see if the team on mangolassi.it has any ideas as I'm also needing some support from the hardware vendor on some settings.

Your test procedure is not clear. Regardless, during an HA event your connection to XenCenter will be lost.

If you crash your master, Xencenter will immediately lose its connection to the pool. Once the slave becomes the new master, you could manually reconnect xencenter or wait until xencenter reconnect timeout is reached and it will reconnect automatically. This may be the delay you are seeing.

If you crash your slave, you will also lose your connection to xencenter. You could manually reconnect it a few seconds after it disappears, or wait for the xencenter reconnect timeout which could be several minutes.

So how long is the expected visible downtime that one should expect to see in XenCenter?

Is it normal for the slave in the pool to not display the NICs when configured in a HA pool?