Re: ISDN Multilink PPP

From: Ron Trunk (rtrunk@xxxxxxxxxxxxx)
Date: Mon Jul 12 1999 - 11:21:50 GMT-3


   
   Ben,
   
   Here is a quote from the command reference:
   
   The dialer load-threshold command is used to enable a rotary group to
   bring up additional links and to add them to a multilink bundle.
   
   When multilink PPP is configured, dialer-load threshold 1 command no
   longer keeps a multilink bundle of n links connected indefinitely and
   the dialer-load threshold 2 command no longer keeps a multilink bundle
   of 2 links connected indefinitely. If you want a multilink bundle to
   be connected indefinitely, you must set a very high idle timer.
   
Example

   The following partial example configures a dialer for Multilink PPP;
   it does not show the configuration of the physical interfaces.
interface Dialer0
 ip address 99.0.0.2 255.0.0.0
 encapsulation ppp
 dialer in-band
 dialer idle-timeout 500
 dialer map ip 99.0.0.1 name atlanta broadcast 81012345678901
 dialer load-threshold 30 either
 dialer-group 1
 ppp authentication chap
 ppp multilink

Ron
6 days ...

   -----Original Message-----
   From: Ben Rife <brife@bignet.net>
   To: ccielab@groupstudy.com <ccielab@groupstudy.com>
   Date: Sunday, July 11, 1999 3:23 PM
   Subject: ISDN Multilink PPP
   
   Hi Guys, I'm 2 days away.....
   
   
   
       I have an issue I can't get past with Multilink PPP.
   
   
   
   I am using a dialer profile on both routers. Their configs are
   identical as follows:
   
   
   
   interface BRI0
    no ip address
    isdn spid1 0835866101 8358661
    isdn spid2 0835866301 8358663
    dialer pool-member 1
   !
   interface Dialer0
    ip address 192.168.2.1 255.255.255.0
    encapsulation ppp
    dialer remote-name r2504
    dialer string 8358662
    dialer load-threshold 1 either
    dialer pool 1
    dialer-group 1
    ppp multilink
   
   
   
   Interesting traffic will bring the first channel up, then one side or
   the other will bring the other channel up. The problem is that my
   idle-timeouts never match. They don't match with each other or with
   the remote side. So what happens is that one channel will reach
   idle-timeout (120 sec) and drop the connection. Then immediately the
   other side will bring it back up again. It's got me perplexed. I can
   be sending pings across the line and the idle time-out on one of the
   channels is updated but not both. And then the other channel will go
   down and up...etc.
   
   
   
   Here is a sh dialer snippet to show my point.
   
   
   
   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
   Interface bound to profile Dialer0
   Time until disconnect 52 secs
   Connected to 8358662
   
   
   
   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
   Interface bound to profile Dialer0
   Time until disconnect 118 secs
   Current call connected 00:01:05
   Connected to 8358662
   
   
   
   I've only got 2 days left....
   
   
   
   Benjy Rife
   MCSE, CNE, CCIE Candidate
   brife@bignet.net
   www.bignet.net/~brife



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:42 GMT-3