[ACX EVO] FEB 0 Major Errors due to broadsync_lock_failure

EMF_EVO_ALARM_SET: Alarm set and cleared

Current Business Impact : No ,Impacted Users : none

In Junos OS Evolved ACX platforms, PTP relies on BroadSync module for hardware time-stamping and clock synchronization. If BroadSync becomes unavailable, the platform cannot provide accurate PTP timing and "broadsync lock failure" alarms are seen. Due to this broadsync lock failure, the platform can no longer maintain hardware assisted timing accuracy, which directly affects PTP operation. While PTP sessions may remain established, the clock transitions to a degraded or faulty state to prevent distribution of inaccurate time. The alarms self-clear when PTP functionality is fully restored once BroadSync operation is recovered. This issue has no impact unless Precision Time Protocol (PTP) timing functionality is in use and deployments not relying on PTP are unaffected. 

Below alarms/logs are seen when this issue is hit:

Mar 9 15:19:00.137+07:00 router-re0 evo-pfemand - [t:3496] [Info] Module: BrcmResiliencyCmError::BrcmCmErrorSet() moduleHandle: 0 pfeId: 0 asicId: 10000 erroId: 551892
Mar 9 15:19:00.138+07:00 router-re0 resiliencyd - CMError: /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure (0x551892), scope: pfe, category: functional, severity: major, module: dnxj2_feb, type: broadsync_lock_failure, oc_category: default
Mar 9 15:19:00.138+07:00 router-re0 resiliencyd - Performing action get-state for error /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure (0x551892) in module: dnxj2_feb with scope: pfe category: functional level: major, oc_category: default
Mar 9 15:19:00.244+07:00 router-re0 resiliencyd - Performing action cmalarm for error /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure (0x551892) in module: dnxj2_feb with scope: pfe category: functional level: major, oc_category: default
Mar 9 15:19:00.245+07:00 router-re0 resiliencyd - EMF_EVO_ALARM_SET: Alarm set: FEB color=red, class=CHASSIS, reason=FEB 0 Major Errors
Mar 9 15:19:00.245+07:00 router-re0 resiliencyd - Cmerror Op Set: dnxj2_feb: broadsync_lock_failure (URI: /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure)

Mar 9 15:19:10.145+07:00 router-re0 evo-pfemand - [t:3496] [Info] Module: BrcmResiliencyCmError::BrcmCmErrorClear() moduleHandle: 0 pfeId: 0 erroId: 551892
Mar 9 15:19:10.145+07:00 router-re0 evo-pfemand - [t:3496] [Info] BrcmPlusResiliency: Broadsync lock clear Error : From unit: 0 Status : 3
Mar 9 15:19:10.146+07:00 router-re0 resiliencyd - cmerror_level_decrement: for /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure (0x551892), scope: pfe, category: functional, severity: major, module: dnxj2_feb, type: broadsync_lock_failure
Mar 9 15:19:10.146+07:00 router-re0 resiliencyd - Performing action clear-cmalarm for error /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure (0x551892) in module: dnxj2_feb with scope: pfe category: functional level: major, oc_category: default
Mar 9 15:19:10.146+07:00 router-re0 resiliencyd - EMF_EVO_ALARM_CLR: Alarm cleared: FEB color=red, class=CHASSIS, reason=FEB 0 Major Errors
Mar 9 15:19:10.146+07:00 router-re0 resiliencyd - Cmerror Op Clear: dnxj2_feb: broadsync_lock_failure (URI: /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure)

System Inactive Errors Detail Information

FEB 0

----------------------------------------------------------------

Error Name      : broadsync_lock_failure

Identifier      : /feb/0/evo-pfemand/0/cm/0/dnxj2_feb/0/broadsync_lock_failure

Description      : broadsync_lock_failure

State         : enabled

Scope         : pfe

Category       : functional

Level         : major

Threshold       : 1

Error limit      : 1

Occur count      : 14

Clear count      : 14

Last occurred(ms ago) : 2026-03-15 14:44:51 +07 (97962118 ms ago)

user@router-re0:pfe> show ptp version 

PTP Version Information:

 Hardware major revision : B7

 Hardware minor revision : 8

Broadsync BitClock was configured to 1 MHz, while the vendor-recommended and supported setting is 10 MHz. According to the vendor, Broadsync behavior is not guaranteed at any BitClock frequency other than 10 MHz. This mismatch is the likely root cause of the failure.

There are no visible impact to production due to these logs.

Issue has been observed in PTP-FPGA firmware B7.8 and previous version and resolved in B9_00

user@router-re0:pfe> show ptp version 

PTP Version Information:

 Hardware major revision : B9

 Hardware minor revision : 0

Resolved in :

evo:24.2R2-S6-EVO 

evo:25.2R2-S2-EVO 

evo:25.4R2-EVO 

evo:26.2R1-EVO 

evo:26.3R1-EVO 

junos:24.2R2-S6 

junos:25.2R2-S2 

junos:25.4R2 

junos:26.2R1 

junos:26.3R1