Enterprise Operations Console 2020.2.6 System Requirements
Release date: July 15, 2021
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.
The following sections list recommended software requirements for a SolarWinds EOC installation. For information about installing EOC 2020.2.6, see the SolarWinds Orion Installer for EOC.
- SolarWinds does not support installing SolarWinds products 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.
EOC 2020.2.6 server requirements
Server Software
Software | Requirements | |
---|---|---|
Operating system | Production | Evaluation environments only |
|
|
|
Installing SolarWinds EOC on Windows Server Core is not supported. |
||
Operating system languages |
|
|
IP address version |
CIDR notation is not supported for IPv6 addresses. |
|
Web server |
Microsoft Internet Information Services (IIS), version 8.5 or later. IIS is installed by the SolarWinds installer. You can install this software manually to reduce your installation time or network bandwidth. |
|
Microsoft .NET Framework |
.NET 4.8 If the required version is not found on the target computer, the installer downloads and installs it. Ensure that .NET is turned on in Windows Features. Run the same version of. NET on your primary server and any Additional Web Servers in the environment. |
|
Web console browser |
Some pages are not compatible with IE 11. If you are using IE 11, you will see a warning messages on incompatible pages. SolarWinds recommends using a different browser, such as Google Chrome, Mozilla Firefox, or Microsoft Edge, for the best user experience with EOC.
|
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. The following requirements are for an EOC server with MS SQL Express 2017 installed as the EOC database.
Optionally, you can install a Standard or Enterprise edition database on a separate server. See Options for the EOC database.
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) |
Options for the EOC database
Unlike other Orion Platform products, you can run EOC 2020.2.6 in a production environment with a SQL Express database installed on the same server. A SQL Express database is sufficient because EOC stores minimal data. For example, the EOC database stores site history, site registrations, user accounts, custom Enterprise Summary Tile definitions, and reports.
Optionally, you can choose to install a Standard or Enterprise edition of SQL Server on a different server. If you choose that option, see the database requirements.
(Optional) Database requirements
If you choose to install the EOC database on a separate server, the hardware and software requirements for the SolarWinds Orion database apply.
Database Software
Software | Optional requirement |
---|---|
SQL Server |
SolarWinds EOC supports Standard or Enterprise editions of the following SQL Server versions:
|
SQL Server Collation |
Notes:
|
Recovery mode | SolarWinds recommends Simple Database Recovery Mode to ensure best performance. |
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 SolarWinds Orion 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:
|
Database Hardware
Hardware | Optional requirement |
---|---|
CPU | Quad-core processor or better |
OS type | 64 bit |
Hard drive space |
20 GB minimum (40 GB recommended) |
Memory |
8 GB minimum (16 GB recommended) |
Microsoft Azure deployments
Orion Platform 2020.2.6 products, including EOC 2020.2.6, support using the Azure SQL Database to host your Orion SQL database. For more information, see Azure SQL Database requirements.
Server port requirements
The following ports are necessary to be opened on your firewall for EOC to connect remotely. For a full-list of Orion Platform required ports, see the Server 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 |
---|---|---|---|---|---|
80 | TCP | IIS (w3wp.exe) | Outbound | HTTP default for the Orion Web Console website | No |
443 | TCP | IIS (w3wp.exe) | Outbound | HTTPS default for the Orion Web Console website | 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 2020.2.6 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. |