VMware

You may notice alerts from the ESX Workload monitor indicating that the Percent Used for a specific VM instance is greater than 100%. This is a valid scenario indicating that the instance is using...

By: CSS | Date Created: 6-26-2010 | Last Modified: 8-10-2011 | Index: 455

The most common reason that ESX systems that were previously collecting performance data but have now stopped collecting is that the password for the ESX system has changed or expired. Verify that...

By: CSS | Date Created: 8-10-2010 | Last Modified: 8-13-2011 | Index: 473

There are several possible reasons why you may be experiencing this issue. To help identify the root cause, take the following steps: 1. Try using Root credentials to add the ESX host by its...

By: CSS | Date Created: 6-9-2011 | Last Modified: 8-12-2011 | Index: 525

There are several reasons a VMware instance may consume a license. 1) VMware tools are not installed on the target VM. 2) The VM is not running on an ESX server that is also monitored by up.time...

By: CSS | Date Created: 8-7-2010 | Last Modified: 5-4-2013 | Index: 470

You may notice that the VMware Virtual Infrastructure Client memory graph doesn't match the memory values shown in up.time. This is because the default VMware graphs display a different metric than...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 312

Agent based monitors, for example File System Capacity or Check for a Process will not work with ESX elements because those elements are monitored agent-lessly.

By: CSS | Date Created: 9-25-2010 | Last Modified: 8-10-2011 | Index: 512