NPM Installation Guide

INSTALLATION GUIDE
SolarWinds Network
Performance Monitor
Version 12.1
Last Updated: June 7, 2017
Retrieve the latest version from: https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/NPM_Documentation

2017 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published
or distributed, in whole or in part, or translated to any electronic medium or other means without the prior
written consent of SolarWinds. All right, title, and interest in and to the software and documentation are
and shall remain the exclusive property of SolarWinds and its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED,

STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING
WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS
BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN
IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds and other SolarWinds marks, identified on the SolarWinds website, as updated from
SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark
Office and may be registered or pending registration in other countries. All other SolarWinds trademarks
may be common law marks or registered or pending registration in the United States or in other countries.
All other trademarks or registered trademarks contained and/or mentioned herein are used for
identification purposes only and may be trademarks or registered trademarks of their respective
companies.
page 2
INSTALLATION GUIDE: SOLARWINDS NETWORK PERFORMANCE MONITOR
Table of Contents
Installation Overview 5
Stand-alone installation 6
Integrated with the OrionPlatform 7
Evaluation installation 7
Terminology 8
NPMlicensing model 10
License NPM with other SolarWinds products 10
Manage and activate your NPM license 11
SolarWinds NPM installation preflight checklist 12
SolarWinds requirements 14
Software requirements 14
Account privileges 16
Server port requirements 16
Hardware requirements 19
Database server (SQL Server) requirements 20
SolarWinds High Availability requirements 25
Supported products 25
Software and Hardware requirements 26
Port requirements 26
Networking requirements 27
Multi-module system guidelines 28
Small deployment guidelines 28
Medium deployment guidelines 29
NTA-specific information 30
Large deployment guidelines 30
page 3
NTA-specific information 32
Prepare the Orion database 33
Install a licensed copy of NPM 34
Integrate NPM with other Orion Platform products 40
Install SolarWinds NPM with High Availability 47
Install with new HA 47
Install with existing HA 48
Enable FIPS 50
Install an evaluation copy of SolarWinds NPM 52
Steps to take after SolarWinds NPM is installed 54
Uninstall SolarWinds NPM 55
page 4
Installation Overview
Supported Version: SolarWinds Network Performance Monitor (NPM) 12.1
SolarWinds NPM is a network monitoring solution that helps you to quickly detect, diagnose, and resolve
network performance problems and outages.
NPMprovides:
l Fault, performance, and availability monitoring

l Hop-by-hop analysis along critical paths
l Cross-stack network data correlation
l Customizable topology and dependency-aware alerts
l Dynamic wired and wireless network discovery and mapping
l Automated capacity forecasting, alerting, and reporting
l Wireless network monitoring and management
l Customizable single-pane-of-glass network monitoring software
l End-user quality of experience with Packet Capture and Analysis
l Dynamic statistical network performance baselines
l Hardware health monitoring
l Customizable performance and availability reports
l Drag-and-discover network performance charts
This guide supports the following installation scenarios:
l Plan for NPM installation

l Stand-alone installation
l Integrated with the Orion Platform
l Evaluation installation
l Uninstallation
page 5
Stand-alone installation
For a stand-alone installation of SolarWinds Network Performance Monitor, install the product on a
dedicated server. This installation assumes you have not installed any other SolarWinds Orion Platform
products on the target server.
page 6
Integrated with the OrionPlatform

SolarWinds Network Performance Monitor supports an integrated installation into an existing Orion
Platform. For this installation, you may install the product on the Orion server, to connect to the Orion
SQLdatabase. As part of this installation, verify if installed products need to be upgraded prior to
installing the new product. If your environment uses SolarWinds High Availability, follow the additional
instructions as part of the installation.
Evaluation installation
SolarWinds Network Performance Monitor supports an evaluation installation with a trial period. This
installation is a full installation of the product with a 30-day license. To continue with a full product
license, contact SolarWinds Sales.
page 7
Terminology
The following terms provide context for the architecture and components of SolarWinds products.
Additional Polling Engine (APE)
To scale polling and monitoring in larger environments, you can add additional polling engines or
stackable polling engines to an existing Orion Platform products. APEs scale your environment to
monitor hundreds of thousands of elements, and poll across multiple pollers and locations to
improve performance. For details, see the Scalability Engine Guidelines for SolarWinds Orion
Products.
Additional Web Server (AWS)
To scale web server access to the Orion Web Console in larger environments, you can add an
additional web server to an existing Orion Platform product. AWS increase the performance and
scalability of users to the Orion Web Console, For details, see the Scalability Engine Guidelines for
SolarWinds Orion Products.
High Availability (HA)
HA protects your Orion environment from server crashes, outages, and database issues. Server pairs
in HA pools provide automatic failover to a backup server for the main Orion server and additional
polling engines. Each server pair can be easily updated with new products and hotfixes using the
Scalability Engine Installer, available through the Orion Web Console.
Orion Platform
The common backend platform used by the Solarwinds Orion suite of products, including NPM, SAM,
NCM, NTA, and more. The platform provides the backbone for navigation, settings, and common
features like alerts and reports. It also provides a consistent look-and-feel across products, giving
you a single pane of glass for your Orion monitoring tools.
Orion Application Server
A Windows server that runs the Orion Web console and collects data from monitored objects. Also
called the Orion Main Poller.
Orion Database Server
A Windows SQL server that should be hosted on a dedicated server in a production environment,
separately from the Orion Application Server. It stores Orion configuration data and all collected
performance and syslog data.
page 8
Polling Engine (Poller)
A Polling Engine controls polling job scheduling, data processing, and queries your monitored
devices for performance metrics like CPU, memory, and up/down status. Additional Polling Engines
can be licensed to provide additional scalability and capacity. By default, the Orion Server provides
one Polling Engine (often referred to as the Main Poller).
Orion Web Console:
The web interface you see when you log on to Orion that is used to view, configure, and manage all
of your monitored objects.
Check out this video on navigating the Web Console.
page 9
NPMlicensing model
The SolarWinds NPM license is based on a number of items to monitor. Each license tier number provides
the maximum limit of nodes, interfaces, and volumes to manage and monitor.
NPM is licensed according to the largest number of the following types of monitored network elements:
l Nodes: any devices being monitored, such as routers, switches, virtual and physical servers, access
points, and modems.
l Interfaces: any single points of network traffic, such as switch ports, physical interfaces, virtual
interfaces, sub-interfaces, and VLANs.
l Volumes: any logical disks being monitored.
NPM has the following available license levels:
LICENSE NUMBER OF MONITORED ELEMENTS
SL100 Up to 100 nodes, 100 interfaces, and 100 volumes (300 elements in total).
SLX Virtually unlimited number of elements. With the default polling interval, one
polling engine can monitor a maximum of 12,000 elements. To monitor over
12,000 elements, use additional polling engines (APEs). Each APE requires a
license.
Database size increases with the addition of monitored elements.
License NPM with other SolarWinds products

Your NPM license interacts additively with your other SolarWinds licenses.
For example, if you have an NPM SL500 (500 nodes and 500 volumes) installed with SAM AL50, you can
monitor a total of 550 nodes (500 NPM nodes + 50 SAM nodes), 550interfaces, 550volumes (matching the
node count), and 50 application monitors.
page 10
To verify the number of consumed and available component monitors in your license, access the NPM
License Summary.
1. Log on to the SolarWinds Web Console with an administrator account.

2. Click Settings > All Settings.
3. Click License Details in the Details section.
Review the Orion and NPMdetails. You can see the current number of monitored nodes, volumes and
interfaces and the number of the total number of elements allowed by your license.
Manage and activate your NPM license

During installation, you will be prompted to activate your NPMlicense. You need the license key located in
the SolarWinds Customer Portal. For more information on licensing NPM, see the web-based License
Manager information.
page 11
SolarWinds NPM installation preflight checklist
Before installing, complete the pre-installation checklist below. This checklist helps you:
l Verify that system requirements are met, all required software is installed, and required roles and
features are enabled.
l Gather the information required to complete the installation.
Review release Review SolarWinds NPM release notes and available documentation in the
notes Success Center.
Review system Make sure your environment has all of the required hardware, software, and
requirements database requirements for your installations.
l If you are installing into an existing Orion Platform installation, confirm

that your environment meets the Multi-module system guidelines.
l If this is the first Orion Platform product that you are installing, ensure
that your environment meets the system requirements.
Prepare product Review your current product licenses and determine if you need to make any
license changes. You can download any updated license keys through the Customer
Portal.
If you need to modify your licenses, contact your SolarWinds account manager
or SolarWinds.
Gather credentials Make sure you have all account credentials, SQL database credentials, your
SolarWinds account, and local admin server credentials.
Use the Local Administrator Account for installation.
The Local Administrator Account is not the same as a domain account

with local admin rights. A domain account is subject to your domain
group policies.
To download SolarWinds products and licenses, you need a SolarWinds

Customer Portal account. To create your SolarWinds account, see Access the
Customer Portal.
Schedule the Set up the maintenance window, preferably during off-peak hours. Depending
installation on the number of products, size of databases, and size of environment, you may
need hours to complete your installation.
Installations in an existing Orion Platform environment require polling

engines and SolarWinds services to be offline for a length of time,
causing you to lose a portion of polling data.
page 12
Notify your Send a message to your company about the installation schedule and
company maintenance window. If you need additional help with the installation process,
contact and allocate staff to be available.
As part of your preflight, prepare the Orion environment:
1. Prepare the l For new server installations, build the servers based on your deployment
environment size and system requirements.
l For installations into an existing Orion Platform, verify that enough drive
space is available for installations. Products may require significant space
for the downloaded installation ZIP file and installation process.
l For an Orion Platform installation or integration, you may need to build
additional polling engines, and an additional web server. For details, see
the SolarWinds Scalability Guidelines.
If adding SolarWinds High Availability (HA) into your environment, review the HA
requirements and VIP address information. Prepare two matching servers for
installation.
2. Run all Before installation, check for and run all Microsoft Windows Updates on all
Windows updates servers. As you install, if a Windows update runs, your system may reboot as
needed by Windows. The installation cannot complete if your system is waiting
to reboot.
3. Backup existing If you are installing with an existing database, back up the database. If you need
database help, check your vendor's site for documentation and instructions.
If you have your database on a VM, create a snapshot or copy of your VM.
4. Open ports For your server ports and firewall, open ports according to the system
according to requirements. Orion uses these ports to send and receive data.
requirements
5. Check for Determine if any antivirus software is installed on the server or servers where
antivirus software you plan to install. To ensure the installation goes smoothly, exclude the
SolarWinds directory. For example, on Windows Server 2012 R2, exclude
C:\ProgramData\SolarWinds\. For a full list of antivirus exclusions, see
Files and directories to exclude from antivirus scanning.
Do not exclude executable files. SolarWinds assumes that C:\ is the

default volume.
page 13
SolarWinds requirements
l 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.
l 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.
l Multiple Orion server installations using the same database are not supported.
Software requirements
l SolarWinds only supports installing the Orion agent on domain controllers.Do not install
any other SolarWinds products on domain controllers.
l SolarWinds does not support the installation of any Orion product on the same server or
using the same database server as a Microsoft SharePoint, Microsoft Exchange, or Research
in Motion (RIM) Blackberry server.
The following table lists software requirements and recommendations for a SolarWinds installation on
both physical and virtual computers.
SOFTWARE REQUIREMENTS
Production Evaluation Environments Only
Operating l Windows Server2008R2SP1 l Windows7SP1, 64-bit (not Home

system or Starter Editions)
l Windows Server2012 and 2012R2
l Windows Server 2016 l Windows8 (not Standard Edition)
l Windows8.1 (not Standard Edition)
l Windows 10
Installing SolarWindsNPM on Windows Server2012R2 Essentials or Windows

Server Core is not supported.
Operating l English (UK or US)

system
l German
languages
l Japanese
l Simplified Chinese
IP address IPv4
version
page 14
SOFTWARE REQUIREMENTS
IPv6 implemented as a dual stack
CIDR notation is not supported for IPv6 addresses.
Web server Microsoft Internet Information Services (IIS), version7.5 or later
IIS is installed by the SolarWinds installer. You can install this software
manually to reduce your installation time or network bandwidth.
.NET Framework .NET4.5
Compatible with 4.6.1
l SolarWinds recommends using .NET 4.5.2.

l Run the same version of. NET on your primary server and any
Additional Polling Engines or Additional Web Servers in the
environment.
Web console l Microsoft Internet Explorer version11 or later with Active scripting
browser
l Microsoft Edge
l Firefox49.0 or later
l Chrome54.0 or later
Do not enable Enterprise Mode on Internet Explorer. This setting forces

InternetExplorer to emulate version 7, which is not supported.
Other l RabbitMQ (primary messaging service between the primary and additional
polling engines)
l MSMQ (fall back and legacy messaging)
l The SysObjectID on monitored devices must be also accessible from the
Orion server.
The following services must be running after installation is complete to collect syslog
Services
messages and traps:
l SolarWinds Syslog Service

l SolarWinds Trap Service
page 15
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

l Ports 4369, 25672, and 5672 are opened by default on the main server for RabbitMQ
messaging. These ports can be blocked by the firewall.
l RPC ports > 1024 (TCP, bidirectional) is used by the Job Engine v2 process to communicate
with network devices.
l If your devices do not use the default syslog port to send messages, you must also modify
the Orion server to listen to that port.
SERVICE/
PORT PROTOCOL DIRECTION DESCRIPTION ENCRYPTION
PROCESS
25 TCP SolarWinds Alerting Outbound SMTP port for non- n/a

Service V2 encrypted messages
53 UDP SolarWinds Job Bidirectional Resolving DNS queries n/a

Engine v2
page 16
SERVICE/
PROCESS
80 TCP IIS Inbound Default additional web n/a

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 is
http://192.168.0.3:8080
. Open the port to
enable communication
from your computers
to the Orion Web
Console.
The port might also be

used for Cisco UCS
monitoring.
161 UDP SolarWinds Job Outbound Sending and receiving SNMP v1 and
Engine v2 SNMPinformation. v2 are
unencrypted.
SNMP v3 uses
AES &3DES
encryption.
162 UDP SolarWinds Trap Inbound Receiving trap n/a

Service messages
443 TCP IIS Inbound Default port for https SSL

binding.
Also used for bi-

directional ESX/ESXi
server polling, or for
Cisco UCS monitoring.
page 17
SERVICE/
PROCESS
465 TCP SolarWinds Alerting Outbound SMTP port used to SSL

Service V2 send TLS-enabled
email alert actions.
514 UDP SolarWinds Syslog Inbound Receiving syslog n/a

Service messages
587 TCP SolarWindsAlerting Outbound SMTP port used to TLS

Service V2 send TLS-enabled
email alert actions.
1433 TCP SolarWinds Alerting Outbound The port used for n/a
Service V2 communication
between the
SolarWinds
SolarWinds server and
Administration
the SQL Server. Open
Service
the port from your
SolarWinds Orion Web Console to
Information Service the SQL Server.
SolarWinds
Information Service
V3
SolarWinds Orion
Module Engine
1434 UDP SolarWinds Alerting Outbound The port used for n/a
Service V2 communication with
the SQL Server
SolarWinds
Browser Service to
Administration
determine how to
Service
communicate with
SolarWinds certain non-standard
Information Service SQL Server
installations.
SolarWinds
Information Service
V3
SolarWinds Orion
Module Engine
page 18
SERVICE/
PROCESS
1801 TCP MSMQ Bidirectional MSMQ WCF binding WCF
5671 TCP RabbitMQ Bidirectional For encrypted TLS

RabbitMQ messaging
(AMQP/TLS) into the
main polling engine
from all Orion servers.
17777 TCP SolarWinds Orion Bidirectional Orion module traffic. RSA

Module Engine Open the port to handshake,
enable communication AES 256
SolarWinds
from your poller to the communication
Information Service
Orion Web Console, using WCF
SolarWinds and from the Orion
Information Service Web Console to your
V3 poller. Used for
communication
between services.
The port used for

communication
between the Orion
Web Console and the
poller.
Used for
communication
between the main
server and pool
members.
17778 HTTPS SolarWinds Agent Inbound to the Required for access to SSL
Orion server the SWIS API and
agent communication
Hardware requirements
The following table lists minimum hardware requirements and recommendations for your SolarWinds
server on both physical and virtual computers.
page 19
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
retentions or more frequent polling intervals.
Installing multiple SolarWinds Orion Platform products on the same computer may change the
requirements.
Hardware requirements are listed by SolarWinds NPM license level.
HARDWARE SL100, SL250, SL500 SL2000 SLX
CPU Quad core processor or Quad core processor or Quad core processor or
better better better
Do not enable Physical Address Extension (PAE).
Hard drive space 10GB minimum 15 GB minimum 30GB minimum
20 GB recommended 40 GBrecommended 40 GBrecommended
Two 146 GB 15K(RAID 1/Mirrored Settings) hard drives are

recommended with a dedicated drive for the server operating system
and SolarWinds installation.
During upgrades the installer needs 2 GB of free space.
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 4GB minimum 8GB minimum 16GB minimum
8 GB recommended 16 GBrecommended 32 GBrecommended
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.
page 20
If you install on a virtual machine, you must maintain your SQL Server database on a separate,
physical drive.
SL100, SL250,
REQUIREMENTS SL2000 SLX
SL500
SQL Server SolarWinds supports Express, Standard, or Enterprise versions of the

following:
l SQL Server 2008

l SQLServer 2008 SP1
l SQL Server 2008 R2
l SQLServer 2008 R2 SP1
l SQL Server 2012
l SQL Server 2014
l SQLServer 2016
SolarWinds strongly recommends using the 64-bit version of

SQLServer.
l Due to latency effects, SolarWinds does not recommend

installing your SQL Server and your Orion server or additional
polling engine in different locations across a WAN. For more
information, see Install SolarWinds software and SolarWinds
database (SQL Server) across a WAN.
page 21
SL100, SL250,
SL500
l You can set the database recovery model to Full Recovery if your
Orion Database is hosted on a SQLCluster or if you use Always
On Availability. However, you must back up your database
regularly and ensure that volume you store your transaction log
has free space that is at least equal to or greater than the size of
your Orion database. Your transaction logs will continue to grow
indefinitely until a database backup is performed and the
transactions committed to the database. We recommend daily
database backups when you use the Full Recovery model.
l SolarWinds recommends Simple database recovery mode to
ensure best performance.
SQL Server collation l English with collation setting SQL_Latin1_General_CP1_CI_AS

l German with collation setting German_PhoneBook_CI_AS
l Japanese with collation setting Japanese_CI_AS
l Simplified Chinese with collation setting Chinese_PRC_CI_AS
We support case-insensitive database on an CSSQLServer.
We do not support case-sensitive databases.
CPU Quad core processor or Dual quad core Dual quad core
better processor or better processor or better
Hard drive space 20GB minimum 50GB minimum 100GB minimum
40 GB recommended 100 GB recommended 400 GBrecommended
SolarWinds
recommends the
following configuration:
l A hardware RAID
Controller with a
battery backed-up
write back cache
page 22
SL100, SL250,
SL500
l Disk Subsystem 1
Array 1: 2x 146 GB
15K disks RAID 1
(mirroring) for the
OS
l Disc Subsystem 2
Array 2: 2x 146 GB
15K disks RAID 1
(Pagefile + Extra
Storage)
l 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.
l 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
l 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
page 23
SL100, SL250,
SL500
l Disk Subsystem 6
Array 6: with 4x
15k 146 GB or 300
GB disks
configured in a
RAID 0 array for
your tempdblog
file
l Due to intense I/O requirements, a RAID1+0 drive is strongly

recommended for the SolarWinds database, data, and log files
with a dedicated drive for the server operating system and
tempdb files.
l Other RAID configurations can negatively affect your SQL
Server's performance.
l Mirrored drives for the OS and RAID 1+0 for database data files
are recommended.
l Solid state drives (SSD) are recommended for all components.
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 SL100 16 GBminimum 64 GB minimum
4 GBminimum 64 GB recommended 128GB recommended
8GB recommended
SL250 &SL500
8 GB minimum
16 GB recommended
Authentication Either mixed-mode or SQL authentication
Other software If you are managing your SolarWinds Orion database, SolarWinds
recommends you install the SQL Server Management Studio component.
The Installation Wizard installs the following required x86 components if they
are not found on your Orion database server:
page 24
SL100, SL250,
SL500
l SQL Server System Common Language Runtime (CLR) Types. Orion

products use secure SQL CLR stored procedures for selected, non-
business data operations to improve overall performance.
l Microsoft SQL Server Native Client
l Microsoft SQL Server Management Objects
SolarWinds High Availability requirements

High Availability is provided for SolarWinds products released on Orion Platform products version 2016.2
and later. You cannot enable an HA pool for a server that includes non-supported products.
Visit SolarWinds KBMT6886 to build an upgrade path.
SUPPORTED PRODUCTS
l Network Performance Monitor 12.0.1 and later
l Server &Application Monitor 6.3 and later
l NetFlow Traffic Analyzer 4.2.1 and later
l Network Configuration Manager 7.5.1 and later
l IPAddress Manager 4.3.2 and later
l User DeviceTracker 3.2.4 and later
l VoIP&Network Quality Manager 4.2.4 and later
l Storage Resource Monitor 6.3 and later
l Web Performance Monitor 2.2.1 and later
The following products can be integrated with your Orion Platform-based product. The integration module
between products is supported under SolarWinds High Availability, but the stand-alone product is not
supported.
l Storage Manager 6.2.3

l Virtualization Manager 6.3.2 and later
l Firewall Security Manager 6.6.8
l Engineers Toolset 11.0.3 and later
l Database Performance Analyzer on Orion 10.2 and later
l Patch Manager 2.1.3 and later
page 25
SOFTWARE AND HARDWARE REQUIREMENTS
SolarWinds strongly recommends that the hardware and software of the standby server matches
the primary server. Using matching system specifications and installed software ensures the same
performance in the event of a failover.
l Both servers must be installed on Windows Server 2008 R2 or later.

l Both servers must also meet or closely match the minimum hardware and software requirements
for the products you have installed on the primary server.
l Both servers must be able to connect to your SolarWinds Orion database.
l If protecting an NTA environment, both servers must be able to connect to the separate NTA Flow
Storage database.
l SolarWinds does not provide failover support for any database.

l Some SNMP trap, syslog message, and flow data is lost while waiting for the secondary
server to become active.
PORT REQUIREMENTS
P SERVICE/
PORT DIRECTION DESCRIPTION
ROTOCOL PROCESS
4369 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the
main and secondary servers to allow RabbitMQ
clustering between the two servers. These ports
exchange EPMD and Erlang distribution protocol
messages for RabbbitMQ. They do not need to be open
in additional polling engine pools.
5671 TCP SolarWinds bidirectional Port 5671 must be open into the HA pool with the main
High Orion server from all Orion servers.
Availability
25672 TCP RabbitMQ bidirectional TCP ports 4369 and 25672 must be open between the
main and secondary servers to allow RabbitMQ
clustering between the two servers. These ports
exchange EPMD and Erlang distribution protocol
messages for RabbbitMQ. They do not need to be open
in additional polling engine pools.
page 26
NETWORKING REQUIREMENTS
SolarWinds High Availability does not support IPv6 addresses.
l Both your primary and secondary servers must be on the same subnet.
l Both pool members must have static IPv4 addresses set on the network adapter. You do not need
dedicated NICs.
l All pool members must be able to resolve the host names of all additional pollers, additional
websites, and the main Orion server. Pool members must also be able to resolve the host names of
members in the same pool.
l A virtual IP address must be available on the same subnet as the primary and secondary servers.
l Devices must be able to accept inbound connections from the source IP and VIP addresses.
l Devices sending syslogs, SNMPtraps, and NetFlow information to your Orion server must be
configured to send the information to the VIP address and receive requests from the pool.
You may need to modify firewall rules to allow traffic from pool members and to the VIP address. For
example, you may need to modify the NetFlow firewall rules to allow incoming TCP traffic on port
2055 to go to the VIP address.
Depending on your network, you may have additional requirements. Up to three IPaddresses per pool may
be in use among the VIP, primary, and secondary servers because of how Windows calculates the source IP
address from the HA pool. You can modify your devices to receive requests from all IP addresses or
determine whichIPaddress is used as the source IP address.
page 27
Multi-module system guidelines
If you have more than one Orion Platform product, use these recommended guidelines for hardware and
software deployment. The information here should be considered guidelines only. You can choose to use
more or less hardware but your performance may vary depending on your deployment scenario.
If you have only one Orion module, see the system requirements listed in the administrator guide for that
module.
Small deployment guidelines

Modules You can install NTA as part of a small deployment, but it is not included in this
configuration. Use the Medium Deployment guidelines for NTA.
Choose up to 3 modules:
l NPM SL100 - SL500 (including up to 10 remote agents for DPI)

l SAM AL150 - AL300
l WPM 5 - WPM 20
l VNQM IPSLA 5 - IPSLA 25 (up to 5,000 operations)
l NCM DL50 - DL200
l IPAM IP1000 - IP4000
l UDT UT2500 - 5000
Orion Physical server or virtual machine

Application
Server l Quad core processor or better
Specifications l 8-16 GB RAM
l 150 GB, 15,000 RPM
l 1 x 1 Gb dedicated NIC
l Windows Server 2016, 2012 R2, 2012, or 2008 R2 SP1
The Orion installer installs IIS(32-bit mode) and .NET4.5 if they are not already on your
server.
SQL Database Physical server recommended

Server
Specifications l Quad core processor or better
l 16 GB RAM
l 100 GB 1 (or more) storage in RAID1+0 configuration (RAID5 not supported)
l Microsoft SQLServer 2016, 2014, 2012, or 2008 R2 Standard Edition
page 28
1More or less space may be needed depending on your data retention policies, number of elements
measured, and polling frequency.
Medium deployment guidelines

Modules NPM SL500 - SL2000
NTA for NPM SL2000
l 50,000 FPSreceived sustained on the main poller
2 - 4 additional modules:
l SAM AL700 - AL1100

l WPM 50 - WPM 200
l VNQM IPSLA 25 - IPSLA 50 (up to 10,000 operations)
l NCM DL500 - DL1000
l IPAM IP16,000
l UDT UT10,000 - 25,000
Orion Application Physical server or virtual machine

Server Specifications
l Quad core processor or better
l 16 GB RAM
l 150 GB, 15,000 RPM
The Orion installer installs IIS(32-bit mode) and .NET 4.5 if they are not already
on your server.

Server Specifications
l Dual quad core processor or better
l 64 GB RAM
l 250 GB 2 (or more) storage in RAID1+0 configuration (RAID5 not
supported)
l HardwareRAIDController (software RAIDnot supported)
NTA Flow Storage Physical server or virtual machine

Database
Server Specifications l Quad core processor or better
l 16 GB 3 RAM
page 29
l 100 GB - 1 TB 4 of storage capacity on local NTFS disk
l Windows Server 2012 R2, 2012, or 2008R2 SP1
NTA-SPECIFIC INFORMATION
l NTA4.0 - If the server is running a 32-bit operating system, NTA4.0 stores flow data in the
SQLDatabase (NTAFlow Storage Database is not installed).For more information, see NTA4.0
Installation:Frequently Asked Questions.
l NTA 4.1 - NTA4.1 only works with a 64-bit operating system. SolarWinds recommends aseparate
NTAFlow Storage Database.
2More or less space may be needed depending on your data retention policies, number of elements
measured, and polling frequency.

3RAMfor the NTAFlow Storage Database should be increased as the database size increases.
4More or less space may be needed depending on your data retention policies and the number of flows
stored. You need approximately 8 GB of additional storage for every 1000 flows that are retained for 30
days. For example, if you want 50,000 flows stored for 30 days, you need a base of 100 GBplus an
additional 400 GB of storage.
Large deployment guidelines

Modules NPM SLX (with multiple pollers)
NTA for NPM SLX
l 50,000 FPSreceived sustained on the main poller

l Up to 6 pollers (5 in addition to the main poller) for 300,000 FPSreceived
sustained
Any combination of these modules:
l SAM ALX
l 1 APE for every 10,000 component monitors
l Maximum of 50,000 component monitors per primary Orion SAMserver + 4
APEs
l VNQM IPX
l ~5,000 IPSLA operations per polling engine
l NCM DLX
l 1 APE for every 10,000 devices, for NCM 7.1 and later
l Maximum of 30,000 devices per NCMinstance (that is, NCM server + 2 NCM
APEs)
page 30
l IPAM IPX
l 750,000 IP
l UDT UTX
l 150,000 ports per polling engine
Orion Physical server or virtual machine

Application
Server l Quad core processor or better
Specifications l 32 GB RAM
l 150 GB, 15,000 RPM
server.

Server
Specifications l Dual quad core processor or better
l 128 GB RAM
l HardwareRAIDController (software RAIDnot supported)
l Disk Subsystem 1 Array 1: 2 x 146 GB15,000 disks RAID1 (mirroring) operating
system
l Disk Subsystem 2 Array 2: 2 x 146 GB 15,000disks RAID1 (Pagefile + extra
storage)
l Disk Subsystem 3 Array 3: with 6x 15,000 146 GB or 300 GB disks configured in a
RAID1+0 arrays to allow for maximum write performance. This is for your
SQLMDF ANDFILEGROUPS
l Disk Subsystem 4 Array 4: with 4x 15,000 146 GB or 300 GBdisks configured in a
RAID1+0 arrays to allow for maximum write performance.This is for your
SQLLDFTransaction LOGfile
l 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
l Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a
RAID 0 array for your tempdblog file
l 1 GbLANport
page 31
NTA Flow Physical server or virtual machine
Storage
Database l Quad core processor or better
Server l 16 GB 3 RAM
Specifications l 100 GB - 1 TB 4 of storage capacity on local NTFS disk
l Windows Server 2012 R2, 2012, or 2008R2
Additional Virtual machine recommended

Polling
Engine l Quad coreprocessor or better
Server l 32 GBRAM
Specifications l 150 GB, 15,000 RPM
l 1 x 1 Gbdedicated NIC
l Windows Server 2016, 2012 R2, 2012, or 2008 R2
server.
NTA-SPECIFIC INFORMATION
l NTA4.0 - If the server is running a 32-bit operating system, NTA4.0 stores flow data in the
SQLDatabase (NTAFlow Storage Database is not installed).For more information, see NTA4.0
Installation:Frequently Asked Questions.
l NTA 4.1 - 5TH4.1 only works with a 64-bit operating system. SolarWinds recommends aseparate
NTAFlow Storage Database.
page 32
Prepare the Orion database

The SolarWinds Orion database stores all monitoring data.
For Orion Platform products, use a new or existing SQL database. Prepare your database using the
following guidelines.
Make sure the database and database server meet the system requirements.
Ensure that you install the Orion database and the Orion Server on the same domain.
The selected SQL Server instance must support mixed-mode or SQL authentication with strong
passwords. A strong password must meet at least three of the following four criteria:
l Contains at least one uppercase letter

l Contains at least one lowercase letter
l Contains at least one number
l Contains at least one non-alphanumeric character, for example, #, %, or ^
For a new database, the user account must be a member of the dbcreator server role. The
sysadmin role and the security administrator (SA) user account are always members of dbcreator.
For a new SQL account, the user account must be a member of the securityadmin server role. The
sysadmin role and the security administrator user account are always members of securityadmin.
Set the recovery model of the database to Simple. SolarWinds does not support other methods.
Select SQL Server Authentication. SolarWinds Orion users use this method to access the SolarWinds
Orion database.
SolarWinds uses SQL Server Authentication to ensure the SolarWinds Orion server can always
access the SolarWinds Orion database, even when hosted remotely on a separate server.
page 33
Install a licensed copy of NPM
These instructions provide stand-alone installation steps for installing SolarWinds Network Performance
Monitor on a dedicated server.
For advanced configuration requirements and steps such as FIPS, see the Administrator Guide.
Do not install SolarWinds NPM on a domain controller or use the same database server as a
Research in Motion (RIM) Blackberry server.
1. Download If you have not yet created a SolarWinds account, see Access the Customer Portal to
installation create an account.
files and
license from 1. Go to customerportal.solarwinds.com.
Customer 2. In the Log In tab, enter your organization's SWID and your email address.
Portal 3. In the Latest Downloads table, click Choose Download for the installation files
for your product. Also check and download any available hotfixes.
4. Depending on your environment, you may also need installers for the
additional polling engines and additional web server. These installers include a
bundle or a Scalability Engine.
SolarWinds recommends using the Scalability Engine Installer for your

additional polling engine and additional web server.
2. Run the 1. Log in as an administrator to the Orion server.

installation
2. Extract the contents of the downloaded installation ZIP file to the server.
file
3. Run SolarWinds-NPM-<version>-Full.exe.
3. Complete 1. Click Next on the Welcome window.

the The system scans the environment to ensure that the system requirements are
Installation met. If your system is not compatible, the installer provides a link to a
wizard knowledge base article with the resolution. When resolved, run the installation
again.
2. Select your preferred language.

3. If the wizard detects that Microsoft Internet Information Services (IIS) is not
installed, select the recommended option to continue and install IIS
automatically.
4. If the wizard detects that the Microsoft .Net framework is not installed, select
the recommended option to continue and install it automatically.
Downloading and installing Microsoft .NET Framework 4.5 can take more
than 20 minutes. If your system reboots, run the installation again.
page 34
5. Accept the terms of the license agreement.

6. Accept the default directory, or click Browse and select a directory.
7. Enable Quality of Experience (QoE) traffic monitoring.
Enabling QoE installs an agent on the Orion Main Polling Engine. This agent
collects packet-level traffic statistics, like network response time and
application response time, for any application traffic it sees going to or from
Orion. SolarWinds recommends that you enable QoE.
8. Click Next to begin copying the files.

If you are using Microsoft Internet Explorer, SolarWinds recommends you add
the URL of your Orion website (http://FullOrionServerName/), the URL of
SolarWinds support (http://solarwinds.com/support), and about:blank to the
list of trusted sites.
4. Run the After the installation completes, the Configuration wizard automatically runs. If the
Configuratio Configuration wizard does not load automatically, start the Configuration wizard in
n wizard the SolarWinds Orion > Configuration and Auto-Discovery program folder.
1. In the Welcome dialog box, click Next.

2. If prompted to stop services, click Yes.
3. In the Database Settings dialog box, select an SQL Server and authentication
method, and click Next.
Use SQL Server Authentication to ensure the SolarWinds Orion server
can always access SQL Server, even when hosted remotely on a separate
server.
page 35
4. In the Database Settings dialog box, select a database from Use an existing
database, and click Next.
5. In the Database Account dialog box, create an account or use an existing
account that the polling engine and Web Console use to access the database,
and click Next.
6. In the Website Settings dialog box, complete selections for your installation:
If you select Skip website binding, the Configuration Wizard does not
make changes within the website configuration in your IIS. This option
blocks IPaddress, port, and SSLcertificate options.
a. Select All Unassigned unless your environment requires a specific IP

address for the Orion Web Console. The Port is 443 by default.
b. Specify the Port and the Website Root Directory where the system installs
the Web Console files.
If you specify any port other than 80, include that port in the URL
used to access the Web Console.
c. To configure SSL, click Enable HTTPS and select your SSLcertificate.

If a certificate is not available, select the option to Generate Self-Signed
Certificate. The Configuration Wizard automatically generates a self-
signed certificate issued to the hostname or FQDN and adds it to the
trusted certificate store.
7. If prompted to create a directory or website, click Yes.

8. Review the list of services to install, and click Next.
9. Click Yes if prompted to disable the SNMP Trap Service and enable the
SolarWinds Trap Service.
page 36
10. In the Completing the Orion Configuration Wizard dialog box, click Next.
11. If prompted to activate your installation, enter the License Key for your
product noted from the SolarWinds Customer Portal.
12. When completed, click Finish to launch the Orion Web Console.
Click Start > All Programs > SolarWinds > Orion Web Console
or
Open a web browser on your Orion server and enter http://ipAddress or
http://hostname, where ipAddress is the IP address of your server and
hostname is the host name of your server.
13. Log in with user name admin and leave the password field blank.
For security purposes, SolarWinds recommends that you change the password
to your admin account.
5. Install any If the Customer Portal listed hotfixes for the product version you downloaded, run
available those installations.
hotfixes
(optional) 1. Download the zip file.
2. Extract the zip files to the main polling engine or Orion server.
3. Review the READMEfor details on the release and further instructions.
4. Run the installation file according to the READMEinstructions.
6. Add If you are not prompted to activate the product license during installation, activate
license key the license through the Orion Web Console.
Get the license key for your product from the Customer Portal:
1. In the Customer Portal, select License Management.

2. Select the product.
3. Copy the license key.
Add and activate the license key from the Customer Portal.
1. Open the Orion Web Console in a web browser.

2. Click Settings > All Settings > License Manager.
3. Click Add/Upgrade License.
4. Enter the Activation Key and Registration Information, and click Activate.
To activate an offline license, see Activate licenses offline.
7. Install on If you have an additional polling engine (APE), download and install the product using
the the Scalability Engine Installer.
additional
polling 1. In the Orion Web Console, click Settings > All Settings > Polling Engines.
page 37
engine 2. Click the Download Installer Now and move the downloaded file to the
(optional) additional polling engine server.
3. Run the installation file. The steps should mirror the installation steps
completed on the main polling engine server. During installation, select the
option for Additional Polling Engine.
4. To activate the license, access the Orion Web Console on the main polling
engine or Orion server.
Do not activate the license directly on the additional polling engine.

8. You may need to assign the license to the additional polling engine.
a. Click Assign.
b. Select the additional polling engine and click Assign.
9. Repeat these instructions for multiple additional polling engines.
Best Practice: If the product included hotfixes, you can also run those directly on the
additional polling engines. The Scalability Engine Installer should have included
them. If the hotfix installation states the fixes are already installed, do not continue.
Otherwise, complete the installation instructions from the README file.
8. Install on If you have an additional web server (AWS), download and install the product using
additional
web server 1. In the Orion Web Console, click Settings > All Settings > Web Console Settings.
(optional) 2. Click the Download Installer Now and move the downloaded file to the
additional polling engine server.
option for Additional Web Server.

8. You may need to assign the license to the additional web server.
a. Click Assign.
b. Select the additional web server and click Assign.
page 38
additional web server. The Scalability Engine Installer should have included them. If
the hotfix installation states the fixes are already installed, do not continue.
page 39
Integrate NPM with other Orion Platform
products
To integrate SolarWinds Network Performance Monitor with an existing Orion Platform, you may need to
install the stand-alone product onto the Orion server and perform additional steps. These instructions
walk-through the specific installation steps, Configuration wizard selections, and any additional licensing
and integration options to select.
Consider these guidelines for your installation:
l When integrating with the existing Orion SQLdatabase, the user account needs only to be in the
db_owner database role for the existing database.
l For advanced configuration requirements and steps such as FIPS, see the Administrator Guide.
l If you have High Availability as part of your Orion Platform installation, review Install SolarWinds
NPM with High Availability
l Install NPM on the Orion server with other products including NCM, SAM, and SRM.
l Installing products on the same server provides a single pane of glass for monitoring: consolidates
polling calls and traffic through polling methods, stores and tracks nodes in one system without
cross-referencing, provides data for alerts and reports on one system, and manages all logic easily
on one system.
l Select the same Orion SQL database used by the current Orion Platform environment.
l If you need to migrate Orion products and install NPM on a new server due to requirements,
migrate the Orion products first.
Adding a new product into an existing Orion Platform may require upgrading the current products
prior to the installation.
l Using compatibility information and the SolarWinds Product Upgrade Advisor, determine if
currently installed products must be upgraded prior to installing this product.
l Depending on the upgrade path, upgrade products following the SolarWinds Upgrade
Guide. When complete, install the new product following these instructions.
l When preparing the server, review the multi-module system guidelines when installing into
an existing Orion Platform.
1. Install the Follow the stand-alone installation instructions.

product
1. Click Next on the Welcome window.
The system scans the environment to ensure that the system requirements are
met. If your system is not compatible, the installer provides a link to a knowledge
base article with the resolution. When resolved, run the installation again.
2. Select your preferred language.
page 40
3. If the wizard detects that Microsoft Internet Information Services (IIS) is not
installed, select the recommended option to continue and install IIS
automatically.
4. If the wizard detects that the Microsoft .Net framework is not installed, select
the recommended option to continue and install it automatically.
5. Accept the terms of the license agreement.

6. Accept the default directory, or click Browse and select a directory.
7. Enable Quality of Experience (QoE) traffic monitoring.
Enabling QoE installs an agent on the Orion Main Polling Engine. This agent
collects packet-level traffic statistics, like network response time and application
response time, for any application traffic it sees going to or from Orion.
SolarWinds recommends that you enable QoE.
8. Click Next to begin copying the files.

If you are using Microsoft Internet Explorer, SolarWinds recommends you add
the URL of your Orion website (http://FullOrionServerName/), the URL of
SolarWinds support (http://solarwinds.com/support), and about:blank to the
list of trusted sites.
2. Run the After the installation completes, the Configuration wizard automatically runs. If the
Configuratio Configuration wizard does not load automatically, start the Configuration wizard in the
n wizard SolarWinds Orion > Configuration and Auto-Discovery program folder.
1. In the Welcome dialog box, click Next.

2. If prompted to stop services, click Yes.
page 41
3. In the Database Settings dialog box, select an SQL Server and authentication
method, and click Next.
Use SQL Server Authentication to ensure the SolarWinds Orion server can
always access SQL Server, even when hosted remotely on a separate
server.
4. In the Database Settings dialog box, select a database from Use an existing
database, and click Next.
5. In the Database Account dialog box, create an account or use an existing
account that the polling engine and Web Console use to access the database,
and click Next.
page 42
6. In the Website Settings dialog box, complete selections for your installation:
If you select Skip website binding, the Configuration Wizard does not
make changes within the website configuration in your IIS. This option
blocks IPaddress, port, and SSLcertificate options.
a. Select All Unassigned unless your environment requires a specific IP

address for the Orion Web Console. The Port is 443 by default.
b. Specify the Port and the Website Root Directory where the system installs
the Web Console files.
If you specify any port other than 80, include that port in the URL
used to access the Web Console.
c. To configure SSL, click Enable HTTPS and select your SSLcertificate.

If a certificate is not available, select the option to Generate Self-Signed
Certificate. The Configuration Wizard automatically generates a self-
signed certificate issued to the hostname or FQDN and adds it to the
trusted certificate store.
7. If prompted to create a directory or website, click Yes.

8. Review the list of services to install, and click Next.
9. Click Yes if prompted to disable the SNMP Trap Service and enable the
SolarWinds Trap Service.
10. In the Completing the Orion Configuration Wizard dialog box, click Next.
11. If prompted to activate your installation, enter the License Key for your product
noted from the SolarWinds Customer Portal.
page 43
12. When completed, click Finish to launch the Orion Web Console.
or
13. Log in with user name admin and leave the password field blank.
3. Install any If the Customer Portal listed hotfixes for the product version you downloaded, run
available those installations.
hotfixes
(optional) 1. Download the zip file.
2. Extract the zip files to the main polling engine or Orion server.
3. Review the READMEfor details on the release and further instructions.
4. Run the installation file according to the READMEinstructions.
4. Add Add and activate the license key from the Customer Portal.
license key
1. Open the Orion Web Console in a web browser.
or

To activate an offline license, see Activate licenses offline.
5. Integrate
the product
into the
Orion
Platform
6. Install on If you have an additional polling engine (APE), download and install the product using
additional
page 44
polling 1. In the Orion Web Console, click Settings > All Settings > Polling Engines.
engine
2. Click the Download Installer Now and move the downloaded file to the
(optional)
option for Additional Polling Engine.

8. You may need to assign the license to the additional polling engine.
a. Click Assign.
b. Select the additional polling engine and click Assign.
9. Repeat these instructions for multiple additional polling engines.
additional polling engines. The Scalability Engine Installer should have included them.
If the hotfix installation states the fixes are already installed, do not continue.
7. Install on If you have an additional web server (AWS), download and install the product using
additional
web server 1. In the Orion Web Console, click Settings > All Settings > Web Console Settings.
(optional) 2. Click the Download Installer Now and move the downloaded file to the
option for Additional Web Server.

page 45
8. You may need to assign the license to the additional web server.
a. Click Assign.
b. Select the additional web server and click Assign.
additional web server. The Scalability Engine Installer should have included them. If
the hotfix installation states the fixes are already installed, do not continue. Otherwise,
complete the installation instructions from the README file.
page 46
Install SolarWinds NPM with High Availability

The following instructions detail how to install an Orion product with a new High Availability (HA) pool or
with existing HApools.
Install with new HA

Both primary and secondary servers in the HApool must match and have the exact same Orion products
and versions installed.
If you have enabled SolarWinds High Availability, you must disable HA before you can install. All
SolarWinds product versions must match on the primary and secondary servers before you can re-
enable your HA pools.
For more information on SolarWinds HA, see High Availability in SolarWinds products.
Before you begin, you need the following:
l A VIP address
l The secondary HA server
l An available HA pool license
1. Prepare the 1. Reserve an available IP address to use as the Virtual IP (VIP) address on
secondary server the same subnet as the primary and secondary servers.
2. Build a standby server on the same subnet as the server you want to
protect.
3. Open port 5671 (TCP) on the primary (incoming) and secondary
(outgoing) servers.
4. Open ports 4369 and 25672 (TCP) on the main Orion server and its
secondary server. These ports are not required when protecting
additional polling engines.
2. Install on the Follow the install instructions for the product. Install on the primary server.
primary server
Do not run the product installer on the secondary server. The HA process
creates the secondary server installer.
3. Activate the HA Have your HA license from the Customer Portal to activate prior to creating a
license pool. The License Manager through the Orion Web Console provides a 30-day
evaluation license to test HA features.

2. Select the HA license.
3. Click Activate.
page 47
4. Enter your license information.
If you do not have a license key, enable the HA evaluation license.
4. Download and HA provides a downloadable installer from the primary server with a list of all
install secondary products and versions. This installer ensures both servers match.
server
1. In the Orion Web Console, click Settings > All Settings > High Availability
Deployment Summary.
2. Click Setup a new HA server.
3. In the dialog box, click Get started setting up a server.
4. In the Setup a High Availability Server dialog box, click Download
installer now.
5. Move the downloaded installer to your secondary server and run it.
Select which type of backup server you want to install under High
Availability.
Enter your SQL credentials for your Orion SQL database when
prompted.
5. Create the HA You can now add the backup server to a pool with your main server or
pool additional polling engine.
Deployment Summary.
2. Click Setup High Availability pool next to your standby server.
3. Enter the pool name and the virtual IP (VIP) address.
The VIP must be unassigned and on the same subnet as the primary and
secondary servers.
4. Click Create Pool to complete the pool setup.
Install with existing HA

These instructions define how to install your product into an existing server pair in a SolarWinds High
Availability (HA) pool. Both primary and secondary servers in the pool must match and have the exact same
Orion products and versions installed.
If you have enabled SolarWinds High Availability, you must disable HA before you can install. All
SolarWinds product versions must match on the primary and secondary servers before you can re-
enable your HA pools.
These instructions assume you have an HA pool already created and enabled. For more information on
SolarWinds HA, see High Availability in SolarWinds products.
page 48
1. Disable the HA The HA pool must be disabled to begin installation. If you install prior to
pool disabling, the pool is automatically disabled.
Deployment Summary.
2. Select the pool you want to disable.
3. Toggle High Availability to Off.
Do not modify the VIP or IP settings for the servers.
2. Install on the Follow the installation instructions on the primary server.

primary server
3. Install on the Follow the install instructions on the secondary server.

secondary server
4. Enable the HA After the servers are installed, enable the HA pool using the following
pool instructions. You may need to recreate the HA pool. For details, see Set up an
HA pool for NPM.
Deployment Summary.
2. Select the pool you want to enable.
3. Toggle High Availability to On.

The Orion Web Console verifies all SolarWinds product versions match
across the HA pair before enabling. If you receive errors, check your
product versions.
page 49
Enable FIPS
You can run your Orion Platform product in FIPS-compliant (Federal Information Processing Standard)
mode to comply with computer security and interoperability standards used by non-military US
government agencies and contractors.
For the full list of tested Orion products for international standards for computer security, see this
site. For a certification letter of Orion FIPScompliance, contact us with your request.
l If FIPS compliance is required, SolarWinds recommends that you enable FIPS as part of a
fresh install instead of as part of an upgrade.
l Before you enable FIPS ensure that the hardware is FIPS-compliant. See the Microsoft
Support knowledge base for more information.
l Not all Orion Platform products are FIPS-compliant. SolarWinds recommends that you
install all FIPS-compliant SolarWinds software on FIPS-compliant servers and maintain all
non-compliant SolarWinds software on non-compliant servers.
1. Configure the Orion server for FIPS compliance.

2. Start the SolarWinds FIPS 140-2 Manager (SolarWinds.FipsManager.exe).
By default, SolarWinds.FipsManager.exe is located in the C:\Program Files (x86)
\SolarWinds\Orion folder.
page 50
3. Read the welcome text, and click Next.

The SolarWinds FIPS 140-2 Manager confirms that the current configuration of your SolarWinds
products is FIPS-compliant.
l If an installed product is not FIPS-compliant, click Close, remove any non-compliant Orion
Platform products from the FIPS-compliant server, and run the FIPS 140-2 Manager again.
l If FIPS 140-2 is disabled, select Enable FIPS 140-2, and click Next.
l If the FIPS Manager provides a list of objects or saved network discovery definitions that are
not FIPS-enabled, complete the following steps.
To refresh the list of non-compliant objects after editing the credentials, restart the FIPS
140-2 Manager.
l Click the non-compliant monitored node, and edit its Polling Method to be FIPS-
compliant.
a. Select SNMPv3 as the SNMP Version.
b. Select FIPS-compliant Authentication and Privacy/Encryption methods, and
provide the passwords.
c. Click Submit.
l Click the non-compliant network discovery, and edit SNMP credentials to be FIPS-
compliant.
a. Confirm that all SNMP credentials are SNMPv3. Delete or edit any credentials that
are not FIPS-compliant SNMPv3.
b. Confirm that all SNMP credentials use FIPS-compliant Authentication and
Privacy/Encryption methods, and provide the passwords.
c. Complete the Network Sonar Wizard using the updated credentials.
4. Click Restart now to restart all relevant SolarWinds services.
While the software is FIPS-compliant, you must choose to use FIPS-compliant polling methods, such as
SNMPv3, to monitor and discover nodes.
FIPS-COMPLIANT METHODS FOR SNMPV3
Authentication SHA1
Privacy or encryption AES128, AES192, AES256
page 51
Install an evaluation copy of SolarWinds NPM
The evaluation version of this product is a full version of the product, functional for 30 days. After the
evaluation period, you can easily convert your evaluation license to a production license by obtaining and
applying a license key.
To update your license, contact SolarWinds sales to purchase a full license of the product. For Orion
products, access the License Manager to update the license with the purchased key. For details, see
Activate licenses.
For evaluation installations only, you can install the Orion server and the Microsoft SQL Server
database on the same machine. The installer automatically installs SQL Server 2014. You can use that
database, or configure the server to use another MS SQL database.
l Do not use MS SQL Server Express in a production deployment.

l Before you install SQL Express 2014 on the same computer as the Orion server, ensure .NET
3.5 is installed.
To use a separate Microsoft SQL Server database, or if you are installing this product into the production
deployment of an existing Orion Platform, see Plan for a production deployment.
For evaluation installations only, installation on a desktop operating system is possible, but not supported.
This product is intended for use in a production environment that meets system requirements.
EVALUATION AND PRODUCTION

EVALUATION ENVIRONMENTS ONLY
ENVIRONMENTS
Windows Server 2008 R2 SP1 Windows 7 64-bit SP1
Windows Server 2012 Windows 8 (except for Standard Edition)
Windows Server 2012 R2 Windows 8.1 (except for Standard Edition)
Windows Server 2016 Windows 8.1 Update 1 (except for Standard Edition)
Windows 8.1 Pro, and Windows 8.1 Enterprise (Pro or Enterprise

version recommended)
Windows 10
To install an evaluation copy of your product:
1. Download the Download the evaluation file for SolarWinds NPM from www.solarwinds.com.
evaluation file
page 52
2. Install using the Follow the standalone installation instructions including the installation and
stand-alone Configuration wizard.
instructions
To use the Microsoft SQL Server Express database that installs with the
product, click Express Install. To use your own Microsoft SQL Server database,
click Advanced Install.
3. Open the Orion If the login page does not open automatically, launch the Orion Web Console in
Web Console your SolarWinds Orion program folder.
Log in with the user name admin and leave the password field blank.
After the evaluation period, you can easily convert your evaluation license to a production license by
obtaining and applying a license key.
page 53
Steps to take after SolarWinds NPM is installed
After SolarWinds NPM is installed, there are a variety of resources you can access to learn the product.
l SolarWinds NPM Getting Started Guide - Get Started: SolarWinds recommends reading the
SolarWinds NPM Getting Started Guide first. Learn about how to configure SolarWinds NPM, begin
collecting data, and alert and report on your mission-critical environment.
Quickly identify performance issues and problems before your customers call the help desk.
Depending on your workload, you should be able to get started in five days or less.
l SolarWinds NPM Getting Started Guide - Customize: Learn how to customize views, alerts, and
reports.
Tailor SolarWinds NPM to your internal processes so you can more effectively respond to
performance issues. Depending on your workload, you should be able to customize SolarWinds NPM
in five or fewer days.
l SolarWinds NPM Administrator Guide: Refer to the SolarWinds NPM Administrator Guide for a
deeper dive into SolarWinds NPM features.
l SolarWinds Customer Success Center: Access the Customer Success Center for all SolarWinds NPM
documentation and troubleshooting knowledge base articles.
l SolarWinds NPM on THWACK: Interact with SolarWinds VNQM Pros who provide answers to your
questions and share lessons learned.
page 54
Uninstall SolarWinds NPM

Uninstalling products may require uninstalling files and editing registries. For technical assistance,
contact Support.
You may need to uninstall SolarWinds NPM to reinstall for resolving issues or to move to a new server
during a migration.
Prior to uninstalling, SolarWinds recommends the following preparation:
Backup the To preserve your data, back up your database(s). If you need help with backups,
existing database check your vendor's site for documentation and instructions.
If you have your database on a VM, create a snapshot or copy of your VM.
If you need software to perform backups and maintenance for Microsoft

SQLdatabases, you can install SQL Management Studio Express for your specific
version of Microsoft SQL on your database server.
Use one of the following links to download the installation:
l SQL Management Studio Express 2008

Backup product Create copies and backups of your product folders. You may have
folders customizations in these folders specific to your installations.
To remove SolarWinds Network Performance Monitor from a server, complete the following steps:
1. Remove product Follow the steps for your specific product to remove the SolarWinds
licenses product licenses.
1. In the Orion Web Console, select Settings > All Settings > and click
License Manager.
2. In the web-based License Manager, select the product license to
remove.
3. Click Deactivate. This removes the license activation and server
assignment.
With the license deactivated, it is parked, or available but unused.
2. Uninstall SolarWinds 1. Open Programs and Features in the Windows Control Panel.
products 2. Select the product(s) to remove one at a time and click Uninstall.
page 55
3. Delete or rename Delete files from the following locations to fully clear all files. If you
SolarWinds folders installed to a different domain, look on that location instead of C:\.
l C:\Program Files (x86)\SolarWinds

l C:\Program Files (x86)\Common Files\SolarWinds
l C:\inetpub\SolarWinds
l C:\ProgramData\Solarwinds
l C:\ProgramData\SolarWindsAgentInstall
4. Remove specific Important: These steps affect your Registry settings. For assistance,
Registry keys contact Support.
1. Open the command line interface on the server.

2. Type regedit, and click OK.
3. Expand HKEY_LOCAL_MACHINE > Software.
4. Delete both the SolarWinds and the SolarWinds.net folders.
5. If you are uninstalling from a 64-bit computer, expand HKEY_
LOCAL_MACHINE > Software > Wow6432Node, and delete both
the SolarWinds and the SolarWinds.net folders.
5. Restart and reinstall Restart the server. You can reinstall new products following this guide.
page 56

NPM Installation Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

NPM Installation Guide

Enviado por

Direitos autorais:

Formatos disponíveis

INSTALLATION GUIDE

Last Updated: June 7, 2017

Retrieve the latest version from: https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/NPM_Documentation

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED,

Integrated with the OrionPlatform 7

License NPM with other SolarWinds products 10

Manage and activate your NPM license 11

SolarWinds NPM installation preflight checklist 12

Server port requirements 16

Database server (SQL Server) requirements 20

SolarWinds High Availability requirements 25

Software and Hardware requirements 26

Multi-module system guidelines 28

Small deployment guidelines 28

Medium deployment guidelines 29

Large deployment guidelines 30

Prepare the Orion database 33

Install a licensed copy of NPM 34

Integrate NPM with other Orion Platform products 40

Install SolarWinds NPM with High Availability 47

Install with new HA 47

Install with existing HA 48

Install an evaluation copy of SolarWinds NPM 52

Steps to take after SolarWinds NPM is installed 54

Uninstall SolarWinds NPM 55

l Fault, performance, and availability monitoring

This guide supports the following installation scenarios:

l Plan for NPM installation

Integrated with the OrionPlatform

Additional Polling Engine (APE)

Additional Web Server (AWS)

High Availability (HA)

Orion Application Server

Orion Database Server

Polling Engine (Poller)

Orion Web Console:

Check out this video on navigating the Web Console.

NPM has the following available license levels:

LICENSE NUMBER OF MONITORED ELEMENTS

Database size increases with the addition of monitored elements.

License NPM with other SolarWinds products

1. Log on to the SolarWinds Web Console with an administrator account.

Manage and activate your NPM license

l If you are installing into an existing Orion Platform installation, confirm

Use the Local Administrator Account for installation.

The Local Administrator Account is not the same as a domain account

To download SolarWinds products and licenses, you need a SolarWinds

Installations in an existing Orion Platform environment require polling

As part of your preflight, prepare the Orion environment:

Do not exclude executable files. SolarWinds assumes that C:\ is the

Production Evaluation Environments Only

Operating l Windows Server2008R2SP1 l Windows7SP1, 64-bit (not Home

Installing SolarWindsNPM on Windows Server2012R2 Essentials or Windows

Operating l English (UK or US)

IPv6 implemented as a dual stack

CIDR notation is not supported for IPv6 addresses.

Web server Microsoft Internet Information Services (IIS), version7.5 or later

.NET Framework .NET4.5

Compatible with 4.6.1

l SolarWinds recommends using .NET 4.5.2.

Do not enable Enterprise Mode on Internet Explorer. This setting forces

l SolarWinds Syslog Service

Server port requirements

25 TCP SolarWinds Alerting Outbound SMTP port for non- n/a