How do I registered a new storage provider using PowerCLI?

[chrischrischris]

Hi all,

How do I registered a new storage provider using PowerCLI?

Thanks in advance!

-Chris

[LucD · Accepted solution]

Did you try the New-VasaProvider cmdlet?

[chrischrischris]

Hi Luc,

I tried and failed :-<

Here is the code:

New-VasaProvider  `

-Name 'EMC-Unity-650F' `

  -Url 'https://Unity-650F:8443/vasa/version.xml' `

  -Force

If I use '-force' I get an error claiming my username and password are not correct; I receive the same error for correct and for incorrect username+password combinations.

If I do not use '-force' then I receive an error about the certificate not being trusted; I receive the same error for correct and for incorrect username+password combinations.

Any help you could provide would be greatly appreciated.

## TESTING WITH INCORRECT CREDENTIALS:

Specify Credential

Please specify Username credential

User: asdfasdfasdfasdfa

Password for user asdfasdfasdfasdfa: ********************

New-VasaProvider : 2/10/20 1:04:18 PM   New-VasaProvider                SMS runtime fault on server '/VIServer=vsphere.local\administrator@67-vCenter:443/': Error registering VASA provider at URL 'https://Unity-650F:8443/vasa/version.xml'. Please verify that the provider details are correct.

At ~/new_vasaProvider_01.ps1:3 char:1

+ New-VasaProvider  `

+ ~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : ResourceExists: (:) [New-VasaProvider], MethodFault

+ FullyQualifiedErrorId : Error encountered while deleting storage policy.,VMware.VimAutomation.Storage.Commands.Cmdlets.Sms.NewVasaProvider

=====================================

## TESTING WITH CORRECT CREDENTIALS:

Specify Credential

Please specify Username credential

User: admin

Password for user admin: *********

New-VasaProvider : 2/10/20 1:04:33 PM   New-VasaProvider                SMS runtime fault on server '/VIServer=vsphere.local\administrator@67-vCenter:443/': Error registering VASA provider at URL 'https://Unity-650F:8443/vasa/version.xml'. Please verify that the provider details are correct.

At ~/new_vasaProvider_01.ps1:3 char:1

+ New-VasaProvider  `

+ ~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : ResourceExists: (:) [New-VasaProvider], MethodFault

+ FullyQualifiedErrorId : Error encountered while deleting storage policy.,VMware.VimAutomation.Storage.Commands.Cmdlets.Sms.NewVasaProvider

[LucD]

Are you trying to register the provider in a VCSA 6.7 where the VMCA of that VCSA is a subordinate CA or where the VCSA is configured with a custom root CA?

See Dell EMC doc 65471

As a matter of fact, I struggled with the same the past weekend.

[chrischrischris]

IT WORKED WHEN I CHANGED PORT TO 8444 (from 8443)!!!!

This means it uses VASA 1.0, not sure how that will impact things ...

Thanks again for your help!

[chrischrischris]

Regarding "Are you trying to register the provider in a VCSA 6.7 where the VMCA of that VCSA is a subordinate CA or where the VCSA is configured with a custom root CA?"

How do I tell?  Someone else setup this vCenter....

[LucD]

You could check the VCSA certificate and verify who published it.
And if there is a root CA in the certificate's chain.

Btw, I just tried with port 8444, and that also works in my test environment.

It seems 8444 is required if VVOLs are used.

But I still get the certificate error.

I'll do some further testing.

[chrischrischris]

Hi Luc,

The solution was to use the Unity CLI to delete all the VASA certificates on the Unity.

Once the VASA certificates on the Unity were deleted I was able to successfully register the vCenters with VASA working.

I sent the command details to both VMware and EMC so they can write KBs for other folks who run into this....

Thanks!

-Chris