Why are Storage Servers being identified as WBEM Service?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2016 04:33 PM
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.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2016 12:14 PM
Guyz - Any updates on this please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2016 12:27 PM
Are you getting a response from your CIM classify probe that matches the criteria in the classifier?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2016 01:04 PM
doug.schulze - Thanks for your response.
Yes, its being classified using "CIM Classify". Below is the data being fetched:
sys_class_name: cmdb_ci_storage_server
firmware_version:
manufacturer: <manufacturer_sys_id>
cim_object_path: <COMMON_across_all_servers_being_identified_as_WBEM_service>
ip_address: <DIFFERENT_across_all_servers_being_identified_as_WBEM_service>
serial_number: <DIFFERENT_across_all_servers_being_identified_as_WBEM_service>
name: <COMMON_across_all_servers_being_identified_as_WBEM_service>
_cimObjectName: <COMMON_across_all_servers_being_identified_as_WBEM_service>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2016 04:12 PM
Did this makes sense? Any leads from this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2016 09:36 AM
Hi doug.schulze - Please let me know if you have any inputs.