SECURITY Permission to manage Sites and manage Devices
NAVIGATION Sites > open a site > New Device
About VMware ESXi
VMware ESXi (also known as VMware vSphere Hypervisor) is a purpose-built hypervisor operating system that runs on bare metal and incorporates VMware’s virtualization technologies. ESXi can be configured to manage virtual machines that run within the ESXi core and that are monitored by it. Virtual machines running on an ESXi server will be allocated a share of the resources of the host system. Also see A note on Subscription.
The ESXi hypervisor operating system does not permit application installation per se, making installation of the Datto RMM Agent impossible. Servers running ESXi must therefore be managed as network devices, facilitating the use of network nodes for device discovery, monitoring and management.
The following ESXi builds are supported:
Please note that ESXi 6.5 and later disable CIM access by default, therefore, the Web Portal will report CIM authentication errors in the ESXi device summary. To solve this:
- Enable the SSH service on the ESXi device.
- Connect to the ESXi device via SSH (for example, using Putty).
- Perform the following commands:
esxcli system wbem set --enable true /etc/init.d/sfcbd-watchdog start
Performing these commands permits the “sfcbd-watchdog” service to start with WBEM (another term for CIM) enabled, permitting the device to broadcast CIM data to the Network Node. Only by performing these steps will your ESXi hypervisor report CPU Socket and RAM information correctly.
These steps also permit ESXi servers to access information pertaining to device serial codes which may not be audited otherwise.
The ESXi account must be the root user account.
Network node requirements for ESXi monitoring:
- The network node device performing ESXi monitoring must run on Windows operating system and have Microsoft .NET Framework version 4.7 or higher.
- The network node device performing ESXi monitoring can run on a guest machine on the ESXi host. Please note that the downside of monitoring from a guest is that all monitoring stops when the host goes down.
- ESXi monitoring is supported across subnets, so the network node device does not have to be on the same subnet as the ESXi device but it must be on the same network to be reachable.
We highly recommend some background reading on VMware vSphere Hypervisor if you are not familiar with the concepts, terminology and technology around ESXi and virtualization. For information, refer to https://www.vmware.com/uk/products/vsphere-hypervisor.
"Subscription" is an industry-standard term used to refer to the maximum potential capacity occupation of all virtual machines within an ESXi host.
VMs have a maximum size they can expand to but, by default, they are provisioned to only occupy the storage that they are actively using on the host. For example, a VM that has a maximum size of 10GB but is only using 2GB will be 2GB in size.
A potential situation can occur where a host's data becomes "oversubscribed" (that is, the host's Subscription shows more than 100%) because the sum of occupied space with all VMs at capacity would exceed the host's storage limit. It is, therefore, recommended to monitor the occupied disk space of the virtual machines and the available space in the ESXi host to avoid "oversubscription".
To be able to monitor your ESXi devices, you need to add them as Managed devices to your account.
You can have one of your fully Managed network node devices scan the network for you to discover ESXi devices. The network node device will check for devices listening on port 902 and if a device responds, it will be listed as an ESXi device in the discovered devices list. For further information on device discovery, refer to Network discovery.
You can also add your ESXi devices as Managed devices manually by following these steps:
- Refer to the first few steps outlined in Downloading or emailing the Agent installer to navigate to the correct site.
NOTE ESXi devices can only be added to Managed sites.
- Click the ESXi Host icon.
- Fill in the following details:
|Field||What to Enter|
|Network Node||Select a network node device that will monitor your device. For more information about network nodes, refer to Network discovery.|
|IP Address||Enter the internal IP address of your device.|
|Name||Give your device a name.|
|Description||Enter a description.|
|Manufacturer||Enter the name of the manufacturer of your device.|
|Model||Enter the model of your device.|
|New ESXi Credentials||Enter the ESXi credentials of your device. For more information, refer to the ESXi Credentials section in Account Settings and Site Settings.|
|Use Account/Site ESXi Credentials||Choose this option if you have ESXi credentials stored at the account or site level. The Site ESXi Credentials will be used in addition to the ESXi credentials specified in Account Settings unless this option is disabled in Site Settings. For information on how to store the ESXi credentials for the entire account or at the site level, refer to the ESXi Credentials section in Account Settings and Site Settings.|
- Click Save. Your ESXi device is now added as a Managed device to your account.
Once an ESXi device has been enrolled, you can apply monitoring to it. ESXi monitoring is performed through a network node. For information on requirements, refer to Requirements.
The following ESXi monitor types are available:
- ESXi CPU Monitor
- ESXi Data Store Monitor
- ESXi Disk Health Monitor
- ESXi Fan Monitor
- ESXi Memory Monitor
- ESXi PSU Monitor
- ESXi Temperature Sensor Monitor
You can also apply the following non-ESXi-specific monitor:
- Online Status Monitor
For more information, refer to Manage monitors.
For information on how to create an ESXi policy, refer to Create an ESXi policy.