Hardware status differs in VMware vCenter server and Veeam ONE

KB ID: 1007
Product: Veeam ONE | 6.0 | 6.5 | 7.0 | 8.0 | 9.0 | 9.5 | 10 | 11
Published: 2011-07-14
Last Modified: 2021-06-03
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

One of Veeam ONE’s monitoring features is monitoring and alerting on host hardware status changes.

These alerts are good to know in case of hosts in your environment have hardware issues, the issue will be notified in the alert, and the severity of the issue by VMware's color scale (Yellow - Something is wrong but doesn't involve data loss, Red - Data loss potential or production down, Unknown - Not knowing what the current status is of the sensor).

However, sometimes the hardware statuses in Veeam ONE are not matching the vSphere UI or hardware status alerts cannot be triggered even if the hardware status is changed to Yellow or Red.

Cause

Veeam ONE pulls hardware status information from vCenter’s API, however, at the same time, the VMware vSphere client uses a different method to obtain this type of data. Because of this difference, you may see different information in the VMware vSphere Client and Veeam ONE.

As for alarms, Veeam ONE uses one of the two following ways to trigger the host hardware alerts:

- Using vSphere hardware alerts (Default)

- Using hardware status changes (Alternative)

If the hardware status changed to Yellow or Red, but Veeam ONE didn’t trigger the alarm, then firstly the corresponding alarm needs to be checked on the vCenter side through the vSphere client.

Solution

In order to narrow down the issue, we should compare the hardware status information for monitored objects using both VMware vCenter’s MOB and Host’s MOB which are the mirrors of their APIs.

How to check the hardware sensors using VMware MOB (for example "VMware Rollup Health State"):

1. Open the VMware vCenter server's MOB web link using your Internet browser (https://[your_vCenter_server_address]/mob) and follow this path:
content -> rootFolder -> childEntity -> hostFolder -> childEntity -> host [select appropriate host] -> runtime -> healthSystemRuntime -> systemHealthInfo -> numericSensorInfo

2. Find HostNumericSensorInfo related to VMware Rollup Health State. Make sure that the summary string is “Sensor is operating under normal conditions” and the label string is “Green”.
User-added image

As you can see from the screenshot, this host is having a problem according to the information provided in vCenter server's MOB (VMware Rollup Health State is in Red). What we where expecting to see is the "Green" status with running as normal conditions.

3. Then open the VMware HOST's MOB web link using your Internet browser (https://[your_VMware_host_address]/mob) and follow this path:
content -> rootFolder -> childEntity -> hostFolder -> childEntity -> host -> runtime -> healthSystemRuntime -> systemHealthInfo -> numericSensorInfo

4. Find HostNumericSensorInfo related to the VMware Rollup Health State. Make sure that the summary string is “Sensor is operating under normal conditions” and the label string is “Green”.
User-added image

As you can see from the screenshot, this host is NOT having a problem according to the information provided in host's MOB (VMware Rollup Health State is in Green).

5. ​Make sure that vCenter’s and Host’s MOBs show you the same status/summary for the VMware Rollup Health State.

 

If you see any difference between the VMware vSphere client and/or VMware MOB statuses (as in the example above), open a support case with VMware's support team.

Please note that for Memory and Storage, hardware sensors will pull the data from additional sections of MOB.

Here are the paths for Memory:

Open the VMware vCenter server's MOB web link using your Internet browser (https://[your_vCenter_server_address]/mob) and follow this path:
content -> rootFolder -> childEntity -> hostFolder -> childEntity -> host [select appropriate host] -> runtime -> healthSystemRuntime -> hardwareStatusInfo -> memoryStatusInfo

Open the VMware HOST's MOB web link using your Internet browser (https://[your_VMware_host_address]/mob) and follow this path:
content -> rootFolder -> childEntity -> hostFolder -> childEntity -> host -> runtime -> healthSystemRuntime -> hardwareStatusInfo -> memoryStatusInfo


Here are the paths for Storages:


Open the VMware vCenter server's MOB web link using your Internet browser (https://[your_vCenter_server_address]/mob) and follow this path:
content -> rootFolder -> childEntity -> hostFolder -> childEntity -> host [select appropriate host] -> runtime -> healthSystemRuntime -> hardwareStatusInfo -> storageStatusInfo

Open the VMware HOST's MOB web link using your Internet browser (https://[your_VMware_host_address]/mob) and follow this path:
content -> rootFolder -> childEntity -> hostFolder -> childEntity -> host -> runtime -> healthSystemRuntime -> hardwareStatusInfo -> storageStatusInfo



If you see any difference between the VMware vSphere client and/or VMware MOB statuses (as in the example above), or if the vSphere client is not triggering hardware status alerts, please open a support case with VMware's support team.

More information

For additional information regarding hardware monitoring, check out the "vSphere Client Hardware Health Monitoring" whitepaper from VMware (4.1).  http://www.vmware.com/files/pdf/techpaper/hwhm41_technote.pdf
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.