How can we help?

How to Troubleshoot VMware Component Alerts

Follow

Auvik receives hardware sensor data from ESXi hosts directly through the VMware API. If you receive an Auvik alert that a component (CPU, disk, RAM or power supply) is in a failed or degraded state, but you can’t find the same information in vCenter or vSphere, you can use the Managed Object Browser (MOB) to verify if Auvik is relaying the state correctly. To do so, follow the three steps below:

Enable the MOB

As noted in https://kb.vmware.com/s/article/2108405, the MOB is disabled by default in vSphere versions 6.x and newer. Please go through the steps described in VMWare's KB article to enable it.

Access the MOB

The MOB runs in a web browser, and is accessed by using the fully-qualified domain name or IP address for the ESX/ESXi or vCenter Server system. Follow these steps to open the MOB.

  1. Start a Web browser.
  2. Enter the fully-qualified domain name (or the IP address) for the ESX/ESXi or vCenter Server system. For example:
https://hostname.yourcompany.com/mob
  1. Enter the user account and password for the system. You should now be in the MOB root.

If warning messages regarding the SSL certificate appear, you can disregard them and continue to log in to the MOB, if VMware is the certificate authority, and you are not in a production environment.

Source: https://vdc-repo.vmware.com/vmwb-repository/dcr-public/f1c3b41b-ead5-4d47-aca4-33298d5a4fcf/778a00f3-a9b6-42f4-8f22-7216733f5f03/doc/PG_Appx_Using_MOB.20.2.html

Note: This information pertains to VMware systems and is subject to change.

Locate the hardware sensor information

Once you are in the MOB root, you'll need to navigate to the correct location to see what the hardware sensors are reporting. The exact path varies slightly depending on whether you are accessing the MOB in the ESXi host directly or in vCenter, as described below.

If you are accessing the ESXi host directly

  • CPU: Content > rootFolder > childEntity > hostFolder > childEntity > host > runtime > healthSystemRuntime > hardwareStatusInfo > cpuStatusInfo
  • RAM: Content > rootFolder > childEntity > hostFolder > childEntity > host > runtime > healthSystemRuntime > hardwareStatusInfo > memoryStatusInfo
  • Disks: Content > rootFolder > childEntity > hostFolder > childEntity > host > click "host" -> runtime > healthSystemRuntime > hardwareStatusInfo > storageStatusInfo
  • General hardware status (including power supply): Content > rootFolder > childEntity > hostFolder > childEntity > runtime > healthSystemRuntime > systemHealthInfo > numericSensorInfo

If you are accessing the MOB through vCenter

  • CPU: Content > rootFolder > childEntity > hostFolder > childEntity > host [select appropriate host] > runtime > healthSystemRuntime > hardwareStatusInfo > cpuStatusInfo
  • RAM: Content > rootFolder > childEntity > hostFolder > childEntity > host [select appropriate host] > runtime > healthSystemRuntime > hardwareStatusInfo > memoryStatusInfo
  • Disks: Content > rootFolder > childEntity > hostFolder > childEntity > host [select appropriate host] > click "host" -> runtime > healthSystemRuntime > hardwareStatusInfo > storageStatusInfo
  • General hardware status (including power supply): Content > rootFolder > childEntity > hostFolder > childEntity > host [select appropriate host] > runtime > healthSystemRuntime > systemHealthInfo > numericSensorInfo
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request