How are people using NetApp storage data from pattern discovery?

[cyked]

We're working with the storage team to help them define how they should represent their storage in CMDB, and how to present it in a way that allows the teams who consume it.  Essentially we are at "we don't know, we provide large buckets of storage capacity and don't know the who/how/what/why".  Two main tenets we  continue to push are 1) if you build it, map it, and 2) if you don't what it will support, don't build it.  Example: server builds, if the requestor cannot point to the thing in the CMDB that server will support, don't provision it.

NetApp discovery has been broken for some time (gap between SNMP discovery that was working fine and NetApp moving to ontap OS), but now we've been running pattern discovery for months.  Pattern discovery represents our NetApp clusters with the cluster, nodes in the cluster, the SVMs, file shares, and pools (which we're being told are actual storage volumes).  We're also utilizing(?)/creating qtree objects as well.

The question I have is for those utilizing NetApp ontop cluster pattern discovery with or without service mapping, how are you relating the things captured by discovery to the applications and services they support?  I know netapp built some kind of integration that is JDBC/API related to OCI, has anyone done that?

[TESLASDREAMS]

I believe the integration of NetApp OCI with SNOW CMDB was implemented within NetApp internal IT Department. If you haven't found this article already, it provides a good overview of that integration process. https://blog.netapp.com/4-steps-to-integrate-netapp-oncommand-insight-with-servicenow-configuration-management-database.

Good Luck!

[Hellfried]

Hi, the current SNMP discovery works well, even with clusters, by connecting only to a physical hosting filer.

But the virtual vFilers are displayed as is_virtual=false,
this is why I created idea   

Mark NetApp vFilers (NETAPP SVM) as "is Virtual" , please

in the idea forum : )