Storage Discovery 3PAR 8440

[abusch]

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:

<results error="CIM_RegisteredProfile{{RegisteredName='Array'}}.CIM_ElementConformsToProfile{{ResultClass:'CIM_ComputerSystem'}}.ElementName - CIM_RegisteredProfile - CIM_ERR_INVALID_NAMESPACE: interop" probe_time="117"><result/>

Thanks,

Tony

[Niranjan Danda]

Hi eric,

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 i have tried to increase the timeout limit but found noluck.

Thanks in advance,

Niranjan.

[terrywang]

This might depend on what device you are discovering. On top of my mind NetApp SMS-S servers are extremely slow, which requires changing 5 second connection timeout to 10 minutes.

I recommend you to create an incident with ServiceNow technical support.

[terrywang]

Hi Anthony,

This issue is documented in:

PRB887860

Workaround:

Go to:

/discovery_port_probe.do?sys_id=bb551dbd37331000627d8c00dfbe5d89

On around line 4, there is a "defaultValue" being set to 'interop".

Try changing that to "root/pg_interop".

I.E. change:

'InteropSchemaNamespace': { parameterName: 'interopNamespace', defaultValue: 'interop' }

to

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

Please also make sure "Replace on Upgrade" field is set to "True" for the records that you need to change.

This guarantees they will be updated during platform upgrade.

If the "Replace on Upgrade" field doesn't show on the form, you can change the form layout and add this field.

Caution

=======

1) By modifying the default value to "root/pg_interop", this will change the default namespace to use to be "root/pg_interop".

2) While either of these methods will work to discover the HP 3PAR device, if you try this on other CIM devices that are looking for the "interop" namespace, this will not work.

The issue is that the port probe only checks against the open ports once, and the port probe only triggers one Classify probe. And also, since this Classify probe can only contain one namespace parameter, we have been unable to check against multiple namespace parameters within one probe.

[nikita_mironov]

Hi Terry

Many thanks for the explanation regarding the default name space in CIM probe. What in your openion shall be a workaround if I need to work not only with HP 3PAR devices using namespace "root/pg_interop" but also with others which use for example "interop"? Any hint here ?

[Brad Kallmeyer1]

I'm also having issues with discovery of HP 3PAR devices, it appears that SN is not receiving all the needed information back from the probes. I'm not sure where to turn with this.