Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2788

February 7th, 2014 12:00

Error when discovering Isilon (ports)

I'm getting the following error

Device discovery failed; Device is unreachable

when discovering an OneFS 7.1 Isilon

Here is the log :

discoverPorts failed. Storage system: urn:storageos:StorageSystem:a3b40471-fbc2-4b89-8761-6fb358489284:

com.emc.storageos.isilon.restapi.IsilonException: Get storage connection info failed on Isilon array, http status Client response status: 200

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at com.emc.storageos.svcs.errorhandling.model.ExceptionMessagesProxy.contructException(ExceptionMessagesProxy.java:177)

at com.emc.storageos.svcs.errorhandling.model.ExceptionMessagesProxy.invoke(ExceptionMessagesProxy.java:66)

at com.sun.proxy.$Proxy46.getStorageConnectionInfoFailedOnIsilonArrayExc(Unknown Source)

at com.emc.storageos.isilon.restapi.IsilonApi.getSmartConnectInfo(IsilonApi.java:886)

at com.emc.storageos.volumecontroller.impl.plugins.IsilonCommunicationInterface.discoverPorts(IsilonCommunicationInterface.java:457)

at com.emc.storageos.volumecontroller.impl.plugins.IsilonCommunicationInterface.discoverAll(IsilonCommunicationInterface.java:274)

at com.emc.storageos.volumecontroller.impl.plugins.IsilonCommunicationInterface.discover(IsilonCommunicationInterface.java:235)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.invoke(DataCollectionJobInvoker.java:132)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.process(DataCollectionJobInvoker.java:86)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.invokeJob(DataCollectionJobConsumer.java:279)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer$1.run(DataCollectionJobConsumer.java:205)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)

at java.lang.Thread.run(Thread.java:662)

Caused by: javax.ws.rs.WebApplicationException: java.lang.Exception: Error parsing JSON object.

at com.sun.jersey.json.impl.provider.entity.JSONObjectProvider.readFrom(JSONObjectProvider.java:93)

at com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App.readFrom(JSONObjectProvider.java:65)

at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:554)

at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:506)

at com.emc.storageos.isilon.restapi.IsilonApi.getSmartConnectInfo(IsilonApi.java:879)

... 15 more

Caused by: java.lang.Exception: Error parsing JSON object.

... 20 more

Caused by: org.codehaus.jettison.json.JSONException: A JSONObject text must begin with '{' at character 2 of

[

{

"service_ip" : "10.250.14.239",

"zones" : [ "NY-NAS-P-SHARE-001" ]

},

{

"service_ip" : "10.250.16.239",

"zones" : [ "NY-NAS-I-SHARE-001", "NY-NAS-I-NFS-001" ]

},

{

"service_ip" : "157.150.187.239",

"zones" : [ "NY-NAS-E-SHARE-001" ]

},

{

"service_ip" : "10.250.25.239",

"zones" : [ "NY-NAS-P-MGT-011", "Backup" ]

}

]

at org.codehaus.jettison.json.JSONTokener.syntaxError(JSONTokener.java:439)

at org.codehaus.jettison.json.JSONObject. (JSONObject.java:169)

at org.codehaus.jettison.json.JSONObject. (JSONObject.java:266)

at com.sun.jersey.json.impl.provider.entity.JSONObjectProvider.readFrom(JSONObjectProvider.java:91)

... 19 more

92 Posts

February 9th, 2014 16:00

We only support Isilon OneFS versions 7.0.2.0 and 7.0.2.1 on ViPR version 1.0 patch 1.  Can you verify you are using a supported version.

Thanks,

Andrew

1 Rookie

 • 

20.4K Posts

February 7th, 2014 13:00

i thought only certain 7.0.x versions were supported.

114 Posts

February 9th, 2014 18:00

Thanks dynamox and Andrew. Any idea when 7.1 support is coming ?

92 Posts

February 11th, 2014 07:00

I have put an email into Product Management asking when 7.1 will be supported.  Will post back when we have an answer.

5 Practitioner

 • 

274.2K Posts

May 21st, 2014 06:00

hey,

We are using a virtual isilon in our poc 7.0.2.1 and the vipr version is vipr-1.1.0.1.44...Getting the same error msg Failed; Device is unreachable... Any suggestions here ?

92 Posts

May 21st, 2014 08:00

Are you discovering with the root account?  Is it licensed?  Did you configure I think its called the webconnect port or zone?  Have you validated that you can login to the Isilon UI?

92 Posts

May 21st, 2014 09:00

"SmartConnect" is Isilon term I was trying to remember earlier....

5 Practitioner

 • 

274.2K Posts

May 21st, 2014 23:00

thanks for the response andrew...

1. yes discovery was done using the root account

2. Yes licensed

3. smartconnect is not configured..as this is a poc we have not connected it to a domain.

4. currently we are having one node...

The things is that viper gets the storage system added and it also shows the storage pool in the virtual isilon node..

Kindly see the snapshots below, not sure what am missing here.

error1.png

error2.pngerror3.png

92 Posts

May 22nd, 2014 05:00

Please check out the ViPR installation and configuration guide.  You will notice some of the Isilon requirements.

Preconfiguration requirements for Isilon

The Isilon storage systems that you add to ViPR must meet certain preconfiguration

requirements.

Before adding an Isilon system to ViPR, verify that:

OneFS version is listed in the EMC ViPR Data Sheet and Compatibility Matrix.

SmartConnect is configured as described in Isilon documentation. 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.

There is a minimum of 3 nodes in the Isilon cluster configured.

Isilon clusters and zones will be reachable from ViPR Controller VMs.

If you ensure these items in place is should work fine for you.  The documents should be on the community and support.emc.com.

Andrew

No Events found!

Top