vSphere 7 vSAN Skyline error for Update Manager

[signalpower]

I have a customer with a vSphere 7 plattform with vSAN, disconnected from Internet. They get a warning/error in Skyline regarding build recommendation. The entry is vSAN Build Recommendation Engine Health with message "VMware Update Manager (VUM) is disabled or is not installed. Please make sure VUM is installed and functioning properly."

I have set up UMDS for patch downloads, copied the latest files in to a web server. Lifecycle manager downloads the patches, and I'm able to patch the hosts.

The warnings in the cluster Summary (in yellow) is "vSAN build recommendation alarm 'vSAN build recommendation engine'" and "alarm.vsan.health.test.vum". To me it looks like this is some old check/code being included in this new version, but I have no idea what's going on here.

Has anyone else had the same problem? Any suggestions for a solution is welcome.

[scottlarsen]

I am experiencing the same issue/result/report today, after applying the VCSA 7.0 U2a patch.

[A13x]

im connected to the internet via proxy but also get this warning after Update 2a patch

[scottlarsen]

@A13x,

Did you have a clean report prior to the U2a installation?

Mine was clean, and then U2a popped this up.

[DanMc85]

I seen this issue too in my homelab. 

Typically required a hard reboot of the VSAN host, in this case a Dell R740. You may also find when this happens to the identified host, as shown in Skyline health, that you cannot do things with the VMs on that host in vCenter, i.e. Shutdown, open console, vmotion.   Others seem unaffected.  Also if the Check for Compliance does work, it comes back with a bunch of updates needed out of nowhere which isn't really true and vanish after a hard reset and checking again.

I have seen this happen randomly with multiple hosts in the cluster at random times since updating to 7.0.2, at first I thought it was a compatibility issue with Veeam Backup and Replication as it always seems to happen overnight, maybe a random coincidence. 

I also see this in ESXi logs when this happens.

2021-05-13T09:25:35.737Z cpu16:2097481)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba32:C0:T0:L0" state in doubt; requested fast path state update...

2021-05-13T09:33:14.398Z cpu0:2103384)WARNING: Fil3: 1534: Failed to reserve volume f533 28 1 60310ddb de7e2394 e9f40d4b f4297dd4 0 0 0 0 0 0 0

2021-05-13T11:07:41.152Z cpu23:2252335)ALERT: Bootbank cannot be found at path '/bootbank'

2021-05-13T14:24:55.591Z cpu0:2097482)ScsiPath: 8058: Cancelled Cmd(0x45bbed5987c0) 0x0, cmdId.initiator=0x4538be99bc58 CmdSN 0x0 from world 0 to path "vmhba32:C0:T0:L0". Cmd count Active:0 Queued:1.
2021-05-13T14:24:55.591Z cpu1:2241148)VMW_SATP_LOCAL: satp_local_updatePath:856: Failed to update path "vmhba32:C0:T0:L0" state. Status=Transient storage condition, suggest retry
2021-05-13T14:25:14.512Z cpu6:2097481)ScsiPath: 8058: Cancelled Cmd(0x45bbed5874c0) 0x9e, cmdId.initiator=0x4538b229a708 CmdSN 0x2bd81 from world 0 to path "vmhba32:C0:T0:L0". Cmd count Active:0 Queued:0.
2021-05-13T14:25:14.512Z cpu6:2097481)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba32:C0:T0:L0" state in doubt; requested fast path state update...
2021-05-13T14:25:14.512Z cpu6:2097481)ScsiDeviceIO: 4315: Cmd(0x45bbed5874c0) 0x9e, cmdId.initiator=0x4538b229a708 CmdSN 0x2bd81 from world 0 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x5 D:0x0 P:0x0 Cancelled from path layer. Cmd count Active:1
2021-05-13T14:25:14.512Z cpu6:2097481)Queued:1

Found this thread @ Dell if your issue is also with a Dell Server or similar using SD Cards for ESXi boot: VMware 7.0 U2 losing contact with SD card - Dell Community

[Spisarau]

Vsphere upgrade to 7.0.2.00400 resolved the issue

[cl_chang]

I have the same issue in 7.0.1, after upgrading to 7.0.3 the warning is still there.

[Casseau33]

Same issue here

[A13x]

I updated vCenter versions and it resolved it for me:

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3e-release-notes.html

Resolved Issues

The resolved issues are grouped as follows.

• Miscellaneous Issues

Miscellaneous Issues

• VMware Skyline Health screen shows an error instead of system health info

  In the vSphere Client, when you navigate to Monitor > Skyline Health under a vSAN or vSphere cluster, you see an error such as Unable to query vSphere health information. Check vSphere Client logs for details.. The issue occurs because in certain environments Skyline Health cannot discover the APIs it needs to collect data from the vCenter Server system and ESXi hosts.
  In the analytics service logs, you see errors such as:
  Error while getting the data providers list from: com.vmware.ph.phservice.provider.appliance.ApplianceDataProvidersConnection java.lang.IllegalStateException: Unable to locate VAPI URI.

  This issue is resolved in this release.