I have the log file as debugging. I am running the configuration with frr.conf. The log output does not generate much. I am referring to the routes added by BGP. I can see the routes oscillating of being added and removed by running the command "ip -6 ro sh" in the linux terminal or "show ipv6 route" through vtysh several times. Either case, the ipv6 routes are being added and removed continuously. Vtysh terminal output of the Relay ----------------------------------------- Relay# show ipv6 route Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP, F - PBR, f - OpenFabric, > - selected route, * - FIB route, q - queued route, r - rejected route B>* 2001:db8:1:1::/64 [20/1024] via fe80::1:2, eth2, 00:00:00 B>* 2001:db8:1:2::/64 [20/1024] via fe80::2:2, eth3, 00:00:00 B>* 2001:db8:1:3::/64 [20/1024] via fe80::1:2, eth2, 00:00:00 B>* 2001:db8:1:4::/64 [20/1024] via fe80::2:2, eth3, 00:00:00 B fd80::1:0/112 [20/0] via fe80::1:2, eth2, 00:00:00 C>* fd80::1:0/112 is directly connected, eth2, 00:00:21 B>* fd80::1:2/128 [20/1024] via fe80::1:2, eth2, 00:00:00 B fd80::2:0/112 [20/0] via fe80::2:2, eth3, 00:00:00 C>* fd80::2:0/112 is directly connected, eth3, 00:00:21 B>* fd80::2:2/128 [20/1024] via fe80::2:2, eth3, 00:00:00 C * fe80::/10 is directly connected, eth3, 00:00:20 C * fe80::/10 is directly connected, eth2, 00:00:20 C * fe80::/10 is directly connected, eth3, 00:00:21 C>* fe80::/10 is directly connected, eth2, 00:00:21 C * fe80::/64 is directly connected, eth1, 00:00:17 C>* fe80::/64 is directly connected, eth0, 00:00:17 Relay# show ipv6 route Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP, F - PBR, f - OpenFabric, > - selected route, * - FIB route, q - queued route, r - rejected route C>* fd80::1:0/112 is directly connected, eth2, 00:02:13 C>* fd80::2:0/112 is directly connected, eth3, 00:02:13 C * fe80::/10 is directly connected, eth3, 00:02:12 C * fe80::/10 is directly connected, eth2, 00:02:12 C * fe80::/10 is directly connected, eth3, 00:02:13 C>* fe80::/10 is directly connected, eth2, 00:02:13 C * fe80::/64 is directly connected, eth1, 00:02:09 C>* fe80::/64 is directly connected, eth0, 00:02:09 Thanks, Katherine -----Original Message----- From: Chriztoffer Hansen [mailto:ch@ntrv.dk] Sent: Wednesday, April 15, 2020 3:14 PM To: Tran (US), Katherine K <katherine.k.tran@boeing.com> Cc: Vijay Kumar Gupta <vijayg@vmware.com>; frog@lists.frrouting.org Subject: Re: [FROG] fd80 prefix allocation On Wed, 15 Apr 2020 at 18:47, Tran (US), Katherine K <katherine.k.tran@boeing.com> wrote:
Was this new behaviour added in FRRouting? My links keep getting dropped and re-added in FRRouting compared to Quagga. I was wondering if the defaulted link-local next-hops would be the cause for why the routes are unstable in FRRouting. Also, would the route-map change increase the route stability?
If you increase the log-level for FRRouting. What log messages gets written out regarding what your consider as oscillating routes? Cheers, Chriztoffer