From: Derek Fage (DerekF@xxxxxxxxxxx)
Date: Sun Jul 11 1999 - 17:59:46 GMT-3
Ben,
With PPP multilink, I'm fairly sure that you need to have the 'encaps ppp'
and the 'ppp multilink' on the physical interface as well.
I always put 'ppp authentication chap' on the dialer and the physical
interfaces as well. When doing this you can do a 'show user' and you will
see the remote user as a Virtual interface, with the BRI0:1 and BRI0:2
underneath if they are in use.
Derek...
> -----Original Message-----
> From: Chad Marsh [SMTP:chad@wa.net]
> Sent: 11 July 1999 21:23
> Cc: ccielab@groupstudy.com
> Subject: Re: ISDN Multilink PPP
>
> Ben, it sounds like the Multilink part isn't working right. Try a 'debug
> ip packet' and see if your pings are all going across one B-channel
> maybe? Also, I think you need to add 'encapsulation ppp' on the physical
> BRI0 interface. You might also change to 'dialer load-threshold 2', I
> think Stephen Hildebrandt was saying there was a bug in (not sure which
> versions of) IOS when it is set to 1, that it worked sporadically.
>
> Chad
>
> P.S. You say one end or the other will bring up the second B-channel.
> You have both sides setup to dial then? Isn't that unusual? If you do
> have it set up that way, I'm pretty sure you only want the
> load-threshold to be set on one side.
>
>
>
> > Ben Rife wrote:
> >
> > 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