UIM - Installing linux/unix robot using nimldr

book

Article ID: 33977

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)

Issue/Introduction

This KB provides additional information / considerations for installing a robot agent using nimldr utility on linux/ unix platforms

Environment

Release:UIM 9.x/ 20.x.x
Component: 

ROBOT -Linux/ Unix

Resolution

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

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

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

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 computer>

4. Perform a Robot installation on the LINUX/UNIX computers as described in the

Deploy Secondary Hubs and Robots on Linux

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

So 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 Server from the remote node where youre trying to install a Robot.

• Verify /etc/hosts file, if it's just the loopback address you do need to add an entry with the actual IP address, and it has precede the loopback address in 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, 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


Additional Information

Understanding the nimldr utility