After Installing the robot on AIX it is getting discovered but giving the communication error while opening the controller.
Some Linux environments have trouble auto-detecting the local IP which causes problems with probes listening for incoming connections.
The first thing to try is to manually set the specific hostname and IP address in the robot.cfg file under /opt/nimsoft directory.
Leave all defaults in place except the following three lines:
robotname = set this to the computer hostname (shortname)
robotip = set this to the local/internal IP address of the machine
first_probe_port = 48003
Also, it is important to note that the local firewall may play a role here; generally speaking you should open ports 48000-48100 on any Nimsoft Robot, allowing connections from all other machines on the local network.
hope it helps,
This is a known-issue with robot on UNIX systems - it's because the robot uses /etc/hosts to determine it's IP address.
See UNIX Robot Communication Fails Due to Invalid /etc/hosts - CA Unified Infrastructure Management - 8.31 - CA Technologies…
This issue is apparent when looking at the robot in the hub IM, as it will normally showing the IP of another interface or 127.0.0.1 (more commonly).
If this is the case, then you only need change/add the robotip = <replace with ip address> line to the robot.cfg, stop the robot, delete the robot from the hub IM and restart the robot. This will cause the robot to register onto the hub again with the specified ip address. You can then test again to see if it resolves this issue - if not then ports between robot and hub may be blocked (which you can use telnet to check).
Retrieving data ...