Description

No service impact, but most LSPs are getting LSP selfping timeout log.

 

e.g.

Oct 25 11:25:02.333 2023 abc rpd[11773]: RPD_MPLS_LSP_SELFPING_TIMEOUT: MPLS LSP Self-ping timeout for LSP 189-to-42, duration: 1800 s

Oct 25 11:25:33.546 2023 abc rpd[11773]: RPD_MPLS_LSP_SELFPING_TIMEOUT: MPLS LSP Self-ping timeout for LSP 189-to-135, duration: 1800 s

 

 

 

 

Symptoms

No service impact, but most LSPs are getting LSP selfping timeout log.

 

e.g.

Oct 25 11:25:02.333 2023 abc rpd[11773]: RPD_MPLS_LSP_SELFPING_TIMEOUT: MPLS LSP Self-ping timeout for LSP 189-to-42, duration: 1800 s

Oct 25 11:25:33.546 2023 abc rpd[11773]: RPD_MPLS_LSP_SELFPING_TIMEOUT: MPLS LSP Self-ping timeout for LSP 189-to-135, duration: 1800 s

 

Solution

Need to allow both source and destination IP addresses of UDP port 8530 on RE protection filter.

Source IP address = 100.69.15.45

Destination IP address = 100.69.0.189

 

 

R1-ingress-LSR(et-0/0/0: 100.69.15.45/31) -- R2 -- R3 -- R4

R1 Lo0.0= 100.69.0.189

R2 Lo0.0 = 100.69.0.203

R3 Lo0.0 = 100.69.0.188

R4 Lo0.0 = 100.69.0.186

 

 

Below configuration only allowed lo0.0 addresses of LSRs, no allowed prefix on source address of 100.69.15.45, hence the LSP Selfping timeout.

 

 

policy-options {

   prefix-list core_subnets {

   100.69.0.0/21;  <<< this is between 100.69.0.0 to 100.69.7.255

   } 

  

           term accept-lsp_self_ping {

               from {

                   source-prefix-list {

                       core_subnets;

                   }   

                   protocol udp;

                   port 8503;

               }

               then {

                   count self_ping;

                   accept;

               }

           }

Modification History

2024-03-25 : Article Created