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.

Administering remote device agents

The topics in this section describe tasks that can be performed to administer BMC Network Automation remote device agents.

Enabling and disabling file transfer protocols

Each remote device agent has its own TFTP, FTP and SCP parameter settings (for example, access credentials and transfer directories). You can enable/disable file transfer protocols per remote device agent. You can manage different credentials for FTP and SCP services.

Syslog listening

Syslog events can be routed directly to the BMC Network Automation application server or can be routed to the remote device agent. The remote device agent can receive syslog events directly from the managed devices and from syslog relays. The remote device agent applies External Event filters to reduce the number of events transferred to the application server. For more information, see Managing external event filters.

In addition, you can configure the remote device agent to log syslog events to a local file.

Assigning devices to remote device agents

A remote device agent manages a set of assigned devices. A device is assigned to a remote device agent in the device record. You can use the Edit option on the Device list to assign multiple devices to the same remote device agent. You can also use Device Import to assign devices to a remote device agent. The Seed file only needs to contain the device Name and the Remote device agent name, as follows:

Example CSV Seed File (name, agent):

ATL-cisco-1760, emea-01

For more information, see Editing devices and Managing device import tasks.

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

Comments