DX Unified Infrastructure Management

I have a question about a strange case with CA UIM 8.2 robot 7.80 and RHEL 7.2 x64

We are monitoring linux RHEL servers those are in network address 10.0.0.0/28.

The nimsoft secondary hub is in network 10.55.250.5/29

There is connectivity (ICMP Ping) between both ends - Secondary Hub to Servers and Servers to Secondary Hub.

There is telnet from ports 22,80,443,48000-48030 between both ends. Secondary Hubs to Servers and Servers to Secondary Hub.

There is no ACLs/Blocks in firewall between the networks. 

Unfortunately, when we start the robot version 7.80 that is in any server with version RHEL 7.2, the robot is attached in secondary hub, we can see the robot in Infrastructure Manager, but there is a problem in communication.

All telnets connections from secondary hub to server with robot cease to work. Telnet from secondary hub to server in any Port Open (22,80,443,48000, etc) cease to work. When we stop the robot, all telnets from secondary hub to server begins to work again. 

I think it is a problem in Robot, because there is only one Server, in the same network, with RHEL 6.3 that is work perfectly.

Anyone have any idea about this case?

Regards,

Jean Gomes

Try to reinstall a robot by runnig the nimldr utility with -I option.

# ./nimldr -I NMS_server_name_or_IP_address

Hi David,

We tried your suggestion, but doesn't worked. 

Regards,

Jean Gomes

Hi Jean,

Try to set the 127.0.0.1 server_name on the etc/hosts

Rubens

Hi Rubens,

We tried your sugestion, but doesn't work.

Regards,

Jean Gomes

In case its not already tried , set 

robotname = set this to the computer hostname (shortname)
robotip = set this to the local/internal IP address of the machine 
first_probe_port = 48003

If there is any NAT'ing involved, meaning the registered robot IP is not reachable directly but only through a NAT'ed interface, add the following parameters to your robot.cfg file for the robot where you are unable to reach the probes.

robotip_alias = <NAT'ed IP through which Robot can be reached>

Knowledge Base Articles 

Knowledge Base Articles