Skip to content

Removing the bfd from a single static route removes the bfd session even if there are more static routes using same gateway with bfd #19014

@rsys-spaul

Description

@rsys-spaul

Description

Removing the bfd from a single static route removes the bfd session even if there are more static routes using the same gateway with bfd.

Version

frr-10.3.1

How to reproduce

Add 2 static routes like below:

ubu-22(config)# ip route 1.1.1.1/32 10.0.2.2 bfd
ubu-22(config)# ip route 1.1.1.2/32 10.0.2.2 bfd

Now check the bfd session:

ubu-22(config)# do show bfd peers brief 
Session count: 1
SessionId  LocalAddress                             PeerAddress                             Status         
=========  ============                             ===========                             ======         
3371454751 unknown                                  10.0.2.2                                down           
ubu-22(config)# 

Remove the bfd from one of the static route:

ubu-22(config)# ip route 1.1.1.1/32 10.0.2.2
ubu-22(config)# do show running-config 
Building configuration...

Current configuration:
!
frr version 10.3.1
frr defaults traditional
hostname ubu-22
service integrated-vtysh-config
!
ip route 1.1.1.1/32 10.0.2.2
ip route 1.1.1.2/32 10.0.2.2 bfd
!
end

Now check the bfd session again:

ubu-22(config)# do show bfd peers brief 
Session count: 0
SessionId  LocalAddress                             PeerAddress                             Status         
=========  ============                             ===========                             ======         
ubu-22(config)# 

Expected behavior

The bfd session should not be removed as there is at least 1 static route has a bfd config for the gateway.

Actual behavior

In this version of frr, the session is getting removed which is not expected as there is a static route if bfd present.

Additional context

No response

Checklist

  • I have searched the open issues for this bug.
  • I have not included sensitive information in this report.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageNeeds further investigation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions