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.

Hardware requirements

OpManager Standard/ Professional Edition

+

OpManager Standard/ Professional Edition with Add-ons

+

OpManager Enterprise Edition

+

OpManager Enterprise Edition with add-ons

+

MSSQL Configuration

+

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. 

Software Requirements

The following table lists the recommended software requirements for an OpManager 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.4/​ Opensuse 15.4/ Debian 10 to 11.6

​Ubuntu 14 to 22.04/ Red Hat version 7 to 9.4/ CentOS Stream 8/ CentOS 7/ CentOS Stream 9

 Browsers

Google Chrome / Mozilla Firefox / Microsoft Edge / Opera / Safari

Google Chrome / Mozilla Firefox / Microsoft Edge / Opera / Safari

User Privilege: Local administrator privileges required for OpManager installation.

Port Requirements

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

Ports used by the application

+

Ports used for monitoring

+

Ports used by add-ons

+

Databases

+

Ports used by Enterprise Edition

+

Note: To learn more about changing port numbers, click here. 

Database Requirements

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

PostgreSQL

Comes bundled with the product (PostgreSQL version 14.11).

For Remote PostgreSQL, OpManager supports PostgreSQL versions 14.11 to 14.x. 

In case of failover, please use MS SQL.

Microsoft SQL

1. Supported versions:

Note: The MSSQL backend has been tested for OpManager with the following cloud services: AWS RDS, Google Cloud Platform SQL.

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 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.

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 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 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 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.

Ports used by Applications Manager plugin

The following are the ports used by Applications Manager plugin:

  • HTTP - 9090
  • HTTPS - 8443

Thank you for your feedback!

Was this content helpful?

We are sorry. Help us improve this page.

How can we improve this page?
Do you need assistance with this topic?
By clicking "Submit", you agree to processing of personal data according to the Privacy Policy.