January 2018 - frog - lists.frrouting.org

received-routes.. doesn't work?
by Mark Kamichoff 01 Sep '18

01 Sep '18

Hi - I'm running various 3.1-dev versions of FRR and noticed that the "show ip bgp nei <peer> received-routes" doesn't seem to work as expected on any of them. Here's an example of the relevant parts of the configuration: ! router bgp 395460 neighbor 169.254.169.254 remote-as 64515 neighbor 169.254.169.254 password <snip> neighbor 169.254.169.254 ebgp-multihop 2 address-family ipv4 unicast neighbor 169.254.169.254 soft-reconfiguration inbound neighbor 169.254.169.254 route-map DENY_ALL in neighbor 169.254.169.254 route-map DENY_ALL out exit-address-family ! route-map DENY_ALL deny 65535 ! orca# show ip bgp neighbors 169.254.169.254 routes orca# show ip bgp neighbors 169.254.169.254 received-routes BGP table version is 0, local router ID is 10.3.4.36 Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, i internal, r RIB-failure, S Stale, R Removed Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path orca# >From tcpdump and other t-shooting I know that there is an IPv4 DFZ being received, but received-routes doesn't show any of the routes that should be in the adj-rib-in. Oddly, if I remove the inbound route-map I see expected prefixes using the "routes" /and/ "received-routes" command. If I put it back, the "received-routes" shows nothing once again. It would almost seem like soft-reconfiguration isn't really enabled, but received-routes should give me an error if it wasn't and the neighbor information confirms that it is: orca# show ip bgp neighbors 169.254.169.254 <snip> For address family: IPv4 Unicast Update group 5, subgroup 5 Packet Queue length 0 Inbound soft reconfiguration allowed <----- <snip> This isn't limited to the IPv4 AF, either. I've got IPv6 peers that echibit the same behavior. Have I found a bug or am I doing something wrong? I'm happy to file a bug report. More info., if it helps: orca# show version FRRouting 3.1-dev (). Copyright 1996-2005 Kunihiro Ishiguro, et al. configured with: '--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--disable-silent-rules' '--libexecdir=${prefix}/lib/frr' '--disable-maintainer-mode' '--disable-dependency-tracking' '--enable-exampledir=/usr/share/doc/frr/examples/' '--localstatedir=/var/run/frr' '--sbindir=/usr/lib/frr' '--sysconfdir=/etc/frr' '--enable-ospfapi=yes' '--enable-vtysh=yes' '--enable-isisd=yes' '--enable-multipath=256' '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--enable-configfile-mask=0640' '--enable-logfile-mask=0640' '--enable-werror' '--enable-gcc-rdynamic' '--with-libpam' '--enable-systemd=yes' '--enable-poll=yes' '--enable-cumulus=yes' '--enable-pimd=yes' '--enable-dependency-tracking' '--enable-bgp-vnc=no' 'build_alias=x86_64-linux-gnu' orca# (orca:20:08:PDT)% uname -a Linux orca 4.9.0-3-amd64 #1 SMP Debian 4.9.25-1 (2017-05-02) x86_64 GNU/Linux (the build is from August 26th) Thanks! - Mark -- Mark Kamichoff prox(a)prolixium.com https://www.prolixium.com/

1 1

Static VRF Route Leaking
by Donald Sharp 23 Jan '18

23 Jan '18

All - I'd like to thanks Philippe Guibert, Lou Berger, Renato Westphal and Russ White working with me to get static route leaking into the FRR code base on master. To configure: vrf DONNA ip route 4.3.2.1/32 99.1.2.3 nexthop-vrf EVA ! vrf EVA ip route 9.1.2.3/32 44.3.2.4 nexthop-vrf DONNA ! These two commands create a static route that leaks the nexthops into the appropriate vrf's. At this point in time, BGP has not been modified to take advantage of vrf route leaking in the traditional manner, but the underpinnings in zebra and the zapi protocol are now there. donald

1 0

layer-2 vxlan discovery w/ EVPN question
by Henry Snow 20 Jan '18

20 Jan '18

I have a bare metal hosting provider that provides me with layer-3 networking to every server. For some applications, I require a layer-2 network spanning the servers. This network is for the applications running on the server OS, not via VM or container tennants. I've been following this blog post: https://vincent.bernat.im/en/blog/2017-vxlan-bgp-evpn, using frr 3.1dev from git master from several nights ago. I believe I have the route reflector + vteps configured with respect to bgpd as described, but no routes are advertised. I do see bgp neighbors as expected. When I run 'show evpn mac vni 100', I do not see any mac addresses. My suspicion is that it is because I'm not using a bridge, but assigning an IP address directly to the vxlan interface. Looking at the source code (my C is very rusty), it looks like it enumerates all the VNIs, finds the bridges they're slaved to, then enumerates the interfaces on the bridge. I'm looking at this: https://github.com/FRRouting/frr/blob/8eac4812601f069f14fc7950e10904c2ae0ae… Is there a way to configure my interfaces without a bridge (or is this a bad approach)? If a bridge and additional slaved interface is required, any suggestions on how to configure the bridge with no additional tenants on the servers? Additional Thoughts: - using static unicast discovery, vxlan membership across servers works - adding a bridge interface and slaving the vxlan interface + a dummy interface, assigning an ip to the dummy did not seem to work - tried kernel 4.4 from elrepo, (tends to work better from previous docker overlay network experiences) Config: compiled from commit c1240044fbf081bb7407b1449d3954e4b63fec9f on CentOS 7.4, with --enable-cumulus Route Reflector: 10.40.1.131/31 bgpd.conf: router bgp 65000 bgp router-id 10.40.1.131 bgp cluster-id 10.40.1.131 bgp log-neighbor-changes no bgp default ipv4-unicast coalesce-time 1000 neighbor fabric peer-group neighbor fabric remote-as 65000 neighbor fabric update-source 10.40.1.131 neighbor fabric capability extended-nexthop bgp listen range 10.40.1.128/25 peer-group fabric ! address-family l2vpn evpn neighbor fabric activate neighbor fabric route-reflector-client exit-address-family ! layer-2 member server example: 10.40.1.129/31 bgpd.conf: router bgp 65000 bgp router-id 10.40.1.129 no bgp default ipv4-unicast coalesce-time 1000 neighbor fabric peer-group neighbor fabric remote-as 65000 neighbor fabric capability extended-nexthop neighbor 10.40.1.131 peer-group fabric ! address-family l2vpn evpn neighbor fabric activate advertise-all-vni exit-address-family ! vxlan configured with: # ip link vxlan100 type vxlan id 100 local 10.40.1.129 port 4789 nolearning # ip link set up dev vxlan100 # ip addr add 172.31.254.2/24 dev vxlan100 Thanks for any suggestions (or course corrections, as this is new to me)! -- Henry Snow | Director, Site Reliability Engineering eXelate, a Nielsen company <http://exelate.com/> E: henry.snow(a)nielsen.com | M: 347.366.2700 675 6th Ave, 3rd Floor, New York, NY 10010

1 1

New EVPN Code in Master
by Donald Sharp 17 Jan '18

17 Jan '18

All - EVPN control plane in FRR is now enhanced so that it supports both asymmetric and symmetric routing models. Prefix-based routing is also supported using EVPN type-5 routes. Also, with all routing models, L3 multi-tenancy is inherently supported I'd like to thank Mitesh for his hard work getting this done! thanks! donald

4 6

Release 3.0.3
by Donald Sharp 13 Jan '18

13 Jan '18

All - Release 3.0.3 has been spun up. Changes over version 3.0.2: Fixes for GCC 7.0 Always enable watchfrr on new installation (req for systemd operation) Add 'no password' command (with warning) Added Ubuntu 17.10 Package support in source (no binary packages built [yet]) https://github.com/FRRouting/frr/releases Thanks! donald

1 0