SolarWinds Orion agent requirements

This topic applies only to the following Orion Platform products:

ACMDPAIMLANAMNOMNPMSAMSCMSRMVMAN*

Agent software is free. Licensing occurs through your product and is usually based on the number of monitored elements.

  • Windows agents run as a service.
  • Linux/Unix agents run as a service daemon.

Before you deploy agents to a target computer, review the following system requirements.

Type Windows Linux/Unix
Operating System

Only 64-bit operating systems are supported.

  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2008 R2 SP1
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019
  • Windows 7
  • Windows 7 SP1
  • Windows 8
  • Windows 8.1
  • Windows 10

Only Pro, Enterprise, and Ultimate workstation
operating systems editions are supported.

  • Amazon AMI, 64-bit
  • CentOS 6.x, 86-bit
  • CentOS 6.x, 7.x, 64-bit
  • IBM AIX 7.x
  • Oracle Linux 6.x, 7.x, 64-bit
  • Raspbian Jessie 8.0
  • Red Hat Enterprise Linux 5.11, 6.x, 86-bit
  • Red Hat Enterprise Linux 5.11, 6.x, 7.x, 64-bit
  • SUSE Linux Enterprise Server 11.x - 15.x, 64-bit
  • SUSE Linux Enterprise Server 11.x, 86-bit
  • Ubuntu 14.x - 16.x, 86-bit
  • Ubuntu 14.x - 18.x, 64-bit
In a TLS 1.2 only environment, the target agent operating system must support TLS 1.2.
Hard drive space Approximately 100 MB of hard drive space on the target computer.
Other software

The following software packages are installed by the agent installer if necessary:

  • Microsoft Visual C++ 2013 Redistributable Package for 32-bit or 64-bit
  • .NET Framework 4.0 (You must install this manually if you are installing an agent on Windows Server 2008 R2 or earlier or Windows Core)
  • .NET Framework 4.5 (Required for Windows Server 2008 R2 SP1 and later)

For Linux, you may need to install the following manually:

  • Python 2, versions 2.4.3 and later

    Python 3 is not supported

  • The bash shell

For AIX:

  • You don't need to install Python manually. Required packages are distributed and deployed automatically with the agent plug-ins.
  • Bash or korn shell is required.
Security

The VeriSign Root Certificate Authority (CA) must be current. This is required because the agent software is signed using a VeriSign certificate. To install a certificate, see Certificates and the agent in the Orion Platform.

After the agent is installed, it runs as a Local System account and does not require administrative permissions to function.

Latency

Agents can tolerate up to 500 ms of latency between the remote computer and the Orion server.

Account Privileges

If you want to deploy agents from the Orion server, the following requirements must be met.

Windows

  • The account used for remote deployment must have access to the administrative share on the target computer: \\<hostname_or_ip>\admin$\temp.
  • User Account Control (UAC) must either be disabled on the target computer, or the built-in Administrator account must be used.
  • You may need to disable UAC remote restrictions.
  • Other remote or mass deployment methods do not have the same requirements.

Linux/Unix

To deploy a Linux/Unix agent via pull deployment, make sure that the following conditions are met:

  • Orion Web Console must be accessible from the target Linux computer.
  • Pull deployment uses wget, curl, or perl to download the installation files from the chosen polling engine.

Agent port requirements

Target computer

Port Protocol Service/
Process
Direction Communication
method
OS Description
22 TCP

sshd

Agent installer

Inbound

Either Linux/Unix

Used to install the agent on Linux/Unix computers through SSH and SFTP or SCP.

135
TCP

Agent installer

Inbound

Either Windows

(DCE/RPC Locator service) Microsoft EPMAP. This port must be open on the target computer for remote deployment.

WMI is only needed for deploying the agent to a Windows server with the Add Node or Add Agent wizard. If you do not want to open WMI ports required for software deployment, you can use another deployment method for the Agent.

WMI also uses any random TCP port greater than 1024. See WMI portocalypse on THWACK.

445
TCP Agent installer

Inbound

Either Windows

Microsoft-DS SMB file sharing. This port must be open on the target computer (inbound) for remote deployment.

17778
TCP

SolarWinds Agent

Outbound

Agent-initiated

All

Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent.

17790

TCP

SolarWinds Agent

Inbound

Server-initiated All Used to communicate with the Orion server.

Orion server

Port Protocol Service/
Process
Direction Communication
method
OS Description
22 TCP n/a

Outbound

Either Linux/Unix

Used to install the agent on Linux/Unix computers through SSH and SFTP or SCP.

17778
TCP

Orion Module Engine

SolarWinds Agent

Inbound

Agent-initiated

All

Used continuously by the agent to communicate back to the Orion server. Also used to deploy the agent.

17790

TCP

Orion Module Engine

SolarWinds Agent

Outbound

Server-initiated All Used to communicate with the Orion server.

Agent resource consumption

Agent resource consumption is variable and depends on what information is collected and how often the information is collected. This is the same as when the data is polled agentlessly, because in most cases, Agents use the same methods for collecting data as agentless polling.

Resource Consumption
CPU Under normal operating conditions, Agent monitoring consumes less than 1% more resources than what would be consumed by monitoring the same node agentlessly.
Memory 10 - 100 MB, depending on the number and types of jobs.
Bandwidth

Roughly 20% (on average) of the bandwidth consumed by the WMI protocol for transmission of the same information.

For example, agents use approximately 1.3 kB/s versus WMI at 5.3 kB/s.

A single polling engine can support up to 1,000 agents.

Some Linux distributions, such as CentOS, log all cron jobs, including jobs that ensure the agent service is still up and responding. The log file can become large quickly. If your distribution logs all cron jobs, ensure that you use a tool such as logrotate to keep your log files to a manageable size.