OpManager MSP - System Requirements
Table of Contents:
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 2.5 GHz, 4 cores/ 8 threads or higher
Virtual Machine: 2.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 2.5 GHz, 4 cores/ 8 threads or higher
Virtual Machine: 2.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 11
|
Windows Server 2025/ 2022/ 2019/ 2016
|
|
Linux OS
|
Ubuntu 16 to 25/ Fedora 41, 42/ Red Hat 7, 8 , 9, 10/ Opensuse 15/ Debian 11, 12, 13
|
Ubuntu 16 to 25/ Red Hat version 7, 8, 9, 10/ CentOS Stream 9, 10
|
|
Browsers
|
Google Chrome/ Mozilla Firefox/ Microsoft Edge
|
Google Chrome/ Mozilla Firefox/ Microsoft Edge
|
User Privilege: Local administrator privileges required for OpManager MSP installation.
This table details the network ports used by OpManager MSP for various monitoring and communication functions.
Ports used for monitoring
+
| Port(s) |
Protocol |
Connection |
Remarks |
| 135 |
TCP |
Outbound from Server |
DCOM Communication (WMI):
Essential for OpManager MSP to establish the initial DCOM connection with remote Windows servers, which is a prerequisite for WMI monitoring.
Source: OpManager MSP Server
Destination: Monitoring Device |
| 1025 – 5000 |
TCP |
Outbound from Server |
WMI Monitoring (Dynamic - Older Windows):
Used for fetching monitoring data once a DCOM connection (initiated on port 135) is established. Microsoft dynamically assigns ports within this range for WMI communication on Windows 2000, Windows XP, and Windows Server 2003. For more details, click here.
Source: OpManager MSP Server
Destination: Monitoring Device |
| 49152 – 65535 |
TCP |
Outbound from Server |
WMI Monitoring (Dynamic - Newer Windows):
Used for fetching monitoring data once a DCOM connection (initiated on port 135) is established. Microsoft dynamically assigns ports within this range for WMI communication on Windows Server 2008 and later, and Windows Vista and later. For more details, click here.
Source: OpManager MSP Server
Destination: Monitoring Device |
| 161 |
UDP |
Outbound from Server |
SNMP Monitoring:
Used by OpManager MSP to send SNMP requests to monitoring devices. OpManager MSP uses a dynamic listening port to receive SNMP responses from devices, which must have port 161 open to receive the initial requests.
Source: OpManager MSP Server
Destination: Monitoring Device |
| 162 |
UDP |
Inbound to Server |
SNMP Traps:
Used by OpManager MSP to receive SNMP Trap messages from monitoring devices.
Source: Monitoring Device
Destination: OpManager MSP Server |
| 23 |
TCP |
Outbound from Server |
CLI Monitoring (Telnet):
OpManager MSP initiates Telnet sessions to remote servers for command-line interface (CLI) monitoring.
Source: OpManager MSP Server
Destination: Monitoring Device |
| 22 |
TCP |
Outbound from Server |
CLI Monitoring (SSH):
OpManager MSP initiates Secure Shell (SSH) sessions to remote servers for secure command-line interface (CLI) monitoring.
Source: OpManager MSP Server
Destination: Monitoring Device |
| 7275 |
TCP |
Outbound from Server |
Remote Desktop Protocol (RDP):
Used by OpManager MSP to establish RDP connections to Windows devices.
Source: OpManager MSP Server
Destination: Monitoring Device |
| 514 |
UDP |
Inbound to Server |
Syslog Messages:
Receiving general Syslog messages from various monitoring devices.
Source: Monitored Device
Destination: OpManager MSP Server |
Ports used by OpManager MSP
+
| Port(s) |
Protocol |
Connection |
Remarks |
| 13307 |
TCP |
Internal (N/A) |
PostgreSQL Database (Central Server):
Used by OpManager MSP's bundled PostgreSQL database in Central Server for internal database communication. No external firewall opening needed.
Source: Internal
Destination: Internal |
| 13308 |
TCP |
Internal (N/A) |
PostgreSQL Database (Probe Server):
Used by OpManager MSP's bundled PostgreSQL database in Probe Server for internal database communication. No external firewall opening needed.
Source: Internal
Destination: Internal |
| 8060 |
TCP |
Inbound to Server |
Web Browser Communication (Evaluation):
Used for communication between the web browser and the OpManager MSP Server during the evaluation period. This port is automatically disabled once a license is applied. You should then switch to 8061 (HTTPS) for secure access.
Source: Web Browser
Destination: OpManager MSP Server |
| 8061 |
TCP |
Both (Inbound & Outbound) |
Secure Web Browser Communication (HTTPS):
Used for secure HTTPS communication between the browser and the OpManager MSP server. In the Enterprise Edition, the outbound connection needs to be open to enable communication between Central and Probe. The port can be changed using the ChangeWebServerPort.bat script.
Source: Web Browser
Destination: OpManager MSP Server |
| 1433 |
TCP |
Outbound from Server |
MSSQL Database Connection:
Used for OpManager MSP to connect to an external MSSQL database. Required only if OpManager MSP uses an external MSSQL database instead of the bundled PostgreSQL.
Source: OpManager MSP Server
Destination: MSSQL Server |
| 9990 – 9999 |
TCP |
Internal (N/A) |
These ports are used for internal communication within the OpManager MSP server, primarily for tasks like PDF generation.
Source: Internal
Destination: Internal |
| 5432 |
TCP |
Outbound from Server |
Remote PostgreSQL Database Connection:
Connection to a remote PostgreSQL database. Required only if using a remote database. If PostgreSQL uses a non-default port, that specific port must be opened.
Source: OpManager MSP Server
Destination: PostgreSQL Server |
Dynamic ports change during each server startup based on the ports available in the system.
Note:
- To learn more about changing port numbers, click here.
- To ensure OpManager MSP functions properly, configure the firewall to allow traffic through all the ports listed in the table, as these ports are required for communication between OpManager MSP, its agents, devices, and integrated services.
- Connection: Specifies the direction of communication for each port, such as "Outbound" (from OpManager MSP to external systems), "Inbound" (from external systems to OpManager MSP), or "Internal" (within the OpManager MSP server itself).
- OpManager MSP uses ICMP (no TCP/UDP ports) for device discovery; refer to the table for the default ports used for each protocol. It is recommended to associate credentials for accurate classification and data collection.
- OpManager MSP uses ICMP for initial device discovery. If ICMP is unsupported, use the 'Add Device' or 'CSV file' options instead.
- Agent: For proper functioning of agent-based monitoring in OpManager MSP, ensure that the OpManager MSP webserver port (HTTPS, 8061 by default) is allowed for outbound requests from each agent-monitored device.
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 2022 (from build 12.8.452) | SQL 2019 | SQL 2017 | SQL 2016
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"(Windows)/"bcp"(Linux) 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.
For Windows:
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 <\OpManagerMSP\bin> directory.
The SQL server version compliant with the SQL Native Client must be installed in the same Server.
For Linux:
For BCP utility in Linux, mssql-tools (Microsoft ODBC driver for Linux) should be installed on an OpManager MSP installed machine. Please follow the steps in the document provided below to install Microsoft ODBC driver on Linux servers.
https://learn.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server
The command to install ODBC driver is different for every Linux flavor. Please choose the correct Linux flavor and install the ODBC driver.
- Steps to move BCP utility to OpManager MSP:
- After the ODBC driver is installed in Linux servers, the bcp utility files can be found in the below mentioned path. Copy both bcp and bcp.rll files to <OpManager MSP_home>/bin and start OpManager MSP once.
- For ODBC driver version 18: bcp file in /opt/mssql-tools18/bin/ and bcp.rll file in /opt/mssql-tools18/share/resources/en_US/
- For other versions of ODBC: bcp file in /opt/mssql-tools/bin/ and bcp.rll file in /opt/mssql-tools/share/resources/en_US/
Dynamic ports change during each server startup based on the ports available in the system.
