[FROG] bgp view broken in 8.0 ?

[Martin Winter]

Philip,

can you open an issue on Github (https://github.com/opensourcerouting/frr-dpd/issues) for this?
We do have an automated test for route-views (as part of topotests), but that one still works.

As you mentioned that you have a testbed, it might be useful if you could do a retest with latest
package from master (get it from https://ci1.netdef.org/browse/FRR-FRR/latestSuccessful/artifact or
build it from source - whichever way you usually use) and you might also try with 8.0.1 (I'm in process to
build it as we speak - packages should be available in the next days).

Martin
On Aug 27 2021, at 7:06 am, Philip Smith <philip at nsrc.org> wrote:
>
> Hi everyone,
> Is anyone using the "bgp view" feature in FRR at all?
> I've been using this feature on FRR 7.5.1 on Ubuntu 20.04 for several
> months without issue.
>
> The upgrade to FRR 8.0 that was pushed out the four weeks back broke all
> the BGP feeds that I have (basically for a routing analysis looking
> glass activity).
>
> This is the an example of the configuration I'm using:
> router bgp 65534 view I2
> bgp router-id 128.223.157.40
> bgp log-neighbor-changes
> no bgp default ipv4-unicast
> timers bgp 15 45
> neighbor 64.57.28.241 remote-as 11537
> neighbor 64.57.28.241 description I2
> neighbor 64.57.28.241 ebgp-multihop 255
> !
> address-family ipv4 unicast
> neighbor 64.57.28.241 activate
> neighbor 64.57.28.241 prefix-list DENY-ALL out
> neighbor 64.57.28.241 route-map IMPORT in
> exit-address-family
> !
>
> and I have around 30 BGP feeds, all going into different views.
> If I use FRR 7.5.1, the BGP sessions are up and running just fine.
> But in 8.0, they all sit there in "Connect" (IPv4 and IPv6). It looks
> like this, in a testbed of mine (I can't put the production system to
> FRR 8.0 unfortunately).
>
> Configuration:
> router bgp 131076 view C1100
> bgp router-id 192.168.1.230
> bgp log-neighbor-changes
> no bgp default ipv4-unicast
> neighbor 192.168.1.254 remote-as 131076
> neighbor 192.168.1.254 description Cisco C1100 Border
> !
> address-family ipv4 unicast
> distance bgp 200 200 200
> neighbor 192.168.1.254 activate
> exit-address-family
> !
>
> frr# sh bgp view C1100 sum
> IPv4 Unicast Summary:
> BGP router identifier 192.168.1.230, local AS number 131076 vrf-id 1
> BGP table version 0
> RIB entries 0, using 0 bytes of memory
> Peers 1, using 727 KiB of memory
>
> Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ
> Up/Down State/PfxRcd PfxSnt Desc
> 192.168.1.254 4 131076 0 0 0 0 0
> never Connect 0 Cisco
>
> Total number of neighbors 1
>
> If I revert to FRR 7.5.1 on the testbed, the peering comes up.
> bgpd.log says this:
> 2021/08/27 14:42:12 ZEBRA: [VTVCM-Y2NW3] Configuration Read in Took:
> 00:00:00
> 2021/08/27 14:42:12 BGP: [VTVCM-Y2NW3] Configuration Read in Took: 00:00:00
> 2021/08/27 14:42:12 STATIC: [VTVCM-Y2NW3] Configuration Read in Took:
> 00:00:00
>
> and frr.log has basically the same content.
> The docs for bgpd don't seem to have changed and I can't find anything
> via the CLI that suggests the configuration is different in 8.0.
>
> Any hints or tips or clues on how to fix this? Or is this a bug
> introduced in 8.0?
>
> Thanks!
> philip
> --
>
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20210827/dc0022dc/attachment.htm>