Description

This issue affects Junos platforms EX2300, EX3400, EX4300 where it runs out of memory due to events like commit config, taking RSI, addition/deletion of mac address, and the system hangs impacting any service and traffic.

 

Symptoms

This issue is seen in low platforms that might run out of memory - EX2300, EX3400, EX4300. For example, Junos platform EX4300-VC hangs due to low memory after doing the commit or taking RSI. L2ald daemon has in memory tracing mechanism, where certain events like mac address add/delete are saved in l2ald memory. By default, 1M such events will be stored which can lead to increase usage of l2ald memory causing the VC to hang. When customer observes low memory logs, they can check output of "show ethernet-switching debug-statistics memory" and see memory used by l2ald_add_ctxt_hist.

 

Solution

As workaround, set context history limit as 10k and restart l2ald process.

-------------

set protocols l2-learning global-ctx-limit 10000

restart l2-learning

 

Issue has been fixed on the following JunOS versions:

 

Resolved-In:

  • 20.4R3-S8-EVO
  • 21.2R3-S6-EVO
  • 21.3R3-S5-EVO
  • 21.4R3-S4-EVO
  • 22.1R3-S3-EVO
  • 22.2R3-S1-EVO
  • 22.3R2-S2-EVO
  • 22.3R3-EVO
  • 22.3X50-EVO
  • 22.3X80-D39-EVO
  • 22.3X80-D40-EVO
  • 22.4R2-EVO
  • 22.4R3-EVO
  • 23.1R2-EVO
  • 23.2R1-EVO
  • 23.3R1-EVO
  • junos:20.2R3-S8
  • junos:20.4R3-S8
  • junos:21.3R3-S5
  • junos:21.4R3-S4
  • junos:22.1R3-S3
  • junos:22.2R3-S1
  • junos:22.3R2-S2
  • junos:22.3R3
  • junos:22.4R2
  • junos:22.4R3
  • junos:23.1R2
  • junos:23.2R1
  • junos:23.3R1

Modification History

2023-10-13 KB Created