holddown (routes that are in the pending state before being declared inactive).
A holddown route was once the active route and is no longer the active route. The route is in the holddown state because a protocol still has interest in the route, meaning that the interest bit is set. A protocol might have its interest bit set on the previously active route because the protocol is still advertising the route. The route will be deleted after all protocols withdraw their advertisement of the route and remove their interest bit. A persistent holddown state often means that the interested protocol is not releasing its interest bit properly. However, if you have configured advertisement of multiple routes (with the add-path or advertise-inactive statement), the holddown bit is most likely set because BGP is advertising the route as an active route. In this case, you can ignore the holddown state because nothing is wrong.
As per the given 126.96.36.199/22 route details, it is in secondary state and nexthop is lt-1/2/0.1 interface which means that it is leaked from another route table. Could you share the policy configuration which rejects route leaking?
Thanks, Nellikka JNCIE x3 (SEC #321; SP #2839; ENT #790) Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too!!!
Yes, you may be learning from MP-BGP from another PE. For example 10.98.146.42. Check if you have this route in your inet.3 table. In other words, do you have the ldp router or rsvp lsp to 10.98.146.42?
I assume those routes are not learned from CE, right?
What I noticed is that some of the routes are pointing to Next Hop of an logical-tunnel (lt-x/x/x). By any chance do you have a lt tunnel between your inet.0 and vrf.inet.0 ?
Some times, some customers choose to use a physical loopback or lt between two instances and run protocol to share routes. This is similar to use RIB-GROUP, but you don't want to use both at the same time