1-800-691-1991 | 9am - 8pm ET
EN

Collection of events with multiple collectors

KB ID: 1037
Product: Veeam Management Pack for Microsoft System Center
Version: 5.x
Published: 2011-07-15
Last Modified: 2020-08-28
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

In most cases and several deployments, there are multiple collectors connecting to the same VMware vCenter(s).

Cause

Collection and publication of metrics is split between collectors; however, all events are collected from the vCenter by all collectors and are eventually presented to all VEM agents. In this scenario it is reasonable to expect duplicate alerts/messages in the Operations Manager console.

Solution

How this is resolved with MS SCOM?

When the collectors start gathering data from a VC, they will all trigger discovery. The top object will be the same for all collectors looking at the same vCenter; however, only the "instance" of the vCenter discovered by the collector that was the first to log the discovery, is used for creation of topology and alerting the vCenter events. This approach helps prevent any duplicate alerts.

The behavior of HP Open View

HPOV does not rely on the service map which is only constructed for the visual reference of the Operator. The duplicate generic VC events will not be filtered and are expected to appear in the messages list; however, nworks provides a solution for this and it is possible to disable capturing generic VC events on specific collectors.

To do this:

 

  1. In the nworks UI go to "Enterprise Manager" tab and select a collector

  2. Where you disable capturing generic VMware vCenter server events, click "Advanced settings"
     
  3. Set "EnableVCGenericEvents" to False
     
  4. Save the settings
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.