Description

This KB describes the symptoms which may trigger backup RE reboot due to high memory usage caused by link flaps.

Symptoms

Memory leak may occur on Backup RE, when the contribute nh flap , such as member interface of AE is brought down or brought up. The memory leak may occur when building unilist nexthop in backup rpd.


The following log may help identify the issue:


user@device> show system processes extensive | match % | except " 0.00%" | except "Inuse|idle|nhinfo"

67129 root 36 0 26768M 25700M CPU5 5 55:05 23.00% rpd{rpd}


user@device> show system processes extensive | match % | except " 0.00%" | except "Inuse|idle|nhinfo"

67129 root 23 0 27488M 26273M kqread 5 67:36 6.40% rpd{rpd}


Solution

We observed high memory usage on the RE.


Issue is related to the below PR.


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

 

The memory high process started on Mar 23 06:

 

$ zmore messages* | grep "Mar " | grep "rt_pfe_veto"

Mar 23 06:20:03.916 2025  kernel: %KERN-3: rt_pfe_veto: Severe memory pressure, low-free-pages is below threshold. Op 1 err 12, rtsm_id 0:-1, msg type 10, veto simulation: 0

Mar 23 06:20:03.960 2025  kernel: %KERN-3: rt_pfe_veto: number of pages free = (229174) number of pages in cache = (0) free page threshold = (156341) number of free pages desired = (302011) veto threshold (high) = (229176) veto threshold (low) = (156341) error = No Memory curproc = ksyncd

Mar 23 06:20:03.960 2025  kernel: %KERN-3: rt_pfe_veto: Possible slowest client is xdpc1. States processed - 139755335. States to be processed - 214672471

Mar 23 06:20:03.960 2025  kernel: %KERN-3: rt_pfe_veto: Possible second slowest client is xdpc2. States processed - 145602419. States to be processed - 208825387

Mar 23 06:20:08.561 2025 kernel: %KERN-3: rt_pfe_veto: Severe memory pressure, low-free-pages is below threshold. Op 1 err 12, rtsm_id 0:-1, msg type 10, veto simulation: 0

Mar 23 06:20:08.561 2025  kernel: %KERN-3: rt_pfe_veto: number of pag


On all Junos platforms with dual REs, rpd memory leak may be seen when an AE member interface flaps ,or contribute nh flap, or immediate restart of master RE.

The memory leak was observed be around 32 bytes per session, the leak is only seen when an unilist nexthop have more than 8 legs.


Modification History

2025-07-08 : Article Created