Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Configuration Manager (NCM) > NCM 7.6 Administrator Guide > Installation > Scalability

Scalability

Table of contents
No headers
Created by Caroline Juszczak, last modified by Anthony.Rinaldi_ret on Oct 03, 2016

Views: 94 Votes: 0 Revisions: 4

Each SolarWinds NCM instance can support up to 20 additional polling engines (APEs). Each additional polling engine can support approximately 10,000 nodes. However, the number of nodes in the entire environment (the primary engine plus all APEs) cannot exceed approximately 30,000. 

Examples:

  • The primary engine and two APEs could support 10,000 nodes each, for a total of 30,000 nodes.
  • The primary engine and 20 APEs could support around 1,400 nodes each, but the combined total cannot exceed the 30,000 maximum. 

The standard Orion Web Console deployment has the Orion platform on the main server, polling for node status at the default rate. This deployment supports two SolarWinds NCM operations, inventory update and configuration download, performed per day on all 30,000 nodes.

Though the main server and each additional polling engine can typically manage up to 10,000 nodes, the actual total depends on the system hardware of the server hosts, the types of devices being monitored, and the number of jobs being run concurrently. Should you need to manage more devices, and you decide to add servers, consider consolidating your views of multiple servers with the Orion Enterprise Operations Console.

 

Last modified
13:32, 3 Oct 2016

Tags

Classifications

Public