From: Cristian Henry H (chenry@reuna.cl)
Date: Wed Oct 16 2002 - 09:53:01 GMT-3
With Dialer-Watch, any way, defining interesting traffic could be
necesary to prevent periodic hellos (from OSPF for instace) ressetting
the dialer idle-timeout avoinding the router deactivate the backup link.
Only when idle-timeout expire the router deactivate the backup link!
Jerry Haverkos wrote:
>
> Another difference?
>
> Dialer Watch keeps the ISDN circuit up, interesting tarffic or not. It keeps
> checking for the routing table routes to indicate a Primary is up.
>
> Floating static routes and other mechanisms allow the ISDN circuit to go
> down when there is no interesting traffic.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> syv
> Sent: Tuesday, October 15, 2002 6:39 PM
> To: MADMAN
> Cc: ccielab@groupstudy.com
> Subject: Re[2]: Dialer watch
>
> On Tuesday, October 15, 2002, MADMAN wrote:
>
> Big differences between floating statics and dialer watch:
> [assumed dealing with ISDN]
>
> Floating static: Need interesting traffic to trigger
> All protocols
> Only 1 router
> Cannot trigger on threshold
> Depend on routing protocol convergence time
> Dialer watch: Route disapearing from routing table
> Only IGRP/EIGRP/OSPF
> Multiple routers
> Can trigger on threshold
> Very fast
>
> -----Original Message-----
> M> I have never used dialer watch but have seen a few threads on it's use
> M> and I don't see much differance between it and a simple floating static
> M> route, ( my method of choice).
>
> M> I know I must be missing something...
>
> M> Dave
>
> M> syv wrote:
> >>
> >> On Tuesday, October 15, 2002, Azhar Mehmood wrote:
> >>
> >> Characteristics of dialer watch:
> >>
> >> * Watches specific routes in the routing table and initiates
> >> backup link if the route is missing
> >> * Encapsulation independent
> >> * Evaluates status of primary link based on the existence of
> >> routes to the peer. Hence it considers primary link status
> >> based on the ability to pass traffic to the peer
> >> Does not rely on interesting packets to trigger dialing
> >> Dialing the backup link is done immediately when the primary
> >> route is lost
> >> * Dependent on the routing protocol convergence time
> >> only IGRP/EIGRP/OSPF supported
> >> * Supports multiple router backup scenario
> >> * Bandwidth on demand is not possible since the route to the
> >> peer will exist regardless of the load on the primary link
> >> Triggered by:
> >> 1. Interesting packets defined with DDR
> >> 2. Connection loss on primary interface
> >> 3. Traffic threshold being exceeded
> >>
> >> -----Original Message-----
> >> AM> Hi,
> >>
> >> AM> I have a router R1 ehich has 3 exit points to reach a specific
> subnet:
> >>
> >> AM> 1. Ethernet
> >> AM> 2. Serial
> >> AM> 3. ISDN
> >>
> >> AM> As long the route over ethernet is available it's prefered over all
> other, after it has gone serial is prefered and as third option the ISDN
> Link.
> >>
> >> AM> Now my problem is how to keep ISDN Link down until both of the
> primary links are available. I tried to acomplish it with dialer watch but
> as soon as the ethernet is gone dialer watch triggers
> >> the
> >> AM> call hence it brings it also down again after idle-timeou
> >> AM> t.
> >>
> >> AM> My question is how to configure the router that it waits until both
> of the link 're unavailable and triggering than an isdn call.
> >>
> >> AM> regards
> >>
> >> AM> AZHAR MEHMOOD
> >> AM> GERMANY
> >>
> >> Thanks
> >> --
> >> syv@911networks.com
>
> Thanks
> --
> syv@911networks.com
-- Cristian E. Henry REUNAE-mail: chenry@reuna.cl Fono: 56-2-3370336
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:48 GMT-3