Customer noticed during 23.4R2-S2 testing that the PE stopped advertising VPN routes to inter-as option B BGP peers.

Importing routes is not an issue when running on 22.3R3-S2.

Here's the related config:

  routing-options {
      rib bgp.rtarget.0 {
          static {
              route-target-filter 200:101/64 local;
          }
      }
      router-id 144.133.128.126;
      autonomous-system {
          65530;
          loops 2;
      }
  }
  protocols {
      bgp {
          group WER_INTER_AS_PEERS {
              traceoptions {
                  file INTER_AS_BGP size 10m files 10;
                  flag all detail;
              }
              minimum-hold-time 10;
              import WER_IMPORT;
              family inet-vpn {
                  unicast;
              }                           
              family inet6-vpn {
                  unicast;
              }
              export WER_EXPORT;
              peer-as 64515;
              neighbor 172.16.129.254 {
                  description vgrk;
                  local-address 172.16.129.250;
              }
              vpn-apply-export;
          }
          local-address 1.3.128.126;
          minimum-hold-time 10;
          log-updown;
      }
  
lo0 routes exists in bgp.l3vpn.0
  root@mx> show route table bgp.l3vpn.0 
  
  bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
  + = Active Route, - = Last Active, * = Both
  
  65530:3007614:10.0.0.79/32                
                   *[Direct/0] 00:29:05
                    >  via lo0.18 <<<<<<<<<<<<<<<<<<<<
  172.26.251.248:18:100.100.100.0/24                
                     *[BGP/170] 00:11:20, localpref 100
                        AS path: 64515 I, validation-state: unverified
                      >  to 172.16.129.254 via ae0.943, Push 16
  172.26.251.248:18:192.168.100.1/32                
                     *[BGP/170] 00:11:20, localpref 100
                        AS path: 64515 I, validation-state: unverified
                      >  to 172.16.129.254 via ae0.943, Push 16
  
BGP neighbor is up:
  172.16.129.254        64515         32         30       0       1       12:13 Establ
    bgp.l3vpn.0: 2/2/2/0
    bgp.l3vpn-inet6.0: 0/0/0/0
    n2000018k.inet.0: 2/2/2/0
  
But this PE does not advertise routes to the peer:

  root@mx> show route advertising-protocol bgp 172.16.129.254    
  
  Warning: License key missing; requires 'BGP' license
  
  root@mx> 

BGP stops advertising VPN routes to ebgp peer if static route-target-filter is configured on all JUNOS and JUNOS-EVO platforms.

The problem is introduced by PR1785231 fix. In releases with PR1785231 fix, if the static route-target-filter as local is configured, BGP stops advertising VPN routes to EBGP peer.

This defect has been fixed via PR1845169.

Customer can either upgrade to the fixed release, or set the static route-target-filter as group/neighbor instead of as local.