Remote device agent system requirements

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

• • OS support
  • Hardware requirements

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.

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

Supported Linux platforms

Hardware requirements

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.