BGP redistribute connected not advertising connected


Running VX version 3.0.0 and setting up leaf/spine with BGP link-local peering. From leaf Im trying to use "redistribute connected" under AF ipv6 to advertise all interface prefixes across the fabric but its not advertising any of the prefixes. Neighbors join just fine and prefixes advertise fine if they are manually set with "network x.x.x.x" statement under address-family. Here is my BGP config in Quagga.conf. Am I missing something or doing it wrong? Thanks! router bgp 45115 bgp router-id 5.5.5.5 bgp bestpath as-path multipath-relax bgp bestpath compare-routerid neighbor fabric peer-group neighbor fabric remote-as external neighbor fabric description Internal Fabric Network neighbor fabric advertisement-interval 0 neighbor fabric default-originate neighbor fabric timers 1 3 neighbor fabric timers connect 3 neighbor fabric capability extended-nexthop neighbor swp1 interface neighbor swp1 peer-group fabric neighbor swp2 interface neighbor swp2 peer-group fabric neighbor swp3 interface neighbor swp3 peer-group fabric ! address-family ipv6 unicast redistribute connected neighbor fabric activate neighbor swp1 activate neighbor swp2 activate neighbor swp3 activate exit-address-family

4 replies

Userlevel 4
Could you post some of the prefixes that you're trying to advertise into BGP? The output of "ip addr show" should have what we're after...
Sure. Im trying to advertise Loopback0 (3.3.3.3/32) and two SVIs 101 and 201 (172.16.101.0/24 and 201.0/24). SVIs use swp3 as a trunk. cumulus@leaf1:mgmt-vrf:~$ ip addr show 1: lo: mtu 1500 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet 3.3.3.3/32 scope global lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 5: swp3: mtu 1500 qdisc pfifo_fast master bridge state UP group default qlen 1000 link/ether 00:50:56:93:ef:ff brd ff:ff:ff:ff:ff:ff 7: bridge: mtu 1500 qdisc noqueue state UP group default link/ether 00:50:56:93:ef:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::250:56ff:fe93:efff/64 scope link valid_lft forever preferred_lft forever 8: bridge.101@bridge: mtu 1500 qdisc noqueue state UP group default link/ether 00:50:56:93:ef:ff brd ff:ff:ff:ff:ff:ff inet 172.16.101.1/24 scope global bridge.101 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fe93:efff/64 scope link valid_lft forever preferred_lft forever 9: bridge.201@bridge: mtu 1500 qdisc noqueue state UP group default link/ether 00:50:56:93:ef:ff brd ff:ff:ff:ff:ff:ff inet 172.16.201.1/24 scope global bridge.201 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fe93:efff/64 scope link valid_lft forever preferred_lft forever routes also show up in routing table just not BGP. leaf1# sh ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, I - IS-IS, B - BGP, T - Table, > - selected route, * - FIB route C>* 3.3.3.3/32 is directly connected, lo B>* 4.4.4.4/32 [20/0] via fe80::250:56ff:fe93:f2c2, swp1, 11:32:29 * via fe80::250:56ff:fe93:d41, swp2, 11:32:29 B>* 5.5.5.5/32 [20/0] via fe80::250:56ff:fe93:f2c2, swp1, 11:33:54 * via fe80::250:56ff:fe93:d41, swp2, 11:33:54 C>* 172.16.101.0/24 is directly connected, bridge.101 C>* 172.16.201.0/24 is directly connected, bridge.201 leaf1# and just in case its needed here is the /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/*.intf # The loopback network interface auto lo iface lo inet loopback address 3.3.3.3/32 # The primary network interface auto mgmt iface mgmt address 227.0.0.1/8 vrf-table auto auto eth0 iface eth0 inet static address 10.0.0.223 netmask 255.255.255.0 gateway 10.0.0.1 vrf mgmt auto swp1 iface swp1 alias swp1 SPINE1 auto swp2 iface swp2 alias swp2 SPINE2 auto swp3 iface swp3 alias swp3 HOST1 auto bridge iface bridge bridge-vlan-aware yes bridge-ports swp3 bridge-vids 101 201 bridge-ageing 150 bridge-stp on auto bridge.101 iface bridge.101 address 172.16.101.1/24 auto bridge.201 iface bridge.201 address 172.16.201.1/24
Userlevel 4
The address families correspond to the routing information being exchanged, while the neighborship is being built over ipv6 the prefixes being exchanged in this case are v4 so the ipv4 unicast address family is where the redist connected command needs to be. Let me know if that does it.
Thanks! I actually thought about that at one point but didnt try it since the "network" statements under the IPv6 address family worked. But yeah this did it. Here is the final config. Thanks for the help dude!! router bgp 45115 bgp router-id 5.5.5.5 bgp bestpath as-path multipath-relax bgp bestpath compare-routerid neighbor fabric peer-group neighbor fabric remote-as external neighbor fabric description Internal Fabric Network neighbor fabric advertisement-interval 0 neighbor fabric default-originate neighbor fabric timers 1 3 neighbor fabric timers connect 3 neighbor fabric capability extended-nexthop neighbor swp1 interface neighbor swp1 peer-group fabric neighbor swp2 interface neighbor swp2 peer-group fabric neighbor swp3 interface neighbor swp3 peer-group fabric ! address-family ipv6 unicast neighbor fabric activate neighbor swp1 activate neighbor swp2 activate exit-address-family ! address-family ipv4 unicast redistribute connected exit-address-family

Reply