OpManager 12 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

No. of Devices 

Processor

Memory

Hard Disk

OpManager <250 

2 GHz

4 GB

20 GB 

OpManager 500

2.5 GHz

8 GB

20 GB 

OpManager 1000

Quadcore 2.5 GHz 

or higher

16 GB

40 GB 

OpManager with add-ons 

(Or)

OpManager Plus 

Dual QuadCore 3.5 GHz 

or higher

32 GB

100 GB 

Enterprise Edition 

Dual Quad Core 3.5 GHz 

or higher

32 GB

100 GB 

Enterprise Edition with add-ons

Dual Quad Core 3.5 GHz 

or higher

32 GB

100 GB 

 

Important Notes:

  1. In the case of OpManager Enterprise, the hardware requirements are the same for both the Central and Probe.

  2. Dedicated resources must be available in the case of VMs

 

 

Software Requirements

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

Software

Evaluation

Production

Windows OS

Windows 10

Windows 8

Windows 7

 

Also works with,

 

Windows Server 2016

Windows Server 2012 R2

Windows Server 2012

Windows Server 2008

 

Windows Server 2016

Windows Server 2012 R2

Windows Server 2012

Windows Server 2008

 

Linux OS

Ubuntu

Suse

Red Hat

Fedora

Mandriva (Mandrake Linux)

Red Hat

64 bit Linux flavors

 

Browsers

Chrome latest

Firefox latest

Edge

IE 11

 

Note: Do not enable Enterprise Mode option in Internet Explorer. This will make Internet Explorer work as version 7. This is not supported.

 

Chrome preferred

User privileges

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

Port

Protocol

Port Type

Usage

Remarks

13306 

TCP

Static (PostGRE SQL)

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.

22

TCP

Static

SSH Port

80/443 

TCP

Static

Web Server Port

Can be configured using ChangeWebServerPort.bat.

 

Ports used for monitoring

Port 

Protocol

Port Type

Usage

Remarks

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.

2000 

TCP

Static

Internal Communication Port

 

56328 

TCP

Dynamic

ShutDown Listener Port

 

162 

UDP

Static

SNMP Trap Receiver Port

 

514 

UDP

Static

SYSLOG Receiver Port

SYSLOG Receiver Port can be changed via web client.

 

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

 

Ports used by add-ons

Port 

Protocol

Port Type

Usage

Remarks

69 

UDP

Static

TFTP Port [NCM]

 -

1514 

UDP

Static

Firewall Log Receiver Port [FWA]

Firewall Receiver Port can be changed via web client. 

9996 

TCP

 

 

NetFlow Listener Port [NFA]

NetFlow Listener Port can be changed via web client.

 

 

Database Requirements

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

Memory & Disk

DB

Essential Edition

Enterprise Edition

PGSQL

Bundled with the product.

For evaluation purposes only. Please use MSSQL for production.

MSSQL

 

 

 

SQL 2016 | SQL 2014 | SQL 2012 | SQL 2008 

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.

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)

Authentication:

Mixed mode (MSSQL & Windows Authentication).

BCP (Only for Enterprise Edition/ Essential Edition with the NFA addon):

The "bcp.exe" and "bcp.rll" must be available in the OpManager 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 into \OpManager\bin directory.

 

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

 

 

Warning: The Manage Engine directory (By Default: C:\ManageEngine\OpManager) and the Database directory should be excluded from the Antivirus program.

OpManager allots a specific number of threads per module. Based on the thread count the job get scheduled in batches (say monitoring or backup or flow processing). Increasing the thread count helps you do more work but at the cost of consuming more hardware resources esp the processor CPU. 

 

Notice

It is advisable to change threads after consulting with tech support. 

 

 

  Thread Count Max recommended
Main 6  
StatusPoll 1  
DataPoll 12  
Discovery 10  
DeepDiscovery 10  
Config 3  
MS 1  
Network Discovery 4  
Provisioning 4  
Datacollection 10  
WMI Datacollection 12  
Realtime Monitoring 6  
VMware Monitoring 10  
Process Monitoring 6  
Hardware Monitoring 4  
Hardware Monitoring Disc 2  
SavePoll 60  
Interface Poll 40  
Bulk Data Saver 40