We do this on our network.
Do not pacify the BRI under EIGRP.
Instead define EIGRP as uninteresting traffic for the BRI.
Define a floating static to intiate the call with interesting traffic, then once the
ISDN is
up, EIGRP will flow across the link. If and when the primary link comes back up th
"backup" also works very nicely in this senario also, with the dialer
interfaces.
""whitaker"" <[EMAIL PROTECTED]> wrote in message
939a8i$cnt$[EMAIL PROTECTED]">news:939a8i$cnt$[EMAIL PROTECTED]...
> So here's the scenario...Numerous routers in a central site connected to
> other remote sites vi
While I haven't set this scenario up in production, I have played with a simlar
configuration in my home lab using async dial backup. I configured the async interface
with a dialer watch-group and (of course) a matching dialer watch-list for the desired
subnet. (The dialer-watch monitors the routi
So here's the scenario...Numerous routers in a central site connected to
other remote sites via frame-relay with backup ISDN. Question: What is the
best way to implement EIGRP in this scenario? My thoughts were to run EIGRP
over the frame, set up the dialer interface / bri as a passive interface
Dear whit,
What are u running frame-relay on (ie. frame-relay switch "passport"?)
anyways yes ur idea is right u can give floating static routes with higher
admin distance but why eigrp why not ospf (my fav ).
"Cheers"
""whitaker"" <[EMAIL PROTECTED]> wrote in message
939a8i$cnt$[EMAIL PROTECTED
So here's the scenario...Numerous routers in a central site connected to
other remote sites via frame-relay with backup ISDN. Question: What is the
best way to implement EIGRP in this scenario? My thoughts were to run EIGRP
over the frame, set up the dialer interface / bri as a passive interface
6 matches
Mail list logo
