Our Ping Management Pack Just Got An Update – V 3.0.14.0

Our Ping Management Pack Just Got An Update – V 3.0.14.0

We’re happy to announce a new update release of our Ping Management Pack V 3.0.14.0 for SCOM 2012/2016. We’ve added three more Performance Monitors and reworked all the previous monitors in the Management Pack.

The full list of the changes we’ve made to the Ping Management Pack V 3.0.14.0:

  • Replaced the WMI with a managed module to be able to handle a larger load
  • Added a performance monitor for average jitter
  • Added a performance monitor for average latency
  •  Added A performance monitor for average packet loss
  •  Reworked all monitors so the TTL, Payload, and number of an averaging point can be configured
  •  Improved configuration UI

Update Instructions

  1. Go the Ping Management Pack Product Page & download the Management Pack.
  2. Import the updated management packs.
  3. When imported wait +/- 10 minutes to get the updated MPs distributed in your SCOM environment.
  4. Restart the SCOM agent
  5. If you still don’t see the dashboard please follow the instructions here.

Team OpsLogix

OpsLogix Ping Management Pack for SCOM 10.000+ downloads

OpsLogix Ping Management Pack for SCOM 10.000+ downloads

We are extremely excited to announce that the OpsLogix Ping Management Pack has been downloaded over 10.000 times by the System Center community.

The Ping Management Pack is our free contribution to the System Center community.

With the Ping Management Pack, we wanted to give System Center administrators and architects a simple but useful tool to check connections within the infrastructure or network.  The Ping Management Pack enables quick checks and confirmations on whether a monitor or device is up or down and how fast the connection is responding.

We are thankful and happy to see that our free solution is being used on a large scale. At OpsLogix we are committed to creating useful and innovative software that enables organizations to run their operations smoothly. To celebrate this milestone we are offering all our Management Packs with a 5% discount until the end of the year.

5% off on all our Management Packs for SCOM until 31-12-2016

Besides the 5% discount, OpsLogix also offers a highly advanced VMware MP, which you can trade in for the renewal price of our competitors until 31-12-2016. Click here to learn more & request a quote.

Because we are feeling generous, we offer a 5% discount on purchases of our Oracle, BlackBerry, SWIFT, Capacity, ProView and VMware Management Packs until the end of 2016.

OpsLogix5%Off.

Contact sales@opslogix.com or request a quote on our product pages. Use the promotional code OpsLogix5%Off.

 

OpsLogix VMware MP

 

 

[Update] OpsLogix IMP PING Management Pack Update V3.0.12.0

[Update] OpsLogix IMP PING Management Pack Update V3.0.12.0

The OpsLogix Dev team has released an update to fix the issue as described in KB post (https://www.opslogix.com/blog/?p=759).

Please contact OpsLogix Sales for this Updated version V3.0.12.0.

 

Notice: This Version will only be for SCOM 2012 and above.
Notice: We do not provide any fixes for this MP for SCOM 2007.

Changes:

  • If you have configured an incorrect IP format as Ping Target the “Target Host Ping Check” monitor will be put in Warning state and a warning Alert will be generated.
  • If you look into the Health explorer the state will be “Ip is Invalid” shown as the warning state. See screenshot below.

 

 

For the download or if you have any questions please contact OpsLogix Sales.

Greetings,

OpsLogix Dev team.

 

 

[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