jnxPingProbeHistoryTable
jnxpingProbeHistoryTable, whose object identifier is {jnxPingObjects 4}, contains the history of all ping tests.
The jnxPingProbeHistoryEntry objects are listed in Table 1.
Table 1: jnxPingProbeHistoryEntry
Object | Object Identifier | Description |
|---|---|---|
jnxPingProbeHistoryResponseUs | jnxPingProbeHistoryEntry 1 | The amount of time, in microseconds, from when a probe was sent to when its response was received or when it timed out. The value of this object is reported as 0 when it is not possible to transmit a probe. |
jnxPingProbeHistoryJitterUs | jnxPingProbeHistoryEntry 2 | The time difference, in microseconds, between the maximum and minimum round-trip times. Each history entry provides a running calculation of the jitter (calculated over the current test) at the time a probe was completed. |
jnxPingProbeHistoryResponseEgressUs | jnxPingProbeHistoryEntry 3 | The amount of time, in microseconds, from when a probe was sent to when it was received by destination. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, the value is irrelevant and this object returns 0. |
jnxPingProbeHistoryResponseIngressUs | jnxPingProbeHistoryEntry 4 | The amount of time, in microseconds, from when a probe was sent from the destination to when it was received. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, the value is irrelevant and this object returns 0. |
jnxPingProbeHistoryEgressJitterUs | jnxPingProbeHistoryEntry 5 | The time difference, in microseconds, between the maximum and minimum egress trip times. Each history entry provides a running calculation of the jitter (calculated over the current test) at the time a probe was completed. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, the value is irrelevant and this object returns 0. |
jnxPingProbeHistoryIngressJitterUs | jnxPingProbeHistoryEntry 6 | The time difference, in microseconds, between the maximum and minimum ingress trip times. Each history entry provides a running calculation of the jitter (calculated over the current test) at the time a probe was completed. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, the value is irrelevant and this object returns 0. |
