Submit a ticketCall us
Home > Success Center > Application-Centric Monitor > Application Centric Monitor Installation Guide > Requirements > Application Centric Monitor (ACM) system requirements

Application Centric Monitor (ACM) system requirements

Created by Su-Lyn Rosenberry-ret, last modified by Caroline Juszczak on Aug 23, 2018

Views: 541 Votes: 0 Revisions: 14

Updated July 30, 2018

Important: These recommended system requirements are for ACM as a single product installed on Orion Platform 2018.2. Requirements may increase for medium or large environments, or environments with multi-modules installed.

For additional information about Orion Platform requirements and configurations, refer to:

You should also review your product administration guides and release notes for the exact product requirements beyond these minimums. We also recommend reviewing the ACM release notes. Use the SolarWinds Orion Installer to install all SolarWinds Orion products, including SAM.

  • Your Orion server and your SolarWinds Orion database must use separate servers.
  • Multiple Orion server installations using the same database are not supported.

Software requirements

  • SolarWinds only supports installing the Orion agent on domain controllers. Do not install any other SolarWinds products on domain controllers.
  • SolarWinds does not support the installation of any Orion product on the same 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
 

Operating system

Production Evaluation Environments Only
  • Windows Server 2012 and 2012 R2
  • Windows Server 2016

Deprecation notice: Although you can install Orion Platform 2018.2 products on Windows Server 2012 and 2012 R2, Windows Server 2012 and 2012 R2 are deprecated and will not be supported in future versions of the Orion Platform. SolarWinds strongly recommends that you upgrade your operating system to Windows Server 2016 or later at your earliest convenience.

  • Windows 8.1, 64-bit (not Standard Edition)
  • Windows 10
  • All production operating systems

Installing SolarWinds SAM on Windows Server 2012 R2 Essentials or Windows Server Core is not supported.
Desktop operating systems, such as Windows 8.1, 64-bit (not Standard Edition), 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.

Operating system languages

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

IP address version

IPv4

IPv6 implemented as a dual stack

CIDR notation is not supported for IPv6 addresses.

Web server

Microsoft IIS 8.0 or later

Use default settings for Anonymous Authentication of the SolarWinds NetPerfMon website (Enabled).

IIS is installed by the SolarWinds Orion Installer. You can install this software manually to reduce your installation time or network bandwidth.

Microsoft .NET Framework

.NET 4.6.2

Run the same version of. NET on your primary server and any Additional Polling Engines (APEs) or Additional Web Servers (AWS) in the environment.

Services

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

  • SolarWinds Syslog Service
  • SolarWinds Trap Service

Orion Web Console browser

  • Microsoft Internet Explorer 11 or later with Active scripting
  • Microsoft Edge
  • Mozilla Firefox 56.0 or later
  • Google Chrome 62.0 or later

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

Orion Web Console screen resolution

1024 by 768

Account privileges

SolarWinds recommends that SolarWinds Orion administrators have local administrator privileges on the Orion server to ensure full functionality of local SolarWinds tools. 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 2012
  • SQL Server 2012 SP1
  • SQL Server 2012 SP2
  • SQL Server 2012 SP3
  • SQL Server 2012 SP4
  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2017

Deprecation notice: Although you can use SQL Server 2012 with Orion Platform 2018.2 products, this version is deprecated and will not be supported on future versions of the Orion Platform. SolarWinds strongly recommends that you upgrade to Microsoft SQL Server 2016, 2017, or later at your earliest convenience.

SolarWinds strongly recommends using the 64-bit version of SQL Server.

  • Due to latency effects, SolarWinds does not recommend installing your SQL Server, Orion server, or Additional Polling Engine in different locations across a WAN. For details, see Install SolarWinds software and SolarWinds database (SQL Server) across a WAN.
  • You can set the database recovery model to Full Recovery if the Orion Database is hosted on a SQL Cluster or if you use Always On Availability. However, be sure to back up the database regularly and ensure that the volume where you store the transaction log has free space that is at least equal to or greater than the size of the Orion database. 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.
  • SolarWinds recommends Simple database recovery mode to ensure best performance.
SQL Server collation
  • English with collation setting SQL_Latin1_General_CP1_CI_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

SolarWinds supports a case insensitive (CI) database on an CS SQL Server.

SolarWinds does not support case-sensitive databases.

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

PowerShell 2.0 or higher is required for remote execution.

SAM WMI Requirements

Microsoft Windows by default uses a random port between 1024 and 65535 for WMI communications. You must create firewall exceptions to allow TCP/UDP traffic on ports 1024 - 65535 or the component monitors and templates that use WMI will not work.

The following component monitors use WMI:

  • Performance Counter Monitor
  • Process Monitor – WMI (if script uses WMI access)
  • Windows Event Log Monitor
  • Windows PowerShell Monitor (if script uses WMI access)
  • Windows Script Monitor
  • Windows Service Monitor (if script uses WMI access)

The following templates use WMI:

  • Active Directory
  • Active Directory 2016 Domain Controller Security
  • Active Directory 2016 Services and Counters
  • Blackberry Enterprise Server
  • Citrix XenApp 5.0 Core WMI Counters
  • Citrix XenApp 5.0 ICA Session WMI Counters
  • Citrix XenApp 5.0 Presentation Server WMI Counters
  • Citrix XenApp 5.0 Services
  • Errors in Application Event Log
  • Exchange 2007
  • Exchange 2007—2010 Client Access Role Services
  • Exchange 2007—2010 Client Access Role WMI Counters
  • Exchange 2007—2010 Common WMI Counters
  • Exchange 2007—2010 Edge Transport Role Services
  • Exchange 2007—2010 Hub Transport Role Services
  • Exchange 2007—2010 Hub Transport Role WMI Counters
  • Exchange 2007—2010 Mailbox Role Services
  • Exchange 2007—2010 Mailbox Role WMI Counters
  • Exchange 2007—2010 Unified Messaging Role Services
  • Exchange 2007—2010 WMI Counters
  • Exchange 2013 Client Access Role Services
  • Exchange 2013 Client Access Role WMI Counters
  • Exchange 2016 Client Access Role Services
  • Exchange 2016 Hub Transport Role Counters
  • Exchange 2016 Hub Transport Role Servers and Counters
  • Exchange 2010 Common Performance Counters
  • Exchange Server 2000 and 2003
  • Internet Information Services
  • Orion Server
  • SharePoint Server (MOSS) 2007
  • SharePoint Services (WSS) 3.0
  • SQL Server 2005 Database
  • SQL Server 2008 Database
  • Windows Print Services
  • Windows Server 2003-2008
Last modified

Tags

Classifications

Public