Hi Sachin

The VASA provider is built into ViPR Controller and is installed when it is installed. By default the VASA provider utilizes the local ViPR nodes.

VIPR VASA Provider is basically a service running on the App. To confirm its running go to Admin -> System > System Health and confirm vasasvc is running.

You can edit the ViPR instance URL that the VASA storage provider utilizes from the Admin -> Configuration -> Other but if using the default (inbuilt VASA with ViPR) leave this UI blank. If you have details in the text field remove and save for the VMS to reboot.

Please try the following to resolve your issue. If you still run into issue please open an SR with support for us to look at the issue by webEX etc...

1. Confirm the Health of the inbuilt VIPR VASA Provider

2. Goto https://< Virtual IP address (VIP) of the ViPR instance>:9083/storageos-vasasvc/

3. Select Services to View the list of all the available services deployed in this server. This will bring you to https://< Virtual IP address (VIP) of the ViPR instance>/storageos-vasasvc/services/listServices

4. From the listServices page look for vasaService - Service EPR (End Point Reference URL) Copy the vasaService URL from the webpage.

5. With the VSphere Web Client Go to Home -> VCenter-> VCenter Servers-> XXXXXXXX > Manage -> Storage Providers

6. In the Register Storage Provider box that is displayed, Provide the following values. Be careful with the format of the login name see below details to confirm all is ok. Click on OK when the details are correct. If you get a Security Alert, Click Yes to continue.

7. Once added, make sure the Storage Provider Details is online. This might take a few minutes.

Be aware of the following solution https://support.emc.com/kb/171036 if you are having issues registering Storage Provider due to user/password

---------------------------------------------------------------------------------------------------------------------------

"ViPR 1.0: Unable to successfully integrate VMware VASA (vSphere API for Storage Awareness) because of username/password combination errors, although they have been verified and work within ViPR"

1. Be sure you are specifying the Virtual IP address (VIP) of the ViPR instance (which in turn has access to all ViPR Controllers)
2. Ensure that the ViPR VIP Ports 9083 and 8443 are open bi-directionally between the vCenter Server and ESXi Servers you are attempting to integrate with ViPR
3. Ensure that the user which is being used to register VASA between the vSphere client and ViPR has been assigned the role “System Administrator" within ViPR
4. Lastly, also ensure that you are using the correct Domain & User ID, and in the proper format to be accepted by both the vSphere client and ViPR. This is explained in more detail in the notes below:

The naming conventions behind AD authentication which are used and accepted in vSphere versus ViPR can be slightly different. In vSphere, the client does not allow the “@” symbol for User ID’s (Ex. “admin-user@viprdomain.com”) – if you use that format (with @), you’ll receive an error that indicates that “@” is not a valid character.

Also however, if you specify the domain by its short name when entering the user (Ex. “viprdomain\admin-user”) as opposed to the FQDN (Ex. “viprdomain.com\admin-user”), you’ll simply receive a “username/password  invalid” error message in the vSphere client, which can be confusing since everything appears to be correct (domain, user ID, and password). Assuming that both ViPR and vSphere have access to the same domains, to resolve this issue, make sure you specify the full FQDN (Ex. "viprdomain.com\admin-user") of the domain in the vSphere client when integrating VASA into ViPR.

---------------------------------------------------------------------------------------------------------------------------

Regards

Conor