From: Todd Veillette (tveillette@myeastern.com)
Date: Sat Dec 21 2002 - 02:42:14 GMT-3
RE: Dialer WatchThanks, Jason. That's exactly what we did do. We have about
120 bri clients
supported by 4 Pri's. With 300 you must know what a pain ISDN to support.
Our biggest problem by far is the loss of long distance calling capabilities
from the clients back to us. Seems telcos change or upgrade switches in
the cloud quite often with no regard as where the bri is picked for long
distance.
We constantly are dealing with remote clients not able to call long distance
any more
after a loss of frame relay. The telcos are clueless, except for billing.
What's even worse is after the long distance is gone the bri continuously
initiates
calls but never succeeds due to no successful chap auth. And the morons
telcos still bill because they see the call go thru...100's of calls every 20
seconds
each billed at a minute for rounding up.
Any way I guess I'm venting. ,, Any suggestions, or what do you do to get
around this?
(Unfortunately callback can't be used. Management refuses to deal with
billing)
TIA,
-TV
----- Original Message -----
From: Coleman, Jason
To: 'Todd Veillette' ; Tim Fletcher
Cc: ccielab@groupstudy.com
Sent: Friday, December 20, 2002 2:57 PM
Subject: RE: Dialer Watch
Sounds like you need to use floating statics along w/ interesting traffic to
get what you want.
You can have a static route for the network that you want to monitor, with a
high distance. Then if your routing protocol fails for any reason your
floating static will point to the other side of your ISDN call. Interesting
traffic will determine what type of traffic will bring up and keep up the
call.
Make sure that you build your interesting traffic properly. Deny your
routing protocol as interesting or the call will never come down. I usually
also block NTP, SNMP, ICMP, and other commonly used management traffic types.
I use this same setup for about 300+ ISDN sites that work 8x5x5 or 8x8x7.
Jason Coleman - CCNP, CCDP
Customer Engineer
Network Management Center - Austin
(ph) 512-340-3134
(email) colemaj@netsolve.com
-----Original Message-----
From: Todd Veillette [mailto:tveillette@myeastern.com]
Sent: Thursday, December 19, 2002 11:10 PM
To: Tim Fletcher
Cc: ccielab@groupstudy.com
Subject: Re: Dialer Watch
Exactly my point! Any Cisco listeners out here .
Dialer watch is a solid backup for a 24/7 client
but for 8x5x5 clients it is not.
When the client gets the $500 bill for being up
18 hours on a Sunday due to a DAX eating itself,
it is not, "Great Job" that I typically hear in response.
How about an option where the idle time out, after
a dialer-watch event, sets a flag converting to DDR
then clears the flag when the route comes back?
-TV
----- Original Message -----
From: "Tim Fletcher" <tim@fletchmail.net>
To: "Todd Veillette" <tveillette@myeastern.com>; <ccielab@groupstudy.com>
Cc: <ccielab@groupstudy.com>
Sent: Thursday, December 19, 2002 11:12 PM
Subject: Re: Dialer Watch
> Dialer watch doesn't work that way. Once it comes up it will stay up until
there is another route. Interesting traffic is irrelevant. Usually I do not
even define a dialer-group.
>
> It does however use the idle-timeout interval to determine how often to
check the routes.
>
> -Tim Fletcher
>
> At 06:31 PM 12/19/02 -0500, Todd Veillette wrote:
> >Along the same lines, dialer watch works great -
> >EXCEPT I have yet to come up with a dialer watch
> >solution that comes up when you lose your route(s)
> >AND will go back down based on not having any
> >interesting traffic over the route(s).
> >
> >Any Ideas?
> >-TV
> >
> >
> >----- Original Message -----
> >From: "Tim Fletcher" <tim@fletchmail.net>
> >To: "rehan u nedaria" <rehannedaria@rediffmail.com>;
> ><ccielab@groupstudy.com>
> >Sent: Thursday, December 19, 2002 11:47 AM
> >Subject: Re: Dialer Watch
> >
> >
> >> Rehen,
> >>
> >> That the way I've always done it. If you define interesting traffic,
the
> >> link can come up even if your route is still valid. So if you only want
it
> >> to come up when your route disappears, don't define interesting
traffic.
> >>
> >> -Tim Fletcher
> >>
> >> At 12:31 PM 12/19/2002 +0000, rehan u nedaria wrote:
> >> >Hi Guys
> >> > A query on dialer watch-list.I was going through a scenario
> >> > where they had asked me that if a specific network goes down say
> >10.0.0.0
> >> > then the isdn should trigger.
> >> >
> >> >I used dialer watch list where i did not used the diler-group command
for
> >> >intresting traffic.This works fine.
> >> >
> >> >Is this configuration without creating the intresting traffic is
right.
> >> >
> >> >Regards
> >> >Rehan
> >> >.
> >> .
> >.
.
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:50 GMT-3