How to Check and Repair Virtual machine objects in VSAN which are inaccessible state in vCenter.

SSH to VCSA using root credentials.
Type RVC
login using SSO credentials.
Go to localhost>Datacenter>Computers>Cluster>
Type : vsan.check_state . -r -e
This will recover inaccessible state vm's in VSAN datastore.

 

Free self-paced eLearning from VMware

Free self-paced eLearning from VMware

https://mylearn.vmware.com/mgrReg/plan.cfm?plan=33611&ui=www_edu

Virtual machines can be in any one of four high-level CPU States

Wait: This can occur when the virtual machine's guest OS is idle (waiting for work), or the virtual machine could be waiting on vSphere tasks.  Some examples of vSphere tasks that a vCPU may be waiting on include waiting for I/O to complete or waiting for ESX level swapping to complete. These non-idle vSphere system waits are called VMWAIT.
Ready (RDY): A CPU is in the Ready state when the virtual machine is ready to run but unable to run because the vSphere scheduler is unable to find physical host CPU resources to run the virtual machine on. One potential reason for elevated Ready time is that the VM is constrained by a user-set CPU limit or resource pool limit, reported as max limited (MLMTD).
CoStop (CSTP): Time the vCPUs of a multi-vCPU virtual machine spent waiting to be co-started. This gives an indication of the co-scheduling overhead incurred by the virtual machine.

When investigating a potential CPU issue, there are several counters that are important to analyze

Demand: Amount of CPU  the virtual machine is demanding / trying to use.
Ready: Amount of time the virtual machine is ready to run but unable to because vSphere could not find physical resources to run the virtual machine on
Usage: Amount of CPU the virtual machine is actually currently being allowed to use.

List of most common CPU performance issues

High Ready Time: A CPU is in the Ready state when the virtual machine is ready to run but unable to run because the vSphere scheduler is unable to find physical host CPU resources to run the virtual machine on. Ready Time above 10% could indicate CPU contention and might impact the Performance of CPU intensive application. However, some less CPU sensitive application and virtual machines can have much higher values of ready time and still perform satisfactorily.

High Costop time: Costop time indicates that there are more vCPUs than necessary, and that the excess vCPUs make overhead that drags down the performance of the VM. The VM will likely run better with fewer vCPUs. The vCPU(s) with high costop is being kept from running while the other, more-idle vCPUs are catching up to the busy one.

CPU Limits: CPU Limits directly prevent a virtual machine from using more than a set amount of CPU resources. Any CPU limit might cause a CPU performance problem if the virtual machine needs resources beyond the limit.

Host CPU Saturation: When the Physical CPUs of a vSphere host are being consistently utilized at 85% or more then the vSphere host may be saturated. When a vSphere host is saturated, it is more difficult for the scheduler to find free physical CPU resources in order to run virtual machines.

Guest CPU Saturation: Guest CPU (vCPU) Saturation is when the application inside the virtual machine is using 90% or more of the CPU resources assigned to the virtual machine. This may be an indicator that the application is being bottlenecked on vCPU resource. In these situations, adding additional vCPU resources to the virtual machine might improve performance.

Oversizing VM vCPUs: Using large SMP (Symmetric Multi-Processing) virtual machines can cause unnecessary overhead. Virtual machines should be correctly sized for the application that is intended to run in the virtual machine. Some applications may only support multithreading up to a certain number of threads. Assignment of additional vCPU to the virtual machine may cause additional overhead. If vCPU usage shows that a machine, which is configured with multiple vCPUs and is only using one of them. Then it might be an indicator that the application inside the virtual machine is unable to take advantage of the additional vCPU capacity, or that the guest OS is incorrectly configured.

Low Guest Usage: Low in-guest CPU utilization might be an indicator, that the application is not configured correctly, or that the application is starved of some other resource such as I/O or Memory and therefore cannot fully utilize the assigned vCPU resources.

How to find the ESXi host nic driver/ firmware using command

SSH the ESXi host using putty.
Type ethtool -i vmnic#
displays with nic driver and firmware version.
useful for updating the nic drivers and firmware to latest version.

 

SDDC Upgrade Order

PC: Copied from vmware site:

vSphere 6.7 Pre-Upgrade Considerations

If your upgrading from either vSphere 6.0 or 6.5 to vSphere 6.7 please do pre-upgrade check as given below.

1.ESXi 5.5 hosts must be upgraded to minimum of version 6.0.
2. Virtual Distributed Switches to minimum of version 6.0
3.VMFS-3 Datastore to VMFS-5

vSphere Upgrade Order

vSphere environment components be upgraded in a specific order.

a.All Platform Services Controllers in the SSO domain to 6.7 version.
b.Upgrade/ Migrate vCenter server & vCenter server appliance to 6.7 version.
c.Upgrade VUM (Windows based) to 6.7 version.
d.Upgrade ESXi servers to 6.7 version.

Upgrade order pic from vmware site.