Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Can't see that BGP aggregate routes are advertised to VPNv4 neighbor.
Enable feature fabric forwarding followed by "fabric forwarding switch-role dci-node border"
No workaround other than removing the feature from the device. But customer wants to keep "fabric forwarding switch-role dci-node border" as they want to interconnect their standalone ACI fabric to VxLAN fabrci in separate DC over MPLS external connectivity.
[+] Customer wants to interconnect their stand-alone DCI fabric with their DC(running VxLAN) and perform some preparation for implementing the solution. [+] They want this Nexus 7K GOLF to act as Border Gateway for connecting VxLAN fabric to external MPLS VPNv4 peer so that EVPN routes can be changed to VPNv4 routes and exchange over MPLS cloud towards ACI fabric and their it should convert back to EVPN routes again. [+] The customer wants to advertise BGP aggregate routes instead of individual routes(as it makes more sense to advertise aggregate routes). [+] However, once they enable the feature "fabric forwarding switch-role dci-node border" to use this device to function as Border Gateway, we see that we stop advertising the BGP aggregate routes to VPNv4 neighbor although routes are there in VRF RIB as well as local VPNv4 table for the VRF but not send across/advertised to neighbor which is strange. Once we remove this command, and BGP establishes again we can see that aggregate routes can be advertised to neighbor. Topology (for Lab Recreate) -------------------------------------- [+] PE-1(N7K-1) and PE-2(N7K-2) are running MPLS LDP and iBGP just as normal MPLS-VPNv4 neighbors(no fancy stuff). [+] N5k-2 acts as CE device and are running OSPF for exchanging routes between CE and PE-2(N7K-2). We are running vrf BCST for the customer on this PE-2. [+] We are receiving three /32 routes from CE to PE-2 (10.145.0.1/32, 10.145.0.2/32 and 10.145.0.3/32) which are loopbacks on CE. We are aggregating these routes on PE-2 (10.145.0.0/16). [+] Additionally, on PE-2 we have direct/connected(Loopbacks) and Static routes. We are summarizing these routes on this PE-2 device as well as following 10.152.0.0/19 --->> Summary for Static Routes 10.159.130.0/24 --->> Summary for Direct Routes [+] Also, we put following static routes10.110.225.0/28, 10.110.225.16/30, 10.143.131.12/30, and 10.143.131.16/30. These route are not catch in the aggregate address for BGP configured. And one 100.100.100.2/32 as loopback 100. VPNv4 Neighbor/PE Rtrs X X XXX X X X XXX X X XX X X X XX XXXX X XX XX X X +---------------------------------------+ +----------------------------------XX | | | | 10.110.224.0/30 | | | | | N7K-2 | | N7k-1 | | | | +--------------------------------------------+ (N7706/ ver 8.3(2) | | (N7706/ ver 8.3(2) |.1 .2 | | | | | | | | | | | | | | +-----------------------------------+ +--------------------+------------------+ | vrf BCST | .3 | | | | | | 10.159.130.152/30 | | | | | | | | .4 +-------------------+------------------+ | | | | | | | | | | | | | N5K-2 | | | | | | | | | | | | | | | +--------------------------------------+ [+] Once the feature is enabled, we dont see aggregate routes advertised and only 10.110.225.0/28, 10.110.225.16/30, 10.143.131.12/30, 10.143.131.16/30 and 100.100.100.2/32 are advertised to neighbor(these routes are Not aggregated). [+] Please refer SR# 686335146 for configurations and detailed outputs.