From: micsoniu@telus.net
Date: Tue Oct 04 2005 - 15:50:21 GMT-3
Sure:
The routing task specifically mentions that the routers will have to receive RIP
updates, since this is a backup link for the main one (FR) ...
Also, another specification is that each router should be able to dial the other
one.
The option you mentioned would be applicable if there is another condition to
trigger the call (dialer-watch, backup interface )... However, if the backup
interface solution is not allowed, the dialer watch is the other option and
we're back at square 0.
HTH
Quoting Victor Cappuccio <cvictor@protokolgroup.com>:
> Hello Narcis, please can you clarify a little bit the wording..
>
> Other point of view could be that RIP should not be part of the
> interesting traffic
>
> Looking forward to your email
> Regards
> Victor.
>
>
>
> micsoniu@telus.net wrote:
>
> >Would it be possibel to use the "ip rip triggered" feature on both routers
> >connected through ISDN in order to satisfy the following requirement ?
> >
> >- "Make sure ISDN does not stay up indefinitely"
> >
> >or snapshot routing is the only option ?
> >
> >Obviously, RIP is the only traffic going across this link...
> >
> >According to CCO:
> >
>
>http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/iprrp_r/ip2_i1g.htm#wp1040537
> >
> >"You might want to enable this feature if you are using an on-demand circuit
> and
> >you are charged for usage time. Fewer routing updates will incur lower usage
> costs."
> >
> >"Entries learned from a triggered response on the WAN are semipermanent;
> they do
> >not time out like other entries"
> >
> >Thank you
> >
> >Narcis
> >
> >_______________________________________________________________________
> >Subscription information may be found at:
> >http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:49 GMT-3