Why are Storage Servers being identified as WBEM Service?

[snowenthusiast]

Hi,

We're implementing discovery in our company and today ran discovery for storage servers. Initially, we thought we were missing servers but then we 'discovered' that they're being identified as WBEM Service. Why is this happening? Is there a way to make them identify as storage servers?

Thanks in advance.

[doug_schulze]

I would have to assume your payload from the classify isnt meeting the criteria for the storage server class.   If it is, then contact support and they can walk you through why its not working..

[snowenthusiast]

Ok. Thanks.

[coryk]

Snowenthusiast - did you get this fixed?   I'm having the same issues and before going to support for the issue, i thought I would ask if they fixed it for you.

[avinashrvn]

Hello Cory/snowenthusiast,

We are ended up with a similar situation, It is being classified as WBEM Service with the below error:

error="CIM_RegisteredProfile{{RegisteredName='Array'}}.CIM_ElementConformsToProfile{{ResultClass:'CIM_ComputerSystem'}}.ElementName - CIM_RegisteredProfile - Authentication failed." probe_time="188" result_code="900000">

We are trying to run discovery for EMC vmax using local credentials created on the storage device. We validated the credentials by doing direct login (Using IE) and those seems to be working. Storage team confirmed SMI-s provider is already present on storage device.

Please confirm if you had any response from support and configuration steps you followed for discovery of storage devices. Thanks!

[Jay118]

I would like to know the answer to this.