[Routing Issue] There are two same net range routing on routing table.

[이재용]

Hello,

We use BIRD for communication with servers with higher-level switches.

But recently we came across the following case:
server run as a ecmp routing.
10.171.0.0/24 proto bird
    nexthop via 10.171.0.25 dev p0 weight 1
    nexthop via 10.171.1.25 dev p1 weight 1
For a change higher-level switches, we adjusted our ibgp LP value to flow traffic as a one path.  As we expected, servers routing are changed as one path routing 
10.171.0.0/24 proto bird
but, one server has a two same net range routing. like this sample
case1) 
10.171.0.0/24 proto bird10.171.0.0/24 proto bird metric 32
    nexthop via 10.171.0.25 dev ${interface1} 
    nexthop via 10.171.1.25 dev ${interface2} 
case2 )
10.171.0.0/24 proto bird metric 3210.171.0.0/24 proto bird
    nexthop via 10.171.0.25 dev ${interface1} 
    nexthop via 10.171.1.25 dev ${interface2} 
in case1, there was any problem , but in case 2 it had. (flow packet as two paths)in my thought, pervious routing not deleted. So, two same range is now avaliable.if there are someone who have same problem, would you advise for this problem? 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20240603/ab8a47d3/attachment.htm>