ITCAM for Transactions - ISM - Q and A - PART 4 (Technotes based)
ericmtn 1000009W88 Visits (3966)
Here is a summary and compilation of some good DCF technotes that list some questions and answers regarding ISM (Internet Service Monitoring) Agent environment.
This is part 4 of this blog.
Q) How should the ICMP monitor and elements be configured and tuned for high volume monitoring and environment?
A) The main factors on the ICMP monitor performance is the number of pings that are required to be sent to complete the current set of configuration and the time intervals allowed to complete them within.
The number of pings and timing intervals are controlled with the following element parameters:
Based on these configuration setting the total number of required pings can be calculated. Calculations assume that all elements are configured with the same options.
Best case scenario (all tests pass):
Worse case scenario (all tests fail):
Using the default configuration values in order to test 1000 hosts it would require the following number of pings:
If the elements were configured to be retested twice on failure the maximum number of pings would then be:
Adding a single retry for a failed pings onto this would require:
As the number of hosts required to be polled increases there are two main ways to tune the configuration, by increasing the poll interval to provide a larger time window to send the required pings and/or reducing the number of pings being sent per test. In order to reduce the number of pings required to complete an element the use of retries and retests should be kept to a minimum. Additionally consider reducing the number of pings per element from the default of 5.
The maximum throughput of the monitor can be configured using the following monitor properties:
Using the calculated total pings required value you can estimate a PingsPerSec setting by dividing it by the Total Pings by the poll interval.
This is only a rough estimate as it isn't taking into account the additional wait times for retests and intervals between pings in a test. Additionally this calculation is for the worst case scenario where every element will send the maximum number of pings possible. The total number of pings value can be adjusted to take into account the expected failure rate in your environment.
For example estimating a 10% failure rate:
Caution should be taken with setting the PingsPerSec to larger values (1000 or more) as it can cause the ICMP monitor to flood the network with ICMP traffic. In some cases network infrastructure can detect this as a ping flood which can interrupt with the operation of the monitor if packets are dropped. In this case the IntraPingWait option might need to be enabled which will cause the monitor to space out the sending of ping values. Using this option will limit the throughput of the monitor and should only be used if absolutely necessary. It should be set using the following formula:
A common cause of ping failures on multihomed machines is for the ICMP monitor to bind to the incorrect IP Address. This binding behavior can be controlled with the following properties:
Remark1: Unlike the other type of ISM monitors, ICMP monitor is not multi-threaded, as documented here:
so MaxCCA parameter doesn't apply to ICMP monitor.
Remark2: another possible parameter to tune is QSize, see : http
For reference, part 1 of this blog: http
Subscribe and follow us for all the latest information directly on your social feeds: