AS400 robot not displaying the probe address and port number in IM and also we are not receiving any metrics and alarms from the same robots

Products

• NIMSOFT PROBES
• DX Infrastructure Management

Issue/Introduction

Not displaying the Probe address and port no in IM and also we are not receiving any metrics and alarms from the same robots. I checked the telnet connectivity and it is fine.

AS400 system hostname-> SYXX

- IM -> Tools->Connect to the robot worked fine
- telnet to the robot at port 48000 worked fine
- Only the controller port is displayed
- Restart of robot made no difference
- All affected AS400 systems are NATTED, others re working fine and ports are displayed
- The hub was not on the same network segment as the robot
- controller showed no errors

spooler log showed errors:

Jul 17 09:24:58:945 spooler: ########## START ########## 
Jul 17 09:24:58:945 spooler: Robot Spooler 5.71 [Jun 29 2012] 
Jul 17 09:24:58:945 spooler: Nimsoft LLC 
Jul 17 09:24:58:945 spooler: PID=527728, loglevel=2 
Jul 17 09:24:58:946 spooler: robot=sysd domain= 
Jul 17 09:24:58:946 spooler: spooling=off flush_timeout=60 flush_priority=3 flush_records=30 
Jul 17 09:24:58:946 spooler: expire=259200 
Jul 17 09:28:07:949 spooler: sockConnect - connect to 10.60.xxx.xxx 48000 failed 3447 
Jul 17 09:28:07:949 spooler: nimSessionNew - _probeCheckin failed - communication error 
Jul 17 09:31:16:955 spooler: sockConnect - connect to 10.60.xxx.xxx 48000 failed 3447 
Jul 17 09:31:16:955 spooler: nimSessionNew - _probeCheckin failed - communication error

Cause

- network routing/NAT

Environment

Release : 9.1.0

Component : UIM - ROBOT 5.71

Resolution

Steps taken to resolve:

Edit the AS400/iSeries robot.cfg and set the following:

robotip = 10.xx.xxx.45
(how the Primary Hub sees the machine)
robotip_alias = 167.xxx.10.70
(internal IP)
strict_ip_binding = no
local_ip_validation = no
No need to set contip parameter

In the left hand navigation pane, RT-click and restart the AS400 robot

All other robots now show ALL ports as expected not just the controller

NAT configuration probably due to network routing/NAT setup for the AS400 systems