Hardware status not updating on vCenter server MOB

Products

• VMware vSphere ESXi 8.0

Issue/Introduction

vCenter server MOB page does not get updated when there is any fault occurred in the vCenter server environment.
Certain monitoring tools depend on vCenter server MOB page for monitoring.
From vCenter server UI, navigating to Monitor, selecting "hardware health", MOB page gets updated.

Environment

vCenter server 7.x
vCenter server 8.x
ESXi 7.x
ESXi 8.x

Cause

This is a known issue. Future releases will have a fix for this issue.

Resolution

Note: MOB is not officially supported way of monitoring VC, MOB page will be disabled in future releases.

Work-around:

SSH to the ESXi host:
1. Get the current config of vpxa
"configstorecli config default get -c esx -g services -k vpxa -outfile vpxa_config.json"
Data written to vpxa_config.json

2. Edit the vpxa_config.json and update the value of "host_health_system_throttle_interval" to 1 (highlighted below) and save the file.
...
   "core": {
      "debug_options": {
         "disconnect_hostd": false,
         "ignore_snapshot_config_cache": false,
         "simulate_invalid_snapshot_mo": true,
         "simulate_invalid_snapshot_mo_once": false
      },
      "host_sync": {
         "get_changes": {
            "asyncvmxblob": true,
            "delay": 0,
            "envbrowser_refresh_rate": 300,
            "timeout": 0
         },
         "guestdisk_use_percentage_diff_check": false,
         "heartbeat": {
            "interval": 10,
            "stress_delayed_heartbeat": 300,
            "stress_duration": 180000000,
            "stress_enabled": false,
            "stress_missed_heartbeat": 500
         },

"host_health_system_throttle_interval": 0,  ===>>>>  Update this value to 1

         "max_event_reporting_delay_seconds": 60,
         "ratelimit_sync_period": 150
      },
...

3. Save the vpxa config to config store. 
"configstorecli config current set -c esx -g services -k vpxa -infile vpxa_config.json"
Set: completed successfully

4. Restart vpxa
/etc/init.d/vpxa restart

5. Re-test the operation by triggering a fault in vCenter server and verify if MOB is updated.

Additional Information

Navigate to "/var/run/log" and run "grep -c  "Increment master gen. no to (.*): HostConfig" vpxa*"

If the output results as below, then it confirms the issue.

vpxa.0:0
vpxa.1:0
vpxa.2:0
vpxa.3:0
:
:
vpxa.log:0