Installing the remote device agent on Windows

The topics in this section describe how to install an optional The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. remote device agent.

A local device agent is automatically installed when you install the The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. application server. You cannot install a remote device agent on the application server host computer.

Note

If you are installing multiple remote device agents, and prefer to use a repeatable procedure that is not wizard-based, and is non-iterative, see Running-the-installer-in-silent-mode.

Remote device agent deployment considerations

Installing the remote device agent is optional. When you install the application server, by default it installs a local device agent.

The local device agent is always active on the server. All devices by default are assigned to the local device agent. However, installing a remote device agent offers these operational benefits:

The remote device agent uses a single secure port (default 1099) to communicate with the application server and uses standard protocols to communicate with devices. This enables you to manage devices that are behind firewalls or in a demilitarized zone (DMZ) where you cannot open Telnet/SSH and TFTP/FTP/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 region site/region. The OS image is transferred once 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.

Before you begin

If you have installed any intrusion prevention system, such as McAfee Intrusion Protection, ensure that it is disabled before you start the installation process. You can enable it once the installation is complete.

To install the remote device agent on Microsoft Windows

Log on as an administrator to the host computer where you are installing the remote device agent.
Start the installation by executing the setup.cmd file that you obtained by extracting the installation files.
The installer might take a minute or more to start.
Welcome panel: Click Next.
End User License Agreement panel: Review the The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. Software License. You must accept the terms of this license agreement to continue installation, and click Next.
(Optional): Microsoft .Net version validation warning panel: Install Microsoft .NET Framework 3.5.x if you see the following warning, and then click Next.
See http://www.microsoft.com/en-in/download/ for details.

It is detected that the host on which you are installing TrueSight Network Automation vv.rr.ss.ppp does not have Microsoft .Net framework 3.5.x which is prerequisite for packaged TFTP Server. Please install it before you proceed if you are planning to use packaged TFTP Server. If you proceed without installing Microsoft .Net framework 3.5.x then packaged TFTP Server will not work.
Component Selection panel: Select the Remote Device Agent option, and click Next.
Note
The installer prevents the installation of the remote device agent, if it detects that the application server has been installed on this computer.
Installation directory panel: Specify the directory in which you want to install the product in the Destination Directory field, and click Next. Default: C:\Program Files\BMC Software\BCA-Networks-Agent
Note
- Do not use the pound ($), hash (#) or at (@) sign in the directory path.
- The directory path cannot contain any non-Latin characters (Chinese, Japanese, Korean, or similar characters). These characters cause the installation to fail.
- You must install the software on a local drive. Do not install the software on a network drive.
- BMC recommends using the default for continuity with uninstallation and future upgrades.
TFTP Server Selection panel: Select the Install and configure TFTP Server option if you want to install and configure the TFTP server, and click Next.
Agent services account panel: Enter the user name and password of the account under which the device agent service runs, and click Next. This user account affects which TCP/UDP ports can be used to communicate with the agent.
Note
For security purposes, the TrueSight Network Automation Device Agent service starts with the user account that you provide in this step. By default, the installer restricts only the users that are part of the Administrators group. Therefore, BMC recommends that you provide details of a non-privileged user account.
RMI Port Number panel: Specify the Java Remote Method Invocation (RMI) port to use for communication between the application server and the remote device agent, and click Next.
This port must be available on the system, and any local firewall might have to be configured to allow communication on this port between the application server and the remote device agent. The default port is 1099.
Certificate Information panel: Enter the information required for the SSL certificate as described in the following table, and click Next. The certificate is used for secure communications between the application server and the remote device agent.
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
Memory and System Options panel: Change memory settings or enter additional startup options if required, and click Next.

The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
NoteIn an environment where the The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. agent is installed on a host computer that is behind a Network Address Translation (NAT) firewall, perform the following actions:
- Specify -Djava.rmi.server.hostname=VALUE, an additional startup parameter during installation. Replace VALUE with the host name of the The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. agent.
- Ensure that the host name of the The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. agent that you specify resolves to a public IP address from the The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. server and resolves to a private IP address from the The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. agent itself, by modifying hosts file accordingly.
Installation Preview panel: Review the summary information, and then click Install.
A panel appears indicating that the installation completed successfully.
Finish and log file panel: Review the summary information. To view the installation log file, click View Log. The name of the log file is bcan_install_log.txt. The location of the file is determined by the %TEMP%environment variable in Windows.
As part of a successful remote device agent installation, the following services are installed:
- TrueSight Network Automation Agent Service
- (Optional) BCA-Networks TFTP server
Note
For security purposes, the TrueSight Network Automation Device Agent service starts with the user account that you provide in step 9. By default, the installer restricts only the users that are part of the Administrators group. Therefore, BMC recommends that you provide details of a non-privileged user account.
When the installation completes, you are reminded of the RMI port (Default: 1099) that is used to communicate between the application server and the remote device agent. Ensure that this port is not blocked by any firewall.
When you are finished, click Done.

Where to go next

If you want to install additional components on your Windows server, see Installing-optional-components-on-Windows.
If you have completed the installation, go to Configuring-after-installation.
Note
If you want to set up your The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. system in a stand-alone configuration, see Performing-a-quick-start-configuration.