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 Beat Rubischon:
I'm trying to configure a ISDN backup link on a Cisco.
First, thanks a lot for your ideas. I have now debugged a lot and my results are the following:
- It's not a problem in the wiring or termination.
- Dial-Out is possible when Layer 2 is in state "MULTIPLE_FRAME_ESTABLISHED" (aka an running call) or "NOT Activated" (not initialized yet)
- Dial-Out is not possible when Layer 2 is in state "TEI_ASSIGNED", debugging shows that the communication simple times out.
I assume now a bug in the IOS - 12.3(8)YA [1] is an early deployment release. I hope to get my service contract soon to access other images.
[1] http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/prod_bulletin0900aecd...
A disconnect of the S-Bus resets the Layer 2 and with the setting "isdn tei-negotiation first-call" no new TEI is allocated. So I will try to switch off Layer 1 - each time Swisscom shuts down Layer 1, my BRI would be resetted :-)
May be someone has another idea. I have put the config and a logfile on [2].
Beat
Hello Beat
I remember, we had also some problems with ZyXEL-ISDN-Routers. We call then to the Swisscom, they may put the Layer 2 always to "on"-state. Maybe it helps?
rog
Beat Rubischon schrieb:
Hello!
Am 03.03.05 schrieb Beat Rubischon:
I'm trying to configure a ISDN backup link on a Cisco.
First, thanks a lot for your ideas. I have now debugged a lot and my results are the following:
It's not a problem in the wiring or termination.
Dial-Out is possible when Layer 2 is in state "MULTIPLE_FRAME_ESTABLISHED" (aka an running call) or "NOT Activated" (not initialized yet)
Dial-Out is not possible when Layer 2 is in state "TEI_ASSIGNED", debugging shows that the communication simple times out.
I assume now a bug in the IOS - 12.3(8)YA [1] is an early deployment release. I hope to get my service contract soon to access other images.
[1] http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/prod_bulletin0900aecd...
A disconnect of the S-Bus resets the Layer 2 and with the setting "isdn tei-negotiation first-call" no new TEI is allocated. So I will try to switch off Layer 1 - each time Swisscom shuts down Layer 1, my BRI would be resetted :-)
May be someone has another idea. I have put the config and a logfile on [2].
Beat
Hi Beat
I agree to Roger. There is a power-save mode which affects the ISDN-Layer2. At least the BRI's from the old cisco2500 needed this feature, otherwise I saw the same behaviour. Go and ask Swisscom, they should activate the Layer2.
Cheers -Lukas
-----Original Message----- From: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] On Behalf Of Roger Buchwalder Sent: Donnerstag, 3. März 2005 23:12 To: swinog@swinog.ch Subject: Re: [swinog] ISDN Layer 2 Problem
Hello Beat
I remember, we had also some problems with ZyXEL-ISDN-Routers. We call then to the Swisscom, they may put the Layer 2 always to "on"-state. Maybe it helps?
rog
Beat Rubischon schrieb:
Hello!
Am 03.03.05 schrieb Beat Rubischon:
I'm trying to configure a ISDN backup link on a Cisco.
First, thanks a lot for your ideas. I have now debugged a lot and my results are the following:
It's not a problem in the wiring or termination.
Dial-Out is possible when Layer 2 is in state "MULTIPLE_FRAME_ESTABLISHED" (aka an running call) or "NOT Activated" (not initialized yet)
Dial-Out is not possible when Layer 2 is in state "TEI_ASSIGNED", debugging shows that the communication simple times out.
I assume now a bug in the IOS - 12.3(8)YA [1] is an early deployment release. I hope to get my service contract soon to access other images.
[1] http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/prod_bulletin09 00aecd80157bb5.html
A disconnect of the S-Bus resets the Layer 2 and with the setting "isdn tei-negotiation first-call" no new TEI is allocated. So I will try to switch off Layer 1 - each time Swisscom shuts down Layer 1, my BRI would be resetted :-)
May be someone has another idea. I have put the config and a logfile on [2].
Beat
_______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Hello!
Am 03.03.05 schrieb Beat Rubischon:
I'm trying to configure a ISDN backup link on a Cisco.
First, thanks a lot for your ideas. I have now debugged a lot
It works now. IOS 12.3(8)YA1 which was installed from the distributor is simple broken. It does not work when Layer 2 goes down.
Swisscom ist not willing to switch on Layer 2 for private customers. Welcome good new world.
A downgrade to IOS 12.3(7)XR3 which is 2 months older solved all problems.
Thanks to everyone who helped me to track down the problem!
Beat
-
Beat Rubischon -
Lukas Krattiger (NOC) -
Roger Buchwalder