Storage Discovery 3PAR 8440

abusch · ‎11-23-2015

Has anybody discovered a 3PAR 8440, OS version 3.2.2 ?

We are new to storage discovery. I've created the CIM credential in ServiceNow and granted it admin privileges on a sub-prod device. Are we doing something fundamentally wrong? Or do we need to do some extra work to support this device? The CIM probe is returning:

Thanks,

Tony

doug_schulze · ‎11-23-2015

Tony,

Error reads that the interop name space (think of the root of the CIM tree) is invalid for the device you are querying. Check with the admin what the valid name space is and if its different you can update the sys_property mid.cim.interop.namespaces to include yours..

erikgardner · ‎04-28-2016

I had the same problem and error code and I changed the wbem port probe's default value for the InteropSchemaNamespace to the 3PAR supported namespace, root/PG_Interop

var resultInfoMap = {

'InteropSchemaNamespace': { parameterName: 'interopNamespace', defaultValue: 'root/PG_interop' }

};

This made the CIM - Classify probe start giving results but now I'm stuck further down the line.

I'm getting an error on "SMI -Array - File Shares" probe:

TPD_StorageSystem{CreationClassName='TPD_StorageSystem',Name='2FF70002AC006DDD'}.CIM_HostedShare.* - CIM_HostedShare - CIM_ERR_INVALID_PARAMETER: CIM_HostedShare

which I think maybe causing CIM - Storage Server CIMProbe to fail next... not sure though....

doug_schulze · ‎04-28-2016

With the latest release you can also use/add the property mid.cim.interop.namespaces and comma separate the different namespaces you might have in your environment.

Niranjan Danda · ‎04-21-2017

Hi Doug,

When running storage discovery i am getting "session timed out" warning while processing "CIM - Identity - WBEM Service probe".

Can you please help me out in resolving this issue.

Here is my ECC queue input payload

Thanks in advance,

Niranjan.