---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/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


---

# How CIM Discovery works

# How CIM Discovery works {#ariaid-title1}

* Release version: Yokohama
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 How CIM Discovery works

CIM Discovery in ServiceNow Yokohama release automates the classification and discovery of Common Information Model (CIM) storage systems on your network.
It leverages the Shazzam probe and wbem port probe to detect CIM servers and collect detailed storage system data, enabling comprehensive storage infrastructure visibility.
Show full answer Show less  

## Processing Flow

* The Shazzam probe initiates the wbem port probe during network discovery to detect activity on target ports (SLP 427, CIM 5989, and 5988).
* The wbem port probe uses an SLP query to identify wbem services, indicating SLP server presence, and retrieves service attributes and CIM interop namespaces.
* Namespace information is appended to port probe results and passed to the CIM Classify probe.
* The CIM Classify probe explores CIM servers to extract details such as VMware ESX serial numbers and relationships between SAN and NAS components.

## Key Components

* **wbem port probe:** Captures wbem service data and stores it in the `discoveryclassycim` table; configured under Discovery Definition \> Port Probes.
* **SLP query:** Detects wbem services on SLP servers and collects service attributes; linked within the wbem port probe configuration.
* **CIM - Classify probe:** Uses SLP data including namespaces to classify CIM storage systems; customizable via the `mid.cim.interop.namespace` system property for vendor-specific namespaces.

## Customization

The `mid.cim.interop.namespace` system property contains default storage namespaces used for discovery. If your environment uses additional or custom namespaces from different storage vendors, you should add them to this property as a comma-separated list to ensure proper classification.

## SMI-S and CIM Probes and Sensors

Multiple probes and sensors support detailed discovery of storage components, including:

* **CIM - Identity:** Identifies systems via CIM per SMI-S standards.
* **SMI - Array Controllers, Disks, Pools, Ports, Volumes:** Retrieve detailed storage array components.
* **SMI - NAS Head Components:** Discover virtual file servers, IPs, file servers (CIFS, NFS), and file shares.
* **SMI - Fabric and Fibre Channel Switch:** Discover SAN fabrics, zones, switches, and connections.
* **SMI - Storage Server and WBEM Service:** Gather SAN/NAS arrays, servers, WBEM service profiles, and SMI-S version details.

## Benefits for ServiceNow Customers

This CIM Discovery process enables ServiceNow customers to gain a comprehensive and automated view of their storage infrastructure, including SAN and NAS components, with rich details on relationships and configurations. It supports multi-vendor environments through namespace customization, facilitating accurate asset classification and improved CMDB accuracy.  
This is the processing flow for classifying Common Information Model (CIM) storage systems.{#r_HowCIMDiscoveryWorks__cim-classification-intro}

## Processing flow

1. The Shazzam probe launches the wbem port probe as part of network discovery.{#r_HowCIMDiscoveryWorks__li_cim_classification1}
{#r_HowCIMDiscoveryWorks__li_cim_classification1}
2. The wbem port probe detects activity on target ports SLP 427, CIM 5989 and 5988, and then examines the Service Registry Queries related list, at Discovery DefinitionPort Probes, for the SLP query. The base system provides this query to detect the service:wbem service type, which indicates the presence of an SLP server.{#r_HowCIMDiscoveryWorks__li_cim_classification2}
{#r_HowCIMDiscoveryWorks__li_cim_classification2}
3. The Shazzam probe launches a scanner for the WBEM service type. The scanner retrieves:
   * The attributes of the service from the SLP server.
   * The interop namespaces of CIM servers in the network.
   {#r_HowCIMDiscoveryWorks__ul_c11_bgq_bp}{#r_HowCIMDiscoveryWorks__li_cim_classification3}
{#r_HowCIMDiscoveryWorks__li_cim_classification3}
4. The scanner appends the namespace values it finds to the port probe results.{#r_HowCIMDiscoveryWorks__li_cim_classification4}
{#r_HowCIMDiscoveryWorks__li_cim_classification4}
5. The wbem port probe appends the SLP data it carries to the CIM Classify probes.{#r_HowCIMDiscoveryWorks__li_cim_classification5}
{#r_HowCIMDiscoveryWorks__li_cim_classification5}
6. The CIM Classify probe uses that information to explore the CIM servers. Figure 1. CIM Shazzam Processing Diagram ![CIM Shazzam Processing Diagram]() {#r_HowCIMDiscoveryWorks__ph_step-6-process-flow}
{#r_HowCIMDiscoveryWorks__ol_cwb_52q_bp}

## The wbem port Probe

The wbem probe stores the data it retrieves in the CIM Classification `[discovery_classy_cim]` table. To view the wbem port probe, navigate to Discovery DefinitionPort Probes.  
Figure 2. wbem port probe record

## SLP query

The SLP query detects the wbem service (service:wbem) on an SLP server and gathers the attributes of the service. To view the SLP Query record, open the wbem port probe record and select SLP Query from the
Service Registry Queries related list.  
Figure 3. SLP Query record

## CIM - Classify probe

The wbem port probe appends the SLP data it carries, including namespaces, to the CIM - Classify probe before launching it. The CIM classification probe extracts VMware ESX serial numbers and connector relationships between the
SAN and NAS components from CIM Servers in the network.  
To access the CIM classification probe, navigate to Discovery DefinitionProbes and select CIM - Classify from the list of probes.  
Note:  
The mid.cim.interop.namespace system property defines four default storage namespaces:

* interop
* root/interop
* root/pg_interop
* pg_interop
{#r_HowCIMDiscoveryWorks__ul_g3w_wq5_bz}If you're using multiple storage vendors with custom namespaces not specified as one of the defaults, add the new namespaces to the comma-separated list in this property. If you intend to continue using any of the default namespaces, make sure to include them in the property.  
Figure 4. CIM - Classify probe record

## SMI-S and CIM probes and sensors {#r_HowCIMDiscoveryWorks__section_r1z_q1z_1cb}

{#r_HowCIMDiscoveryWorks__table_mb5_nbm_b5__entry__2}

| Probe/Sensor | Description |
|-|-|
| CIM - Identity | Identifies a system via CIM per SMI-S. |
| SMI - Array - Controllers | Retrieves controller information. |
| SMI - Array - Disks | Retrieves storage disk information. |
| SMI - Array - File Shares | Enumerates NAS file shares from a storage server. |
| SMI - Array - Pools | Retrieves storage pools. |
| SMI - Array - Ports | Retrieves storage ports. |
| SMI - Array - Volumes | Retrieves storage volumes. |
| SMI - Fabric | Retrieves SANs, fabrics, zone sets, zones, zone aliases, endpoints, and connections. |
| SMI - Fibre Channel Switch | Retrieves FC switches. |
| SMI - NAS Head - Component Systems | Retrieves all virtual file servers in a NAS head profile. |
| SMI - NAS Head - File Server IPs | Retrieves IP addresses for each NAS file server. |
| SMI - NAS Head - File Servers | Retrieves NAS file servers such as Common Internet File System (CIFS) and Network File System (NFS). |
| SMI - NAS Head - File Shares | Retrieves file shares for each NAS file server. |
| SMI - Storage Server | Retrieves SAN and NAS arrays and servers. |
| SMI - WBEM Service | Retrieves WBEM Service information such as profiles and SMI-S version. |
[Table 1. SMI-S and CIM probes and sensors]

{#r_HowCIMDiscoveryWorks__table_mb5_nbm_b5}

*[\>]: and then