System Requirements for Network Configuration Manager

Hardware Requirements 

Professional Edition

No. of Devices	Processor	Memory	Hard Disk
Upto 50 Devices	2 GHz Dual-core, or more	4 GB RAM	100 GB of Hard Disk space
From 50 to 200 Devices	2.3 GHz Dual-core, or more	4 GB RAM or more	150 GB of Hard Disk space
From 200 to 500 Devices	2.5 GHz Dual-core, or more	8 GB RAM	200 GB of Hard Disk space
From 500 to 2000 Devices	3 GHz Quad-core, or more	8 to 16 GB RAM	300 GB Hard Disk space
From 2000 to 5000 Devices	3 GHz Quad-core, or more	16 to 32 GB RAM	300 - 500 GB Hard Disk space

 

Enterprise Edition

Central

No. of Devices	Processor	Memory	Hard Disk
Upto 50 Devices	2.5 GHz Dual-core, or more	16 GB RAM	100 GB of Hard Disk space
From 50 to 200 Devices	2.5 GHz Dual-core, or more	16 GB RAM or more	150 GB of Hard Disk space
From 200 to 500 Devices	3 GHz Dual-core, or more	16 to 20 GB RAM	200 GB of Hard Disk space
From 500 to 2000 Devices	3.5 GHz Quad-core, or more	16 to 32 GB RAM	300 GB Hard Disk space
From 2000 to 5000 Devices	3.5 GHz Quad-core, or more	24 to 32 GB RAM	300 - 500 GB Hard Disk space
From 5000 to 20000 devices	3.5 GHz Quad-core, or more	32 - 48 GB RAM	300 - 500 GB Hard Disk space

Probe

No. of Devices	Processor	Memory	Hard Disk
Upto 50 Devices	2 GHz Dual-core, or more	4 GB RAM	100 GB of Hard Disk space
From 50 to 200 Devices	2.3 GHz Dual-core, or more	4 GB RAM or more	150 GB of Hard Disk space
From 200 to 500 Devices	2.5 GHz Dual-core, or more	8 GB RAM	200 GB of Hard Disk space
From 500 to 2000 Devices	3 GHz Quad-core, or more	8 to 16 GB RAM	300 GB Hard Disk space
From 2000 to 5000 Devices	3 GHz Quad-core, or more	16 to 32 GB RAM	300 - 500 GB Hard Disk space

Software Requirements

Software	Version 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	Debian 10 to 11.6 / Ubuntu 14 to 22.04 / Cent OS 7 / Fedora 37 / Redhat 7 to 9.1 / Opensuse 15.4	Ubuntu 14 to 22.04 / RedHat 7 to 9.1 / CentOS 7 / CentOS Stream 8 / CentOS Stream 9
Browsers	Chrome/ Firefox/ Edge	Chrome (preferred)/ Firefox/ Edge

Supported Protocols

SNMP v1/v2/v3, Telnet, SSH v1/v2, and TFTP.

 

Port Requirements

The following table summarizes the ports and protocols that Network Configuration Manager uses for communication:

Port	Protocol	Port Type	Usage	Direction	Remarks
22	TCP	Static	SCP Port	Bidirectional	Used for backup / upload / configlets
69	UDP	Static	TFTP Port	Bidirectional	Used for backup / upload / configlets
8060	TCP	Static	Web Client port	Inbound	Can be configured using ChangeWebServerPort.bat.
514 & 519	UDP	Static	Syslog Server port	Inbound	Used for change detection. SYSLOG Server Port can be changed via WebClient
1433	TCP	MSSQL Database Port	Database Port	-	Can be changed in conf/database_params.conf file/ dbconfiguration.bat file.
13306	TCP	PostgreSQL Database Port	Database Port	-	Can be changed in conf/database_params.conf file.

 

Note:

Port	Usage
32000-32999	Wrapper
31000-31999	JVM (To Connect Wrapper)

Database Requirements

The following table lists the basic requirements for your Network Configuration Manager database server.

PostgreSQL

Comes bundled with the product (PostgreSQL version 14.11).

For Remote PostgreSQL, Network Configuration Manager supports PostgreSQL versions 14.11 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 Network Configuration Manager 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"(Windows)/"bcp"(Linux) and "bcp.rll" must be available in the Network Configuration Manager bin directory (applicable only for Network Configuration Manager Enterprise Edition).

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.

For Windows:

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 <\NetworkConfigurationManager\bin> directory.

For Linux:

For BCP utility in Linux, mssql-tools (Microsoft ODBC driver for Linux) should be installed on an Network Configuration Manager installed machine. Please follow the steps in the document provided below to install Microsoft ODBC driver on Linux servers.

https://learn.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server

• Steps to move BCP utility to Network Configuration Manager:
  • After the ODBC driver is installed in Linux servers, the bcp utility files can be found in the below mentioned path. Copy both bcp and bcp.rll files to <NetworkConfigurationManager_home>/bin and start Network Configuration Manager once.
    • For ODBC driver version 18: bcp file in /opt/mssql-tools18/bin/ and bcp.rll file in /opt/mssql-tools18/share/resources/en_US/
    • For other versions of ODBC: bcp file in /opt/mssql-tools/bin/ and bcp.rll file in /opt/mssql-tools/share/resources/en_US/

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.