Deploy Secondary Hubs and Robots on Linux

This article describes the process for deploying hubs and robots using the nimldr utility.
This article describes the process for deploying hubs and robots using the nimldr utility.
Understand The nimldr Utility
utility installs secondary hubs and robots on Linux . You can run nimldr in express mode to perform a silent installation.
Cloud deployment is not supported on AIX.
Flags for nimldr
You can execute nimldr with flags to modify how the installer runs, or to specify information.
All installations
Debug level, 0 - 5 (default, 0)
Installation logfile
Location for temporary files during installation; default is
NimBUS domain name
NimBUS hub name
Override robot name Default,
NimBUS installation path; Default,
Override package file name. The default installation file is detected by the program.
: The file name is case-sensitive. Omit the .zip extension.
Install as the current user, and not as root (
First probe port
If you omit this flag (recommended), the system assigns the first probe to port
, or the first available subsequent port. Specify any available port. The port number increments by 1 for each subsequent assignment.
The IP address for the robot
Set the automatic unregister flag. Default,
Set the robot to passive mode
for NAT This is a special case, use caution.
Print the version of
Print this help text.
Installation file is on local system
If the installation file is on the local system, specify the directory containing the installation file.
Installation file is on a NimBUS Distribution Server
The IP address of the NimBUS hub running a Distribution Server. This parameter overrides the
The username for logging in to the hub.
The password for logging in to the hub.
Package version Use the specified version of the package, and not the latest one.
Installation modes
Install only the robot (default)
Install an Infrastructure (robot, hub, nas, and distsrv)
Express installation This method uses the defaults, or supplied flags.  The installation file must be on the local system.
Silent express installation If there is an error, this method fails instead of going to interactive mode. The installation file must be on the local system.
Cloud installation
option not available for AIX systems
The number of restarts until robot is expected to become active
DNS name of the system running the hub
nimldr Robot and Hub Questions
During the install process, the nimldr utility prompts you to answer questions. The following table lists all the potential questions. Not all questions are asked. Some questions depend on your answers to previous questions, and some depend on the type of installation you are performing.
In the installer, the default answers are in brackets. Press
to accept the default.
Where should nimldr store temporary files?
Directory of your choice
Do we have the installation file locally?
Where do we have the installation file(s)?
to installation files
Is there a host running a hub we can query for the installation file?
What is the IP address of the host running a hub?
IP address
What is the Domain called?
Domain name
(if it exists)
Desired name
(if it is created)
(asterisk) to search for domains
What is the hub called?
Hub name
(if it exists)
Desired name
(if it is created)
to search for hubs
What is the installation file called?
Which of these archives would you like to connect to?
Archive name
Enter username and password.
for the administrator account set up during UIM installation
Where do we have the installation files?
Install file directory
(if local)
What are we installing?
(robot only)
(robot and hub, tunnel server, or tunnel client)
Would you like to install the Distribution Server (distsrv)?
distsrv is the UIM probe archive
Where should the software be installed?
Automatically unregister robot from hub on termination?
Should this robot run in passive mode?
(default; robot sends data to hub)
(hub must request data from robot)
What is this Domain called?
set up during UIM installation
Which hub should this robot connect to?
Hub name
What is this hub called?
Hub name
What is that hub's IP address?
IP address
Are you setting up a tunnel between this hub and another hub?
Would you like to initialize the security settings on this hub?
Please specify the administrator user password.
for the account created during UIM installation
Are you setting up a tunnel between this hub and another hub?
(default, installation completes and the installer exits)
(installation continues)
Nimldr Tunnel Client Questions
Answer the following questions to set up a tunnel client hub.
What is the IP address of the tunnel server hub?
Tunnel server hub IP address
What port is the server listening on?
Port number assigned during UIM installation; typically 48000 (default)
What password was used to generate this certificate?
Password that is defined when the tunnel client certificate was created during tunnel server setup
What file is the client certificate in?
Path and file name for the client certificate that was copied from the tunnel server to the tunnel client
Run the nimldr Utility
Run the nimldr utility to install secondary hubs and robots.
Follow these steps:
  1. If UIM software is installed and running on the system, turn off all UIM processes and remove the software. Execute:
    /opt/Nimsoft/bin/niminit stop /opt/Nimsoft/bin/ remove
  2. Verify that the system
    file maps to localhost, and its own IP address to its hostname.
  3. Download and unpack the installers:
    1. On the client computer, browse to your UIM Server home page:
      The default wasp port number is 80.
      Click the
      tab. Under
      Infrastructure Installers
      , select
      UNIX installation utility (nimldr) for all platforms
      , and save the archive on the client. If the client system does not have a browser, download the installer to another computer and copy it to the client. Ensure the file is named
    2. Uncompress and extract the file,
      , using the tar command:
      # tar -xzf nimldr.tar.Z
      This command creates the subdirectories that contain nimldr installers for various Linux platforms.
      On certain non-Linux UNIX platforms, the tar command does not contain the
      option. In such cases, follow these steps:
      1. Use
        uncompress nimldr.tar.Z
        gunzip nimldr.tar.Z
        to uncompress nimldr.tar.Z file.
      2. Use
        tar -xf nimldr.tar
        tar -xvf nimldr.tar
        to extract the contents of the nimldr.tar file.
  4. Enter the appropriate subdirectory for your platform. For example,
  5. Change the file permissions to add executable permissions for the file owner:
    # chmod 755 nimldr
  6. Launch the installer. If the client is on the:
    • Same network segment as the primary hub, execute:
      # ./nimldr
    • Different network segment, execute:
      # ./nimldr -I NMS_server_name_or_IP_address
  7. Answer the nimldr questions to install the hub.
  8. If you are installing a tunnel server hub:
    1. Answer the nimldr tunnel server questions. The values are used to generate the tunnel client certificate, and save it to a file.
    2. Copy the certificate file to the tunnel client hub. After installation, install the certificate on the tunnel client hub
  9. If you are installing a tunnel client hub:
    1. Ensure that the certificate file resides on the hub.
    2. Answer the nimldr tunnel client questions.
Installation progress is logged in the
file, typically located in
. To view it, execute:
tail -f /opt/nimsoft/tmp/nimldr.log
Example: Perform an Installation with a Local File
This example provides high-level steps to perform an installation with a local file.
Follow these steps:
  1. Copy
    to a directory on the computer, such as
  2. Rename the version information from the install file
  3. Run
    from the
  4. Specify
    when the installer prompts you to specify whether the installation file is available locally (
    Do we have the installation file locally?
  5. Specify
    when the installer prompts you to specify the installation file location (
    Where do we have the installation file(s)?
  6. Continue with the remianing installation steps.
Next Steps
  • Set up queues and tunnels between hubs. See the Hub probe documentation on the Probes Documentation Space for more information.
  • If you want to use Admin Console to manage this hub or its child robots or probes, deploy the Probe Provisioning Manager (ppm) probe to the hub. Use either Admin Console or Infrastructure Manager to deploy the probe from your local archive.