CIM Storage discovery issue for Dell Unity

Gopi Ramesh
Tera Contributor

Hi Everyone,

 

We are not able to discover the logical nas servers in dell unity boxes and we are observing below warnings. We are in Yokahama version

 

CIM_RegisteredProfile.* - CIM_RegisteredProfile - No response received.

 

Kindly let me know if anyone faced this issue and resolved.

3 REPLIES 3

AJ-TechTrek
Giga Sage
Giga Sage

Hi @Gopi Ramesh ,

 

As per my understanding the Problem recap is -


You’re running Discovery on Dell Unity storage arrays, trying to get logical NAS servers discovered.
You’re seeing this warning:

CIM_RegisteredProfile.* - CIM_RegisteredProfile - No response received.


This typically means:
* The SMI-S / CIM protocol is enabled in the probe/pattern,
* But the Dell Unity device isn’t responding to CIM queries,
* Or the device doesn’t fully support the standard CIM class being queried.

 

Step-by-step solution:
1. Verify prerequisites and connectivity
* Ensure the Dell Unity box actually has SMI-S enabled.
* Confirm the SMI-S Provider or CIMOM is running on the Dell Unity management controller.
* Confirm the MID Server can reach the SMI-S endpoint on the correct port (usually 5988 for HTTP, 5989 for HTTPS).
* Try using a basic CIM client (e.g., wbemcli or SMI-S test tool) to query the device from the MID Server host to check if CIM responds at all.

 

2. Check credentials
* Validate the SMI-S / CIM credentials configured in ServiceNow Discovery:
* Must have sufficient privileges to access CIM_RegisteredProfile and related namespaces.
* If in doubt, test these credentials separately.

 

3. Confirm probe & pattern configuration
* Go to:
* Discovery → Patterns → Storage patterns
* Check if there is a pattern specifically for Dell Unity NAS logical servers.
* By default, ServiceNow uses generic storage patterns based on SMI-S.
* Dell Unity may not fully support certain standard SMI-S profiles (especially CIM_RegisteredProfile) → so some classes might return "No response".

 

4. Alternative approach using REST
Dell Unity supports a REST API that is far richer and faster than SMI-S.
ServiceNow Storage discovery from Washington DC & Yokohama supports Dell Unity via REST (if pattern is updated).
Steps:
* Ensure the MID Server can access the Dell Unity REST endpoint (default port 443).
* In Discovery credentials, add a REST credential with the Dell Unity username/password.
* Modify the discovery pattern or use the out-of-the-box Dell Unity REST-based pattern (if available).

 

5.Patch or Content Update
* Make sure the latest Storage Discovery Content Pack is installed:
* Go to: System Applications → All Available Applications → All
* Filter: Storage Discovery
* Sometimes, Dell Unity support is enhanced in newer content packs rather than core platform.
* Check if Yokohama patch or later content packs add better support for Dell Unity NAS.

 

6. Troubleshoot logs
* Check Discovery → Status → Discovery Log.
* Look for:
* MID Server errors
* Pattern errors
* Credential failures
These logs will tell you if the device is responding partially, or not at all.

 

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
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community MVP 2025

Thank you AJ for detailed explanation. We verified the port 5989 port and it is connecting fine. The credentials are working perfect as Storage server as entity getting discovered. We observe this issue after Yokahama upgrade.

 

I dont see Dell Unity Rest based pattern available in my instance. we are currently running with 1.27 version which is latest and I dont see storage discovery pack as well in our applications. Can you suggest?

AJ-TechTrek
Giga Sage
Giga Sage

Hi @Gopi Ramesh ,

 

Please also cross check the Discovery and Service Mapping Pattern Plugin is up to date with Latest version, Might be that is causing issue.

 

Otherwise check with ServiceNow or HI Support once on that.

 

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
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
ServiceNow Community MVP 2025