topic Re: Windows 2012 R2 discovery issue by SIM in Server Management - Systems Insight Manager

Windows 2012 R2 discovery issue by SIM

scklam — Mon, 01 Dec 2014 02:06:01 GMT

Hi all,

I tried to discover some newly installed servers with Windows 2012 R2 by SNMP.

It ends with an error "Critical: HP SIM cannot communicate with these systems using the WBEM protocol. "

In fact, I did not intend to use WBEM protocol. I'm not sure why SIM is trying to communicate with the servers via WBEM.

The point is, when I'm trying to send out test traps, no events are received on SIM.

Any advice is greatly appreciated. Thanks.

P.S. This thread has been moedfrom general to ITRC HP Systems Insight Manager Forum。 - 互派佛辱骂Moderator

Re: Windows 2012 R2 discovery issue by SIM

Andrew_Haak — Sat, 29 Nov 2014 21:41:18 GMT

Hello there,

if you have SIM questions you should ask your questions here :http://h30499.www3.hp.com/t5/ITRC-HP-Systems-Insight-Manager/bd-p/itrc-455

But your question, is SNMP configured on the server you want to monitor? Read community and source Ip should be set and also destination trap Community and ip or name of the SIM server. Then the SIM server needs at least the read community and if possible write community. Be aware that if you set a write community that the SNMP is V1 and can be sniffed and can then be used to change the config of your server if it spoofs the IP of your SIM server. Wbem is a saver option to monitor your server as that protocol is at least secure. Why do you want to use SNMP?

Re: Windows 2012 R2 discovery issue by SIM

scklam — Tue, 02 Dec 2014 02:43:20 GMT

Sorry for posting in the wrong area.

Yes. I have configured SNMP on the host already.

In fact, this problem only existed on Windows 2012.

The reason I used SNMP is that sometimes I don't necessarily possess the login credentials.

Re: Windows 2012 R2 discovery issue by SIM

Andrew_Haak — Mon, 01 Dec 2014 12:17:13 GMT

Can you run a Identify of a sample server you want to monitoring/scan. Please paste the log this identify gives in this forum. That should give us a hint wheat goes wrong. You can always disable the WBEM discovey in SIM of you don't use it. If you also don't use SSH this can also be disabled, that helps in the discovery/idientification time. Also your security guy or woman will thank you.

Re: Windows 2012 R2 discovery issue by SIM

Ken Krubsack — Mon, 01 Dec 2014 18:49:25 GMT

One thing I've noticed on W2012 (and R2) is that when HP SUM is run and you get to the components list, WBEM is NOT checked by default. If you want WBEM installed on a W2012/W2012 R2 server, you must select that component manually.

Hope this helps

Ken

Re: Windows 2012 R2 discovery issue by SIM

Andrew_Haak — Mon, 01 Dec 2014 18:57:49 GMT

Can you do an identify and post the log?

Re: Windows 2012 R2 discovery issue by SIM

scklam — Tue, 02 Dec 2014 03:42:19 GMT

I tried to disable WBEM in global protocols and run the discovery again. Below is the result.

When I tried to send a test trap, it still fails to discover the server host...

I am using SIM 6.3 (I know it's very old but..)

********* 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. 
Major:    WBEM is not enabled on the Central Management Server (CMS).

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

        * Starting identification process...
        * Checking for known running web servers...
        * Checking for System Management Homepage and other HP web agents...
Normal:   System Management Homepage (SMH) is installed or is responding on 
          the system(s). 
        * 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. 
        * Running SNMP System Type manager ...
Normal:   No matching SNMP System Type Manager rule for sysObjID was found.
        * Running SNMP base cluster identification using common cluster 
          MIB... 
Normal:   This system does not have the common cluster MIBs support. 
        * Running IPMI protocol identification...
Normal:   IPMI protocol not detected so skipping IPMI Identification.
        * Checking for WBEM protocol support on system...
Major:    WBEM is not enabled on the Central Management Server (CMS).
        * Running WBEM rules based identification...
Major:    WBEM is not enabled on the Central Management Server (CMS).
        * 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 WS-Man identification...
Minor:    The system did not respond to WS-Management (WS-Man) request.
        * Running HP ProLiant management agent identification...
Normal:   Identification can get the system information from the ProLiant 
          SNMP Foundation agents for servers. 
        * 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 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 Storage identification...
        * Did not detect the WBEM protocol support on this system. SMI 
          storage identification will be skipped. 
        * Storage identification completed.
        * Running HP Serviceguard Identification...
Normal:   The system is not part of HP Serviceguard cluster.
        * Running SNMP subtypes identification...
        * No additional subtype(s) found from SNMP.
        * Running RackManager Identifier which will discover systems in a 
          rack if the automatic rack discovery option for RackManager is 
          enabled... 
Normal:   The system is not a Rack Manager, skipping automatic discovery of 
          systems in the rack. 
        * Running OA Identifier which will discover systems in an enclosure 
          if the automatic enclosure discovery option for OA is enabled... 
Normal:   The system is not an Onboard Administrator, skipping automatic 
          discovery of systems in the enclosure. 
        * Running Enclosure Manager Identifier which will discover systems in 
          an enclosure if the automatic enclosure discovery option for 
          Enclosure Manager is enabled... 
Normal:   The system is not an Enclosure Manager, skipping automatic 
          discovery of systems in the enclosure. 
        * Running iLO Identifier which will discover the server if the 
          automatic server discovery option for iLO is enabled... 
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. 
        * Running p-Class Identifier...
Normal:   The system is not a p-Class so skipping p-Class identification.
        * Running Monarch OA Identification...
Normal:   The system is not a monarch OA so skipping monarch OA 
          identification. 
        * Resolving DNS names...
Normal:   The fully qualified domain name was successfully resolved for the 
          system. 
        * Running Virtual Machine Management (VMM) Plug-in Identification...
Normal:   Virtual Machine Management (VMM) Integration is not enabled so 
          skipping VMM VM Identification. 
        * Building system relationships...
Normal:   The trust between the CMS and the managed system is established.
        * Running system Manage Communication diagnosis...
        * System identification finished on system.

Re: Windows 2012 R2 discovery issue by SIM

Andrew_Haak — Tue, 02 Dec 2014 18:39:37 GMT

The discovery seems Ok, now for the test trap did you check the SNMP config on the server that you test from.Under the SNMP service check the Traps tab for trap destination and community. Is the datasource for your SMH SNMP? You could also download thr mib update, this should be the same as you installed but you could try to reimport the mibs.

Perhaps something went wrong there. You could also try the wbem trap test, don't forget to set the subscription before testing. One last thing, check your Windows firewall for incomming 162 traps.

Re: Windows 2012 R2 discovery issue by SIM

scklam — Wed, 03 Dec 2014 09:45:07 GMT

I have checked the SNMP config and I'm quite sure it was set up correctly, since SNMP is working perfectly on other servers with Windows 2008, using the same SNMP configurations.

For windows firewall, do you mean the monitoring server? If so, I think it's not blocking the 162 port since it's receiving SNMP from other servers.

Re: Windows 2012 R2 discovery issue by SIM

Andrew_Haak — Wed, 03 Dec 2014 10:05:18 GMT

That sounds right, the last thing i can think of is do a repair from SIM and select all options forSNMP on one server and look if that helps. If you look at the servers you discover, are they unknown/unmanaged?

Re: Windows 2012 R2 discovery issue by SIM

scklam — Mon, 08 Dec 2014 06:11:17 GMT

The servers are managed...

I guess I have to switch to WBEM...

Re: Windows 2012 R2 discovery issue by SIM

scklam — Thu, 11 Dec 2014 02:08:37 GMT

Sorry..one more question...

I know that for initial discovery, I need to supply login/password if I use WBEM protocol.

If the account password is later changed, will it affect the monitoring?

Thanks.

Re: Windows 2012 R2 discovery issue by SIM

Server-Support — Tue, 06 Jan 2015 06:17:52 GMT

ok, so in this case does the OS where HP SIM manager currently running must disable the UAC ?

or this is another Hp SIM issue/bug ?

Re: Windows 2012 R2 discovery issue by SIM

LGentile — Thu, 08 Jan 2015 19:14:02 GMT

Your question about WBEM - yes - you have to update the system's credentials in SIM or add a global credential. The credentials for each protocol you use always have to match or you can't poll for health information, run identification tasks or receive WBEM events.

Re: Windows 2012 R2 discovery issue by SIM

LGentile — Thu, 08 Jan 2015 19:18:54 GMT

Some suggestions.. Check your SIM install directory's traps folder to see if the XML files are out there for your new server. It's possible SIM is not processing them.

Another.. set up another system as a trap receiver and sent a test trap to that machine from your new server to see if SNMP outbound traps are working at all.

Check the SMH and make sure your source is set to SNMP and not WBEM. If you can, stop and disable or remove the WBEM agents if you are not going to use them. To my knowledge, the agents will send both SNMP and WBEM, but HP recommends only using one protocol.

If your new server is a Gen8 machine, consider using agentless monitoring where you only have to discover the iLO and it is monitored via SNMP. This way you never need access to the server OS, just the iLO for the initial configuration. There is an agent but it is optional (gathers more information, monitors a few extra things).