Timing Defects and Event Management on Routing Platforms

Junos OS supports defect and event management capabilities for timing features. Defects and events are notified in the form of SNMP traps. These SNMP traps are logged into the system log-file (var/log/snmpd).

Junos OS and Junos OS Evolved support defect and event management capabilities for timing features. Defects and events are notified in the form of SNMP traps and these SNMP traps are logged into the system log-file (var/log/snmpd). For each of the SNMP traps (timing defects and timing events) that are generated, a message is logged in the clksyncd file (var/log/clksyncd).

Table 1 shows the list of SNMP trap notifications for timing defects and events supported.

Table 1: SNMP trap notifications for timing defects and events
SNMP Trap	Notification Type	Description
jnxTimingFaultLOS	Defects (Set, Clear)	Set denotes loss of signal Clear denotes loss of signal is cleared
jnxTimingFaultEFD	Defects (Set, Clear)	Denotes exceeded frequency deviation
jnxTimingFaultLOESMC	Defects (Set, Clear)	Denotes loss of Ethernet Synchronization Message Channel (ESMC)
jnxTimingFaultQLFail	Defects (Set, Clear)	Denotes failure in quality level
jnxTimingFaultLTI	Defects (Set, Clear)	Denotes loss of timing information
jnxTimingFaultPriSrcFailed	Defects	Denotes the failure of timeTransmitter source
jnxTimingFaultSecSrcFailed	Defects	Denotes the failure of secondary source
jnxTimingFaultPtpUniNegRateReject	Defects	When acting as timeTransmitter, this SNMP trap denotes failure or rejects timeReceivers for signaling messages. When acting as a timeReceiver, this SNMP trap denotes failure or timeReceiver stops receiving signaling messages
jnxTimingEventPriSrcRecovered	Events	Denotes the recovery of timeTransmitter source
jnxTimingEventSecSrcRecovered	Events	Denotes the recovery of secondary source
jnxTimingEventPriRefChanged	Events	Denotes a change in timeTransmitter reference such as a change in logical interface or a change from SyncE to BITS/external interface)
jnxTimingEventSecRefChanged	Events	Denotes a change in secondary reference such as a change in logical interface
jnxTimingEventQLChangedRx (ACX7332, ACX7348)	Events	Denotes a change in quality level at Receiver SSM/ESMC
jnxTimingEventQLChangedTx (ACX7332, ACX7348)	Events	Denotes a change in quality level at Transmitter SSM/ESMC
jnxTimingEventDpllStatus	Events	Denotes the DPLL status (SyncE, BITS, Hybrid)
jnxTimingEventSynceDpllStatus (ACX7332, ACX7348)	Events	Denotes the following SyncE DPLL states: jnxClksyncIfIndex: Frequency is derived from this interface index. jnxClksyncIntfName: Frequency is derived from this interface name. jnxClksyncDpllState: DPLL status. jnxClksyncDpllStateStr: DPLL status in string format.
jnxTimingEventPtpServoStatus	Events	Denotes the following PTP Servo states: INITIALIZING ACQUIRING (TimeTransmitter is elected and servo starts acquiring lock) PHASE ALIGNED (Locked to TimeTransmitter) FREERUN (no PTP source available) HOLDOVER (Member locked to PTP for more than 12 hours and then loses all the PTP sources)
jnxTimingEventPtpClockClassChange	Events	Denotes a change in PTP clock class
jnxTimingEventPtpClockAccuracyChange	Events	Denotes a change in PTP accuracy
jnxTimingEventPtpGMChange	Events	Denotes a change in PTP grandmaster clock
jnxTimingEventHybridStatus	Events	Denotes the following hybrid states: INITIALIZING ACQUIRING (TimeTransmitter is elected and servo starts acquiring lock) FREQUENCY LOCKED (Frequency locked but acquiring phase) PHASE ALIGNED (Frequency and phase locked)
jnxTimingEventPhaseErrorHoldoverStarted	Events	Denotes that the monitored phase threshold has been exceeded for 10 measurement windows (MWs) and therefore the PTP servo has moved to the holdover state. SyncE will also get into holdover state if jnxPtpPhaseErrorMonitoringSynceHoldover is 1. This event yields: jnxPtpPhaseCorrection for the attempted ignored phase correction when holdover started jnxPtpPhaseErrorRelativeThreshold for the configured threshold jnxPtpPhaseMonitoringHoldoverLimit for the configured holdover time limit for this feature jnxPtpPhaseMonitoringSynceHoldover if SyncE was configured to go into holdover too jnxPtpPhaseMonitoringPtpIntfName for the monitored PTP interface name jnxPtpPhaseMonitoringSynceIntfName for the interface name of the locked SyncE source name prior to the start of holdover. This is blank if jnxPtpPhaseMonitoringSynceHoldover is 0 or if SyncE wasn’t locked at the time Note: This event is applicable on platforms that support the Phase Adjustment Mitigation feature.
jnxTimingEventPhaseErrorHoldoverEnded	Events	Denotes that the servo has stopped ignoring phase adjustments and has come out of holdover. SyncE will also come out of holdover if it was configured to go into holdover after the threshold was exceeded. This event yields: jnxPtpPhaseMonitoringReason for why phase corrections stopped being ignored (eg: PTP master switch, phase back under threshold for 10MWs or more, etc.) jnxPtpPhaseErrorRelativeThreshold for the configured threshold jnxPtpPhaseMonitoringHoldoverLimit for the configured holdover time limit for this feature jnxPtpPhaseMonitoringSynceHoldover for if SyncE was configured to go into holdover too jnxPtpPhaseMonitoringPtpIntfName for the previously-monitored PTP interface name jnxPtpPhaseMonitoringSynceIntfName for the interface name of the locked SyncE source name prior to the start of holdover. This is blank if jnxPtpPhaseMonitoringSynceHoldover is 0 or if SyncE wasn’t locked at the time Note: This event is applicable on platforms that support the Phase Adjustment Mitigation feature.

To configure and generate timing defects and events trap notifications, include the timing-events statement at the [edit snmp trap-group trap-group-name categories] hierarchy level as shown below:

The following is a sample configuration for SNMP timing in ACX Series routers:

Platform-Specific Timing Defects and Event Management Behavior

Use Feature Explorer to confirm platform and release support for specific features.

Use the following table to review platform-specific behaviors for your platform:

Table 2: Platform-Specific Behavior
Platform	Difference
ACX Series	Starting Junos OS Evolved release version 24.2R1, ACX7332 and ACX7348 devices support additional defect management capability for the SYNCE, PTP MIB (SNMP traps) and display error messages for timing features. For details, see SNMP MIB for Timing on Routing Platforms. ACX7020-AC, ACX7020-DC, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X devices also support additional defect management capability and display error messages for timing features. For details, see SNMP MIB for Timing on Routing Platforms.
PTX Series	PTX10004 and PTX10008 devices also support additional defect management capability and display error messages for timing features. For details, see SNMP MIB for Timing on Routing Platforms.