ISDN Layer 2 Problems

[boo...@my-deja.com]

Hi, this may appear twice :)

I have a 801 Cisco router, and it has worked perfectly for 6 months,
but now everytime it tries to dial, I get the following error on the
console

%ISDN-6-LAYER2DOWN: Layer 2 for interface BRI0, TEI 255 changed to down

I have looked through cisco docs and can't find out more, so I am
coming to all the experience of you guys.

The telco says its a problem with the router.

The switch type is basic-net3

Thanks in advance :)

Carl

Sent via Deja.com http://www.deja.com/
Before you buy.

[Andreas Bourges]

In article <8g0r3c$1p7$1...@nnrp1.deja.com>,

boo...@my-deja.com wrote:
> %ISDN-6-LAYER2DOWN: Layer 2 for interface BRI0, TEI 255 changed to
down
> I have looked through cisco docs and can't find out more, so I am

...have you tried a "debug isdn q921" ? If not try it have a look at the
output, when trying to dial out.

Andy

[boo...@my-deja.com]

Here is the output from debug isdn p921:

00:53:20: ISDN BR0: TX -> IDREQ ri = 29037 ai = 127
00:53:22: ISDN BR0: TX -> IDREQ ri = 34878 ai = 127
00:53:24: ISDN BR0: TX -> IDREQ ri = 3103 ai = 127
00:53:26: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 255
changed to down

Not quite sure what it means :(

Also sho isdn status:

ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
Total Allocated ISDN CCBs = 0

The line light is on too

Hope this helps someone help me :)

thanks

Carl

[leroy]

This might be due to faulty Network Termination-1 box or the ISDN line is
full of errors.

Correct me if I am wrong.

Regards,

<boo...@my-deja.com> wrote in message news:8g0r3c$1p7$1...@nnrp1.deja.com...

> Hi, this may appear twice :)
>
> I have a 801 Cisco router, and it has worked perfectly for 6 months,
> but now everytime it tries to dial, I get the following error on the
> console
>

> %ISDN-6-LAYER2DOWN: Layer 2 for interface BRI0, TEI 255 changed to down

>
> I have looked through cisco docs and can't find out more, so I am

> coming to all the experience of you guys.
>
> The telco says its a problem with the router.
>
> The switch type is basic-net3
>
> Thanks in advance :)
>

[Owen Brodal-Robertson]

Don't know if it helps...

Is the IOS 12.0.4T or 12.0.5T ?

IF it is, you need to add the command: "isdn send-alerting" under the
BRI interface... it's a problem with this IOS and basic-net3 type ISDN
switches.

I believe this needs to be on the end that's accepting the call... but
it can't hurt to use it on both ends if you have access to them.

Regards,
Owen Brodal-Robertson
ow...@dunson.com.au - 0412 467 152
Systems Engineer - Dunson Pty Ltd.
"Windows announces it has corrupted it's registry, so I try to let it
fix it... reboot." -- Ewen McNeil

-----Original Message-----
From: boo...@my-deja.com [mailto:boo...@my-deja.com]
Posted At: Friday, 19 May 2000 0:33
Posted To: cisco
Conversation: ISDN Layer 2 Problems
Subject: Re: ISDN Layer 2 Problems

Here is the output from debug isdn p921:

00:53:20: ISDN BR0: TX -> IDREQ ri = 29037 ai = 127
00:53:22: ISDN BR0: TX -> IDREQ ri = 34878 ai = 127
00:53:24: ISDN BR0: TX -> IDREQ ri = 3103 ai = 127

00:53:26: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 255
changed to down

Not quite sure what it means :(

Also sho isdn status:

ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
Total Allocated ISDN CCBs = 0

The line light is on too

Hope this helps someone help me :)

thanks

Carl

[Stephen A. Metts]

Looking at this s Debug screen shows me that you're no receiving any
acknowledgement for the TelCo ISDN Switch. For each "ISDN BR0: TX -> IDREQ
ri = 29037 ai = 127" their should be a response from the TelCo ISDN Switch.
I have experienced problems were the router and the Switch would loose
connectivity to each other. When this would occur I would re-initialize the
ISDN Interface by shutdown and the restarting. Give it try.

<boo...@my-deja.com> wrote in message news:8g0uum$66c$1...@nnrp1.deja.com...