From: Ahmed Mustafa (ahmed.mustafa@sbcglobal.net)
Date: Tue Feb 17 2004 - 03:10:50 GMT-3
Thanks Everyone,
Since I was using 2 SPID, I configured the second DN with the mapping
command, and with "PPP Multilink link minimum 2"
command both channels went up rightaway.
With Dialer-load thershold command, it is still inconsistent. As you can
see from the output that it took some time before 2nd bri channel became
active regardless I configured load-threshold 1 either.
Rack1R4#ping
Protocol [ip]:
Target IP address: 183.1.45.5
Repeat count [5]: 20
Datagram size [100]: 1500
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 20, 1500-byte ICMP Echos to 183.1.45.5, timeout is 2 seconds:
.!
00:52:31: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
00:52:31: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up!!
00:52:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed
state
to up
00:52:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2,
chang
ed state to up!!!!!!!!!!!
00:52:37: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 5552221
Rack1R5!
!!!!
Success rate is 95 percent (19/20), round-trip min/avg/max = 384/393/504 ms
Rack1R4#show diale
BRI0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
5552222 12 6 00:02:18 successful
5552221 12 26 00:00:13 successful
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0:1 - dialer type = ISDN
Idle timer (60 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Dial reason: ip (s=183.1.45.4, d=183.1.45.5)
Connected to 5552221 (Rack1R5)
BRI0:2 - dialer type = ISDN
Idle timer (60 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle
Rack1R4#
00:53:02: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
Rack1R4#
00:53:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:2, changed
state
to up
Rack1R4#show dialer
BRI0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
5552222 12 6 00:02:41 successful
5552221 12 26 00:00:05 successful
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0:1 - dialer type = ISDN
Idle timer (60 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Dial reason: ip (s=183.1.45.4, d=183.1.45.5)
Connected to 5552221 (Rack1R5)
BRI0:2 - dialer type = ISDN
Idle timer (60 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Connected to 5552221 (Rack1R5)
Rack1R4#
00:53:08: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to 5552221
Rack1R5
Rack1R4#show ppp mult
Rack1R4#show ppp multilink
Virtual-Access2, bundle name is Rack1R5
Bundle up for 00:00:44
Dialer interface is BRI0
0 lost fragments, 0 reordered, 0 unassigned
0 discarded, 0 lost received, 1/255 load
0x0 received sequence, 0x0 sent sequence
Member links: 2 (max not set, min not set)
BR0:1, since 00:00:44, no frags rcvd
BR0:2, since 00:00:13, no frags rcvd
Rack1R4#show dialer
BRI0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
5552222 12 6 00:02:56 successful
5552221 12 26 00:00:20 successful
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0:1 - dialer type = ISDN
Idle timer (60 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Dial reason: ip (s=183.1.45.4, d=183.1.45.5)
Connected to 5552221 (Rack1R5)
BRI0:2 - dialer type = ISDN
Idle timer (60 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Connected to 5552221 (Rack1R5)
Rack1R4#
00:53:40: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
00:53:40: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from 5552221
Rack1R
5, call lasted 68 seconds
00:53:40: %ISDN-6-DISCONNECT: Interface BRI0:2 disconnected from 5552222
Rack1R
5, call lasted 37 seconds
Rack1R4#
00:53:40: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
00:53:40: %LINK-3-UPDOWN: Interface BRI0:2, changed state to down
Rack1R4#
00:53:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed
state
to down
00:53:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:2, changed
state
to down
00:53:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2,
chang
ed state to down
Rack1R4#
----- Original Message -----
From: "Marko Berend" <marko.berend@storm.hr>
To: "Ahmed Mustafa" <ahmed.mustafa@sbcglobal.net>; <ccielab@groupstudy.com>
Sent: Monday, February 16, 2004 12:00 AM
Subject: RE: PPP with Multilink
Ahmed,
If you're using Adtran Atlas ISDN simulator, this will be of interest to
you.
http://www.adtran.com/adtranpx/Doc/0/075RA6EBVJB139RU038BE81ID8/When+I+dial+
into+my+ADTRAN+unit+from+the+PRI-BRI+interface+of+my+Cisco+router%2C+I+canno
t+make+an+MLPPP+connection.html
In short:
The Cisco router is dialing both numbers simultaneously. ADTRAN units do not
support simultaneous answering of calls. The Cisco router must be set to
dial the numbers one at a time. This can be done by adding the following
command to the Cisco router configuration:
isdn fast-rollover-delay 1
-----Original Message-----
From: Ahmed Mustafa [mailto:ahmed.mustafa@sbcglobal.net]
Sent: 16. veljaha 2004 8:37
To: kaiseranwar@sbcglobal.net; ccielab@groupstudy.com
Subject: Re: PPP with Multilink
Kaiser/Bill,
According to InterneworkExpert Workbook, Either the "Dialer Load-Threshold
or PPP multilink link-min 2" could achieve the desired results. I also
tried, "Load-Threshold command, but no luck.
----- Original Message -----
From: "Kaiser anwar" <kaiseranwar@sbcglobal.net>
To: "'Ahmed Mustafa'" <ahmed.mustafa@sbcglobal.net>;
<ccielab@groupstudy.com>
Sent: Sunday, February 15, 2004 11:09 PM
Subject: RE: PPP with Multilink
>
>
> You will need to use dialer load-threshold command to bring the second
> B channel up. I don't see that in your config.
>
> Thanks
> Kaiser
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Ahmed Mustafa
> Sent: Monday, February 16, 2004 12:56 AM
> To: ccielab@groupstudy.com
> Subject: PPP with Multilink
>
> I am not able to bring up both both B channels. When I generate a
> normal ping or extended ping with big datagram size, and still it will
> only bring one
> channel up, not both of them. Please see my config below, and let me
know
> if
> there are any errors. I am using Astricom ISDN Simulator, not a true
> ISDN Switch. Is is because of that.
>
> Thanks,
>
>
>
> R4
> ----------------------------------------------------
> interface BRI0
> ip address 183.1.45.4 255.255.255.248
> encapsulation ppp
> ip ospf demand-circuit
> dialer map ip 183.1.45.5 name Rack1R5 broadcast 552221 dialer-group
> 1 isdn switch-type basic-ni
> isdn spid1 30355511110101
> isdn spid2 30355511120101
> ppp authentication pap
> ppp pap sent-username Rack1R4 password 0 CISCO
> ppp multilink
> ppp multilink links-min 2
> --------------------------------------------------------------------------
-- > - > ------ > > R5 > ---------------------------------------------------------------------- > ---- -- > - > ----- > > interface BRI0 > ip address 183.1.45.5 255.255.255.248 > encapsulation ppp > ip ospf demand-circuit > dialer idle-timeout 180 either > dialer map ip 183.1.45.4 name Rack1R4 broadcast 5551111 dialer-group > 1 isdn switch-type basic-ni > isdn spid1 30355522220101 > isdn spid2 30355522210101 > ppp authentication pap > ppp pap sent-username Rack1R5 password 0 CISCO > ppp multilink > multilink min-links 2 > > ______________________________________________________________________ > _ > 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 : Fri Mar 05 2004 - 07:13:50 GMT-3