We have a routing table where we have 2 routes to 20.0.0.0/24.
I am trying to make second route to 20.0.0.0/24(via 71.0.0.0/24) active.
I put a filter on BGP peer from where this route is coming from(to change the scope to “20”
After that first route, which was active before(via 70.0.0.0/24) suddenly becomes NOT ACTIVE.
But still WORKING as before.
But traceroute output is changed after.
It’s all good from the functionality perspective, but I am confused with the view of the routing table showed to me.
(attached screenshot)

I believe I fixed my issue.
It’s not that I found why it was looking weird.
I just changed my approach and it’s working fine as before and showing everything good now.
- Instead of decreasing the scope of incoming iBGP routers to 20, I increased the target-scope of incoming iBGP routes to 45.
This made those routes resolvable
Also I increased the distance to 210 as before and decreased the bgp-local-pref to 90. To make those routes less preferable. - I learned that BGP takes 2-3 minutes to recognise the changes.
Before I was rushing to see the difference too fast and was confused
On the screenshot you can see it’s working as expected now.
