What is the purpose of setting the MID server IP Range?

[mr_smith]

I read on the Wiki that setting the IP range of a MID server will help Orchestration know which MID server to use. Is the same true for Discovery?

Does this mean if I create a Discovery Schedule for a specific IP and forget to pick the MID server it will choose the MID server based on its IP Ranges?

Does this also mean if I have two MID servers with similar IP Ranges it'll choose between those two?

[amit_dhuleshia]

Discovery does not use IP ranges.

[glennpinto · Accepted solution]

Hi Greg:

Discovery Schedules do not use the MID Server IP Range configurations like Orchestration. The only time a MID Server IP range comes into play is if you run a Quick Discovery. Based on the target IP you choose, a MID with the appropriate IP range could autopopulate the Quick Discovery pop up.

Generally IP ranges being discovered are controlled within the Discovery Schedule. You do have the flexibility to import IP Ranges into the Discovery IP Range Set table and then associate these Range sets to a Discovery Schedule.

With respect to mulitiple MIDs, only the one MID defined in the Discovery Schedule will perform the entire Discovery, unless that MID is part of a Discovery Load Balance Cluster. If this is the case the work will be shared between both MIDs. With Eureka, they introduced in the Discovery Schedule a checkbox to enable Shazzam cluster support.   What this does is if the MID chosen in the schedule is part of a Load Balance Cluster, then the Shazzam probe will be divided between all MIDs in the cluster vs without this option, only the MID chosen in the schedule would run the entire Shazzam phase of the discovery. This can significantly reduce the time of the overall discovery.