Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM Documentation > SolarWinds VNQM Installation Guide > System requirements for a stand-alone installation of SolarWinds VNQM

System requirements for a stand-alone installation of SolarWinds VNQM

The following requirements are based on a minimum installation of SolarWinds VoIP and Network Quality Manager with SQL Server on a separate database server. If you are installing SolarWinds VNQM into an existing Orion Platform installation, see the multi-module system guidelines.

To optimize database scalability, SolarWinds recommends that you maintain your SQL Server installation on its own server. If you must host your SQL server on the same server, SolarWinds recommends at least a quad-processor, 2.67 GHz, 64-bit CPU and 16 GB of RAM.

SolarWinds VoIP and Network Quality Manager requirements

Hardware or software

Requirements

Environment

SolarWinds VoIP and Network Quality Manager supports IP SLA for Cisco IP SLA capable devices. It is possible to monitor Cisco CallManager, CallManager Express, and Avaya Communication and Media Server devices with SolarWinds VoIP and Network Quality Manager.

CPU

Dual processor, 3GHz

RAM

8 GB

Hard drive space

20 GB

Operating system

Windows Server 2012, 2012 R2

Windows Server 2016

.NET Framework

Version 4.6.2

Compatible with 4.6.1

Web browser

 

 

Internet Explorer 11

Microsoft Edge

Mozilla Firefox - two most recent versions

Google Chrome - two most recent versions

SQL Server requirements

Hardware or software

Requirements

CPU

Dual processor, 3 GHz

Quad-processor, 2.67 GHz, 64-bit (for large networks)

RAM

8 GB

16 GB (for large networks)

Hard drive space

20 GB

Database

SQL Server 2012, 2012 SP1, 2012 SP2, or 2012 SP3 (also with AlwaysOn Availability Groups)

SQL Server 2014 (also with AlwaysOn Availability Groups) or 2014 SP1

SQL Server 2016 RC

SQL Server 2017

If you anticipate up to six million standard, device to device calls per month with a peak hour of 20,000 calls, SolarWinds recommends using a dedicated SQL server with a 64-bit, 2.67 GHz quad-processor CPU and 16 GB of RAM. SolarWinds VNQM does not support more than six million calls per month.

Port requirements

Port #

Protocol Service / Process Direction Description
21 TCP SolarWinds Collector Service Bidirectional The port used for FTP (CDR/CMR download)
22 TCP SolarWinds Collector Service Bidirectional

The port used for SFTP (CDR/CMR download)

SSH for CLI (operation polling)

23

TCP SolarWinds Collector Service Bidirectional The port used for TELNET for CLI (operation polling)

80

TCP World Wide Web Publishing Service Bidirectional HTTP port

The default port used by Additional Web Servers. If you change this setting, you must include the port in the URL used to access the Orion Web Console.

161 UDP SolarWinds Collector Service Outbound The default UDP port of NPM, used by SNMP.
443 TCP World Wide Web Publishing Service Bidirectional The port used for conducting secure SSL communications.
5022 TCP SolarWinds Collector Service Bidirectional The port used for communication with Avaya Call Manager via CLI through SSH.
5005 UDP SolarWinds Collector Service Bidirectional

The port used for RTCP data (call metrics) listening from Avaya Call Manager.

8443 HTTPS SolarWinds Orion Module Engine/Business Layer Plugin Outbound The port used for troubleshooting Cisco Call Manager AXL credentials.
17777 TCP SolarWinds Information Service Bidirectional

The port used forcommunication from your polling engine to the Orion Web Console, and from the Orion Web Console to your polling engine.

50000 TCP SolarWinds Collector Service Bidirectional The port used for CDR data (call records) listening from Avaya Call Manager.
Last modified

Tags

Classifications

Public