Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Archive > 2017December28 - Deletes > Alerts on VM nodes with VMAN integration

Alerts on VM nodes with VMAN integration

Created by Roger Lofamia, last modified by Gerald.Prado on Dec 28, 2017

Views: 1,057 Votes: 0 Revisions: 8


This article details the following:

  • Where the VM nodes get information on alerts for Orion NPM with VMAN integrated work.
  • Should SNMP be enabled for the alerts to work on VM nodes for Orion NPM with VMAN integrated.


NPM 11.5.2 with VMAN 6.3 integrated


  • VM nodes get information from the vCenter provided by VMAN.
  • The alerts work even if SNMP is not enabled (only ICMP) since Orion NPM is able to provide the statistics and information of the VM nodes from VMAN integration.



VIM - Account Limitations

Virtualization limitations can be set on several entities:

  • VCenter
  • Datacenter
  • Cluster
  • Host
  • Virtual Machine
  • Datastore (only available when integration is enabled)

One thing to keep in mind is that Virtualization limitations are separated from Node limitations.

To give an example:

  • limitation set on VM will hide only the VM but it will not hide the Node itself.
  • limitation set on Node will hide VM/Host/VCenter which is linked to the Node, but it will not hide any child entities, so in case that the hidden Node is Host, user will be able to see all child VMs.

Because of this behavior it is necessary to configure limitations not only on Virtualization entities or Nodes, but on both. Otherwise some parts of the environment may be still visible to the user.

How the application of limitations works

The limitations are applied to the entities in two directions at the same time.

  • DOWN - When limitation is set to some entity, user should be able to see all its children.
    • Example: Limitation on single Cluster will cause that user will only see the specified Cluster and its children (Hosts, Virtual Machines)
  • UP - When limitation is set to some entity user should not be able to see parents of the limited entity.
    • Example: Limitation on single Host will cause that parent Cluster, Datacenter and VCenter are not visible.

Following picture shows how the limitation will be applied in case that the limitation is set to a single Cluster. Only the area in the red box will be visible to the user.

Another things that needs to be considered due to this behavior are following:

  1. Everything that is above the level for which the limitation is set will not be available.
  2. When there is a limitation to some entity all the entities that have relation to same level are affected as well.
    1. Example: Limitation on Cluster - all hosts that do have cluster are affected by limitation (will be visible only if their cluster passes limitation), standalone hosts without cluster will be visible (relation to Cluster is missing - can't be limited).
    2. This behavior allows to configure special use cases in environments where there are both clustered hosts and non-clustered hosts.
  3. Between 3 limitations that can be applied for the user AND operator is used.
    1. If multiple VIM limitations are set for the user, he will be able to see only intersection of those.
    2. If there is no intersection no data is available
    3. Example: Consider Cluster C1 with Host H1 and Cluster C2 with Host H2
      1. Limitation set for C1 and H2
      2. Nothing is shown, because there is no intersection in set limitations
  4. For the Group (Container) limitations OR is used.
    1. Meaning that at least some condition needs to be met
    2. Example: Consider Cluster C1 with Host H1 and Cluster C2 with Host H2
      1. Group containing C1 and H2 is created and used for limitation
      2. C1, H1, H2 is visible, because H1 belongs to C1 which is allowed by limitation



Last modified