Problem configuring passive robot (9.20HF10)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

I migrated a robot from one hub to another (as part of retiring old hub servers), and under the new hub I had to make the robot a passive robot. The hub is able to connect just fine, and the robot is green in Infrastructure Manager. But I find myself unable to configure any probes on it, including the controller.

I had to test on a different robot, as I'm currently unable to deploy upgrades to the robot that was already passive. Similar to before, I am seeing this in the log:

Feb 10 15:36:00:679 [140415332546368] 2 Controller: nimVerifyLogin robot
Feb 10 15:36:00:679 [140415332546368] 1 Controller: verify - [target] prid=controller cmd=probe_list ip=1x7.xxx.xxx.xxx perm=1
Feb 10 15:36:00:680 [140415332546368] 0 Controller: verify - SID is issued to another IP (sid=1x2.x.xx.xxx [list=|||172.xx.xx.xxx|] req=1x7.xxx.xxx.xxx)
Feb 10 15:36:00:680 [140415332546368] 1 Controller: verify - [source] id=xxxxx.xxxxx.super ip=1x2.xx.xx.xxx hub=Ixx-xxx-xA perm=4 ver=3 (illegal SID)
Feb 10 15:36:00:680 [140415332546368] 1 Controller: (nimVerifyLogin) cmd=probe_list frm=1x7.xxx.xxx.xxx/xxx failed

IP validation is disabled in our environment.

Sometimes I see this error in the log instead:

Feb 10 15:35:04:832 [140415332546368] 2 Controller: nimVerifyLogin robot
Feb 10 15:35:04:832 [140415332546368] 1 Controller: verify - [target] prid=controller cmd=probe_list ip=xxxxxxxxxxxxxx perm=1
Feb 10 15:35:04:832 [140415332546368] 0 Controller: verify - SID has invalid signature: 2QVGrYAHas09bv/f1OpnlQADMTU4MjAzODUxMgFJbnQtRFNNLTFBATABMTcyLjI0LjMwLjIxNQEBMAFrZWl0aC5rcnVlcGtlLnN1cGVyATQBfHx8MTcyLjI0LjMwLjIxNXxB
Feb 10 15:35:04:832 [140415332546368] 1 Controller: verify - [source] id=xxxxx ip=xxx.xx.xx.xxx hub=Ixxxxxxxperm=0 ver=3 (illegal SID)
Feb 10 15:35:04:832 [140415332546368] 1 Controller: (nimVerifyLogin) cmd=probe_list frm=xxx.xx.xx.xxx/57x60 failed

Environment

Release : 8.51

Component : UIM - ROBOT

Cause

- passive robot defects

Resolution

Deployed two updated packages which contained passive robot fixes:

- hub v9.20HF9
- robot v9.30HF1