Query: VMware Integration

[jchen522]

When trying to turn on VASA Provider (VVols) from HPE Nimble Storage, I am getting the following error.

The following errors occurred

extension.     error
vasa.     SmsTask failed, state=error, key=SmsTask-11

If I turn on Web Client only then it registers fine.  vCenter is 8.0.2.00100.  I can see the plug in vCenter and create VMFS volume no problems.

How do I go about troubleshooting this?  Is there a detailed log somewhere?

[buzzsubash]

Hello,

VASA issues needs some log verification and cannot assist through this forum, you will need to create a support case.

But let me try to provide some hints,  Verify the array’s FQDN in your DNS records. From both the array and the vCenter appliance run nslookup <array-fqdn> and make sure it resolves to the correct IP.

And there are other possibilities including SSL, firewall ports 80, 443, 8443 etc are open. Please open a support ticket.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

[jchen522]

Hi Subash,

Thank you for the quick reply!

Didn't realize the array need to have FQDN record. I can setup DNS entry but where do I configure the FQDN on the array?

I am testing this on a HPE Nimble Storage Virtual Array not sure if I can open a case on this.

Is there a log somewhere I can look at to troubleshoot this?

Thank you!

[buzzsubash]

Hi

You don’t really configure the FQDN on the array directly — the key is that whatever hostname the array uses internally should resolve properly via DNS. So just make sure that the FQDN you're adding in DNS matches the array’s hostname (you can check that from the array GUI or CLI). Then from both vCenter and the array, run nslookup <array-fqdn> to confirm.

As for logs — in the virtual array, access is pretty limited. You won’t get the full set of logs you’d typically expect on a physical array. So while there might be something basic, it’s probably not worth spending too much time digging in there for deep VASA/API issues.

Also,  testing vCenter integration (especially VASA) on a virtual array isn’t ideal. There are a lot of dependencies and API interactions that might not behave as expected. It’s fine for UI demos, functionality checks, or some light PoC work, but for anything production-like or detailed troubleshooting, you’ll need a physical array.