0
/ Published in Product, SolarWinds

SolarWinds Network Performance Monitor (NPM)

SolarWinds is one of the outstanding producers of IT management software. The company’s Network Performance Monitor (NPM) is one of its key product. This system focuses on monitoring the health of the devices connected to a network. The hardware that SolarWinds NPM keeps an eye on includes network equipment, such as routers and switches; endpoint devices, including terminals, desktop PCs, and mobile devices; and office equipment, such as printers. The constant monitoring process gathers metrics that serve troubleshooting tasks.

The NPM includes a dashboard with comprehensive controls that can help you customize your views of network data and also filter the events that are reported by the system. This is a very flexible system that is suitable for any size of network. The NPM is a standalone package, and it can work as integration with the company’s other product to offer end to end unified IT management solution.

Features

The operating procedures of the Network Performance Monitor are based on the Simple Network Monitoring Protocol (SNMP). This is a network industry standard that requires an agent program installed on every device. Each device that can be connected to a network will already have an SNMP agent installed on it as part of its firmware. SNMP requires a central controller and the Network Performance Monitor provides this function.

The other main features of the SolarWinds Network Performance Monitor are:

Network Availability Monitoring

Reduce network downtime

Network downtime can be caused by a variety of different issues and without the right network performance analysis it can be like searching for a needle in a hay stack. SolarWinds network monitoring software is a network diagnostics tool that continuously monitors the performance, and availability of network devices and aids in network troubleshooting when problems arise. With intelligent network alerting, Network Performance Monitor lets you know when key performance metrics cross your pre-defined thresholds so you are the first to know when issues occur.

Quickly resolve network connectivity issues

Intermittent network availability and connectivity can cause serious network troubleshooting headaches. One minute the problem is there, the next it isn’t. SolarWinds Network Performance Monitor is a network diagnostics tools that tracks and displays current and historical performance metrics in customizable charts and dashboards. Using NPM, you can monitor interfaces to identify if the problem is caused by flapping routes, downtime, or hardware health to help quickly resolve issues and optimize network performance.

Accelerate time-to-resolution

When users can’t access their applications or the network, the finger pointing begins. It’s the network. No, it’s the app. Being able to determine which will greatly accelerate time-to-resolution and help you pinpoint the root cause. SolarWinds Network Performance Monitor uses packet analysis to help you determine if it is the application or the network that is causing poor user experience and accelerate time to resolution.

NetPath Network Path Analysis

Visual analysis and problem solving for hybrid IT

See inside the internet cloud for the first time. NetPath™ is more than a visual traceroute tool that lets you see into all your critical network paths for deeper insights and faster time to resolution. See all devices, applications, networks, and vendors in single-page path analysis for more signal and less noise. Track every hop and view latency historically or in real-time.

Map hybrid paths like never before

Get complete control of your internet. View performance, traffic, and configuration details of devices and applications that are on-premises, in the cloud, or across hybrid environments. With NetPath, you can isolate network slowdowns and determine the actual person you need to contact to solve it. Understand your provider’s network better than they do with visibility into the entire network path.

Enhanced quality of service for end-users

Increasingly complex environments require more robust tools for overall business success. Know about outages before your users, and see the exact location of the issue along your network path. NetPath measures the performance characteristics of each network node and link, making it easy to spot slowdowns. NetPath monitors connectivity from your users to the services they care about, determines what infrastructure is in the path, and where traffic slowdowns are occurring. It provides additional infrastructure data only when it appears to be related to a real problem.

Network Mapping Tool

Use Network Atlas maps to build geographic visualizations

The dynamic network mapping tool, Network Atlas, included in SolarWinds® Network Performance Monitor (NPM) is built to create custom network maps within the Orion Platform. Drag and drop network devices, servers, and wireless access points onto default or custom background images, including dynamic backgrounds like weather maps. Or, automatically use node location properties like GPS coordinates or street addresses to add nodes to realistic geographic maps. Customize visual qualities and access key node details by simply double-clicking objects. Use the Orion Maps widget to add a map to any dashboard, then easily monitor availability and performance across your networks.

Automate network mapping with intelligent Orion Maps

A spatial understanding of networks can help streamline admin monitoring. The Network Atlas map feature in NPM allows you to easily view the automatically updated physical and logical links between network devices like routers, switches, and servers. Simply place objects on default backgrounds or upload custom options like office blueprints, then click connect to automatically add relationships between devices based on your network topology. You can view Layer 2, Layer 3, or both topologies, and manually add any interfaces not automatically monitored. You can also customize the appearance of nodes, labels, and links. Network Atlas maps are designed to automatically monitor link analysis factors like speed, utilization, and down status, and display a child device status indicator if the parent device status changes.

Easily create wireless heatmaps

Automatically create dynamic, color-coded Wi-Fi signal strength maps using Network Performance Monitor. You can also map Cisco wireless controllers and mobile devices to your floor plan. Simply upload the background of your choice, then drag and drop relevant devices to the correct locations. Its algorithm uses real and projected signal analyses to create a more accurate estimate of Wi-Fi availability for end users. Once you name and save a Wi-Fi map, it’ll automatically update every five minutes to reflect current signal strength conditions.

Use NetPath™ for in-depth network traffic mapping

NetPath enables you to perform critical path visualization both inside and outside your firewall. The tool provides visual insight into remote sites and satellite offices across on-premises, cloud, and hybrid environments. It’s designed to ensure smooth service delivery to all sites by helping you understand how traffic flows between devices. By tracing packets hop by hop, NetPath shows network performance, traffic, and configuration details along the service delivery path, so you can see exactly what’s causing the problem when users are reporting slow or intermittent service. With full visibility into network paths, you can find and resolve issues sooner.

Wi-Fi Monitor

Easily discover and monitor wireless access points

Once the network discovery process is completed, automatically discover wireless access points and controllers as wireless devices with the Wi-Fi monitoring software in SolarWinds Network Performance Monitor. SolarWinds network monitoring software helps categorize and recognize all wireless devices available in your network.

Build wireless heat maps

Visualizing wireless coverage makes it easy to identify dead zones, make adjustments, and improve coverage. Network Performance Monitor’s Wi-Fi monitoring tools use the information from wireless APs, connected clients, and their signal strengths per AP in order to create a wireless heat map.

Manage and monitor Wi-Fi infrastructure

Periodically poll thin and autonomous wireless access points, controllers, and connected devices. With SolarWinds Network Performance Monitor’s wireless network monitoring, you can alert, monitor, and report on details, including IP address, device type, SSID, channels used, and the number of clients currently connected. Client details include client name, SSID, IP Address, MAC Address, Received Signal Strength Indication (RSSI), time connected, data rate, and bytes received and bytes transmitted.

Network Monitoring Alerts

Reduce the flood of unnecessary network alerts

With Network Performance Monitor (NPM), you can use or modify built-in default alerts, or set precise custom alerts according to your needs. For large networks, you can leverage intelligent alerting to help avoid an influx of unnecessary notifications. You can also create notifications that are dependency- and topology-aware so you only receive alerts that are truly critical. Using the NPM web-based network notification software, you can easily create alerts based on simple or complex nested trigger conditions, defined parent/child dependencies, and network topology.

Receive network alerts when it matters most

With SolarWinds network alert software, you can easily specify the time of day or the days of the week during which you will receive specific network alerts via email or text, or other means. You can further specify which admin receives a network notification and when—no more sending all alerts to the entire systems team, if it isn’t necessary. And don’t worry about missing critical alerts, you can also decide how the alert engine should escalate unacknowledged alerts using SolarWinds® NPM.

Get the information you need to take action

Network monitoring alerts are only as useful as the information they provide—simply alerting you to a down node isn’t enough. With in-depth network alert software, NPM is designed so that you can configure notifications to provide the detailed information you need, including interface and node name, the date and time when the alert occurred, and the alert severity, helping you know exactly where to start troubleshooting your network. The intelligent alerting engine also allows you to flag certain conditions using dozens of custom actions, including sending an email, text, audio alerts, or executing an external program.

Benefits

Salary/Staff Time Savings
Today’s complex networks require highly trained network professionals to maintain the network,
configure new users, respond to support calls, and plan and support network expansions and
changes. Automated technology that helps maintain or even reduce headcount offers a directly
quantifiable return. In most cases, network management and monitoring solutions free network
professionals to work on more strategic projects, which can help to reduce costs and drive
increased revenue.

Reduced Network Downtime
Network downtime can be directly quantified by simply calculating the cost of the time a
network professional spends troubleshooting and resolving the cause of the downtime. This
cost, however, is simply the tip of the iceberg as far as the total cost of network downtime is
concerned. Lost employee productivity, lost revenue, and lost customer goodwill are all examples
of costs that are harder to calculate but have a much greater impact.

Reduction in Support Calls
Network management and monitoring solutions alert network management and support teams
to potential problems before users start to complain and generate support calls. The cost of
support calls can be easily calculated by looking at the number of calls per week, the time to
resolve a support call, and the cost per hour of support time. By reducing the number of support
calls through proactive monitoring and management of the network, you will be able to directly
quantify the cost savings.

Decreased Time to Resolution
Time to resolution is the amount of time that it takes to resolve an issue once the network
professional is notified. Network monitoring and management systems with real-time diagnostic
data that is viewable through dynamic network maps can greatly reduce the amount of time
required to troubleshoot and pinpoint the source of the issue.

Managing Service Level Agreements
Network operations teams are typically held to or measured against a quantifiable service level
agreement (SLA) that is typically a percent of network uptime. This SLA can be an internal SLA
or an external SLA with your service provider, for example. If network availability is directly
attributable to a company’s revenue, then the cost of downtime can be easily measured based
on the average revenue that would have been generated during the downtime.

New features and improvements in NPM

Release Date: November 5, 2019

NPM 2019.4 offers the following new features and improvements compared to previous releases of NPM.

NPM 2019.4 is an Orion Platform product, and runs on Orion Platform 2019.4.

Device View

  • Visually display your network switches on Cisco 2960 and Juniper devices to check port status, utilization, and position from the Orion Web Console.

Display physical layout of interfaces on graphical stencils (Device View)

Starting with NPM 2019.4, you can visually display interface status and utilization on the device layout for the following rack-mountable devices:

  • Cisco 2960 switches

    Switch stacks and devices with stackwise images, such as -UNIVERSALK9-M, are not supported.

  • EX 2200 Juniper switches
  • EX 3300 Juniper switches

The physical layout is available on Node Details views, as the Device View tab.

  1. In the Orion Web Console, go to the node details view for a node that is monitored using SNMP.

  2. Click the Device View subview. Here, you can:

    • See the status of interfaces on the physical layout
    • Find out more information on individual interfaces
    • Display In- and Out-utilization of individual interfaces

Highlight interfaces with a certain status

  • Select interface statuses to display. Filtered out interfaces are grayed out.

The filters are included in the browser URL. When sharing URL links, you can change the filters by simply adjusting them in the URL.

Display status details for an interface

  • Click an interface to display a panel with details on the right.
  • Click the interface name in the panel to open the Interface Details view.

Display In and Out Utilization of interfaces

Click option buttons above the device stencil to display In or Out Utilization of interfaces.

Click an interface box to display more details about the interface.

When you click an unmonitored interface (black port icon) and have Node Management rights, you can add the interface for monitoring. Click the Start Monitoring Unknown Interface link in the panel.

Real-time charts

Display real-time data with new dashboard widgets:

  • CPU Load and Memory Utilization on Node Details
  • Percent Utilization on Interface Details

Performance improvements

Check out the improved load times for widgets.

Updated and improved localization

Use NPM in German and Japanese UI. NPM improved support for German and Japanese localization.

Improved interface port type mapping

Discover port types with more accuracy.

Other improvements

Configure custom pollers to influence node status calculation.

New features and improvements in Orion Platform 2019.4

Orion Platform 2019.4 offers the following new features and improvements:

  • Orion Maps enhancements, such as Entity Library improvements, bulk administration, custom images, manual topology and customizable frequency of refreshing the maps.
  • Installation improvements: in-product evaluations, support for Azure SQL Database managed instance, and deployment directly from Azure Marketplace.
  • Website performance improvements.
  • Scalability Engines Installer download performance improvements.
  • Legacy Syslog & Traps replacement: Log Viewer replaces legacy Syslog & Traps with instant evaluation of Log Analyzer.
  • Version numbering is now consistent across all Orion Platform products. See the THWACK post What’s in a version number.
  • Orion Platform out-of-the-box reports migrated to web-based Report Manager.
  • Orion SDK enhancements: Automate ‘List Resources’ and import results.

System Requirements

Orion Platform 2019.4 Requirements

Release Date: November 5, 2019

Updated: November 18, 2019

Requirements depend on various variables, such as:

  • Orion Platform deployment in the cloud vs on-premise.
  • Size of the environment to be monitored. This topic provides requirements for small, medium, large and extra large deployments, based on NPM license levels.
  • Orion Platform products to be deployed. This document provides minimum requirements for a single Orion Platform product. If you plan to deploy more SolarWinds products from the Orion Platform family, see Multi-module system guidelines.
  • Review your product Administrator Guides and release notes for the exact product requirements beyond these minimums.
  • SolarWinds recommends reviewing the Orion Platform 2019.4 Release Notes.

Cloud Deployment

Orion Platform products support the following cloud solutions:

Amazon Web Service

To deploy a single Orion Platform product 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 m5d.2xlarge m5.2xlarge
SolarWinds Orion database using Amazon RDS db.r4.large db.r4.xlarge db.r4.2xlarge db.r4.8xlarge
SolarWinds Orion database deployed on an Amazon VM m4.large r4.xlarge r4.2xlarge

Recommended: r5d.4xlarge

 r5d.8xlarge

Recommended: r5d.16xlarge
Additional Polling Engines Only relevant for environments that monitor over 12,000 elements. m5.xlarge

Microsoft Azure

To deploy a single Orion Platform product on Microsoft Azure, consider using the following instance types, based on your deployment size.

Require-
ments		 Small

SL100, SL250, SL500

 Medium

SL2000

 Large

SLX

 XL (up to 400,000 elements)
Orion server A4_v2 DS12_v2 DS4_v2 DS4_v2
SolarWinds Orion database using Azure SQL DB All installed products must run on Orion Platform 2019.2 or later.

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.
DTU Standard Tier S3 or better

vCore General Purpose Tier 2 or better

 DTU Standard Tier S3 or better

vCore General Purpose Tier 2 or better

 DTU Standard Tier S4 or better

vCore General Purpose Tier 2 or better

 DTU Standard Tier S9 (up to 100k elements), S12 (up to 400k elements) or better

vCore General Purpose Tier 16 (up to 100k elements), 30 (up to 400k elements) or better
SolarWinds Orion database using Azure SQL Database managed instance Gen5
4 vCores		 Gen5
8 vCores		 Gen5
16 vCores		 Gen5
40 vCores
SolarWinds Orion database deployed in an Azure VM A4_v2 DS4_v2 Standard E8s_v3 E32-8s_v3

On-premise

To deploy a single Orion Platform product locally, on a server, review the following recommendations.

Require-
ments		 Small

SL100, SL250, SL500

 Medium

SL2000

 Large

SLX

 XL (up to 400,000 elements)
Minimum / Recommended
Orion server

hardware

 

 

 

 

More details

 Quad core processor or better

6 GB/8 GB RAM

10 GB/20 GB HD

 Quad core processor or better

8 GB/16 GB RAM

15 GB/40 GB HD

 Quad core processor or better

16 GB/32 GB RAM

30 GB /40 GB HD

 CPUs with a total combined PassMark score of 7,000 or higher

16 GB/32 GB RAM

40 GB/50 GB HD

Read/Write I/O:

800 IOPS
Orion server software

More details

 Windows Server 2016

Windows Server 2019

Desktop OS’s only for evaluations; NOT recommended for production environments
SolarWinds Orion database server

 

 

 

 

 

 

 

 

 

 

More details

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.
SQL Server Standard or Enterprise 2014 and later

Quad core processor or better

8 GB/16 GB RAM

20 GB/40 GB HD

 SQL Server Standard or Enterprise 2014 and later

Dual quad core processor or better

16 GB/64 GB RAM

50 GB/100 GB HD

 SQL Server Standard or Enterprise 2014 and later

Dual quad core processor or better

64 GB/128 GB RAM

100/400 GB HD

 

 SQL Server Enterprise 2014 and later

CPUs with a total combined PassMark score of 32,000 or higher

256 GB/512 GB RAM

500 GB/1 TB HD

Read/Write I/O:

30,000 IOPs / 190,000 IOPS or better recommended
Additional Polling Engines Only relevant for environments that monitor over 12,000 elements. 4-core processor or better

16 GB RAM
Ports to open

 

More details

 Outbound: 22, 25, 465, 587, 1433, 1434,

Inbound: 80, 162, 443, 514, 17778

Bi-directional: 53, 135, 161, 1801, 5671, 1777
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.

Users running the Configuration wizard must have DBO specified as the default database schema.

More information on hardware recommendations for the Orion Server

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

RAID recommendations only apply to physical environments. If you have your Orion Platform server installed on a virtual machine, these recommendations do not apply to your environment.

Processor speed

Use processors that work at 2.4 GHz or faster.

CPU

Do not enable Physical Address Extension (PAE).

HD

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.

More information on software requirements for the Orion Server

Do not install Orion Platform products on the same server as SolarWinds Access Rights Manager (ARM).

The following table lists software requirements and recommendations for a SolarWinds installation on both physical and virtual computers.

Software Requirements
Operating system
  • Windows Server 2016
  • Windows Server 2019

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

  • You cannot install Orion Platform products on domain controllers. Exception: You can install Orion Agents on domain controllers.
  • You cannot install Orion Platform products or any scalability engines on Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers. Exception: You can install Orion Agents on the same server as a Microsoft SharePoint, Microsoft Exchange or Research in Motion (RIM) Blackberry server.
Operating system languages
  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese
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.

Make sure that the operating system of your Orion Platform supports .NET 4.8. See .NET Framework system requirements (© 2019 Microsoft, available at https://dotnet.microsoft.com, obtained on October 3, 2019).

If your Orion Platform runs on an operating system that does not support .NET 4.8, consider upgrading your environment to be able to use the new features provided by Orion Platform 2019.4.
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:

  • SolarWinds Syslog Service
  • SolarWinds Trap Service
Web console browser Orion Platform products support two most recent versions of the following web browsers available at the release date:

  • Firefox
  • Chrome

Orion Platform products also support the following browsers:

  • Microsoft Internet Explorer 11 with Active scripting

    Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported.

  • Microsoft Edge

More details on requirements for the Orion Database Server

SQL Server versions

Use Express, Standard, or Enterprise versions of the following:

  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2014 SP3
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2016 SP2
  • SQL Server 2017 (including installations on Linux)
  • SQL Server 2019

Which SQL Server version to use?

  • For XL environments, use only Enterprise versions
  • Use Express only for evaluations, very small environments, or EOC.

Recommendations

  • Use the Simple database recovery mode to ensure best performance.
  • Use 64-bit version of SQL Server.
  • You can set the database recovery model to Full Recovery if your Orion Database is hosted on a SQL Cluster 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.

SQL Server Collation

The Orion Platform does not support case-sensitive databases.

The Orion Platform supports CI database on an CS SQL Server.

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

Server roles and permissions

Required server roles:

  • dbcreator
  • public
  • securityadmin

Permissions:

  • You need read permissions to the master database.
  • You don’t need dbcreator permissions if you are installing an Orion Platform product with a pre-existing blank database.

Hard drive space

The following recommendations apply to physical environments only. If you have your SolarWinds Orion database installed on a virtual machine, these recommendations do not apply to your environment.

  • Due to intense I/O requirements, a RAID 1+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.
  • Other RAID configurations can negatively affect your SQL Server’s performance.
  • Mirrored drives for the OS and RAID 1+0 for database data files are recommended.
  • 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.

Database hardware recommendations for large environments

For large environments with a physical SQL Server, SolarWinds recommends the following hard drive configuration.

These recommendations are not relevant for SQL Servers running in a virtual environment.

  • 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

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:

  • 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.
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

You cannot share the SolarWinds Orion database with Microsoft SharePoint, Microsoft Exchange, and Research in Motion (RIM) BlackBerry servers.

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 Encrypt ion
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 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.		 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-
directional		 Send and receive SNMP
information		 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.

Tagged under: ,

What you can read next

SolarWinds Patch Management Software
Web Security Assessment as a Service (WASA) Technical Overview by E-SPIN
E-SPIN Vulnerability Management Portfolio Update – Acunetix Web Vulnerability Scanner version 9 Features Overview & Updates
How to instant session hijack other people Facebook and Twitter user account?

Leave a Reply

Your email address will not be published. Required fields are marked *