<html><head></head><body>Fine then! I was suspicious about some changes in thread-next (where this problem can be actually reproduced with a good probability) and now I know that I should assess the whole algorithm instead.<br><br>Thanks a lot!<br>Maria<br><br><div class="gmail_quote">On October 7, 2022 11:29:09 AM UTC, Mihai <mihaigabriel@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre dir="auto" class="k9mail">Hi Maria,<br><br>Yes you are correct, the metric is not a random value but an old value, probably the first one after OSPF established.<br>It looks like any subsequent change in the OSPF topology/metrics is not reflected in the BGP_NH metric.<br><br>Best regards,<br>Mihai<br><br>On 03/10/2022 12:43, Maria Matejka via Bird-users wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Hello!<br><br>I'd suspect the internal nexthop resolving mechanisms of missing the OSPF route update. When working on the multithreaded version, I came across a similar kind of bug and I honestly don't know yet how exactly this may be broken.<br><br>That said, is it possible that the metric is just an obsolete value from some previous route version?<br><br>Thanks for your report.<br><br>Maria<br><br>On 9/30/22 17:10, Mihai via Bird-users wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">Hello,<br><br>The same issue on another RR, the BGP_Metric=60380 while the OSPF_Metric=60315.<br><br>bird> sh route 10:10 202.81.16.0/24 all<br>Table vpntab4:<br>10:10 202.81.16.0/24 unicast [ROUTER2 2022-09-29 15:21:18 from 10.100.186.6] * (100/60380) [AS4826i]<br> Type: BGP univ<br> BGP.origin: IGP<br> BGP.as_path: 4826<br> BGP.next_hop: 10.100.186.6<br><br>bird> show route 10.100.186.6/32<br>Table master4:<br>10.100.186.6/32 unicast [OSPF 2022-09-30 15:01:51] IA (150/60315) [10.100.186.4]<br><br><br><br>On 30/09/2022 09:08, Mihai wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">Hello,<br><br>First I would like to thank you for this amazing software!<br><br>I am running Bird 2.0.7 as RR for L3VPNs and on one RR the OSPF metric for the BGP NH is different than what's seen in BGP as shown below.<br><br>BGP PREF/METRIC = (100/61580) , OSPF_METRIC = 61480.<br><br><br>bird> sh route 10:10 94.207.96.0/19 all primary<br>Table vpntab4:<br>10:10 94.207.96.0/19 unicast [ROUTER1 2022-09-28 00:10:09 from 10.100.186.1] * (100/61580) [AS15802i]<br> Type: BGP univ<br> BGP.origin: IGP<br> BGP.as_path: 15802<br> BGP.next_hop: 10.100.184.8<br><br>bird> sh route 10.100.184.8/32<br>Table master4:<br>10.100.184.8/32 unicast [OSPF 2022-09-29 12:33:35] IA (150/61480) [10.100.186.5]<br><br>After restarting the BIRD OSPF adjancency the BGP metric changed to 61480.<br><br><br>Any help in understanding the issue would be much appreciated.<br><br>Thank you!<br></blockquote><br><br></blockquote></blockquote><br></pre></blockquote></div><div style='white-space: pre-wrap'><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>