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.

[glennpinto]

See if this recording targeted on Storage Discovery can assist.

https://youtu.be/9V_XhzG7CoA

[snowenthusiast]

Thanks Glenn. Let me go through this and reply back.

[snowenthusiast]

Hi glennpinto ,

Thanks a lot for sharing the video. It was immensely helpful in sharing a overview of storage discovery, however, it doesn't tells me why storage servers are only being identified as WBEM service in my case. I understand WBEM service is a implementation of CIM and it means that CIM is running on those servers but why:

1. They're being identified under one CI (gets updated by the last IP details)
2. They're being identified as "WBEM service" only (all 10 IP's) and they roll up to a single CI

Thanks.

[snowenthusiast]

Also, I just checked that serial numbers returned by CIM query are all unique..still they're being identified as one CI..coz probably they have same CIM path name? I see "Storage Server" identifier has 3 methods - findByObjectPath, findByName and findBySerial. Probably, its searching by name and appending it as a WBEM service to that ONE CI?