How to discover EMC Isilon Storage Systems?

wowashish · ‎08-29-2017

Hi,

We have few EMC Isilon Storage Systems, which we would like to discover. Any input on how to do that would be appreciated.

Thanks,

Ashish

Tony Branton · ‎09-11-2017

You can use two methods to discover Isilon Clusters:

Using a server-less horizontal discovery pattern, use the Isilon OneFS API to extract information via REST. You'll need both the Isilon REST endpoint URL (or IP address), port and a set of credentials to perform the REST queries. See the Isilon OneFS API Reference for more information on the type of information you can extract using REST.
Using a horizontal discovery pattern, use SNMP to query Isilon Clusters. I built a very basic pattern to discover an Isilon Cluster and create a CI with a Storage Server [cmdb_ci_storage_server] class. The pattern captures:
- Cluster hostname
- Chassis model
- Chassis serial number
- OneFS version
- File system volume and mount point
- Total and available space
- Storage devices and disks (name, model, serial number)
- Network adapters

An update set containing the pattern is attached below - note that it's supplied without warranty or support, and used at your own risk.

Of these two methods, the OneFS API allows you to extract information more readily than via SNMP. You may also want to review the OOTB CI classes to determine if they're adequate or whether custom CI classes may better model the Isilon cluster in the CMDB.

Hope this helps.

View solution in original post

Brad Kallmeyer1 · ‎11-20-2017

Tony - on the Horizontal Discovery, are you creating the CI as well? I'm seeing the data returned however the CI is not getting created

armand3 · ‎01-10-2018

Tony - we're utilizing the Isilon SNMP Horizontal discovery and have gotten quite a lot of good information out of it. However, we're running into an issue where the Horizontal Discovery pattern isn't linking NAS FS to Storage Server relationships/reference. I'm pretty fresh to SNOW discovery, let alone horizontal discovery diagnosis, so bear with me.

Specifically Step 30 of Identification (NAS FS to Storage Server relationship) fails to populate the relationships. I'm trying to find out why this is, and my best guess right now is the utilization of the 'computer' column name to build the relationship? I'm not sure if I'm following a red herring or not, or am just reading it incorrectly.

Here's what Debug shows against a node, which is essentially confirming no data:

NAS FS to Storage Server relationship

2018-01-09 14:16:56: setAttribute(nas_file_system_to_storage_server_relation,[{relationType=, parentTableIndex=, parentTableName=, childTableIndex=, childTableName=}])

2018-01-09 14:16:56: setAttribute(nas_file_system_to_storage_server_reference,[{parentTableIndex=, parentTableName=, referenceField=, referenceDirection=, childTableIndex=, childTableName=}])

2018-01-09 14:16:56: Execution time: 0 ms

Other reference/relationship aspects of the horizontal discovery are working as expected and populating. We're on a Jakarta instance as well.

Any help is appreciated!

-Armand

Tony Branton · ‎01-10-2018

Hi Armand - as you've discovered the computer column is used to relate the NAS FS and the Storage Server. The computer column is set in step 7, so if you're able to step through the pattern in debug mode you can validate that at step 30, the $cmdb_ci_storage_server table still contains value(s) in this column. If step 36 is working properly then an unpopulated computer column is unlikely to be the problem.

Some other things to check (assuming this hasn't already been done):

Ensure the Computer reference field is added to the NAS File System form
Ensure the NAS File System related list is added to the Storage Server form
Re-run discovery

Without looking at the instance and being able to step through the pattern (i.e. in debug mode), there's not a lot more I can think of trying.

gani1 · ‎04-08-2018

Hi Daadpool,

Thanks for the pattern and it is working great. One more thing I need is we would like an entry in the CMDB for each cluster that automatically has each node listed as an affected CI. I’m not sure if this would have to be a manual entry or if there is some logic that could create and associate them automatically.

Eg:- As shown in below screenshot I want "miaubnisil-1" to have a relationship as affected CI with parent "miaubnisil" . Please help me on how can I achieve this?

Tony Branton · ‎11-20-2017

Yes, a CI should be created for the Isilon array using the Storage Server CI class.

I suggest using a Discovery Schedule configured to Discover Networks, and specify the IP address range that covers the Isilon arrays you want to discover - then perform a discovery of that network.

Note that this pattern has been developed on Jakarta and may not work on earlier releases.