The system requirements mentioned below are minimum requirements for the specified number of devices. The sizing requirements may vary based on the load.
OpManager Plus Standard Edition
|
No. of Devices
|
Processor
|
Memory
|
Hard Disk
|
|
Upto 1000
|
Intel Xeon 3.5 GHz 4 cores/ 8 threads or higher.
CPUs with a total combined PassMark score of 7,000 or higher.
|
32 GB or higher
|
40 GB minimum
|
OpManager Plus Enterprise Edition
Central Server
|
Processor
|
Memory
|
Hard Disk
|
|
Intel Xeon 3.5 GHz 4 cores/ 8 threads or higher
CPUs with a total combined PassMark score of 7,000 or higher
|
32 GB or higher
|
100 GB minimum
|
Probe Server
|
Processor
|
Memory
|
Hard Disk
|
|
Intel Xeon 3.5 GHz 4 cores/ 8 threads or higher
|
32 GB
|
40 GB minimum
|
Note :
- CPU recommendation for deployments use the ®PassMark score. To learn more, click here.
- The above is the primary requirement for OpManager Plus. For additional system requirements for each module, check the corresponding modules below
- Dedicated resources must be available in the case of VMs
- We strongly recommend assigning a dedicated machine for OpManager Plus central and each probes.
Network Configuration Manager
|
Number of devices
|
Additional Hard Disk required
|
|
Upto 1000
|
50 GB minimum
|
|
Rate of Flow/Second
|
Additional Disk space for Aggregate Data (Forever)
|
Additional Disk space for RawData (Optional)
|
|
0 to 1000
|
200 GB
|
75 GB/Day
|
|
Firewall Log Rate
|
Additional Harddisk space required
|
|
Upto 1000 logs/sec
|
90GB / day
|
IP Address & Switch Port Management (OpUtils)
|
Number of IPs & Switch ports
|
Hard Disk
|
|
250 IPs and 250 switch ports
|
Above 10 GB
|
We strongly recommend assigning a dedicated machine for OpManager.
Software Requirements
The following table lists the recommended software requirements for an OpManager Plus installation.
|
Software
|
Versions requirements for Evaluation
|
Version requirements for Production
|
|
Windows OS
|
Windows 10 (or) Windows Server 2012
|
Windows Server 2022/ 2019/ 2016/ 2012 R2/ 2012
|
|
Linux OS
|
Ubuntu 14 to 20.04/ CentOS 7/ Fedora 37/ Red Hat 7 to 9.1/ Opensuse 15.4/ Debian 10 to 11.5
|
Ubuntu 14 to 20.04/ Red Hat version 7 to 9.1/ CentOS Stream 8/ CentOS 7/ CentOS Stream 9
|
|
Browsers
|
Chrome/ Firefox/ Edge
|
Chrome (preferred)/ Firefox/ Edge
|
User Privilege: Local administrator privileges required for OpManager Plus installation.
Port Requirements
The following table summarizes the ports and protocols that OpManager Plus uses for communication.
Ports used by the application
|
Port
|
Protocol
|
Port Type
|
Usage
|
Direction
|
Remarks
|
|
22
|
TCP
|
Static
|
SSH Port
|
Bidirectional
|
|
|
8060 and 8061
|
TCP
|
Static
|
Web Server Port
|
Inbound
|
Can be configured using ChangeWebServerPort.bat.
|
|
7275
|
TCP
|
Static
|
Remote Desktop Port (RDP)
|
Bidirectional
|
Can be configured using gateway.conf (Under \conf folder)
|
|
9990 to 9999
|
TCP
|
Static
|
To export certain reports in PDF format
|
N/A
|
Please ensure that these ports are blocked in the Firewall for inbound and outbound connections.
|
Ports used for monitoring
|
Port
|
Protocol
|
Port Type
|
Usage
|
Direction
|
Remarks
|
|
23
|
TCP
|
Static
|
Telnet Port
|
Bidirectional
|
|
|
161
|
UDP
|
Static
|
SNMP
|
Bidirectional
|
|
|
135
|
TCP
|
Static
|
WMI
|
Inbound
|
|
|
5000 to 6000
|
TCP
|
Dynamic
|
WMI
|
Bidirectional
|
|
|
49152 to 65535
|
TCP
|
Dynamic
|
WMI
|
Bidirectional
|
Windows 2008R2 and higher |
|
162
|
UDP
|
Static
|
SNMP Trap Receiver Port
|
Inbound
|
|
|
514
|
UDP
|
Static
|
SYSLOG Receiver Port
|
Inbound
|
SYSLOG Receiver Port can be changed via WebClient |
Dynamic ports change during each server startup based on the ports available in the system.
Central Server
|
Port
|
Protocol
|
Port Type
|
Usage
|
Direction
|
Remarks
|
|
69
|
UDP
|
Static
|
TFTP Port [NCM]
|
Bidirectional
|
|
|
1514
|
UDP
|
Static
|
Firewall Log Receiver [FWA]
|
Inbound
|
Firewall Receiver Port can be changed via WebClient
|
|
9996
|
UDP
|
Static
|
NetFlow Listener Port [NFA]
|
Inbound
|
NetFlow Listener Port can be changed via WebClient |
|
Port
|
Protocol
|
Description
|
Remarks
|
|
13306
|
TCP
|
PostgreSQL Database Port
|
Can be changed in conf/database_params.conf file. |
|
1433
|
TCP
|
MSSQL Database Port
|
Can be changed in conf/database_params.conf file/ dbconfiguration.bat file.
|
Note: To learn more about changing port numbers, click here.
Database Requirements
The following table lists the basic requirements for your OpManager Plus database server.
PostgreSQL
Comes bundled with the product (PostgreSQL version 14.7).
For Remote PostgreSQL, OpManager Plus supports PostgreSQL versions 14.7 to 14.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
2. Important Notices:
1. For production use 64 bit versions of SQL
2. Recovery mode should be set to SIMPLE.
3. SQL and OpManager Plus 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" 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 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 Plus 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 - 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 Plus 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 Plus server)
Note: OpManager Plus 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:
The SQL server version compliant with the SQL Native Client must be installed in the same Server.
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.
