How to disable monitoring of Virtual Machines with nworks MP

KB ID: 1553
Product: Veeam Management Pack for Microsoft System Center
Version: 5.6
Published: 2012-03-11
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.

Purpose

In some environments, there is no need to monitor certain (or any) virtual machines.

With nworks MP, it is possible to:

  - Disable discovery of all virtual machines, and

  - Disable discovery of specific virtual machines (workaround available since 5.6).

Solution

Disable discovery of virtual machines

To disable discovery of virtual machines, it is necessary to:

Uncheck "VM and Core metrics" in nworks UI -> "Enterprise Manager" tab -> Collection Settings; then save the settings.

Disable discovery of virtual machines per container:

Large scale discovery was introduced in nworks 5.6. When SV102LS is enabled, it creates a number of VM containers per host. The discovery can be disabled per container in SCOM.

nworks allows the user to configure the number of VMs per container. To access the setting, go to nworks UI -> "Enterprise Manager" tab -> select top node on the left -> Advanced Settings -> VMsPerLargeScaleGroup. If the setting equals "1", there will be only one VM per container, so:

  1. Set "VMsPerLargeScaleGroup" to "1".

  2. Once you do this, wait until the topology is updated in SCOM so that there is only one VM per container. Then find the container, which holds the VM you do not want monitored.

  3. Override SV102LS, disabling it for the container(s) you selected in the previous step (SCOM Authoring -> Object Discoveries -> SV102LS).

  4. In nworks UI, go to "Enterprise Manager" tab -> Collection Settings and uncheck "VM and Core metrics".

  5. Wait until the VMs disappear completely from SCOM topology.

  6. In nworks UI, go to "Enterprise Manager" tab -> Collection Settings -> enable "VM and Core metrics".

The container will be empty in the end. It may change its health state, but the alerts view will be empty. The health is  not rolled up to the parent.

IMPORTANT NOTE:

If the VM ID changes, the VM might have been moved to another container. If collection of VM and Core metrics is disabled, some of the host metrics will no longer be available since they are calculated based on VM activity.  See the Operations Guide -> Changing Data Collection Settings for details.

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.
Verify your email to continue your product download
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.