RE: Dialer watch backup & RIP v2

From: Kamran Sadiq (ksadiq@cisco.com)
Date: Thu Mar 27 2003 - 17:33:30 GMT-3


Since RIP considers hop-count as cost so it will load balance across the
primary and ISDN link when the primary link comes back up. Use offset-list
at Dialer Watch router to increase the hop count for all the routes learned
through ISDN interface. Now the router will not do load balancing and the
Dialer Watch works perfect.

You can also use "ip rip triggered" at both end of the ISDN link and remove
the Dialer Watch. This feature works exactly as OSPF demand circuit in OSPF.

Same is true for ISIS but in case of ISIS you can use "isis metric 20" under
ISDN link at Dialer watch router to stop it from doing load balancing and
that fixes the problem with Dialer Watch

Kamran Sadiq

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
jfaure@sztele.com
Sent: Thursday, March 27, 2003 1:19 PM
To: ccielab@groupstudy.com
Subject: Dialer watch backup & RIP v2

Hi all:

Anybody can tell me if you can use dialer watching backup with Rip v2. This
is, having Ripv2 as the routing protocol in the backup line. I've tried it,
the backup link comes up when it's needed but when the watched route appear
newly through the primary interface (and then the backup must be down) the
isdn line doesn't go down.

I've tried dialer watch with OSPF, and with EIGRP too and it works totally
fine. Besides, if you read about this feature in the support CD, it says
you can use it with IGRP, EIGRP or OSPF. None about RIP.

Anybody has any experience with this and can help?

Regards

Juan Faure Ferrer
email: jfaure@sztele.com

Lmnea de Negocio de Telematica y CC
Ingeniero de Integracisn de Redes y Sistemas
----------------------------------------------------------------------------

SOLUZIONA TELECOMUNICACIONES
Servicios Profesionales de UNION FENOSA
Jerez, 3
28016 MADRID
tel 91 579 30 00 fax 91 350 72 83
---------------------------------------------------------------------------



This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:45 GMT-3