HA Advanced Optiopns not active after vCenter restart

[GreyhoundHH]

Hi,

we're running our clusters with fixed slot-sizes, so we've specified these HA's Advanced Options:

das.slotcpuinmhz

das.slotmeminmb

das.vmcpuminmhz

das.vmmemoryminmb

These are working as long as the vCenter is not beeing restarted. After the restart that slotsizes are being calculated automatically again as by default.

If we then change one value and save the settings, the slot sizes are fixed again.

Anyone having an idea why this happens and why the settings don't remain active?

Kind regards

[vmroyale]

Note: Discussion successfully moved from VMware vCenter™ Server to Availability: HA & FT

[marcelo_soares]

Check if the configurations are being stored on the vpxd.cfg file. Example:

<vpxd>

<das>

<slotCpuMinMHz>256</slotCpuMinMHz>

</das>

</vpxd>

Try also to leave all in case-sensitive strings. This file should be stored at:

%ALLUSERPROFILE%\Application Data\VMware\VMware VirtualCenter\vpxd.cfg

[GreyhoundHH]

There's no <das></das> section in our vpxd.cfg. Does it really have to be stored there as this is a per-cluster setting...

I mean, wehen we restart the vCenter and take a look at the HA Advanced Options, theses values are still there, they are just not activated.

[marcelo_soares]

Can't answer this, but try to specify the configuration on the vpxd.cfg file to check if this works.

[admin]

The HA advanced options are stored in the VC database, not in the vpxd.cfg file. What version + build of vCenter are you using?

[GreyhoundHH]

We're running vCenter 5.1 Bulid 799731. We haven't updated to Update 1 yet....

[admin · Accepted solution]

I checked the code and this looks like a product bug. I'll file a bug report about this.

Thanks,

Elisha

[GreyhoundHH]

OK, thanks for that.

Is this issue maybe already fixed in Update 1?

[admin]

No, this bug exists on all released vCenter versions.