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.

Installing the remote device agent on Linux

The topics in this section describe how to install an optional BMC Network Automation remote device agent on a Linux server.

A remote device agent is installed using the same setup file as the BMC Network Automation application server. You cannot install a remote device agent on the application server 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

Before you install the remote device agent, perform the following tasks:

  • Print out and enter in the worksheet the selections and parameter values you plan to use when you run the installer. (see Remote device agent installation worksheet.)
  • Refer to the worksheet when you run the installation.
  • Verify the following prerequisites:
    • Free space available: The remote device agent installation on Linux requires 2 GB of free disk storage. In addition, the /tmp directory requires at least 450 MB of free space.

      If the /tmp directory does not have sufficient free space, you can run the following commands, before installing, to make the installation use an alternate temp directory. The IATEMPDIR directory must have at least 200 MB of free space available.
      $ IATEMPDIR=/your/free/space/tmp_directory
      $ export IATEMPDIR
    • Permissions:

      The installation and temp directories must be assigned the permissions listed in the following table:

      Directory

      Owner Permissions

      Group Permissions

      Other Permissions

      Installation directory

      rwx

      rwx

      rwx

      Temp or alternate directory

      rwx

      rwx

      rwx

      Parent directories of the temp or alternate directory

      rwx

      rx

      rx


      * r=read, w=write, x=execute

To install the remote device agent on Linux

  1. Log on as root to the host computer where you are installing the remote device agent.
  2. Run the umask 022 command.
  3. Extract the installation files, as explained in step 4 of  Installing the application server on Linux .
  4. Run the ./setup.sh command.
    The installer might take a minute or more to start.
  5. Start panel: Select the language to be used for installation.

    BMC Network Automation supports the English, French, and Chinese languages.

    Note

    Starting from version 8.9.02, BMC Network Automation does not support French.

  6. Click OK.
  7.   Welcome panel: Click Next.
  8. Click Next.
  9. End User License Agreement panel: Review the BMC Network Automation Software License, accept the terms of this license agreement, and click Next to continue the installation.
  10. 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.

  11. Installation directory panel: Specify the directory in which you want to install the product in the Destination Directory field, and click Next. (Default) /opt/bmc/bca-networks-agent

    Note

    • Do not use any spaces, or 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.
  12. Agent services account panel: Enter the user name 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.
    The device agent service must run as root if it has to receive syslog messages on port 514. If you plan to use only TCP/UDP ports over 1024, then the device agent service can run under a less-privileged user account.
  13.  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.
  14. Certificate Information panel: Enter the information required for the SSL certificate, and click Next. The certificate is used for secure communications between the application server and the remote device agent.

    Setting

    Description

    Common Name (CN)

    Enter the host name or IPv4 or IPv6 address of the server.

    Note: This field must match the host name in the URL that is used to access the BMC Network Automation web server.

    Organization Unit (OU)

    Enter the name of your organization unit.

    Organization Name (O)

    Enter your city or other locality.

    State Name (S)

    Enter the name of your state, province, or other political subdivision.

    Country (C)

    Enter the name of your country.

    Create Keystore Password

    Enter a minimum six-character password to secure the certificate keystore.

    Note: Record this password in a secure location.

    Confirm Keystore Password

    Enter the keystore password again.

  15. Memory and System Options panel: Change memory settings or enter additional startup options, if required, and click Next.

    Setting

    Description

    Initial Memory Allocation

    The amount of memory that the software allocates and holds upon startup. Additional memory is allocated, as needed, up to the Maximum Memory Allocation value (see next item).

    Maximum Memory Allocation

    The maximum amount of memory that the software process can use. Use the guidelines in the Memory guidelines table below to estimate of the setting for initial and maximum memory based on number of devices. The actual values depend on how your BMC Network Automation system is used. If required, these values can be adjusted later.

    Cache Successful DNS Lookups for

    The number of seconds to cache successful DNS lookups. A value of 0 caches the lookups forever. This value controls how many seconds it takes for the software to detect an IP Address change in your BMC Network Automation system when performing DNS lookups (for example, for syslog processing). Typically this value need not be changed.

    Additional Startup Options

    Additional startup options for the application. For a specific recommendation, see the note following this table. The FAQ and Knowledge Base articles might recommend additional startup options to solve issues unique to your environment.


    Memory guidelines

    Number of devices

    Recommended initial memory

    Recommended maximum memory

    < 1000 (default )

    128 MB

    256 MB

    1000-5000

    256 MB

    512 MB

    > 5000

    512 MB

    1024 MB

    Note

    In an environment where the BMC Network Automation 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 BMC Network Automation agent.
    • Ensure that the host name of the BMC Network Automation agent that you specify resolves to a public IP address from the BMC Network Automation server and resolves to a private IP address from the BMC Network Automation agent itself, by modifying hosts file accordingly.
  16. Installation Preview panel: Review the summary information, and then click Install.
    A panel appears indicating that the installation completed successfully.
  17. 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 /tmp.

    Note

    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.

  18. When you are finished, click Done.

As part of a successful remote device agent installation, the BMC Network Automation Device Agent Service service is installed:

The service binaries are installed in /etc/init.d and /etc/rc.*.

Where to go next

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

Comments