JUNIPER-PING-MIB: View SNMP OID List / Download MIB

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.

Defines the jnxPing Control Table for providing enterprise specific options to the corresponding pingCtlTable entry.

Defines an entry in the jnxPingCtlTable. This essentially augments the pingCtlTable with additional objects.

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.

The name of the ping test. This is locally unique, within the scope of an pingCtlOwnerIndex.

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

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

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

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.

Maximum round trip time allowed. If this threshold is crossed by any probe, a jnxPingRttThresholdExceeded trap will be sent.

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.

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.

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.

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.

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.

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.

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.

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.

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. Bits: 'egressThreshold': 3, 'rttThreshold': 0, 'ingressThreshold': 6, 'egressStdDevThreshold': 4, 'rttStdDevThreshold': 1, 'ingressJitterThreshold': 8, 'rttJitterThreshold': 2, 'ingressStdDevThreshold': 7, 'egressJitterThreshold': 5.

The target UDP/TCP port used by the probe. When ICMP ping is used, jnxPingCtlTargetPort value will be shown as 0.

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.

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.

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).

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.

Use to enable the RPM Hardware Timestamp feature on EX-series switches. For thoses, this object must have the value: false.

Augments the pingResultsTable with additional data.

Each entry provides additional ping test results.

The round trip delays measured for the most recent successful probe during this test. Measured in microseconds.

The sum of the round trip delays measured for all the probes during this test. Measured in microseconds.

The minimum of the round trip delays measured for all the probes during this test. Measured in microseconds.

The maximum of the round trip delays measured for all the probes during this test. Measured in microseconds.

The average of the round trip delays measured for all the probes during this test. Measured in microseconds.

The standard deviation of the round trip delays measured during this test. Measured in microseconds.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

The jitter of the round trip delays measured for all the probes during this test. Measured in microseconds.

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.

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.

The result of the most recent probe.

Timestamp for when the most recent probe result was determined.

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.

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.

Augments the pingHistoryTable with additional data.

Each entry provides additional ping history data.

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.

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.

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.

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.

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.

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.

Stores result of the most recently completed test. Entry corresponding to a test will be created only after completion of first test.

Each entry provides most recently completed test result.

Number of responses received in the most recently completed test.

The value of this object reflects the number of probes sent in the most recently completed test.

The sum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.

The minimum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.

The maximum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.

The average of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.

The standard deviation of the round trip delays measured during the most recently completed test. Measured in microseconds.

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.

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.

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.

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.

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.

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.

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.

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.

This indicates the difference between the min and max delays over the course of the last completed test. Measured in microseconds.

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.

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.

Timestamp for when the last test was completed.

Indicates that an implementation is using the Internet Control Message Protocol (ICMP) 'TimeStamp' facility. This probe-type provides egress and ingress delay measurements.

Indicates that an implementation is using an HTTP GET query to calculate a round trip time.

Indicates that an implementation is using an HTTP GET Metadata query to calculate a round trip time.

Indicates that an implementation is using a DNS query to calculate a round trip time.

Indicates that an implementation is using an NTP query to calculate a round trip time.

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

All Juniper-specific ping notifications are registered under this branch.

This notification is generated when the round trip time (jnxPingCtlRttThreshold) exceeds the configured threshold (jnxPingCtlRttThreshold) and the rttThreshold bit is set in jnxPingCtlTrapGeneration.

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.

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.

This notification is generated when the egress time (jnxPingResultsEgressUs) exceeds the configured threshold (jnxPingCtlEgressTimeThreshold) and the egressThreshold bit is set in jnxPingCtlTrapGeneration.

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.

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.

This notification is generated when the ingress time (jnxPingResultsIngressUs) exceeds the configured threshold (jnxPingCtlIngressTimeThreshold) and the ingressThreshold bit is set in jnxPingCtlTrapGeneration.

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.

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.