Page MenuHomeVyOS Platform

BFD Configuration causes flapping
Open, Requires assessmentPublicBUG

Description

The following BFD configuration causes the 10.0.10.12 peer to flap constantly:

admin@edge# show protocols bfd
 peer 10.0.10.11 {
     source {
         address 10.0.10.1
     }
 }
 peer 10.0.10.12 {
     source {
         address 10.0.10.1
     }
 }

It works perfectly with either this config:

admin@edge# show protocols bfd
 peer 10.0.10.11 {
     source {
         address 10.0.10.1
     }
 }
 peer 10.0.10.12 {
     source {
         interface eth0.10
     }
 }

or this config:

peer 10.0.10.11 {
    source {
        interface eth0.10
    }
}
peer 10.0.10.12 {
    source {
        interface eth0.10
    }
}

This is the example of the error from the VyOS side:

Jun 19 03:35:09 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:09 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:09 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:09 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:09 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] up -> down reason:neighbor-down
Jun 19 03:35:10 edge bfdd[1222]: state-change: [mhop:no peer:10.0.10.12 local:0.0.0.0 vrf:default ifname:eth0.10] down -> up

And this is what it looks like from the peer side:

jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection closed 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection opened by remote host 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection closed 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection opened by remote host 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection closed 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection opened by remote host 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection closed 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection opened by remote host 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1 
jun/18 22:35:10 route,bgp,info Connection closed 
jun/18 22:35:10 route,bgp,info     RemoteAddress=10.0.10.1

Details

Difficulty level
Unknown (require assessment)
Version
1.3
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)