Ping Status Monitor

  • ID:  Microsoft.SystemCenter.Ping
  • Description:  This monitor pings a agentless computer using an ICMP ping. If the computer is agent-managed, it pings itself locally.
  • Target:  Windows Computer
  • Enabled:  No

Operational States

Name State Description
Target Reachable Success  
Slow Response Time Warning  
Target Unreachable Error  

Overridable Parameters

Parameter Name Default Value Description Override
Response Time Threshold 5000  
Frequency 300  

Alert Details

Monitor State Message Priority Severity Auto Resolution
Target Unreachable (Error) Failed to Ping Computer Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This monitor pings the target computer on a regular interval and changes state based on whether a response is received or not. By default this monitor is only enabled for agentless managed computers. If the monitor is enabled for an agent-managed computer then the agent will ping itself. This monitor relies on the Win32_PingStatus method WMI to perform its pings and as such will only works on Windows XP and higher or Windows Server 2003 and higher.

Causes

1. The default firewall settings for computers running Windows Vista or Windows Server 2008 prevent the computers from providing a ping response. This cause applies to agent-managed and agentless managed systems alike.

2. If the computer is being agentlessly managed, the computer may no longer be responding via ICMP Ping. This can happen for the following reasons:

  • The computer has been rebooted or shut down

  • The computer's network adapter is not plugged into the network

  • The ICMP Ping request is being dropped or the Time To Live (TTL) has expired

3. If the computer is agent-managed, this could indicate a problem with the local network adapter.

4. There could also be a problem with WMI.

Resolutions

For computers running Windows Vista or Windows Server 2008, configure the firewall to allow incoming ICMP traffic. For instructions, see "Create an Inbound ICMP Rule on Windows Vista or Windows Server 2008" (http://go.microsoft.com/fwlink/?LinkId=161045).

Check if the remote machine is plugged into the network and that it has an IP address. Locally log into the machine, and type the following at the command line:

ipconfig

If the computer doesn't have an IP address or the IP address is 0.0.0.0, repair the network connection on the local machine by following the steps below:

  • Open the Control Panel

  • Open Network Connections

If the category view, Network Connections can be found in the Network and Internet Connections category.

  • Right click on the network connection that cannot be pinged, and choose Repair

  • Check again that the computer has a valid IP address by typing ipconfig from the command line.

  • If this does not work, disable the network connection and then enable it.

External References
This monitor does not contain any external references.

See Also for System Center 2016 Operations Manager inbox MP hotfix for WMI health monitor issue Management Pack


Downloads for System Center 2016 Operations Manager inbox MP hotfix for WMI health monitor issue Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED