[BUG FIX]: Ping MP ‘false positive’ situation may occur

[BUG FIX]: Ping MP ‘false positive’ situation may occur

Problem:

It looks like the Ping MP isn’t reporting configured hosts that are down.

Investigation:

If you configure a server that must be monitored by the Ping MP (called Target Host) you specify an IP address using the Configuration Dashboard. If you don’t specify a valid IP range, for example an extra space / other chars or 255+ numbers, the workflows will be unloaded by SCOM. This will result in a ‘false positive’ situation. You think the servers are pingable because SCOM reports a healthy situation, but it could be they aren’t. The Operations Manager NT Eventlog of the configured Ping Host (the SCOM agent you use to execute the ping checks for the target hosts) will contain 1206 events, describing the unloading of the workflows.

Solution:

Please check if you have entered valid V4 IP ranges. So no chars (example: trailing, leading spaces) and numbers higher than 255. If you have a big list of configured ping servers you can use the Export/Import Batch function found in the OpsLogix Ping IMP configuration dashboard or you can press CTRL + A in the Targets -> Status View and copy the section to an excel sheet. Review the IPs and fix the incorrect ones.

Action taken by the OpsLogix Team:

There will be a fix release for this issue in a short time window.

This issue has been resolved.

If you have any questions or suggestions we are happy to assist you.

OpsLogix Team

Scaling the Ping Management Pack

Scaling the Ping Management Pack

Just a quick word on the scaling/sizing of the free Ping Management Pack.

From all the feedback we have received over the years on the sizing of the Ping Management Pack, the following can be used as a rule of thumb:

  • A physical Windows based machine (Windows 2003/2008/2012) with a SCOM agent (2007 R2 / 2012 SP1/R2) installed, will be able to handle a maximum of about 800 ping targets.
  • The Windows based machine should have 4 GB RAM and at least 1 CPU.
  • When running the Ping Management Pack from a Virtual Windows based machine, depending on its resource configuration, the maximum number of ping targets per Ping Host might far smaller than 800.

Finally, the Ping Management Pack demands resources from SCOM. When only a few Ping targets are configured, SCOM will probably be able to handle the additional workflows with ease. By default the Ping Management Pack only runs two workflows per Ping Target. If you are planning to configure hundreds or even thousands of Ping Targets, you will need to size your SCOM environment to cope with the workload accordingly.

 

As usual the disclaimer: OpsLogix will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information.

Understanding the Ping MP’s “Target Host Ping Check” Monitor parameters

Understanding the Ping MP’s “Target Host Ping Check” Monitor parameters

In the past I have gotten a lot of questions on the overridable parameters for the “Target Host Ping Check” Monitor in the Ping Management Pack, this is reason for the blog entry “Understanding the Ping MP’s “Target Host Ping Check” Monitor parameters”.

By default the monitor pings a target once a minute and turns to critical if it doesn’t get a reply if the target doesn’t reply to the second ping. For various reasons some organizations don’t always want the monitor to turn to critical right after only one ping response was missed.


To influence this behavior there are a couple of parameters you can override:

  • Interval
  • NumberOfNoRepliesAllowed

 


 

For example let’s say that we want to ping a target, but only want the monitor to turn critical after three responses have been missed. In this case we set the NumberOfNoRepliesAllowed
to 3. This setting will result in the monitor only turning to critical after four minutes if three consecutive pings are missed.

Now if four minutes is too long for the monitor to turn critical, you can adjust the Interval
parameter. The Interval parameter controls the amount of time between the pings. If in the same example you would like the monitor to turn to critical after two minutes, you should adjust the Interval parameter to 30. This would mean the following for this example:

  • The monitor pings every 30 seconds
  • The monitor is allowed to miss three consecutive pings and if the fourth ping is missed to it turns to a critical state
  • 30 seconds * 4 = 2 minutes

 


KB0005 – Ping IMP Configuration Dashboard Crashes due to a”blank ping target”

KB0005 – Ping IMP Configuration Dashboard Crashes due to a”blank ping target”

If the Ping IMP Configuration Dashboard crashes unexpectedly, this might be due to a “blank ping target” entry in the OpsMgrDB database.

The “blank ping target” is caused by a bug in the csv import function of the Ping IMP Configuration Dashboard, when you leave a blank line (carriage return) at the end of the csv file. The easiest way to resolve this issue is to export the targets and remove the ping hosts to which the “blank ping target” was added. Wait for an hour or so and re-add the ping host and import the ping targets, making sure you leave no blank line (carriage return) at the end of the csv file.

If you do not want to remove the ping host, an unsupported way of removing the “blank ping target” is by using the SQL statements shown below on the OpsMgr database.

CAUTION: As always make sure you have a current backup of your OpsMgrDB database. Because the method of deleting instances directly from the OpsMgrDB database is not supported by Microsoft, we cannot be held responsible for any damage that might occur as a result of running the SQL statements.

The sql statements below are an adaptation of the SQL statement from the blog post: http://basementjack.com/uncategorized/remove-stubbornstuck-computer-objects-from-ms-scom/

  1. Open SQL Management Studio and connect to the OpMgrDB
  2. First check if there are any blank entries for the source host name by running the following sql statement:

    Select * from basemanagedentity where Path
    like ‘<Source Host name>%’
    and Name is null
    and DisplayName =

  3. Then if you are sure you have the correct instance (source host) run the following:

    Update BaseManagedEntity Set Isdeleted=1 where Path
    like ‘<Source Host name>%’
    and Name is null
    and DisplayName =

After the SQL statements are run, the “blank ping target” should no longer exist in the Ping IMP Configuration Dashboard.