[an error occurred while processing this directive][an error occurred while processing this directive]

Gathering Ping Test Results

You can either poll pingResultsOperStatus to find out when the test is complete or request that a trap be sent when the test is complete. For more information about pingResultsOperStatus, see pingResultsTable. For more information about Ping MIB traps, see Generating Traps.

The statistics calculated and then stored in pingResultsTable include:

  • pingResultsMinRtt—Minimum round-trip time
  • pingResultsMaxRtt—Maximum round-trip time
  • pingResultsAverageRtt—Average round-trip time
  • pingResultsProbeResponses—Number of responses received
  • pingResultsSentProbes—Number of attempts to send probes
  • pingResultsRttSumOfSquares—Sum of squares of round-trip times
  • pingResultsLastGoodProbe—Timestamp of the last response

You can also consult pingProbeHistoryTable for more detailed information about each probe. The index used for pingProbeHistoryTable starts at 1, goes to 0xFFFFFFFF, and wraps to 1 again.

For example, if pingCtlProbeCount is 15 and pingCtlMaxRows is 5, then upon completion of the first run of this test, pingProbeHistoryTable contains probes like those in Table 1.

Table 1: Results in pingProbeHistoryTable: After the First Ping Test

pingProbeHistoryIndex

Probe Result

11

Result of 11th probe from run 1

12

Result of 12th probe from run 1

13

Result of 13th probe from run 1

14

Result of 14th probe from run 1

15

Result of 15th probe from run 1

Upon completion of the first probe of the second run of this test, pingProbeHistoryTable will contain probes like those in Table 2.

Table 2: Results in pingProbeHistoryTable: After the First Probe of the Second Test

pingProbeHistoryIndex

Probe Result

12

Result of 12th probe from run 1

13

Result of 13th probe from run 1

14

Result of 14th probe from run 1

15

Result of 15th probe from run 1

16

Result of 1st probe from run 2

Upon completion of the second run of this test, pingProbeHistoryTable will contain probes like those in Table 3.

Table 3: Results in pingProbeHistoryTable: After the Second Ping Test

pingProbeHistoryIndex

Probe Result

26

Result of 11th probe from run 2

27

Result of 12th probe from run 2

28

Result of 13th probe from run 2

29

Result of 14th probe from run 2

30

Result of 15th probe from run 2

History entries can be deleted from the MIB in two ways:

  • More history entries for a given test are added and the number of history entries exceeds pingCtlMaxRows. The oldest history entries are deleted to make room for the new ones.
  • You delete the entire test by setting pingCtlRowStatus to destroy.

Published: 2010-04-27

[an error occurred while processing this directive]