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 the
ISDN will time-out even if EIGRP flows across. Unteresting traffic does not reset the
IDLE timer.
Simple way to think about it is...
Only interesting traffic can initiate a call and reset the IDLE timer.
Uninteresting traffic can and will flow if the link is already up.
The part which makes it confusing...the definition of interesting and unteresting
traffic
looks just like an access list.
The difference is how you apply it to the interface
'dialer-group' vs 'access-group'
Jim
whitaker wrote:
> 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,
> and use floating static routes (static route with higher administrative
> distance for ISDN backup)
>
> Thoughs, comments, suggestions, ridicules? ;-)
>
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
