<div dir="ltr">Unfortunately, this is horrible, but no. iBGP peers exchange AIGP attributes. Workaround would be to switch to using eBGP sessions temporarily if possible.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 30, 2023 at 3:27 PM mike tancsa <<a href="mailto:mike@sentex.net">mike@sentex.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi,</p>
<p> Thanks for the explanation. Is there any way to work around
this via configuration ? e.g. temporarily ignore the setting as
Transitive ? This makes for upgrading very intrusive as I have to
upgrade all the ibgp routers at once which is very service
effecting. <br>
</p>
<p> ---Mike<br>
</p>
<div>On 6/30/2023 3:20 AM, Donatas Abraitis
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Hello, Mike!</div>
<div><br>
</div>
<div>
<p>With the 8.5.0 release, the new BGP attribute AIGP
(Accumulated IGP Metric Attribute) was introduced. This
new attribute was mistakenly set as Transitive. This was
fixed (<a href="https://github.com/FRRouting/frr/commit/53afb27eb892a107c9426a01dbba82bee6fa86a7" target="_blank"><tt>53afb27</tt></a>)
with the 8.5.2 release, but it's not backward-compatible
between 8.5.x versions. We suggest using only the latest
version of the 8.5 release.</p>
<p>If you see such errors/notifications, upgrade to the
latest 8.5.x versions, and avoid using 8.5.0, and 8.5.1.</p>
<span>
<div>
<pre><code>AIGP attribute must be flagged as "Transitive"
</code></pre>
</div>
</span>
<div>
<pre><code>%NOTIFICATION: received from neighbor X.Y.Z.W 3/4 (UPDATE Message Error/Attribute
Flags Error) 14 bytes 80 1a 0b 01 00 0b 00 00 00 00 00 00 00 01
</code></pre>
</div>
<p>(This affects only iBGP sessions).</p>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jun 30, 2023 at
12:09 AM mike tancsa <<a href="mailto:mike@sentex.net" target="_blank">mike@sentex.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,
I am guessing it is this commit ?<br>
<br>
commit 231e4de73f46b9c75a07bf0144aafce18aeb3a55<br>
Author: Donatas Abraitis <<a href="mailto:donatas@opensourcerouting.org" target="_blank">donatas@opensourcerouting.org</a>><br>
Date: Mon May 8 22:49:10 2023 +0300<br>
<br>
bgpd: Make sure AIGP attribute is non-transitive<br>
<br>
The AIGP attribute is an optional, non-transitive BGP
path attribute.<br>
<br>
Signed-off-by: Donatas Abraitis <<a href="mailto:donatas@opensourcerouting.org" target="_blank">donatas@opensourcerouting.org</a>><br>
<br>
<br>
Is there a way to work around this in configs ?<br>
<br>
---Mike<br>
<br>
On 6/29/2023 2:39 PM, mike tancsa wrote:<br>
> I was updating an internal distribution router that got
wedged in <br>
> vtysh from 8.5 to 8.5.2 and found all my ibgp peers would
not come up. <br>
> Same error on the half dozen peers<br>
><br>
> Jun 29 14:00:55 ibgp-4 bgpd[38150]: [HZN6M-XRM1G]
%NOTIFICATION: <br>
> received from neighbor xx.yy.zz.251 3/4 (UPDATE Message <br>
> Error/Attribute Flags Error) 14 bytes 80 1a 0b 01 00 0b
00 00 00 00 00 <br>
> 00 00 01<br>
> Jun 29 14:01:00 ibgp-4 bgpd[38150]: [HZN6M-XRM1G]
%NOTIFICATION: <br>
> received from neighbor xx.yy.zz.251 3/4 (UPDATE Message <br>
> Error/Attribute Flags Error) 14 bytes 80 1a 0b 01 00 0b
00 00 00 00 00 <br>
> 00 00 01<br>
> Jun 29 14:01:05 ibgp-4 bgpd[38150]: [HZN6M-XRM1G]
%NOTIFICATION: sent <br>
> to neighbor xx.yy.zz.251 3/4 (UPDATE Message
Error/Attribute Flags <br>
> Error) 14 bytes c0 1a 0b 01 0<br>
><br>
> On the older versions of frr,<br>
><br>
> [NYD0B-A3BTB][EC 33554433] AIGP attribute must be flagged
as "Transitive"<br>
> [HZN6M-XRM1G] %NOTIFICATION: sent to neighbor
xx.yy.zz.241 3/4 (UPDATE <br>
> Message Error/Attribute Flags Error) 14 bytes 80 1a 0b 01
0<br>
> [GW152-RVASS][EC 33554455] bgp_process_packet: BGP UPDATE
receipt <br>
> failed for peer: xx.yy.zz.241<br>
><br>
> I downgraded from 8.5.2 to 8.5.1 and all was good. Also,
another peer <br>
> thats still running 7.x was fine with it all.<br>
><br>
><br>
> Nothing special about the config. One of the untouched
boxes running 8.5<br>
><br>
> neighbor THOTLAN peer-group<br>
> neighbor THOTLAN remote-as 11647<br>
> neighbor THOTLAN description Core1LanEx<br>
> neighbor THOTLAN update-source [dot.251]<br>
> neighbor .241 peer-group HOTLAN<br>
> neighbor .241 description The box the flipped out<br>
> neighbor .241 bfd<br>
> neighbor THOTLAN activate<br>
> neighbor THOTLAN next-hop-self<br>
> neighbor THOTLAN weight 111<br>
><br>
> The box I tried to upgrade from 8.5 to 8.5.2 that then
went back to 8.5.1<br>
><br>
> neighbor THOTLAN peer-group<br>
> neighbor THOTLAN remote-as 11647<br>
> neighbor THOTLAN update-source [dot.241]<br>
> neighbor THOTLAN timers 16 50<br>
> neighbor .251 description One of the many other peers
that didnt like me<br>
> neighbor .251 bfd<br>
> neighbor THOTLAN activate<br>
> neighbor THOTLAN next-hop-self<br>
> neighbor THOTLAN soft-reconfiguration inbound<br>
> neighbor THOTLAN weight 109<br>
><br>
><br>
> ---Mike<br>
><br>
><br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote></div>