VoIP and Network Quality Manager 4.4 System Requirements
Important: These system requirements define the minimum requirements for VNQM 4.4 as a single installed product. You may need to increase your requirements in small, medium, or large environments with multi-modules installed.
Hardware and software requirements
Important End of Support
Microsoft Windows Server: Support for Windows Server 2008 R2 is deprecated as of this release. Future releases will no longer support installing on Windows Server 2008 R2, though you can continue to monitor computers running Windows Server 2008 R2. SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience.
|
HARDWARE OR SOFTWARE |
REQUIREMENTS |
|---|---|
|
Environment |
SolarWinds VoIP and Network Quality Manager supports IP SLA for Cisco IP SLA capable devices. With VNQM, you can monitor:
|
|
CPU |
Dual processor, 3GHz |
|
RAM |
8 GB |
|
Hard drive space |
20 GB |
|
Operating system |
Windows Server 2008 R2 SP1 Windows Server 2012, 2012 R2 Windows Server 2016 |
|
.NET Framework |
Version 4.5 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
Important End of Support
Microsoft SQL Server: Support for SQL 2008 and 2008 R2 is deprecated as of this release. Future releases will no longer support using SQL 2008 or 2008 R2 as your database server. SolarWinds recommends that you upgrade directly to SQL 2016 at your earliest convenience.
|
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 2008, 2008 SP1, 2008 SP2, 2008 SP3, or 2008 SP4 |
- If you anticipate six million standard, device to device calls per month with a peak hour of 20,000 calls, we recommend using a dedicated SQL server with a 64-bit, 2.67 GHz quad-processor CPU and 16 GB of RAM. We do not support more than six million calls per month.
- If you are installing SolarWinds VoIP and Network Quality Manager with SolarWinds NPM, see Orion Platform Requirements.
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) and for 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 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. |
| 5005 | UDP | SolarWinds Collector Service | Bidirectional |
The port used for RTCP data (call metrics) listening from Avaya Call Manager. |
| 5022 | TCP | SolarWinds Collector Service | Bidirectional | The port used for communication with Avaya Call Manager via CLI through SSH. |
| 8443 | HTTPS | SolarWinds Orion Module Engine/Business Layer Plugin | Outbound | The port used for Cisco Call Manager AXL credentials troubleshooting. |
| 17777 | TCP | SolarWinds Information Service | Bidirectional |
The port used for communication 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. |