Re: eigrp, frame relay, and ISDN
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]
Re: eigrp, frame relay, and ISDN
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]">news: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, 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]
Re: eigrp, frame relay, and ISDN
"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 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]
Re: eigrp, frame relay, and ISDN
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 routing table for the specified route(s) and kicks off the dialer if this route disappears (i.e. the primary connection fails)). To keep the EIGRP hello's from keeping my link up I used the a dialer-list commands which referenced an extended access-list similar to the following: int async 1 dialer-group 1 dialer-list 1 protocol ip list 100 access-list 100 deny eigrp any any access-list 100 permit ip any any Remember the dialer-list specifies interesting traffic and *not* what traffic is actually allowed to cross the link. Once the dialer watch-group brings up the link the EIGRP hellos will be allowed and the routers should establish neighbor relationships. One thing to remember is that your dialer map statement should reference the subnet that you are watching. There is also a "dialer watch-disable" that lets you specifiy how the primary link must be up before the dial-backup connection is dropped. You may want to search the archives for the CCIELAB mailing list .. there is some excellent information relating to EIGRP and ISDN there. Hope this helps, Sandy Turnage 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]
eigrp, frame relay, and ISDN
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]
