Discovery Issue while using clustered approach

[PavanBV]

Hello,

I'm experiencing strange behavior when discovering the CIs using the MID Server Cluster(Load Balance).

The issue is, when the discovery is run using a single mid-server I can see more probes and more devices getting discovered. But when the same schedule is run using a MID server cluster, only a few probes are triggered and fewer devices are discovered. 

Can someone please help me with leads to troubleshoot this?

Note: All the clustered MID servers are sitting on the same host.

DIS0010069, DIS0010068,DIS0010059 are the runs with a single MID server - The probe count is close to 1K

DIS0010067,DIS0010066,DIS0010065 are the runs with MID server cluster - Probe count is ~300-400

[Rahul Priyadars]

All the clustered MID servers are sitting on the same host.---How Come on same Host?

Please check there is no Discovery Behavior configured?

See if this KB helps you- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0635604

Regards

RP

[PavanBV]

Hi Rahul,

Thanks for your response. Yes. unfortunately, they are on the same host as the Infra resources are very limited, and for our DEV environment, we have only one host to have all our MID servers. 

I Had a look at the KB article and looks like having them on the same VM is causing the issue. We have seen a lot of credential and timeout issues in the discovery status record.

[Rahul Priyadars]

How Can any clustering is done on Single Host.

Any kind of HA or Failover Clustering (Server Clusters, SQL Clusters, Mid Server Clusters etc) needs 2 Host at-least. I am interested in knowing how >1 Mid Server Installation on 1 server u clustered it in Service Now?

Regards

RP

[pratiksha5]

If it's on the same host then load balancing won't be of any use. Try failover (cluster type)