From: Joe Soricelli (jsoricelli@xxxxxxxx)
Date: Fri Oct 01 1999 - 21:06:30 GMT-3
Think of it this way.
A dialer profile can be used on multiple interfaces. There is no way for
the interface Dialer1 (or whatever) to know which interface it is going to
get assigned to. So, the dialer in-band command must be placed on a dialer
profile when using legacy DDR because it could get used on an asynch seial
interface.
-joe
------------------------------------------------------------------
Joseph M. Soricelli, CCIE #4803, CCNP, CCSI #20666
EMAIL: jsoricelli@ccci.com
Chesapeake Network Solutions
8110 Gatehouse Road, Suite 101E Phone: (703) 207-0757
Falls Church, VA 22042 Fax: (703) 207-0441
FYI - About Chesapeake: We are a Cisco Certified Training and
professional services partner. We offer most of the Cisco
training courses as well as training for Fore, NetScout, and
CheckPoint-1 Firewalls. We provide network consulting services,
including design, network health, management, firewall,
and problem solving. We now have 23 CCIEs on our staff
of instructor/consultants.
-------------------------------------------------------------------
-----Original Message-----
From: Mark Olson <molson@uswest.com>
To: ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Wednesday, September 29, 1999 2:58 PM
Subject: Re: More Dialer stuff
>I was under the impression that the dialer in-band command, when
>specified on an interface, would enable call setup and call teardown
>functionality on an interface (I seem to remember a mention of the ITU-T
>V.25bis standard somewhere). As you have seen, you can't configure
>a dialer map command (using the legacy DDR method) without first
>configuring dialer in-band. And if you don't have a dialer map command
>(using the legacy DDR method), you can't originate a call (or tear down
>a call originated by the other end since the idle-timeout is ignored).
>
>As Vaughan mentioned, the dialer in-band command isn't necessary on a
>physical ISDN BRI since it uses q931. However, when you move to
>a dialer interface, even though you're dealing with a BRI (or multiple
>BRI's), you need to config the dialer in-band command again (if your
>using the legacy DDR method). Hmmm, that's interesting....what does
>q931 have to do with V.25bis?? Guess, it must be a little more generic
>and maybe safer saying it enables call setup and call teardown
functionality
>on an interface.
>
>I could be totally off my rocker but that's just some of my observations
>obtained by playing around with asynch dialin/dialout and ISDN!
>
>Good luck to all!
>
>mark
>
>
>Vaughan Lee wrote:
>
>> I did once manage to get snapshot routing working using a dialer
interface
>> using dialer maps and dialer in-band, but only in conjunction with a
rotary
>> group, which can probably be regarded as cheating! I have the config
>> available still if anyone is desperate enough to want it, though it
should
>> be fairly easy to work out if you start by configuring for rotary groups.
>>
>> My understanding of the dialer in-band command is that it specifies if
the
>> connection is to be established over the link that will be used to carry
>> data e.g. you are instructing the modem or whatever via the data channel
to
>> establish a call. In the case of an analogue line this is the case, but
>> with ISDN there is a separate channel (the D channel) that is used to
>> establish the connection, the data being carried over the B channel, so
>> dialer in-band is not required.
>>
>> Hope that helps a bit.
>>
>> Regards,
>> Vaughan
>>
>> Vaughan Lee, Network Specialist.
>> debis IT Services (UK) Ltd.
>> E-mail: vaughan.lee@debis.co.uk
>> Direct Phone: 01908 279561
>> Direct Fax: 01908 279061
>> http://www.debis.co.uk/
>>
>> -----Original Message-----
>> From: Chad Marsh [mailto:chad@wa.net]
>> Sent: 29 September 1999 09:28
>> To: CCIE Lab; Cisco
>> Subject: Re: More Dialer stuff
>>
>> Correction, after further study, it appears the mutually exclusive
>> commands on the dialer interface are 'dialer remote-name' and 'dialer
>> map'. If you set a remote name, you can no longer use 'dialer map'(which
>> is required for snapshot), you can only set a dialer string.
>> But, if you do specify a 'dialer remote-name' first, you cannot enter
>> 'dialer in-band', you get that error '%Remove the dialer profile first'
>> You can enter 'dialer in-band', then enter 'dialer remote-name', but at
>> that point you can't enter dialer maps, so I guess that doesn't do any
>> good anyway.
>>
>> So what exactly does 'dialer in-band' do anyway?
>> CCO says:
>> dialer in-band
>> To specify that dial-on-demand routing (DDR) is to be supported, use the
>> dialer in-band interface configuration command. To disable DDR for the
>> interface, use the no form of this command.
>>
>> But that doesn't make any sense, I can setup DDR with dialer profiles
>> using dialer pools, and without using 'dialer in-band' and it works just
>> fine.
>>
>> Chad Marsh
>>
>> >
>> > It appears that the 'dialer in-band' and 'dialer remote-name' commands
>> > are mutually exclusive on the Dialer interface.
>> > I have this working with rotary-groups, not sure if it would work with
>> > dialer pools, maybe I'll try that next.
>> > But the bottom line is that it DOES work.
>> > I just got it working, here are some relevant outputs and portions of
>> > the configs:
>> >
>> > Chad Marsh
>> >
>> > R5#sho snap
>> > Dialer1 is up, line protocol is upSnapshot client
>> > Options: dialer support
>> > Length of active period: 5 minutes
>> > Length of quiet period: 8 minutes
>> > Length of retry period: 8 minutes
>> > For dialer address 1
>> > Current state: active, remaining/exchange time: 4/2 minutes
>> > Connected dialer interface:
>> > BRI0:1
>> > Updates received this cycle: ip
>> >
>> > R6#sho snap
>> > Dialer1 is up, line protocol is upSnapshot server
>> > Options: dialer support
>> > Length of active period: 5 minutes
>> > For ip address: 172.16.1.5
>> > Current state: active, remaining time: 3 minutes
>> > Connected dialer interface:
>> > BRI0:1
>> >
>> > R5#sh ru
>> > Building configuration...
>> >
>> > Current configuration:
>> > !
>> > hostname R5
>> > !
>> > !
>> > username R6 password 0 ccie
>> > isdn switch-type basic-dms100
>> > !
>> > interface Loopback0
>> > ip address 10.5.1.1 255.255.255.0
>> > !
>> > interface BRI0
>> > no ip address
>> > encapsulation ppp
>> > isdn spid1 20649906240101 4990624
>> > isdn spid2 20649906250101 4990625
>> > dialer rotary-group 1
>> > no cdp enable
>> > !
>> > interface Dialer1
>> > ip address 172.16.1.5 255.255.255.0
>> > encapsulation ppp
>> > dialer in-band
>> > dialer in-band
>> > dialer map snapshot 1 4990622
>> > dialer map ip 172.16.1.6 name R6 broadcast 4990622
>> > dialer-group 1
>> > snapshot client 5 8 dialer
>> > no cdp enable
>> > ppp authentication chap
>> > !
>> > router rip
>> > network 10.0.0.0
>> > network 172.16.0.0
>> > !
>> > ip classless
>> > !
>> > dialer-list 1 protocol ip permit
>> > !
>> > R5#
>> >
>> > R6#sho run
>> > Building configuration...
>> >
>> > Current configuration:
>> > !
>> > hostname R6
>> > !
>> > !
>> > username R5 password 0 ccie
>> > isdn switch-type basic-dms100
>> > !
>> > interface Loopback0
>> > ip address 20.6.1.1 255.255.255.0
>> > !
>> > interface BRI0
>> > no ip address
>> > encapsulation ppp
>> > isdn spid1 20649906220101 4990622
>> > isdn spid2 20649906230101 4990623
>> > dialer rotary-group 1
>> > no cdp enable
>> > !
>> > interface Dialer1
>> > ip address 172.16.1.6 255.255.255.0
>> > encapsulation ppp
>> > dialer in-band
>> > dialer idle-timeout 30
>> > dialer map ip 172.16.1.5 name R5 broadcast 4990624
>> > dialer-group 1
>> > snapshot server 5 dialer
>> > no cdp enable
>> > ppp authentication chap
>> > !
>> > router rip
>> > network 10.0.0.0
>> > network 172.16.0.0
>> > !
>> > ip classless
>> > !
>> > dialer-list 1 protocol ip permit
>> > !
>> > R6#
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:52 GMT-3