Re: Multiple discovered VMs merged into one entry (335 Views)
Reply
Advisor
Robert Yung
Posts: 17
Registered: ‎11-20-2009
Message 1 of 4 (408 Views)

Multiple discovered VMs merged into one entry

While troubleshooting why several VM servers are missing in HP SIM (7.2+latest hotfixes), I've found that one VM entry contains all the IP addresses of all the missing VMs. Any idea what is going on and how do I resolve this? All the VMs are running Windows and are hosted on the same Windows 2008 R2 Hyper-V host.

 

If I run a single system discovery job for each of the missing VMs, it will find them and list them with the correct name, but a few minutes later, the entry will disappear and its IP will be added to as another identifier in one of the VMs.

 

If I run a discovery job with an entry for each system (using hostname), the first system will have a status of 'complete', but the rest will mysteriously have the same target name as the second system in the list and have a status of 'completed with minor errors'. The task log is:

 

********* Significant issues and overall target discovery/identification
status:
Minor: The discovered VM guest is not associated with the VM host. Verify that the supported HP Insight Management Agents or WBEM providers are installed on the host, and verify that the host has been discovered. For an association between Citrix XenServer host and its virtual machines, the HP Insight Control virtual machine management (VMM) software must be installed and the VM Host must be registered in VMM.


Normal: The system has valid hardware data (model, serial number, and unique identifier) and has been identified properly for SIM to manage.

 

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

* Starting identification process...

 

* Checking for known running web servers...

 

* Checking for SNMP protocol support on system...

 

Normal: The system did not respond to SNMP. Verify security settings and community strings in Options->Security->Credentials->System Credentials

 

* Checking for SNMPv3 protocol support on system...


Normal: The system did not respond to SNMPv3. Verify security settings and v3 credentials in Options->Security->Credentials->System Credentials


* Running HP ProLiant management agent identification...

 

Normal: The system does not support SNMP.

 

* Running SNMP base cluster identification using common cluster
MIB...

 

Normal: SNMP is not supported or globally disabled, skipping SNMP cluster identification.

 

* 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...


Normal: Got the system information from the WBEM / WMI providers and it has a valid WBEM credential.

 

* Running Virtual Machine (VM) Host (non HP Integrity VM Host) Identification...

 

Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM credentials may not be specified so skipping VM Identification.

 

* Running Storage identification...

 

* Storage identification completed.

 

* Running HP NetServer identification...

 

Normal: The system does not support SNMP.

 

* Running HP-UX SNMP identification...

 

Normal: The system does not support SNMP.

 

* Running OA Identifier which will discover systems in an enclosure if the automatic enclosure discovery option for OA is enabled...

 

Normal: A non-embedded operating system is detected so skipping the OA identification.

 

* Running XMLReply Identifier which will discover systems in a rack/enclosure if the automatic discovery option for the container node is enabled...

 

Normal: A non-embedded operating system is detected so skipping the Management processor identification.

 

* Running iLO Identifier which will discover the server if the automatic server discovery option for iLO is enabled...

 

Normal: A non-embedded operating system is detected so skipping the ILO identification.

 

* Running p-Class Identifier...

 

Normal: The system is not a p-Class so skipping p-Class identification.

 

* Running IPMI protocol identification...

 

Normal: Skipping IPMI discovery in favor of WBEM/SNMP discovery.

 

* Running SSH Protocol identification...

 

Minor: The system(s) do not have Secure Shell (SSH) installed or it is not running on the managed system(s).

 

* Running SSH Identification...

 

Normal: SSH Protocol is not enabled so skipping SSH Identification.

 

* Running WS-Man identification...

 

Normal: A non-embedded operating system is detected so skipping the WS-MAN identification.

 

* Running Monarch OA Identification...

 

Normal: The system is not a monarch OA so skipping monarch OA identification.

 

* Checking for System Management Homepage and other HP web agents...

 

Normal: The System Management Homepage is not installed on this system. It may not be supported.

 

* Running HP Serviceguard Identification...

 

Normal: The system is not part of HP Serviceguard cluster.

 

* Running SNMP System Type manager ...

 

Normal: The system does not support SNMP.

 

* Running SNMP subtypes identification...

 

* Resolving DNS names...

 

Normal: The fully qualified domain name was successfully resolved for the system.

 

* Checking if the Node is a Virtual Center...

 

Normal: Skipping MxVirtualCenter Identifier

 

* Running Virtual Machine Management (VMM) Plug-in Identification...

 

* Building system relationships...

 

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.

Trusted Contributor
Andrew_Haak
Posts: 385
Registered: ‎09-13-2013
Message 2 of 4 (348 Views)

Re: Multiple discovered VMs merged into one entry

Hello Robert,

Could it be that you cloned your virtual servers?

If The id/ serialiteit Is the same for these servers that would explain a lot.

Kind regards,

Andrew

Kind regards,

Andrew
Advisor
Robert Yung
Posts: 17
Registered: ‎11-20-2009
Message 3 of 4 (341 Views)

Re: Multiple discovered VMs merged into one entry

Yes, we do create our VMs from common master copies. Are you referring to the Windows SID? We don't do anything to reset that and it would be too late for existing systems. Anyway, is there a way to the configure the identification process to differentiate systems bases solely on the IP address or hostname? We had recently upgraded from 6.2 to 7.2 (now 7.3) and this behavior seems new.

 

And it is pretty hard to find these entries in SIM that are claiming multiple identities. In the list view, it only shows one IP per system and you have to open the properties of the system to see the multiple IP addresses. I don't even think there is a report option to list more than one IP per system. I don't really want to manually examine each entry. Any hint on this would be wonderful.

 

Thanks!

Robert

Trusted Contributor
Andrew_Haak
Posts: 385
Registered: ‎09-13-2013
Message 4 of 4 (335 Views)

Re: Multiple discovered VMs merged into one entry

Hello Robert,

You could print a data collection report for the server that has all of the IP adresses and then delete that server. Then discover one of the servers again and compare the datacollection report. See what field is identical. Perhaps you could post these reportage and we see if this record can be edited in the VM or SIM.

Kind regards,

Andrew
Kind regards,

Andrew
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.