MidServer Functionality Validation

[matthewroal]

Hello,

I just took over an existing Discovery configuration, with zero documentation.

We have five mid-servers. Two of them, based upon their configuration and the devices we see, are functional. Three of them have capabilities configured, but no IP address ranges set. The places they should be scanning overlap heavily with our SCCM connector, and I'm trying to determine if the mid-servers are even needed. 

When I check the ECC queue, I do see that the various inputs from the three servers, and it looks as though they may be running their capabilities, since I can see the results of the probes showing device information for other machines. 

This gives me two questions:

1. Is the ECC queue the only way I can map MidServer X performed action Y and found Laptop Z? Do the midservers keep any kind of local logs indicating what they've found that I could review? 

2. I was under the impression that MidServers have to have an IP Range specified in order for their capabilities to function. Is this incorrect? If so, are there capabilities that require an ip range, and won't function without one being specified?

[Danish Bhairag2]

Hi @matthewroal ,

1. How to identify which MID Server discovered a device

• ECC Queue is the main place to trace the actual Discovery activity, probes, sensors, and MID Server involved.
• You can also check Discovery Status / Discovery Log for the Discovery run and identify which MID Server was used.
• Credentials can help determine which MID Server is mapped/selected for a credential, but credentials alone don't prove that a specific MID Server discovered a particular CI.

MID Servers do maintain local logs, but these are mainly operational/debug logs and are not a clean inventory of "MID Server X discovered Laptop Z." They are useful for troubleshooting.

2. Does a MID Server need an IP range?

No. A MID Server does not need an IP range just to have capabilities or to function.

• IP ranges are primarily associated with Discovery schedules/ranges and determine what IPs Discovery scans.
• A MID Server can be used for other activities such as Orchestration, integrations, Service Graph Connectors, SCCM, REST/SOAP calls, etc., without having Discovery IP ranges assigned.
• Some Discovery mechanisms can dynamically determine targets or be initiated from other sources, so absence of a MID Server IP range doesn't necessarily mean the MID Server is unused.

Thanks,

Danish Bhairagdar