networks.
For debug purposes I did filter those announcements and problem was fixed.
I did remove filter to test if the announcement loop was gone and it was
for now.
No configuration changes to bgpd.conf before or after upgrade (except that
filter after the high cpu load reason was found).
Br
-Esa
And before anyone asks, I did check eBGP peers that networks in question
did not repeatedly update and withdrew. Update messages between eBGP peers
are nominal.
Br
-Esa
On Sat, May 23, 2020 at 12:47 AM Esa Kuusisto
wrote:
> Hi
>
> I upgraded today two openbsd routers with openbgpd
Exact configs are sent.
Thanks
-Esa
On Sat, May 23, 2020 at 11:23 AM Claudio Jeker wrote:
> On Sat, May 23, 2020 at 12:47:58AM +0300, Esa Kuusisto wrote:
> > Hi
> >
> > I upgraded today two openbsd routers with openbgpd from 6.6 -> 6.7.
> Upgrade
> > was d
>On Fri, Oct 25, 2019 at 11:46 PM Claudio Jeker wrote:
> > On Fri, Oct 25, 2019 at 11:09:14PM +0300, Esa Kuusisto wrote:
> > > Hi
> > >
> > > I encountered a BGPD problem after upgrade from 6.5 -> 6.6. BGPD
> crashes to
> > > "fatal in R
Hi
I encountered a BGPD problem after upgrade from 6.5 -> 6.6. BGPD crashes to
"fatal in RDE: prefix_adjout_update: update for non existing prefix"
problem.
Environment:
Two OpenBGPD instances. Primary (ROUTER1, now 6.5) and secondary 6.6
(ROUTER2). Two iBGP instances to local switches (SW1 and S
>On Sat, Oct 26, 2019 at 11:21 AM Claudio Jeker wrote:
> > On Sat, Oct 26, 2019 at 12:13:58AM +0300, Esa Kuusisto wrote:
> > > >On Fri, Oct 25, 2019 at 11:46 PM Claudio Jeker
> wrote:
> > >
> > > > > On Fri, Oct 25, 2019 at 11:0
even drm from kernel and it did not solve the issue as
system refused to work then. I have tried different options is system bios
to find workaround but no success. Same issue with SP kernel.
Br
Esa Kuusisto
top -S -U
load averages: 0.48, 0.18, 0.18
box 23:28:51
71 processes:
