thing with ppp multilink is the following Both end times ie, load-thres, dialer-timeouts have to be exactly the same. Also, I found that u need ppp multilink on the dialers and bri ints and ensure both sides are the same.
Maybe this will help. -----Original Message----- From: Leo Song [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 18:49 To: [EMAIL PROTECTED] Subject: Help needed on ISDN PPP Multilink [7:58474] Hi, friends. I have one ISDN issue which make me quite headache, ok, I can call each channel up (through dialer map or isdn call interface command) separately without problem, which the problem is when I try to leverage PPP multilink to bundle two channels in case of load-threshold events was fired, the calling router did try to establish the second channel, and it's connected, and the second call was CONNECTED for couple of seconds, then disconnected, without error messages. I opened a ticket with Cisco and our ISP, but no positive answer yet, any help. The following attachment is the debug (isdn, q931, ppp) from the called router, as well as the config-file from the calling router, and the configuration of called router is very similar with the calling router, thanks. dslvanrt3#sh debug PPP: Multilink activity debugging is on Multilink events debugging is on First bytes of multilink packet debugging is on ISDN: ISDN events debugging is on ISDN Q931 packets debugging is on dslvanrt3#terminal monitor dslvanrt3# dslvanrt3# dslvanrt3# dslvanrt3# dslvanrt3# dslvanrt3# Dec 3 10:37:38: ISDN BR0: RX CONNECT pd = 8 callref = 0x81 Dec 3 10:37:38: Channel ID i = 0x89 Dec 3 10:37:38: ISDN BR0: RX was hung up. Dec 3 10:38:06: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from 14163623576 dsltorrt3, call lasted 28 seconds Dec 3 10:38:06: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down Dec 3 10:38:06: BR0:1 MLP: Multilink down event pending Dec 3 10:38:06: BR0:1 MLP: Multilink down event pending Dec 3 10:38:06: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x81 Dec 3 10:38:06: BR0:1 MLP: Removing link from dsltorrt3 Dec 3 10:38:06: dsltorrt3 MLP: Removing bundle Dec 3 10:38:06: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down Dec 3 10:38:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed state to down Dec 3 10:38:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to down Dec 3 10:38:06: ISDN BR0: RX CONNECT pd = 8 callref = 0x81 Dec 3 10:38:21: Channel ID i = 0x89 Dec 3 10:38:21: ISDN BR0: RX <- CONNECT_ACK pd = 8 callref = 0x01 Dec 3 10:38:21: Signal i = 0x4F - Alerting off Dec 3 10:38:21: Locking Shift to Codeset 5 Dec 3 10:38:21: Codeset 5 IE 0x2A i = 0x809A0B, '14163623576', 0x800109800114800114800114 Dec 3 10:38:21: ISDN BR0: received HOST_CONNECT Dec 3 10:38:21: ISDN BR0: Event: Connected to 14163623576 on B1 at 64 Kb/s Dec 3 10:38:22: BR0:1 MLP: Multilink up event pending Dec 3 10:38:22: Vi1 MLP: Added to huntgroup BR0 Dec 3 10:38:22: Vi1 MLP: Clone from BR0 Dec 3 10:38:22: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up Dec 3 10:38:22: BR0:1 MLP: dsltorrt3, multilink up, first link Dec 3 10:38:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed state to up Dec 3 10:38:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up Dec 3 10:38:27: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 14163623576 dsltorrt3 interface BRI0 ip address 10.10.191.2 255.255.255.0 encapsulation ppp bandwidth 128 isdn spid1 60468746360101 6874636 isdn spid2 60468746300101 6874630 dialer map ip 10.10.191.1 name dsltorrt3 14163623576 dialer map ip 10.10.191.1 name dsltorrt3 14163625538 dialer-group 1 no fair-queue ppp authentication chap ppp multilink hold-queue 75 out access-list 100 permit ip xxxxxxx dialer-list 1 protocol ip list 100 Leo For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=58552&t=58474 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
