Routing

 View Only

  • 1.  MX480 – Persistent PPE and HEM Errors After Installing Additional MPC5E Cards

    Posted 07-08-2025 08:05

    Hi everyone,

    I'm running an MX480 with the following hardware:

    Routing Engines:

    RE-S-1800x4

    RE-S-1800x4

    Line Cards:

    Slot 0: MPC5E 3D Q 24XGE+6XLG
    Slot 1: MPC5E 3D Q 24XGE+6XLG
    Slot 2: MPC 3D 16x 10GE
    Slot 3: MPC 3D 16x 10GE
    Slot 4: MPC5E 3D 24XGE+6XLGE
    Slot 5: MPC5E 3D 24XGE+6XLGE

    Junos version: 19.4R1-S2.2

    Lately I've been seeing persistent log errors like these:


    Jul  8 15:01:43  RE0-MX480 fpc0 ppe_error_interrupt(4801): XL[0:0]_PPE  1 Errors sync xtxn error
    Jul  8 15:01:43  RE0-MX480 fpc0 hash_event_handler(655): XL[0:0].hem[0] HF_A_NOT_VLD.
    Jul  8 15:01:46  RE0-MX480 fpc1 ppe_error_interrupt(4801): XL[0:0]_PPE  1 Errors sync xtxn error
    Jul  8 15:01:46  RE0-MX480 fpc1 hash_event_handler(655): XL[0:0].hem[0] HF_A_NOT_VLD.
    Jul  8 15:01:48  RE0-MX480 fpc0 ppe_error_interrupt(4801): XL[0:0]_PPE 32 Errors sync xtxn error
    Jul  8 15:01:48  RE0-MX480 fpc0 hash_event_handler(655): XL[0:0].hem[2] HF_A_NOT_VLD.
    Jul  8 15:01:51  RE0-MX480 fpc1 ppe_error_interrupt(4801): XL[0:0]_PPE 49 Errors sync xtxn error
    Jul  8 15:01:51  RE0-MX480 fpc1 hash_event_handler(655): XL[0:0].hem[3] HF_A_NOT_VLD.
    Jul  8 15:01:53  RE0-MX480 fpc0 ppe_error_interrupt(4801): XL[0:0]_PPE 32 Errors sync xtxn error
    Jul  8 15:01:53  RE0-MX480 fpc0 hash_event_handler(655): XL[0:0].hem[2] HF_A_NOT_VLD.
    Jul  8 15:01:56  RE0-MX480 fpc1 ppe_error_interrupt(4801): XL[0:0]_PPE 16 Errors sync xtxn error
    Jul  8 15:01:56  RE0-MX480 fpc1 hash_event_handler(655): XL[0:0].hem[1] HF_A_NOT_VLD.
    Jul  8 15:01:58  RE0-MX480 fpc0 ppe_error_interrupt(4801): XL[0:0]_PPE  1 Errors sync xtxn error
    Jul  8 15:01:58  RE0-MX480 fpc0 hash_event_handler(655): XL[0:0].hem[0] HF_A_NOT_VLD.
    Jul  8 15:02:01  RE0-MX480 fpc1 ppe_error_interrupt(4801): XL[0:0]_PPE 49 Errors sync xtxn error
    Jul  8 15:02:01  RE0-MX480 fpc1 hash_event_handler(655): XL[0:0].hem[3] HF_A_NOT_VLD.
    Jul  8 15:02:03  RE0-MX480 fpc0 ppe_error_interrupt(4801): XL[0:0]_PPE  0 Errors sync xtxn error
    Jul  8 15:02:03  RE0-MX480 fpc0 hash_event_handler(655): XL[0:0].hem[0] HF_A_NOT_VLD.
    Jul  8 15:02:06  RE0-MX480 fpc1 ppe_error_interrupt(4801): XL[0:0]_PPE 32 Errors sync xtxn error
    Jul  8 15:02:06  RE0-MX480 fpc1 hash_event_handler(655): XL[0:0].hem[2] HF_A_NOT_VLD.

    These appear on both FPC0 and FPC1 and occur repeatedly every few seconds.

    I suspect this may have started after I installed the two newer MPC5E 3D 24XGE+6XLGE cards in slots 4 and 5, but I'm not completely sure.
    Has anyone else seen similar issues?
    Could this be related to Junos compatibility or firmware mismatch with the MPC5E cards?
    I'm also aware that both the RE-S-1800x4 and MPC 3D 16x10GE are now EOL, so I'm wondering:
    What is the recommended Junos version for this setup (especially with MPC5E cards)?
    Should I consider upgrading Junos to resolve these errors?
    Any input or suggestions would be appreciated.

    Thanks!



    ------------------------------
    Victor Stoliarchuk
    ------------------------------


  • 2.  RE: MX480 – Persistent PPE and HEM Errors After Installing Additional MPC5E Cards

    Posted 07-09-2025 06:19

    From 19.4, go via 20.4R3 to 21.2R3-S8. 



    ------------------------------
    Olivier Benghozi
    ------------------------------

    Original Message


  • 3.  RE: MX480 – Persistent PPE and HEM Errors After Installing Additional MPC5E Cards

    Posted 07-09-2025 10:09

    Greetings,

    To elaborate further.

    Juniper last supported software version for legacy MX hardware, as defined in TSB17733, is 21.2R3. It entered End-Of-Engineering milestone at the end of December, but EoL one is extended to End-of-June 2026. The same date is EoL milestone for hardware support.

    Regarding the messages, this CVE-2022-22249 looks like 102% match.

    Best e-gards, 

    Georgi Sinapov 

    Core Network Architect

     




    Original Message