System Requirements

This page describes the hardware, operating system, and database requirements for running NetXMS server and agents.

Server Requirements

Hardware

Minimum hardware recommendations depend on the number of monitored nodes:

Component Up to 500 nodes Up to 2,000 nodes Up to 10,000 nodes Up to 50,000 nodes

CPU

2 cores

4 cores

8 cores

16+ cores

RAM

4 GB

8 GB

16 GB

32+ GB

Disk

50 GB

100 GB

500 GB SSD

1 TB+ SSD

Network

100 Mbps

1 Gbps

1 Gbps

10 Gbps

The figures assume an all-in-one installation: the database server runs on the same host as the NetXMS server, and the totals cover both. If the database runs on a separate host, the NetXMS server itself needs noticeably less RAM and disk, and the database host must be sized for the collected data volume instead.

Disk space depends heavily on the number of DCIs per node and data retention settings. Environments with high-frequency polling or long retention periods require significantly more storage.

Supported Server Operating Systems

Platform Notes

Debian 11, 12, 13

Recommended for new deployments

Ubuntu 20.04, 22.04, 24.04, 26.04 LTS

Recommended for new deployments

Red Hat Enterprise Linux 8, 9, 10

Includes CentOS Stream, AlmaLinux, Rocky Linux, Oracle Linux

Windows Server 2016+

64-bit only. Open-source builds are limited to 250 managed nodes; any support tier removes this limit.

FreeBSD 13, 14

Community support

Supported Databases

NetXMS server requires an external database for storing configuration, collected data, and event history.

Database Minimum Version Notes

PostgreSQL

12

Recommended for all deployments

MySQL

8.0

MariaDB 10.5+ also supported

Microsoft SQL Server

2017

Windows and Linux editions

Oracle Database

19c

Requires Oracle client libraries

SQLite

3.36

Evaluation only — not for production use

TimescaleDB

2.0

PostgreSQL extension, recommended for large-scale deployments with high DCI counts

SQLite is suitable only for evaluation environments with a small number of nodes. It does not support concurrent access patterns required for production workloads.

Agent Requirements

The NetXMS agent has minimal resource requirements:

  • CPU: Negligible overhead (typically <1% of a single core)

  • RAM: 20-50 MB depending on configured subagents

  • Disk: 10 MB for the agent binary and configuration

Supported Agent Platforms

Platform Notes

Linux (x86_64, ARM64)

All major distributions; also available as a static binary

Windows (x86, x86_64, ARM64)

Windows 7+ and Server 2012+

FreeBSD

12+

NetBSD, OpenBSD

Built from source

AIX

7.1+

Solaris

11 (SPARC, x86)

macOS

12+ (Intel and Apple Silicon)

Network Requirements

The following network ports must be accessible between NetXMS components:

Port Protocol Direction Description

4701

TCP

Client → Monitoring Server

Desktop management client and web management console server connections

4700

TCP

Monitoring Server → Agent

Agent communication (initiated by monitoring server)

4703

TCP

Agent → Monitoring Server

Agent tunnel connections (TLS, initiated by agent)

161

UDP

Monitoring Server → Devices

SNMP polling

162

UDP

Devices → Monitoring Server

SNMP trap reception

514

UDP

Devices → Monitoring Server

Syslog reception (optional)

Depending on your monitoring configuration, additional ports may be required. For example, Modbus/TCP (502), MQTT (1883), and SSH (22) need to be reachable from the agent or monitoring server to the target devices.
In environments using agent tunnels (port 4703), you do not need to open port 4700 from monitoring server to agent. Tunnels allow agents behind firewalls to establish outbound connections to the monitoring server.

Web Interface Requirements

The NetXMS web management console requires:

  • Java Runtime Environment (JRE) 17 or later

  • Apache Tomcat 11 or later, Jetty 12 or later, or any Java servlet container supporting Jakarta Servlet API 6.0 or later

  • Modern web browser (Chrome, Firefox, Edge, Safari)

WebAPI Requirements

The NetXMS WebAPI is served directly by the server process — no separate service or runtime is required. The REST API endpoints are provided by the webapi server module (loaded with Module = webapi in netxmsd.conf). By default the server listens for API requests on TCP port 8000 on the loopback interface; address, port, and TLS settings are controlled by the [WEBAPI] section of netxmsd.conf.