vSphere Storage Appliance

we went through a VASA provider migration from an external Vasa appliance to an internal one. All VMs on our VVOLs are now inaccessible. Dell has no idea what is wrong. 

VVOLs dont say they are inaccessible, but trying to browse to a VM's files in a VVOL results in no files found and we get an error. What can I can check here? 

[root@ndcpvm02f:~] esxcli storage vvol vasaprovider list
vasa-1
VP Name: vasa-1
URL: https://192.168.253.19:5989/vasa-providers.xml
Status: online
Arrays:
Array Id: VmaxVVolVasaProvider:60000970000197903181F00000000000
Is Active: true
Priority: 255
[root@ndcpvm02f:~] cd /vmfs/volumes/Unmanaged_Container_01
[root@ndcpvm02f:/vmfs/volumes/vvol:600009700bcbc34d-4ceb0167000008b7] ls
ls: ./naa.600009700BCBC34D4CEB00670003FCB6: Invalid argument
ls: ./vCLS-8bfb1bff-d939-46a1-968f-5c51ea1dee8d: Invalid argument
ls: ./naa.600009700BCBC34D4CEB0067000014B8: No such file or directory
ls: ./ndcpdo801y: No such file or directory
ls: ./naa.600009700BCBC34D4CEB0067000008F3: No such file or directory
ls: ./ndcpdo801z: No such file or directory
ls: ./naa.600009700BCBC34D4CEB006700000887: No such file or directory

"2024-03-26T05:03:02.444Z info vvold[2100413] [Originator@6876 sub=Default] StorageArray::QueryPEs, arrayId=VmaxVVolVasaProvider:600009700001979
2024-03-26T05:03:02.444Z info vvold[2100413] [Originator@6876 sub=Default] VasaOp::QueryPEs [#441]: ===> Issuing 'queryProtocolEndpoint' to VP
2024-03-26T05:03:03.771Z warning vvold[2100413] [Originator@6876 sub=Default] Error parsing response to: QueryPEs from VP: vasa-1 soap_error: 4
2024-03-26T05:03:03.771Z warning vvold[2100413] [Originator@6876 sub=Default] **** invalid soap response start ****
--> HTTP/1.1 200 OK
--> Set-Cookie: VASASESSIONID=IWLHQ0MKM24O5O+_0DP1XR9_
--> Content-Type: application/soap+xml;charset=utf-8
--> Transfer-encoding: chunked"

For anyone that comes across this issue, I have heard back from VMware Engineering:

"before the upgrade the VASA provider was using vvol-ids with 32 hexadecimal digits (no hyphens) format, example: "600009700BCBC34D4CEB006700019D61" and after the upgrade VASA provider is using NAA 64-bit UUID with prefix, example: "naa.600009700BCBC34D4CEB006700019D61".

With the firmware upgrade the vvol-id format must not change.

This change has caused vvold to crash and it is unable to keep running.
We need to check with Dell EMC Powermax side, why they are not following the same format across firmware versions."