Application server system requirements
This topic describes the system requirements for the BMC Network Automation application server.
If you would like BMC Network Automation to support any particular version of operating system or database, log an IDEA on .
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 Runtime Environment (JRE) version||Apache Tomcat web server version|
|8.9.02||1.8.0 update 131||8.0.47|
|8.9.01||1.8.0 update 121||8.0.41|
|8.9.00||1.8.0 update 92||8.0.36|
The application server is compatible with the operating systems listed in the following tables.
Supported Windows platforms
|Windows Server 2016||x64 (64-bit)||Standard|
|Windows Server 2008 R2||x64 (64-bit)||SP1|
Windows Server 2008
Windows Server 2012 R2
|Windows Server 2012||x64 (64-bit)||Standard|
Supported Linux platforms
|SUSE Linux Enterprise Server||x64 (64-bit)||11 SP3, SP2|
|Oracle Enterprise Linux||x64 (64-bit)||6.1|
|Red Hat Enterprise Linux||x64 (64-bit)||7, 7.2|
|Red Hat Enterprise Linux||x64 (64-bit)||6.x|
Red Hat Enterprise Linux
|Ubuntu Linux||x64 (64-bit)||16.04|
|Ubuntu Linux||x64 (64-bit)||11.10|
10.04 - LTS
- BMC Network Automation version 8.9.x does not support 32-bit platform installation files for Windows and Linux.
- BMC Network Automation 8.9.02 and earlier versions do not support installation on Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 on the Resilient File System (ReFS).
- BMC Network Automation 8.9.02 and earlier versions do not support installation on an IPv6 system where the local host name does not get resolved via Domain Name System (DNS). That is, the
nslookupcommand on the local host name must succeed if the product needs to use an IPv6 stack.
The following databases are supported for use with the application server:
- Microsoft SQL Server 2008 (support for encrypted connections with SQL Server 2008 Service Pack 3 and later)
- PostgreSQL 9.6.42
1.The supported version of 12c is 18.104.22.168 with pluggable database (PDB).
2.When you choose the embedded database option, BMC Network Automation uses the following PostgreSQL versions:
BMC Network Automation version PostgreSQL version 8.9.02 9.6.4 8.9.01 9.5.5 8.9.00 9.5.3
BMC Network Automation does not support database compression. Therefore, you must disable database compression prior to installing or upgrading BMC Network Automation.
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
Maximum number of managed devices
Processor speed (GHz)
Number of processors
The application server and database can run on the same host computer or different host computers or virtual machines (VMs).
When uploading OS images larger than 300 MB to BMC Network Automation, the system running PostgreSQL must have enough RAM when BMC 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 BMC 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 (
<size>) to three times your maximum OS image file size. See Performance tuning.
Disk space requirements
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.
Disk space requirements
Total requirement (configuration files, log files, and so on)
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.
User account privileges
The BMC 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