Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

SIM WBEM Subscriptions and ESXi 4.1 issues

 
Highlighted
Regular Advisor

SIM WBEM Subscriptions and ESXi 4.1 issues

I have read through the threads and found things I have tried but no luck.

I have ONE ESXi system that allowed me to subscribe to WBEM events.
The rest (completely indentical Proliant servers) fail on trying to subscribe.

During system indentification it sees WBEM:

Normal: This system has WBEM protocol support.
Normal: The system support SLP.
Normal: This system has at least one SMI-S CIMOM installed to serve as the
storage proxy to discover storage systems.
Normal: This system has a server CIMOM installed.
* Running WBEM rules based identification...
Normal: Got the system information from the WBEM / WMI providers and it has
a valid WBEM credential.


Then when I try to subscribe to WBEM events it comes back with this:

Create Subscriptions for:

FAILED to create indication subscription.

Cause:Subscriptions are not supported

Recommended Action:Install the HP WBEM providers

OR

FAILED to create indication subscription.

Cause:Subscription infrastructure is not present or corrupted

Recommended Action:Update or reinstall the HP WBEM providers


I'm I missing something?
It seems to see it but doesn't see it.

Thanks
14 REPLIES 14
Highlighted
Honored Contributor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

I have had fun here as well. Check in amongst the server details, click on server name and under Tools go to Edit System Details (I think that's what it is, at home so cannot verify). Cross check that the settings look the same as one that's working.
In the past I've had to clear all of those and ensure any check boxes that stop the ID task from changing things are unchecked.
The only other thing is to ensure the SIM server can access the server using the credentials spec'd. You could try using server specific credentials.
Highlighted

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

I am having the same problem. I have 50 HP-UX servers discovered in SIM and only one of them is giving this error message. When I run "Identify Systems" in SIM the output looks good but the "Subscribe to WBEM events" fails every time. The information on the "Edit System Properties" page looks good. I don't know what else to try. Everything matches on all 50 servers. Any ideas?
Highlighted
Regular Advisor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

Sorry for late replies. Traveling.
I have tried checking all the settings and even removing and readding the systems.

Still no luck.
Highlighted
Esteemed Contributor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

I saw the same at a customer site.
Try unsubscribe if it finish with success the subscribe should work.

Highlighted
Regular Advisor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

Tried that. I won't allow me to run the command to unsubscribe.
Highlighted
Esteemed Contributor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

Sorry I forgotten to mention that I tried it from the command line mxwbemsub command.
If you had it on an esxi41 Update 1 it could be also a bug or a new feature.
Highlighted
Regular Advisor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

Well, allowed me to unsubscribe using the CLI, but still cannot subscribe using SIM or the CLI.

Says to install the HP WBEM Providers. Which are.

Even shows the WBEM health indicators and protocol found on the node.

Systems having the issue are indentical to the one that works.
Frustrating.
Highlighted
Frequent Advisor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

I have this working for my ESXi servers but, I was looking for an explanation on subscribing to WBEM and why that's necessary.

It's my own ignorance but, I don't fully understand the need to specifically subscribe to WBEM events.

I suppose I'm wondering why it doesn't automatically subscribe. Why is it a seperate process.

Can anyone provide and insight into this.
Highlighted
Honored Contributor

Re: SIM WBEM Subscriptions and ESXi 4.1 issues

@Brian: It's the functional equivalent to setting SNMP trap destinations on the target; "subscribing" is the method adopted by the DMTF for WBEM.