HPE 3PAR StoreServ / HPE Primera VVols in disconnected state after upgrading to VMware vCenter Server 6.7 Update 3l and later

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• In VMware vCenter Server, you see error message similar to:

• HPE 3PAR StoreServ Storage or HPE Primera VMware Virtual Volumes (VVols) VASA VP appears as disconnected in VMware vCenter Server.
• In the /var/log/vmware/vmware-sps/sps.log file, you see error message similar to:

cat /var/log/vmware/vmware-sps/sps.log | grep -i "Tag mismatch"

2021-01-18T16:49:01.858Z [Thread-277] ERROR opId=sps-Main-987507-454 com.vmware.vim.sms.policy.SyncPolicyManager - [queryStorageCapability] Internal error occured while processing queryStorageCapability:
com.vmware.vim.sms.fault.VasaServiceException: org.apache.axis2.AxisFault: Tag mismatch!
        at com.vmware.vim.sms.client.VasaClientImpl.queryUniqueIdentifiersForEntity(VasaClientImpl.java:329)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.vmware.vim.sms.client.VasaClientMethodInvoker.invokeMethod(VasaClientMethodInvoker.java:48)
        at com.vmware.vim.sms.client.VasaClientMethodInvoker.invoke(VasaClientMethodInvoker.java:35)
        at com.vmware.vim.sms.client.VasaClientHandler.invoke(VasaClientHandler.java:27)
        at com.sun.proxy.$Proxy113.queryUniqueIdentifiersForEntity(Unknown Source)
        at com.vmware.vim.sms.policy.SyncPolicyManager.queryStorageCapability(SyncPolicyManager.java:150)
        at com.vmware.vim.sms.policy.SyncPolicyManager.queryStorageCapability(SyncPolicyManager.java:69)
        at com.vmware.vim.sms.policy.PolicyManagerImpl.queryStorageCapability(PolicyManagerImpl.java:346)
        at com.vmware.sps.vp.LegacyVasaDataCollector.process(LegacyVasaDataCollector.java:80)
        at com.vmware.sps.vp.VendorProviderPolicySyncThread.run(VendorProviderPolicySyncThread.java:48)
        at com.vmware.vim.storage.common.task.opctx.RunnableOpCtxDecorator.run(RunnableOpCtxDecorator.java:38)
        at java.lang.Thread.run(Thread.java:748)

Note: The preceding log excerpts are only examples. The date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server 6.7.x

Resolution

This is not a VMware issue. For more information, see HPE Customer Advisory.
This issue is seen in vSphere 6.7 U3l and later.

Workaround:
To work around this issue, follow either:

• Restore from backup taken prior to upgrade.

Or

• Upgrade to vCenter Server to 7.0 Update 1c or later.

Note: For upgrade compatibility, see vSphere Back-in-time release upgrade restriction.