Application server system requirements

This topic describes the system requirements for the TrueSight Network Automation application server.


Note

If you would like Network Automation to support any particular version of operating system or database, log an IDEA on BMC Communities .

The application server is bundled with a PostgreSQL database, TFTP server (for Microsoft Windows), syslogd server, and the following third-party software:

Product version

Java version

Apache Tomcat web server version

23.2

AdoptOpenJDK 11.0.17

9.0.76

Installing Microsoft .NET 3.5 for the TFTP server

To use the TFTP server bundled with the installer as the file transfer protocol for devices, you must install and enable Microsoft .NET Framework version 3.5.x.

Important

You must enable Microsoft .NET Framework version 3.5x, even if you have a later version of the .NET Framework installed.

To install the .NET Framework specific to your OS, see the Microsoft website.

 OS support

The application server is compatible with the operating systems listed in the following sections.

Supported Windows platforms

Product version /
OS Platform (x64 (64-bit))

23.2

Windows Server 2022

add.png

Windows Server 2019

add.png

Windows Server 2016 (Standard)

add.png

Windows Server 2012 R2 (Standard)

add.png

Windows Server 2012 (Standard)

add.png

Supported Linux platforms

Product version /
OS Platform (x64 (64-bit))

23.2

Oracle Enterprise Linux 9.0

add.png

Oracle Enterprise Linux 8.3, 8.4, 8.5, 8.6

add.png

Oracle Enterprise Linux 7.9 (supported only when it is running on UEK5)

add.png

Red Hat Enterprise Linux 9.0

add.png

Red Hat Enterprise Linux 8.x

add.png

Red Hat Enterprise Linux 7.8, 7.9

add.png

Ubuntu Linux 22.04.1 LTS

add.png

Ubuntu Linux 22.04

add.png

Ubuntu Linux 20.04 LTS

add.png

Ubuntu Linux 18.04

add.png

Ubuntu Linux 16.04

add.png


Note

  • Network Automation does not support installation on Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 on the Resilient File System (ReFS).
  • Network Automation does not support installation on an IPv6 system where the local host name does not get resolved via Domain Name System (DNS). That is, the  nslookup command on the local host name must succeed if the product needs to use an IPv6 stack.

Back to top

Database support

The following databases are supported for use with the application server:

  • Oracle Database 12c1 (external database encryption)
  • Microsoft SQL Server 2022
  • Microsoft SQL Server 2019 (support for encrypted connections)
  • Microsoft SQL Server 2017 AlwaysOn Clustering
  • Microsoft SQL Server 2017 Active-Passive Mode Clustering
  • Microsoft SQL Server 2016 (support for encrypted connections)
  • Microsoft SQL Server 2014 (support for encrypted connections)
  • Microsoft SQL Server 2012 (support for encrypted connections)
  • PostgreSQL 14.6
  • PostgreSQL 14.4
  • PostgreSQL 14.1
  • PostgreSQL 13.2
  • PostgreSQL 12.6

  • PostgreSQL 10.22

    Note

    • The supported version of 12c is 12.1.0.2 with pluggable database (PDB).
    •  When you choose the embedded database option, Network Automation version 23.2 uses the PostgreSQL version 14.6.
Warning

Network Automation does not support database compression. Therefore, you must disable database compression prior to installing or upgrading Network Automation.

 Back to top

Hardware requirements

The application server specifications in the following table are based on the number of managed devices. These specifications are for a live production environment.

Application server hardware specifications

Number of managed devices

Processor speed

Number of processors

Memory 

Up to 5,000

3 GHz

2

8 GB

5001–25,000

3 GHz

8

24 GB

The application server and database can run on the same host computer or different host computers or virtual machines (VMs).


Note

When uploading OS images larger than 300 MB to Network Automation, the system running PostgreSQL must have enough RAM when Network Automation writes large OS image files to the database. BMC recommends that the system running PostrgeSQL have RAM greater than three times your maximum OS image file size.

If you are running the Network Automation application server and PostgreSQL on the same computer, make sure you have sufficient cumulative RAM.

In addition, your Java heap must be configured to process large files. BMC recommends that you set your maximum java heap size (-Xmx <size>) to three times your maximum OS image file size. See Performance-tuning.


Back to top

Disk space requirements

Note

The application server installation procedure requires approximately 1.2 GB of free disk storage. For more information about the installation procedure, see Installing.

The following table lists the disk space requirements of these components. The requirements are separate and independent, whether the components run on the same host or different hosts.

Component

Data

Disk space requirements

Application server

Total requirement (configuration files, log files, and so on)

5 GB

Database server

General data
Configuration and image data

Note

45 KB per configuration * 90 days * 1 configuration per day = 4 MB for configurations
30 MB per image / 30 devices per image = 1 MB for images
25 KB per transcript * 1 job per day * 90 days = 2.25 MB for transcripts
25 KB per transcript * 20 span actions = 0.5 MB for device status
(where 90 days is the default job/configuration purge criteria)

Per-device sizing is greatly affected by the number of changes made per day (more changes result in more configurations and more transcripts), the type of image the device is running (many images can be over 100 MB in size), the use of tunneled mode for snapshots (where the configurations are also embedded in every transcript), and the purge settings for both configurations and jobs.

Back to top

User account privileges

The Network Automation Oracle or Microsoft SQL Server user account must be granted the following privileges:

  • Create/alter/drop tables/indexes/constraints
  • Insert/update/delete rows

Back to top

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*