From: aansar@sscomp.com.sg
Date: Thu Oct 17 2002 - 05:44:55 GMT-3
i tried karl solie page no 508 , with dialer watch ..
i am stuck with this dialer watch ..
if you see the configuration in the page 508, the remote router implement
the dialer watch to watch the HO ethernet and loopback.
the objective is if the serial interface connecting BR and HO goes down .
BRI should kick in .
ok all the configuration is done ,when i shut down the serial interface ,
BRI doesnt kicks in ..
i think the problem is with the access-list in the BR router which is link
to the dialer list to block eigrp traffic and allow all other ip traffic.
so when the serial interface goes down , the dialer-list doesnt see EIGRP
traffic as interesting and doesnt initiate the EIGRP hand shake..
if i remove the access-list , things works fine .. but EIGRP keeps the line
always up .. what to do now..
i am lost .. i am using IOS 12.1(5)T9, Is this the problem.
"Bola
Adegbonmire" To: "Frank Maisano" <FrankM@netarch.com>, "Azhar Mehmood "
<BolaAD@Resource <azhar.mehmood@web.de>
ry.com.ng> cc: <ccielab@groupstudy.com>
Sent by: Subject: RE: RE: Dialer watch
nobody@groupstud
y.com
17-10-02 02:17
PM
Please respond
to "Bola
Adegbonmire"
Would you be willing to post configs. Sounds funny this happens. I actually
even did it in a case over two ethernet links (all I did in this case too
was to change the BW of my sec ethernet interface to 9000. I run EIGRP
simultaneously over both E links, can see the neighbour across both links
with "sh eigrp nei xxx", except the route installed in table is e1 and once
e1 is down, e2 is installed in table without dialer watch ever kicking my
PSTN link to dial). Are you also sure that the paticular network been
watched is in the database from pri as well as sec links even while pri is
up?
ethernet1 - primary (BW 10000)
ethernet2 - secondary (BW 9000)
Async Serial - dialer watch interface (BW 64)
the client did not want to load balance over the ethernet links because the
secondary is a DSL link, less reliable and less bandwidth available in
comparison to the primary.
It worked fine over all situations with the configs I described.
By the way just a thought what IOS and platfrom are you using? Just
wondering beacause CCO states that IOS earlier than 12.1(7) introduce
instabilities with dialer watch operations, the nature of which is not
stated. This a long shot though.
-----Original Message-----
From: Frank Maisano [mailto:FrankM@netarch.com]
Sent: Wednesday, October 16, 2002 7:04 PM
To: 'Azhar Mehmood '; Bola Adegbonmire
Cc: 'ccielab@groupstudy.com '
Subject: RE: RE: Dialer watch
Tweak eigrp metrics to make both ethernet and serial lines equal cost paths
in the mind of eigrp. then both paths should load into the routing table
since eigrp will do equal cost load balancing. If one of the paths fail,
the second will remain in the routing table and keep the route up and thus
keep the isdn from dialing.
-----Original Message-----
From: Azhar Mehmood
To: Bola Adegbonmire
Cc: ccielab@groupstudy.com
Sent: 10/16/2002 11:32 AM
Subject: Re: RE: Dialer watch
hi,
the config is as you described bellow, despite having e0 as primary,
serial as secondry and ISDN as last option dialer-watch triggers ISDN
call right after e0 is anavailable. Although ISDN link is down again
after idle-timeout has expired because serial interface is prefered as
second option and also routes are installed in routing table. My
question was how to prevent dialer-watch to trigger ISDN call right
after E0 is down and serial is available as second option. By the way
I'm using EIGRP and Serial is a permanent link with HDLC enc.
regards
AZHAR M.
Germany
"Bola Adegbonmire" <BolaAD@Resourcery.com.ng> schrieb am 16.10.02
13:38:22:
> Hi,
> I did something like this a recently and used Dialer watch. Though my
DDR link is over an asychromous modem via PSTN. First I will like to
know if your Serial interface is a permanent connection. for example is
it a frame-relay PVC? If you had something like this
>
> Ethernet
> Serial - frame-relay PVC
> ISDN
>
> 1 make sure that the network been watched "xxxx" by dailer watch is
also sent by your dynamic routing protocol (Eigrp/Igrp/OSPF) over the
serial link.
>
> 2 make sure your Serial interface is made less desirable than your
ethernet(default interface bandwidth makes sure though), use bandwidth
command
>
> 3 make sure ISDN interface is least desirable of all three (use
bandwidth command here too)
>
> Scenario is close to this
>
> int e0
> bandwidth 10000
> !
> int s0
> bandwidth 256
> !
> int bri0
> bandwidth 64
>
> and you were running your dynamic protocol on all interfaces, you will
have network xxxx in topology table(EIGRP) but route through e0
installed in routing table. When e0 no longer receives hello packets,
route through serial is installed and finally if PVC goes down then
there is no interface in routing table referencing xxxx dialer watch
noiw kicks the ISDN link to dial.
>
>
> -----Original Message-----
> From: Ashok.Gupta [mailto:Ashok.Gupta@gmconsultants.com]
> Sent: Tuesday, October 15, 2002 7:44 PM
> To: 'Azhar Mehmood'; ccielab@groupstudy.com
> Subject: RE: Dialer watch
>
>
> floating static
>
> Regds
>
> Ashok
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Azhar Mehmood
> Sent: 15 October 2002 17:09
> To: ccielab@groupstudy.com
> Subject: Dialer watch
>
>
> Hi,
>
> I have a router R1 ehich has 3 exit points to reach a specific subnet:
>
> 1. Ethernet
> 2. Serial
> 3. ISDN
>
> 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.
>
> 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 call hence it brings it
also down
> again after idle-timeout.
>
> My question is how to configure the router that it waits until both of
the
> link 're unavailable and triggering than an isdn call.
>
>
> regards
>
> AZHAR MEHMOOD
> GERMANY
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:49 GMT-3