discovery_server and other probes not starting after changing controller & hub default ports to custom ports
search cancel

discovery_server and other probes not starting after changing controller & hub default ports to custom ports

book

Article ID: 249482

calendar_today

Updated On:

Products

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

Issue/Introduction

Due to security requirements, we need to reconfigure the ports 48000-48002 in our environment. We have changed the ports in our dev environment to observe the impact but after changing the ports from 48000 to 48100 the below probes are failing 

  • cm_data_import
  • discovery_server
  • discovery_agent
In the discovery server log the below error is recorded " (80) Session error, Unable to open a client session for 10.xx.xx.xx:48000: Connection refused: connect
FATAL [main, cm_data_import] (80) Session error, Unable to open a client session for 10.xx.xx.xx:48000:"

Environment

  • Release : 20.3 or higher
  • Component : UIM - DISCOVERY_SERVER

Cause

  • Environmental

Resolution

Tested and confirmed this works using the specified custom ports for the hub, controller, and spooler.
 
Here are additional notes to be aware of that should help.
  1. Deactivate the hub robot

  2. Add/change
hubport = 48102 (change this in the robot.cfg AND the hub.cfg)
 
In the robot.cfg set your other custom ports for controller and spooler:
 
controller_port = 48100

spooler_port = 48101
 
first_probe_port = 48105
  1. You MUST delete the robot.sds and the hubs.sds files from the hub directory on the Primary Hub.

  2. Activate the hub-robot

  3. If the udm_manager probe doesn’t start, check the udm_manager.log for errors and make sure it is pointing to the correct Primary hub and not a failover/HA Hub. If it's not pointing to the correct IP/Primary hub, delete the udm_manger and redeploy it and that should fix the pointer issue.

  4. Then, activate the discovery_agent

  5. Activate discovery_server

Everything started up as expected without issue.

Additional Information

Please also refer to the firewall port reference techdoc:

Firewall Port Reference