Skip to content

Unable to advertise EVPN type 3 (multicast) routes when using a route-map #13792

@DaniilHarun

Description

@DaniilHarun

Describe the bug
When using any route map, EVPN type 3 (multicast) routes are not advertised.

  • Did you check if this is a duplicate issue?
  • Did you test it on the latest FRRouting/frr master branch?

To Reproduce

  1. Create vxlan and bridge interface (vxlan 100).
  2. Apply this config:
router bgp 65023
 bgp router-id 10.32.0.41
 bgp log-neighbor-changes
 no bgp ebgp-requires-policy
 no bgp default ipv4-unicast
 no bgp network import-check
 neighbor RS-EVPN peer-group
 neighbor RS-EVPN remote-as 65020
 neighbor RS-EVPN bfd
 neighbor RS-EVPN ebgp-multihop 32
 neighbor RS-EVPN update-source dum0
 neighbor RS-EVPN capability extended-nexthop
 neighbor 10.32.1.2 peer-group RS-EVPN
 !
 address-family l2vpn evpn
  neighbor RS-EVPN activate
  neighbor RS-EVPN allowas-in 1
  neighbor RS-EVPN route-map RS-OUT out
  advertise-all-vni
  vni 100
   rd 65023:100000100
   route-target import 65000:100
   route-target export 65002:1
   advertise-svi-ip
  exit-vni
 exit-address-family
exit
!
route-map RS-OUT permit 10
  1. Checking the route:
# show bgp l2vpn evpn route rd 65023:100000100 type 3

EVPN type-1 prefix: [1]:[EthTag]:[ESI]:[IPlen]:[VTEP-IP]:[Frag-id]
EVPN type-2 prefix: [2]:[EthTag]:[MAClen]:[MAC]
EVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP]
EVPN type-4 prefix: [4]:[ESI]:[IPlen]:[OrigIP]
EVPN type-5 prefix: [5]:[EthTag]:[IPlen]:[IP]

BGP routing table entry for 65023:100000100:[3]:[0]:[32]:[10.32.0.43]
Paths: (1 available, best #1)
  Not advertised to any peer
  Route [3]:[0]:[32]:[10.32.0.43] VNI 100
  Local
    10.32.0.43 from 0.0.0.0 (10.32.0.41)
      Origin IGP, weight 32768, valid, sourced, local, best (First path received)
      Extended Community: ET:8 RT:65002:1
      Last update: Tue Jun 13 09:56:27 2023
      PMSI Tunnel Type: Ingress Replication, label: 100

This route is not advertised to any peer. As a result, any multicast and broadcast traffic is not routed.
If I turn off the route map, the problem with route advertising goes away:

  1. Disabling a route map
# conf
(config)# router bgp 65023
(config-router)#  address-family l2vpn evpn
(config-router-af)# no   neighbor RS-EVPN route-map RS-OUT out
(config-router-af)# end
  1. Checking the route:
# show bgp l2vpn evpn route rd 65023:100000100 type 3

EVPN type-1 prefix: [1]:[EthTag]:[ESI]:[IPlen]:[VTEP-IP]:[Frag-id]
EVPN type-2 prefix: [2]:[EthTag]:[MAClen]:[MAC]
EVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP]
EVPN type-4 prefix: [4]:[ESI]:[IPlen]:[OrigIP]
EVPN type-5 prefix: [5]:[EthTag]:[IPlen]:[IP]

BGP routing table entry for 65023:100000100:[3]:[0]:[32]:[10.32.0.43]
Paths: (1 available, best #1)
  Advertised to non peer-group peers:
  10.32.1.2
  Route [3]:[0]:[32]:[10.32.0.43] VNI 100
  Local
    10.32.0.43 from 0.0.0.0 (10.32.0.41)
      Origin IGP, weight 32768, valid, sourced, local, best (First path received)
      Extended Community: ET:8 RT:65002:1
      Last update: Tue Jun 13 14:33:37 2023
      PMSI Tunnel Type: Ingress Replication, label: 100

Displayed 1 prefixes (1 paths) with this RD (of requested type)

This route advertised.

Expected behavior

Screenshots

Versions

  • OS Version: Debian11
  • Kernel: 6.1.33
  • FRR Version: 8.5.1-43

Additional context

Metadata

Metadata

Assignees

Labels

triageNeeds further investigation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions