---
sourceDocument: Zurich IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Storage discovery

# Storage discovery {#ariaid-title1}

Release version: Zurich  
Updated July 31, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Storage discovery

Storage Discovery in ServiceNow Zurich release enables automated collection and mapping of storage-related data across Direct Attached Storage (DAS), Storage Area Networks (SAN), and Network Attached Storage (NAS).
It discovers storage connected via specialized devices (like Storage Arrays, Fibre Channel Switches, iSCSI disks) and host operating systems (Windows, Linux, Solaris).
This capability helps build an accurate and comprehensive CMDB by identifying storage components and their dependencies, including virtual storage for VMware ESX and Linux KVM environments.
Show full answer Show less  

## Key Features

* Discovery of various storage types: DAS, NAS, SAN, including those accessed via SMI-S and CIM protocols.
* Support for virtual storage mapping to underlying physical storage for VMware and KVM platforms.
* Custom pattern creation through Pattern Designer for devices lacking existing discovery patterns, enabling REST or CLI-based data collection.
* Automated reconciliation of storage devices with host file systems when discovered via the host, assuming prior discovery of the storage server.
* Creation of detailed CIs in the CMDB for file systems, disks, Fibre Channel HBAs and ports, Linux LVM volumes, and Veritas Volume Manager components.
* Specialized probes and sensors tailored for multiple operating systems and platforms (Linux, Solaris, Windows 2008/2012, VMware ESX).
* NetApp storage discovery patterns for single-node and clustered environments using REST APIs.
* Support for managing large storage payloads on Linux and Solaris to prevent memory issues.

## Platform and Configuration Requirements

* **Windows:** Supports Windows Server 2008 and 2012 with DAS or NAS over Fibre Channel or iSCSI. Requires installation of fcinfo.exe, WMI, PowerShell enabled on MID Server, proper credentials, and optionally Windows Remote Management (WinRM) for Fibre Channel discovery.
* **Linux and Solaris:** Supports Solaris, CentOS, Ubuntu with DAS, NAS, SAN over FC or iSCSI. Requires SSH credentials with root or sudo access and MID Server credentials.

## Relationships and CMDB Integration

Discovery creates explicit parent-child and provider relationships between storage components, such as Storage Exports, Fibre Channel disks, iSCSI disks, and file systems. This relational mapping enhances the CMDB's accuracy and supports impact analysis.

## Practical Benefits for ServiceNow Customers

* Automatically populate and maintain detailed storage configuration items and their dependencies in the CMDB.
* Gain visibility into storage infrastructure across physical, virtual, and clustered environments.
* Enable streamlined troubleshooting, impact analysis, and capacity planning through accurate storage discovery and relationship mapping.
* Customize discovery for unsupported storage devices using Pattern Designer, enhancing flexibility.
* Leverage platform-specific discovery probes for comprehensive storage insights on various operating systems.  
Discovery collects information on Direct Attached Storage (DAS), Storage Area Networks (SAN), and Network Attached Storage (NAS).

Storage can be located on specialized devices, such as Storage Arrays, Fibre Channel Switches, iSCSI disks, or on host operating systems, including Windows, Linux, and Solaris.  
Discovery finds and maps dependencies for the following types of storage:

* Direct-attached storage (DAS), network-attached storage (NAS), or storage area network (SAN).
* NAS or SAN storage that is discovered via a Storage Management Initiative Specification (SMI-S) and Common Information Model (CIM).
* Virtual storage for VMware ESX servers and Linux Kernel-based Virtual Machines (KVM). Discovery maps this storage to the underlying physical storage.
{#c_Storage__ul_pfj_4fp_cr}

For storage devices that don't support SMI-S/CIM and aren't covered by an existing Discovery pattern, you can use Pattern Designer to create a custom infrastructure pattern. The pattern collects device information and populates configuration items (CIs) in the CMDB using REST APIs or CLI commands over SSH, depending on the device's supported interfaces.

For more information, see [Create or customize patterns](https://www.servicenow.com/docs/KX15Ano0vyhO9dAEZOp4iw "Create or modify a discovery pattern and define its basic attributes."). For REST-based discovery, see [Run discovery through an HTTP or HTTPS REST call](https://www.servicenow.com/docs/3xTHvsVZxhaL~o2fxdV46w "Discovery can classify devices using the HTTP(S) protocol. You can create your own HTTP classifier to find devices and access them with Basic Auth credentials, rather than using SNMP or SSH credentials.").

Discovery of storage via a host reconciles data and creates relationships between the host's
file systems and associated local storage devices. The local storage devices represent the
storage available to the host, whether it's directly attached or provided by Fibre Channel or
iSCSI. This reconciliation assumes that the storage server has been discovered first.  
Note:  
Tape storage drivers are not discovered.  
Discovery collects and creates CIs in the CMDB for the following information:

* File systems (local and NAS).
* Disks (both SAN disks and DAS drives).
* Fibre Channel (FC) HBAs and ports.
* Linux Volume Manager (LVM) volumes. LVM volume data resides in the Storage Pool \[cmdb_ci_storage_pool\] table.
* [Veritas Volume Manager](https://www.servicenow.com/docs/TfpKQ6ubA7bLvscFOTAG9Q "Discovery collects disk and volume information for Veritas Volume Manager (VxVM) on Linux hosts and maps file systems mounted on Veritas volumes to the upstream storage provider.") disks, subdisks, disk groups, plexes, and volumes.

{#c_Storage__ul_i25_4lh_ys}  
Note:  
For details about the discovery of direct attached or multipath block storage provisioned on a Linux host, see [KB0622583](https://support.servicenow.com/kb_view.do?sysparm_article=KB0622583).

## Probes, sensors, and patterns

* KVM - Storage Pools: identifies storage attached to KVM virtual machines.
* Linux - Storage: identifies storage attached to systems running the Linux operating system.
* Solaris - Storage: identifies storage attached to systems running the Solaris operating system.
* Windows - Storage 2008: identifies storage attached to systems running Windows 2008.
  * Windows - Storage 2008 - PS: identifies storage attached to systems running Windows 2008, using the PowerShell.
  * Windows - Storage 2008 - WMI: identifies storage attached to systems running Windows 2008, using WMI Runner.
  {#c_Storage__ul_uf5_35s_bt}
* Windows - Storage 2012: identifies storage attached to systems running Windows 2012 and later.
  * Windows - Storage 2012 - PS: identifies storage attached to Windows systems, using PowerShell.
  * Windows - Storage 2012 - WMI: identifies storage attached to Windows systems, using WMI Runner.
  {#c_Storage__ul_zrh_l5s_bt}
* VMWare - vCenter ESX Hosts Storage: collects information about ESX servers and creates relationships from datastores to underlying disks.
* Patterns for [NetApp storage
  discovery](https://www.servicenow.com/docs/Nl1tZVdHURpWMvxPCOVPaQ "Discovery and Service Mapping find NetApp servers and clusters using patterns. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."):
  * NetApp 7-mode: finds NetApp servers via REST with two nodes.
  * NetApp cluster mode: finds NetApp servers via REST when more than two nodes are connected through a cluster interconnect switch.

  {#c_Storage__ul_d5m_s4l_nbb}  
  Note:  
  For information on Probe to Pattern migration see the knowledge article [KB0694477](https://support.servicenow.com/kb_view.do?sysparm_article=KB0694477).
{#c_Storage__ul_alg_xmh_ys}

## Requirements {#c_Storage__section_c2h_lyy_1cb}

Windows
:
    * Supports the following configurations:
      * Windows Server 2012, DAS or NAS with Fibre Channel (FC) or Internet Small Computer System Interface (iSCSI).
      * Windows Server 2008, DAS or NAS with FC or iSCSI.
      {#c_Storage__ul_qzj_2ss_bt}
    * Install the fcinfo.exe tool on Windows 2008 and 2012 servers that attach to storage via FC.
    * Install Windows Management Instrumentation (WMI).
    * Enable Powershell on the MID Server host server.
    * Provide the instance with the necessary credentials to the host server.
    * Put the MID Server and the target machine in the same domain or add the target machine to the trusted host list on the MID Server machine.
    * Optionally, install [Windows Remote Management (WinRM)](https://msdn.microsoft.com/en-us/library/aa384372(v=vs.85).aspx) on the host server to discover Fibre Channel information. WinRM is on by default for Windows 2012 and Windows 2016 machines, but not for Windows 2008.
    {#c_Storage__ul_f2q_gmh_ys}

Linux
:
    * Supports the following configurations:
      * Solaris, DAS, NAS, or SAN with iSCSI
      * CentOS, DAS, NAS, or SAN with FC or iSCSI
      * Ubuntu Server, DAS, NAS, or SAN with iSCSI
      {#c_Storage__ul_k3l_5ts_bt}
    * Provide the device with SSH credentials that have root or sudo access.
    * Provide the MID Server with the necessary credentials to the host server.
    {#c_Storage__ul_vln_hmh_ys}

## Relationships {#c_Storage__section_r1f_fyy_1cb}

Discovery creates the following relationships for storage CIs:{#c_Storage__table_ffj_4qm_ns__entry__3}

| Parent Component | Relationship | Child Component |
|-|-|-|
| Storage Export \[cmdb_ci_storage_export\] | Exports to::Imports from | Storage Device \[cmdb_ci_storage_device\] |
| Fibre Channel Disk \[cmdb_ci_fc_disk\] | Provides::Provided by | File System \[cmdb_ci_file_system\] |
| iSCSI Disk \[cmdb_ci_iscsi_disk\] | Provides::Provided by | File System \[cmdb_ci_file_system\] |
[ ]

{#c_Storage__table_ffj_4qm_ns}
* **[Configure discovery of hosts with attached storage](https://www.servicenow.com/docs/eeBF12H9KGB4PxPUbX8W1g)**   
  Discovery can find information about UNIX, Linux, and Windows hosts with attached storage.
* **[Discovery data collected for storage via a host](https://www.servicenow.com/docs/mnqmOHzPGZKfosnfz7nqMw)**   
  Discovery gathers information about storage units that connect to Linux, Solaris, and Windows hosts via a local I/O port or Host Bus Adapter (HBA).
* **[Storage Discovery via SMI-S and CIM](https://www.servicenow.com/docs/rEuuQJh9k1pN0jdJlntdNQ)**   
  Discovery can explore storage devices that contain a Storage Management Initiative Specification (SMI-S) provider that is a specialized Common Information Model (CIM) server.
* **[Data collected for Veritas Volume Manager on Linux](https://www.servicenow.com/docs/TfpKQ6ubA7bLvscFOTAG9Q)**   
  Discovery collects disk and volume information for Veritas Volume Manager (VxVM) on Linux hosts and maps file systems mounted on Veritas volumes to the upstream storage provider.
* **[NetApp Server and Cluster discovery](https://www.servicenow.com/docs/Nl1tZVdHURpWMvxPCOVPaQ)**   
  Discovery and Service Mapping find NetApp servers and clusters using patterns. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
* **[Manage large storage payloads in Linux and Solaris](https://www.servicenow.com/docs/mK8cf5B3eS5_Gsr8LfB4tw)**   
  Large payloads for Linux and Solaris direct attached storage can cause out of memory errors if not configured to serialize the processing of the payload.
* **[Storage discovery examples](https://www.servicenow.com/docs/6WrQ3n9Tg02WOr3hglTXTQ)**   
  Discovery creates configuration items (CI) and CI relationships for physical and logical storage components attached to application and database servers or by fibre channel switched fabric.

