4/10 Q. ITOM Project Help !! (Please No Paste CHATGPT ANSWER)

[SandeepKSingh]

I must ensure Discovery and outbound integrations keep running even if one MID Server goes down. How we can Build a high-availability  + failover setup for two (or more) MID Servers across the same network, so that:

• Jobs are load-balanced during normal operation.

• If MID-A fails, jobs auto-failover to MID-B (and vice-versa) with minimal disruption.

• The design remains upgrade-safe and easy to support.

[Ravi Gaurav · Accepted solution]

Hi @SandeepKSingh 
As you must be knowing
Every MID Server sends a heartbeat to the ServiceNow instance (by default every 40 seconds).

If that heartbeat stops coming in (because the service crashed, server rebooted, or network broke), ServiceNow marks the MID as Down.

You can see this in MID Servers > Status (shows Up, Down, Validate).

According to me You must ensure Discovery and outbound integrations keep running even if one MID Server ...goes down. 

Jobs are load-balanced during normal operation.

If MID-A fails, jobs auto-failover to MID-B (and vice-versa) with minimal disruption.

The design remains upgrade-safe and easy to support.

Example :

MID-A and MID-B: Same site/subnet

Selection method: MID Server Cluster.

Cluster: the one containing MID-A and MID-B.

Keep IP ranges common to the cluster (no hard-binding to a single MID).

Configure monitoring/notifications when a MID goes Down (e.g., notify NOC if heartbeat older than X minutes).

[Dr Atul G- LNG]

Hi @SandeepKSingh 

• Jobs are load-balanced during normal operation.

[Bhuvan]

@SandeepKSingh 

Setup a MID Server cluster and use it for discovery and integrations. This will act both as a load balancer and failover. Refer below link for more details,

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0997595

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[Ravi Gaurav]

I guess @Bhuvan   Cluster alone can't help .. we eed to cheak hearbeat  as well.. every 40 Sec. What you say??

[Bhuvan · Accepted solution]

@Ravi Gaurav 

As per my understanding, it is not mandatory to setup heartbeat and MID Server cluster configuration is enough for failover to work. 

You can refer Business Rule 'MID Server Cluster Management' for more information on the logic.

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/mid-server/reference/...

https://noderegister.service-now.com/kb?id=kb_article_view&sysparm_article=KB0661756

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/mid-server/concept/c_...

Monitoring heartbeat, failed jobs and job status in ServiceNow MID Server Dashboard is useful for tracking overall health of MID Servers.

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan