MID server auto-selection and clustered mid servers.

[shaunbrachmann]

Discovery and Service Mapping have mid server auto-selection capabilities based upon ip ranges, applications, and capabilities.  Traditionally, Discovery worked by selecting an individual mid server or a cluster.  

In Discovery, when a mid server cluster (load-balanced cluster) member is selected, the ECC Queue entries will be processed by all members of the cluster.  I believe that when Service Mapping auto-selects a load-balanced cluster member that it will automatically load-balance across all cluster members.

Is this assumption correct?

Additionally, if there are multiple mid servers that meet the mid server auto-select criteria, will it automatically load balance across those mid servers even if they are not in a load-balance cluster ?

[johnnyjava]

What a great question, Shuan. I'd like to know if SN thinks that that Clustering is still preferred over using MID Server Selection.

If a Discovery Schedule is set to auto-select MID Servers, will it automagically distribute the load across all MIDs that pass selection criteria?

[krishnavooka]

In Discovery, when a mid server cluster (load-balanced cluster) member is selected, the ECC Queue entries will be processed by all members of the cluster. I believe that when Service Mapping auto-selects a load-balanced cluster member that it will automatically load-balance across all cluster members.

Is this assumption correct?

Yes, for performance improvement, a MID server can be added to load balancing Cluster. MID server clusters are available for Discovery, Service Mapping, Event Management, Orchestration.

Additionally, if there are multiple mid servers that meet the mid server auto-select criteria, will it automatically load balance across those mid servers even if they are not in a load-balanced cluster?

When it comes to auto select,

To determine which MID server to use, ServiceNow Progresses through a selection process.

1. Find all MID servers that have the required Capabilities and are configured to work on the IP Range for the target system.
2. If there is more than one MID server, randomly select one.
3. If there are no MID servers, fall back to the default MID server defined in properties.

So here if the MID servers are not in the cluster then the load is not balanced which means one MID server completes the job.

[Geet6]

Hi Team, what exactly we need to check for auto selection of mid server via quick discovery currently its disabled..Thanks