EZ5 MIB Catalog

JUNIPER-TIMING-NOTFNS-MIB

2021-07-18

This is Juniper Networks' implementation of enterprise specific MIB for alarms from the router chassis box.

Download JUNIPER-TIMING-NOTFNS-MIB.txt Open JUNIPER-TIMING-NOTFNS-MIB.txt in a new tab

SCALARS (43) · TABLES (6) · TRAPS (52)

Scalars (43)

NameOID
jnxClksyncState1.3.6.1.4.1.2636.3.75.1.3.1
jnxClksyncIfIndex1.3.6.1.4.1.2636.3.75.1.3.2
jnxClksyncIntfName1.3.6.1.4.1.2636.3.75.1.3.3
jnxAcbFpgaRevMajor1.3.6.1.4.1.2636.3.75.1.3.4
jnxAcbFpgaRevMinor1.3.6.1.4.1.2636.3.75.1.3.5
jnxBootCpldFpgaRevMajor1.3.6.1.4.1.2636.3.75.1.3.6
jnxBootCpldFpgaRevMinor1.3.6.1.4.1.2636.3.75.1.3.7
jnxClksyncQualityCode1.3.6.1.4.1.2636.3.75.1.3.8
jnxClksyncDpllState1.3.6.1.4.1.2636.3.75.1.3.9
jnxPtpServoState1.3.6.1.4.1.2636.3.75.1.3.10
jnxPtpClass1.3.6.1.4.1.2636.3.75.1.3.11
jnxPtpAccuracy1.3.6.1.4.1.2636.3.75.1.3.12
jnxPtpGmId1.3.6.1.4.1.2636.3.75.1.3.13
jnxPtpGmIpAddr1.3.6.1.4.1.2636.3.75.1.3.14
jnxClkStreamHandle1.3.6.1.4.1.2636.3.75.1.3.15
jnxRemoteIpAddr1.3.6.1.4.1.2636.3.75.1.3.16
jnxClksyncHybridState1.3.6.1.4.1.2636.3.75.1.3.17
jnxPtpPhaseOffset1.3.6.1.4.1.2636.3.75.1.3.18
jnxClksyncQualityCodeStr1.3.6.1.4.1.2636.3.75.1.3.19
jnxClksyncDpllStateStr1.3.6.1.4.1.2636.3.75.1.3.20
jnxPtpServoStateStr1.3.6.1.4.1.2636.3.75.1.3.21
jnxClksyncHybridStateStr1.3.6.1.4.1.2636.3.75.1.3.22
jnxClksyncColorStr1.3.6.1.4.1.2636.3.75.1.3.23
jnxPtpPhaseOffsetThresholdExceeded1.3.6.1.4.1.2636.3.75.1.3.24
jnxPtpUtcOffset1.3.6.1.4.1.2636.3.75.1.3.25
jnxGpsRecvStatus1.3.6.1.4.1.2636.3.75.1.3.26
jnxPtpAdvClockClass1.3.6.1.4.1.2636.3.75.1.3.27
jnxClksyncSynceLockedIfIndex1.3.6.1.4.1.2636.3.75.1.3.28
jnxClksyncSynceLockedIntfName1.3.6.1.4.1.2636.3.75.1.3.29
jnxPtpUtcValid1.3.6.1.4.1.2636.3.75.1.3.31
jnxTimingFrequencyTraceability1.3.6.1.4.1.2636.3.75.1.3.34
jnxTimingTimeTraceability1.3.6.1.4.1.2636.3.75.1.3.35
jnxClksyncAdditionalInformationStr1.3.6.1.4.1.2636.3.75.1.3.38
jnxPtpPhaseErrorRelativeThreshold1.3.6.1.4.1.2636.3.75.1.3.39
jnxPtpPhaseMonitoringHoldoverLimit1.3.6.1.4.1.2636.3.75.1.3.40
jnxPtpPhaseMonitoringSynceHoldover1.3.6.1.4.1.2636.3.75.1.3.41
jnxPtpPhaseMonitoringPtpIntfName1.3.6.1.4.1.2636.3.75.1.3.42
jnxPtpPhaseMonitoringSynceIntfName1.3.6.1.4.1.2636.3.75.1.3.43
jnxPtpPhaseCorrection1.3.6.1.4.1.2636.3.75.1.3.44
jnxPtpPhaseMonitoringReason1.3.6.1.4.1.2636.3.75.1.3.45
jnxPtpPerformanceMonitorEnabled1.3.6.1.4.1.2636.3.75.1.5.1
jnxPtpPassivePortMonitorEnabled1.3.6.1.4.1.2636.3.75.1.6.1
jnxPtpPassivePortMonitorDelayRequestInterval1.3.6.1.4.1.2636.3.75.1.6.2

Tables (6)

NameOID
jnxClksyncSynceQualityTable1.3.6.1.4.1.2636.3.75.1.3.30
jnxClksyncPtpOperationalMasterTable1.3.6.1.4.1.2636.3.75.1.3.36
jnxClksyncPtpOperationalSlaveTable1.3.6.1.4.1.2636.3.75.1.3.37
jnxPtpStatisticsTable1.3.6.1.4.1.2636.3.75.1.5.2
jnxPtpPerformanceTable1.3.6.1.4.1.2636.3.75.1.5.3
jnxPtpPassivePortMonitorTable1.3.6.1.4.1.2636.3.75.1.6.3

Traps (52)

NameOID
jnxTimingFaultLOSSet1.3.6.1.4.1.2636.3.75.1.1.1
jnxTimingFaultLOSClear1.3.6.1.4.1.2636.3.75.1.1.2
jnxTimingFaultEFDSet1.3.6.1.4.1.2636.3.75.1.1.3
jnxTimingFaultEFDClear1.3.6.1.4.1.2636.3.75.1.1.4
jnxTimingFaultLOESMCSet1.3.6.1.4.1.2636.3.75.1.1.5
jnxTimingFaultLOESMCClear1.3.6.1.4.1.2636.3.75.1.1.6
jnxTimingFaultQLFailSet1.3.6.1.4.1.2636.3.75.1.1.7
jnxTimingFaultQLFailClear1.3.6.1.4.1.2636.3.75.1.1.8
jnxTimingFaultLTISet1.3.6.1.4.1.2636.3.75.1.1.9
jnxTimingFaultLTIClear1.3.6.1.4.1.2636.3.75.1.1.10
jnxTimingFaultAcbcFpgaVerNotCompatible1.3.6.1.4.1.2636.3.75.1.1.11
jnxTimingFaultBootCpldVerNotCompatible1.3.6.1.4.1.2636.3.75.1.1.12
jnxTimingFaultPriSrcFailed1.3.6.1.4.1.2636.3.75.1.1.13
jnxTimingFaultSecSrcFailed1.3.6.1.4.1.2636.3.75.1.1.14
jnxTimingFaultPtpUniNegRateRejectSet1.3.6.1.4.1.2636.3.75.1.1.15
jnxTimingFaultPtpUniNegRateRejectClear1.3.6.1.4.1.2636.3.75.1.1.16
jnxTimingEventSquelchSet1.3.6.1.4.1.2636.3.75.1.1.17
jnxTimingEventSquelchClear1.3.6.1.4.1.2636.3.75.1.1.18
jnxTimingAlarmNoForeignMasterSet1.3.6.1.4.1.2636.3.75.1.1.29
jnxTimingAlarmNoForeignMasterClear1.3.6.1.4.1.2636.3.75.1.1.30
jnxTimingAlarmPtpLocalClockOutOfSyncSet1.3.6.1.4.1.2636.3.75.1.1.33
jnxTimingAlarmPtpLocalClockOutOfSyncClear1.3.6.1.4.1.2636.3.75.1.1.34
jnxTimingAlarmLossOfReference1Set1.3.6.1.4.1.2636.3.75.1.1.35
jnxTimingAlarmLossOfReference1Clear1.3.6.1.4.1.2636.3.75.1.1.36
jnxTimingAlarmLossOfReference2Set1.3.6.1.4.1.2636.3.75.1.1.37
jnxTimingAlarmLossOfReference2Clear1.3.6.1.4.1.2636.3.75.1.1.38
jnxTimingAlarmNoMoreReferenceSet1.3.6.1.4.1.2636.3.75.1.1.43
jnxTimingAlarmNoMoreReferenceClear1.3.6.1.4.1.2636.3.75.1.1.44
jnxTimingAlarmQlBelowThresholdSet1.3.6.1.4.1.2636.3.75.1.1.45
jnxTimingAlarmQlBelowThresholdClear1.3.6.1.4.1.2636.3.75.1.1.46
jnxTimingAlarmTodInSignalFailSet1.3.6.1.4.1.2636.3.75.1.1.49
jnxTimingAlarmTodInSignalFailClear1.3.6.1.4.1.2636.3.75.1.1.50
jnxTimingEventPriSrcRecovered1.3.6.1.4.1.2636.3.75.1.2.1
jnxTimingEventSecSrcRecovered1.3.6.1.4.1.2636.3.75.1.2.2
jnxTimingEventPriRefChanged1.3.6.1.4.1.2636.3.75.1.2.3
jnxTimingEventSecRefChanged1.3.6.1.4.1.2636.3.75.1.2.4
jnxTimingEventQLChangedRx1.3.6.1.4.1.2636.3.75.1.2.5
jnxTimingEventQLChangedTx1.3.6.1.4.1.2636.3.75.1.2.6
jnxTimingEventSynceHldovrToLck(deprecated)1.3.6.1.4.1.2636.3.75.1.2.7
jnxTimingEventSynceLckToHldovr(deprecated)1.3.6.1.4.1.2636.3.75.1.2.8
jnxTimingEventDpllStatus1.3.6.1.4.1.2636.3.75.1.2.9
jnxTimingEventSynceDpllStatus1.3.6.1.4.1.2636.3.75.1.2.10
jnxTimingEventBitsDpllStatus1.3.6.1.4.1.2636.3.75.1.2.11
jnxTimingEventPtpServoStatus1.3.6.1.4.1.2636.3.75.1.2.12
jnxTimingEventPtpGMClockClassChange1.3.6.1.4.1.2636.3.75.1.2.13
jnxTimingEventPtpGMClockAccuracyChange1.3.6.1.4.1.2636.3.75.1.2.14
jnxTimingEventPtpGMChange1.3.6.1.4.1.2636.3.75.1.2.15
jnxTimingEventHybridStatus1.3.6.1.4.1.2636.3.75.1.2.16
jnxTimingEventLedColorChange1.3.6.1.4.1.2636.3.75.1.2.19
jnxTimingPhaseOffsetThresholdExceeded1.3.6.1.4.1.2636.3.75.1.2.20
jnxTimingEventPhaseErrorHoldoverStarted1.3.6.1.4.1.2636.3.75.1.2.21
jnxTimingEventPhaseErrorHoldoverEnded1.3.6.1.4.1.2636.3.75.1.2.22

END OF TOC

Scalar details

jnxClksyncState

1.3.6.1.4.1.2636.3.75.1.3.1

INTEGER0 = clear1 = set · Integer32

Fault status.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxAcbFpgaRevMajor

1.3.6.1.4.1.2636.3.75.1.3.4

Integer32

Major version information.

jnxAcbFpgaRevMinor

1.3.6.1.4.1.2636.3.75.1.3.5

Integer32

Minor version information.

jnxBootCpldFpgaRevMajor

1.3.6.1.4.1.2636.3.75.1.3.6

Integer32

Major version information.

jnxBootCpldFpgaRevMinor

1.3.6.1.4.1.2636.3.75.1.3.7

Integer32

Minor version information.

jnxClksyncQualityCode

1.3.6.1.4.1.2636.3.75.1.3.8

INTEGER2 = prc4 = ssu-a8 = ssu-b11 = sec15 = dnu1 = prs0 = stu7 = st216 = tnc13 = st3e10 = st312 = smc14 = st417 = dus · Integer32

SSM/ESMC quality levels.

jnxClksyncDpllState

1.3.6.1.4.1.2636.3.75.1.3.9

INTEGER0 = init-phase1 = acquiring-lock2 = locked3 = holdover4 = free-run5 = unknown · Integer32

BITS/SyncE DPLL states.

jnxPtpServoState

1.3.6.1.4.1.2636.3.75.1.3.10

INTEGER0 = init1 = free-run2 = holdover3 = acquiring4 = freq-locked5 = phase-aligned · Integer32

PTP servo states.

jnxPtpClass

1.3.6.1.4.1.2636.3.75.1.3.11

Integer32

PTP clock status.

jnxPtpAccuracy

1.3.6.1.4.1.2636.3.75.1.3.12

Integer32

PTP clock accuracy.

jnxPtpGmId

1.3.6.1.4.1.2636.3.75.1.3.13

JnxPtpClockIdTCClock Identifier. SIZE (8) · OCTET STRING

PTP Grand Master clock-id.

jnxPtpGmIpAddr

1.3.6.1.4.1.2636.3.75.1.3.14

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

PTP Grand Master stream ip-address.

jnxClkStreamHandle

1.3.6.1.4.1.2636.3.75.1.3.15

Integer32

PTP clock accuracy.

jnxRemoteIpAddr

1.3.6.1.4.1.2636.3.75.1.3.16

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

PTP clock stream's remote ip-address.

jnxClksyncHybridState

1.3.6.1.4.1.2636.3.75.1.3.17

INTEGER0 = init1 = freq-acq2 = freqLck-phaseAcq13 = freqLck-phaseAcq24 = freqLck-phaseAcq35 = freq-phase-lck · Integer32

hybrid states.

jnxPtpPhaseOffset

1.3.6.1.4.1.2636.3.75.1.3.18

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..255) · OCTET STRING · hint 255a

Phase Offset.

jnxClksyncQualityCodeStr

1.3.6.1.4.1.2636.3.75.1.3.19

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..255) · OCTET STRING · hint 255a

SSM/ESMC quality levels in string format.

jnxClksyncDpllStateStr

1.3.6.1.4.1.2636.3.75.1.3.20

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..255) · OCTET STRING · hint 255a

Dpll state in string format.

jnxPtpServoStateStr

1.3.6.1.4.1.2636.3.75.1.3.21

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..255) · OCTET STRING · hint 255a

PTP servo states in string format.

jnxClksyncHybridStateStr

1.3.6.1.4.1.2636.3.75.1.3.22

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..255) · OCTET STRING · hint 255a

hybrid states in string format.

jnxClksyncColorStr

1.3.6.1.4.1.2636.3.75.1.3.23

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..255) · OCTET STRING · hint 255a

Color of the LED unit.

jnxPtpPhaseOffsetThresholdExceeded

1.3.6.1.4.1.2636.3.75.1.3.24

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..255) · OCTET STRING · hint 255a

Indicates whether the Phase Threshold of the monitored Passive Port has exceeded the configured Max Phase Offset Threshold as per Annex G of ITU-T G.8275.1

jnxPtpUtcOffset

1.3.6.1.4.1.2636.3.75.1.3.25

JnxPtpPhaseOffsetTCPhase Offset. (0..1000) · Integer32

UTC Offset.

jnxGpsRecvStatus

1.3.6.1.4.1.2636.3.75.1.3.26

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..255) · OCTET STRING · hint 255a

Gps Receiver Status

jnxPtpAdvClockClass

1.3.6.1.4.1.2636.3.75.1.3.27

Integer32

UTC Offset.

jnxClksyncSynceLockedIfIndex

1.3.6.1.4.1.2636.3.75.1.3.28

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncSynceLockedIntfName

1.3.6.1.4.1.2636.3.75.1.3.29

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..255) · OCTET STRING · hint 255a

Interface name.

jnxPtpUtcValid

1.3.6.1.4.1.2636.3.75.1.3.31

INTEGER0 = false1 = true · Integer32

PTP UTC Offset Valid.

jnxTimingFrequencyTraceability

1.3.6.1.4.1.2636.3.75.1.3.34

INTEGER0 = false1 = true · Integer32

Frequency Traceable Flag.

jnxTimingTimeTraceability

1.3.6.1.4.1.2636.3.75.1.3.35

INTEGER0 = false1 = true · Integer32

Time Traceable Flag.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxPtpPhaseErrorRelativeThreshold

1.3.6.1.4.1.2636.3.75.1.3.39

Unsigned32 (250..10000)

The currently configured phase-error-limit threshold

jnxPtpPhaseMonitoringHoldoverLimit

1.3.6.1.4.1.2636.3.75.1.3.40

Unsigned32 (5..10080)

The currently configured phase-error-limit max holdover time

jnxPtpPhaseMonitoringSynceHoldover

1.3.6.1.4.1.2636.3.75.1.3.41

INTEGER0 = false1 = true · Integer32

If SyncE can go to holdover when phase-error-limit holdover occurs

jnxPtpPhaseMonitoringPtpIntfName

1.3.6.1.4.1.2636.3.75.1.3.42

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..255) · OCTET STRING · hint 255a

The PTP interface being monitored for the phase-error-limit feature

jnxPtpPhaseMonitoringSynceIntfName

1.3.6.1.4.1.2636.3.75.1.3.43

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..255) · OCTET STRING · hint 255a

The currently locked SyncE source while monitoring PTP for phase-error-limit feature, or previously locked if in SyncE holdover due to the feature. Not present if SyncE holdover isn't configured

jnxPtpPhaseCorrection

1.3.6.1.4.1.2636.3.75.1.3.44

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

The ignored phase corrrection when holdover started due to the phase-error-limit feature

jnxPtpPhaseMonitoringReason

1.3.6.1.4.1.2636.3.75.1.3.45

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..255) · OCTET STRING · hint 255a

The reason for the occurrence of some phase-monitoring event

jnxPtpPerformanceMonitorEnabled

1.3.6.1.4.1.2636.3.75.1.5.1

INTEGER0 = false1 = true · Integer32

Indicates that performance monitor feature as per Annex J1 of IEEE 1588v2.1 (2019) is enabled or disabled.

jnxPtpPassivePortMonitorEnabled

1.3.6.1.4.1.2636.3.75.1.6.1

INTEGER0 = false1 = true · Integer32

Indicates that passive port monitor feature as per Annex G of ITU-T G.8275.1 is enabled or disabled.

jnxPtpPassivePortMonitorDelayRequestInterval

1.3.6.1.4.1.2636.3.75.1.6.2

Integer32 (-7..7)

Represents passive port monitor feature delay request interval as per Annex G of ITU-T G.8275.1.

Table details

jnxClksyncSynceQualityTable

1.3.6.1.4.1.2636.3.75.1.3.30

Index: jnxClksyncSynceQualityTableIndex

Synce Table to get Quality metrics for all configured sources

jnxClksyncSynceQualityTableIndex

1.3.6.1.4.1.2636.3.75.1.3.30.1.1

Integer32

The index for each configured source, not displayed for get/walk

jnxClksyncSynceQualityIntfName

1.3.6.1.4.1.2636.3.75.1.3.30.1.2

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..255) · OCTET STRING · hint 255a

The ifName of the configured source

jnxClksyncSynceQualityValue

1.3.6.1.4.1.2636.3.75.1.3.30.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..255) · OCTET STRING · hint 255a

The Quality Level of the configured source

jnxClksyncPtpOperationalMasterTable

1.3.6.1.4.1.2636.3.75.1.3.36

Index: jnxClksyncPtpOperationalMasterIndex · jnxClksyncPtpOperationalMasterAttrIndex

PTP Operational Master Table displays the upstream clock details

jnxClksyncPtpOperationalMasterIndex

1.3.6.1.4.1.2636.3.75.1.3.36.1.1

Integer32 (0..512)

The index for each operational master, not displayed for get/walk

jnxClksyncPtpOperationalMasterAttrIndex

1.3.6.1.4.1.2636.3.75.1.3.36.1.2

Integer32 (1..512)

The index for each attribute displayed for master, not displayed index not displayed for get/walk

jnxClksyncPtpOperationalMasters

1.3.6.1.4.1.2636.3.75.1.3.36.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..255) · OCTET STRING · hint 255a

Attributes displayed for each master i.e ifl, localip, no_of_rem_clks and followed by remote ips

jnxClksyncPtpOperationalSlaveTable

1.3.6.1.4.1.2636.3.75.1.3.37

Index: jnxClksyncPtpOperationalSlaveIndex · jnxClksyncPtpOperationalSlaveAttrIndex

PTP Operational Slave Table displays the downstream clock details

jnxClksyncPtpOperationalSlaveIndex

1.3.6.1.4.1.2636.3.75.1.3.37.1.1

Integer32 (0..512)

The index for each operational slave, not displayed for get/walk

jnxClksyncPtpOperationalSlaveAttrIndex

1.3.6.1.4.1.2636.3.75.1.3.37.1.2

Integer32 (1..512)

The index for each attribute displayed for master, not displayed index not displayed for get/walk

jnxClksyncPtpOperationalSlaves

1.3.6.1.4.1.2636.3.75.1.3.37.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..255) · OCTET STRING · hint 255a

Attributes displayed for each slave i.e ifl, localip, no_of_rem_clks and followed by remote ips

jnxPtpStatisticsTable

1.3.6.1.4.1.2636.3.75.1.5.2

Index: jnxPtpStatisticsAttrIndex

Performance monitor statistics table as per Annex J3 of IEEE 1588v2.1 (2019).

jnxPtpStatisticsAttrIndex

1.3.6.1.4.1.2636.3.75.1.5.2.1.1

Unsigned32 (1..98)

The index for each performance monitor statistics data attribute: (1..96) represents 15 min counters; (97..98) represents 24 h counters.

jnxPtpStatisticsTimestamp

1.3.6.1.4.1.2636.3.75.1.5.2.1.2

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..255) · OCTET STRING · hint 255a

Timestamp of PTP slave port monitor statistics data.

jnxPtpStatisticsTxAnnounce

1.3.6.1.4.1.2636.3.75.1.5.2.1.3

Unsigned32

Counter indicating the number of Announce messages that have been transmitted for each 15 min and 24 h interval.

jnxPtpStatisticsTxSync

1.3.6.1.4.1.2636.3.75.1.5.2.1.4

Unsigned32

Counter indicating the number of Sync messages that have been transmitted for each 15 min and 24 h interval.

jnxPtpStatisticsTxDelayRequest

1.3.6.1.4.1.2636.3.75.1.5.2.1.5

Unsigned32

Counter indicating the number of Delay Request messages that have been transmitted for each 15 min and 24 h interval.

jnxPtpStatisticsTxDelayResponse

1.3.6.1.4.1.2636.3.75.1.5.2.1.6

Unsigned32

Counter indicating the number of Delay Response messages that have been transmitted for each 15 min and 24 h interval.

jnxPtpStatisticsTxFollowup

1.3.6.1.4.1.2636.3.75.1.5.2.1.7

Unsigned32

Counter indicating the number of Follow Up messages that have been transmitted for each 15 min and 24 h interval.

jnxPtpStatisticsTxError

1.3.6.1.4.1.2636.3.75.1.5.2.1.8

Unsigned32

Counter indicating the number of Transmit Error messages that have been transmitted for each 15 min and 24 h interval.

jnxPtpStatisticsAnnouncedFromAllForeignMasters

1.3.6.1.4.1.2636.3.75.1.5.2.1.9

Unsigned32

Counter indicating the total number of announce messages from the foreign Masters that have been received for each 15 min and 24 h interval as per Annex J3 of IEEE 1588v2.1 (2019).

jnxPtpStatisticsRxAnnounce

1.3.6.1.4.1.2636.3.75.1.5.2.1.10

Unsigned32

Counter indicating the number of Announce messages from the current GM that have been received for each 15 min and 24 h interval.

jnxPtpStatisticsRxSync

1.3.6.1.4.1.2636.3.75.1.5.2.1.11

Unsigned32

Counter indicating the number of Sync messages that have been received for each 15 min and 24 h interval.

jnxPtpStatisticsRxDelayRequest

1.3.6.1.4.1.2636.3.75.1.5.2.1.12

Unsigned32

Counter indicating the number of Delay Request messages that have been received for each 15 min and 24 h interval.

jnxPtpStatisticsRxDelayResponse

1.3.6.1.4.1.2636.3.75.1.5.2.1.13

Unsigned32

Counter indicating the number of Delay Response messages that have been received for each 15 min and 24 h interval.

jnxPtpStatisticsRxFollowup

1.3.6.1.4.1.2636.3.75.1.5.2.1.14

Unsigned32

Counter indicating the number of Follow Up messages that have been received for each 15 min and 24 h interval.

jnxPtpStatisticsRxError

1.3.6.1.4.1.2636.3.75.1.5.2.1.15

Unsigned32

Counter indicating the number of Receive Error messages that have been received for each 15 min and 24 h interval.

jnxPtpPerformanceTable

1.3.6.1.4.1.2636.3.75.1.5.3

Index: jnxPtpPerformanceAttrIndex

Performance monitor table as per Annex J1 of IEEE 1588v2.1 (2019).

jnxPtpPerformanceAttrIndex

1.3.6.1.4.1.2636.3.75.1.5.3.1.1

Unsigned32 (1..98)

The index for each performance monitor attribute: (1..96) represents 15 min counters; (97..98) represents 24 h counters.

jnxPtpPerformanceIntfName

1.3.6.1.4.1.2636.3.75.1.5.3.1.2

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..127) · OCTET STRING · hint 255a

The interface name for ptp performance monitor data.

jnxPtpPerformanceSourcePortIdentity

1.3.6.1.4.1.2636.3.75.1.5.3.1.3

Unsigned32 (0..65535)

Idenity of the source port associated with the performance monitor data.

jnxPtpPerformanceTimestamp

1.3.6.1.4.1.2636.3.75.1.5.3.1.4

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..255) · OCTET STRING · hint 255a

Timestamp of PTP slave port monitor measurement data.

jnxPtpPerformancePeriodComplete

1.3.6.1.4.1.2636.3.75.1.5.3.1.5

INTEGER0 = false1 = true · Integer32

Flag to represent if any data collected within a measurement window (15min or 24h) is partial as per IEEE 1588 2019 Annex J.4.1.

jnxPtpPerformanceDataValid

1.3.6.1.4.1.2636.3.75.1.5.3.1.6

INTEGER0 = false1 = true · Integer32

Validity of performance monitor data for each 15 min and 24 h interval.

jnxPtpPerformanceDataInvalidReason

1.3.6.1.4.1.2636.3.75.1.5.3.1.7

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..127) · OCTET STRING · hint 255a

PTP slave port monitor measurement data (15min/24h) invalid reasons: 1) PTP servo sync state not phase aligned & Phy sync state not in sync. 2) PTP servo sync state not phase aligned & Phy sync state in sync. 3) PTP servo sync state phase aligned & Phy sync state not in sync. 4) Measurement not started: PTP servo sync state not phase aligned.

jnxPtpPerformanceAverageMasterSlaveDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.8

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average of the Master to Slave Delay for each 15 min and 24 h interval.

jnxPtpPerformanceMinMasterSlaveDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.9

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Minimum of the Master to Slave Delay for each 15 min and 24 h interval.

jnxPtpPerformanceMaxMasterSlaveDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.10

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Maximum of the Master to Slave Delay for each 15 min and 24 h interval.

jnxPtpPerformanceStdDevMasterSlaveDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.11

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Standard Deviation of the Master to Slave Delay for each 15 min and 24 h interval.

jnxPtpPerformanceAverageSlaveMasterDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.12

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average of the Slave to Master Delay for each 15 min and 24 h interval.

jnxPtpPerformanceMinSlaveMasterDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.13

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Minimum of the Slave to Master Delay for each 15 min and 24 h interval.

jnxPtpPerformanceMaxSlaveMasterDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.14

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Maximum of the Slave to Master Delay for each 15 min and 24 h interval.

jnxPtpPerformanceStdDevSlaveMasterDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.15

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Standard Deviation of the Slave to Master Delay for each 15 min and 24 h interval.

jnxPtpPerformanceAverageMeanPathDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.16

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average of the Mean Path Delay for each 15 min and 24 h interval.

jnxPtpPerformanceMinMeanPathDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.17

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Minimum of the Mean Path Delay for each 15 min and 24 h interval.

jnxPtpPerformanceMaxMeanPathDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.18

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Maximum of the Mean Path Delay for each 15 min and 24 h interval.

jnxPtpPerformanceStdDevMeanPathDelay

1.3.6.1.4.1.2636.3.75.1.5.3.1.19

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Standard Deviation of the Mean Path Delay for each 15 min and 24 h interval.

jnxPtpPerformanceAverageOffsetFromMaster

1.3.6.1.4.1.2636.3.75.1.5.3.1.20

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average of the Phase Offset From Master for each 15 min and 24 h interval.

jnxPtpPerformanceMinOffsetFromMaster

1.3.6.1.4.1.2636.3.75.1.5.3.1.21

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Minimum of the Phase Offset From Master for each 15 min and 24 h interval.

jnxPtpPerformanceMaxOffsetFromMaster

1.3.6.1.4.1.2636.3.75.1.5.3.1.22

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Maximum of the Phase Offset From Master for each 15 min and 24 h interval.

jnxPtpPerformanceStdDevOffsetFromMaster

1.3.6.1.4.1.2636.3.75.1.5.3.1.23

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Stdandard Deviation of the Phase Offset From Master for each 15 min and 24 h interval.

jnxPtpPassivePortMonitorTable

1.3.6.1.4.1.2636.3.75.1.6.3

Index: jnxPtpPassivePortMonitorIntfName

PTP passive port performance monitor table to get the passive port performance against the selected slave port.

jnxPtpPassivePortMonitorIntfName

1.3.6.1.4.1.2636.3.75.1.6.3.1.1

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..128) · OCTET STRING · hint 255a

The interface name for PTP passive port data displayed for the stream.

jnxPtpPassivePortMonitorSourcePortIdentity

1.3.6.1.4.1.2636.3.75.1.6.3.1.2

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..127) · OCTET STRING · hint 255a

Identity of the source port to which PTP passive port data is associated.

jnxPtpPassivePortMonitorDataValid

1.3.6.1.4.1.2636.3.75.1.6.3.1.3

INTEGER0 = valid1 = inactive2 = not-applicable · Integer32

This describes the validity of the data. If port state is passive and, passive port monitoring feature is enabled, then there is a valid measurement data available set to (0). If port state is other than passive, then not-applicable will be set to (1); and if port state is passive and servo state is other than phase-aligned, this will be set to (2) inactive.

jnxPtpPassivePortMonitorStartTimestamp

1.3.6.1.4.1.2636.3.75.1.6.3.1.4

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..255) · OCTET STRING · hint 255a

Start Timestamp of PTP passive port monitor performance data.

jnxPtpPassivePortMonitorEndTimestamp

1.3.6.1.4.1.2636.3.75.1.6.3.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..255) · OCTET STRING · hint 255a

End Timestamp of PTP passive port monitor performance data.

jnxPtpPassivePortMonitorAveragePhaseOffsetFromMaster

1.3.6.1.4.1.2636.3.75.1.6.3.1.6

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average Phase Offset value of the passive port from Master.

jnxPtpPassivePortMonitorMinPhaseOffsetFromMaster

1.3.6.1.4.1.2636.3.75.1.6.3.1.7

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Minimum Phase Offset value of the passive port from Master.

jnxPtpPassivePortMonitorMaxPhaseOffsetFromMaster

1.3.6.1.4.1.2636.3.75.1.6.3.1.8

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Maximum Phase Offset value of the passive port from Master.

jnxPtpPassivePortMonitorAverageMasterSlaveDelay

1.3.6.1.4.1.2636.3.75.1.6.3.1.9

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average Master to Slave Delay value of the passive port from Master.

jnxPtpPassivePortMonitorMinMasterSlaveDelay

1.3.6.1.4.1.2636.3.75.1.6.3.1.10

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Minimum Master to Slave Delay value of the passive port from Master.

jnxPtpPassivePortMonitorMaxMasterSlaveDelay

1.3.6.1.4.1.2636.3.75.1.6.3.1.11

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Maximum Master to Slave Delay value of the passive port from Master.

jnxPtpPassivePortMonitorAverageSlaveMasterDelay

1.3.6.1.4.1.2636.3.75.1.6.3.1.12

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average Slave to Master Delay value of the passive port from Master.

jnxPtpPassivePortMonitorMinSlaveMasterDelay

1.3.6.1.4.1.2636.3.75.1.6.3.1.13

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Minimum Slave to Master Delay value of the passive port from Master.

jnxPtpPassivePortMonitorMaxSlaveMasterDelay

1.3.6.1.4.1.2636.3.75.1.6.3.1.14

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Maximum Slave to Master Delay value of the passive port from Master.

jnxPtpPassivePortMonitorAveragePathDelay

1.3.6.1.4.1.2636.3.75.1.6.3.1.15

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

Average Mean Path Delay of the passive port from Master.

jnxPtpPassivePortMonitorMaxPhaseOffsetThreshold

1.3.6.1.4.1.2636.3.75.1.6.3.1.16

Unsigned32

The configured Phase Offset threshold acceptable between the passive port and slave port.

jnxPtpPassivePortMonitorPhaseOffsetThresholdExceeded

1.3.6.1.4.1.2636.3.75.1.6.3.1.17

INTEGER0 = false1 = true · Integer32

Reflects the status as whether the passive port exceeded the configured Max offset threshold or not.

jnxPtpPassivePortMonitorPortConfig

1.3.6.1.4.1.2636.3.75.1.6.3.1.18

INTEGER0 = stateful1 = stateful-slave-only2 = stateful-master-only3 = stateful-not-master4 = stateful-measure-only5 = stateful-not-master-and-measure-only · Integer32

Represents the current state of the configured passive port.

jnxPtpPassivePortMonitorPortState

1.3.6.1.4.1.2636.3.75.1.6.3.1.19

INTEGER0 = initializing1 = faulty2 = disabled3 = listening4 = pre-master5 = master6 = passive7 = uncalibrated8 = slave9 = unknown · Integer32

Represents the current state of the port.

Trap details

jnxTimingFaultLOSSet

1.3.6.1.4.1.2636.3.75.1.1.1

A trap which signifies that Loss Of Signal has been detected. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultLOSClear

1.3.6.1.4.1.2636.3.75.1.1.2

A trap which signifies that Loss Of Signal has been cleared. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultEFDSet

1.3.6.1.4.1.2636.3.75.1.1.3

A trap which signifies Exceeded frequency deviation. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultEFDClear

1.3.6.1.4.1.2636.3.75.1.1.4

A trap which signifies Exceeded frequency deviation cleared. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultLOESMCSet

1.3.6.1.4.1.2636.3.75.1.1.5

A trap which signifies Loss of ESMC is set. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultLOESMCClear

1.3.6.1.4.1.2636.3.75.1.1.6

A trap which signifies Loss of ESMC is cleared. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultQLFailSet

1.3.6.1.4.1.2636.3.75.1.1.7

A trap which signifies ESMC/SSM Quality Level failed is set. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultQLFailClear

1.3.6.1.4.1.2636.3.75.1.1.8

A trap which signifies ESMC/SSM Quality Level failed is cleared. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultLTISet

1.3.6.1.4.1.2636.3.75.1.1.9

A trap which signifies Loss of timing information is set. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultLTIClear

1.3.6.1.4.1.2636.3.75.1.1.10

A trap which signifies Loss of timing information is cleared. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultAcbcFpgaVerNotCompatible

1.3.6.1.4.1.2636.3.75.1.1.11

A trap which signifies ACBC FPGA version is not compatible. jnxBootCpldFpgaRevMajor indicates the current ACBC FPGA Major revision jnxBootCpldFpgaRevMinor indicates the current ACBC FPGA Minor revision.

jnxAcbFpgaRevMajor

1.3.6.1.4.1.2636.3.75.1.3.4

Integer32

Major version information.

jnxAcbFpgaRevMinor

1.3.6.1.4.1.2636.3.75.1.3.5

Integer32

Minor version information.

jnxTimingFaultBootCpldVerNotCompatible

1.3.6.1.4.1.2636.3.75.1.1.12

A trap which signifies Boot-cpld version is not compatible. jnxClksyncVersion indicates the current Boot-cpld version.

jnxBootCpldFpgaRevMajor

1.3.6.1.4.1.2636.3.75.1.3.6

Integer32

Major version information.

jnxBootCpldFpgaRevMinor

1.3.6.1.4.1.2636.3.75.1.3.7

Integer32

Minor version information.

jnxTimingFaultPriSrcFailed

1.3.6.1.4.1.2636.3.75.1.1.13

A trap which signifies Primary source failed (Whenever PFM/CFM/SCM error occurs). jnxClksyncIfIndex is the Primary source interface index jnxClksyncIntfName is the Primary source interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultSecSrcFailed

1.3.6.1.4.1.2636.3.75.1.1.14

A trap which signifies Secondary source failed (Whenever PFM/CFM/SCM error occurs). jnxClksyncIfIndex is the Secondary source interface index jnxClksyncIntfName is the Secondary source interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingFaultPtpUniNegRateRejectSet

1.3.6.1.4.1.2636.3.75.1.1.15

A trap which signifies: When acting as MASTER - Failing/rejecting clients for signaling messages When acting as SLAVE - Failing or receiving rejection for signaling messages jnxClkStreamHandle is the clock stream handle jnxRemoteIpAddr is the clock stream's remote ip-address.

jnxClkStreamHandle

1.3.6.1.4.1.2636.3.75.1.3.15

Integer32

PTP clock accuracy.

jnxRemoteIpAddr

1.3.6.1.4.1.2636.3.75.1.3.16

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

PTP clock stream's remote ip-address.

jnxTimingFaultPtpUniNegRateRejectClear

1.3.6.1.4.1.2636.3.75.1.1.16

A trap which signifies: When acting as MASTER - Failing/rejecting clients for signaling messages When acting as SLAVE - Failing or receiving rejection for signaling messages jnxClkStreamHandle is the clock stream handle jnxRemoteIpAddr is the clock stream's remote ip-address.

jnxClkStreamHandle

1.3.6.1.4.1.2636.3.75.1.3.15

Integer32

PTP clock accuracy.

jnxRemoteIpAddr

1.3.6.1.4.1.2636.3.75.1.3.16

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

PTP clock stream's remote ip-address.

jnxTimingEventSquelchSet

1.3.6.1.4.1.2636.3.75.1.1.17

A trap which signifies that interface status changed to squelched. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingEventSquelchClear

1.3.6.1.4.1.2636.3.75.1.1.18

A trap which signifies that interface status changed to active. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingAlarmNoForeignMasterSet

1.3.6.1.4.1.2636.3.75.1.1.29

A trap which signifies that there is no foreign master available. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmNoForeignMasterClear

1.3.6.1.4.1.2636.3.75.1.1.30

A trap which signifies that there is now a foreign master available. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmPtpLocalClockOutOfSyncSet

1.3.6.1.4.1.2636.3.75.1.1.33

A trap which signifies that the local clock is out of sync. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmPtpLocalClockOutOfSyncClear

1.3.6.1.4.1.2636.3.75.1.1.34

A trap which signifies that the local clock is no more out of sync. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmLossOfReference1Set

1.3.6.1.4.1.2636.3.75.1.1.35

A trap which signifies that EEC has lost reference1. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmLossOfReference1Clear

1.3.6.1.4.1.2636.3.75.1.1.36

A trap which signifies that EEC has regained reference1. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmLossOfReference2Set

1.3.6.1.4.1.2636.3.75.1.1.37

A trap which signifies that EEC has lost reference2. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmLossOfReference2Clear

1.3.6.1.4.1.2636.3.75.1.1.38

A trap which signifies that EEC has regained reference2. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmNoMoreReferenceSet

1.3.6.1.4.1.2636.3.75.1.1.43

A trap which signifies that EEC has no references to lock. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmNoMoreReferenceClear

1.3.6.1.4.1.2636.3.75.1.1.44

A trap which signifies that EEC has a reference to lock. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmQlBelowThresholdSet

1.3.6.1.4.1.2636.3.75.1.1.45

A trap which signifies that EEC QL has fallen below threshold. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmQlBelowThresholdClear

1.3.6.1.4.1.2636.3.75.1.1.46

A trap which signifies that EEC QL has regained the threshold. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmTodInSignalFailSet

1.3.6.1.4.1.2636.3.75.1.1.49

A trap which signifies that TOD input signal has failed. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingAlarmTodInSignalFailClear

1.3.6.1.4.1.2636.3.75.1.1.50

A trap which signifies that TOD input signal is good. jnxClksyncAdditionalInformationStr has additional information for the trap. This TRAP is supported only on ACX710.

jnxClksyncAdditionalInformationStr

1.3.6.1.4.1.2636.3.75.1.3.38

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..255) · OCTET STRING · hint 255a

Additional information in string format.

jnxTimingEventPriSrcRecovered

1.3.6.1.4.1.2636.3.75.1.2.1

A trap which signifies Primary source recovered. jnxClksyncIfIndex is the Primary source interface index jnxClksyncIntfName is the Primary source interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingEventSecSrcRecovered

1.3.6.1.4.1.2636.3.75.1.2.2

A trap which signifies Secondary source recovered. jnxClksyncIfIndex is the Secondary source interface index jnxClksyncIntfName is the Secondary source interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingEventPriRefChanged

1.3.6.1.4.1.2636.3.75.1.2.3

A trap which signifies Primary reference changed (Ifd name change or change from synce to BITS/external interface etc). jnxClksyncIfIndex is the Primary reference interface index jnxClksyncIntfName is the Primary reference interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingEventSecRefChanged

1.3.6.1.4.1.2636.3.75.1.2.4

A trap which signifies Secondary reference changed (Ifd name change or change from synce to BITS/external interface etc). jnxClksyncIfIndex is the Secondary reference interface index jnxClksyncIntfName is the Secondary reference interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingEventQLChangedRx

1.3.6.1.4.1.2636.3.75.1.2.5

A trap which signifies RX SSM/ESMC quality level changed. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name jnxClksyncQualityCode is the SSM/ESMC quality level jnxClksyncQualityCodeStr is the SSM/ESMC quality level in string format.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxClksyncQualityCode

1.3.6.1.4.1.2636.3.75.1.3.8

INTEGER2 = prc4 = ssu-a8 = ssu-b11 = sec15 = dnu1 = prs0 = stu7 = st216 = tnc13 = st3e10 = st312 = smc14 = st417 = dus · Integer32

SSM/ESMC quality levels.

jnxClksyncQualityCodeStr

1.3.6.1.4.1.2636.3.75.1.3.19

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..255) · OCTET STRING · hint 255a

SSM/ESMC quality levels in string format.

jnxTimingEventQLChangedTx

1.3.6.1.4.1.2636.3.75.1.2.6

A trap which signifies TX SSM/ESMC quality level changed. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name jnxClksyncQualityCode is the SSM/ESMC quality level jnxClksyncQualityCodeStr is the SSM/ESMC quality level in string format.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxClksyncQualityCode

1.3.6.1.4.1.2636.3.75.1.3.8

INTEGER2 = prc4 = ssu-a8 = ssu-b11 = sec15 = dnu1 = prs0 = stu7 = st216 = tnc13 = st3e10 = st312 = smc14 = st417 = dus · Integer32

SSM/ESMC quality levels.

jnxClksyncQualityCodeStr

1.3.6.1.4.1.2636.3.75.1.3.19

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..255) · OCTET STRING · hint 255a

SSM/ESMC quality levels in string format.

jnxTimingEventSynceHldovrToLck

1.3.6.1.4.1.2636.3.75.1.2.7

A trap which signifies SyncE Holdover to Locked EEC state. jnxClksyncIfIndex is the SyncE interface index jnxClksyncIntfName is the SyncE interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingEventSynceLckToHldovr

1.3.6.1.4.1.2636.3.75.1.2.8

A trap which signifies SyncE Locked to Holdover EEC state. jnxClksyncIfIndex is the SyncE interface index jnxClksyncIntfName is the SyncE interface name.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxTimingEventDpllStatus

1.3.6.1.4.1.2636.3.75.1.2.9

A trap which signifies that DPLL state change (unknown, lock_acq, locked, holdover, freerun). jnxClksyncDpllState indicates the Dpll status jnxClksyncDpllStateStr indicates the Dpll status in string format.

jnxClksyncDpllState

1.3.6.1.4.1.2636.3.75.1.3.9

INTEGER0 = init-phase1 = acquiring-lock2 = locked3 = holdover4 = free-run5 = unknown · Integer32

BITS/SyncE DPLL states.

jnxClksyncDpllStateStr

1.3.6.1.4.1.2636.3.75.1.3.20

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..255) · OCTET STRING · hint 255a

Dpll state in string format.

jnxTimingEventSynceDpllStatus

1.3.6.1.4.1.2636.3.75.1.2.10

A trap which signifies that Synce DPLL state change (unknown, lock_acq, locked, holdover, freerun). jnxClksyncIfIndex is the interface index from which Frequency is derived jnxClksyncIntfName is the interface name from which Frequency is derived jnxClksyncDpllState indicates the Dpll status jnxClksyncDpllStateStr indicates the Dpll status in string format.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxClksyncDpllState

1.3.6.1.4.1.2636.3.75.1.3.9

INTEGER0 = init-phase1 = acquiring-lock2 = locked3 = holdover4 = free-run5 = unknown · Integer32

BITS/SyncE DPLL states.

jnxClksyncDpllStateStr

1.3.6.1.4.1.2636.3.75.1.3.20

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..255) · OCTET STRING · hint 255a

Dpll state in string format.

jnxTimingEventBitsDpllStatus

1.3.6.1.4.1.2636.3.75.1.2.11

A trap which signifies that BITS DPLL state change (unknown, lock_acq, locked, holdover, freerun). jnxClksyncIfIndex is the interface index from which Frequency is derived jnxClksyncIntfName is the interface name from which Frequency is derived jnxClksyncDpllState indicates the Dpll status jnxClksyncDpllStateStr indicates the Dpll status in string format.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxClksyncDpllState

1.3.6.1.4.1.2636.3.75.1.3.9

INTEGER0 = init-phase1 = acquiring-lock2 = locked3 = holdover4 = free-run5 = unknown · Integer32

BITS/SyncE DPLL states.

jnxClksyncDpllStateStr

1.3.6.1.4.1.2636.3.75.1.3.20

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..255) · OCTET STRING · hint 255a

Dpll state in string format.

jnxTimingEventPtpServoStatus

1.3.6.1.4.1.2636.3.75.1.2.12

A trap which signifies that PTP servo state (Init, Acquiring, PhaseAligned, FreeRun, Holdover). jnxPtpServoState indicates the ptp servo status jnxPtpServoStateStr indicates the ptp servo status in string format.

jnxPtpServoState

1.3.6.1.4.1.2636.3.75.1.3.10

INTEGER0 = init1 = free-run2 = holdover3 = acquiring4 = freq-locked5 = phase-aligned · Integer32

PTP servo states.

jnxPtpServoStateStr

1.3.6.1.4.1.2636.3.75.1.3.21

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..255) · OCTET STRING · hint 255a

PTP servo states in string format.

jnxTimingEventPtpGMClockClassChange

1.3.6.1.4.1.2636.3.75.1.2.13

A trap which signifies PTP clock class changes. jnxPtpGmId indicates the ptp Grand Master clock-id jnxPtpClass indicates the ptp Grand Master clock status.

jnxPtpGmId

1.3.6.1.4.1.2636.3.75.1.3.13

JnxPtpClockIdTCClock Identifier. SIZE (8) · OCTET STRING

PTP Grand Master clock-id.

jnxPtpClass

1.3.6.1.4.1.2636.3.75.1.3.11

Integer32

PTP clock status.

jnxTimingEventPtpGMClockAccuracyChange

1.3.6.1.4.1.2636.3.75.1.2.14

A trap which signifies PTP clock accuracy changes. jnxPtpGmId indicates the ptp Grand Master clock-id jnxPtpAccuracy indicates the ptp Grand Master clock accuracy.

jnxPtpGmId

1.3.6.1.4.1.2636.3.75.1.3.13

JnxPtpClockIdTCClock Identifier. SIZE (8) · OCTET STRING

PTP Grand Master clock-id.

jnxPtpAccuracy

1.3.6.1.4.1.2636.3.75.1.3.12

Integer32

PTP clock accuracy.

jnxTimingEventPtpGMChange

1.3.6.1.4.1.2636.3.75.1.2.15

A trap which signifies PTP Grand Master changes. jnxPtpGmId indicates the ptp Grand Master clock-id.

jnxPtpGmId

1.3.6.1.4.1.2636.3.75.1.3.13

JnxPtpClockIdTCClock Identifier. SIZE (8) · OCTET STRING

PTP Grand Master clock-id.

jnxTimingEventHybridStatus

1.3.6.1.4.1.2636.3.75.1.2.16

A trap which signifies that Hybrid state (Init, FreqAcq, FreqLckPhaseAcq, FreqPhaseLck). jnxClksyncHybridState indicates the hybrid status jnxClksyncHybridStateStr indicates the hybrid status in string format.

jnxClksyncHybridState

1.3.6.1.4.1.2636.3.75.1.3.17

INTEGER0 = init1 = freq-acq2 = freqLck-phaseAcq13 = freqLck-phaseAcq24 = freqLck-phaseAcq35 = freq-phase-lck · Integer32

hybrid states.

jnxClksyncHybridStateStr

1.3.6.1.4.1.2636.3.75.1.3.22

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..255) · OCTET STRING · hint 255a

hybrid states in string format.

jnxTimingEventLedColorChange

1.3.6.1.4.1.2636.3.75.1.2.19

A trap which signifies TX SSM/ESMC quality level changed. jnxClksyncIfIndex is the interface index jnxClksyncIntfName is the interface name jnxClksyncColorStr is the color of the LED unit.

jnxClksyncIfIndex

1.3.6.1.4.1.2636.3.75.1.3.2

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

Snmp ifIndex of member interface.

jnxClksyncIntfName

1.3.6.1.4.1.2636.3.75.1.3.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..255) · OCTET STRING · hint 255a

Interface name.

jnxClksyncColorStr

1.3.6.1.4.1.2636.3.75.1.3.23

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..255) · OCTET STRING · hint 255a

Color of the LED unit.

jnxTimingPhaseOffsetThresholdExceeded

1.3.6.1.4.1.2636.3.75.1.2.20

A trap which signifies Passive Port Threshold Exceeded. jnxPtpPhaseOffsetThresholdExceeded indicates whether the Phase Threshold of the monitored Passive Port has exceeded the configured Max Phase Offset Threshold as per.

jnxPtpPhaseOffsetThresholdExceeded

1.3.6.1.4.1.2636.3.75.1.3.24

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..255) · OCTET STRING · hint 255a

Indicates whether the Phase Threshold of the monitored Passive Port has exceeded the configured Max Phase Offset Threshold as per Annex G of ITU-T G.8275.1

jnxTimingEventPhaseErrorHoldoverStarted

1.3.6.1.4.1.2636.3.75.1.2.21

A trap which signifies holdover started after phase-error-limit exceeded. jnxPtpPhaseCorrection is the attempted phase correction when threshold exceeded jnxPtpPhaseErrorRelativeThreshold is the configured phase-error-limit jnxPtpPhaseMonitoringHoldoverLimit is the max holdover time jnxPtpPhaseMonitoringSynceHoldover is if SyncE is configured to go to holdover jnxPtpPhaseMonitoringPtpIntfName is the monitored PTP interface jnxPtpPhaseMonitoringSynceIntfName is the locked SyncE source prior to holdover

jnxPtpPhaseCorrection

1.3.6.1.4.1.2636.3.75.1.3.44

Integer64A 64-bit signed integer. The value is restricted to the BER serialization of the following ASN.1 type: I64TYPE ::= [122] IMPLICIT I64Type (note: the value 122 is the sum of '30'h and '4a'h) The BER serialization of the length for values of this type must use the definite length, short encoding form. For example, the BER serialization of value 129 of type I64TYPE is '9f7a020081'h. (The tag is '9f7a'h; the length is '02'h; and the value is '0081'h.) The BER serialization of value '9f7a020081'h of data type Opaque is '44059f7a020081'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a020081'h.) Also for example, the BER serialization of value -129 of type I64TYPE is '9f7a02ff7f'h. (The tag is '9f7a'h; the length is '02'h; and the value is 'ff7f'h.) The BER serialization of value '9f7a02ff7f'h of data type Opaque is '44059f7a02ff7f'h. (The tag is '44'h; the length is '05'h; and the value is '9f7a02ff7f'h.) SIZE (4..11) · Opaque

The ignored phase corrrection when holdover started due to the phase-error-limit feature

jnxPtpPhaseErrorRelativeThreshold

1.3.6.1.4.1.2636.3.75.1.3.39

Unsigned32 (250..10000)

The currently configured phase-error-limit threshold

jnxPtpPhaseMonitoringHoldoverLimit

1.3.6.1.4.1.2636.3.75.1.3.40

Unsigned32 (5..10080)

The currently configured phase-error-limit max holdover time

jnxPtpPhaseMonitoringSynceHoldover

1.3.6.1.4.1.2636.3.75.1.3.41

INTEGER0 = false1 = true · Integer32

If SyncE can go to holdover when phase-error-limit holdover occurs

jnxPtpPhaseMonitoringPtpIntfName

1.3.6.1.4.1.2636.3.75.1.3.42

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..255) · OCTET STRING · hint 255a

The PTP interface being monitored for the phase-error-limit feature

jnxPtpPhaseMonitoringSynceIntfName

1.3.6.1.4.1.2636.3.75.1.3.43

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..255) · OCTET STRING · hint 255a

The currently locked SyncE source while monitoring PTP for phase-error-limit feature, or previously locked if in SyncE holdover due to the feature. Not present if SyncE holdover isn't configured

jnxTimingEventPhaseErrorHoldoverEnded

1.3.6.1.4.1.2636.3.75.1.2.22

A trap which signifies holdover from phase-error-limit feature ended jnxPtpPhaseMonitoringReason is the reason why holdover ended jnxPtpPhaseErrorRelativeThreshold is the configured phase-error-limit jnxPtpPhaseMonitoringHoldoverLimit is the max holdover time jnxPtpPhaseMonitoringSynceHoldover is if SyncE is configured to go to holdover jnxPtpPhaseMonitoringPtpIntfName is the monitored PTP interface prior to holdover jnxPtpPhaseMonitoringSynceIntfName is the locked SyncE source prior to holdover

jnxPtpPhaseMonitoringReason

1.3.6.1.4.1.2636.3.75.1.3.45

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..255) · OCTET STRING · hint 255a

The reason for the occurrence of some phase-monitoring event

jnxPtpPhaseErrorRelativeThreshold

1.3.6.1.4.1.2636.3.75.1.3.39

Unsigned32 (250..10000)

The currently configured phase-error-limit threshold

jnxPtpPhaseMonitoringHoldoverLimit

1.3.6.1.4.1.2636.3.75.1.3.40

Unsigned32 (5..10080)

The currently configured phase-error-limit max holdover time

jnxPtpPhaseMonitoringSynceHoldover

1.3.6.1.4.1.2636.3.75.1.3.41

INTEGER0 = false1 = true · Integer32

If SyncE can go to holdover when phase-error-limit holdover occurs

jnxPtpPhaseMonitoringPtpIntfName

1.3.6.1.4.1.2636.3.75.1.3.42

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..255) · OCTET STRING · hint 255a

The PTP interface being monitored for the phase-error-limit feature

jnxPtpPhaseMonitoringSynceIntfName

1.3.6.1.4.1.2636.3.75.1.3.43

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..255) · OCTET STRING · hint 255a

The currently locked SyncE source while monitoring PTP for phase-error-limit feature, or previously locked if in SyncE holdover due to the feature. Not present if SyncE holdover isn't configured

↑ To TOC