IBM SVC Discovery

[Ziad Qadora]

Hello,

I have a requirement to implement discovery of storage devices managed by "IBM SVC" V8.5.X 

I have checked the community and I do not see much about this type of discovery.  There is a 2015 Community Post, and the recommended solution was to add  'storageVirtualizer' Classification Criteria to the SMI - Storage Server record which is already available in the UTAH release. 

The difference between is that the recommended Classification Criteria in the post  is that  the recommended Classification Criteria is "CIM_RegisteredProfile{{RegisteredName='Storage Virtualizer'}}.CIM_ElementConformsToProfile{{ResultClass:'CIM_ComputerSystem'}}.ElementName" 

While the Classification Criteria in Utah release is

"CIM_RegisteredProfile{{RegisteredName='Storage Virtualizer'}}.CIM_ElementConformsToProfile{{ResultClass:'CIM_Cluster'}}.ElementName"

My question is: has anyone been able to successfully implement discovery of "IBM SVC".  If yes, would you please share what was done in order to so.

P.S. I have posted the same question in the ITOM forum, but did not get a response.  

Regards,

Ziad

[SwarnadeepNandy]

Hello,

There are some possible ways to discover storage devices managed by IBM SVC using ServiceNow Discovery. Here are some suggestions:

• You can use the SMI-S Storage Server pattern to discover storage devices that support the SMI-S protocol, such as IBM SVC. This pattern uses the SMI-S credentials and probes to connect to the SMI-S provider and retrieve information about the storage devices, such as name, model, serial number, capacity, and status. You can also discover the relationships between the storage devices and other CIs, such as hosts, di....
• You can use the IBM SVC Storage Virtualizer pattern to discover IBM SVC clusters and nodes that provide virtualization services for storage devices. This pattern uses the SSH credentials and probes to connect to the IBM SVC nodes and run commands to get information about the clusters, nodes, disks, volumes, pools, and mappings. You can also discover the relationships between the IBM SVC CIs and other CIs, such as hosts and sto....
• You can use the IBM SVC REST API pattern to discover IBM SVC clusters and nodes using the REST API. This pattern uses the REST credentials and probes to send requests to the IBM SVC REST API endpoint and parse the responses to get information about the clusters, nodes, disks, volumes, pools, and mappings. You can also discover the relationships between the IBM SVC CIs and other CIs, such as hosts and storage devices.

I hope this helps you with your discovery of storage devices managed by IBM SVC.

Kind Regards,

Swarnadeep Nandy

[Ziad Qadora]

Hi @SwarnadeepNandy 

Thank you for your response.

Does using the SMI-S Storage Server and IBM SVC Storage Virtualizer involves serverless discovery?

If yes, so far I have tried serverless discovery for Cohesity and NetApp discovery and my experience that serverless discovery is not straight forward.

Please let me what type of discovery schedule you recommend using, and if you are aware of any challenges when setting the discovery schedule and how to tackle them.

Again, I appreciate your response and help.

Regards,

Ziad 

[Ziad Qadora · Accepted solution]

We did setup the discovery schedule to use behavior CIM, which was setup as shown in the screenshot.  Moreover, we added probe parameter "cim_version" and set the value to modern as per 

KB0853408 

Regards,

Ziad