From: Chris Lewis (chrlewiscsco@yahoo.com)
Date: Sat Nov 12 2005 - 11:43:38 GMT-3
to make all traffic uninteresting has ben recommended as a best practice for when dialer watch is in use, to be 100% certain that the missing route is the only thing that triggers a dial.
Gorito's lab book goes through this in one of his examples.
Chris
"Schulz, Dave" <DSchulz@dpsciences.com> wrote:
John -
I have never heard of your last statement.....by make all traffic
uninteresting. Weren't we just trying to keep one side from dialing, which
should be taken care of with removing the dialer string/map statements?
Dave
-----Original Message-----
From: nobody@groupstudy.com
To: Montiean
Cc: ccielab@groupstudy.com; nobody@groupstudy.com
Sent: 11/11/2005 6:56 PM
Subject: Re: dialer-group under BRI interface
monty,
in IE's manual they state that you can prevent a router from dialing by
leaving off the dialer string at the end of the dialer-map statement.
however, whenever i did this i was not able to ping from on side to the
other.....i could only get layer 2 to come up if there was the
dialer-string on both sides. t
the easiest way to prevent a router from dialing isdn is to make all
traffic uninteresting by not defining a dialer-group. very simple, very
effective.
Regards,
John D. Matus
Technical Support / PAS
Fujitsu Consulting
626-568-7716
John.Matus@tokiom.com
"Montiean"
.net>
To
Sent by:
nobody@groupstudy
cc
.com
Subject
dialer-group under BRI interface
11/11/2005 09:49
AM
Please respond to
"Montiean"
.net>
Folks,
Let say the question asking only one side to initiate the call so on
other site will just configure "dialer map" without remote isdn calling
number. This would be enough not to let the router call out.
However, in some solution guide from lab workbook use additional
command
like " dialer-group" on the side that doesnot need to initiate the call.
As
I know, dialer-group will use to screen the traffic to initiate the
call. I
am not sure why we still need it as above scenario.
Any ideas?
Thanks,
Montiean
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3