Description

When having MX-SPC3 in MX-VC chassis, flooding of l2ald messages logs can be seen:

Jan 10 04:48:03.247 jtac-mx960-r2045-re0 l2ald[16748]: L2ALD_DUPLICATE_CONNECTIONS: Duplicate connection for peer DPC-0 (Ident: 136). Disconnecting...

Jan 10 04:48:03.947 jtac-mx960-r2045-re0 l2ald[16748]: L2ALD_DUPLICATE_CONNECTIONS: Duplicate connection for peer DPC-0 (Ident: 137). Disconnecting...

Jan 10 04:48:04.266 jtac-mx960-r2045-re0 l2ald[16748]: L2ALD_DUPLICATE_CONNECTIONS: Duplicate connection for peer DPC-0 (Ident: 136). Disconnecting...

Jan 10 04:48:04.960 jtac-mx960-r2045-re0 l2ald[16748]: L2ALD_DUPLICATE_CONNECTIONS: Duplicate connection for peer DPC-0 (Ident: 137). Disconnecting...

Symptoms

With MXVC and MXSPC3, continuous syslog messages "L2ALD_DUPLICATE_CONNECTIONS: Duplicate connection for peer DPC-0 (Ident: 137). Disconnecting..." can be seen.

Solution

This problem reported on MX virtual-chassis is different then the one described in TSB18039 [juniper.net], which was seen on SRX HA mode only.

On MX virtual-chassis, this problem is tracked and fixed via PR1668368.

customer is recommended to upgrade to junos:21.3R3-S2 junos:22.1R3 junos:22.2R2 junos:22.3R2 junos:22.4R1 and higher.

Modification History

2024-02-05 : Article Created