There are times when some UIM administrators don't have access to Linux/UNIX machines without needing to schedule time in the future with other team members that may or may not have flexibility, e.g., to check the status/processes of a non-working robot or hub or to make any changes to the system.
Open a support case or update an existing one and collect the following info and share it with support.
Run each command as root and copy and PASTE the output for all the following:
Note: Ensure you have added robotip = <ip_address> to the controller section of the robot.cfg to ensure proper robot registration.
1. Check robot processes
ps -ef | grep nim
The robot's processes are controller, hdb and spooler.
2. Check robot status
/opt/nimsoft/bin/niminit status
3. Try to start the robot
/opt/nimsoft/bin/niminit start
4. Check OS and version
oslevel -s
cat /etc/os-release (Linux)
5. Check network connctions, ports, stats
netstat –an | findstr "48000"
6. Check DNS resolution
nslookup <hostname>
nslookup <IP>
7. Check connectivity
From the robot command line:
telnet <hub_ip> 48002
Confirms the robot can reach the Primary/Secondary Hub on port 48002.
8. Check hostname is valid/accurate (unchanged)
hostname
9. Check hosts file
cat or vi /etc/hosts and search for the hostnames/IPs
Usage: Ensure robotip or hostname is correctly mapped in /etc/hosts
10. Check network route/routing
traceroute <hub_ip>
Detects network routing issues to the hub. Run it from the hub and from the robot (both directions).
telnet TO the robot FROM the hub on port 48000
telnet TO the hub FROM the robot on port 48002
11. Check security software
Is there any security/whitelisting software like Illumio installed on the machine (Y/N)?
12. List firewall filter rules
AIX
lsdev -Cc IPsec
If the output includes ipsec_v4 Available, it means the IP Security extension is available.
/usr/sbin/lsfilt -v 4 -O -a
lsfilt: List filters rules present in the table. When created, each rule is assigned a number, which can be easily seen using this command.
Linux
firewall-cmd --state
systemctl stop firewalld
13. Check and upload logs (if you have a support case or open one)
Logs to upload:
controller.log
hub.log (from the parent robot)
14. Check for missing libraries
Run the ldd command (Linux/Unix systems)
On Linux/Unix systems run the ldd command on the probe in the probe directory, e.g., ldd <probe_name> to see if there are any missing libraries.
as an example, when trying to run the controller on a Linux OS, if the probe cannot start, you can run the ldd command and examine the output.
cd /opt/nimsoft/robot
# ldd controller
For example, ldd controller output showing an error regarding a missing library file on AIX 7:
/usr/lib/libc.a(shr_64.o)
/usr/lib/libpthread.a(shr_xpg5_64.o)
/usr/lib/libdl.a(shr_64.o)
/usr/lib/libiconv.a(libiconv.so.2)
ar: 0707-109 Member name libiconv.so.2 does not exist.
dump: /tmp/tmpdir..../extract/libiconv.so.2: 0654-106 Cannot open the specified file.
./lib/libnim_shared.so
/unix
/usr/lib/libcrypt.a(shr_64.o)
/usr/lib/libpthreads.a(shr_xpg5_64.o)
Another AIX OS system example:
bash-4.3# ldd controller
controller needs:
/usr/lib/libc.a(shr_64.o)
/usr/lib/libpthread.a(shr_xpg5_64.o)
/usr/lib/libdl.a(shr_64.o)
./lib/libiconv.a(libiconv.so.2)
Cannot find libpcre2-8.a(libpcre2-8.so.0)
./lib/libnim_shared.so
/unix
/usr/lib/libcrypt.a(shr_64.o)
./lib/libgcc_s.a(shr.o)
/usr/lib/libpthreads.a(shr_xpg5_64.o)
Cannot find libpcre2-8.a(libpcre2-8.so.0)
Miscellaneous
Do NOT do the following unless explicitly asked to - when working with Broadcom Support...
Uninstall and Clean Up
Remove Robot RPM: rpm -e nimsoft-robot
Usage: Uninstalls the robot if installed via RPM.
Remove Service: rmssys -s nimbus
Usage: Ensures the Nimbus service is removed from the AIX System Resource Controller (SRC).
Clean Directories: rm -rf /opt/nimsoft
Usage: Removes all associated files to prepare for a fresh install.