---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Test MID Server connectivity

# Test MID Server connectivity {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Confirm that the MID Server host is able to communicate with the instance. Resolve
any issues with the network connectivity such as conflicts with firewalls, access control
lists, and routing errors. Successful communication is necessary for automatic
upgrades.

## Vorbereitungen

Role required: admin  

|-|
|   |
[ ]

{#t_ValidateNetworkConnectivity__table_jjm_fs4_nhb}

## Warum und wann dieser Vorgang ausgeführt wird

The computer that hosts the MID Server must be able to access one of these URLs to upgrade automatically:

* HTTPS: `https://install.service-now.com on the default HTTPS port
  (443)`
* HTTP: `http://install.service-now.com on the default HTTPS port
  (80)`
{#t_ValidateNetworkConnectivity__ul_q2s_tnt_px}

## Prozedur

1. Use PING to test connectivity with the host on the network (ping\<host IP\>).
2. If no ping response is returned, use TRACEROUTE to see where traffic might be stopped (traceroute\<host\>).
3. Use TELNET to connect to any of the TCP ports (telnet\<host\> \<port\>).
4. Use an SNMP scanning tool to determine if a potential network device is responsive.
5. Resolve the most likely issues around network connectivity:
   * Routing: Confirm that the MID Server host has network access to the IP ranges you are attempting to discover.
   * Firewalls: Confirm access to the physical firewalls that protect a large environment such as the Data Center. Confirm access to any logical firewalls that protect an individual computer. MID Server communications are initiated inside the firewall and therefore do not require any special firewall rules or VPNs.
   * Access Control Lists (ACL): Confirm that ACLs contain the IP addresses based list on SNMP network devices that allows communication to a particular target.
   * Resolve all issues with your network teams to better understand your topology. Deploy additional MID Servers if necessary to help keep your network secure. Configure access from your existing MID Server host to networking components.
6. Verify that the MID Server service is running on the host:
   * Windows: In the Windows Services console, locate the ServiceNow \[MID Server name\] and confirm that each MID Server has the Started Status value.
   * Linux: Ensure that the agent0.log.0.lck appears in the /servicenow/ MID Server name\]/agent folder.
   {#t_ValidateNetworkConnectivity__choices_cr2_xsy_r1b}
7. After each MID Server restart, open the agent0.log.0 and address all error messages.
8. From the ServiceNow instance, navigate to MID ServerServers.
9. Review and verify that all MID Servers that are connected to the instance are listed.
10. Verify that the Status is Up for the MID Servers.

## Nächste Maßnahme

This concludes the installation of a single MID Server. If necessary, continue to
[deploy multiple MID
Servers from a single host](https://servicenow-prod.fluidtopics.net/Db6PQgljVCvKe3xyUBFoYw#t_InstallMultplMIDSvrOnASingleSys "Install multiple MID Servers on the same host computer. Multiple MID Servers can support each other with load balancing, as well as use domain separation. The number of MID Servers required is determined by factors like network policies, security restraints, and the reliability of the host computer.") in your network. Otherwise, begin [configuring your MID
Server](https://servicenow-prod.fluidtopics.net/uqhk3S8zX3n_fiVotz_twA "After installing and validating your MID Servers, ensure that they have access to sufficient system resources, probe the proper targets, and communicate with the instance as expected. Configure MID Server selection criteria, create clusters for failover protection, and set up MID Servers in different domains to protect data.").