Discover windows VM host

ashish1 — Fri, 25 Mar 2016 18:52:28 GMT

HP SIM ver 7.5

I have added list of some known host into discovery. Discovery task showing following errors

********* Significant issues and overall target discovery/identification
status:
Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.
Normal: Identification status is only available for servers, workstations,
or desktops, where monitoring is enabled.

********* Additional results (listed for information only):

* Starting identification process...
* Checking for known running web servers...
* Checking for SNMP protocol support on system...
* Checking for WBEM protocol support on system...
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.
Minor: The Central Management System (CMS) cannot communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol, Identification will try to identify Windows systems using
the WMI Mapper as proxy; for Linux and HP-UX systems, check
credentials by going to Options->Security->Credentials->System
Credentials. For Linux systems also check if the HP WBEM provider
is installed.
* Running WBEM rules based identification...
Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...

Minor: The system responds to the HTTP request but cannot get the XML
output. It is normal for servers not to get the XML data.
Minor: If the http communication from CMS to target is working, but if it
is found to be slow then try increasing the Default connection
timeout parameter for http in global protocol settings.
* Running p-Class Identifier...

Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

Am I missing on basic configuration?

Re: Discover windows VM host

n0kia — Fri, 25 Mar 2016 22:26:10 GMT

To understand the issue more, are you trying to discover a physical proliant server?

Do you have snmp configured and or using wbem?

Re: Discover windows VM host

ashish1 — Mon, 28 Mar 2016 12:40:03 GMT

No SNMP on the windows server but would like to use wbem ..

Re: Discover windows VM host

n0kia — Mon, 28 Mar 2016 18:21:46 GMT

If it's a Physical Machine then I would use the HP SPP to install the necessary drivers /firmware then install the providers that you want to use.

If it's already installed and just need the providers then use: http://h17007.www1.hp.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx

If it's a Windows VM. We don't have any providers for VMs

Re: Discover windows VM host

Andrew_Haak — Tue, 29 Mar 2016 09:43:30 GMT

Just to be complete, if your server is a Gen8 or newer. Look for the Agentless Management Software.

topic Re: Discover windows VM host in Server Management - Systems Insight Manager

Discover windows VM host

Re: Discover windows VM host

Re: Discover windows VM host

Re: Discover windows VM host

Re: Discover windows VM host