Comments on: Update: HA Advanced Options

By: hypervisor.fr » Blog Archive » Liens du jour #1

hypervisor.fr » Blog Archive » Liens du jour #1 — Wed, 29 Oct 2008 23:48:16 +0000

[...] HA Advanced Options pour Virtual Center 2.5 U3 [...]

By: Daniel Whittaker

Daniel Whittaker — Tue, 09 Sep 2008 10:58:48 +0000

Dennes: So far as I can tell I am experiencing the following issues with U2:

- HA seems to work fine on a 2 ESX server cluster in the normal sense where if one ESX host is isolated the already-powered-on VMs on that host will automatically power up on the other host. However, I cannot manually power on any VMs on the one remaining host whilst the other host is down, receiving a “Insufficient resources” error pop up box.

- Cannot remember specifically, but I think VMWare increased the requirements for resources and the slot size per vm in U2. This makes having reservations set for resources on your VMs particularly hard to manage if you’re running a decent number of VMs per ESX.

- Finally, although I’m not sure this is particularly a HA issue, when putting an ESX host into Maintenance Mode it will not progress further than 2% as it will not automatically VMotion live VMs over to my remaining host. I have to manually initiate a migration, which completes successfully. Once I’m manually live-migrated the powered-on VMs the Entering Maintenance Mode task continues from where it paused and completes successfully.

If anyone has any insights on these issues, please do respond. They’re driving me a little nuts.

By: Dennes

Dennes — Mon, 08 Sep 2008 08:40:51 +0000

I read in the VMWare forums that supposedly there’s a problem with HA in 3.5 U2 when used in a 2 physical server environment and i was advised to stick to U1. Are you aware of any issues with 3.5 U2?

By: Duncan

Duncan — Wed, 27 Aug 2008 07:02:38 +0000

that’s a great question. have to look into that.

By: Simon Wilson

Simon Wilson — Tue, 26 Aug 2008 09:38:58 +0000

Hi,
Do you know where the parameters are stored?
I’ve typed a duff second network into das.allownetworks and if I try to delete it in VC, it gives the old “object reference not set to and instance of an object” message.

By: Duncan Epping

Duncan Epping — Tue, 12 Aug 2008 22:05:50 +0000

well, das.allowvmotionnetworks is specifically for ESXi. You can’t actually use a dead gateway for this purpose. But you can specify not to use the default gateway and specify a seperate isolation address.

By: Scott

Scott — Tue, 12 Aug 2008 17:07:40 +0000

One question… In my setup we have a deadend switch connecting the 4 ESX servers we have and it is used for vmotion only. Can I use that network even though the vmotion gateway address I put in is not really there (becasue traffic never leaves the switch)?

thanks.

By: Virtualization Short Take #16 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers

Tue, 12 Aug 2008 02:59:25 +0000

[...] at Yellow Bricks has also been pumping out some very helpful information, with an update on HA advanced options and a pointer to a document describing what happens if VirtualCenter [...]

By: Joop van Helvoort

Joop van Helvoort — Fri, 01 Aug 2008 07:39:02 +0000

Hi,

Perfect, HA works again on our cluster. We had one ESX server with a hardware iSCSI card. Since that one server didn’t have a iSCSI network on the console HA kept failing on this machine.

Thank you for your explanation of this option

By: Duncan Epping

Duncan Epping — Fri, 01 Aug 2008 07:20:40 +0000

Thanks Joop,

you can set several networks, in other words:
das.allownetwork0 = service console
das.allownetwork1 = service console 2