If you're on vSphere 6 and you don't have VUM, something I'd recommend is to upgrade to vSphere 6.5 using the vCenter Server Appliance. This will bring you up to date as well as give you VUM buil...
See more...
If you're on vSphere 6 and you don't have VUM, something I'd recommend is to upgrade to vSphere 6.5 using the vCenter Server Appliance. This will bring you up to date as well as give you VUM built-in to the appliance allowing you to automate the patching of your hosts. Since you have Essentials Plus, you have the ability to vMotion VMs around as part of maintenance, and this is something VUM will do for you.
My mistake. I could have sworn earlier that I'd logged into these. Been a long week, digging into what the previous Systems Admin left behind. Yes, they are both apparently running ESXi 6.0.0
VUM = vSphere Update Manager. What version of vSphere are you running here? Are you using the vCenter Appliance or Windows? If you can speak more to what you have it'll be easier to provide ad...
See more...
VUM = vSphere Update Manager. What version of vSphere are you running here? Are you using the vCenter Appliance or Windows? If you can speak more to what you have it'll be easier to provide advice on how to go about patching it.
Ok, I guess that's a start. Never heard of "VUM", so I'll have to Google that. Meanwhile, can I just login to the physical hosts and patch them the way I do any other server? Same for the VM ru...
See more...
Ok, I guess that's a start. Never heard of "VUM", so I'll have to Google that. Meanwhile, can I just login to the physical hosts and patch them the way I do any other server? Same for the VM running vCenter Server, can I just patch and reboot like any other server?
If you aren't periodically touching your ESXi hosts or vCenter until now with the recent Spectre and Meltdown flaws, I'd strongly recommend you begin to touch them on a regular cadence especially...
See more...
If you aren't periodically touching your ESXi hosts or vCenter until now with the recent Spectre and Meltdown flaws, I'd strongly recommend you begin to touch them on a regular cadence especially if this is in a business environment. Notwithstanding the security vulnerabilities patches regularly address, they also address a large number of stability issues not to mention features. That said, if you're not using VUM that's definitely a way to begin to automate the patching of your ESXi hosts. If you're using the vCenter Server Appliance, patches are even easier to deploy. Whatever methods you choose, you will be in a much better (and safer) position if you incorporate them into your processes.
I generally don't touch the physical hosts or vCenter Server, but recent security scares tell me I need to keep these patched. Is there a recommended way to go about it?
Hi turazw4l I know this post is old, but I'm having the same problem. Any luck on this? I'm working with plink too, putty also possible, I don't mind which one. I can't get it work that c...
See more...
Hi turazw4l I know this post is old, but I'm having the same problem. Any luck on this? I'm working with plink too, putty also possible, I don't mind which one. I can't get it work that command shutdown sc both is executed via script. Would be great to have a solution on this. Thanks in advance Rgds
Answer is 'it depends'! Hot plug and vNUMA are mutually exclusive. vNUMA optimises the scheduling of vCPUs on physical cores, if there are more vCPUs in a VM than exists within a physical CPU soc...
See more...
Answer is 'it depends'! Hot plug and vNUMA are mutually exclusive. vNUMA optimises the scheduling of vCPUs on physical cores, if there are more vCPUs in a VM than exists within a physical CPU socket, vNUMA will make sure they are scheduled in the most efficient way - same goes for memory which is assigned to a 'local' CPU E.g. you have 256GB memory in a 2 CPU socket system then you have 128GB per channel. If you have a VM with more than 128GB it is a wide VM and can benefit from vNUMA. If you enable hot plug then this will be disabled, if you have smaller VMs you won't notice. If you have larger VMs you may not even notice depending on the utilisation of your environment and what is running on the VMs. It often comes down to a trade off between what is most important and what is best from an operational perspective too. Also just because the VM supports hot plug does not mean the OS/App does e.g. in the case of certain DB software... Ps Frank Dennenman explains it a lot better than I can - Impact of CPU Hot Add on NUMA scheduling - frankdenneman.nl
Hi, need to know that if someone has the knowledge of the impact on the VMware if we turn on the CPU and Memory hotplug enabled on all of our VMs? will it slow it down? does it takes more ...
See more...
Hi, need to know that if someone has the knowledge of the impact on the VMware if we turn on the CPU and Memory hotplug enabled on all of our VMs? will it slow it down? does it takes more resources than to have it disabled? any input is highly appreciated thanks
I can also recommend XIA. It detects my vCenter servers and virtual machines automatically, I can then automatically generate documentation for both VMware and my virtual machines. Here's a l...
See more...
I can also recommend XIA. It detects my vCenter servers and virtual machines automatically, I can then automatically generate documentation for both VMware and my virtual machines. Here's a link direct to their VMware page: https://www.centrel-solutions.com/xiaconfiguration/capabilities.aspx?capability=vmwaresystem