Виробник: SolarWinds
SolarWinds Network Performance Monitor 11
Software requirements
Do not install NPM on the same server as SolarWinds Access Rights Manager (ARM).
The following table lists software requirements and recommendations for an NPM installation on both physical and virtual computers.
| Software Requirements | ||
|---|---|---|
| Operating system |
Desktop operating systems, such as Windows 10, 64-bit Pro or Enterprise, are supported for evaluation environments only. To make a smooth transition from your evaluation to production deployment, SolarWinds recommends that you avoid installing evaluations on desktop operating systems. Support differences between Orion Agents and Orion Platform products
End-of-support notice: Products with Orion Platform 2018.4 and later are no longer compatible with Windows Server 2012 and 2012 R2. To use the new features introduced in Orion Platform 2018.4 or later, upgrade your environment at your earliest convenience. |
|
| Operating system languages |
|
|
|
IP address version |
IPv4 IPv6 Dual stack CIDR notation is not supported for IPv6 addresses. |
|
|
Web server |
If you are not using Windows Authentication, make sure the Anonymous Authentication is enabled for the SolarWinds NetPerfMon website. Anonymous Authentication is used with the default forms-based authentication. IIS is installed by the SolarWinds installer. You can install this software manually to reduce your installation time. |
|
|
.NET Framework |
.NET 4.8 Run the same version of. NET on your primary server and any Additional Polling Engines or Additional Web Servers in the environment. .NET 4.8 support was introduced in NPM 12.5 Hotfix 1. |
|
|
Services |
If you are using the Syslog or SNMP Traps feature of the Orion Platform, make sure the following services are running after installation is complete to collect syslog messages and traps:
|
|
|
Web console browser |
Orion Platform products support two most recent versions of the following web browsers available at the release date:
Orion Platform products also support the following browsers:
|
|
Account privileges
SolarWinds recommends that SolarWinds Orion administrators have local administrator privileges on the Orion server to ensure full functionality of local SolarWinds tools.
SolarWinds Orion user accounts limited to the Orion Web Console do not require local administrator privileges.
Server port requirements
- Ports 4369, 25672, and 5672 are opened by default on the main server for RabbitMQ messaging. These ports can be blocked by the firewall. When running SolarWinds High Availability, ensure ports 4369 and 25672 are open.
- RPC ports > 1024 (TCP, bidirectional) is used by the Job Engine v2 process to communicate with Windows nodes.
| Port | Pro- tocol | Service/ Process | Direction | Description | Encryption |
|---|---|---|---|---|---|
| user-defined, default: 22 | SSH |
SolarWinds Job Engine v2 IIS |
Outbound from the Orion server to the device | Port for accessing ASA devices through CLI | Device-based |
|
25 |
TCP |
SolarWinds Alerting Service V2 | Outbound |
SMTP port for non-encrypted messages |
n/a |
| 53 | UDP | SolarWinds Job Engine v2 | Bi- directional |
Resolving DNS queries | n/a |
|
80 |
TCP |
IIS | Inbound |
Default additional web server port. If you specify any port other than 80, you must include that port in the URL used to access the web console. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the web console ishttp://192.168.0.3:8080. The port might also be used for Cisco UCS monitoring. |
n/a |
| 135 | TCP | Microsoft EPMAP (DCE/RPC Locator service) | Bi- directional |
Required for devices polled via WMI. Used to initiate communication with the remotely managed host. | |
|
161 |
UDP |
SolarWinds Job Engine v2 SolarWinds Cortex |
Bi- |
Send and receive SNMP |
SNMP v1 and v2 are unencrypted. SNMP v3 uses AES and 3DES encryption. |
|
162 |
UDP |
SolarWinds Trap Service SNMP Informs |
Inbound |
Receive trap messages |
n/a |
|
443 |
TCP |
IIS | Inbound |
Default port for https binding. |
SSL |
|
465 |
TCP |
SolarWinds Alerting Service V2 | Outbound |
SMTP port used to send TLS-enabled email alert actions |
SSL |
|
514 |
UDP |
SolarWinds Syslog Service | Inbound |
Receive syslog messages |
n/a |
|
587 |
TCP |
SolarWinds Alerting Service V2 | Outbound |
SMTP port used to send TLS-enabled email alert actions |
TLS |
|
1433 |
TCP |
SolarWinds Alerting Service V2 SolarWinds Administration Service SolarWinds Information Service SolarWinds Information Service V3 SolarWinds Orion Module Engine |
Outbound |
Communication between the Orion server and the SQL Server. |
n/a |
|
1434 |
UDP |
SolarWinds Alerting Service V2 SolarWinds Administration Service SolarWinds Information Service SolarWinds Information Service V3 SolarWinds Orion Module Engine SQL Server Browse Service |
Outbound |
Communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. Required only if your SQL Server is configured to use dynamic ports. |
n/a |
|
1801 |
TCP |
MSMQ | Bidirectional |
MSMQ WCF binding |
WCF |
|
5671 |
TCP |
RabbitMQ |
Bi- directional |
For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers (additional polling engines, HA servers, or additional web servers). Sending messages to RabbitMQ. |
TLS 1.2 |
|
17777 |
TCP |
SolarWinds Orion Module Engine SolarWinds Information Service SolarWinds Information Service V3 SolarWinds Cortex |
Bi- directional |
Communication between services and SolarWinds Orion module traffic. Communication between the Orion Web Console and the polling engines. Communication between the main server and pool members. |
RSA handshake, AES 256 communication using WCF TLS 1.2 with Cortex |
|
17778 |
HTTPS |
SolarWinds Agent | Inbound to the Orion server |
Required for access to the SWIS API and agent communication |
SSL |
See SolarWinds Port requirements for a comprehensive list of port requirements for SolarWinds products.
Optional, individual components, such as Orion agents and High Availability, have additional port requirements.
Hardware requirements
The following table lists minimum hardware requirements and recommendations for your SolarWinds Orion server on physical computers, virtual computers, and cloud instances.
Use the minimum hardware configuration if you are evaluating the product or do not anticipate heavy usage.
SolarWinds strongly suggests using the recommended hardware configuration to avoid potential performance issues caused by a heavy load or custom configurations such as increased data retention or more frequent polling intervals.
Installing multiple SolarWindsOrion Platform products on the same computer may change the requirements.
Hardware requirements are listed by deployment size, based on the SolarWinds NPM license levels.
CPU recommendations for XL deployments use the PassMark Score. To learn more, see Pass Mark Performance Test (Copyright © 2018 PassMark® Software, obtained at https://www.cpubenchmark.net/high_end_cpus.html on April 9, 2018).
| Require- ments |
SMALL |
Medium SL2000 |
Large SLX | XL (Up to 400,000 monitored elements) |
|---|---|---|---|---|
|
CPU |
Quad core processor or better |
Quad core processor or better |
Quad core processor or better |
CPUs with a total combined PassMark score of 7,000 or higher |
|
Do not enable Physical Address Extension (PAE). |
||||
|
Hard drive space |
10 GB minimum 20 GB recommended |
15 GB minimum 40 GB recommended |
30 GB minimum 40 GB recommended |
40 GB minimum 50 GB recommended Read/Write I/O performance of 800 IOPS |
|
Two 146 GB 15K (RAID 1/Mirrored Settings) hard drives are recommended with a dedicated drive for the server operating system and SolarWinds installation. Some common files may need to be installed on the same drive as your server operating system. You may want to move or expand the Windows temporary directories. |
||||
|
Memory |
6 GB minimum 8 GB recommended |
8 GB minimum 16 GB recommended |
16 GB minimum 32 GB recommended |
16 GB minimum 32 GB recommended |
Database server (SQL Server) requirements
The following table lists software and hardware requirements for your SolarWinds Orion database server using SolarWinds NPM license levels.
The Orion server and the SolarWinds Orion database must use separate servers.
If you install on a virtual machine, you must maintain your SQL Server database on a separate, physical drive.
As of Orion Platform 2019.2, you can use Azure SQL as your database server.
As of Orion Platform 2018.2, you can use Amazon RDS as your database server.
| Require- ments |
Small SL100, SL250, SL500 |
Medium SL2000 |
Large SLX |
XL (up to 400,000 elements) |
|---|---|---|---|---|
|
SQL Server |
Express, Standard, or Enterprise versions of the following:
SolarWinds recommends that you use Express versions only for evaluations, very small environments, and EOC. |
Enterprise versions of supported SQL Servers:
|
||
|
End-of-support notice: Products running on Orion Platform 2018.4 and later are no longer compatible with SQL Server 2012, 2012 SP1, 2012 SP2, 2012 SP3, and 2012 SP4. To use the new features introduced in Orion Platform 2018.4 and later, upgrade your environment at your earliest convenience. Recommendations
|
||||
| SQL Server collation |
We support CI database on an CS SQL Server. We do not support case-sensitive databases. |
|||
|
CPU |
Quad core processor or better |
Dual quad core processor or better |
Dual quad core processor or better |
CPUs with a total combined PassMark score of 32,000 or higher |
|
Hard drive space |
20 GB minimum 40 GB recommended |
50 GB minimum 100 GB recommended |
100 GB minimum 400 GB recommended* |
500 GB minimum 1TB recommended
Read/Write I/O performance of 30,000 IOPs 190,000 IOPS or better recommended 1 Gbit dedicated NIC
|
Some common files may need to be installed on the same drive as your server operating system. You may want to move or expand the Windows or SQL temporary directories. |
||||
|
Memory |
8 GB minimum 16 GB recommended |
16 GB minimum 64 GB recommended |
64 GB minimum 128 GB recommended |
256 GB minimum 512 GB recommended |
|
Authentication |
Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server. |
|||
| Other software |
SolarWinds recommends you install the SQL Server Management Studio component on your Orion database server. The Orion Installer installs the following required x86 components if they are not found on your Orion database server:
You cannot share the SolarWinds Orion database with Microsoft SharePoint, Microsoft Exchange, and Research in Motion (RIM) BlackBerry servers. |
|||
* SolarWinds recommends the following hard drive configuration:
- A hardware RAID Controller with a battery backed-up write back cache
- Disk Subsystem 1 Array 1: 2x 146 GB 15K disks RAID 1 (mirroring) for the OS
- Disc Subsystem 2 Array 2: 2x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)
- Disk Subsystem 3 Array 3: with 6x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL MDF and FILEGROUPS.
- Disk Subsystem 4 Array 4: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL LDF Transaction LOG file
- Disk Subsystem 5 Array 5: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your tempdb data file
- Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a RAID 0 array for your tempdb log file
Amazon Web Services (AWS deployments)
To deploy NPM using Amazon Web Service, consider using the following templates:
| Require- ments |
Small SL100, SL250, SL500 |
Medium SL2000 |
Large SLX | XL (up to 400,000 elements) |
|---|---|---|---|---|
|
Orion server |
m4.large |
m4.xlarge Recommended: m5d.xlarge with SDD drive |
m4.2xlarge Recommended: m5d.2xlarge with SSD |
m5.4xlarge Recommended: m5d.2xlarge with SSD |
|
SolarWinds Orion database server |
r4.xlarge |
r4.xlarge |
r3.2xlarge Recommended: r5d.xlarge with SSD |
r5d.4xlarge Recommended: r5d.12xlarge |
| Amazon RDS | db.r4.xlarge | db.r4.2xlarge | db.r4.4xlarge | db.r4.8xlarge |
| Additional Polling Engines | Only relevant for environments that monitor over 12,000 elements. |
m5.xlarge |
||
Microsoft Azure
To deploy NPM on Microsoft Azure, consider using the following instance types, based on your deployment size. The table provides NPM license levels as a reference.
| Require- ments |
Small SL100, SL250, SL500 |
Medium SL2000 |
Large SLX | XL (up to 400,000 elements) | |||
|---|---|---|---|---|---|---|---|
|
Orion server |
DS12_v2 4 CPU 16 GB RAM 150 GB disk |
DS12_v2 4 CPU 16 GB RAM 150 GB disk |
DS4_v2 8 CPU 32 GB RAM 150 GB disk |
DS4_v2 8 CPU 32 GB RAM 150 GB disk |
|||
|
SolarWinds Orion database server in an Azure VM |
D12_v2 4 CPU 30.5 GB RAM System SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB* |
DS4_v2 Standard 8 CPU 28 GB RAM System SSD 126 GB (included in Azure VM instance) + 1 TB for SQL database (included in Azure SQL Server Computer) |
D4_v2 Azure Storage Disk with Provisioned IOPS recommended 8 CPU 61 GB RAM System SSD 160 GB (included in D4_v2) + 2x Data Azure Storage Disk Volume 500 GB* |
E32-8s_v3 Azure Storage Disk with Provisioned IOPS recommended 8 CPU 256 GB RAM System SSD 512 GB (included in E32-8s_v3) + 2x Data Azure Storage Disk Volume 500 GB* |
|||
| SolarWinds Orion database using Azure SQL DB |
All installed products must run on Orion Platform 2019.2, such as:
Time zone setting of the Orion Server must be in the same time zone as Azure SQL DB time zone (UTC). When deploying Azure SQL and creating a new user in the Configuration wizard, SA account credentials are required in the Configuration wizard. When using Azure SQL database as your database server, the required tiers also depend on whether you are using memory-optimized tables. Memory-optimized tables, also known as In-Memory OLTP, are a feature available in MS SQL Server 2016 and 2019 that improves the performance of transaction processing, data ingestion, data load, and transient data scenarios. |
||||||
| Azure SQL DB tiers if you use memory-optimized tables |
DTU Tier P1 vCore Business Critical Gen4 Tier 1 vCore Business Critical Gen5 Tier 2 |
DTU Tier P2 vCore Business Critical Gen4 Tier 2 vCore Business Critical Gen5 Tier 2 |
DTU Tier P4 vCore Business Critical Gen4 Tier 4 vCore Business Critical Gen5 Tier 4 |
DTU Tier P11 vCore Business Critical Gen4 Tier 16 vCore Business Critical Gen5 Tier 14 |
|||
| Azure SQL DB tiers without memory-optimized tables |
DTU Standard Tier S3 DTU Premium Tier P1 vCore General Purpose Tier 2 vCore Business Critical Tier 2 |
DTU Standard Tier S3 DTU Premium Tier P1 vCore General Purpose Tier 2 vCore Business Critical Tier 2 |
DTU Standard Tier S4 DTU Premium Tier P2 vCore General Purpose Tier 2 vCore Business Critical Tier 2 |
DTU Standard Tier S9 (up to 100k elements), S12 (up to 400k elements) DTU Premium Tier P6 (up to 100k elements), P11 (up to 400k elements) vCore General Purpose Tier 16 (up to 100k elements), 30 (up to 400k elements) vCore Business Critical Tier 8 (up to 100k elements), 14 (up to 400k elements). |
|||
* Azure Storage Disk volumes are not your dedicated hardware. Consider using Azure Reserved Instances of storage disk volumes for SQL servers.
