topic Re: WBEM traps in Server Management - Systems Insight Manager

WBEM traps

Martiquet — Tue, 01 Feb 2011 14:58:08 GMT

Hi.
When using SNMP, CMR receives all traps from managed servers.
When using WBEM (which I assume is possible), nothing happens.

Is openssh mandatory whith Wbem ?

I can I debug the "trap sending process ?"

Re: WBEM traps

NJK-Work — Tue, 01 Feb 2011 17:19:11 GMT

Hello,

It's been a while since I looked at this stuff. But from my recollection, you have to subscribe to WBEM events in the SIM console.

Click on "Options", then "Events" and then "Subscribe to WBEM Events" on the menu. Then provide the appropriate information.

I am still using SIM 5.2, so this may be a bit different in SIM 6.2 (assuming you are using that version).

Nelson

Re: WBEM traps

Martiquet — Wed, 02 Feb 2011 08:23:21 GMT

"Subscribe to WBEM Events" was already performed, for every serveur in my collection.

Thank you.

Re: WBEM traps

shocko — Wed, 02 Feb 2011 09:37:21 GMT

What account have you used to subscribe to the events? Does it have the correct permissions on the box i.e. member of DCOM users or administrators etc and also the appropriate WMI namespace permissions?

Run a system identification on one of the affected boxes and postthe results.

Re: WBEM traps

Martiquet — Wed, 02 Feb 2011 14:39:39 GMT

Hello.
1) I use a domain admin account
2) here is the result of identification

********* Significant issues and overall target discovery/identification
status:
Minor: The discovered blade is not in an enclosure. For c-Class
enclosures, verify that the supported OA firmware version is
installed and verify that the OA has been discovered in HP SIM. For
p-Class enclosures, verify that the iLO firmware and the HP Insight
Management Agents on the server are installed and verify that the
iLO has been discovered in HP SIM.
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 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 did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
Credentials
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* 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...
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 WS-Man identification...
Minor: The system did not respond to WS-Management (WS-Man) request.
* Running HP ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running HP NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Normal: The system can be logged in using SSH protocol; has a valid SSH
credential.
Normal: OS Name is identified by the SSH 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 Serviceguard Identification...
Normal: The system is not part of HP Serviceguard cluster.
* Running SNMP subtypes identification...
* 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.
* idPluginStart.EMIdentifier
Normal: em.skip.auto.disc
* 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...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Normal: The trust between the CMS and the managed system is established.
* Running system Manage Communication diagnosis...
* System identification finished on system.

Re: WBEM traps

Martiquet — Wed, 02 Feb 2011 14:42:38 GMT

NB : the "properties" page for all ther servers works fine.
The only issue is that I have no event in the CMS

Re: WBEM traps

Martiquet — Wed, 02 Feb 2011 15:04:42 GMT

Also,
I find these errors :
Event filter with query "select * from HP_InitCompleteEvent" could not be reactivated in namespace "//./root/wmi" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

Event filter with query "select * from HP_McSystemEvent" could not be reactivated in namespace "//./root/wmi" because of error 0x80041010. Events cannot be delivered through this filter until the problem is corrected.

on all my servers (including CMS).
And the requested wmi classes are not present. Not sure it should be the problem...

Re: WBEM traps

Martiquet — Wed, 02 Feb 2011 17:05:41 GMT

did I say I user Win 2008 64 SP1 ?
and PSP 8.6

Re: WBEM traps

Evan Nadeau — Tue, 22 Mar 2011 12:59:08 GMT

I am having the exact same event log WMI errors as well. I do get events from my servers fine, I just would like to clear this error from the log.

Re: WBEM traps

Rob Buxton — Wed, 23 Mar 2011 18:58:53 GMT

Seems an old thread, but here we go.
In order to get WBEM Events you need to Subscribe to them. It's an option under Events.

The discovery above seems to show it connected via SSH but not WBEM.
Check that the wbem component is configured and installed. In the VCRM there's an option to configure the wbem component, you provide a username for WMI Access. If not configured, do that and also ensure those credentials are used in the global wbem category.
Redeploy the wbem component if it's been changed.

Re: WBEM traps

Martiquet — Thu, 24 Mar 2011 09:49:35 GMT

I put a sniffer:
I see traffic outgoing from the managed box, and I see it incoming into the CMS box.
There is something going wrong with the WMI Proxy. I uninstalled/reinstalled it.
Nothing better...