From: Sandy Turnage (sturnage@xxxxxxxxxxx)
Date: Mon Feb 05 2001 - 00:13:55 GMT-3
As far as I know the best way to setup EIGRP and DDR (not dial backup) is
to use a dialer-list which specify's EIGRP traffic as uninteresting in
conjunction with a floating static route to (re)establish the dialup
connection when interesting traffic does indeed arrive. However, since it
has long been rumored that proctors have a deeply held aversion to any type
static route, it occurred to me that I might have to make this work without
using a floating static route. So I have spent most of the afternoon
playing with various configurations in a somewhat futile effort to
accomplish this.
My first thought was to increase the hello-interval and hold-time so that
the once the neighbor relationship was established the idle timer could
drop the line between hello packets but this didn't work well at all. It
seems that as soon as the link drops, EIGRP wants to notify his neighbors
of a topology change and brings the line right back up. I tried this with
legacy DDR and Dialer profiles with the same results. Am I missing
something here ?
My approach for the next attempt was to assign addresses to the dialer
profile interfaces which are *not* part of the EIGRP network statement,
then setup a GRE tunnel between these addresses, assign IP addresses to the
tunnel interfaces which *are* a part of the EIGRP network statement, then
increase the hello-interval and hold-time, decrease the idle-timer and
increase the hold-queue. This seems to work pretty well. I am basically
taking advantage of the nature of GRE tunnels, if they are based on
non-dynamically-learned addresses then they don't seem to ever go
down/down. Since EIGRP is looking at the tunnel interface and not the
dialer, he doesn't see a topology change. Not exactly something I would
want to put in production but it seems to fix this particular problem.
What are my other options for EIGRP/DDR? Is there a way to leverage the
dialer-watch for this scenario?
TIA,
Sandy Turnage
Global Data Systems
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:36 GMT-3