Pattern Error for EMC Isilon

[Shantanu_99]

Hi All,

We have Discovery schedule to discover storage devices. We are getting EMC Isilon Pattern error like below.

Also attached snapshot of the error below.

Identification Engine: Discovery status is FAILURE, Identification sections in pattern failed: section: Identification, error: class java.lang.String cannot be cast to class java.util.List (java.lang.String and java.util.List are in module java.base of loader 'bootstrap')
java.lang.ClassCastException: class java.lang.String cannot be cast to class java.util.List (java.lang.String and java.util.List are in module java.base of loader 'bootstrap')

Can you please help me how to resolve this error

Thanks in Advance,

Shantanu B

[oronsubayi]

Hey!

There is not a lot of info provided, so my answer will make some assumption. Feel free to correct me

The first thing I recommend when troubleshooting issues reside on the MID is to set "mid.log.level" MID config parameter to "debug", regardless whether the issue can be resolved without turning it on

This will most likely get you to a faster resolution and also help whoever is helping you : )

This error usually means that the step in question is expecting to work with a table\list variable, but got a string variable instead

You need to identify what is step in the pattern that throws this error

You can do it by looking at the MID server logs, but I'm also quite sure that if you open the pattern log and do a browser search on the full log, it will get you to the place which will also have the step's name

As soon as you find what this variable is, you will have to track down how its value was populated and understand why it is a string

[orons]

Well..apparently I was logged in with my private user.....😅

Hope that answer helps

[DaveHertel]

I observed same problem & error message.   EMC Isilon pattern had worked everyday for months, suddenly stopped working.  The credential (basic auth) used to query EMC had expired/locked.  Fixed cred, which fixed the problem.    To verify, open pattern in debugger and observe results returned after pattern steps to get cluster info.  If it says "401 Unauthorized to access...." thats your clue

Hope this helps?