Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Orion Platform > Application Centric Monitor > Application Centric Monitor Installation Guide > Requirements > ACM requirements

ACM requirements

Created by Su-Lyn Rosenberry, last modified by Su-Lyn Rosenberry on Nov 02, 2017

Views: 49 Votes: 0 Revisions: 10

Software Requirements

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

  • Do not install SolarWinds software on domain controllers.
  • SolarWinds neither recommends nor supports the installation of any Orion product on the same server or using the same database server as a Research in Motion (RIM) Blackberry server.
  • Windows 2008 and SQL Server 2008, all versions, are deprecated. While installing on these are supported for this version, SolarWinds recommends installing on later versions.

 

Software Requirements
Operating system
  • Windows Server 2008 R2 SP1 with IIS in 32-bit mode.
  • Windows Server 2012 and 2012 R2
  • Windows Server 2016

Windows Server 2012 R2 Essentials is not supported.

Operating system languages

  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese

IP address version

IPv4

IPv6 implemented as a dual stack. For more information, see RFC 4213 - Basic Transition Mechanisms for IPv6 Hosts and Routers.

  • CIDR notation is not supported for IPv6 addresses.
  • SolarWinds High Availability does not support IPv6 addresses.

Web server

Microsoft Internet Information Services (IIS), version7.5 or later, in 32-bit mode

  • DNS specifications require that host names be composed of alphanumeric characters (A-Z, 0-9), the minus sign (-), and periods (.). Underscore characters (_) are not allowed. For more information, see RFC 952 - DOD Internet Host Table Specification.
  • IIS is installed by the SolarWinds installer. You can install this software manually to reduce your installation time or network bandwidth.

.NET Framework

.NET 4.6.2

.NET 4.5.2

Be sure that you are running the same version of .NET on your primary server and any additional polling engines or web servers in the environment.

Web console browser

  • Microsoft Internet Explorer version 11 or later with Active scripting
  • Microsoft Edge
  • Firefox 46.0 or later (Toolset Integration is not supported on Firefox)
  • Chrome 51.0 or later
  • Safari for iPhone
Other
  • RabbitMQ (primary messaging service between the primary and additional polling engines)
  • MSMQ (fall back and legacy messaging)

Services

The following services must be running after installation is complete to collect syslog messages and traps:

  • SolarWinds Syslog Service
  • SolarWinds Trap Service
PowerShell

SAM PowerShell Script Monitor works with PowerShell 1.0 and later for local execution.

PowerShell 2.0 or later is required for remote execution.

Account privileges

SolarWinds recommends that administrators have local administrator privileges 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

The following table lists the port requirements for Application Centric Monitor.

Port

Type

Direction Product/
Feature

Description

22 TCP

Inbound (target)

 

Outbound (Orion server)

Agents

The default port to transfer configs using SSH/SCP. It is also used for CDR/CMR downloads through SFTP and CLI operations through SSH.

25

TCP

Outbound

SAM

The SMTP port used for non-encrypted messages.

80

TCP

Inbound All

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

135 TCP

Inbound (target)

 

Agents Open on the remote computer (inbound) to deploy the Orion agent from the SolarWinds server.

161

UDP

TCP

Bidirectional All

The default port for Polling Devices and Statistics Collection using SNMP.

The NTA collector uses this port for polling CBQoS-enabled devices for traffic-shaping policies and results using SNMP.

162

UDP

Incoming

SAM

The Trap Server uses this port to listen and receive incoming messages.

443

TCP

Bidirectional All

The default port for https binding.

It is also used for bi-directional ESX/ESXi server polling.

445

TCP

Inbound (target) Agents Microsoft-DS SMB file sharing. This port must be open on the target computer (inbound) to deploy the Orion agent remotely.

465

TCP

Outbound All

The port used for SSL-enabled email alert actions.

587

TCP

Outbound All

The port used for TLS-enabled email alert actions.

1433

TCP

Outbound All

The port used for communication between the SolarWinds server and the SQL Server. Open the port from your Orion Web Console to the SQL Server.

1434

UDP

Outbound All

The port used for communication with the SQL Server Browser Service to determine how to communicate with certain, non-standard SQL Server installations. For more information, see this Microsoft Technet article.

1801

TCP

Bidirectional All

Used with MSMQ WCF binding (for more information see this KB: http://support.microsoft.com/kb/183293).

4369

TCP

Bidirectional High
Availability

Open on the main Orion server and its standby server. This port is not required when protecting additional polling engines.

5671 TCP Bidirectional High Availability

SSL encrypted RabbitMQ messaging from the additional polling engines to the main polling engine. Open on the primary (incoming) and standby (outgoing) servers.

This port is also used for communication between HA pool members.

17777

TCP

Bidirectional All

Used for Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console and from the Orion Web Console to your poller.

17778

HTTPS

TCP

Outbound

(target)

 

Inbound (Orion server)

All

The port is required for access to the SWIS API and Oroin agent communication. It is also used by the NetPath probe.

17781 TCP Inbound WPM Passive agent only. Port for incoming connection on machine where Agent is installed.
17782 TCP Inbound WPM Active agent only. Port on main WPM server/additional poller to which Agent connects in active mode.
17783 TCP Inbound WPM Port for incoming connection on the machine where the WPM Agent is being deployed.
17790 TCP

Inbound (target)

 

Outbound (Orion server)

Agents

Used by the Orion agent to communicate with the Orion server when the agent is in server-initiated communication mode.

In Passive mode, port 17790 must be opened on the host where the Orion agent is installed and allowed by the firewall

17791

TCP

Outbound (target)

 

Inbound

(Orion server)

Agents

Open for Orion agent communication on any SolarWinds Orion server running Windows Server 2008 R2 SP1.

25672 TCP Bidirectional   Required for RabbitMQ messaging (Erlang distribution)

Hardware requirements

Use the minimum hardware configuration if you are evaluating the product or do not anticipate heavy usage.

SolarWinds strongly suggests using the recommended hardware configuration to avoid potential performance issues caused by a heavy load or custom configurations such as increased data retention or more frequent polling intervals.

Server sizing is impacted by:

  • Number of monitored elements:  An element is a component monitor, a node, interface or volume.
  • Polling frequency: SolarWinds regularly polls devices  to collect data and determine status. If you collect statistics more often than the default 5 minute polling rate, system requirements will increase.
  • Number of simultaneous users: Add 1 GB of RAM for every 25 simultaneous users.
Hardware Requirement

CPU speed

Quad core, 3.0 GHz or better

Do not enable Physical Address Extension (PAE).

Hard drive space

50 GB minimum

150 GB recommended

Some common files may need to be installed on the same drive as your server operating system.

Due to intense I/O requirements, your SQL Server should be hosted on a separate physical server configured as RAID 1+0. RAID 5 is not recommended for the SQL Server hard drive.

Memory

16 GB minimum

32 GB recommended

Orion SQL database requirements

Your Orion Platform product and your SolarWinds Orion database should use separate servers.

Multiple Orion server installations using the same database are not supported.

The following table lists software and hardware requirements for your SolarWinds Orion database server.

Software/Hardware Requirements

SQL Server

SolarWinds supports Express, Standard, or Enterprise versions of the following:

  • SQL Server 2008, 2008 SP1, 2008 SP2, 2008 SP3, or 2008 SP4
  • SQL Server 2012, 2012 SP1, 2012 SP2, or 2012 SP3

  • SQL Server 2014  or 2014 SP1
  • SQL Server 2016
  • SolarWinds strongly recommends using 64-bit version of SQL Server.
  • The FullWithSQL installer package automatically installs SQL Server 2014 Express. This is recommended for evaluations.
  • Due to latency effects, SolarWinds does not recommend installing your SQL Server and your SolarWinds server or additional polling engine in different locations across a WAN. For more information, see this SolarWinds Knowledge Base article.
  • Either mixed-mode or SQL authentication must be supported.
  • If you are managing your Orion database, SolarWinds recommends you install the SQL Server Management Studio component.
  • You can set the database recovery model to Full recovery mode only if you use Always On Availability. We strongly recommend Simple recovery mode to ensure best performance.

CPU speed

Dual quad core processor,
3.0 GHz or better

Hard drive space

100 GB minimum

400 GB recommended

SolarWinds recommends the following configuration:

  • A hardware RAID Controller with a battery backed-up write back cache
  • Disk Subsystem 1 Array : 2x 146 GB 115K disks RAID 1 (mirroring) for the OS
  • Disk Subsystem 2 Array 2: 1x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)
  • Disk Subsystem 3 Array 3: with 6 x 15K 146 GB or 300 GB disks configured in a RAID 1+0 array to allow for maximum write performance 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 to allow for maximum write performance 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 to allow for maximum write performance 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 to allow for maximum write performance for your tempDB LOG file

 

  • 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 are recommended for all components except the OS drive.

 

Per Windows standards, some common files may need to be installed on the same drive as your server operating system.

Memory

16 GB minimum

32 GB recommended

Additional memory improves both performance and reliability.
Memory and Additional Pollers Each additional polling engine requires 16 GB of additional RAM. For example, SAM plus two additional polling engines would require 32GB of RAM. Three additional polling engines would require 48GB of RAM, and so on.

Authentication

Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server.

Other software

If you are managing your Orion SQL 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:

  • 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

The SAM PowerShell Script Monitor works with PowerShell 1.0 and higher for local execution.

PowerShell 2.0 or higher is required for remote execution.

Last modified

Tags

Classifications

Public