From: Larry Roberts (groupstudy@american-hero.com)
Date: Sat Jun 19 2004 - 02:29:37 GMT-3
Working configurations with my notes attached. Anyone who sees an error in
my explanation PLEASE correct me. I'm still trying to master the fine
details of ISDN and callback configurations.
R1 is the callback server
R3 is the callback client
On R1 I have defined a username R3
On R3 I have defined a username R1
R1:
interface BRI0/0
ip address 167.1.45.4 255.255.255.0
encapsulation ppp
dialer callback-secure
! If the other side doesn't request a callback, or doesn't complete LCP
negotiations for callback, drop the call.
dialer idle-timeout 30
! If the link is idle (as per the dialer-list definition) for 30 seconds,
drop it.
dialer enable-timeout 10
! This command tells the interface that after 10 seconds it is available for
use again
dialer map ip 167.1.45.5 name R3 class callback broadcast 230800
! My class callback is set for username.
dialer-group 1
! This defines witch dialer-list to use. In my case dialer-list 1 has a
permit ip any any
isdn switch-type basic-net3
ppp callback accept
! Ppp callback permit allows a callback to be returned. I believe that this
would go on the client to permit a callback.
! I have never used the callback permit...
ppp authentication chap callin
! Authenticate the callback client on the incoming call ONLY
! This is most often used in a AAA scenario, where the client wouldn't have
access to the TACACS server.
ppp chap hostname R1
! In my case the hsotname isn't needed since I set my routers hostname to
R1.
! I have included it just to try and match your configuration as best as
possible
R3:
ip address 167.1.45.5 255.255.255.0
encapsulation ppp
dialer idle-timeout 30
! Same use as above.
dialer map ip 167.1.45.4 name R1 broadcast 237388
dialer-group 1
isdn switch-type basic-net3
no cdp enable
ppp callback request
! Request a callback during LCP negotiations.
ppp authentication chap
On R3. Notice that the call is "IN". I can provide debugs if you wish.
R3#ping 167.1.45.4 rep 10
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 167.1.45.4, timeout is 2 seconds:
......!!!!
Success rate is 40 percent (4/10), round-trip min/avg/max = 32/32/33 ms
R3#sho isdn active
----------------------------------------------------------------------------
---
ISDN ACTIVE CALLS
----------------------------------------------------------------------------
---
Call Calling Called Remote Seconds Seconds Seconds Charges
Type Number Number Name Used Left Idle
Units/Currenc
----------------------------------------------------------------------------
---
In 237388 230800 R1 5 26 3
----------------------------------------------------------------------------
---
R3#
Hope this helps. I know that I learned a little more about ISDN today since
I had never worked with NET3.
Larry
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Larry Roberts
Sent: Friday, June 18, 2004 8:49 AM
To: 'Sharma, Mohit'
Cc: 'studygroup'
Subject: RE: ISDN timers clash
Couple of things I see or would recommend trying.
1) I believe your ppp authentication chap callin should be on the server. (
at least with TACACS it should be )
2) remove the ip router isis and the clns dialer map. ( its extra
configurations..lets simplify)
3) on the server add "dialer enable-timeout 10" ( Im not on a router so
verify the format)
4) set both routers to have the same dialer idle-timeout.
Here are the values I typically use
dialer idle-timeout 30
dialer enable-timeout 10 ( on server only )
dialer hold-queue 20
I would strip down your configuration of anything unneccessary, and add it
back later.
I will be in a position to test in my lab this afternoon, so I will play
around with your configuration as well.
-----Original Message-----
From: Sharma, Mohit [mailto:mohit.sharma@hp.com]
Sent: Friday, June 18, 2004 4:02 AM
To: Larry Roberts
Cc: studygroup
Subject: RE: ISDN timers clash
Hi Larry,
Here are the configs,
I am not using any simulator, but real ISDN lines :)
Rack1R4#sh run int bri 0
Building configuration...
Current configuration : 469 bytes
!
interface BRI0
ip address 167.1.45.4 255.255.255.0
ip router isis
encapsulation ppp
dialer callback-secure
dialer idle-timeout 60
dialer map ip 167.1.45.5 name Rack1R5 class callback broadcast 230800
dialer map clns 49.3490.0001.0001.0005.00 name Rack1R5 class callback
broadcast 230800 dialer-group 1 isdn switch-type basic-net3 no peer
neighbor-route ppp callback permit ppp authentication chap ppp chap
hostname ROUTER4 end
-------------
Rack1R5#sh run int bri 0
Building configuration...
Current configuration : 370 bytes
!
interface BRI0
ip address 167.1.45.5 255.255.255.0
ip router isis
encapsulation ppp
dialer idle-timeout 0
dialer map ip 167.1.45.4 name ROUTER4 broadcast 237388 dialer map clns
49.3490.0001.0001.0004.00 name ROUTER4 broadcast 237388 dialer-group 1 isdn
switch-type basic-net3 no peer neighbor-route ppp callback request ppp
authentication chap callin end
Rack1R5#
---------------
The dialer-list is configured to permit icmp so, a ping can bring up the
line.
I have played around with enable time-out on R4 and wait-for-carrier time in
R5 but in vain.
Thanks,
Mohit.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Larry Roberts
Sent: Friday, June 18, 2004 1:36 AM
To: Sharma, Mohit
Cc: studygroup
Subject: RE: ISDN timers clash
Can you post your ISDN configurations.
What ISDN sim are you using?
I had something similar with mine going on. I was doing TACACS callback, and
chap authentication via dialer interfaces. when I didn't do chap
authentication under the BRI interface as well as the dialer interfaces I
was getting this behavior.
I was also running into a problem with the simulator that upgrading the code
on fixed ( for the record it wasn't a simulator problem, but they adjusted
thier code to fix the problem on the routers.)
On Thu, 2004-06-17 at 12:16, Sharma, Mohit wrote:
> Hi All,
>
> Replying to my own mail.
> I really cant get this thing cleared up.
> The ppp callback is not working as intended- R5 calls R4, and R4 is
> only able to call R5 on channel2. as channel 1 is still busy freeing
> callback.
> ack1R5#sh isdn act
>
> ISDN ACTIVE CALLS
> ----------------------------------------------------------------------
> --
> --------
> Call Calling Called Remote Seconds Seconds Seconds
> Charges
> Type Number Number Name Used Left Idle
> Units/Currency
> ----------------------------------------------------------------------
> --
> --------
> Out 237340 35 24 35
0
>
> In ---N/A--- 230897 ROUTER4 27 32 27
>
> ----------------------------------------------------------------------
> --
> -
>
> On R4 is configured as a callback server and here is what I get on R4
> with debugs- Rack1R4#
> 00:30:06: BR0:1 PPP: Using dialer call direction
> 00:30:06: BR0:1 PPP: Treating connection as a callin
> 00:30:07: BR0:1 CHAP: Using alternate hostname ROUTER4
> 00:30:07: BR0:1 CHAP: O CHALLENGE id 7 len 28 from "ROUTER4"
> 00:30:07: BR0:1 CHAP: I RESPONSE id 7 len 28 from "Rack1R5"
> 00:30:07: BR0:1 CHAP: O SUCCESS id 7 len 4
> 00:30:07: BR0:1 DDR: callback to Rack1R5 already started
> 0:30:13: DDR: Callback timer expired
> 00:30:13: BR0 DDR: beginning callback to Rack1R5 230897
> 00:30:13: BR0 DDR: Attempting to dial 230897 Rack1R4#
> 00:30:15: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
> Rack1R4#
> 00:30:15: DDR: Freeing callback to Rack1R5 230897
> 00:30:15: BR0:2 PPP: Using dialer call direction
> 00:30:15: BR0:2 PPP: Treating connection as a callout
> 00:30:15: BR0:2 CHAP: Using alternate hostname ROUTER4
> 00:30:15: BR0:2 CHAP: O CHALLENGE id 3 len 28 from "ROUTER4"
> 00:30:15: BR0:2 CHAP: I CHALLENGE id 3 len 28 from "Rack1R5"
> 00:30:15: BR0:2 CHAP: Using alternate hostname ROUTER4
> 00:30:15: BR0:2 CHAP: O RESPONSE id 3 len 28 from "ROUTER4"
> 00:30:15: BR0:2 CHAP: I SUCCESS id 3 len 4
> 00:30:15: BR0:2 CHAP: I RESPONSE id 3 len 28 from "Rack1R5"
> 00:30:15: BR0:2 CHAP: O SUCCESS id 3 len 4
> 00:30:15: BR0:2 DDR: dialer protocol up
> ----------------------------------------------------------------------
> --
> ------
> According to the doc cd-
> """Router(config-if)# dialer enable-timeout seconds
> Configures the time to wait before initiating callback. ""
> SO I tried to set dialer wait-for-carrier-time 60 on R5 And dialer
> enable-timeout 120 on R4. But then the call from R5 on channel 1 lasts
> for 60 seconds and R4 still calls R5 on channel2.
> Can somebody please suggest what timers I should use on R4 and R5
> (the
> client) so that R4 WAITS before giving a callback to R5.
> PLEASE HELP.
> Many Thanks,
> Mohit.
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Sharma, Mohit
> Sent: Wednesday, June 16, 2004 10:08 PM
> To: studygroup
> Subject: ISDN timers clash
>
> Hello All,
>
> I have seen in the labs that whenever I configure callback (ppp or
> dialer), the callback router always has a clash when calling back. The
> result is that the first channel is always trying to connect and the
> connection is always established on the second channel.
>
> Anybody can give a hint on whats going on??
>
> I think I have to play around with dialer enable timeout and some
> other values??
>
> But on the calling side or the caller??
>
> Thanks,
>
> Mohit.
>
> ______________________________________________________________________
> _ Please help support GroupStudy by purchasing your study materials
> from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________________
> _ Please help support GroupStudy by purchasing your study materials
> from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:44 GMT-3