Hi It probably will help very much if you say : what router, what IOS version what BRI interface config you use...
Christian
-----Original Message----- From: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch]On Behalf Of Beat Rubischon Sent: Donnerstag, 3. März 2005 14:22 To: SWINOG Mailing List Subject: [swinog] ISDN Layer 2 Problem
Hello!
I'm trying to configure a ISDN backup link on a Cisco. Each time I reset the BRI it takes about 15 seconds until the session will be terminated from the Swisscom's side. Call out is only possible (but working) during this 15 second time frame.
Layer 1 is activated permanently since several years and working OK.
Following [1], I debugged the link:
[1] http://www.cisco.com/warp/public/129/bri-layer2.html
---8<--- Mar 1 01:26:39: ISDN BR0 Q921: User TX -> IDREQ ri=44602 ai=127 Mar 1 01:26:39: ISDN BR0 Q921: User RX <- IDASSN ri=44602 ai=89 Mar 1 01:26:39: ISDN BR0 Q921: L2_EstablishDataLink: sending SABME Mar 1 01:26:39: ISDN BR0 Q921: User TX -> SABMEp sapi=0 tei=89 Mar 1 01:26:39: ISDN BR0 Q921: User RX <- UAf sapi=0 tei=89 Mar 1 01:26:39: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 89 changed to up Mar 1 01:26:49: ISDN BR0 Q921: User RX <- RRp sapi=0 tei=89 nr=0 Mar 1 01:26:49: ISDN BR0 Q921: User TX -> RRf sapi=0 tei=89 nr=0 Mar 1 01:26:54: ISDN BR0 Q921: User RX <- DISCp sapi=0 tei=89 Mar 1 01:26:54: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 89 changed to down Mar 1 01:26:54: ISDN BR0 Q921: User TX -> UAf sapi=0 tei=89 Mar 1 01:26:54: ISDN BR0 Q921: L2_EstablishDataLink: DISC received & not Passive-shutdown SABME will not be sent. ---8<---
Cisco says "If the DISC message originated from the ISDN switch, contact the telco." But on the Swisscom-side, nobody is able to understand my problem or willing to help.
Any hint what I should say to the "Swisskomiker" to get the right solution? Anyone here who knows a magic keyword in IOS to disable the need for a permanent Layer 2 connection?
Thanks! Beat
Hello!
Am 03.03.05 schrieb Kuster, Christian:
It probably will help very much if you say : what router, what IOS version what BRI interface config you use...
I think it's more an generic problem then a product specific one... but:
---8<--- rt-1#show version Cisco IOS Software, C836 Software (C836-K9O3S8Y6-M), Version 12.3(8)YA1, RELEASE SOFTWARE (fc1) Synched to technology version 12.3(9.6)T Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2005 by Cisco Systems, Inc. Compiled Fri 21-Jan-05 17:22 by ealyon
ROM: System Bootstrap, Version 12.2(11r)YV1, RELEASE SOFTWARE (fc1) ROM: Cisco IOS Software, C836 Software (C836-K9O3S8Y6-M), Version 12.3(8)YA1, RELEASE SOFTWARE (fc1)
rt-1 uptime is 2 days, 15 hours, 56 minutes System returned to ROM by reload at 01:42:52 CET Fri Mar 1 2002 System restarted at 22:49:01 CET Mon Feb 28 2005 System image file is "flash:c836-k9o3s8y6-mz.123-8.YA1.bin"
[cryptographic blabla]
Cisco C836 (MPC857T) processor (revision 0x201) with 46695K/2457K bytes of memory. Processor board ID FOC09042B0E (623996758), with hardware revision 0000 CPU rev number 7 2 Ethernet interfaces 4 FastEthernet interfaces 1 ISDN Basic Rate interface 1 ATM interface 128K bytes of NVRAM. 12288K bytes of processor board System flash (Read/Write) 2048K bytes of processor board Web flash (Read/Write)
Configuration register is 0x2102 ---8<---
Beat
Hello
I use the following config with the 836er Cisco Routers.
I think it's more an generic problem then a product specific one... but:
interface BRI0 no ip address encapsulation ppp no ip route-cache no ip mroute-cache load-interval 30 dialer pool-member 6 isdn switch-type basic-net3 isdn tei-negotiation first-call no cdp enable ppp multilink
Regards Erich
Hello!
Am 03.03.05 schrieb Erich Hohermuth:
interface BRI0 no ip address encapsulation ppp no ip route-cache no ip mroute-cache load-interval 30 dialer pool-member 6 isdn switch-type basic-net3 isdn tei-negotiation first-call no cdp enable ppp multilink
My options:
interface BRI0 description ISDN interface no ip address encapsulation ppp dialer pool-member 2 isdn switch-type basic-net3 isdn answer1 0556145044 isdn calling-number 0556145044 no cdp enable
I added "isdn tei-negotiation first-call", channel bundling is no desired option:
rt-1#conf t rt-1(config)#int bri0 rt-1(config-if)#isdn tei-negotiation first-call rt-1(config-if)#no ip route-cache rt-1(config-if)#no ip mroute-cache rt-1(config-if)#end Mar 3 15:11:39.332: %SYS-5-CONFIG_I: Configured from console by console
rt-1#clear interface bri 0 Mar 3 15:12:05.896: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 75 changed to up
(now Layer 2 is up):
rt-1#show isdn status Mar 3 15:14:19.404: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 77 changep Global ISDN Switchtype = basic-net3 ISDN BRI0 interface dsl 0, interface ISDN Switchtype = basic-net3 Layer 1 Status: ACTIVE Layer 2 Status: TEI = 77, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 0 CCBs = 0 The Free Channel Mask: 0x80000003 Total Allocated ISDN CCBs = 0
(15 seconds later):
Mar 3 15:12:20.864: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 75 changed to down
(and Layer 2 is down):
rt-1#show isdn status Global ISDN Switchtype = basic-net3 ISDN BRI0 interface dsl 0, interface ISDN Switchtype = basic-net3 Layer 1 Status: ACTIVE Layer 2 Status: TEI = 75, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 0 CCBs = 0 The Free Channel Mask: 0x80000003 Total Allocated ISDN CCBs = 0
Dialing is only possible while Layer 2 Status is MULTIPLE_FRAME_ESTABLISHED...
Beat
On Thu, 3 Mar 2005 15:16:24 +0100 (CET) Beat Rubischon beat@rubis.ch wrote: Hi
Am 03.03.05 schrieb Erich Hohermuth:
interface BRI0 no ip address encapsulation ppp no ip route-cache no ip mroute-cache load-interval 30 dialer pool-member 6 isdn switch-type basic-net3 isdn tei-negotiation first-call no cdp enable ppp multilink
My options:
interface BRI0 description ISDN interface no ip address encapsulation ppp dialer pool-member 2 isdn switch-type basic-net3 isdn answer1 0556145044 isdn calling-number 0556145044 no cdp enable
I would remove the 'isdn answer1 ' and 'isdn calling-number' options until you have a working connection. after that you may add one after one option and check if it still works.
and what is your 'interface dialer <n>' configuration? maybe the hardware interface cannot bind the call to the software interface.
Hope it helps Ueli
-
Beat Rubischon -
Erich Hohermuth -
Kuster, Christian -
Pascal Gloor -
Ueli Heuer