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

No. of Devices

 Processor 

 Memory 

 Hard Disk

 1 to 250

 Intel Xeon 2.0 Ghz 4 cores/ 4 threads

 4 GB

 20 GB minimum

 251 to 500

 Intel Xeon 2.5 Ghz 4 cores/ 8 threads

 8 GB

 20 GB minimum

 501 to 1000

 Intel Xeon 2.5 Ghz 4 cores/ 8 threads or higher

 16 GB

 40 GB minimum

 
OpManager Plus (or) OpManager Standard/ Professional Edition with Add-ons
 
OpManager Enterprise Edition
 
OpManager Enterprise Edition with add-ons

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
  • For MSSQL User requirements, click here

Software Requirements

The following table lists the recommended software requirements for an OpManager installation.

Software 

Evaluation 

Production 

 Windows OS

Windows 10/8/7 (or) Windows Server 2019/ 2016/ 2012 R2/ 2012/ 2008

Windows Server 2019/ 2016/ 2012 R2/ 2012/ 2008

 Linux OS

Ubuntu / Suse / Red Hat Enterprise Linux (upto version 8) / Fedora / CentOS / Mandriva (Mandrake Linux)

Red Hat/ 64 bit Linux flavors

 Browsers

Chrome/ Firefox/ Edge/ IE11

Chrome (preferred)/ Firefox/ Edge/ IE11

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

Database Requirements

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

PostgreSQL

  • Comes bundled with the product (PostgreSQL version 10.12).
  • For Remote PostgreSQL, OpManager supports PostgreSQL versions 10.12 to 10.x. 
  • In case of failover, please use MS SQL.

Microsoft SQL

1. Supported versions:

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

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.

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

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.
  • WMI - 445, 5000-6000 and 49152-65535(TCP) - Bidirectional
  • WMI - 135(TCP) - Inbound
  • SNMP-161(UDP) - Bidirectional
  • SNMP Traps- 162(UDP)- Unidirectional (From monitored device to OpManager server)
  • Telnet- 23(TCP)- Bidirectional
  • SSH- 22(TCP)- Bidirectional
  • ICMP- Used to check the availability status and to add a device. - Bidirectional
  • Default syslog port 514(UDP)- Unidirectional (From monitored device to OpManager server)
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.
 

Ports used by Applications Manager plugin

The following are the ports used by Applications Manager plugin:

  • HTTP - 9090
  • HTTPS - 8443

General Information

Antivirus scanners interfering with database files may affect normal functioning of the database. Please make sure that your anti-virus scanners do not affect the functioning of the product/database.