Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM - Knowledgebase Articles > Account limitations are not working as expected in VNQM 4.1 and NPM 10.7

Account limitations are not working as expected in VNQM 4.1 and NPM 10.7

Created by Interspire Import, last modified by MindTouch on Jun 16, 2016

Views: 740 Votes: 0 Revisions: 8


IP SLA operations are not displayed in the IP SLA operations resource and in the Manage IP SLA operations page of VNQM.

The issue occurs with the IP SLA operations created for nodes that you added in Orion, and then imported to VNQM.
The IP SLA operations of these nodes are not displayed as expected if you add an account limitation of the Single Network Node - Source Node type to a user account.


This article applies to VNQM 4.1 and NPM 10.7.


The reason for this issue is that the Single Network Node account limitation type now applies to both the source and the target nodes, regardless of the fact whether the target node is Internal or External.

Last modified