RE: ISDN dialer watch VS floating static routes [7:31609]

2002-01-13 Thread Charlie Wehner
Thanks for the advice Benjamin and Jenny. It sounds like you have to be careful when implementing dialer watch. (Especially, if you only want to bring up the link for 'interesting traffic'. I guess since 'dialer watch' is fairly new most people have 'floating static routes' in place. Message

RE: ISDN dialer watch VS floating static routes [7:31609]

2002-01-13 Thread R. Benjamin Kessler
though; I intend to kick the tires of dialer watch a bit more myself. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Sunday, January 13, 2002 6:31 PM To: [EMAIL PROTECTED] Subject: Re: ISDN dialer watch VS floating static ro

Re: ISDN dialer watch VS floating static routes [7:31609]

2002-01-13 Thread [EMAIL PROTECTED]
I have always used floating statics to back up a frame relay network. Why? Easy - we're only just migrating to IOS 12.1. And anyway, this particular network has been using floating static routes for the last several years (since *long* before dialer watch was available) - they are flexible, suit

ISDN dialer watch VS floating static routes [7:31609]

2002-01-10 Thread Charlie Wehner
When configuring an ISDN backup for a frame relay circuit do most people typically use "dialer watch" or "floating static routes". In my scenerio, it's for an eigrp network and a single router. I've seen the following article on Cisco's website: http://www.cisco.com/warp/public/123/backup-main.