From: Chuck South (cciesouth@bellsouth.net)
Date: Sat Jul 31 2004 - 13:33:10 GMT-3
Thanks for the info!
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
john matijevic
Sent: Saturday, July 31, 2004 10:11 AM
To: 'Chuck South'; 'mani poopal'; ccielab@groupstudy.com
Subject: RE: Re: ISDN callback/dialer load-threshold.
Hello Team,
I think I maybe able to answer your first two questions with a good
reference:
Solie's book practical studies version 1 gives a good example.
Chuck you also have the configuration listed below. In order to see this
please try using the debug dialer on the client, than do the ping, you
should see a Callback negotiated - waiting for server disconnect, than
you should see the callback client create, than disconnecting call, than
callback received from the server, in the debug output, also you can
verify with the show dialer, when you use the show dialer command you
look at the dial reason and it should say Callback return call, you use
this command on the callback server.
Here is the ouput of the client:
r1#deb dialer
Dial on demand events debugging is on
r1#ping 172.16.12.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.12.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
r1#
1w4d: BR0 DDR: Dialing cause ip (s=172.16.12.1, d=172.16.12.2)
1w4d: BR0 DDR: Attempting to dial 5552002
1w4d: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
1w4d: BR0:1 DDR: Callback negotiated - waiting for server disconnect
1w4d: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
1w4d: DDR: Callback client for r2 5552002 created
1w4d: BR0:1 DDR: disconnecting call
r1#
1w4d: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
r1#
1w4d: BR0:1 DDR: dialer protocol up
1w4d: BR0:1 DDR: Callback received from r2 5552002
1w4d: DDR: Freeing callback to r2 5552002
r1#
1w4d: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed s
p
Here is the output on the server:
r2#sh dialer
BRI0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
5552001 2 0 00:00:01 successful
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0:1 - dialer type = ISDN
Idle timer (40 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: Callback return call
Time until disconnect 38 secs
Connected to 5552001 (r1)
BRI0:2 - dialer type = ISDN
Idle timer (40 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle
r2#
AS you can se from the debug and the show command you should be able to
see how this process works again, this is documented in Solie's book
page 484-487.
AS far as the load-threshold question.
Lets look at Solie's example he has dialer load-threshold 25 either
Here both B channels should be used after the first B channel has
exceeded the threshold of 10 percent in either outbound or inbound
traffic. Because 25 is 10% of 255. This is reference in Solie's
practical studies vol1 page 489. Also you can see the load by doing a sh
int bri 0 1 and look for the load in the show command. Also to create
additional traffic you can do the following:
r1#p
Protocol [ip]:
Target IP address: 172.16.12.2
Repeat count [5]: 100
Datagram size [100]: 1500
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 1500-byte ICMP Echos to 172.16.12.2, timeout is
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!.
Success rate is 98 percent (97/98), round-trip min/avg/max =
r1#
1w4d: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
1w4d: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to
1w4d: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:2
p
r1#sh int bri 0 1
BRI0:1 is up, line protocol is up
Hardware is BRI
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 31/255, rxload 31/255 <------ this is
you can see is over the 10%
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
Time to interface disconnect: idle 00:01:52
LCP Open, multilink Closed
Open: IPCP, CDPCP
Last input 00:00:07, output 00:00:06, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 8000 bits/sec, 1 packets/sec
5 minute output rate 8000 bits/sec, 1 packets/sec
566 packets input, 501195 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0
580 packets output, 503510 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 output buffer failures, 0 output buffers swapped out
49 carrier transitions
r1#sh dialer
BRI0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last st
5552002 13 0 00:00:13 succ
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0:1 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=172.16.12.1, d=172.16.12.2)
Time until disconnect 107 secs
Connected to 5552002 (r2)
BRI0:2 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: Dialing on overload <------------- Here
you can see why the second channel comes up
Time until disconnect 110 secs
Connected to 5552002 (r2)
I hope that helps clarify.
John Matijevic, CCIE #13254, MCSE, CNE, CCEA
Network Consultant
Hablo Espanol
305-321-6232
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Chuck South
Sent: Saturday, July 31, 2004 1:09 AM
To: mani poopal; ccielab@groupstudy.com
Subject: Re: Re: ISDN callback/dialer load-threshold.
Hey Mani,
I spent some time on your first item A - this was a good exercise for
me...
R2---------ISDN----------R3
R2 configured as callback client, R3 as callback server...
R2********************************************
!
interface BRI0
ip address 172.16.230.2 255.255.255.0
encapsulation ppp
dialer map ip 172.16.230.3 name Termine_R3 broadcast 8358662
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866101
isdn spid2 0835866301
ppp callback request
ppp authentication chap
!
R3********************************************
!
interface BRI1/0
ip address 172.16.230.3 255.255.255.0
encapsulation ppp
dialer map ip 172.16.230.2 name Termine_R2 class CHEAPER broadcast
8358661
isdn switch-type basic-ni
isdn spid1 0835866201
isdn spid2 0835866401
ppp callback accept
ppp authentication chap
!
map-class dialer CHEAPER
dialer callback-server username
!
Ping from R2...watching R3...
Termine_R3#
01:04:01: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to up
01:04:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1,
changed state to up
01:04:02: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to
8358661 Termine_R2
01:04:02: %ISDN-6-DISCONNECT: Interface BRI1/0:1 disconnected from
8358661 Termine_R2,
call lasted 1 seconds
Termine_R3#
01:04:13726923028: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to
down
01:04:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1,
changed state to
down
Termine_R3#
01:04:73076319848: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to
up
Termine_R3#
01:04:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1,
changed state to up
Termine_R3#
01:04:23: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to
8358661 Termine_R2
Termine_R3
Termine_R3#sh isdn active
------------------------------------------------------------------------
--------
ISDN ACTIVE CALLS
------------------------------------------------------------------------
--------
Call Calling Called Remote Seconds Seconds Seconds
Charges
Type Number Number Name Used Left Idle
Units/Currency
------------------------------------------------------------------------
--------
Out ---N/A--- 8358661 Termine_R2 13 106 13 0
------------------------------------------------------------------------
--------
Termine_R3#
Removed the "class CHEAPER" from R3s dialer map and pinged again from R2
again...
Termine_R3#
01:15:49: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to up
Termine_R3#
01:15:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1,
changed state to up
Termine_R3#
01:15:55: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to
8358661 Termine_R2
Termine_R3#
Termine_R3#show isdn active
------------------------------------------------------------------------
--------
ISDN ACTIVE CALLS
------------------------------------------------------------------------
--------
Call Calling Called Remote Seconds Seconds Seconds
Charges
Type Number Number Name Used Left Idle
Units/Currency
------------------------------------------------------------------------
--------
In 8358661 8358662 Termine_R2 33 86 33
------------------------------------------------------------------------
--------
Termine_R3#
Did not DISCONNECT and call R2 back...
So it appears the "class" component of the dialer map is required. I
couldn't find a good debug command to detail ppp callback. Anyone have
any ideas on this?
>
> From: mani poopal <mani_ccie@yahoo.com>
> Date: 2004/07/30 Fri PM 09:58:37 EDT
> To: ccielab@groupstudy.com
> Subject: Re: ISDN callback/dialer load-threshold.
>
> Hi john matijevic/Gladstone/others,
>
> Thanks for giving URL info for my previous ATM/DLSW question. I did
not get any reply for my previous post. I am pasting my previous post
again. Guys keep up the good work.
>
> Mani
>
> ==========================================================
> My previous post:
> Dear group:
>
> (A.) In legay DDR when you enable callback(on client router: ppp
callback request & on server router: ppp callback accept) you have to
enable above commands. Do we need map-calss dialer XYZ command and
appropriate map class(dialer map ip x.x.x.x class XYZ name R1 broadcast)
or is optional.
>
> (B.)What is the equivalent commands(ppp callback accept, ppp callback
request) for Dialer profiles(Non legacy DDR), any config examples are
greatly appriciated.
>
> (C.)In dialer load-threshod 128 command when will the second B channel
is activated(Is it at 50% load on B1[64kbps] or 50% load on combined B
channels[128kbps]. When above command is given when will the second
channel decativated(Is it when load falls below 50% of primary or 50% of
combined.
>
> I really enjoy the study group and contents
>
> Mani
>
>
> B.ENG,A+,CCNA,CCNP,CCNP-VOICE, CSS1,CNA,MCSE
> (416)431 9929
> MANI_CCIE@YAHOO.COM
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
>
>
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:12:08 GMT-3