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.
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.
I was wondering if you were following the info in this guide when setting vasa up:
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!
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?