Important

   

Starting version 8.9.03, BMC Network Automation is renamed to TrueSight Network Automation. This space contains information about BMC Network Automation 8.9.02 and previous versions. For TrueSight Network Automation 8.9.03 and later releases, see the TrueSight Network Automation documentation.

Remote device agent system requirements

This topic describes the system requirements for the BMC Network Automation remote device agent.

Installing the application server installs a local device agent by default. Installing a remote device agent is optional.

The local device agent initially is active after installation. It is always present in the server and can be disabled but not deleted. All devices by default are assigned to the local device agent.

Note

If you are upgrading the application server from an earlier version, you must also upgrade all remote device agents to the same version as BMC Network Automation.

Installing a remote device agent offers these operational benefits:

  • The remote device agent uses a secure port (default 1099) to communicate with the server and uses standard protocols to communicate with devices. This enables you to manage devices that are behind firewalls or in a DMZ where you cannot open Telnet, SSH, TFTP, FTP, or SCP ports, but can open an SSL port.
  • The remote device agent enables you to manage multiple networks that have duplicate IP address ranges.This improves performance and reduces WAN bandwidth when loading software images to devices in a remote site or region. The OS image is transferred one time to the remote device agent for distribution locally to the devices.
  • Managed service providers can securely manage customer networks through a dedicated remote device agent co-located at the customer premises. The customer remote device agents are managed over a single SSL connection.

The BMC Network Automation application server initiates all communication with the remote device agent.

OS support

The remote device agent can be installed on the following OSs:

Supported Windows platforms

Platform

CPU architecture

Version

Windows Server 2016 x64 (64-bit)Standard
Windows Server 2012 R2x64 (64-bit)Standard

Windows Server 2012

x64 (64-bit)Standard

Windows Server 2008 R2

x64 (64-bit)

SP1

Windows Server 2008

x64 (64-bit)

SP2

Supported Linux platforms

Platform

CPU architecture

Version

SUSE Linux Enterprise Serverx64 (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 Linuxx64 (64-bit)6.x
Red Hat Enterprise Linuxx64 (64-bit)5.5
Ubuntu Linuxx64 (64-bit)16.04
Ubuntu Linuxx64 (64-bit)11.10

Ubuntu Linux

x64 (64-bit)

10.04 - LTS

Note

  • 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).

Hardware requirements

Note

Installation disk space: The remote device agent installation procedure requires approximately 2 GB of free disk storage. For more information about the installation procedure, see Installing.

The remote device agent specifications in the following table are based on the number of devices that one agent manages. These specifications are for a live, production environment.

Remote device agent hardware specifications

Maximum number of managed devices

Processor speed (GHz)

Number of processors

Memory (GB)

Disk space (GB)

1,000

3

1

1

2

5,000

3

1

2

2

10,000

3

2

4

5

25,000

3

2

8

5

Was this page helpful? Yes No Submitting... Thank you

Comments