DX Unified Infrastructure Management

I am new to an existing large environment....there are numerous systems here with cdm and logmon failing to start with the following:

Mar  9 18:20:27:721 [139898666776352] logmon: sockServer: next available port is 48012
Mar  9 18:20:27:721 [139898666776352] logmon: sockServer: bind failed 98
Mar  9 18:20:27:721 [139898666776352] logmon: nimSession - failed to create server session on port 0, error code 98
Mar  9 18:20:27:721 [139898666776352] logmon: nimSession failed

There seems to be a problem using any port above 48012, and also 48003-48006 are skipped on most systems.

Besides firewall blocks and other programs using these ports, is there any other reason these might fail?

At what point does the controller quit looking for a new port for a probe when attempts to connect to them fail?

check controller.log, controller is the probe that loads other probes and is responsible for getting ports

If you are sure that no Firewall and Antivirus are actually blocking communication (ports from 48000 to 48099 is required to be open),

First:

- Check if the probes, the robot version and the operating systems are compatible and supported. If your are running OS's version that not mentioned in the matrices, it might be one of the reasons it is not working as expected.

https://support.nimsoft.com/downloads/doc/Platform_Support_Availability_current.pdf 
https://support.nimsoft.com/downloads/doc/NMSCompatibility_SupportMatrix_current.pdf 

Then:

In the robot.cfg, try to change the first probe port key:

By default key looks like this:

first_probe_port = 48000

Change it to something else inside your open range throw the firewall:

First try: 

first_probe_port = 48005

If same issue:

Change it to something higher within your open range:

ie:

first_probe_port = 48013

Please also check you have a valid localhost entry in the etc/hosts file

on the  system. This must be a fully qualified hostname and IP address.

If only loopback is defined (for example, localhost 127.0.0.1), then the controller probe on that system will be unaware of its own IP address, resulting in network communication failure.

Kind regards,

Britta Hoffner