Robots from remote hub not in inventory and no QOS visible in OC for them
search cancel

Robots from remote hub not in inventory and no QOS visible in OC for them

book

Article ID: 281109

calendar_today

Updated On: 03-25-2024

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have a Tunnel hub and robots from this specific hub are not showing as correctly discovered in the OC inventory. We can see alarms from the robots but systems are only discovered as VM's from the Vmware probe, but not as robots as we expect.

Also, QOS is reaching the DB, but metrics are not visible under the discovered systems in OC. 

Also, when we are logged into the primary hub in IM, the concerned hub cannot be opened and vice versa from the concerned hub is not possible to open the primary hub. We must log into the specific hub to be able to manage it. 

What is causing this?  

Environment

DX UIM 20.4.*/ 23.4

Cause

These issues could be caused by:

- Communication between the 2 hubs is not enabled correctly hence the Discovery_server cannot reach the concerned robots. 

- QOS is not visible in OC because ci_metric_id's are not getting through to the DB so the OC is not able to display them. 

- TELNET from remote hub to primary hub (Client to server) fails.

Resolution

For using an encrypted tunnel between 2 hubs We must open 48003 as described below.

Firewall Port Reference (broadcom.com)

Tunnel server needs to be able to "receive" inbound connections on port 48003.

Tunnel client needs to be able to "send to" server on port 48003. 

TELNET from remote hub to primary hub (Client to server) must succeed. 

 

Once this communication is enabled between the open ports, the issue will be solved as discovery_server will use the correct route and the remote hub will manageable from IM from the primary hub. 

Additional Information