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.
jnxPingCtlOwnerIndex
1.3.6.1.4.1.2636.3.7.1.2.1.1
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
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.
jnxPingCtlTestName
1.3.6.1.4.1.2636.3.7.1.2.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
The name of the ping test. This is locally unique, within the scope of an pingCtlOwnerIndex.
jnxPingCtlIfName
1.3.6.1.4.1.2636.3.7.1.2.1.3
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..24) · OCTET STRING · hint 255a
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
jnxPingCtlRoutingIfIndex
1.3.6.1.4.1.2636.3.7.1.2.1.4
InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d
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
jnxPingCtlRoutingIfName
1.3.6.1.4.1.2636.3.7.1.2.1.5
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..24) · OCTET STRING · hint 255a
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
jnxPingCtlRoutingInstanceName
1.3.6.1.4.1.2636.3.7.1.2.1.6
DisplayStringRepresents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
- the use of character codes 0-127 (decimal)
- the graphics characters (32-126) are interpreted as US ASCII
- NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854
- the other 25 codes have no standard interpretation
- the sequence 'CR LF' means newline
- the sequence 'CR NUL' means carriage-return
- an 'LF' not preceded by a 'CR' means moving to the same column on the next line.
- the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..31) · OCTET STRING · hint 255a
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.
jnxPingCtlRttThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.7
Unsigned32 (0..6000000) · microseconds
Maximum round trip time allowed. If this threshold is crossed by any probe, a jnxPingRttThresholdExceeded trap will be sent.
jnxPingCtlRttStdDevThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.8
Unsigned32 (0..6000000) · microseconds
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.
jnxPingCtlRttJitterThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.9
Unsigned32 (0..6000000) · microseconds
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.
jnxPingCtlEgressTimeThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.10
Unsigned32 (0..60000000) · microseconds
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.
jnxPingCtlEgressStdDevThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.11
Unsigned32 (0..60000000) · microseconds
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.
jnxPingCtlEgressJitterThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.12
Unsigned32 (0..60000000) · microseconds
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.
jnxPingCtlIngressTimeThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.13
Unsigned32 (0..60000000) · microseconds
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.
jnxPingCtlIngressStddevThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.14
Unsigned32 (0..60000000) · microseconds
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.
jnxPingCtlIngressJitterThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.15
Unsigned32 (0..60000000) · microseconds
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.
jnxPingCtlTrapGeneration
1.3.6.1.4.1.2636.3.7.1.2.1.16
BITS
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. maxrttThreshold(9) - Generate a jnxPingMaxRttThresholdExceeded notification at the end of test session when rtt of any of the probe exceeds the configured rtt threshold.
jnxPingCtlTargetPort
1.3.6.1.4.1.2636.3.7.1.2.1.17
InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>.
The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (7 | 49152..65535) · Unsigned32 · hint d
The target UDP/TCP port used by the probe. When ICMP ping is used, jnxPingCtlTargetPort value will be shown as 0.
jnxPingCtlJseriesHWTimeStamp
1.3.6.1.4.1.2636.3.7.1.2.1.18
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
jnxPingCtlOneWayHWTimeStamp
1.3.6.1.4.1.2636.3.7.1.2.1.19
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
jnxPingCtlMovAvgSize
1.3.6.1.4.1.2636.3.7.1.2.1.20
Unsigned32
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).
jnxPingCtlMXseriesHWTimeStamp
1.3.6.1.4.1.2636.3.7.1.2.1.21
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
jnxPingCtlEXseriesHWTimeStamp
1.3.6.1.4.1.2636.3.7.1.2.1.22
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Use to enable the RPM Hardware Timestamp feature on EX-series switches. For thoses, this object must have the value: false.
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
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.
pingCtlTestName
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
The name of the ping test. This is locally unique, within the scope of an pingCtlOwnerIndex.
jnxPingResultsRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.1
Unsigned32 · microseconds
The round trip delays measured for the most recent successful probe during this test. Measured in microseconds.
jnxPingResultsSumRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.2
Unsigned32 · microseconds
The sum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsMinRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.3
Unsigned32 · microseconds
The minimum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsMaxRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.4
Unsigned32 · microseconds
The maximum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsAvgRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.5
Unsigned32 · microseconds
The average of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsStdDevRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.6
Unsigned32 · microseconds
The standard deviation of the round trip delays measured during this test. Measured in microseconds.
jnxPingResultsEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.7
Unsigned32 · 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.
jnxPingResultsMinEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.8
Unsigned32 · microseconds
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.
jnxPingResultsMaxEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.9
Unsigned32 · microseconds
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.
jnxPingResultsAvgEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.10
Unsigned32 · microseconds
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.
jnxPingResultsStddevEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.11
Unsigned32 · microseconds
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.
jnxPingResultsIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.12
Unsigned32 · microseconds
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.
jnxPingResultsMinIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.13
Unsigned32 · microseconds
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.
jnxPingResultsMaxIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.14
Unsigned32 · microseconds
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.
jnxPingResultsAvgIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.15
Unsigned32 · microseconds
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.
jnxPingResultsStddevIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.16
Unsigned32 · microseconds
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.
jnxPingResultsJitterRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.17
Unsigned32 · microseconds
The jitter of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsJitterEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.18
Unsigned32 · 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.
jnxPingResultsJitterIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.19
Unsigned32 · microseconds
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.
jnxPingResultsStatus
1.3.6.1.4.1.2636.3.7.1.3.1.20
OperationResponseStatus1 = responseReceived2 = unknown3 = internalError4 = requestTimedOut5 = unknownDestinationAddress6 = noRouteToTarget7 = interfaceInactiveToTarget8 = arpFailure9 = maxConcurrentLimitReached10 = unableToResolveDnsName11 = invalidHostAddressUsed to report the result of an operation:
responseReceived(1) - Operation completes successfully. unknown(2) - Operation failed due to unknown error. internalError(3) - An implementation detected an error in its own processing that caused an operation to fail. requestTimedOut(4) - Operation failed to receive a valid reply within the time limit imposed on it. unknownDestinationAddress(5) - Invalid destination address. noRouteToTarget(6) - Could not find a route to target. interfaceInactiveToTarget(7) - The interface to be used in sending a probe is inactive without an alternate route existing. arpFailure(8) - Unable to resolve a target address to a media specific address. maxConcurrentLimitReached(9) - The maximum number of concurrent active operations would have been exceeded if the corresponding operation was allowed. unableToResolveDnsName(10) - The DNS name specified was unable to be mapped to an IP address. invalidHostAddress(11) - The IP address for a host has been determined to be invalid. Examples of this are broadcast or multicast addresses. · Integer32
The result of the most recent probe.
jnxPingResultsTime
1.3.6.1.4.1.2636.3.7.1.3.1.21
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Timestamp for when the most recent probe result was determined.
jnxPingResultsOwnerIndex
1.3.6.1.4.1.2636.3.7.1.3.1.22
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
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.
jnxPingResultsTestName
1.3.6.1.4.1.2636.3.7.1.3.1.23
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
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.
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
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.
pingCtlTestName
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t
The name of the ping test. This is locally unique, within the scope of an pingCtlOwnerIndex.
pingProbeHistoryIndex
Unsigned32 (1..4294967295)
An entry in this table is created when the result of a ping probe is determined. The initial 2 instance identifier index values identify the pingCtlEntry that a probe result (pingProbeHistoryEntry) belongs to.
An implementation MUST start assigning pingProbeHistoryIndex values at 1 and wrap after exceeding the maximum possible value as defined by the limit of this object ('ffffffff'h).
jnxPingProbeHistoryResponseUs
1.3.6.1.4.1.2636.3.7.1.4.1.1
Unsigned32 · microseconds
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.
jnxPingProbeHistoryJitterUs
1.3.6.1.4.1.2636.3.7.1.4.1.2
Unsigned32 · microseconds
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.
jnxPingProbeHistoryResponseEgressUs
1.3.6.1.4.1.2636.3.7.1.4.1.3
Unsigned32 · microseconds
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.
jnxPingProbeHistoryResponseIngressUs
1.3.6.1.4.1.2636.3.7.1.4.1.4
Unsigned32 · microseconds
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.
jnxPingProbeHistoryEgressJitterUs
1.3.6.1.4.1.2636.3.7.1.4.1.5
Unsigned32 · microseconds
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.
jnxPingProbeHistoryIngressJitterUs
1.3.6.1.4.1.2636.3.7.1.4.1.6
Unsigned32 · microseconds
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.
jnxPingLastTestResultTable
1.3.6.1.4.1.2636.3.7.1.5
Index: jnxPingCtlOwnerIndex · jnxPingCtlTestName
Stores result of the most recently completed test. Entry corresponding to a test will be created only after completion of first test.
jnxPingLastTestResultProbeResponses
1.3.6.1.4.1.2636.3.7.1.5.1.1
Unsigned32 · responses
Number of responses received in the most recently completed test.
jnxPingLastTestResultSentProbes
1.3.6.1.4.1.2636.3.7.1.5.1.2
Unsigned32 · probes
The value of this object reflects the number of probes sent in the most recently completed test.
jnxPingLastTestResultSumRttUs
1.3.6.1.4.1.2636.3.7.1.5.1.3
Unsigned32 · microseconds
The sum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.
jnxPingLastTestResultMinRttUs
1.3.6.1.4.1.2636.3.7.1.5.1.4
Unsigned32 · microseconds
The minimum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.
jnxPingLastTestResultMaxRttUs
1.3.6.1.4.1.2636.3.7.1.5.1.5
Unsigned32 · microseconds
The maximum of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.
jnxPingLastTestResultAvgRttUs
1.3.6.1.4.1.2636.3.7.1.5.1.6
Unsigned32 · microseconds
The average of the round trip delays measured for all the probes during the most recently completed test. Measured in microseconds.
jnxPingLastTestResultStdDevRttUs
1.3.6.1.4.1.2636.3.7.1.5.1.7
Unsigned32 · microseconds
The standard deviation of the round trip delays measured during the most recently completed test. Measured in microseconds.
jnxPingLastTestResultMinEgressUs
1.3.6.1.4.1.2636.3.7.1.5.1.8
Unsigned32 · 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.
jnxPingLastTestResultMaxEgressUs
1.3.6.1.4.1.2636.3.7.1.5.1.9
Unsigned32 · microseconds
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.
jnxPingLastTestResultAvgEgressUs
1.3.6.1.4.1.2636.3.7.1.5.1.10
Unsigned32 · microseconds
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.
jnxPingLastTestResultStddevEgressUs
1.3.6.1.4.1.2636.3.7.1.5.1.11
Unsigned32 · microseconds
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.
jnxPingLastTestResultMinIngressUs
1.3.6.1.4.1.2636.3.7.1.5.1.12
Unsigned32 · microseconds
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.
jnxPingLastTestResultMaxIngressUs
1.3.6.1.4.1.2636.3.7.1.5.1.13
Unsigned32 · microseconds
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.
jnxPingLastTestResultAvgIngressUs
1.3.6.1.4.1.2636.3.7.1.5.1.14
Unsigned32 · microseconds
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.
jnxPingLastTestResultStddevIngressUs
1.3.6.1.4.1.2636.3.7.1.5.1.15
Unsigned32 · microseconds
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.
jnxPingLastTestResultPeakToPeakJitterRttUs
1.3.6.1.4.1.2636.3.7.1.5.1.16
Unsigned32 · microseconds
This indicates the difference between the min and max delays over
the course of the last completed test. Measured in microseconds.
jnxPingLastTestResultPeakToPeakJitterEgressUs
1.3.6.1.4.1.2636.3.7.1.5.1.17
Unsigned32 · 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.
jnxPingLastTestResultPeakToPeakJitterIngressUs
1.3.6.1.4.1.2636.3.7.1.5.1.18
Unsigned32 · microseconds
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.
jnxPingLastTestResultTime
1.3.6.1.4.1.2636.3.7.1.5.1.19
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Timestamp for when the last test was completed.
Trap details
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.3
Unsigned32 · microseconds
The minimum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsMaxRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.4
Unsigned32 · microseconds
The maximum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsAvgRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.5
Unsigned32 · microseconds
The average of the round trip delays measured for all the probes during this test. Measured in microseconds.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsRttSumOfSquares
1.3.6.1.2.1.80.1.3.1.9
Unsigned32 · milliseconds
This object contains the sum of the squares for all ping responses received. Its purpose is to enable standard deviation calculation. The value of this object MUST be reported as 0 when no ping responses have been received.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlRttThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.7
Unsigned32 (0..6000000) · microseconds
Maximum round trip time allowed. If this threshold is crossed by any probe, a jnxPingRttThresholdExceeded trap will be sent.
jnxPingResultsRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.1
Unsigned32 · microseconds
The round trip delays measured for the most recent successful probe during this test. Measured in microseconds.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.3
Unsigned32 · microseconds
The minimum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsMaxRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.4
Unsigned32 · microseconds
The maximum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsAvgRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.5
Unsigned32 · microseconds
The average of the round trip delays measured for all the probes during this test. Measured in microseconds.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsRttSumOfSquares
1.3.6.1.2.1.80.1.3.1.9
Unsigned32 · milliseconds
This object contains the sum of the squares for all ping responses received. Its purpose is to enable standard deviation calculation. The value of this object MUST be reported as 0 when no ping responses have been received.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlRttStdDevThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.8
Unsigned32 (0..6000000) · microseconds
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.
jnxPingResultsStdDevRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.6
Unsigned32 · microseconds
The standard deviation of the round trip delays measured during this test. Measured in microseconds.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.3
Unsigned32 · microseconds
The minimum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsMaxRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.4
Unsigned32 · microseconds
The maximum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsAvgRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.5
Unsigned32 · microseconds
The average of the round trip delays measured for all the probes during this test. Measured in microseconds.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsRttSumOfSquares
1.3.6.1.2.1.80.1.3.1.9
Unsigned32 · milliseconds
This object contains the sum of the squares for all ping responses received. Its purpose is to enable standard deviation calculation. The value of this object MUST be reported as 0 when no ping responses have been received.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlRttJitterThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.9
Unsigned32 (0..6000000) · microseconds
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.
jnxPingResultsJitterRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.17
Unsigned32 · microseconds
The jitter of the round trip delays measured for all the probes during this test. Measured in microseconds.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.8
Unsigned32 · microseconds
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.
jnxPingResultsMaxEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.9
Unsigned32 · microseconds
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.
jnxPingResultsAvgEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.10
Unsigned32 · microseconds
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.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlEgressTimeThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.10
Unsigned32 (0..60000000) · microseconds
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.
jnxPingResultsEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.7
Unsigned32 · 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.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.8
Unsigned32 · microseconds
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.
jnxPingResultsMaxEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.9
Unsigned32 · microseconds
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.
jnxPingResultsAvgEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.10
Unsigned32 · microseconds
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.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingResultsStddevEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.11
Unsigned32 · microseconds
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.
jnxPingCtlEgressStdDevThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.11
Unsigned32 (0..60000000) · microseconds
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.
jnxPingResultsStddevEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.11
Unsigned32 · microseconds
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.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.8
Unsigned32 · microseconds
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.
jnxPingResultsMaxEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.9
Unsigned32 · microseconds
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.
jnxPingResultsAvgEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.10
Unsigned32 · microseconds
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.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlEgressJitterThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.12
Unsigned32 (0..60000000) · microseconds
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.
jnxPingResultsJitterEgressUs
1.3.6.1.4.1.2636.3.7.1.3.1.18
Unsigned32 · 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.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.13
Unsigned32 · microseconds
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.
jnxPingResultsMaxIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.14
Unsigned32 · microseconds
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.
jnxPingResultsAvgIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.15
Unsigned32 · microseconds
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.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlIngressTimeThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.13
Unsigned32 (0..60000000) · microseconds
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.
jnxPingResultsIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.12
Unsigned32 · microseconds
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.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.13
Unsigned32 · microseconds
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.
jnxPingResultsMaxIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.14
Unsigned32 · microseconds
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.
jnxPingResultsAvgIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.15
Unsigned32 · microseconds
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.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlIngressStddevThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.14
Unsigned32 (0..60000000) · microseconds
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.
jnxPingResultsStddevIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.16
Unsigned32 · microseconds
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.
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.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.13
Unsigned32 · microseconds
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.
jnxPingResultsMaxIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.14
Unsigned32 · microseconds
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.
jnxPingResultsAvgIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.15
Unsigned32 · microseconds
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.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlIngressJitterThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.15
Unsigned32 (0..60000000) · microseconds
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.
jnxPingResultsJitterIngressUs
1.3.6.1.4.1.2636.3.7.1.3.1.19
Unsigned32 · microseconds
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.
jnxPingMaxRttThresholdExceeded
1.3.6.1.4.1.2636.4.9.0.10
This notification is generated when the max round trip time (jnxPingCtlMaxRttThreshold) exceeds the configured threshold (jnxPingCtlMaxRttThreshold) and the maxrttThreshold bit is set in jnxPingCtlTrapGeneration.
pingCtlTargetAddressType
1.3.6.1.2.1.80.1.2.1.3
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
Specifies the type of host address to be used at a remote host for performing a ping operation.
pingCtlTargetAddress
1.3.6.1.2.1.80.1.2.1.4
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
pingResultsOperStatus
1.3.6.1.2.1.80.1.3.1.1
INTEGER1 = enabled2 = disabled · Integer32
Reflects the operational state of a pingCtlEntry:
enabled(1) - Test is active.
disabled(2) - Test has stopped.
pingResultsIpTargetAddressType
1.3.6.1.2.1.80.1.3.1.2
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType.
To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation.
Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
pingResultsIpTargetAddress
1.3.6.1.2.1.80.1.3.1.3
InetAddressDenotes a generic Internet address.
An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row.
The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
jnxPingResultsMinRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.3
Unsigned32 · microseconds
The minimum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsMaxRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.4
Unsigned32 · microseconds
The maximum of the round trip delays measured for all the probes during this test. Measured in microseconds.
jnxPingResultsAvgRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.5
Unsigned32 · microseconds
The average of the round trip delays measured for all the probes during this test. Measured in microseconds.
pingResultsProbeResponses
1.3.6.1.2.1.80.1.3.1.7
Unsigned32 · responses
Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
pingResultsSentProbes
1.3.6.1.2.1.80.1.3.1.8
Unsigned32 · probes
The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
pingResultsRttSumOfSquares
1.3.6.1.2.1.80.1.3.1.9
Unsigned32 · milliseconds
This object contains the sum of the squares for all ping responses received. Its purpose is to enable standard deviation calculation. The value of this object MUST be reported as 0 when no ping responses have been received.
pingResultsLastGoodProbe
1.3.6.1.2.1.80.1.3.1.10
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
Date and time when the last response was received for a probe.
jnxPingCtlRttThreshold
1.3.6.1.4.1.2636.3.7.1.2.1.7
Unsigned32 (0..6000000) · microseconds
Maximum round trip time allowed. If this threshold is crossed by any probe, a jnxPingRttThresholdExceeded trap will be sent.
jnxPingResultsRttUs
1.3.6.1.4.1.2636.3.7.1.3.1.1
Unsigned32 · microseconds
The round trip delays measured for the most recent successful probe during this test. Measured in microseconds.