vSAN Datastore Not Compatible with Performance Service Policy due to Offline IO Filters
search cancel

vSAN Datastore Not Compatible with Performance Service Policy due to Offline IO Filters

book

Article ID: 433799

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

When creating a new VMware vSAN cluster, the vSAN Health score displays warnings for "vSAN cluster configuration consistency" and "Performance service status".

The storage policy screen shows vSAN datastores incompatible with reason "Datastore not does match current storage policy"

The vmware-vsan-health-summary-result.log on vCenter reports:

  • VsanDatastoreIsNotCompatibleWithThePolicyConfiguredForVsanPerformanceService

  • PerformanceServiceIsTurnedOnInClusterConfiguration,ButItIsNotEnabledYet

Reviewing the vCenter Server VMware vSphere Profile-Driven Storage Service (SPS) logs (sps.log) reveals that the service cannot locate the storage information for the newly created datastore:

WARN opId=######-#### com.vmware.spbm.domain.vp.VendorProvider - StorageInfo is null for blob: PolicyBlob}

Environment

VMware vCenter Server 8.0.x
VMware ESXi 8.0.x
VMware vSAN 8.x

Cause

The presence of "Offline" storage providers in the vCenter Server inventory results in the vSAN VASA provider timing out when executing periodic getEvent and getAlarm updates. This interruption stops the VMware vSphere Profile-Driven Storage Service (SPS) from dynamically updating its StorageInfo cache when a new vSAN datastore is created. Because the SPS cache lacks the configuration data for the newly created datastore, it is incorrectly flagged as incompatible with the vSAN Performance Service policy.

Resolution

Remove the Offline storage providers:

Solution 1: Unregister the offline providers using the vCenter SMS Mob page

    • Log in to the following link: https://<vCenter-fqdn.local>/sms/mob
    • Click on QueryStorageManager link
    • Click on Invoke method, then on the storageManager link in the Method Invocation Result
    • Click on the QueryProvider link and Invoke method
    • Click through the vasaProvider-### links in the Method Invocation Results one by one
    • For each vasaProvider selected click on QueryProviderInfo link and Invoke Method
    • Cross reference the result for "uid" field and note it down for each "url" entry that matches from the url's mentioned in the vCenter Storage Provider pane as showing offline.
      • For example: (sms.provider.VasaProviderInfo) { dynamicType = null, dynamicProperty = null, uid = ########-####-####-####-############)
    • Go Back to the QueryStorageManager link (see step 1, step 2 and step 3)
    • Click on UnregisterProvider_Task link
    • Enter one of the the provider uid's found in step 6 and click on the invoke method
    • Repeat steps 7 to 10 for each of the IOFilter providers shown as Offline
    • Use one of the following methods  to synchronize storage providers
      • Restart the SPS service with these commands to reregister the I/O Filter providers:
        • service-control --stop vmware-sps && service-control --start vmware-sps
      • In vSphere Client, go to vCenter > Configure > Storage Providers, Click on “Synchronize Storage Providers

Solution 2: Remove all Offline providers using a PowerCLI script

Additional Information

Certain IOFIlter Providers are showing as offline

Recurring alerts in vCenter "vSAN Performance Service is not enabled" and "'vSAN Cluster Configuration Consistency"

Datastore does not match current VM policy