This article explains the reason for the below log message.
PFE-5: fpc0 Error: /fpc/0/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_PGQ_MISC_INT_EVENTS_ENQ_192K_VIOL (0x210107), scope: pfe, category: functional, severity: major, module: PE Chip, type: Description for PECHIP_CMERROR_PGQ_MISC_INT_EVENTS_ENQ_192K_VIOL
Customer might face an issue where outage is noticed and the below log is observed.
Feb 29 00:16:51 lab : %PFE-5: fpc0 Error: /fpc/0/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_PGQ_MISC_INT_EVENTS_ENQ_192K_VIOL (0x210107), scope: pfe, category: functional, severity: major, module: PE Chip, type: Description for PECHIP_CMERROR_PGQ_MISC_INT_EVENTS_ENQ_192K_VIOL
Feb 29 00:16:51 lab : %PFE-5: fpc0 Performing action get-state for error /fpc/0/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_PGQ_MISC_INT_EVENTS_ENQ_192K_VIOL (0x210107) in module: PE Chip with scope: pfe category: functional level: major
Feb 29 00:16:51 lab : %PFE-5: fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_PGQ_MISC_INT_EVENTS_ENQ_192K_VIOL (0x210107) in module: PE Chip with scope: pfe category: functional level: major
Feb 29 00:16:51 lab : %PFE-3: fpc0 Cmerror Op Set: PE Chip: PE1[1]: PGQ:misc_intr: 0x00000020: Enqueue of a packet with out-of-range VOQ in 192K-VOQ mode (URI: /fpc/0/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_PGQ_MISC_INT_EVENTS_ENQ_192K_VIOL)
Feb 29 00:16:51 lab : %PFE-5: fpc0 Error: /fpc/0/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_CM_INT_REG_DCHK_PIPE (0x21011a), scope: pfe, category: functional, severity: fatal, module: PE Chip, type: Description for PECHIP_CMERROR_CM_INT_REG_DCHK_PIPE
Feb 29 00:16:51 lab : %PFE-5: fpc0 Performing action disable-pfe for error /fpc/0/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_CM_INT_REG_DCHK_PIPE (0x21011a) in module: PE Chip with scope: pfe category: functional level: fatal
Feb 29 00:16:55 lab : %PFE-3: fpc0 pechip_set_pfe_disabled:976: PECHIP[3]: PFE Marked Disabled !!!
Feb 29 00:16:55 lab : %PFE-3: fpc0 pechip_set_pfe_disabled:976: PECHIP[4]: PFE Marked Disabled !!!
Feb 29 00:16:54 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/13 (275) on pfe-3
Feb 29 00:16:54 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/15 (277) on pfe-3
Feb 29 00:16:54 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/17 (279) on pfe-3
Feb 29 00:16:54 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/19 (281) on pfe-3
Feb 29 00:16:55 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/22 (284) on pfe-4
Feb 29 00:16:55 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/20 (282) on pfe-4
Feb 29 00:16:55 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/24 (286) on pfe-4
Feb 29 00:16:55 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/26 (288) on pfe-4
Feb 29 00:16:55 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/28 (290) on pfe-4
Feb 29 00:16:55 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/21 (283) on pfe-5
Feb 29 00:16:55 lab : %PFE-3: fpc0 ISSUING ifd-down for et-0/0/23 (285) on pfe-5
An Improper Check or Handling of Exceptional Conditions vulnerability in packet processing of Juniper Networks Junos OS allows an unauthenticated, adjacent attacker on the local broadcast domain sending a malformed packet to the device, causing all PFEs other than the inbound PFE to wedge and to eventually restart, resulting in a Denial of Service (DoS) condition. Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition.
This issue can only be triggered by sending a specific malformed packet to the device. Transit traffic does not trigger this issue.
the error may get clear on its own however the pfe would remain disabled and the relative interface would reamain down until the affected FPC is rebooted.
Reboot the affected FPC to bring the pfe back up.