OpManager MSP - System Requirements

The system requirements mentioned below are the minimum requirements for the specified number of devices. The sizing requirements may vary based on the load.

Hardware requirements

Central Server

Processor	Memory	Hard Disk
Physical Machine: Intel Xeon 3.5 GHz, 4 cores/ 8 threads or higher Virtual Machine: 3.5 GHz, 8 vProcessors CPUs with a total combined PassMark score of 7,000 or higher	16 GB or higher	100 GB minimum

Probe Server

Processor	Memory	Hard Disk
Physical Machine: Intel Xeon 3.5 GHz, 4 cores/ 8 threads or higher Virtual Machine: 3.5 GHz, 8 vProcessors CPUs with a total combined PassMark score of 7,000 or higher	16 GB	40 GB minimum

Note :

CPU recommendation for deployments use the ®PassMark score. To learn more, click here.
We strongly recommend assigning a dedicated machine for OpManager MSP.
For 1000 devices, 5000 monitors and 5000 interfaces with default monitoring interval and default database retention, OpManager MSP utilizes about 1 GB/day of disk space. The number may vary based on the entities monitored in your environment & other factors like events generated, Syslogs, Traps etc.

Software Requirements

The following table lists the recommended software requirements for both OpManager MSP central and probe server installation.

Software	Version requirements for Evaluation	Version requirements for Production
Windows OS	Windows 10, Windows 11 (or) Windows Server 2012	Windows Server 2022/ 2019/ 2016/ 2012 R2/ 2012
Linux OS	Ubuntu 14 to 22.04/ CentOS 7/ Fedora 37/ Red Hat 7 to 9.1/ Opensuse 15.4/ Debian 10 to 11.6	Ubuntu 14 to 22.04/ Red Hat version 7 to 9.1/ CentOS Stream 8/ CentOS 7/ CentOS Stream 9
Browsers	Chrome/ Firefox/ Edge	Chrome (preferred)/ Firefox/ Edge

User Privilege: Local administrator privileges required for OpManager MSP installation.

Port Requirements

The following table summarizes the ports and protocols that OpManager MSP uses for communication.

Ports used by Central

Port	Protocol	Port Type	Usage	Remarks
Central - 13307	TCP	Static (PostgreSQL)	Database Port	Can be changed in conf/database_params.conf file.
1433	TCP	Static (MS SQL)	Database Port	Can be changed in conf/database_params.conf file/ dbconfiguration.bat file.
8060	TCP	Static	Web Server Port	Can be configured using ChangeWebServerPort.bat.
8061	TCP	Static	Secure Port

Ports used by Probe

Port	Protocol	Port Type	Usage	Remarks
Probe - 13308	TCP	Static (PostgreSQL)	Database Port	Can be changed in conf/database_params.conf file.
1433	TCP	Static (MS SQL)	Database Port	Can be changed in conf/database_params.conf file/ DBConfiguration.bat file.
8060	TCP	Static	Web Server Port	Can be configured using ChangeWebServerPort.bat.
23	TCP	Dynamic	SSH Port
7275	TCP	Static	Remote Desktop Port (RDP)	Can be configured using gateway.conf (Under\conf folder)
161	UDP	Static	SNMP
135	TCP	Static	WMI
445	TCP	Static	WMI
5000 to 6000	TCP	Dynamic	WMI
49152 to 65535	TCP	Dynamic	WMI	Windows 2008R2 and higher
162	UDP	Static	SNMP Trap Receiver Port
514	UDP	Static	SYSLOG Receiver Port	SYSLOG Receiver Port can be changed via WebClient

Dynamic ports change during each server startup based on the ports available in the system.

Note :

Outbound websocket protocol should be enabled in the Probe Server and inbound websocket protocol should be enabled in the Central Server.
Ports to be opened in Firewall for installations with public access: Open only the 8061 Secure Port for the Central Server.

Database Requirements

The following table lists the basic requirements for your OpManager MSP database server.

PostgreSQL

Comes bundled with the product
In case of failover, please use MS SQL.

Microsoft SQL

1. Supported versions:

SQL 2019 (from build 125379) | SQL 2017 | SQL 2016 | SQL 2014

2. Important Notices:

1. For production use 64 bit versions of SQL
2. Recovery mode should be set to SIMPLE.
3. SQL and OpManager MSP should be in the same LAN. Currently WAN based SQL installations are not supported.

3. Collation:

English with collation setting (SQL_Latin1_General_CP1_CI_AS)
Norwegian with collation setting (Danish_Norwegian_CI_AS)
Simplified Chinese with collation setting (Chinese_PRC_CI_AS)
Japanese with collation setting (Japanese_CI_AS)
German with collation setting (German_PhoneBook_CI_AS)

4. Authentication:

Mixed mode (MSSQL and Windows Authentication).

5. BCP:

The "bcp.exe" and "bcp.rll" must be available in the OpManager MSP bin directory.

The BCP utility provided with Microsoft SQL Server is a command line utility that allows you to import and export large amounts of data in and out of SQL server databases quickly. The bcp.exe and bcp.rll will be available in the MSSQL installation directory. If MSSQL is in a remote machine, copy bcp.exe and bcp.rll files and paste them in the <\OpManager MSP\bin> directory.

The SQL server version compliant with the SQL Native Client must be installed in the same Server.

List of Ports to be opened in Firewall

For device discovery

OpManager uses ICMP protocol (which has no TCP/UDP ports) by default during device discovery.
Associate credentials during discovery for proper classification of devices and data collection. Refer below for the default ports used for each protocol.

For data collection and monitoring of devices

Open the below ports in the firewall to ensure uninterrupted monitoring of your devices.

Port	Protocol	Port Type	Usage	Direction	Remarks
135	TCP	Static	WMI	Inbound
161	UDP	Static	SNMP	Bidirectional
162	UDP	Static	SNMP traps	Unidirectional(From monitored device to OpManager probe server)
23	TCP	Static	Telnet	Bidirectional
22	TCP	Static	SSH	Bidirectional
-	ICMP	-	-	Bidirectional	Used to check the availability status and to add a device
514	UDP	Static	Default syslog port	Unidirectional (From monitored device to OpManager probe server)
1025 - 5000	TCP	Dynamic	WMI	Bidirectional	Windows 2000, Windows XP, and Windows Server 2003 Know More
49152 to 65535	TCP	Dynamic	WMI	Bidirectional	Windows Server 2008 and later versions, Windows Vista and later versions Know More

Dynamic ports change during each server startup based on the ports available in the system.

Note: OpManager MSP uses ICMP for its initial discovery of devices. If your device does not support ICMP, discovering it via 'Discovery Profile' is not possible. You will only be able to discover the device through 'Add Device' or 'CSV file' options.

For Monitoring Agent-related communication

To ensure the smooth functioning of Agent-based monitoring in OpManager, OpManager's webserver port (https, 8061 by default) must be allowed to send outbound requests from the respective agent-monitored device.