Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Test MID Server connectivity

Log in to subscribe to topics and get notified when content changes.

Test MID Server connectivity

Confirm network connectivity to the MID Server host or to the instance for automatic upgrades, and then ensure that the MID Server can communicate with the instance.

Before you begin

Role required: admin

About this task

The MID Server installer download process has changed for new instances in the London release. Access to install.service-now.com is no longer required for the MID Server host machines in your environment. When you request a MID Server installer, the download is performed by the instance, not the MID Server host. This change does not require any additional configuration. Customer instances hosted in a ServiceNow® datacenter have access to install.service-now.com automatically.

Existing MID Servers on upgraded instances do not have the code required to make upgrade requests through the instance and must have access to install.service-now.com for auto-upgrades. During the first MID Server upgrade, however, these MID Servers receive the updates they need to request future upgrades from the instance. You can then configure these MID Servers to send upgrade requests to the instance or continue using the existing download process. All new MID Servers installed for upgraded instances are equipped to make their upgrade requests through the instance.

The computer that hosts existing MID Servers in an upgraded system must be able to access one of these URLs to upgrade automatically for the first time:
  • HTTPS: https://install.service-now.com on the default HTTPS port (443)
  • HTTP: http://install.service-now.com on the default HTTPS port (80)

Procedure

  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.
  7. After each MID Server restart, open the agent0.log.0 and address all error messages.
  8. From the ServiceNow instance, navigate to MID Server > Servers.
  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.
Feedback