KB63: SMALL CLUSTER

Troubleshooter is reporting an alert because some clusters in the farm have too few hosts (less than 5) The best practice is to have few clusters with many hosts, in order to make the best use of Eco4Cloud Workload Consolidation … Continue reading

KB45: BALLOONED MEMORY OVER 5 PERCENT

By this error, Troubleshooter reports that VM and Host performances are highly degraded because of high memory ballooning. Virtual memory ballooning is a computer memory reclamation technique used by a hypervisor to allow the physical host system to retrieve unused memory … Continue reading

KB46: BALLOONED MEMORY OVER 2 PERCENT

By this alarm, Troubleshooter reports that VM and Host performances are slightly degraded because of high memory ballooning. Virtual memory ballooning is a computer memory reclamation technique used by a hypervisor to allow the physical host system to retrieve unused memory from certain … Continue reading

KB53: HOST MAINTENANCE MODE

E4C Troubleshooter raises a warning when a host remains in maintenance mode for more than 12 hours.

KB55: CLUSTER RECOMMENDATIONS

The warning is raised by E4C Troubleshooter when there are important pending DRS recommendations that need to be applied on VMware vClient.

KB44: WRONG RESOURCES RESERVATION

This is an advice of E4C Troubleshooter to remove reservations on virtual machines. Setting a memory reservation on a resource pool level has its own weaknesses, but it is much fairer and more along the whole idea of consolidation and sharing … Continue reading

KB:42 WRONG RESOURCES ASSIGNMENT

This is an advice by E4C Troubleshooter to remove limits on virtual machines. Setting a limit on VM memory OR CPU directly is not the best thing to do. VM level reservation can be rather evil, it will hoard memory if it has been … Continue reading

KB23: INVENTORY ERROR

Generic error of missing connection to the vCenter Server, usually due to: Connection refused by vCenter Connection timed out with the vCenter general communication problem with vCenter

KB50: VMOTION INTERFACE NOT CONFIGURED

This error occurs when a host has not been properly configured for VMotion. To VMotion a VM between ESX host, a VMkernel port with a unique IP address is required on each of the ESX host systems. If this port group has not been … Continue reading

KB47: OVERPROVISIONED VM

Overprovisioning resources brings some risks and downsides that should be understood: Potential for high CPU Ready times. As more vCPUs are added to hosts that might already have high workloads, CPU ready time can increase, thus forcing the VM to wait … Continue reading