Scribd
Upload
36 views

OpManager Plus System Requirements

The document outlines the system and port requirements for OpManager Plus, detailing the necessary ports for communication, monitoring, and add-ons, as well as database requirements for PostgreSQL and Microsoft SQL. It specifies the protocols, directions, and configuration options for each port, along with important notices regarding SQL server versions and settings. Additionally, it emphasizes the need for specific firewall configurations to ensure uninterrupted monitoring of devices.

Uploaded by

Raj Khanna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
36 views

OpManager Plus System Requirements

The document outlines the system and port requirements for OpManager Plus, detailing the necessary ports for communication, monitoring, and add-ons, as well as database requirements for PostgreSQL and Microsoft SQL. It specifies the protocols, directions, and configuration options for each port, along with important notices regarding SQL server versions and settings. Additionally, it emphasizes the need for specific firewall configurations to ensure uninterrupted monitoring of devices.

Uploaded by

Raj Khanna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

OpManager Plus System Requirements

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

Ports used by the application

Port Protocol Port Usage Direction


Type
Remarks
22 TCP Static SSH Port Bidirectional
8060 TCP Static Web Server Inbound Can be conf igured using
and Port ChangeWebServerPort.bat.
8061
7275 TCP Static Remote Bidirectional Can be conf igured using
Desktop gateway.conf (Under \conf folder)
Port (RDP)
9990 to TCP Static To export N/A Please ensure that these ports are
9999 certain blocked in the Firewall f or inbound
reports in and outbound connections.
PDF f ormat

Ports used for monitoring:

Port Protocol Port Usage Direction Remarks


Type

23 TCP Static Telnet Port Bidirectional


161 UDP Static SNMP Bidirectional
135 TCP Static WMI Inbound
5000 to TCP Dynamic WMI Bidirectional
6000
49152 TCP Dynamic WMI Bidirectional Windows 2008R2 and higher
to
65535
162 UDP Static SNMP Trap Inbound
Receiver Port
514 UDP Static SYSLOG Inbound SYSLOG Receiver Port can
Receiver Port be changed via WebClient
Ports used by add-ons

Central Server
Port Protocol Port Usage Direction Remarks
Type

69 UDP Static TFTP Port [NCM] Bidirectional


1514 UDP Static Firewall Log Inbound Firewall Receiver Port can be
Receiver [FWA] changed via WebClient
9996 UDP Static NetFlow Listener Inbound NetFlow Listener Port can be
Port [NFA] changed via WebClient

Databases:

Port Protocol Description Remarks


13306 TCP PostgreSQL Can be changed in conf/database_params.conf f ile.
Database Port
1433 TCP MSSQL Database Can be changed in conf/database_params.conf
Port file/ dbconfiguration.bat f ile.

List of Ports to be opened in Firewall


Open the below ports in the firewall to ensure uninterrupted monitoring of your devices .

Port Protocol Port Usage Direction Remarks


Type

135 TCP Static WMI Inbound


161 UDP Static SNMP Bidirectional
162 UDP Static SNMP Unidirectional(From
traps 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 Def ault Unidirectional (From
syslog monitored device to
port OpManager server)
1025 - TCP Dynamic WMI Bidirectional Windows 2000,
5000 Windows XP, and
Windows Server 2003
Know More
49152 TCP Dynamic WMI Bidirectional Windows Server 2008
to and later versions,
65535 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

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.

Note: 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:

o English with collation setting (SQL_Latin1_General_CP1_CI_AS)


o Norwegian with collation setting (Danish_Norwegian_CI_AS)
o Simplified Chinese with collation setting (Chinese_PRC_CI_AS)
o Japanese with collation setting (Japanese_CI_AS)
o 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".

You might also like