Found this issue last week and wanted to note it for future reference for myself (getting old and best way for me to remember as much as anyone:)).
So removed a VM from one of our datastore clusters. Now this machine had an affinity rule applied to it which i wasn’t aware of. Interestingly found i couldn’t remove the rule even wanted to from the datastore cluster.
Turns out the solution was slightly inelegant but it worked.
i) Moved said VM back into the datastore cluster
ii) In the vSphere client (or web) browse to the datastore cluster.
iii) Click the Manage tab and select Settings
iv) Under Configuration, click Rules
v) Pick out your offending rule you want deleted and click Remove and click Ok
Picked up this useful tip from the vCenter Server HA performance and Best Practices guide (see – http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vcha65-perf.pdf)
Will see on Pg 23 it will refer to the fact that:
“As a best practice, it is highly recommended to pick a time period with a very light workload to enable VCHA. Otherwise, the newly cloned Passive node PostgreSQL DB could lag behind too much and not be able to catch up with the Active DB due to transaction logs on the Active DB getting purged on the Active node. We are working on adding archivelog support to address this issue in upcoming releases.”
Sensible advice, might mean weekend work for some folk mind 😦
Although theoretically possible in vSphere 6.0 VM secure boot support only officially supported with vSphere 6.5. Interesting thing with 6.5 is the range of improvements made in the security space with the hypervisor. Been good too that VMware have been listening to the user community in simplifying the adoption of a lot of these features.
An example being VM secure boot support which is easy to setup.
I) Requires EFI firmware support
II) Works for Windows and Linux virtual machines
To setup simply:
i) edit your virtual machine properties
ii) Choose VM Options tab
iii) Make sure EFI is choosen under the Choose which firmware should be used to boot the virtual machine
iv) Tick the tick box beside Secure Boot (EFI boot only) and ok
And your done
Recently came across an issue trying to assign a static IP address to an OVA file. Was going to post it on the VMware communities site but someone had raised a post asking same question. Turns out the fix is a little more involved than assigning one to an OVF file. Good VMWare discussions article came to my (and some other folks’) rescue:
Handy command i found on my travels – vicfg-hostops –
Nifty way to perform operations across all your hosts at the same time (though needless to say be careful too given its power!)
Enhanced Linked Mode enables a single point of management across all vCenter Servers in the same vSphere Single Sign On (SSO) domain. Easier admin results as can look after multiple vCenter instances from one pane.
To enable Enhanced Linked Mode, follow these steps:
- Ensure that Enhanced Linked Mode requirements are met:
- All PSCs are in the same vSphere Single Sign On domain.
- Deploy PSC and vCenter Servers in a supported deployment topology.
Once all enabled all the inventories from your vCenter environments in the same SSO domain will be linked together in Enhanced Link Mode. Can then access all from the vSphere web client (unfortunately not available in the traditional client :()