EOC 2025.1 system requirements

EOC RC documentation - The following content is a draft for a release candidate. All content subject to change. Some links might not function yet.

RC release date: December 12, 2024

SolarWinds strongly recommends that you install the SolarWinds Platform on a server that is neither public, nor internet-facing. To learn about best practices for configuring your SolarWinds Platform installation securely, see Secure Configuration for the SolarWinds Platform.

When installing EOC on a virtual machine (VM), if you are using the offline installer (ISO), copy the installer to the VM. Mounting the ISO in VMware and then sharing it with the VM will prevent you from installing EOC.

Requirements depend on several variables, such as:

SolarWinds Platform deployment in the cloud or on premises.
Size of the environment to be monitored. This topic provides requirements for deployments based on the number of monitored elements such as nodes, interfaces, or component monitors for which you are licensed. As with all products, more connected instances of EOC in your environment benefit from more network and CPU/IO bandwidth. See Licensing model for SolarWinds Platform products.
SolarWinds Platform products to be deployed. This document provides minimum requirements for a single SolarWinds Platform product. If you plan to deploy more SolarWinds products from the SolarWinds Platform family, see Deployment sizing guidelines for the SolarWinds Platform. But keep in mind that EOC must always be installed on a separate server from other products running on the SolarWinds Platform.

Review the EOC Administrator Guide and Release Notes for additional information.
SolarWinds recommends reviewing the SolarWinds Platform 2025.1 Release Notes and the SolarWinds Hybrid Cloud Observability 2025.1 Release Notes.
As always, EOC must be installed on a separate server from other products running on the SolarWinds Platform.

What requirements are you looking for?

Requirements for supported cloud solutions:
- Amazon Web Service
- Microsoft Azure
On-premises deployment requirements overview:
Web Console browser requirements

Amazon Web Service

To deploy EOC (or any single SolarWinds Platform product) using Amazon Web Service, consider using the following templates.

Requirements
SolarWinds Platform server	m4.large
SolarWinds Platform database using Amazon RDS for SQL Server	db.r5.large
SolarWinds Platform database deployed on an Amazon VM	m4.large
Additional Web Servers	Fewer than 50 concurrent users: m4.xlarge More than 50 concurrent users: m4.2xlarge or larger

Microsoft Azure

To deploy EOC (or any single SolarWinds Platform product) on Microsoft Azure, consider using the following instance types, based on your deployment size.

To create a new database or a new database user in the Configuration Wizard, use an account with appropriate privileges.

Requirements
SolarWinds Platform server	DS12_v2
SolarWinds Platform database using Azure SQL DB	Time zone setting of the SolarWinds Platform server must be in the same time zone as Azure SQL DB time zone (UTC).
SolarWinds Platform database using Azure SQL DB	DTU Standard Tier S3 or better vCore General Purpose Tier 2 or better
SolarWinds Platform database using Azure SQL Database managed instance	Gen5 8 vCores
SolarWinds Platform database deployed in an Azure VM	DS4_v2 Standard
Additional Web Server	Fewer than 50 concurrent users: DS12_v2 More than 50 concurrent users: DS4_v2 or larger

On premises

Server hardware

Enterprise Operations Console supports a maximum of 100 attached SolarWinds sites with up to 2 million elements—such as nodes, volumes, interfaces, applications, alerts, and events—total from all attached SolarWinds sites.

Optionally, you can install a Standard or Enterprise edition database on a separate server. See Database requirements.

Hardware	< 60 attached SolarWinds Sites	> 60 attached SolarWinds Sites (max of 100 sites)
CPU	Quad-core processor or better	Octa-core processor or better
OS type	64 bit	64 bit
Hard drive space	20 GB minimum (40 GB recommended)	20 GB minimum (40 GB recommended)
Memory	16 GB minimum (32 GB recommended)	32 GB minimum (64 GB recommended)

Server software

Software Requirements
Operating system	Windows© Server 2022 Windows Server 2019 Windows Server 2016 Desktop operating systems, such as Windows 10 or 11, 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.
Operating system languages	English (UK or US) German Japanese Simplified Chinese
IP address version	IPv4 Dual stack
Web server	If you are not using Microsoft 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 activated by the Configuration Wizard. You can install this software manually to reduce your installation time.
Microsoft .NET Framework	.NET 4.8 Run the same version of. NET on your primary server and any Additional Web Servers in the environment. Make sure the operating system of your SolarWinds 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 SolarWinds product runs on an operating system that does not support .NET 4.8, consider upgrading your environment to be able to use new features.

Database server

If you choose to install the EOC database on a separate server, the hardware and software requirements for the SolarWinds Platform database apply. During installation, SolarWinds Platform creates the following database:

SolarwindsOrion - Primary SolarWinds Platform database.

The default names of the databases can be modified during installation.

Before upgrading from Orion Platform 2020.2.6 and earlier to SolarWinds Platform 2022.3 or later, make sure the database user you use to connect to your SQL Server has the db create privilege. Without this privilege, the upgrade will not complete.

SQL Server versions

Use Standard or Enterprise editions of the following SQL versions. Support for Microsoft SQL Server Service Packs and Cumulative Updates is assumed unless otherwise noted.

Supported versions

SQL Server 2022 CU1 (including installations on Linux)
SQL Server 2019 (including installations on Linux)
SQL Server 2017 (including installations on Linux)
SQL Server 2016 SP1 or SP2

Which SQL Server edition to use?

For XL environments, use only Enterprise versions.
Express editions are supported only for evaluations.

Recommendations

Use the Simple database recovery mode to ensure best performance.
Use the 64-bit version of SQL Server.
You can set the database recovery model to Full Recovery if your SolarWinds Platform 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 the volume where you store your transaction log has free space that is equal to or greater than the size of your SolarWinds Platform database. Your transaction logs will continue to grow indefinitely until a database backup is performed and the transactions are committed to the database. SolarWinds recommends daily database backups when you use the Full Recovery model.

MS SQL Express Limits (evaluations only)

Starting with SolarWinds Platform 2022.3, Express editions of supported MS SQL Server versions are not supported for the production environment. Express editions are supported only for evaluation purposes.

MS SQL Express can be installed on the same server as the SolarWinds Platform server.

When using MS SQL Express, make sure you are aware of the following limits:

Feature	Limit
Maximum database size	10 GB
Maximum computing capacity used by a single instance - SQL Server Database Engine Maximum computing capacity used by a single instance - Analysis Services or Reporting Services	Limited to lesser of 1 socket or 4 cores
Maximum memory for buffer pool per instance of SQL Server Database Engine	1410 MB
Maximum memory for Columnstore segment cache per instance of SQL Server Database Engine	352 MB
Maximum memory-optimized data size per database in SQL Server Database Engine	352 MB
SolarWinds Platform groups	up to 100 groups
SolarWinds Platform concurrent users	up to 5 users logged in simultaneously
SolarWinds Platform performance	Complex groups, limitations, or alerts can affect performance of your deployment.

SQL Server Collation

The SolarWinds Platform does not support case-sensitive databases.

The SolarWinds Platform supports CI databases on 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 a SolarWinds Platform product with a pre-existing blank database.

Hard drive space

The following recommendations apply to physical environments only. If you have your SolarWinds Platform 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. For more information, see Working with 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: Array 1: 2x 146 GB 15K disks RAID 1 (mirroring) for the OS
Disk Subsystem 2 Array: Array 2: 2x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)
Disk Subsystem 3 Array: Array 3: 6x 146 GB or 300 GB 15K disks configured in a RAID 1+0 array for your SQL MDF and FILEGROUPS
Disk Subsystem 4 Array: Array 4: 4x 146 GB or 300 GB 15K disks configured in a RAID 1+0 array for your SQL LDF Transaction LOG file
Disk Subsystem 5 Array: Array 5: 4x 146 GB or 300 GB 15K disks configured in a RAID 1+0 array for your tempdb data file
Disk Subsystem 6 Array: Array 6: 4x 146 GB or 300 GB 15K 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 that you install the SQL Server Management Studio component on your SolarWinds Platform database server.

The SolarWinds Installer installs the following required x86 components if they are not found on your SolarWinds Platform database server:

SQL Server System Common Language Runtime (CLR) Types. SolarWinds Platform uses 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 Platform database with Microsoft SharePoint, Microsoft Exchange, and Research in Motion (RIM) BlackBerry servers.

Server port requirements

The following ports must be opened on your firewall for EOC to connect remotely. For a full list of SolarWinds Platform required ports, see SolarWinds Port requirements.

Optional, individual components, such as SolarWinds Platform Agents and High Availability, have additional port requirements.

SolarWinds does not recommend the use of HTTP (Port 80). Please use HTTPS (Port 443) to ensure that any web-related connections are secure.

Port Protocol Service or process Direction Description Encryption

TCP

Port	Protocol	Service or process	Direction	Description	Encryption
80	TCP	World Wide Web Publishing Service	Inbound	HTTP default for the SolarWinds Platform Web Console website If you specify any port other than 80, you must include that port in the URL used to access the SolarWinds Platform 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`.	No
443	TCP	IIS	Inbound	Access through VPN port (HTTPS)	SSL/TLS 1.2
17777	TCP	SolarWinds Information Service	Bidirectional	Used for the SolarWinds Information Service (SWIS) protocol and for product installation.	RSA handshake, AES 256 communication using WCF TLS 1.2 with Cortex Certificate (SHA-512)

World Wide Web Publishing Service

Inbound

HTTP default for the SolarWinds Platform Web Console website

If you specify any port other than 80, you must include that port in the URL used to access the SolarWinds Platform 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.

443

TCP

IIS

Inbound

Access through VPN port (HTTPS)

SSL/TLS 1.2

17777

TCP

SolarWinds Information Service

Bidirectional

Used for the SolarWinds Information Service (SWIS) protocol and for product installation.

RSA handshake, AES 256 communication using WCF

TLS 1.2 with Cortex Certificate (SHA-512)

Network and scalability

Scalability

With the system requirements outlined above, EOC 2025.1 was successfully tested with 100 SolarWinds Sites with a total of 2 million elements (nodes, interfaces, volumes, and so on).

Connectivity

Multiple EOC servers can be connected to the same SolarWinds Site.

Latency

SolarWinds recommends that latency between the EOC server and connected SolarWinds Sites be less than 200 ms (both ways). EOC can function at higher latencies, but performance might be affected.

EOC was tested with up to 500 ms of latency and remained functional, but performance (specifically with reports) was affected.

Web Console browser requirements

Performance of the computer where you open the browser significantly influences the speed of the SolarWinds Platform Web Console.

SolarWinds Platform supports the two most recent versions of the following web browsers available at the release date:

Firefox
Chrome

SolarWinds Platform also supports the following browsers:

Microsoft Edge

Browser requirements:

JavaScript enabled
Cookies enabled