Documentation forServer Configuration Monitor

SCM 1.0 System Requirements

Important: These recommended system requirements are for SolarWinds Server Configuration Monitor (SCM) 1.0 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 SCM 1.0 release notes. Use the SolarWinds Orion Installer to install all SolarWinds Orion products, including SCM.

Your Orion server and your SolarWinds Orion database must use separate servers.

Server requirements

Type

Requirements

Operating System

  • Windows Server 2016

  • Windows Server 2012 and Windows Server 2012 R2

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

For evaluation purposes only:

  • Windows 8.1 including Update 1, 64-bit only (except Standard edition)
  • Windows 10

Installing SolarWinds Orion Platform on Windows Server 2012 R2 Essentials or Windows Server Core is not supported.

Operating System Language
  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese
 

SolarWinds SCM Server Hardware

  SCM 10 - SCM 100 SCM 250 - SCM 500 SCM 1000

CPU Speed

Quad-core processor or better

Memory

6 GB minimum

8 GB recommended

8 GB minimum

16 GB recommended

16 GB minimum

32 GB recommended

Hard Drive Space

10 GB minimum

20 GB recommended

20 GB minimum

40 GB recommended

40 GB minimum

100 GB recommended

Installing Windows Account

Requires administrator permission on the target server.

File System Access Permissions

Ensure the Network Service account has modify access to the system temp directory: %systemroot%\temp.

SolarWinds Orion Syslog Server

If you want real time change detection triggered through devices sending Syslog messages, the executable must have read and write access to the Orion Platform database.

SolarWinds Orion Trap Service

If you want real time change detection triggered through devices sending SNMP traps, the executable must have read and write access to the Orion Platform database.

Microsoft SNMP Trap Service

Must be installed if you want real time change detection triggered through devices sending SNMP traps.

Microsoft IIS

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

SolarWinds does not support installing SolarWinds SCM on the same server or using the same database server as a Research in Motion (RIM) Blackberry server.

Microsoft ASP .NET 2.0 Ajax Extension

Version 1 or later

If this is not found on the target computer, the setup program downloads and installs the component.

Microsoft .NET Framework

Version 4.6.2

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.

Database server requirements

You must create the SolarWinds Orion database with the SolarWinds Configuration Wizard. Creating the database another way is not supported.

Type Requirements
Language

SolarWinds supports using SCM with database servers set up in the following languages:

  • English
  • German
  • Japanese
  • Chinese
SQL Server versions
  • SQL Server 2017
  • SQL Server 2016 and SQL Server 2016 with SP1
  • SQL Server 2014 and SQL Server 2014 with SP1-SP4
  • SQL Server 2012, with or without SP1 and SP2, Standard or Enterprise

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.

SCM local SQL database uses SQL 2017 EE Advanced by default.

You can use the following database select statement to check your SQL Server version, service pack or release level, and edition:

select SERVERPROPERTY ('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
SQL server collations

The following SQL server collations are supported:

  • 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
Authentication and protocols

Your database server must support mixed-mode authentication or SQL authentication and have the following protocols enabled:

  • Shared memory
  • TCP/IP
  • Named Pipes
x86 components

The following x86 components must be installed:

  • SQL Server System Common Language Runtime (CLR) Types
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

If the components are not found on the target computer, the setup program downloads and installs the components.

  SCM 10 -
SCM 100
SCM 250 -
SCM 500
SCM 1000
CPU Quad-core processor or better 2 x quad-core processor or better
Memory

8 GB minimum

16 GB recommended

16 GB minimum

64 GB recommended

64 GB minimum

128 GB recommended

Hard drive space

The amount of space needed by SCM depends on several variables in your environment. See the table below for more details.

20 GB minimum

50 GB recommended

100 GB minimum

250 GB recommended

200 GB minimum

500 GB recommended

SolarWinds recommends the following configuration:

  • A hardware RAID Controller with a battery backed-up write back cache
  • Disk Subsystem 1 Array 1: 2x 146 GB 15K disks RAID 1 (mirroring) for the OS
  • Disc Subsystem 2 Array 2: 2x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)

  • Disk Subsystem 3 Array 3: with 6x 15K 146 GB or 300 GB disks configured in a RAID 1+0 array for 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 for a 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 for a tempdb data file

  • Disk Subsystem 6 Array 6: with 4x 15K 146 GB or 300 GB disks configured in a RAID 0 array for a 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 OS and tempdb files.
  • Other RAID configurations can negatively affect SQL Server 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.

Additional database space requirements

The amount of space required by SCM depends on the number of nodes being monitored, the frequency of changes, the number of configuration items being monitored, and the average size of a configuration item. Use the following examples to help determine your needs.

Number of nodes monitored by SCM Number of configuration items per node Average size of configuration item Frequency of changes Additional database space recommendation
1000 100 10.00 kB Once per week, every item changes 52 GB

Once per day, every item changes

365 GB
50 10.00 kB Once per week, every item changes 26 GB
5.00 kB 13 GB

Port requirements

Port Protocol Service/
Process
Direction Description
22 SSH SolarWinds Job Engine v2 IIS Bidirectional Port for accessing ASA devices through CLI
25 TCP SolarWinds Alerting Service V2 Outboun SMTP email default that Orion Platform products use for notification (if SSL/TLS encryption is set up on SMTP server; default port is 465)
53 UDP SolarWinds Job Engine V2 Bidirectional Resolving DNS queries
80 TCP IIS Inbound HTTP default for the Orion Web Console
161 UDP SolarWinds Job Engine V2 Outbound SNMP statistics collection, the default for polling
162 UDP SolarWinds Trap Service Bidirectional Trap messages listened for and received by the Trap Server
443 TCP IIS Inbound Default port for HTTPS binding
445 TCP File and Printer Sharing (SMB-In) Bidirectional Used to store firmware updates and configuration files remotely
465 TCP SolarWinds Alerting Service V2 Outbound The port used for SSL-enabled email alert actions
514 UDP SolarWinds Syslog Service Inbound Syslog Service listens for incoming messages
587 TCP SolarWinds Alerting Service V2 Outbound The port used for TLS-enabled email alert actions
1434 UDP

SolarWinds Alerting Service V2

SolarWindsAdministration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

SQL Server Browse Service

Outbound Communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. Required only if your SQL Server is configured to use dynamic ports.
1801 TCP MSMQ Bidirectional MSMQ WCF binding (For more information, see this article from Microsoft)
5671 TCP RabbitMQ Bidirectional For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers
17777 TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

Bidirectional 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. The port used for communication between the Orion Web Console and the poller.
17778 HTTPS SolarWinds Agent Inbound to the Orion server Required for access to the SWIS API and agent communication

Ports 4369, 5672, and 25672 are opened by default. These ports can be blocked by the firewall.

Supported Web Console browsers

  • Microsoft Internet Explorer version 11 or later with Active scripting

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

  • Microsoft Edge

Orion Platform products support two most recent versions of the following web browsers available at the release date:

  • Firefox
  • Chrome

Additional information

  • SCM 1.0 supports monitoring on nodes running Windows Server 2008 R2 SP1 and newer.
  • SCM requires read permissions to the monitored path for all file, parsed file, and registry profile elements.

Scalability

  • An Orion instance with SCM installed can process up to 280 changes/second combined. If you expect to have more than 1,000 agents per poller, you will need an Additional Polling Engine.

See also Orion Scalability Guidelines.