OSPF stuck in 2-way state

Kenth Eriksson Kenth.Eriksson at infinera.com
Mon Oct 7 16:38:13 CEST 2019


On Mon, 2019-10-07 at 12:50 +0000, Kenth Eriksson wrote:
> On Mon, 2019-10-07 at 14:44 +0200, Ondrej Zajicek wrote:
> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> > 
> > 
> > On Mon, Oct 07, 2019 at 12:23:56PM +0000, Kenth Eriksson wrote:
> > > Collected some more logs when the state machine becomes stuck. It
> > > appears as the eth1 has been DR when this stuck state happens. Note
> > > that interface transitions from Down to DROther in one step and then
> > > maintains that state even after prio is changed from 0 to 5.
> > > 2019-10-04 19:35:40.109 <TRACE> ospfv2_1: Changing priority of eth1 from 0 to 5
> > 
> > Thanks. Not sure why there is the prio change. In the first mail you
> > wrote that BIRD has 5 and Quagga has 0.
> > 
> The prio change is user driven, the user changed from prio 0 to 5 and
> then re-configured. So now bird has prio 5 and quagga 0. Initially both
> ends had prio 0.
> 
Shouldn't the interface state machine be kicked when interface priority
is changed? E.g. from ospf_iface_reconfigure, invoke ospf_iface_sm with
state ISM_NEICH?
> > --
> > Elen sila lumenn' omentielvo
> > 
> > Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
> > OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
> > "To err is human -- to blame it on a computer is even more so."



More information about the Bird-users mailing list