From: Aidan Marks (amarks@cisco.com)
Date: Fri Jan 03 2003 - 10:29:24 GMT-3
At 11:38 PM 3/01/2003, Evgeny Tantsura wrote:
> > The dialer-watch will look for a network not a host, unless the /32 is in
> > the routing table.
> > You also need to map the next hop for that particular
> > network and host to go over the dialer interface.
>
>I think explicit mapping is needed only if legacy DDR is used.
>Dialer prifiles maps next hop dynamically.
Correct, if using dialer profiles with dialer watch, you don't have to
create a dialer map (actually you can't due to the dialer map command being
invalid with a pool configuration), unless you are using rotary
groups/dialer in-band (DDR) on the dialer profile.
Aidan
> >
> > HTH
> >
> > John E.
> > CCIE #8150
> >
> >
> >
> > >From: "Sam Lai" <slai@gggroup.net>
> > >Reply-To: "Sam Lai" <slai@gggroup.net>
> > >To: "Evgeny Tantsura" <ivgen@castel.nl>
> > >CC: <ccielab@groupstudy.com>
> > >Subject: RE: ISDN Backup With Dialer Watch
> > >Date: Thu, 2 Jan 2003 12:39:06 -0500
> > >
> > >In a nutshell, if "ip ospf demand-circuit" is the one to keep, then
> > >"access-list 170 deny ospf any any" should be taken out. However, since it
> > >sounds like a "watch-list" scenario, then you are right, "ospf
> > >demand-circuit" should be out. Note that the routers should be configured
> > >to prevent ospf hellos from activating the dialer, in case ospf is enable
> > >on the dialer interfaces. Or ospf should not be included on the dialer
> > >interfaces, and some static routes may be needed.
> > >
> > >Sam
> > >
> > >-----Original Message-----
> > >From: Evgeny Tantsura [mailto:ivgen@castel.nl]
> > >Sent: Thursday, January 02, 2003 12:25 PM
> > >To: Sam Lai
> > >Cc: ccielab@groupstudy.com
> > >Subject: RE: ISDN Backup With Dialer Watch
> > >
> > >
> > >The whole problem was ip ospf demand-circuit command on the calling router
> > >and thus no ip traffic as expected.
> > >
> > >
> > > > It seems that you configure the watch-list to track on a host route -
> > >192.168.5.1/32 - "dialer watch-list 1 ip 192.168.5.1 255.255.255.255".
> Note
> > >that if there is no such route in routing table on the 1st router (has
> > >watch-list configured) come from the primary interface (being
> watch-group),
> > >watch-list will activate the dialing. But you may want to take "ospf
> > >demand-circuit" into the equation. If you have ospf demand-circuit
> > >configured, you should not block the ospf traffic on the dialer-list. ospf
> > >demand-circuit will take care of the hello suppression. That makes me
> think
> > >that the reason to dial is not by watch-list, it is rather from the 2nd
> > >router (w/o watch-list) for ospf adj. Check with "show dialer" on both
> > >routers to find out.
> > > >
> > > > It would be great if you can provide the complete configuration on both
> > >routers.
> > > >
> > > > Sam
> > > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > > > Evgeny Tantsura
> > > > Sent: Thursday, January 02, 2003 10:04 AM
> > > > To: ccielab@groupstudy.com
> > > > Subject: ISDN Backup With Dialer Watch
> > > >
> > > >
> > > > Hi,
> > > >
> > > > My ISDN interface with Dialer Watch on it
> > > > is going down every idle-timeout and then dialing again.
> > > >
> > > > interface Dialer1
> > > > ip address 1.1.1.2 255.255.255.0
> > > > encapsulation ppp
> > > > ip ospf demand-circuit
> > > > dialer pool 1
> > > > dialer idle-timeout 180
> > > > dialer string 0496406937
> > > > dialer load-threshold 127 either
> > > > dialer watch-group 1
> > > > dialer-group 1
> > > > pulse-time 0
> > > > no cdp enable
> > > > ppp authentication chap
> > > > ppp multilink
> > > > end
> > > >
> > > > access-list 170 deny ospf any any
> > > > access-list 170 permit ip any any
> > > > dialer watch-list 1 ip 192.168.5.1 255.255.255.255
> > > > dialer-list 1 protocol ip list 170
> > > > ----------------------------------------------------
> > > >
> > > > interface Dialer1
> > > > ip address 1.1.1.1 255.255.255.0
> > > > encapsulation ppp
> > > > dialer pool 1
> > > > dialer idle-timeout 180
> > > > dialer load-threshold 50 either
> > > > dialer-group 1
> > > > no cdp enable
> > > > ppp authentication chap
> > > >
> > > > dialer-list 1 protocol ip permit
> > > >
> > > >
> > > > According to CCO it should stay connected until the router gets the
> > > > route via primery interface.
> > > >
> > > > Any idea's ?
> > > >
> > > > With kind regards/ met vriendelijke groeten,
> > > > ------------------------------------------------
> > > > E. Tantsura
> > > > Network Developer
> > > > Essent Kabelcom N.V.
> > > > Dr.van Deenweg 84
> > > > 8025BN Zwolle, The Netherlands
> > > > Tel: +31-(0)38-850-7642
> > > > Fax: +31-(0)38-850-7410
> > > > Mob: +31-(0)6-290-80458
> > > > ------------------------------------------------
> > > > .
> > > > .
> > >With kind regards/ met vriendelijke groeten,
> > >------------------------------------------------
> > >E. Tantsura
> > >Network Developer
> > >Essent Kabelcom N.V.
> > >Dr.van Deenweg 84
> > >8025BN Zwolle, The Netherlands
> > >Tel: +31-(0)38-850-7642
> > >Fax: +31-(0)38-850-7410
> > >Mob: +31-(0)6-290-80458
> > >------------------------------------------------
> > >.
> > _________________________________________________________________
> > MSN 8: advanced junk mail protection and 2 months FREE*.
> > http://join.msn.com/?page=features/junkmail
> >
>
>With kind regards/ met vriendelijke groeten,
>------------------------------------------------
>E. Tantsura
>Network Developer
>Essent Kabelcom N.V.
>Dr.van Deenweg 84
>8025BN Zwolle, The Netherlands
>Tel: +31-(0)38-850-7642
>Fax: +31-(0)38-850-7410
>Mob: +31-(0)6-290-80458
>------------------------------------------------
>.
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:39 GMT-3