Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

Data collection found no data

ccoho
Advisor

Data collection found no data

I just installed SIM 7.5, I have all of my servers updated with the most recent WBEM, SMH, agentless management.  SMH is configured to use WBEM.  I've confirmed a test WBEM notifications gets pushed to SIM (and emailed if appropriate)... but on most of my servers under events every night when data collection runs I get "Data collection found no data":

"The data collection task could not find any data to collect.  the target system may not have been running any supported instrumentation protocol, such as SNMP, WBEM or DMI."

If I look at the task itself i see:

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

Firewall is disabled on that machine as well.  Credentials are correct and that user has administrator priv on that machine.

Any thoughts?

10 REPLIES
ccoho
Advisor

Re: Data collection found no data

In addition, if I look at the Bi-Weekly Data Collection task, most of my servers are failing with:

"This system does not have any supported instrumentation.
Root Cause: Identification failed to detect any supported instrumentation (e.g. SNMP, DMI, WBEM) on this system.
Corrective Action: Check network and configuration of target system. Check the following pages to ensure appropriate credentials and data are provided: Global Protocol Settings, System Protocol Settings, WMI Mapper Proxy. Rerun Identification and then Data Collection. "

I can confirm that WBEM and SNMP are both installed on the target machines, SNMP is configured (if I set the SMH to use SNMP and do a test trap it comes through), and the SMH is currently set to WBEM.

 

Andrew_Haak
Honored Contributor

Re: Data collection found no data

Hello,

 

Can you run a identification of one server and post the log ? Are the servers Windows servers? Or do you have ESX or Linux like OS? What type of hareware do you have ?  Gen 6,7,8 or 9 ? For windows server you can use either SNMP or WBEM not both. Traps do not mean that you can read the server. Is the discovered server idientified as a Proliant.?

Kind regards,

Andrew
ccoho
Advisor

Re: Data collection found no data

These are windows servers, a mix of a few older G6 but mostly 8's and 9's.  WBEM is what is set on the SMH, I meant that SNMP was configured on the server and the SNMP service was running.  The servers do appear to be discovered with most or all details, but every time they are collected that is the error I get.  I did go through and set up SNMP on all of the iLo's, which seems to be helping, but I sitll don't understand why WBEM isn't working.  Here is the log from one of the servers identification:

 

********* Significant issues and overall target discovery/identification
status:
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Normal: System(s) have been successfully identified.

********* 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 responded to an SNMP request; it supports SNMP Protocol
and has a valid read community string.
* 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: Identification can get the system information from the ProLiant
SNMP Foundation agents for servers.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: This system does not have the common cluster MIBs support.
* 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...
* This system has some storage related information and additional
storage systems may be added.
* This system has some storage related information and additional
storage systems may be added.
* This system has some storage related information and additional
storage systems may be added.
* This system has some storage related information and additional
storage systems may be added.
* This system has some storage related information and additional
storage systems may be added.
* Storage identification completed.
* Running HP NetServer identification...
Normal: System supports the NetServer SNMP agent, adding system type.
* Running HP-UX SNMP identification...
Normal: System does not have the HP-UX SNMP agents installed.
* 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...
Major: Using SSH Protocol in discovery is disabled on the Central
Management Server (CMS).
* Running SSH Identification...
Major: Using SSH Protocol in discovery is disabled on the Central
Management Server (CMS).
* 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: System Management Homepage (SMH) is installed or is responding on
the system(s).
* Running HP Serviceguard Identification...
Normal: The system is not part of HP Serviceguard cluster.
* Running SNMP System Type manager ...
Normal: No matching SNMP System Type Manager rule for sysObjID was found.
* Running SNMP subtypes identification...
* No additional subtype(s) found from SNMP.
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Node is not a Virtual Center Node
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
Major: In order to access Secure Sockets Layer (SSL) based tools such as
System Management Homepage and Version Control Repository Manager
on remote systems without performing an additional sign-in, you
need to establish trust between the Central Management Server (CMS)
and the managed system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

 

Andrew_Haak
Honored Contributor

Re: Data collection found no data

So most problems probably are with the gen8 and gen9. Things changed quite a bit since gen8. This was the first ILO4 machine and discovery of such servers should not be done by discovering the OS/server.

The server should not have a SMH, WBEM agent and/or SNMP and snmp subagents. These servers should only have the agentless Management software.  The ILO should be discovered and the datacollection of the ILO will add the server. The server talks with the AMS service on the server and give OS information.

so first delete your Gen8 and newer servers and ILO's, then readd the ILO's. This should work. The only real problem that you can have is that you have credentials in the general settings and that after some time the servers that were added by the datacollection of the ILO. When this happens you get your errros back with the datacollection.

The only real solution is to create seperate discovery jobs for servers older then the Gen8 server and set windows discovery credentials in that specific job. This way the working Gen8 and above will not try to use the credentials. I also changed the datacollection job to run this job on everything exept gen8 and above servers. This can be done by creating a new collection that matches this criteria and change the datacollection job to use the new collection.

Kind regards,

Andrew
ccoho
Advisor

Re: Data collection found no data

Ok Thank you, I'll give that a try

NJK-Work
Honored Contributor

Re: Data collection found no data

Andrew - is it correct that the iLO (agentless monitoring) still uses SNMP?  So for our servers/iLOs behind firewalls we would need to open up SNMP ports?  Seems like a step backwards to keep using SNMP....but I guess if that is what is required that is what we would need to do.

Thanks

NK

n0kia
Valued Contributor

Re: Data collection found no data

Hello Nelson,

Agentless means that the host server is free of agents and that job is now handled by ilo4 via snmp port 161/162.

If you still want host OS information from the servers than you would want to install the Agentless Management Service on the OS/Server side to give you those details.

The AMS is not an agent but a service that talks through the ILO Driver then through the PCIe Bus.

Andrew_Haak
Honored Contributor

Re: Data collection found no data

Correct, AMS is the only needed piece of software needed from a monitoring point of view. Wether you call it a service or agent does not realy mattor the AMS has no web user interface and is used by the ILO. The ILO needs to be configured for SNMP. Login to the ILO, go to Administration > Management and set the following :
Enable AgentlessManagement
Read Community : yourcommunitystring (can be Public)
Trap Community : yourcommunitystring (can be Public)
SNMP Alert Destination(s): the IP of your SIM server. 
This way you can monitor your server from an OOB if you place your ILO in such a network.
 
Kind regards,

Andrew
NJK-Work
Honored Contributor

Re: Data collection found no data

Thank you for the information.

NK

Andrew_Haak
Honored Contributor

Re: Data collection found no data

You're welcome !

Kind regards,

Andrew