OpManager - System Requirements
The system requirements mentioned below are minimum requirements for the specified number of devices. The sizing requirements may vary based on the load.
OpManager Standard/ Professional Edition
+
|
No. of Devices
|
Processor
|
Memory
|
Hard Disk
|
|
1 to 250
|
Physical Machine: Intel Xeon 2.0 Ghz, 4 cores/ 4 threads
Virtual Machine: 2.0 Ghz, 4 vProcessors
|
4 GB
|
20 GB minimum
|
|
251 to 500
|
Physical Machine: Intel Xeon 2.5 Ghz, 4 cores/ 8 threads
Virtual Machine: 2.5 Ghz, 8 vProcessors
|
8 GB
|
20 GB minimum
|
|
501 to 1000
|
Physical Machine: Intel Xeon 2.5 Ghz, 4 cores/ 8 threads or higher
Virtual Machine: 2.5 Ghz, 8 vProcessors
|
16 GB
|
40 GB minimum
|
OpManager Standard/ Professional Edition with Add-ons
+
|
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
|
OpManager Enterprise Edition
+
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
|
No. of Devices
|
Processor
|
Memory
|
Hard Disk
|
|
1 to 250
|
Physical Machine: Intel Xeon 2.0 Ghz, 4 cores/ 4 threads
Virtual Machine: 2.0 Ghz, 4 vProcessors
|
4 GB
|
20 GB minimum
|
|
251 to 500
|
Physical Machine: Intel Xeon 2.5 Ghz, 4 cores/ 8 threads
Virtual Machine: 2.5 Ghz, 8 vProcessors
|
8 GB
|
20 GB minimum
|
|
501 to 1000
|
Physical Machine: Intel Xeon 2.5 Ghz, 4 cores/ 8 threads or higher
Virtual Machine: 2.5 Ghz, 8 vProcessors
|
16 GB
|
40 GB minimum
|
|
Above 1000 upto 2500
|
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
|
60 GB minimum
|
OpManager Enterprise Edition with add-ons
+
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 or higher
|
40 GB minimum
|
Important Note : Dedicated resources must be available in the case of VMs.
MSSQL Configuration
+
|
CPU
|
RAM
|
Hard Disk
|
Physical Machine: Intel Xeon 2.5 GHz, 16 Cores & 32 Threads
Virtual Machine: 2.5 GHz,
32 vProcessors
CPUs with a total combined PassMark score of 15,000 or higher |
32 GB or higher |
For Central DB, minimum 1 TB required.
A minimum of 100 GB is required for each Probe DB |
Note:
- Configure a dedicated MSSQL server for OpManager databases.
- It is recommended to have only five databases per MSSQL server.
- If there is only one database on the MSSQL server, 8 GB of RAM and 8 cores with 16 threads (or 16 vProcessors if VM) will be sufficient.
Note:
- CPU recommendation for deployments use the ®PassMark score. To learn more, click here.
- We strongly recommend assigning a dedicated machine for OpManager.
- For 1000 devices, 5000 monitors and 5000 interfaces with default monitoring interval and default database retention, OpManager 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.
- For customized Hardware requirements, click here.
- For customized disk space requirements, click here.
- For Scalability Recommendations, click here.
- Click here for recommendations when monitoring up to 2500 devices.
- For MSSQL User requirements, click here.
The following table lists the recommended software requirements for an OpManager 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 installation.
This table details the network ports used by OpManager for various monitoring and communication functions.
Ports used by OpManager
+
| Port(s) |
Protocol |
Connection |
Remarks |
| 8060 |
TCP |
Inbound to Server |
Web Browser Communication (Evaluation):
Used for communication between the web browser and the OpManager 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 Server |
| 8061 |
TCP |
Both(Inbound & Outbound) |
Secure Web Browser Communication (HTTPS):
Used for secure HTTPS communication between the browser and the OpManager 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 Server |
| 9990–9999 |
TCP |
Internal (N/A) |
These ports are used for internal communication within the OpManager server, primarily for tasks like PDF generation.
Source: Internal
Destination: Internal |
| 13306 |
TCP |
Internal (N/A) |
PostgreSQL Database:
Used by OpManager's bundled PostgreSQL database in Essential Edition. Primarily for internal OpManager database communication. No external firewall opening needed.
Source: Internal
Destination: Internal |
| 13307 |
TCP |
Internal (N/A) |
PostgreSQL Database (Central Server):
Used by OpManager'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's bundled PostgreSQL database in Probe Server for internal database communication. No external firewall opening needed.
Source: Internal
Destination: Internal |
| 1433 |
TCP |
Outbound from Server |
MSSQL Database Connection:
Used for OpManager to connect to an external MSSQL database. Required only if OpManager uses an external MSSQL database instead of the bundled PostgreSQL.
Source: OpManager Server
Destination: MSSQL Server |
| 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 Server
Destination: PostgreSQL Server |
Ports used for monitoring
+
| Port(s) |
Protocol |
Connection |
Remarks |
| 135 |
TCP |
Outbound from Server |
DCOM Communication (WMI):
Essential for OpManager to establish the initial DCOM connection with remote Windows servers, which is a prerequisite for WMI monitoring.
Source: OpManager 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 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 Server
Destination: Monitoring Device |
| 161 |
UDP |
Outbound from Server |
SNMP Monitoring:
Used by OpManager to send SNMP requests to monitoring devices. OpManager uses a dynamic listening port to receive SNMP responses from devices, which must have port 161 open to receive the initial requests.
Source: OpManager Server
Destination: Monitoring Device |
| 162 |
UDP |
Inbound to Server |
SNMP Traps:
Used by OpManager to receive SNMP Trap messages from monitoring devices.
Source: Monitoring Device
Destination: OpManager Server |
| 23 |
TCP |
Outbound from Server |
CLI Monitoring (Telnet):
OpManager initiates Telnet sessions to remote servers for command-line interface (CLI) monitoring.
Source: OpManager Server
Destination: Monitoring Device |
| 22 |
TCP |
Outbound from Server |
CLI Monitoring (SSH):
OpManager initiates Secure Shell (SSH) sessions to remote servers for secure command-line interface (CLI) monitoring.
Source: OpManager Server
Destination: Monitoring Device |
| 7275 |
TCP |
Outbound from Server |
Remote Desktop Protocol (RDP):
Used by OpManager to establish RDP connections to Windows devices.
Source: OpManager Server
Destination: Monitoring Device |
| 514 |
UDP |
Inbound to Server |
Syslog Messages:
Receiving general Syslog messages from various monitoring devices.
Source: Monitored Device
Destination: OpManager Server |
| 445 |
TCP |
Outbound from Server |
File and Folder Monitoring:
Used by OpManager to fetch file and folder information from Windows devices.
Source: OpManager Server
Destination: Monitoring Device |
Ports used by Add-ons
+
| Port(s) |
Protocol |
Connection |
Remarks |
| 5985 |
TCP |
Outbound from Server |
OpUtils Module (DHCP):
OpUtils module to connect to DHCP servers for configuring MAC filters and reservations. Only required if the OpUtils module is used.
Source: OpManager Server
Destination: DHCP Server |
| 5986 |
TCP |
Outbound from Server |
OpUtils Module (DHCP - Secure):
OpUtils module to connect to DHCP servers for configuring MAC filters and reservations in a secure way. Only required if the OpUtils module is used.
Source: OpManager Server
Destination: DHCP Server |
| 69 |
UDP |
Inbound to Server |
Network Configuration Module (NCM) - TFTP Server:
NCM module TFTP server for receiving device configuration backups. Only required if the NCM module is used and configured to use TFTP.
Source: Monitoring Device
Destination: OpManager Server |
| 22 |
TCP |
Inbound to Server |
SCP/SFTP Server (NCM & Firewall Analyzer):
Used by the NCM module and Firewall Analyzer module for receiving device configuration backups and are only required if either module is used for backups.
Source: Monitoring Device
Destination: OpManager Server |
| 4118 |
TCP |
Inbound to Server |
SCP/SFTP Server (WatchGuard Firewalls):
Used by the Firewall Analyzer module to receive configuration backups from WatchGuard Firewall. Ensure the device is configured to push configurations to OpManager on this port.
Source: Monitoring Device
Destination: OpManager Server |
| 1514 |
UDP |
Inbound to Server |
Firewall Analyzer Module (Syslog):
Firewall Analyzer module to receive Syslog messages from end devices like firewalls and proxy servers. This is distinct from general Syslog (port 514) and required only when the module is enabled.
Source: Firewalls / Proxy Servers
Destination: OpManager Server |
| 9996 |
UDP |
Inbound to Server |
NetFlow Analyzer Module:
NetFlow Analyzer module to receive network traffic flow data (NetFlow, sFlow, IPFIX, J-Flow, etc.) from devices, and is required only when this module is enabled.
Source: Devices (Routers, Switches, Firewalls, NPS Agents)
Destination: OpManager Server |
Note:
- To learn more about changing port numbers, click here.
- To ensure OpManager 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, its agents, devices, and integrated services.
- Connection: Specifies the direction of communication for each port, such as "Outbound" (from OpManager to external systems), "Inbound" (from external systems to OpManager), or "Internal" (within the OpManager server itself).
- OpManager 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 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, ensure that the OpManager webserver port (HTTPS, 8061 by default) is allowed for outbound requests from each agent-monitored device.
- If the Application Manager plugin is installed in OpManager, refer this document to learn more about its port requirements.
Database Requirements
The following table lists the basic requirements for your OpManager database server.
Comes bundled with the product (PostgreSQL version 14.19).
For Remote PostgreSQL, OpManager supports PostgreSQL versions 14.19 to 14.x.
In case of failover, use MSSQL or Remote PostgreSQL.
1. Supported versions:
Note: The MSSQL backend has been tested for OpManager with the following cloud services: AWS RDS, Google Cloud Platform SQL, Azure SQL and Azure SQL Managed Instance.
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 should be in the same LAN. Currently WAN based SQL installations are not supported.
4.Developer edition of SQL Server is 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 bin directory (applicable only for OpManager Enterprise Edition).
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 <\OpManager\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 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:
- 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_home>/bin and start OpManager 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/
6. User-role requirement:
Server roles - "dbcreator", "public" and "sysadmin".
User Mapping - Map this login to "master" with database role ownership as "db_owner" and "public". Click here to learn more.
Thank you for your feedback!
