From: Karim (karim_ccie@hotmail.com)
Date: Sun Jun 13 2004 - 21:00:28 GMT-3
Thanks for both of you.
Karim.
----- Original Message -----
From: <tycampbell@comcast.net>
To: "John Cameron (johcamer)" <johcamer@cisco.com>
Cc: "Karim" <karim_ccie@hotmail.com>; <ccielab@groupstudy.com>
Sent: Monday, June 14, 2004 2:47 AM
Subject: RE: Watch-list question....
> Thanks :-)
>
>
> > Good point!
> >
> >
> > JDC
> >
> > -----Original Message-----
> > From: Ty [mailto:tycampbell@comcast.net]
> > Sent: Sunday, June 13, 2004 5:20 PM
> > To: John Cameron (johcamer); Karim; ccielab@groupstudy.com
> > Subject: Re: Watch-list question....
> >
> > You can create a separate dialer watch group for each route, specifying
> > one route for each dialer watch.
> >
> > Don't forget the extra dialer map statements that you will need...one
> > for each dialer-watch group
> >
> > I am not 100% sure, but I think you can have a total of 7 different
> > watch groups
> > ----- Original Message -----
> > From: "John Cameron (johcamer)" <johcamer@cisco.com>
> > To: "Karim" <karim_ccie@hotmail.com>; <ccielab@groupstudy.com>
> > Sent: Sunday, June 13, 2004 9:22 AM
> > Subject: RE: Watch-list question....
> >
> >
> > > Karim,
> > >
> > > For the first scenario - I would use two floating static and
> > dialer-map
> > > statements.
> > >
> > > For the second scenario, I would use dialer-watch. Dialer-watch will
> > > not kick in until ALL "watched" routes are lost - so it would not work
> > > for your first scenario.
> > >
> > > From Cisco IOS Dial Technologies Configuration Guide, Release 12.3:
> > >
> > > "Monitoring the watched routes is done in the following sequence:
> > >
> > > 1. Whenever a watched route is deleted, Dialer Watch checks whether
> > > there is at least one valid route for any of the defined watched IP
> > > addresses.
> > >
> > > 2. If no valid route exists, the primary line is considered down and
> > > unusable.
> > >
> > > 3. If a valid route exists for at least one of the defined IP
> > addresses
> > > and if the route is pointing to an interface other than the backup
> > > interface configured for Dialer Watch, the primary link is considered
> > > up.
> > >
> > > 4. If the primary link goes down, Dialer Watch is immediately notified
> > > by the routing protocol and the secondary link is brought up.
> > >
> > > 5. Once the secondary link is up, at the expiration of each idle
> > > timeout, the primary link is rechecked.
> > >
> > > 6. If the primary link remains down, the idle timer is indefinitely
> > > reset.
> > >
> > > 7. If the primary link is up, the secondary backup link is
> > disconnected.
> > > Additionally, you can set a disable timer to create a delay for the
> > > secondary link to disconnect, after the primary link is reestablished.
> > "
> > >
> > >
> > > HTH,
> > > JDC
> > >
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> > Of
> > > Karim
> > > Sent: Sunday, June 13, 2004 9:55 AM
> > > To: ccielab@groupstudy.com
> > > Subject: Watch-list question....
> > >
> > > Hi all,
> > >
> > > Would like to know the difference between the following 2 scenarios:
> > > - When asked to initiate a call when losing reachability to any of 2
> > > given routes to watch.
> > >
> > > I believe that I need to create 2 dialer-maps statement (if using
> > legacy
> > > DDR) plus dialer watch-group (in either legacy or dailer interfaces).
> > > Whenever the reachability lost to any of the two routes, a call will
> > be
> > > initiated.
> > >
> > > - I asked not to initiate a call only if reachability lost to both
> > > routes, what will be the solution ????
> > >
> > >
> > > Regards,
> > > Karim.
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:40 GMT-3