This post is more than 5 years old
53 Posts
0
5733
Configuring VMware's VASA with ViPR
Hi,
I have installed vipr-1.0.0.8.103 with below IP addresses configured:
UI, REST: 10.112.93.62
vipr1 (10.112.93.27)
vipr2 (10.112.93.37)
vipr3 (10.112.93.48)
I wanted to configure VASA with ViPR, so I gave a VASA base URL at admin ->config -> Other as http://10.112.93.62:8090/vasa/services/vasaService
All vipr nodes got restarted but this URL is not accessible. I even tried giving http://10.112.93.27:8090/vasa/services/vasaService , but still it is not accessible in browser.
Please suggest how to integrate VASA with ViPR.
-Sachin
ConorLawlor
2 Intern
2 Intern
•
233 Posts
0
January 16th, 2014 08:00
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"
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
sachinnagargoje
53 Posts
0
January 17th, 2014 03:00
Thanks Conor for the detailed information.
I have added ViPR as a storage provider in the vCenter. I could also see the list of all VASA APIs residing at ViPR. I will get back to you on this front. I have below issue now related to creating storage share:
I have attached Isilon backend array. In the ViPR UI, I tried "Creating Unix Share - Create new file system and NFS export". I am getting an error. I have given the "Logs" and "Execution Steps" below.
Do you have idea about this?
Also what is the location of logs at ViPR nodes?
Logs
sachinnagargoje
53 Posts
0
January 17th, 2014 04:00
Hi Conor,
Thanks for the info. I will raise a SR for the above mentioned error.
Can I collect these log from directly logging into the ViPR nodes?
Regards,
Sachin Nagargoje
ConorLawlor
2 Intern
2 Intern
•
233 Posts
0
January 17th, 2014 04:00
Hi Sachin,
Within Create new file system and NFS export UI the "Export Hosts" text field When you added the IPs or Hostnames that should have access to the export. Values must match exactly what is specified within ViPR. Confirm IP of the host was added to the network. There must be network connectivity between the physical storage system and the target host. Ensure the hosts you are giving access to the export are successfully discovered within Admin -> Physical Assets -> Hosts / vCenter
From the help menu in the UI
ConorLawlor
2 Intern
2 Intern
•
233 Posts
0
January 17th, 2014 04:00
Hi Sachin
The logs can be collected from the UI Admin -> logs -> Download
https://community.emc.com/docs/DOC-28089 provides more details on collecting logs.
For the above issue open an SR with Support.
Regards
Conor
ConorLawlor
2 Intern
2 Intern
•
233 Posts
0
January 20th, 2014 03:00
Hi Sachin,
You may need to register your user details with https://support.emc.com/ if you have not done this already. Options available at the login screen.
If you had previously created a support.emc.com user and could login etc... below are the options to request help
At the bottom of every page in the Online Support site is a link for Site Help and Feedback. You can
use this link to submit questions and issues to EMC for follow up. Alternatively, you can email
support@emc.com directly.
Regards
Conor
sachinnagargoje
53 Posts
0
January 20th, 2014 03:00
How do I create a SR ticket?
When I access https://support.emc.com/ , I am unable to access it with my current credentials using which I post here at community right now.
When I go for technical chat, they ask me to redirect at https://support.emc.com/servicecenter/contactEMC/ which again does not open due to my login credentials.
Please suggest.
sachinnagargoje
53 Posts
0
January 20th, 2014 03:00
Hi Conor,
I could not see much options other than logging in at Welcome to EMC Support, which if I try fails.
For now, i have raised my voice at support@emc.com and ecn_support@emc.com.
Thanks for the info.
-Sachin
sachinnagargoje
53 Posts
0
January 20th, 2014 05:00
Hi Conor,
I have raised a SR ticket and currently I am communicating my issue to get it resolved.
Thanks for your info.
-Sachin
sachinnagargoje
53 Posts
0
January 20th, 2014 21:00
Hi Conor,
I got the issue of 'connecting Isilon with ViPR' resolved with the help of technical team from EMC.
I had below doubts regarding working of ViPR:
Q1. How do ViPR manage server swaps? Lets say I unmask a LUN and set up my FCP zones for server A. Then server A dies. Can I say that WWID XXXX is now server A’s replacement and have ViPR re-zone everything and unmask the LUN to the new WWID?
Q2. Are ViPR aware of path status for FCP and IP? What happens when a path is degraded? Do they keep provisioning against that degraded object? Do they attempt remediation?
Q3. Can ViPR take VMDK granular actions? Like, when I put a VMDK onto an NFS share, can I turn on backup against it?
Q4. Where is the service lying in ViPR for managing tenant management? URL? Say, create a new tenant.
Regards,
Sachin
mumshad
16 Posts
0
June 26th, 2016 12:00
I have errors configuring VASA for ViPR and when I go to https://< Virtual IP address (VIP) of the ViPR instance>:9083/storageos-vasasvc/ I do not see the Apache web page. I am using ViPR 2.4.1 and I see that the vasa service is running. I also tried restarting the vasa service.
FoolInTheRain
123 Posts
0
June 27th, 2016 05:00
Hi Mumshad,
I was wondering if you were following the info in this guide when setting vasa up:
http://www.emc.com/collateral/TechnicalDocument/docu59842.pdf
I do not believe the above doc was changed from version Vipr-c 2.3 to 2.4.
After you have seen the vasa serverice running, there are a few more steps after that:
Copying the Storage Provider Service EPR
Registering the Storage Provider
I hope this helps!
mumshad
16 Posts
0
June 27th, 2016 07:00
Hi Jay,
I am trying to perform that step, but when I run the below URL, I do not see any results:
Type the appliance URL as specified https:// :9083/storageos-vasasvc/ services/listServices in the browser address bar.
Is there anything else to be done in ViPR 2.4?
mumshad
16 Posts
0
June 27th, 2016 09:00
Never mind. My issue was due to an expired VMWare certificate, which I resolved following https://kb.vmware.com/kb/2079087
I couldn't see the Tomcat web pages mentioned above though.