PFE might get reset and might lead to a complete outage. Interfaces might be up, but without traffic.


When the issue happens, the FPC crashes and generates core dump. 

More the scale, greater the probability of hitting this issue. 

The core-dump files could be seen by executing CLI command "show system core-dumps": 

user@device> show system core-dumps
fpc0:
--------------------------------------------------------------------------
/var/crash/*core*: No such file or directory
-rw-rw----  1 root  field   <size> <timestamp>  /var/tmp/pfex_junos.core.0.gz
...

This issue might be seen if the following conditions are met:
* On all Junos platforms with scaled traffic scenario
* The l2alm frees the memory allocated to IPC messages twice due to l2alm fails to send IPC message to the l2ald and retries later

On all Junos platforms, in scale scenarios, when l2alm fails to send IPC message to l2ald due to busy socket communication, it retries. 


In both the first attempt and the subsequent retries l2alm frees the memory allocated to IPC message (i.e. double free). 


It might result in FPC to crash. This is a rare timing issue.


Issue is resolved in the below releases:


evo:21.2R3-EVO evo:21.3R1-EVO junos:18.3R3-S5 junos:18.4R3-S9 junos:19.1R3-S6 junos:19.2R3-S3 junos:19.3R3-S3 junos:19.4R3-S6 junos:20.2R3-S3 junos:20.2R3-S4 junos:20.2R3-S7 junos:20.4R3 junos:21.1R2 junos:21.1R3 junos:21.2R3 junos:21.3R1


https://prsearch.juniper.net/problemreport/PR1596615