Discovery issue with NetApp Storage Cluster-Mode Pattern

[SunilKumar_P]

Hi Experts,

I am trying to discover a storage device and I do see the classification is working as it is getting OID data. However, the device is not being created in the cmdb table.

Error: 

Identification Engine: Discovery status is FAILURE, CI Type cmdb_ci_storage_server cannot be created since there are no attributes defined. Debug pattern to understand why no attributes have been assigned.

Has anyone experienced this error? If yes, what was the fix?

[Pratiksha]

OOB their is a identification rule avl for storage server. Check in ci class manager if its present. Also, if its not try to get it from PDI

Hope it helps

[SunilKumar_P]

Hi @Pratiksha  - Thanks for your response. I will check and keep you posted.

[AJ-TechTrek]

Hi @SunilKumar_P ,

As per my understanding why this happens

During Discovery, the process is:
1. Classification → the device is correctly identified as a cmdb_ci_storage_server based on OID.
2. Exploration → the pattern runs to collect attributes (name, serial number, manufacturer, etc.).
3. Identification & Reconciliation Engine (IRE) → needs required attributes to either create or update the CI.
Your error:
“cannot be created since there are no attributes defined”
means:
* The pattern did not collect any attributes needed by the Identification Rule.
* So, the IRE cannot create the CI.

Solution which can help you on this
1. Debug the pattern
Go to:
Discovery → Patterns → Find the pattern for cmdb_ci_storage_server.
Click Debug Pattern:
* Select MID Server + IP address.
* Run the pattern.
* Watch what attributes get populated.
If the debug shows empty fields → the pattern isn’t getting data from the device.

2. Check which attributes are required
Go to:
Identification Rules → cmdb_ci_storage_server.
Typical required attributes:
Field Why
name Mandatory
serial_number Usually part of identification
manufacturer / model_id Often required
If these fields are empty, IRE won’t create the CI.

3. Update or fix the pattern
* Confirm the device supports the required SNMP OIDs.
* Update the pattern to:
* Use the correct OIDs.
* Add Set Parameter Value steps to map SNMP values to target fields (name, serial_number, etc.).
For example:
- SNMP OID → sysName → name
- OID for serial number → serial_number
If the OIDs are vendor-specific, add them manually.

4. Validate Discovery credentials
Make sure:
* The MID Server is able to SNMP walk the device.
* The right SNMP credentials are active and valid in Discovery Credentials.

5. Check identification rule itself
* Ensure the rule is active.
* Has at least one identifying attribute configured.
If it’s blank, the system won’t know what data to use to create/update CIs.

6. Test again
* Run Debug Pattern again.
* Confirm the payload shows required fields populated.
* Run Discovery → confirm the CI gets created.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025

[SunilKumar_P]

Hi @AJ-TechTrek - Thanks for your response. I will check and keep you posted.