In this article we will understand the meaning of log messages and how such log messages are repeated.

You would notice below logs messages in the device but no RSVP LSP is flapped.

Jun 26 14:30:04.193 2024 Router-1 rpd[6624]: RPD_MPLS_PATH_UP: MPLS path up on LSP 172.00.XX.X:100:3:12472:mvpn:60082 path bandwidth 100000 bps
Jun 26 14:30:04.194 2024 Router-1 rpd[6624]: RPD_MPLS_LSP_UP: MPLS LSP 172.00.XX.X:100:3:12472:mvpn:60082 up on dynamic() Route 172.17.X.X(flag=0x20) 68.1.X.X(Label=56640) 172.17.X.X(flag=0x20) 68.1.X.X(Label=381790) 172.17.X.X(flag=0x20) 68.1.X>X(Label=921946) 172.17.X.X(flag=0x20) 68.1.X.X(Label=531356) 172.17.X.X(flag=0x20) 68.1.X.X(Label=170200) 172.17.X.X(flag=0x20) 68.1.X.X(Label=0) lsp bandwidth 100000 bps
Jun 26 14:30:04.996 2024 Router-1 rpd[6624]: RPD_MPLS_LSP_DOWN: MPLS LSP 172.00.XX.X:100:3:12472:mvpn:75062 down on dynamic()
Jun 26 14:30:04.997 2024 Router-1 rpd[6624]: RPD_MPLS_PATH_DOWN: MPLS path down on LSP 172.00.XX.X:100:3:12472:mvpn:75062
Jun 26 14:30:05.127 2024 Router-1 rpd[6624]: RPD_MPLS_PATH_UP: MPLS path up on LSP 172.00.XX.X:100:3:12472:mvpn:63032 path bandwidth 100000 bps
Jun 26 14:30:05.129 2024 Router-1 rpd[6624]: RPD_MPLS_LSP_UP: MPLS LSP 172.00.XX.X:100:3:12472:mvpn:63032 up on dynamic() Route 172.17.X.X(flag=0x20) 68.1.X.X(Label=56642) 172.17.X.X(flag=0x20) 68.1.X.X(Label=381792) 172.17.X.X(flag=0x20) 68.1.X>X(Label=921948) 172.17.X.X(flag=0x20) 68.1.0.143(Label=531358) 172.17.X.X(flag=0x20) 68.1.X.X(Label=170202) 172.17.X.X(flag=0x20) 68.1.X.X(Label=0) lsp bandwidth 100000 bps
Jun 26 14:30:05.639 2024 Router-1 rpd[6624]: RPD_MPLS_LSP_DOWN: MPLS LSP 172.00.XX.X:100:3:12472:mvpn:59447 down on dynamic()

1) Based on the log message figure out the peer device and RD value.

Example :

Jun 26 14:30:04.193 2024 Router-1 rpd[6624]: RPD_MPLS_PATH_UP: MPLS path up on LSP 172.00.XX.X:100:3:12472:mvpn:60082 path bandwidth 100000 bps

• 172.00.XX.X is remote PE router-ID 
• 100:3 is the RD value configured.
• IEEE 802.3 Slow_Protocols_Multicast address

2) On the peer device : 172.00.XX.X. check for instance configured with Route-Distinguisher 100:3. 

As per below example there is a MVPN instance and provider-tunnel is configured at Selective and create-new-ucast-tunnel;

Router-1 Config:

 MVPN {
instance-type vrf;
  interface xe-0/0/22.0;
  interface ae5.3;
  interface ae99.10;
  interface lo0.1;
  route-distinguisher 100:3;
  provider-tunnel {
   selective {
    group 224.0.0.0/4 {
     source 0.0.0.0/0 {
      ingress-replication {
       create-new-ucast-tunnel;
       label-switched-path {
        label-switched-path-template {
         MVPN-LSP-TEMPLATE;

As per above configuration when create-new-ucast-tunnel is configured, each time a new destination is added to the multicast distribution tree, a new unicast tunnel to the destination is created in the ingress replication tunnel. The new tunnel is deleted if the destination is no longer needed
 

Reference : https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/ingress-replication-mvpn-new-ucast-tunnel.html