search cancel

DX UIM - Installing a Linux/Unix robot using nimldr

book

Article ID: 33977

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

This KB provides additional information / considerations for installing a robot agent using the nimldr utility on Linux or UNIX platforms

Environment

  • Release: UIM 9.x/ 20.x.x/20.3/20.4
  • Component: Robot
  • OS: Linux or Unix

Cause

- Robot installation guidance and tips

Resolution

Installing a Robot on LINUX/UNIX systems where robot was not previously installed:

1. Uncompress the nimldr file:
    # uncompress nimldr.tar.Z

or

    #gunzip nimldr*

2. Extract nimldr.tar
    (This creates a directory on your disk with tree-structure, where you can access the different UNIX platforms):
    #chmod 755 nimldr-9.36.tar

      then

    # tar -xzf nimldr.tar.Z

3. Enter the sub-directory to which your UNIX platform was copied (e.g., LINUX) and run nimldr.

If the LINUX/UNIX system is on the same network segment as the Nimsoft Server computer use:

    #./nimldr

If the UNIX system is on a different network segment use:

    # ./nimldr -I <ip-address to Nimsoft Server (Primary Hub) computer>

4. Perform a Robot installation on the LINUX/UNIX computers as described in the 'Deploy Secondary Hubs and Robots on Linux' article included in the Additional Information section below.

    Note when using nimldr it should ask you if you want to set the first probe port as well, so we recommend you set it to 48000 or 48003.

Please refer to the UIM Compatibility matrix for supported platforms/OS:

UIM compatibility matrix

Other tips

• uname -a

You can decide which install_LINUX package you need to copy/ftp over onto the server (32-bit vs 64-bit) if you cannot connect to the Primary Hub machine from the remote node where you're trying to install a Robot.

• Verify /etc/hosts file, if it just contains the loopback address you do need to add an entry with the actual IP address, and it should precede the loopback address at the top of the file.

• You might need to run nimldr -d 5 (DEBUG MODE) then look at the nimldr.log for what exact install_LINUX file it is looking for. Most of the time when the install_LINUX.zip is ftp'ed/coped over it has a version number appended to the file name, like install_LINUX_3.1.3.zip, so if that happens, you might need to change that to install_LINUX.zip.

• You should be able to finish the robot install and the robot should show up in the Infrastructure Manager as green. If you cannot open the controller (communication error). check two things:

• If you can telnet to the Linux server (robot) on port 48000 from the hub server

   cd /opt/nimsoft/bin (or your install directory if it’s different)

• Run ./niminit stop -> then add an entry in the robot.cfg:

   robotip = <ip address>

   rm -r /opt/nimsoft/pids

   ./niminit start

Note: you can also use nimldr to install a hub  as well; when prompted to install Robot or Infrastructure, choose "2" (Infrastructure.)

Additional Information

Understanding the nimldr utility

To download the nimldr package from the support.nimsoft.com website, you can use wget.

For example,

If wget is not installed, run:

   yum install wget -y

Once its downloaded into your desired directory, run:

   wget http://support.nimsoft.com/Files/Archive/00056/nimldr-9.36.tar.Z