UIM MCS profiles failed to deploy to robot in different domain

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We have a UIM hub that is using MCS group to push out CDM Probe and Profiles. We have no issue monitoring UIM Robots using MCS group and Profiles in the same Domain. But now we have servers in different Domain that we need to monitor by the same UIM Hub, MSC group and Profiles.

The new UIM Robots were installed on servers with a different UIM domain and they appeared in the MCS group but all Profiles failed with an error:

   ( (80) Session error, Unable to open a client session for ##.##.##.##:48000; Connection timed out, connect).

According to our Network team FW ports were opened between the UIM hub and all  servers in the different Domain. If we are seeing all new Robots in OC under the MCS group that proves the robot port is open?

If so, why are the profiles failing?

Environment

• Release: 20.4

Resolution

Expected ports were not fully opened by the network team.