From: Montiean (noktes@bellsouth.net)
Date: Sat Jun 25 2005 - 18:40:09 GMT-3
Before answer the question 1,2. Just take a look on this concept first.
Dialer rotary-group - allows you to apply a logical interface to multiple
physical interfaces, once you put this command under physical interface
then it will creat dialer interface profile. This command usually use in
legacy DDR with multiple interfaces.
Now see, two commands below that uses together
dialer pool number - Specify the dialing pool to use for calls to this
destination, this one will use under logical interface like dialer profile
dialer pool-member number - assigned interface to be a member of the dialing
pool that the dialer interface will use.
Then looking at sentence below, I got from cisco page
dialer in-band - Enable DDR on an asynchronous interface or a synchronous
serial interface using V.25bis modems
This step is not required for ISDN interfaces (BRI interfaces and ISDN PRI D
channels) and for purely passive interfaces that will receive calls only
from interfaces that use DTR dialing.
Answer question 1
===============
I think because the question in the lab might trick us by not using dialer
string under dialer profile, so we use legacy ddr as a solution. In the real
world, we are probably seeing it using this with multiple interfaces such as
pri group and tied to a dialer profile. For exaple see
http://www.cisco.com/warp/public/793/access_dial/multilink.html
Answer question 2
===============
dialer in-band, per above. once you use rotary-group so you will need this
under logical interface. But if you use pool-member under physical
interface, so we will need to use dialer pool x. Does it make sense? See an
error that might get.
r4(config-if)#dialer map ip 10.120.120.1 name r1 broadcast 5551000
%Configure a "dialer in-band", or "dialer pool" first.
Answer question 3
===============
Look at configuration below, I have removed "dialer-group 1" out from under
bri0/0.This command is automatically enable under physical interface that
using rotary-group while we have added under dialer interface. The purpose
of it have to be the same to monitor the interesting traffic.
r4#
Current configuration : 110 bytes
!
interface BRI0/0
no ip address
encapsulation ppp
dialer rotary-group 1
isdn switch-type basic-net3
!
interface Dialer1
ip address 10.120.120.4 255.255.255.0
ip broadcast-address 10.120.120.255
encapsulation ppp
dialer in-band
dialer idle-timeout 0
dialer map ip 10.120.120.1 name r1 broadcast 5551000
dialer-group 1
end
r1#
!
interface BRI0/0
no ip address
encapsulation ppp
dialer rotary-group 1
isdn switch-type basic-net3
interface Dialer1
ip address 10.120.120.1 255.255.255.0
encapsulation ppp
dialer in-band
dialer idle-timeout 0
dialer map ip 10.120.120.4 name r4 broadcast 5552000
dialer-group 1
end
r1# and r4#
BRI0/0 unassigned YES TFTP up
up
BRI0/0:1 unassigned YES unset up
up
BRI0/0:2 unassigned YES unset down
down
I also found other solution for NAS in the real world that using group-async
with group range to tied to line interface. Hopefully,we will discuss more
about this.
--Montiean
----- Original Message -----
From: "ccie2be" <ccie2be@nyc.rr.com>
To: "Group Study" <ccielab@groupstudy.com>
Sent: Saturday, June 25, 2005 6:36 AM
Subject: Dialer profiles without dialer strings
> Hi guys,
>
> Aside from not losing points on the lab, what are the "real world" reasons
> one would use this config technique.
>
>
> interface BRI0/0
> no ip address
> encapsulation ppp
> dialer rotary-group 0 <-- the 0 refers to int dialer 0 below
> dialer-group 1
> isdn switch-type basic-ni
> isdn spid1 5272014
> !
> interface Dialer0
> ip address 157.1.45.4 255.255.255.0
> encapsulation ppp
> dialer in-band <-- must have this instead of dialer pools
> dialer map ip 157.1.45.5 broadcast 5272015
> dialer-group 1
>
>
> Also, notice that dialer-group 1 is configured on both the phy and the
> dialer int. Why is that ?
>
> TIA, Tim
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:44 GMT-3