Has anyone got successful discovering Hitachi Storage

[RM10]

Team,

We are implementing discovery for Hitachi storage servers. I believe model is DS120.

Has anyone being successful running discovery for it? If yes please advise what is the approach and the steps you have taken?  

ServiceNow documentation talks about discovering CIM (SMI-S) server using CIM credentials for any storage discovery. Does same applies for Hitachi as well? 

Please advise.

Thanks.

[ServiceNow Tec2]

This has been resolved by ServiceNow Technical Support. Please refer to KB0754891 for more information.

[RM10]

Hello Servicenow Support Team,

I can't open this document. 

https://hi.service-now.com/kb_view.do?sysparm_article=KB0754891

[Brandon Lance]

Same here.  Sadly, this happens quite often.   

I opened a case to get access...  I'll post back the results.

[Brandon Lance]

Here is the information that was provided in that KB article:

SYMPTOMS -

When Discovering Pure Storage devices we repeatedly see the error/warning '"undefined.* - undefined - CIM namespace "undefined" not found.'

Environment

Kingston Patch 14
__________________________________
CAUSE -

CIM SIM-S - Storage Server for Mass Storage triggered MultiProbe CIM - Identity output

The sensor input data did not make it to the MultiProbe CIM - Identity output so parameters take on the value "undefined"

<parameter name="device_instance" value="undefined"/>
<parameter name="instance" value="undefined"/>
<parameter name="cidata" value="undefined"/>

Below is an example of how the parameter values should have been populated:

<parameter name="device_instance" value="PURESTORAGE_ObjectManager{CreationClassName='PURESTORAGE_ObjectManager',SystemName='10.1.43.94',SystemCreationClassName='PURESTORAGE_WBEMServerSystem',Name='51aa9609-4c59-433e-b269-e59bbbbe0e64'}"/>

<parameter name="instance" value="PURESTORAGE_ObjectManager{CreationClassName='PURESTORAGE_ObjectManager',SystemName='10.1.43.94',SystemCreationClassName='PURESTORAGE_WBEMServerSystem',Name='51aa9609-4c59-433e-b269-e59bbbbe0e64'}"/>

<parameter name="cidata" value="<CIData><data><fld name="sys_class_name">cmdb_ci_wbem_service</fld></data></CIData>"/>

These name-value pairs were used to issue the CIM Query for the next output and this is why we are seeing the following warning: 'undefined.* - undefined - CIM namespace "undefined" not found'
_____________________________________

RESOLUTION -

Disabled the custom CIM SIM-S - Storage Server for Mass Storage Devices

_____________________________________

ADDITIONAL INFORMATION -

We deactivated the newer Storage Server Probe to prevent Discovery from hanging:

Disabled the SMI 1.5 - Storage Server probe
Enabled older SMI - Storage Server probe

PRB1236133: The CIM exploration probes can take an excessive (12+ hours) amount of time

Next Steps:

If you are facing an issue and this KB article does not help to resolve it please feel free to reopen a new case with all of the exact issues you are facing so the correct team can help if you need.

--------

Based on the age of the KB data and it referring to Kingston, this may or may not be applicable any longer.  😞   That said, if the "older SMI - Storage Server probe" is still present, that proble may give some insight on how to develop a custom pattern to get the goods.  Of course, you'll need to likely create a custom probe to trigger that custom pattern to run....?   

If there was a way ServiceNow could just make it a tad more non-intuitive and convoluted it would all just work out.  😆  Oh, wait, not possible... 😛