Hub robot with mcs profiles stay in pending, while robots under the hub using the same profiles are active
search cancel

Hub robot with mcs profiles stay in pending, while robots under the hub using the same profiles are active

book

Article ID: 392230

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have hubs that have mcs profiles pushed to them, that will never go active. Metrics are being collected, but the profiles stay in a pending state.

Environment

Version: 23.4
Component: mon_config_service 

Cause

Security filter was set (IM > Security > Probe Administration) for controller, and hub. This was creating an issue where the spooler probe on the hub could not create the needed checksum to be verified with the UIM database.

Message in hub.log:

verify_login from ctrl 10.0.0.1/61627
verify - [target] prid=controller cmd=probe_list  ip=10.0.0.1 perm=1
verify - filter access denied ip=10.0.0.1
...
login - probe ip 10.0.0.1 does not match access mask: '10.0.0.2'

Resolution

Update IM > Security > Probe Administration for controller, and or hub if a filter is present to an asterisk '*'.