Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Configuration Manager (NCM) > NCM 7.6 system requirements

NCM 7.6 system requirements

Updated March 13, 2017

Supports: NCM version 7.6 

Requirements vary based on:

  • The number of nodes
  • The frequency of configuration downloads
  • The length of time that configurations are maintained in the database

Port requirements

The following ports may be needed for the Orion Web Console, depending on how SolarWinds NCM is set up to download and upload configurations:

Port Type Description
22 SSH/SCP

Default port for NCM to transfer configs

23 Telnet Default port for NCM to transfer configs
25 TCP SMTP email default that NCM uses for notification (If SSL/TLS encryption is set up on SMTP server, default port is 465)
69 UDP TFTP server listens on this port
80 TCP HTTP default for the Orion Web Console
161 UDP SNMP statistics collection, the default for polling in NCM
162 UDP Trap messages listened for and received by the Trap Server
443 TCP Default port for HTTPS binding.
465 TCP The port used for SSL-enabled email alert actions
514 UDP Syslog Service listens for incoming messages
587 TCP The port used for TLS-enabled email alert actions
1801 TCP

MSMQ WCF binding (For more information see this article from Microsoft)

5671 TCP For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers
17777 TCP Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console, and from the Orion Web Console to your poller. The port used for communication between the Orion Web Console and the poller.
17778 HTTPS Required for access to the SWIS API and agent communication
17779 HTTP SolarWinds Toolset Integration over HTTP

Ports 4369, 5672, and 25672 are opened by default. These ports can be blocked by the firewall.

Server requirements

Type

Requirements

Operating System

  • Windows Server 2008 R2, Windows Server 2008 R2 SP1
  • Windows Server 2012 and Windows Server 2012 R2
  • Windows Server 2016

For evaluation purposes only:

  • Windows 7 SP1
  • Windows 8 (except Standard edition)
  • Windows 8.1 including Update 1 (except Standard edition)
  • Windows 10

Installing SolarWinds Orion on Windows Server 2012 R2 Essentials is not supported.

Operating System Language
  • English
  • German
  • Japanese
  • Simplified Chinese.

NCM does not support using locales outside the group of supported operating system languages.

SolarWinds NCM Server Hardware

CPU Speed

3 GHz dual core dual processor

Memory

4GB

Hard Drive Space

30GB

This version of SolarWinds NCM holds a searchable config index on local disk that adds 6 - 10GB additional disk space to the previous requirement.

Installing Windows Account

Requires administrator permission on the target server.

File System Access Permissions

Ensure the Network Service account has modify access to the system temp directory: %systemroot%\temp.

SolarWinds Orion Syslog Server

If you want real time change detection triggered through devices sending Syslog messages, the executable must have read and write access to the Orion Platform database.

SolarWinds Orion Trap Service

If you want real time change detection triggered through devices sending SNMP traps, the executable must have read and write access to the Orion Platform database.

Microsoft SNMP Trap Service

Must be installed if you want real time change detection triggered through devices sending SNMP traps.

Microsoft IIS

Version 7.5 or later. DNS specifications require hostnames to be composed of alphanumeric characters (A-Z, 0-9), the minus sign (-), and periods (.). Underscore characters (_) are not allowed.

SolarWinds neither recommends nor supports the installation of SolarWinds NCM on the same server or using the same database server as a Research in Motion (RIM) Blackberry server.

Microsoft ASP .NET 2.0 Ajax Extension

Version 1 or later

If this is not found on the target computer, the setup program downloads and installs the component.

Microsoft .NET Framework

Version 4.5 (and compatible with 4.6.1)

If the required version is not found on the target computer, the setup program downloads and installs it. Ensure that .NET is turned on in Windows Features.

Database

You must create the SolarWinds Orion database with the SolarWinds Configuration Wizard. Creating the database another way is not supported.

SolarWinds supports using NCM with database servers set up in these languages: English, German, Japanese, and Chinese, but only supports storing characters in the UTF-8 set.

The following database servers are supported:

  • SQL Server 2016 and SQL Server 2016 with SP1
  • SQL Server 2014 and SQL Server 2014 with SP1 , and with Always On Availability Groups
  • SQL Server 2012, with or without SP1 and SP2, Standard or Enterprise
  • SQL 2008 R2 without SP, 2008 R2 SP1, 2008 R2 SP2
  • SQL 2008 without SP, 2008 SP1, 2008 SP2, 2008 SP3

NCM local SQL database uses SQL 2014 Express.

You can use the following database select statement to check your SQL Server version, service pack or release level, and edition:

select SERVERPROPERTY ('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

The following SQL server collations are supported:

  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • English with collation setting SQL_Latin1_General_CP1_CS_AS
  • German with collation setting German_PhoneBook_CI_AS
  • Japanese with collation setting Japanese_CI_AS
  • Simplified Chinese with collation setting Chinese_PRC_CI_AS

Your database server must support mixed-mode authentication or SQL authentication and have the following protocols enabled:

  • Shared memory
  • TCP/IP
  • Named Pipes

SQL Server 2008 Express Edition does not enable these protocols.

The following x86 components must be installed:

  • SQL Server System Common Language Runtime (CLR) Types
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

If the components are not found on the target computer, the setup program downloads and installs the components.

Ports

The following ports may be needed for Orion Web Console, depending on how SolarWinds NCM is set up to download and upload configurations:

  • 22: SSH/SCP default for NCM to transfer configs
  • 23: TELNET default for NCM to transfer configs
  • 25: SMTP email default that NCM uses for notification (If SSL/TLS encryption is set up on SMTP server, default port is 465)
  • 69: TFTP server listens on it
  • 80: HTTP default for Orion Web Console
  • 161: SNMP statistics collection, the default for polling in NCM
  • 162: UDP trap messages listened for and received by Trap Server
  • 443: TCP default port for https binding.
  • 465: TCP port used for SSL-enabled email alert actions
  • 514: UDP Syslog messages arrive for Orion Syslog Service
  • 587: Port used for TLS-enabled email alert actions.
  • 1801: TCP used for MSMQ WCF binding
  • 5671: TCP for SSL-encrypted RabbitMQ messaging from the additional polling engines to the main polling engine
  • 17777: SolarWinds Information Service for Orion Web Console
  • 17778: SolarWinds Information Service for Orion Web Console
  • 17779: SolarWinds Information Service for Orion Web Console

Ports 4369, 5672, and 25672 are opened by default. These ports can be blocked by the firewall.

Browser

  • Microsoft Internet Explorer 11 (standard and mobile views) and Microsoft Edge
  • Mozilla Firefox 45, or latest supported versions
  • Google Chrome 49, or latest supported versions

Additional information

  • The SolarWinds NCM Information Service requires that the Net.TCP Port Sharing service be enabled and port 17777 open for TCP traffic to the SolarWinds NCM server. By default, this service is disabled. The setup program sets the service to manual. Resetting the service setting to disabled is not recommended.
  • To take advantage of the numerous integration points in SolarWinds NCM, install the SolarWinds Engineer's Toolset on the same server. You can also take advantage of integration points built into the Web Console by installing the Toolset on computers used to access the Web Console.

Scalability

SolarWinds NCM 7.6 was tested for scalability in a standalone deployment of three servers: one server hosts the main server and the other two servers each host an additional polling engine. The main server manages up to 10,000 nodes, as does each additional polling engine. Therefore, the deployment supports up to 30,000 nodes total.

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 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.

Server sizing

SolarWinds Network Configuration Manager can perform configuration management for any sized network, from small corporate LANs to large enterprise and service provider networks. Most SolarWinds NCM implementations perform well on Pentium-class 3GHz systems with 4GB of RAM using the default simultaneous transfer settings, and with no modifications to node monitoring settings.

Should scalability issues arise, adjust the following:

  • Number of simultaneous transfers
  • Frequency of uploads, downloads, and inventory jobs
  • Node polling interval for up/down monitoring

Inventory jobs may run longer than expected in larger environments. To remedy this situation, break large inventory jobs into smaller jobs that do not include as many nodes, and space these jobs over a longer period of time. Adjusting server CPU and memory will enhance user interface performance and job execution speed.

 
Last modified
09:16, 18 Jul 2017

Tags

Classifications

Public