As per "docu49617_ViPR-1.0-Data-Sheet-and-Compatibility-Matrix.pdf" doc, supported version of Isilon is OneFS 188.8.131.52, 184.108.40.206.
Is Isilon ObeFS v220.127.116.11 compatible as well (as it is a newer version)?
Now, I have installed Isilon OneFS v18.104.22.168 as well in our lab (from here). I can access it using the IP address configured for external communication (i have same IP address of internal and external communication) - https://10.112.93.59:8080/Status?loadState=1 and page looks good - see attached FireShot - Status - isilon-7-cluster-1.png
When I try to add it as physical assets at ViPR, it shows below mentioned error (see attached screenshot :FireShot - Physical Assets I Storage Systems.png)
Discovery: Error - Discovery failed for Isilon urn:storageos:StorageSystem:f88f0645-c72f-428a-bde3-e62a60c36bd3: because discoverPorts failed. Storage system: urn:storageos:StorageSystem:f88f0645-c72f-428a-bde3-e62a60c36bd3:
Any suggestions, what could be wrong here?
However the Isilon VM (10.112.93.59) is accessible from ViPR VM. See the attached screenshot- “isilon_accessible_from_vipr.png”.
These are the preconfiguration requirements for Isilon to discover in ViPR 1.0
The Isilon storage systems that you add to ViPR 1.0 must meet certain preconfiguration requirements.
Before adding an Isilon system to ViPR, verify that:
Be sure to verify that: the names for SmartConnect zones are set to the appropriate delegated domain. DNS is in use for ViPR and provisioned hosts are delegating requests for SmartConnect zones to SmartConnect IP.
The EMC ViPR Data Sheet and Compatibility Matrix on support.EMC.com is the authoritative source of supported version numbers.
Is Isilon OneFS v22.214.171.124 compatible as well (as it is a newer version)?
No not with ViPR 1.0 due to the issue documented in solution https://support.emc.com/kb/172573 as soon as more versions of Isilon OneFS become supported the EMC ViPR Data Sheet and Compatibility Matrix will be updated.
Thanks for the earlier reply. Below are the two follow-up questions:
1. During installation, when I select the vmx file inside clone1, that is: "Virtual Isilon Nodes\b.126.96.36.199r.vga\clone1\b.188.8.131.52r.vga.clone1.vmx", it give below error message:
"Unable to obtain hardware information for the selected machine."
2. For time being, I selected vmx file present at outside, that is : "Virtual Isilon Nodes\b.184.108.40.206r.vga\b.220.127.116.11r.vga.vmx", and proceeded without any error. But as a requirement mentioned in above post, I do not have 3 nodes in the Isilon cluster, but I proceed with single node because of error #1 mentioned above. Thereafter I attached Isilon with EMC's ViPR product. I tried making few actions ("Create Unix Share, Create new file system and NFS export" in User View), and I am getting below error message:
"The evaluation license key for SmartQuotas has expired. Please contact your Isilon representative."
Herewith attached the error log file as well. Do I need to get the license for Isilon? I could not find any forum where they do mention about the licensing part of Isilon. Do I need to raise SRM for this?
A requirement to discover and manage Isilon in VIPR is a min of 3 nodes in the cluster I cannot predict what type of issues you will have by discovering with 1 node as this type of configuration is not supported.
If all the preconfiguration requirements that are stated in the documentation and you are still having issues after discovering Isilon in ViPR please open an SR with support to take a deeper look at the logs etc...
Thanks for your reply.
I just resolved that issue with license. I got EVAL license from EMC. However I have just added one node of the Isilon and I am able to provision the storage to consumers. Not sure why did they kept the requirement of minimum 3 nodes of isilon. Nevertheless, I will proceed with adding few more nodes to it.
I have deployed ViPR 2.0 controller successfully, but i am not able to see "data services configuration tab" under settings, hence not able to download config.iso .
Any idea ?
Are you logged in as root? Also does the license show items with object in them? You may not have a license for this functionality.