Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM 6.5 system requirements

SRM 6.5 system requirements

Created by Nigel, last modified by Nigel on Sep 20, 2017

Views: 99 Votes: 0 Revisions: 4

Updated February 21, 2017

Supports: SRM 6.5

See also the SRM 6.5 Release Notes.

The following table provides server requirements based on the size of your environment:

Environment Small Medium Large

SRM Server

CPU

2

2

2

RAM (GB)

8

8

8

Disk (GB)

100

100

100

Additional Polling Engines needed

0

1

3

Additional Polling Engine

CPU

not needed

2

2

RAM (GB)

not needed

8

8

Disk (GB)

not needed

50

50

Database Server

CPU

not needed

2

2

RAM (GB)

not needed

8

8

Disk (GB)

not needed

100

100

Monitored Environment

Arrays 5 25 50

Disks

2,000

5,000

30,000

LUNs 5,000 20,000 60,000

 

The following table outlines the minimum software requirements for SRM.

Software Requirements

Operating System

  • Windows Server 2012, 2012 R2, 2016

For evaluation, SolarWinds products are supported on Windows 8 (excluding Windows 8 Standard edition), and Windows 8.1 (excluding Windows 8.1 Standard edition), Windows 8.1 Update 1 (Except Standard edition) and Windows 10.

IIS and MSMQ must be installed. SolarWinds recommends that the Orion administrators have local administrative privileges to ensure full functionality of local Orion tools. Accounts limited to use of the Orion Web Console do not require administrative privileges.

Language versions supported: English (UK or US).

Web Server

  • Microsoft IIS, version 6.0 and higher, in 32-bit mode.
    • SolarWinds products are not compatible with installations of Internet Information Service version 6.0 (IIS 6) that make use of web gardens.
    • DNS specifications require that hostnames be composed of alphanumeric characters (A-Z, 0-9), the minus sign (-), and periods (.). Underscore characters (_) are not allowed. For more information, see RFC 952.

.NET Prerequisites

  • .Net 4.5 SP1 is required

SNMP Trap Services

  • Windows operating system management and monitoring tools component

Web Browser

  • Microsoft Internet Explorer version 8 or higher with Active scripting
  • Firefox 32.0 or higher (Toolset Integration is not supported on Firefox)
  • Chrome 40.0 or higher
  • Safari for iPhone

FIPS Support

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

Storage Resource Monitor is FIPS 140-2 compliant. 

The following table lists software and hardware requirements for your Orion Platform database server.

Environment Size
 

Small

Medium

Large

CPUs

2 Cores

4 Cores

8 Cores

Hard Drive Space

2 GB

5 GB 20 GB

Due to intense I/O requirements, a RAID 10 drive is strongly recommended for the SQL Server database, SRM, and its log files. RAID 5 is not recommended for the hard drive hosting your SQL Server. The SRM installer needs at least 1GB of free space on the drive where temporary Windows system or user variables are stored. Per Windows standards, some common files may need to be installed on the same drive as your server operating system.

Memory

2 GB

3 GB

4 GB

SolarWinds supports Express, Standard, and Enterprise editions of the following:

  • SQL 2012, SQL 2012 SP1, SQL 2012 SP2
  • SQL 2014, 2014 SP1, 2014 SP2
  • SQL 2016

The following database versions are incompatible with SRM and will be blocked:

  • SQL 2008 without SP, 2008 SP1, 2008 SP2, 2008 SP3
  • SQL 2008 R2 without SP, 2008 R2 and SP1, 2008 R2 and SP2
  • SQL 2005 SP1, SP2, SP3, SP4
  • SQL 2000
  • MSDE

Due to latency effects, SolarWinds does not recommend installing your SQL Server, SRM, or additional polling engine in different locations across a WAN.

Either mixed-mode or SQL authentication must be supported.

If you are managing your SQL database, SolarWinds recommends installing the SQL Server Management Studio component.

If SRM installs SQL Server System Common Language Runtime, a manual restart of the SQL Server service for SRM is required.

Use the following database query to check your SQL Server version, service pack, release level, and edition:

select SERVERPROPERTY ('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

Additional components

The Configuration Wizard installs the following required x86 components if they are not found on your database server:

  • SQL Server System Common Language Runtime (CLR). SolarWinds products use 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

.NET Framework is not required if your database is on a separate server.

SQL server collations

The following collations are supported:

  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • English with collation setting SQL_Latin1_General_CP1_CS_AS

The following diagram shows SolarWinds SRM, its components, and the ports being used for communications between those components:

File:Success_Center/New_Articles/SRM_CHM_for_MT/020/050/STM_Port_Requirements_3_1041x409.png

The following diagram shows the supported storage arrays and the ports being used for data collection from the storage arrays:

File:Success_Center/New_Articles/SRM_CHM_for_MT/020/050/STM_Port_Requirements_2_2_1038x793.png

Port requirements

The following table shows the ports used by SRM:

Port Type Description

25

TCP

SSL/TLS for email alert actions should be enabled.

80

TCP

Default web port. If you specify any port other than 80, you must include that port in the URL used to access the 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. Open the port to enable communication from your computers to the Orion Web Console.

Used on the NetApp head/cluster node and any available CIFS/NFS.

Used by EMC VNX/Clariion for file side performance.

161

UDP

Used for polling storage arrays through SNMP.

Used on the EqualLogic Group IP.

443

TCP

(HTTPS) Used on the NetApp head/cluster node and any available CIFS/NFS.

Used by EMC VNX/Clariion for file side performance.

1433

TCP

Used for communication between the SRM and the SQL Server.

1434

UDP

Used for communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations.

1801

TCP

MSMQ WCF binding (for more information see this KB:http://support.microsoft.com/kb/183293).

5988

TCP

(HTTP) Used by SMI-S providers.

5989

TCP

(HTTPS) Used by SMI-S providers.

8088

TCP

(HTTP) Backup port used for NetApp DFM management servers for 7-mode arrays.

8443

TCP

(HTTPS) Used by Storage Profiler SWIS.

8488

TCP

(HTTPS) Used for NetApp DFM management servers for 7-mode arrays.

17777

TCP

Orion module traffic. Open the port to enable communication from your poller to the SRM Web Console, and from the SRM Web Console to your poller.

The port used for communication between the Orion Web Console and the poller.

17778

TCP

(HTTPS) Required for access to the SWIS API.

17779

TCP

(HTTP/HTTPS) SolarWinds Toolset integration.

The following condensed table shows the ports used by SRM for collecting data from the storage arrays:

Port Type Storage Array Description
80 HTTP

NetApp ONTAP API,

NetApp DFM clustered mode

Alternate ONTAP API port for NetApp connections.

Alternate connection to NetApp On command for clustered mode management server.

80 HTTP EMC VNX XML API

Alternate connection to the EMC VNX control station for collecting file side performance data.

161 UDP SNMP SNMP connections to the storage array.
443 HTTPS

NetApp ONTAP API,

NetApp DFM clustered mode

Secure ONTAP API port for NetApp connections.

Secure connection to NetApp On command for clustered mode management server.

443 HTTPS EMC VNX XML API

Secure, preferred connection to the EMC VNX control station for collecting file side performance data.

5988 HTTP SMI-S provider Alternate port on SMI-S provider (external or on onboard).
5989 HTTPS SMI-S provider Secure and preferred SMI-S port on SMI-S provider (external or on onboard).
8088 HTTP NetApp DFM 7 mode

Alternate connection to the NetApp On command management servers for 7 mode arrays.

8488 HTTPS NetApp DFM 7 mode

Secure connection to the NetApp On command management servers for 7 mode arrays.

 
Last modified

Tags

Classifications

Public