The system requirements mentioned below are minimum requirements for the specified number of devices. The sizing requirements may vary based on the load.
OpManager Nexus Standard/ Professional Edition
No. of Devices | Processor | Memory | Hard Disk |
|---|
Upto 1000 | 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 |
OpManager Nexus 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
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 |
Note :
- CPU recommendation for deployments use the ®PassMark score. To learn more, click here.
- The above is the primary requirement for OpManager Nexus. 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 Nexus 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 Nexus installation.
Software | Versions requirements for Evaluation | Version requirements for Production |
|---|
Windows OS | Windows 11 | Windows Server 2025/ 2022/ 2019/ 2016 |
Linux OS | Ubuntu 16 to 25 / Fedora 42, 43 / Red Hat 7, 8 , 9, 10 / Opensuse 15 / Debian 11, 12, 13/ Rocky 10/ BOSS 10 | Ubuntu 16 to 25/ Red Hat version 7, 8, 9, 10 / CentOS Stream 9, 10/ Rocky 10/ BOSS 10 |
Browsers | Google Chrome/ Mozilla Firefox/ Microsoft Edge | Google Chrome/ Mozilla Firefox/ Microsoft Edge |
User Privilege: Local administrator privileges required for OpManager Nexus installation.
Port Requirements
This table details the network ports used by OpManager Nexus for various monitoring and communication functions.
Ports used by OpManager Nexus
Port(s) | Protocol | Connection | Remarks |
|---|
| 8060 | TCP | Inbound to Server | Web Browser Communication (Evaluation):
Used for communication between the web browser and the OpManager Nexus 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 Nexus Server |
| 8061 | TCP | Both(Inbound & Outbound) | Secure Web Browser Communication (HTTPS):
Used for secure HTTPS communication between the browser and the OpManager Nexus 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 Nexus Server |
| 9990–9999 | TCP | Internal (N/A) | These ports are used for internal communication within the OpManager Nexus server, primarily for tasks like PDF generation.
Source: Internal
Destination: Internal |
| 13306 | TCP | Internal (N/A) | PostgreSQL Database:
Used by OpManager Nexus's bundled PostgreSQL database in Essential Edition. Primarily for internal OpManager Nexus database communication. No external firewall opening needed.
Source: Internal
Destination: Internal |
| 13307 | TCP | Internal (N/A) | PostgreSQL Database (Central Server):
Used by OpManager Nexus'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 Nexus '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 Nexus to connect to an external MSSQL database. Required only if OpManager Nexus uses an external MSSQL database instead of the bundled PostgreSQL.
Source: OpManager Nexus 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 Nexus Server
Destination: PostgreSQL Server |
Ports used for monitoring
Port(s) | Protocol | Connection | Remarks |
|---|
| 135 | TCP | Outbound from Server | DCOM Communication (WMI):
Essential for OpManager Nexus to establish the initial DCOM connection with remote Windows servers, which is a prerequisite for WMI monitoring.
Source: OpManager Nexus 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 Nexus 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 Nexus Server
Destination: Monitoring Device |
| 161 | UDP | Outbound from Server | SNMP Monitoring:
Used by OpManager Nexus to send SNMP requests to monitoring devices. OpManager Nexus uses a dynamic listening port to receive SNMP responses from devices, which must have port 161 open to receive the initial requests.
Source: OpManager Nexus Server
Destination: Monitoring Device |
| 162 | UDP | Inbound to Server | SNMP Traps:
Used by OpManager Nexus to receive SNMP Trap messages from monitoring devices.
Source: Monitoring Device
Destination: OpManager Nexus Server |
| 23 | TCP | Outbound from Server | CLI Monitoring (Telnet):
OpManager Nexus initiates Telnet sessions to remote servers for command-line interface (CLI) monitoring.
Source: OpManager Nexus Server
Destination: Monitoring Device |
| 22 | TCP | Outbound from Server | CLI Monitoring (SSH):
OpManager Nexus initiates Secure Shell (SSH) sessions to remote servers for secure command-line interface (CLI) monitoring.
Source: OpManager Nexus Server
Destination: Monitoring Device |
| 7275 | TCP | Outbound from Server | Remote Desktop Protocol (RDP):
Used by OpManager Nexus to establish RDP connections to Windows devices.
Source: OpManager Nexus Server
Destination: Monitoring Device |
| 514 | UDP | Inbound to Server | Syslog Messages:
Receiving general Syslog messages from various monitoring devices.
Source: Monitored Device
Destination: OpManager Nexus Server |
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 Nexus 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 Nexus 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 Nexus 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 Nexus 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 Nexus on this port.
Source: Monitoring Device
Destination: OpManager Nexus 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 Nexus 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 Nexus Server |
| 9090 | HTTP | Bi-directional | Application Manager Module(APM):
The port is used to access the APM console by default and support communication between APM components and monitored applications.
Source: Monitoring Application, Monitoring server, Agents
Destination: APM Server |
| 8443 | HTTPS | Bi-directional | Application Manager Module(APM-secure):
The secured port is used to access the APM console and to support communication between APM components and monitored applications. This port serves as the default for communication between OpManager Nexus and Application Manager.
For Application Manager plugin port requirements, refer here.
Source:Monitoring Application, Monitoring server, Agents
Destination: APM Server |
Note:
- To learn more about changing port numbers, click here.
- To ensure OpManager Nexus 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 Nexus , its agents, devices, and integrated services.
- Connection: Specifies the direction of communication for each port, such as "Outbound" (from OpManager Nexus to external systems), "Inbound" (from external systems to OpManager Nexus ), or "Internal" (within the OpManager Nexus server itself).
- OpManager Nexus 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 Nexus 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 Nexus , ensure that the OpManager Nexus webserver port (HTTPS, 8061 by default) is allowed for outbound requests from each agent-monitored device.
- For Application Manager plugin, refer this document to learn more about its port requirements.
Database Requirements
The following table lists the basic requirements for your OpManager Nexus database server.
PostgreSQL
Comes bundled with the product (PostgreSQL version 14.22).
For Remote PostgreSQL, OpManager Nexus supports PostgreSQL versions 14.22 to 14.x.
In case of failover, please use MS SQL.
Microsoft SQL
1. Supported versions:
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 Nexus 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.
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.
We recommend using the latest version for the best experience.
