- frog - lists.frrouting.org

EIGRP with Variance > 1
by Kumar., Sandeep 09 Aug '18

09 Aug '18

I am trying a topology with mininet using eigrp and variance > 1. If I run with variance = 1 I have a topology where all hosts are reachable in case I I run with variance > 1 though I get the routes as expected for unequal path load balancing the hosts are all not reachable. I tried frr 4.0 and frr 5.0 I see a change in the way the master branch checks on feasible successors and successors… Could you point me to a version that would have support for variance > 1 ?

2 1

Features supported by FreeBSD?
by Muenz, Michael 09 Aug '18

09 Aug '18

Hi, I'm searching for some documents what features are Linux exclusive and what can run also on FreeBSD. I know that basic services like zebra, ospfd2+3 or bgpd are supported, or MPLS for FreeBSD not. But what about PBRd? Or features like VPNV4? Thanks, Michael

2 3

Static Daemon now part of master
by Donald Sharp 08 Aug '18

08 Aug '18

All - Static route handling has been moved from within zebra to it's own daemon `staticd`. This daemon is automatically built as part of the standard distribution and both redhat and debian packaging has been updated to point to it as well. If you are using static routes you now must run `staticd`. Please update your startup scripts to reflect this: 1) Modify /etc/frr/daemons or /etc/frr/daemons.conf as necesary. 2) If you are using an integrated config, you do not need to modify any configuration file. 3) If you are not using an integrated config, staticd has been modified to allow it to read the zebra.conf file to get it's static routes. It is recommended that you do a write mem after bring up to get staticd it's own configuration file. Why was this change made? It was done for 2 reasons: 1) Zebra has rib_add_multipath for route entry from higher level protocols. static routes were violating this coding standard and we ended up with 2 code paths for handling new routes in the system. This simplfiies this to 1 entry point, which is good because we are working on further zebra changes in how it handles nexthop groups and having 2 code paths would make this work more complicated than what it needed to be. 2) Moving static routes to it's own daemon simplifies a bunch of code paths in zebra as that we do not need to keep track of special case code for static routes. I'd Like to thank everyone who's had their hand in this, Martin Winter, Renato Westphal, Quentin Young, Philippe Guibert, Lou Berger and David Lamparter! thanks! donald

1 0

Re: [FROG] "set origin igp" on FRRouting, possible ?
by Christoffer Hansen 06 Aug '18

06 Aug '18

On Mon, 6 Aug 2018 at 17:03, Bob wrote: > On August 6, 2018 3:45 PM, Christoffer wrote: > > Even though it is not mentioned in the docs. > > You can do "set origin XYZ" in route-maps applied to BGP neighbors. > > > > Nb: Sometimes you will run into the docs not being 100 % updated when > > compared to available features/commands in FRR. > > Fab thanks ! Now with PR, too. https://github.com/FRRouting/frr/pull/2794

1 0

Re: [FROG] "set origin igp" on FRRouting, possible ?
by Christoffer Hansen 06 Aug '18

06 Aug '18

Hi Bob, On Mon, 6 Aug 2018 at 16:24, Bob Smith via frog <frog(a)lists.frrouting.org> wrote: > I've had a quick grep through The Fabulous Manual (http://docs.frrouting.org/en/latest/bgp.html) and whilst other old friends such as always-compare-med seem to be implemented, there appears to be no mention of "set origin". > > Is it possible to do this ? If so, could someone update the docs? If not, could someone implement this rather useful feature ! Even though it is not mentioned in the docs. You can do "set origin XYZ" in route-maps applied to BGP neighbors. Nb: Sometimes you will run into the docs not being 100 % updated when compared to available features/commands in FRR. /Christoffer

1 0

"set origin igp" on FRRouting, possible ?
by Bob Smith 06 Aug '18

06 Aug '18

Hi, I've had a quick grep through The Fabulous Manual (http://docs.frrouting.org/en/latest/bgp.html) and whilst other old friends such as always-compare-med seem to be implemented, there appears to be no mention of "set origin". Is it possible to do this ? If so, could someone update the docs? If not, could someone implement this rather useful feature ! Thanks ! Bob

1 0

Multipod evpn deployment over eBGP MPLS.
by Hendrik Meyburgh 01 Aug '18

01 Aug '18

Hi. Please can someone help me, I am a bit stuck at the moment and not winning? The image is the lab I am testing. PE1,P1,P2 and PE2 are Junos devices. The leaf/spines are Cumulus implementations on Mellanox switches. +-------+ +-------+ | | | | |--------------------> P1 |<-----------------------------------------------> P2 | | | | | | | | | | | | +-------+ +-------+ PODA | ^ +--------------------------------------------+ | | +-------+ | | | ^---------------> |<--------------^ | | | | y.y.y.y | PE1 | | | | | | |z.z.z.z| | | | | | | | | | | | | +-------+ | | PODB | | | | | +--------------------------------------+ | | | | | | | | | +-------+ +-------+ | | | +-------+ | | | | | | | | | | | | | | | | | | Spine1| | Spine2| | | | | Spine1| | | | | | | | | | | + | | | | | | | | | | | | | | | | | | | | +-------+-- +-------+ | | | +-------+ | | | | | \-- -- | | | | | | | | | | \- ---/ | | | | | | | | | | ---/ | | | | | | | | | | ---/ \-- | | | | | | | | | v <-/ \> v | | | v v | | | +------------+ +-------+ | | | +-------+ +-------+ | | | | | | | | | | | | | | | | | | | |Leaf2 | | | | |Leaf1 | | PE2 | | | v--| Leaf1 | | |---v | | | |<--------> | | | | | b.b.b.b | |c.c.c.c| | | |x.x.x.x| a.a.a.a |g.g.g.g| | | +------------+ +-------+ | | +-------+ +-------+ | | <-- <- | | -> | | \---- \-- | | --/ | +--------------------------------------------+ -|-/ | \--- \> Port2 --/ +--------------------------------------+ \---- +------------------------+</ \---- | | Port3 \-> | | | Testing Device | Port1| | +------------------------+ Internally in both pods, the architecture is L3 and using eBGP by means of unnumbered interfaces, advertising connected routes. In PODA PE1 is connected to both leafs, over separate links with labeled-unicast enabled, using implicit-null. The testing device is a Juniper SRX, with each interface setup in a virtual router, but part of the same subnet. On the switch side, the port facing the testing device is in a bridge, with a VNI setup and the local tunnel endpoint the loopback address. I am also using an SVI on the same subnet. Each port can reach the SVI locally. and testing between Port1 and Port2 is successful via the uplinks to PE1, label switching seems to be working correctly. There is reachability between the loopbacks of all the leafs as well. It seems there is a problem with the route-map since switching to labeled-unicast routes after testing ospf and ldp. I still need to confirm that, in order to test the reachability over the leaf/spine network, as it was working. I am running into an issue with testing between Port1/Port2 and Port3. It seems like all routes are present, but with the eBGP architecture, the standard operation is to change the next-hop on external routes, but it changes the remote vtep as well. The mac/ip from Port3 is advertised by PODB leaf 1 with the VTEP as x.x.x.x, however displaying it on PODA Leaf1, it reports as y.y.y.y, where y.y.y.y is the link local address of PE1. root@poda-leaf1:~# net show evpn mac vni 1001 Number of MACs (local and remote) known for this VNI: 3 MAC Type Intf/Remote VTEP VLAN 54:4b:8c:51:1c:a9 local swp13 1001 54:4b:8c:51:1c:ad remote y.y.y.y root@poda-leaf1:~# net show bgp evpn route vni 1001 mac 54:4b:8c:51:1c:ad BGP routing table entry for [2]:[0]:[0]:[48]:[54:4b:8c:51:1c:ad] Paths: (1 available, best #1) Not advertised to any peer Route [2]:[0]:[0]:[48]:[54:4b:8c:51:1c:ad] VNI 993 Imported from x.x.x.x:2:[2]:[0]:[0]:[48]:[54:4b:8c:51:1c:ad] 11111 65202 y.y.y.y from y.y.y.y (z.z.z.z) Origin IGP, metric 200, localpref 100, valid, external, bestpath-from-AS 11111, best Extended Community: RT:65202:1001 ET:8 AddPath ID: RX 0, TX 56 Last update: Wed Aug 1 11:54:59 2018 I am also not understanding why the route above outputs VNI 993, it does however seem to import correctly into 1001. root@poda-leaf1:~# net show bgp evpn route vni 1001 vtep y.y.y.y BGP table version is 33, local router ID is b.b.b.b Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete EVPN type-2 prefix: [2]:[ESI]:[EthTag]:[MAClen]:[MAC]:[IPlen]:[IP] EVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP] EVPN type-5 prefix: [5]:[ESI]:[EthTag]:[IPlen]:[IP] Network Next Hop Metric LocPrf Weight Path *> [2]:[0]:[0]:[48]:[54:4b:8c:51:1c:ad] y.y.y.y 200 0 11111 65202 i *> [2]:[0]:[0]:[48]:[54:4b:8c:51:1c:ad]:[32]:[10.2.0.200] y.y.y.y 200 0 11111 65202 i *> [3]:[0]:[32]:[x.x.x.x] y.y.y.y 200 0 11111 65202 i Checking in anything is present for the loopback of podb-leaf1 root@poda-leaf1:~# net show bgp evpn route vni 1001 vtep x.x.x.x BGP table version is 33, local router ID is b.b.b.b Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete EVPN type-2 prefix: [2]:[ESI]:[EthTag]:[MAClen]:[MAC]:[IPlen]:[IP] EVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP] EVPN type-5 prefix: [5]:[ESI]:[EthTag]:[IPlen]:[IP] Network Next Hop Metric LocPrf Weight Path Displayed 9 prefixes (0 paths) Below is the same command on the originating leaf. root@podB-leaf-01:~# net show bgp evpn route vni 1001 mac 54:4b:8c:51:1c:ad BGP routing table entry for [2]:[0]:[0]:[48]:[54:4b:8c:51:1c:ad] Paths: (1 available, best #1) Not advertised to any peer Route [2]:[0]:[0]:[48]:[54:4b:8c:51:1c:ad] VNI 1001 Local x.x.x.x from 0.0.0.0 (x.x.x.x) Origin IGP, localpref 100, weight 32768, valid, sourced, local, bestpath-from-AS Local, best Extended Community: ET:8 RT:65202:1001 AddPath ID: RX 0, TX 63 Last update: Wed Aug 1 11:51:44 2018 Spanning the uplink port to another port on the same switch, allowed me to look at the dataplane, and it does confirm that it is sending the traffic to the wrong destination. tcpdump on the uplink interface: 12:21:53.724226 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 134) b.b.b.b.20496 > y.y.y.y.4789: [no cksum] VXLAN, flags [I] (0x08), vni 1001 IP (tos 0x0, ttl 64, id 45715, offset 0, flags [none], proto ICMP (1), length 84) 10.2.0.1 > 10.2.0.200: ICMP echo request, id 20365, seq 231, length 64 0x0000: 4500 0086 0000 4000 4011 a2ec 29c1 77ea E.....@.@...).w. 0x0010: d1cb 2404 5010 12b5 0072 0000 0800 0000 ..$.P....r...... 0x0020: 0003 e900 544b 8c51 1cad 544b 8c51 1ca9 ....TK.Q..TK.Q.. 0x0030: 0800 4500 0054 b293 0000 4001 b349 0a02 ..E..T....@..I.. 0x0040: 0001 0a02 00c8 0800 ae01 4f8d 00e7 5b61 ..........O...[a 0x0050: f7a0 0009 bb7b 0809 0a0b 0c0d 0e0f 1011 .....{.......... 0x0060: 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 ...............! 0x0070: 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 "#$%&'()*+,-./01 0x0080: 3233 3435 3637 234567 It is showing the VXLAN packet and not MPLS as there is no static entry for it as I am using labeled-unicast distribution. I would appreciate any assistance as I have spend a lot of hours on this deployment and just keep on failing to get the 2 pods to talk to each other. If you can also confirm if this type of architecture is suppose to work? Below are the config files. poda-leaf1 interface file: auto lo iface lo inet loopback address b.b.b.b/32 auto swp3 iface swp3 address y.y.y.z/31 mpls-enable yes mtu 9178 auto bridge iface bridge bridge-ports swp13 vni1001 bridge-pvid 1 bridge-vids 1001 bridge-vlan-aware yes auto vlan1001 iface vlan1001 #hwaddress 44:39:39:FF:40:94 address 10.2.0.150/24 vlan-id 1001 vlan-raw-device bridge auto vni1001 iface vni1001 bridge-access 1001 bridge-arp-nd-suppress on bridge-learning off mstpctl-bpduguard yes mstpctl-portbpdufilter yes vxlan-id 1001 vxlan-local-tunnelip b.b.b.b poda-leaf1 frr.conf router bgp 65200 bgp router-id b.b.b.b coalesce-time 1000 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 capability extended-nexthop neighbor swp47 interface peer-group fabric neighbor swp48 interface peer-group fabric neighbor y.y.y.y remote-as 11111 neighbor y.y.y.y ebgp-multihop 3 ! address-family ipv4 unicast network b.b.b.b/32 redistribute connected no neighbor y.y.y.y activate export vpn exit-address-family ! address-family ipv4 labeled-unicast neighbor y.y.y.y activate neighbor y.y.y.y route-map HigherMetric in exit-address-family ! address-family l2vpn evpn neighbor fabric activate neighbor y.y.y.y activate neighbor y.y.y.y route-map HigherMetric in advertise-all-vni exit-address-family ! route-map HigherMetric permit 10 set metric 200 ! ip route z.z.z.z/32 y.y.y.y ! mpls label global-block 16 1000 mpls label bind b.b.b.b/32 implicit-null mpls label bind c.c.c.c/32 102 mpls label bind x.x.x.x/32 103 podb-leaf01 interface file auto lo iface lo inet loopback address x.x.x.x/32 auto swp3 iface swp3 address a.a.a.b/31 mpls-enable yes mtu 9178 auto bridge iface bridge bridge-ports swp5 swp13 vni1001 bridge-pvid 1 bridge-vids 1001 bridge-vlan-aware yes auto vlan1001 iface vlan1001 address 10.2.0.152/24 vlan-id 1001 vlan-raw-device bridge auto vni1001 iface vni1001 bridge-access 1001 bridge-arp-nd-suppress on bridge-learning off mstpctl-bpduguard yes mstpctl-portbpdufilter yes vxlan-id 1001 vxlan-local-tunnelip x.x.x.x podb-leaf1 frr.conf router bgp 65202 bgp router-id x.x.x.x coalesce-time 1000 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 capability extended-nexthop neighbor swp47 interface peer-group fabric neighbor swp48 interface peer-group fabric neighbor a.a.a.a remote-as 11111 neighbor a.a.a.a ebgp-multihop 3 ! address-family ipv4 unicast network x.x.x.x/32 redistribute connected no neighbor a.a.a.a activate export vpn exit-address-family ! address-family ipv4 labeled-unicast neighbor a.a.a.a activate exit-address-family ! address-family l2vpn evpn neighbor fabric activate neighbor a.a.a.a activate advertise-all-vni exit-address-family ! ip route g.g.g.g/32 a.a.a.a ! mpls label global-block 16 1000 mpls label bind b.b.b.b/32 301 mpls label bind c.c.c.c/32 302 mpls label bind x.x.x.x/32 implicit-null

1 0

Redistribute to BGP ipv4 labeled-unicast
by Marco Marzetti 30 Jul '18

30 Jul '18

Dear members of the group, I've noticed neither "redistribute" nor "network" commands are supported by bgpd for AFI/SAFI ipv4 labeled-unicast. I took a look at github and i can't find the features in any of the milestones. Is there an underlying reason i can't spot or is it just the dev team hasn't found time yet? Thank you for your help. Regards

3 9

Fwd: Segment Routing with FRR
by 唐志军 22 Jul '18

22 Jul '18

Hello, My name is Zhijun. I am learning segment routing by using FRRouting. First, thank you for writing such a guide to setup segment routing in FRRouting. I have read this guide and set up an sr environment with 5 FRR routers. However, I cannot make it sure whether I did correctly. Bellow is my topo. [image: image.png] and this is my r1 config, [image: image.png] and I got bellow sr info, [image: image.png] I would be very grateful if you can tell me if this is right to config such an sr environment. And, in depth, how can I config a label switch path for traffic between H1 and H2, such as icmp packets? Best Reguards, Zhijun

1 0

[EVPN] ./configure options to create crash dump and debugging for EVPN
by Felipe Arturo Polanco 17 Jul '18

17 Jul '18

Hi, Could anyone please share the ./configure options to enable debugging information as well as crash dump ? I have BGPd crashing in an EVPN environment with this as backtrace: Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/libfrr.so.0(zlog_backtrace_sigsafe+0x32) [0x7f592688fb94] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/libfrr.so.0(zlog_signal+0x219) [0x7f59268900b1] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/libfrr.so.0(+0x4a729) [0x7f59268a0729] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/bgpd() [0x4a12e4] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/bgpd() [0x4a15ad] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/bgpd() [0x4a1660] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/bgpd(bgp_evpn_local_vni_add+0x133) [0x4a5163] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/bgpd() [0x446f2c] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/libfrr.so.0(+0x5b572) [0x7f59268b1572] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/libfrr.so.0(thread_call+0x46) [0x7f59268aa5d1] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/libfrr.so.0(frr_run+0x1ae) [0x7f592688eb93] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/bgpd(main+0x1f8) [0x41cf74] Jul 13 20:08:10 li1276-116 bgpd[14597]: /usr/lib/frr/bgpd() [0x41e826] Jul 13 20:08:10 li1276-116 watchfrr[14612]: bgpd state -> down : read returned EOF This is happening randomly and is hard to reproduce so I believe a crash dump can help see where the problem is. Thanks,

2 4