All MIBs › JUNIPER-PING-MIB
Organization: Juniper Networks, Inc.
Last Updated: 2011--0-9-
Category: Vendor: Juniper
Description: Juniper Networks MIB for configuring and executing ICMP ping connectivity tests and reporting results on Juniper platforms.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is JUNIPER-PING-MIB?
JUNIPER-PING-MIB is a Juniper Networks enterprise MIB implementing Juniper-specific extensions to the standard IETF PING-MIB (DISMAN-PING-MIB), letting an SNMP manager configure and run ICMP ping connectivity tests from a Juniper device and read back the results. It exposes a ping control table defining test parameters such as owner, test name, source interface/routing instance, and threshold values for round-trip time, RTT standard deviation, jitter, and egress time. Its monitoring purpose is network reachability and path-performance status rather than hardware sensors: confirming a remote target is reachable and that latency/jitter stay within acceptable bounds, with configurable thresholds that can drive alerting when a path degrades. It explicitly builds on and shares data model concepts with the standard mib-2 pingMIB (DISMAN-PING-MIB). It is deployed on Juniper routers used as active-testing endpoints for network performance monitoring in service-provider or enterprise WANs. Engineers can download the JUNIPER-PING-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-PING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Juniper Networks routers
Monitoring Examples
An administrator configures a test in jnxPingCtlTable (jnxPingCtlEntry), setting jnxPingCtlTestName, jnxPingCtlIfName, and jnxPingCtlRoutingInstanceName to source the ping from a specific VRF, then sets jnxPingCtlRttThreshold and jnxPingCtlRttJitterThreshold to define acceptable latency variation. If measured round-trip time or jitter exceeds jnxPingCtlRttThreshold/jnxPingCtlRttJitterThreshold, or jnxPingCtlEgressTimeThreshold is crossed, the test flags the path as degraded, which an operator uses to detect a congested or failing WAN link before customer traffic is impacted. jnxPingCtlOwnerIndex lets multiple test owners run concurrent tests without collision.
What Can Be Monitored
- ping/RTT test configuration
- round-trip time vs threshold
- RTT jitter/standard deviation
- egress time threshold
- per-routing-instance test source
This MIB depends on
Related MIBs
Imported Objects
From DISMAN-PING-MIB
| OperationResponseStatus | |
| pingCtlTargetAddress | OBJECT-TYPE |
| pingCtlTargetAddressType | OBJECT-TYPE |
| pingProbeHistoryEntry | OBJECT-TYPE |
| pingResultsAverageRtt | OBJECT-TYPE |
| pingResultsEntry | OBJECT-TYPE |
| pingResultsIpTargetAddress | OBJECT-TYPE |
| pingResultsIpTargetAddressType | OBJECT-TYPE |
| pingResultsLastGoodProbe | OBJECT-TYPE |
| pingResultsMaxRtt | OBJECT-TYPE |
| pingResultsMinRtt | OBJECT-TYPE |
| pingResultsOperStatus | OBJECT-TYPE |
| pingResultsProbeResponses | OBJECT-TYPE |
| pingResultsRttSumOfSquares | OBJECT-TYPE |
| pingResultsSentProbes | OBJECT-TYPE |
From IF-MIB
| InterfaceIndexOrZero |
From INET-ADDRESS-MIB
| InetPortNumber |
From JUNIPER-SMI
| jnxMibs | OBJECT-IDENTITY |
| jnxPingNotifications | OBJECT-IDENTITY |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DateAndTime | |
| DisplayString | |
| TruthValue |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| U32 jnxPingCtlEgressJitterThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.12 | Unsigned32 | read-create | The maximum allowed jitter in the egress trip time over the course of any test. Jitter is defined as the difference between the maximum and minimum egress trip times measured over the course of a single test (jnxPingResultsMaxSrcDstt minus jnxPingResultsMinSrcDstt). If the measured jitter exceeds this threshold, a jnxPingEgressJitterThresholdExceeded trap will be sent. This applies only if the probe type (pingCtlType) provides one way delay measurements. Currently jnxPingIcmpTimeStamp is the only supported probe type with this property. |
| U32 jnxPingCtlEgressStdDevThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.11 | Unsigned32 | read-create | The maximum egress trip time standard deviation allowed over the course of any test. If the calculated standard deviation of the egress trip time at the end of any test exceeds this threshold, a jnxPingEgressStdDevThresholdExceeded trap will be sent. This applies only if the probe type (pingCtlType) provides one way delay measurements. Currently jnxPingIcmpTimeStamp is the only supported probe type with this property. |
| U32 jnxPingCtlEgressTimeThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.10 | Unsigned32 | read-create | Maximum egress trip time allowed. If this threshold is crossed by any probe, a jnxPingEgressThresholdExceeded trap will be sent. This applies only if the probe type (pingCtlType) provides one way delay measurements. Currently jnxPingIcmpTimeStamp is the only supported probe type with this property. |
| jnxPingCtlEntry | 1.3.6.1.4.1.2636.3.7.1.2.1 | not-accessible | Defines an entry in the jnxPingCtlTable. This essentially augments the pingCtlTable with additional objects. | |
| T/F jnxPingCtlEXseriesHWTimeStamp | 1.3.6.1.4.1.2636.3.7.1.2.1.22 | TruthValue | read-create | Use to enable the RPM Hardware Timestamp feature on EX-series switches. For thoses, this object must have the value: false. |
| STR jnxPingCtlIfName | 1.3.6.1.4.1.2636.3.7.1.2.1.3 | DisplayString | read-create | Setting this object to an interface name prior to starting a remote ping operation directs the ping probes to be transmitted over the specified interface. To specify the interface index instead, see pingCtlIfIndex. The interface name must be specified under interfaces statement of the JUNOS configuration. A zero length string value for this object means that this option is not enabled. The following values may be set simultaneously, however, only one value is used. The precedence order is a follows: pingCtlIfIndex (see pingCtlTable in pingMIB) jnxPingCtlIfName jnxPingCtlRoutingIfIndex (deprecated) jnxPingCtlRoutingIfName (deprecated) jnxPingCtlRoutingInstanceName |
| U32 jnxPingCtlIngressJitterThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.15 | Unsigned32 | read-create | The maximum allowed jitter in the ingress trip time over the course of any test. Jitter is defined as the difference between the maximum and minimum ingress trip times measured over the course of a single test (jnxPingResultsMaxDstSrct minus jnxPingResultsMinDstSrct). If the measured jitter exceeds this threshold, a jnxPingIngressJitterThresholdExceeded trap will be sent. This applies only if the probe type (pingCtlType) provides one way delay measurements. Currently jnxPingIcmpTimeStamp is the only supported probe type with this property. |
| U32 jnxPingCtlIngressStddevThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.14 | Unsigned32 | read-create | The maximum ingress trip time standard deviation allowed over the course of any test. If the calculated standard deviation of the ingress trip time at the end of any test exceeds this threshold, a jnxPingIngressStddevThresholdExceeded trap will be sent. This applies only if the probe type (pingCtlType) provides one way delay measurements. Currently jnxPingIcmpTimeStamp is the only supported probe type with this property. |
| U32 jnxPingCtlIngressTimeThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.13 | Unsigned32 | read-create | Maximum ingress trip time allowed. If this threshold is crossed by any probe, a jnxPingIngressThresholdExceeded trap will be sent. This applies only if the probe type (pingCtlType) provides one way delay measurements. Currently jnxPingIcmpTimeStamp is the only supported probe type with this property. |
| T/F jnxPingCtlJseriesHWTimeStamp | 1.3.6.1.4.1.2636.3.7.1.2.1.18 | TruthValue | read-create | Use to enable the RPM Hardware Timestamp feature on J-series routers. For M/T series routers, use the jnxPingCtlIfName and pingCtlByPassRouteTable objects to redirect probes to the AS Pic. For those routers, this object must have the value: false. |
| U32 jnxPingCtlMovAvgSize | 1.3.6.1.4.1.2636.3.7.1.2.1.20 | Unsigned32 | read-create | The Juniper RPM feature maintains a set of the most recent probe measurements & provides the same calculations over that collection as provided over a test (ie, average, standard deviation, etc). This data is available via the jnx-rpm mib or via the CLI/XML. The number of samples maintained in this moving collection is specified by this object. This value must be less than the number of samples maintained in the history table (ie, pingCtlMaxRows). |
| T/F jnxPingCtlMXseriesHWTimeStamp | 1.3.6.1.4.1.2636.3.7.1.2.1.21 | TruthValue | read-create | Use to enable the RPM Hardware Timestamp feature on MX-series routers. For M/T series routers, use the jnxPingCtlIfName and pingCtlByPassRouteTable objects to redirect probes to the AS PIC. For those routers, this object must have the value: false. |
| T/F jnxPingCtlOneWayHWTimeStamp | 1.3.6.1.4.1.2636.3.7.1.2.1.19 | TruthValue | read-create | Use this object to enable Hardware Timestamp-based one-way measurements. If this object is not enabled (ie, set to true), no Hardware Timestamp based one way measurements or calculations will be performed for this control entry. This object applies to all Juniper routers. Note, due to clock synchronization artifacts, many one-way jitter measurements & calculations may include signifacant variations, in some cases orders of magnitude greater than the round trip times. |
| STR jnxPingCtlOwnerIndex | 1.3.6.1.4.1.2636.3.7.1.2.1.1 | SnmpAdminString | not-accessible | To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible. |
| NUM jnxPingCtlRoutingIfIndex | 1.3.6.1.4.1.2636.3.7.1.2.1.4 | InterfaceIndexOrZero | read-create | Use this option to specify the routing instance used when directing outgoing ping packets. The interface ifIndex specified should be in the desired routing instance table. The interface specified will not necessarily be the interface packets are transmitted on. By default, the source address of the packets will be set to the address of the interface chosen. pingCtlSourceAddress should be used to override the choice for source address if necessary. A value of zero for this object means that this option is not enabled. NOTE: deprecated by jnxPingCtlRoutingInstanceName |
| STR jnxPingCtlRoutingIfName | 1.3.6.1.4.1.2636.3.7.1.2.1.5 | DisplayString | read-create | Use this option to specify the routing instance used when directing outgoing ping packets. The interface name specified should be in the desired routing instance table. The interface specified will not necessarily be the interface packets are transmitted on. By default, the source address of the packets will be set to the address of the interface chosen. pingCtlSourceAddress should be used to override the choice for source address if necessary. NOTE: deprecated by jnxPingCtlRoutingInstanceName |
| STR jnxPingCtlRoutingInstanceName | 1.3.6.1.4.1.2636.3.7.1.2.1.6 | DisplayString | read-create | Use this option to specify the name of the routing instance used when directing outgoing ping packets. The instance name specified must be configured under routing-instances of the JUNOS configuration. |
| U32 jnxPingCtlRttJitterThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.9 | Unsigned32 | read-create | The maximum allowed jitter in the round trip time over the course of any test. Jitter is defined as the difference between the maximum and minimum round trip times measured over the course of a single test (jnxPingResultsMaxRttUs minus jnxPingResultsMinRttUs). If the measured jitter exceeds this threshold, a jnxPingRttJitterThresholdExceeded trap will be sent. |
| U32 jnxPingCtlRttStdDevThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.8 | Unsigned32 | read-create | The maximum round trip time standard deviation allowed over the course of any test. If the calculated standard deviation of the round trip time at the end of any test exceeds this threshold, a jnxPingRttStdDevThresholdExceeded trap will be sent. |
| U32 jnxPingCtlRttThreshold | 1.3.6.1.4.1.2636.3.7.1.2.1.7 | Unsigned32 | read-create | Maximum round trip time allowed. If this threshold is crossed by any probe, a jnxPingRttThresholdExceeded trap will be sent. |
| jnxPingCtlTable | 1.3.6.1.4.1.2636.3.7.1.2 | not-accessible | Defines the jnxPing Control Table for providing enterprise specific options to the corresponding pingCtlTable entry. | |
| INE jnxPingCtlTargetPort | 1.3.6.1.4.1.2636.3.7.1.2.1.17 | InetPortNumber | read-create | The target UDP/TCP port used by the probe. When ICMP ping is used, jnxPingCtlTargetPort value will be shown as 0. |
| STR jnxPingCtlTestName | 1.3.6.1.4.1.2636.3.7.1.2.1.2 | SnmpAdminString | not-accessible | The name of the ping test. This is locally unique, within the scope of an pingCtlOwnerIndex. |
| BIT jnxPingCtlTrapGeneration | 1.3.6.1.4.1.2636.3.7.1.2.1.16 | Bits | read-create | The value of this object determines when and if to generate a notification for this entry: rttThreshold(0) - Generate a jnxPingRttThresholdExceeded notification when the configured rtt threshold is exceeded. rttStdDevThreshold(1) - Generate a jnxPingRttStdDevThresholdExceeded notification when the configured rtt standard deviation threshold is exceeded. rttJitterThreshold(2) - Generate a jnxPingRttJitterThresholdExceeded notification when the configured rtt jitter threshold is exceeded. egressThreshold(3) - Generate a jnxPingEgressThresholdExceeded notification when the configured egress threshold is exceeded. This applies only if the probe type supports one way measurments. egressStdDevThreshold(4) - Generate a jnxPingEgressStdDevThresholdExceeded notification when the configured egress standard deviation threshold is exceeded. This applies only if the probe type supports one way measurments. egressJitterThreshold(5) - Generate a jnxPingEgressJitterThresholdExceeded notification when the configured egress jitter threshold is exceeded. This applies only if the probe type supports one way measurments. ingressThreshold(6) - Generate a jnxPingIngressThresholdExceeded notification when the configured ingress threshold is exceeded. This applies only if the probe type supports one way measurments. ingressStdDevThreshold(7) - Generate a jnxPingIngressStdDevThresholdExceeded notification when the configured ingress standard deviation threshold is exceeded. This applies only if the probe type supports one way measurments. ingressJitterThreshold(8) - Generate a jnxPingIngressJitterThresholdExceeded notification when the configured ingress jitter threshold is exceeded. This applies only if the probe type supports one way measurments. The value of this object defaults to zero, indicating that none of the above options have been selected. |
| jnxPingDnsQuery | 1.3.6.1.4.1.2636.3.7.2.4 | Indicates that an implementation is using a DNS query to calculate a round trip time. | ||
| NTF jnxPingEgressJitterThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.6 | This notification is generated when the egress time jitter (jnxPingResultsMaxEgressUs minus jnxPingResultsMinEgressUs) exceeds the configured threshold (jnxPingCtlEgressJitterThreshold) and the egressJitterThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| NTF jnxPingEgressStdDevThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.5 | This notification is generated when the standard deviation of the egress time (jnxPingResultsStddevEgressUs) exceeds the configured threshold (jnxPingCtlEgressStdDevThreshold) and the egressStdDevThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| NTF jnxPingEgressThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.4 | This notification is generated when the egress time (jnxPingResultsEgressUs) exceeds the configured threshold (jnxPingCtlEgressTimeThreshold) and the egressThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| jnxPingHttpGet | 1.3.6.1.4.1.2636.3.7.2.2 | Indicates that an implementation is using an HTTP GET query to calculate a round trip time. | ||
| jnxPingHttpGetMetadata | 1.3.6.1.4.1.2636.3.7.2.3 | Indicates that an implementation is using an HTTP GET Metadata query to calculate a round trip time. | ||
| jnxPingIcmpTimeStamp | 1.3.6.1.4.1.2636.3.7.2.1 | Indicates that an implementation is using the Internet Control Message Protocol (ICMP) 'TimeStamp' facility. This probe-type provides egress and ingress delay measurements. | ||
| jnxPingImplementationTypeDomains | 1.3.6.1.4.1.2636.3.7.2 | |||
| NTF jnxPingIngressJitterThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.9 | This notification is generated when the ingress time jitter (jnxPingResultsMaxIngressUs minus jnxPingResultsMinIngressUs) exceeds the configured threshold (jnxPingCtlIngressJitterThreshold) and the ingressJitterThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| NTF jnxPingIngressStddevThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.8 | This notification is generated when the standard deviation of the ingress time (jnxPingResultsStddevIngressUs) exceeds the configured threshold (jnxPingCtlIngressStddevThreshold) and the ingressStdDevThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| NTF jnxPingIngressThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.7 | This notification is generated when the ingress time (jnxPingResultsIngressUs) exceeds the configured threshold (jnxPingCtlIngressTimeThreshold) and the ingressThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| U32 jnxPingLastTestResultAvgEgressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.10 | Unsigned32 | read-only | The average of the egress trip delays measured over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultAvgIngressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.14 | Unsigned32 | read-only | The average of the ingress trip delays measured over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultAvgRttUs | 1.3.6.1.4.1.2636.3.7.1.5.1.6 | Unsigned32 | read-only | The average of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds. |
| jnxPingLastTestResultEntry | 1.3.6.1.4.1.2636.3.7.1.5.1 | not-accessible | Each entry provides most recently completed test result. | |
| U32 jnxPingLastTestResultMaxEgressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.9 | Unsigned32 | read-only | The maximum of the egress trip delays measured over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultMaxIngressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.13 | Unsigned32 | read-only | The maximum of the ingress trip delays measured over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultMaxRttUs | 1.3.6.1.4.1.2636.3.7.1.5.1.5 | Unsigned32 | read-only | The maximum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds. |
| U32 jnxPingLastTestResultMinEgressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.8 | Unsigned32 | read-only | The minimum of the egress trip delays measured over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultMinIngressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.12 | Unsigned32 | read-only | The minimum of the ingress trip delays measured for over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultMinRttUs | 1.3.6.1.4.1.2636.3.7.1.5.1.4 | Unsigned32 | read-only | The minimum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds. |
| U32 jnxPingLastTestResultPeakToPeakJitterEgressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.17 | Unsigned32 | read-only | This indicates the difference between the min and max egress trip delays over the course of the last completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultPeakToPeakJitterIngressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.18 | Unsigned32 | read-only | This indicates the difference between the min and max ingress trip delays over the course of the last completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultPeakToPeakJitterRttUs | 1.3.6.1.4.1.2636.3.7.1.5.1.16 | Unsigned32 | read-only | This indicates the difference between the min and max delays over the course of the last completed test. Measured in microseconds. |
| U32 jnxPingLastTestResultProbeResponses | 1.3.6.1.4.1.2636.3.7.1.5.1.1 | Unsigned32 | read-only | Number of responses received in the most recently completed test. |
| U32 jnxPingLastTestResultSentProbes | 1.3.6.1.4.1.2636.3.7.1.5.1.2 | Unsigned32 | read-only | The value of this object reflects the number of probes sent in the most recently completed test. |
| U32 jnxPingLastTestResultStddevEgressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.11 | Unsigned32 | read-only | The standard deviation of the egress trip delays measured over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultStddevIngressUs | 1.3.6.1.4.1.2636.3.7.1.5.1.15 | Unsigned32 | read-only | The standard deviation of the ingress trip delays measured over all probes during the most recently completed test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingLastTestResultStdDevRttUs | 1.3.6.1.4.1.2636.3.7.1.5.1.7 | Unsigned32 | read-only | The standard deviation of the round trip delays measured during the most recently completed test. Measured in microseconds. |
| U32 jnxPingLastTestResultSumRttUs | 1.3.6.1.4.1.2636.3.7.1.5.1.3 | Unsigned32 | read-only | The sum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds. |
| jnxPingLastTestResultTable | 1.3.6.1.4.1.2636.3.7.1.5 | not-accessible | Stores result of the most recently completed test. Entry corresponding to a test will be created only after completion of first test. | |
| DAT jnxPingLastTestResultTime | 1.3.6.1.4.1.2636.3.7.1.5.1.19 | DateAndTime | read-only | Timestamp for when the last test was completed. |
| jnxPingMIB | 1.3.6.1.4.1.2636.3.7 | This is Juniper Networks' implementation of enterprise specific portions of pingMib. Any data stored in this MIB has directly related entries in mib-2, pingMIB. | ||
| jnxPingNotificationPrefix | 1.3.6.1.4.1.2636.4.9.0 | All Juniper-specific ping notifications are registered under this branch. | ||
| jnxPingNtpQuery | 1.3.6.1.4.1.2636.3.7.2.5 | Indicates that an implementation is using an NTP query to calculate a round trip time. | ||
| jnxPingObjects | 1.3.6.1.4.1.2636.3.7.1 | |||
| U32 jnxPingProbeHistoryEgressJitterUs | 1.3.6.1.4.1.2636.3.7.1.4.1.5 | Unsigned32 | read-only | The time difference measured 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 will return 0. |
| jnxPingProbeHistoryEntry | 1.3.6.1.4.1.2636.3.7.1.4.1 | not-accessible | Each entry provides additional ping history data. | |
| U32 jnxPingProbeHistoryIngressJitterUs | 1.3.6.1.4.1.2636.3.7.1.4.1.6 | Unsigned32 | read-only | The time difference measured 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 will return 0. |
| U32 jnxPingProbeHistoryJitterUs | 1.3.6.1.4.1.2636.3.7.1.4.1.2 | Unsigned32 | read-only | The time difference measured 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. |
| U32 jnxPingProbeHistoryResponseEgressUs | 1.3.6.1.4.1.2636.3.7.1.4.1.3 | Unsigned32 | read-only | The amount of time measured 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 will return 0. |
| U32 jnxPingProbeHistoryResponseIngressUs | 1.3.6.1.4.1.2636.3.7.1.4.1.4 | Unsigned32 | read-only | The amount of time measured 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 will return 0. |
| U32 jnxPingProbeHistoryResponseUs | 1.3.6.1.4.1.2636.3.7.1.4.1.1 | Unsigned32 | read-only | The amount of time measured 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. |
| jnxPingProbeHistoryTable | 1.3.6.1.4.1.2636.3.7.1.4 | not-accessible | Augments the pingHistoryTable with additional data. | |
| U32 jnxPingResultsAvgEgressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.10 | Unsigned32 | read-only | The average of the egress trip delays measured over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsAvgIngressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.15 | Unsigned32 | read-only | The average of the ingress trip delays measured over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsAvgRttUs | 1.3.6.1.4.1.2636.3.7.1.3.1.5 | Unsigned32 | read-only | The average of the round trip delays measured for all the probes during this test. Measured in microseconds. |
| U32 jnxPingResultsEgressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.7 | Unsigned32 | read-only | The egress trip delays measured for the most recent successful probe during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| jnxPingResultsEntry | 1.3.6.1.4.1.2636.3.7.1.3.1 | not-accessible | Each entry provides additional ping test results. | |
| U32 jnxPingResultsIngressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.12 | Unsigned32 | read-only | The ingress trip delays measured for the most recent successful probe during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsJitterEgressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.18 | Unsigned32 | read-only | The jitter of the egress trip delays measured for all the probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsJitterIngressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.19 | Unsigned32 | read-only | The jitter of the ingress trip delays measured for all the probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsJitterRttUs | 1.3.6.1.4.1.2636.3.7.1.3.1.17 | Unsigned32 | read-only | The jitter of the round trip delays measured for all the probes during this test. Measured in microseconds. |
| U32 jnxPingResultsMaxEgressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.9 | Unsigned32 | read-only | The maximum of the egress trip delays measured over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsMaxIngressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.14 | Unsigned32 | read-only | The maximum of the ingress trip delays measured over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsMaxRttUs | 1.3.6.1.4.1.2636.3.7.1.3.1.4 | Unsigned32 | read-only | The maximum of the round trip delays measured for all the probes during this test. Measured in microseconds. |
| U32 jnxPingResultsMinEgressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.8 | Unsigned32 | read-only | The minimum of the egress trip delays measured over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsMinIngressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.13 | Unsigned32 | read-only | The minimum of the ingress trip delays measured for over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsMinRttUs | 1.3.6.1.4.1.2636.3.7.1.3.1.3 | Unsigned32 | read-only | The minimum of the round trip delays measured for all the probes during this test. Measured in microseconds. |
| STR jnxPingResultsOwnerIndex | 1.3.6.1.4.1.2636.3.7.1.3.1.22 | SnmpAdminString | read-only | This object has the same value as pingCtlOwnerIndex and is provided for those applications that are unable to parse the value of pingCtlOwnerIndex from the instance portion of the OIDs belonging to this table. |
| U32 jnxPingResultsRttUs | 1.3.6.1.4.1.2636.3.7.1.3.1.1 | Unsigned32 | read-only | The round trip delays measured for the most recent successful probe during this test. Measured in microseconds. |
| OPE jnxPingResultsStatus | 1.3.6.1.4.1.2636.3.7.1.3.1.20 | OperationResponseStatus | read-only | The result of the most recent probe. |
| U32 jnxPingResultsStddevEgressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.11 | Unsigned32 | read-only | The standard deviation of the egress trip delays measured over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsStddevIngressUs | 1.3.6.1.4.1.2636.3.7.1.3.1.16 | Unsigned32 | read-only | The standard deviation of the ingress trip delays measured over all probes during this test. Measured in microseconds. This applies only if the probe type (pingCtlType) provides one-way delay measurements. For all other probe types, their values are irrelevant and will return 0. |
| U32 jnxPingResultsStdDevRttUs | 1.3.6.1.4.1.2636.3.7.1.3.1.6 | Unsigned32 | read-only | The standard deviation of the round trip delays measured during this test. Measured in microseconds. |
| U32 jnxPingResultsSumRttUs | 1.3.6.1.4.1.2636.3.7.1.3.1.2 | Unsigned32 | read-only | The sum of the round trip delays measured for all the probes during this test. Measured in microseconds. |
| jnxPingResultsTable | 1.3.6.1.4.1.2636.3.7.1.3 | not-accessible | Augments the pingResultsTable with additional data. | |
| STR jnxPingResultsTestName | 1.3.6.1.4.1.2636.3.7.1.3.1.23 | SnmpAdminString | read-only | This object has the same value as pingCtlTestName and is provided for those applications that are unable to parse the value of pingCtlTestName from the instance portion of the OIDs belonging to this table. |
| DAT jnxPingResultsTime | 1.3.6.1.4.1.2636.3.7.1.3.1.21 | DateAndTime | read-only | Timestamp for when the most recent probe result was determined. |
| NTF jnxPingRttJitterThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.3 | This notification is generated when the round trip time jitter (jnxPingResultsMaxRttUs minus jnxPingResultsMinRttUs) exceeds the configured threshold (jnxPingCtlRttJitterThreshold) and the rttJitterThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| NTF jnxPingRttStdDevThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.2 | This notification is generated when the standard deviation of the round trip time (jnxPingResultsStdDevRttUs) exceeds the configured threshold (jnxPingCtlRttStdDevThreshold) and the rttStdDevThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| NTF jnxPingRttThresholdExceeded | 1.3.6.1.4.1.2636.4.9.0.1 | This notification is generated when the round trip time (jnxPingCtlRttThreshold) exceeds the configured threshold (jnxPingCtlRttThreshold) and the rttThreshold bit is set in jnxPingCtlTrapGeneration. | ||
| jnxPingUdpTimestamp | 1.3.6.1.4.1.2636.3.7.2.6 | Indicates that an implementation is using a UDP timestamp query to calculate a round trip time. This probe-type provides egress and ingress delay measurements |
RFC description
Juniper-specific extensions to standard ping MIB for monitoring ICMP echo requests and network reachability testing with timestamps and RTT measurements.
Start monitoring Juniper routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.