DCPFE Crash on QFX5200 resulting in traffic disruption
The PFE will crash and the following logs might be observed:
localre:
--------------------------------------------------------------------------
root@SW> show system uptime no-forwarding
Current time: 2025-08-11 20:58:18 UTC
Time Source: NTP CLOCK
System booted: 2019-10-10 16:39:38 UTC (304w4d 04:18 ago) >>>>>>>>>>>>>
Protocols started: 2019-10-10 16:40:36 UTC (304w4d 04:17 ago)
Last configured: 2023-01-18 21:51:37 UTC (133w4d 23:06 ago) by auto806983
8:58PM up 2132 days, 4:19, 1 users, load averages: 0.47, 0.31, 0.26
root@SW> show chassis fpc detail
Slot 0 information:
State Online
Total CPU DRAM 3907 MB
Total SRAM 0 MB
Total SDRAM 0 MB
Start time 2025-08-11 17:46:02 UTC
Uptime 3 hours, 12 minutes, 17 seconds >>>>>>>>>>>>>
root@SW> show version detail no-forwarding
Hostname: SW
Model: qfx5200-32c-32q
Junos: 15.1X53-D231.2
fpc0 [auto-chan] pic:0 link:21 p-mode:40g flags:1 Split Cable detected. Channelizing the port. >>>>>>>>>>>>>
fpc0 [auto-chan] pic:0 link:5 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:7 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:8 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:9 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:10 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:11 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:12 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:13 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:14 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 qsfp_tk_cdr_control: qsfp-0/0/5 channelization not yet supported
fpc0 qsfp_tk_cdr_control: qsfp-0/0/13 channelization not yet supported
fpc0 qsfp_tk_cdr_control: qsfp-0/0/14 channelization not yet supported
fpc0 [auto-chan] pic:0 link:12 p-mode:25g flags:3 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:8 p-mode:25g flags:3 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:7 p-mode:25g flags:3 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:14 p-mode:25g flags:3 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:10 p-mode:25g flags:3 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:9 p-mode:25g flags:3 Split Cable detected. Channelizing the port.
fpc0 [auto-chan] pic:0 link:14 p-mode:50g flags:3 Split Cable detected. Channelizing the port.
…… <auto channelization still happening after PFE crash>
fpc0 [auto-chan] pic:0 link:2 p-mode:25g flags:1 Split Cable detected. Channelizing the port.
fpc0 qsfp_tk_cdr_control: qsfp-0/0/2 channelization not yet supported
The issue is related to auto-channelization support, an optic speed mismatch connection might cause the auto-channelization to get into an infinite loop trying to match a proper speed. In this case, due to some memory leaks, the resources get exhausted, resulting in system crash. The traffic gets disrupted when the system dcpfe restarts.
The following PR has been filed to address this issue: PR1484336
https://prsearch.juniper.net/problemreport/PR1484336
Fix available in latest JunOS code: junos:18.4R2-S9 junos:19.4R3-S8 junos:20.1R3 junos:20.2R3-S4 junos:20.3R2 junos:20.3R3 junos:20.3X75-D30 junos:20.3X75-D40 junos:20.4R2 junos:21.1R1 junos:21.2R1 junos:23.4R2