Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Enterprise Operations Console (EOC) > EOC 1.6.3 Administrator Guide > Requirements

Requirements

Created by Anthony.Rinaldi, last modified by Anthony.Rinaldi on Mar 16, 2017

Views: 215 Votes: 0 Revisions: 4

The following table provides the minimum requirements for an SolarWinds EOC installation.

For evaluation purposes, you may install SolarWinds EOC on Microsoft Windows Vista SP1 or Windows 7 in a test environment. However, SolarWinds does not support SolarWinds EOC installed on these operating systems in a production environment.

Software or Hardware Requirements

Operating System

32-bit or 64-bit Microsoft Windows Server 2003, Windows Server 2008 (including R2), or Windows Server 2012 (including R2).

Web Server

Microsoft IIS 6.0 or later. DNS specifications require that hostnames be composed of alphanumeric characters (A-Z, 0-9), the minus sign (-), and periods (.). Underscore characters (_) are not allowed.

.NET Framework

Version 4.0 or later

CPU Speed

3.0 GHz

Memory

2 GB

Hard Drive Space

750 MB

Network Speed

100 Mbit/s between SolarWinds EOC and SQL Server

SQL Server

SolarWinds Enterprise Operations Console supports the following versions, with latest service packs:

  • SQL Server 2005 Express, Standard, or Enterprise
  • SQL Server 2008 Express, Standard, or Enterprise
  • SQL Server 2008 R2 Express, Standard or Enterprise
  • SQL Server 2012 SP1 Express, Standard or Enterprise

Notes:

  • The selected SQL Server instance must support mixed-mode or SQL authentication with strong passwords. A strong password must meet at least three of the following four criteria:
    • Contains at least one uppercase letter
    • Contains at least one lowercase letter
    • Contains at least one number
    • Contains at least one non-alphanumeric character, for example, #, %, or ^
  • .NET is not required if your database is on a separate server.
  • Use the following database select statement to check your SQL Server version, select pack or release level, and edition:

    Select SERVERPROPERTY ('productversion'), SERVERPROPETY ('productlevel'), SERVERPROPERTY ('edition')

  • For a new database, the user account must be a member of the dbcreator server role. The sysadmin role and the security administrator (SA) user account are always members of dbcreator.
  • For an existing database, the user account needs only to be in the db_owner database role for the existing database.
  • For a new SQL account, the user account must be a member of the securityadmin server role. The sysadmin role and the security administrator user account are always members of securityadmin.
  • Set the recovery model of the database to Simple. SolarWinds does not support other methods.
  • Select the authentication method used by the EOC user to access the EOC database.

    SolarWinds recommends using SQL Server Authentication to ensure the EOC server can always access the EOC database, even when hosted remotely on a separate server.

SQL Server Collation

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

SQL Server Memory

SolarWinds recommends a minimum of 4 GB of RAM.

Ports

SolarWinds Information Service Protocol uses port 17777/tcp.

SolarWinds EOC Web Console typically uses port 80/tcp.

Recovery Model

Simple

Browsers
  • Microsoft Internet Explorer 7 and later
  • Mozilla Firefox 4 and later
  • Google Chrome 20 and later
  • Apple Safari Mobile

Notes:

  • There is a known compatibility issue with EOC and Internet Explorer 11. If you are using Internet Explorer 11 and having issues with how EOC is being displayed in your web browser, enable Enterprise Mode. For more information see this KB article.
  • SolarWinds does not support administrative functions for SolarWinds EOC on Apple Safari Mobile.

Scalability

Note that the requirements stated earlier are the minimal requirements recommended for EOC. Scalability testing has been performed against EOC. The test involved using two servers. One server hosted EOC and the second server was used to run the MSSQL database. Hardware configuration for both servers consisted of a quad core processor with 8GB of RAM. The EOC server was on a virtual machine while SQL resided on a physical server. Testing confirmed that EOC was able to poll data from more than 30 Orion servers if the TOTAL amount of elements (nodes, interfaces, and volumes) was between 600,000 and 1 million elements. The polling interval for scalability testing was set to 10 minutes.

Port requirements

Port Protocol Service or Process Direction Component Encryption Description
80 TCP IIS (w3wp.exe) Bidirectional Website No HTTP default for the Orion Web Console
443 TCP IIS (w3wp.exe) Bidirectional Website SSL/TLC HTTPS default for the Orion Web Console
17777 TCP SolarWinds Information Service Bidirectional SWIS Certificate (SHA) Used for the SolarWinds Information Service (SWIS) protocol

Deployment best practices

Follow these guidelines to help establish the optimum software and hardware configuration for deploying SolarWinds EOC in your monitoring environment.

Best deployment practice

Install SolarWinds EOC on its own server. Provide at least 100Mbit/s of network connectivity between SolarWinds EOC and the SQL Server. For optimal performance, allow at least 1Mbit/s of bandwidth between SolarWinds EOC and each SolarWinds Server you are monitoring.

Redundancy

As a redundancy option, you can install two instances of EOC that monitor the same SolarWinds Orion servers.

Hardware-constrained deployments

If you do not have a dedicated server for SolarWinds EOC, you may decide to install SolarWinds EOC on the server hosting SQL. SolarWinds EOC cannot be installed on a server running other SolarWinds products.

Bandwidth considerations

Large SolarWinds deployments (monitoring 10,000 - 100,000 nodes across 5 to 30 SolarWinds Servers) can require an aggregate of 15 - 60 GB of daily data transfer between SolarWinds EOC and the SolarWinds Servers you are monitoring, and 10 - 40 GB of daily data transfer between SolarWinds EOC and the SQL Server.

FIPS support

FIPS (Federal Information Processing Standard) defines security and interoperability standards for computers used by the U.S. Federal Government.

EOC is FIPS 140-2 compliant. For instructions see Enable FIPS.

Last modified
09:46, 16 Mar 2017

Tags

Classifications

Public