SCM 1.1 System Requirements
Important: These recommended system requirements are for SolarWinds Server Configuration Monitor (SCM) 1.1 as a single product installed on Orion Platform 2018.4. 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:
- Multi-module system guidelines
- High Availability requirements
- Scalability Engine Guidelines
- Optimization Guide
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.1 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.
Software requirements
|
Type |
Requirements |
|||
|---|---|---|---|---|
|
Operating system |
Desktop operating systems, such as Windows 10, 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 |
|
|||
| SolarWinds SCM Server hardware |
SCM 10 - SCM 100 |
SCM 250 - SCM 500 |
SCM 1000 - SCM 2000* |
|
|
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 |
|
|
IP address version |
IPv4 CIDR notation is not supported for IPv6 addresses. |
|||
| Web server |
If you are not using Windows Authentication, make sure Anonymous Authentication is enabled for the default SolarWinds Orion website, NetPerfMon. Anonymous Authentication is used with the default, forms-based authentication. IIS is installed by the SolarWinds Orion Installer. You can install this software manually to reduce installation time or network bandwidth. |
|||
|
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: |
|||
|
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. |
|||
*For SCM 2000, see the Scalability section for more information.
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:
|
||
| SQL Server versions |
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:
|
||
| Authentication |
Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server. |
||
| x86 components |
The following x86 components must be installed:
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 - SCM 2000* |
|
| 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 details. |
20 GB minimum 50 GB recommended |
100 GB minimum 250 GB recommended |
200 GB minimum 500 GB recommended SolarWinds recommends the following configuration:
|
Some common files may need to be installed on the same drive as your server operating system. You may want to move or expand Windows or SQL temporary directories. |
|||
| *For SCM 2000, see the Scalability section for more information. | |||
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 SolarWinds Administration 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 2020.2.1 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.