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

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
KB ID: 1037
Product: Veeam Management Pack for Microsoft System Center
Version: 5.x
Published: 2011-07-15
Last Modified: 2020-08-28

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
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

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.