Description

Customer has reported that they are observing NH failure related logs on their router.

 

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (290784) for deletion

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (290785) for deletion

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (315977) for deletion

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (315978) for deletion

Symptoms

 

 

FPC crash is observed due to Failed NH leak and following logs will be seen post LSP change

 

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (290784) for deletion

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (290785) for deletion

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (315977) for deletion

%PFE-3: fpc2 PFE_ERROR_NOT_FOUND: NH: Failed to find nh (315978) for deletion

 

when we have EVPN ELAN over SRv6 is enabled or evpn signaling/Srv6 services is used and whenever there is a route churn due to interface flaps, LSP flaps, LSP path down/LSP change path.

 

ELAN over SRv6 is not being cleaned up correctly consequently causes JNH leak leading to fpc crash.

 

 

      family evpn {

        signaling {

          advertise-srv6-service;

          accept-srv6-service;

        }

      }

  

Solution

 

Reported issue is fixed through already existing PR shared below:

  

PR1796406- Incomplete Clean up of multicast check with ELAN over SRv6. 

 

junos:23.4R1-S1 junos:23.4R2 junos:24.1R1 junos:24.1R2 junos:24.2R1

Modification History

2024-04-29 : Article Created