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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Storage discovery

# Storage discovery {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 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 Yokohama release enables automated identification and mapping of various storage types including Direct Attached Storage (DAS), Storage Area Networks (SAN), and Network Attached Storage (NAS).
It supports discovery on specialized storage devices such as Storage Arrays, Fibre Channel Switches, iSCSI disks, and host operating systems like Windows, Linux, and Solaris.
This process collects detailed information and creates Configuration Items (CIs) and relationships in the CMDB, facilitating comprehensive visibility into physical and virtual storage infrastructures.
Show full answer Show less  

## Key Features

* Discovers and maps dependencies for DAS, NAS, SAN, and virtual storage on VMware ESX and Linux KVM.
* Uses Storage Management Initiative Specification (SMI-S) and Common Information Model (CIM) protocols for NAS and SAN discovery.
* Reconciles host file systems with local storage devices, assuming prior discovery of storage servers.
* Collects CIs for file systems, disks (SAN and DAS), Fibre Channel HBAs and ports, Linux Volume Manager (LVM) volumes, and Veritas Volume Manager components.
* Supports multiple probes and sensors tailored for various operating systems (Linux, Solaris, Windows 2008/2012) and virtual environments.
* Provides specialized discovery patterns for NetApp storage in both 7-mode and cluster mode configurations.

## Requirements

* **Windows:** Supports Windows Server 2008 and 2012 with DAS or NAS using Fibre Channel or iSCSI; requires tools such as fcinfo.exe, WMI, PowerShell, and optionally WinRM for Fibre Channel data collection; proper credentials and domain/trusted host configurations are necessary.
* **Linux and Solaris:** Supports Solaris, CentOS, Ubuntu Server with DAS, NAS, or SAN using Fibre Channel or iSCSI; requires SSH credentials with root or sudo access and appropriate MID Server credentials.

## Relationships Created

Discovery establishes key relationships among storage CIs, such as:

* Storage Export linked to Storage Device via export/import relationships.
* Fibre Channel and iSCSI Disks linked to File Systems they provide storage for.

## Additional Capabilities and Considerations

* Supports discovery of storage through hosts running UNIX, Linux, and Windows by gathering data from local I/O ports and HBAs.
* Discovers storage devices exposing SMI-S providers for enhanced storage device exploration.
* Collects detailed Veritas Volume Manager data on Linux, mapping volumes and file systems to underlying storage.
* Enables discovery of NetApp servers and clusters with updated Discovery and Service Mapping patterns.
* Includes recommendations for handling large storage payloads on Linux and Solaris to avoid memory issues by serializing processing.

## Practical Benefits for ServiceNow Customers

By leveraging Storage Discovery, customers gain a unified and accurate view of their storage infrastructure directly within the CMDB. This visibility supports better configuration management, impact analysis, and operational efficiency by automatically creating detailed storage CIs and their relationships. The discovery process reduces manual data entry, ensures data consistency, and enables effective management of complex storage environments spanning physical, virtual, and clustered storage 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}

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/O988yvemSiEZXn7ji_7qCA "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/lH0lztamBDucoNcXb5xjnA "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/DB6hAG1FgF2eZbkR7dyDHg)**   
  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/0tRSBKPKVUJA0hW3tVdNCw)**   
  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/iA6WoJFKEpYo5QwKfDaYrA)**   
  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/O988yvemSiEZXn7ji_7qCA)**   
  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/lH0lztamBDucoNcXb5xjnA)**   
  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/Mj9A3Pc9faK~ysfezxbxcA)**   
  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/SWAVutv~1QRHhg4_lRzdtg)**   
  Discovery creates configuration items (CI) and CI relationships for physical and logical storage components attached directly to application and database servers or by fibre channel switched fabric in a multi-path configuration.

