ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Robot communication error and hub log shows Login: failed for controller, ip = 10.xxx.xxx.xxx

book

Article ID: 238657

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) DX Unified Infrastructure Management (Nimsoft / UIM) Unified Infrastructure Management for Mainframe CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

robot bxxxxx-xxx-it-09.aa.companycom.net controller GUI will not open in IM nor in Admin Console.

In the hub log:

Login: failed for controller, ip = 10.123.xxx.xxx
login - probe ip 10.123.xxx.xxx does not match access mask: '10.zz.xx.xx'

ping of 10.zz.xx.xx = no response

nslookup 10.zz.xx.xx yielded no result/hostname/FQDN.

Cause

- controller entry for specific defunct IP address in IM Security->Probe Administration

Environment

Release : 20.4

Component : UIM - ROBOT 9.32

Resolution

Error in the robot's parent hub.log showed:
   
    hub: login - probe ip 10.123.xxx.xxx does not match access mask: '10.zz.xx.xx'   

for a non-existent seemingly defunct IP-> 10.zz.xx.xx

So, we followed these steps and this particular error was resolved:

In IM go to Security > Probe Administration. There will be an entry for controller with an IP address listed.

Probe Administration should not have an entry for the controller, so delete the entry.

Restart of the Primary and Secondary hubs may be needed.

Additional Information

This workaround prevented any further login failed errors but did nothing to resolve the robot communication error.