Default route prevents NHT from working

Unanswered Question
Aug 24th, 2009

I've got a campus MPLS network and I'm stuck with an EIGRP default route that I can't get rid of until everything is migrated to its proper VRF. This is causing me pains with BGP next-hop tracking. The core switches don't clear out the neighbor right away when the interface goes down. Let's say I want to remove the default route from the global routing table but keep default routing behavior, I was thinking of putting aggregated routes for all the IPv4 space, like, ... in my WAN distribution block pointing to the same next-hop IP as my default route, then remove the default route entirely from EIGRP. Is this approach been implemented before or is there a better way of doing it? I am using a Cat 6500 with a Sup 720, and selective NHT is not available :(

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Laurent Aubert Tue, 09/01/2009 - 05:18


Aggregate routes will not help. You will have the same behavior as with the default one.

If it's supported, you can try BGP Fast Peering Session Deactivation but it's useful for iBGP session only if there is no RR.

The behavior is the same as NHT except it focus on the neighbor address instead of the NH.

You can attach a route-map to this feature to select which routes to watch (like S-NHT):

If it's not possible, you can always decrease the BGP timers for faster peer failure detection but be careful of the CPU impact.



silemire Tue, 09/01/2009 - 05:37

Thanks for your input Laurent,

I've decided to reduce the BGP timers.


This Discussion