Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2453
Views
24
Helpful
13
Replies

Isdn invoked with no apparently reason

maghisi-2007
Level 1
Level 1

‎10-12-2009 07:03 AM - edited ‎03-04-2019 06:20 AM

Isdn backup layer 2 is constantly invoked with no reason for me as per local PTT main line is working perfectly.

By activating debug dialer events and debug isdn events, I can't get relevant informations.

I attached sh ver/sh run/debug results

Thanks

Oct 12 12:37:09: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 70 changed to down

Oct 12 12:52:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 71 changed to up

Oct 12 12:53:09: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 71 changed to down

Labels:
Preview file
3 KB
0 Helpful
13 Replies 13

paolo bevilacqua
Hall of Fame
Hall of Fame

‎10-12-2009 07:54 AM

That is normal, configure "isdn tei-negotiation preserve" so the tei will not be negotiated every time L2 goes up.

maghisi-2007
Level 1
Level 1
In response to paolo bevilacqua

‎10-13-2009 01:05 AM

I'm trying, thanks

0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to maghisi-2007

‎10-13-2009 02:58 AM

You are welcome, please remember to rate useful posts with the scrollbox below.

0 Helpful

maghisi-2007
Level 1
Level 1
In response to paolo bevilacqua

‎10-13-2009 06:30 AM

Oct 13 14:12:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 83 changed to up

Oct 13 14:13:09: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 83 changed to down

I implemented the isdn command suggested above but I can see isdn layer 2 is still invoked even if the main circuit never got problems today

0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to maghisi-2007

‎10-13-2009 06:45 AM

Check with "debug isdn q931" and "term mon" if there is any call associated with the activation.

maghisi-2007
Level 1
Level 1
In response to paolo bevilacqua

‎10-14-2009 01:03 AM

debug isdn error is ON.

debug isdn q921 is ON. (filter is OFF)

debug isdn q931 is ON. (filter is OFF)

sh log

Oct 14 03:00:56: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Oct 14 03:00:56: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 03:00:57: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 03:00:57: ISDN BR0/1/0 Q921: User RX <- UAf sapi=0 tei=83

Oct 14 03:00:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 83 changed to up

Oct 14 03:01:07: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=83 nr=0

Oct 14 03:01:07: ISDN BR0/1/0 Q921: User RX <- RRf sapi=0 tei=83 nr=0

Oct 14 03:01:10: ISDN BR0/1/0 Q921: User RX <- DISCp sapi=0 tei=83

Oct 14 03:01:10: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 83 changed to down

Oct 14 03:01:10: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=83

Oct 14 03:01:10: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Oct 14 03:01:20: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

Oct 14 03:16:56: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Oct 14 03:16:56: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 03:16:57: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 03:16:57: ISDN BR0/1/0 Q921: User RX <- UAf sapi=0 tei=83

Oct 14 03:16:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 83 changed to up

Oct 14 03:17:07: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=83 nr=0

Oct 14 03:17:07: ISDN BR0/1/0 Q921: User RX <- RRf sapi=0 tei=83 nr=0

Oct 14 03:17:10: ISDN BR0/1/0 Q921: User RX <- DISCp sapi=0 tei=83

Oct 14 03:17:10: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 83 changed to down

Oct 14 03:17:10: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=83

Oct 14 03:17:10: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Oct 14 03:17:20: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

Oct 14 07:16:56: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Oct 14 07:16:56: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 07:16:57: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 07:16:57: ISDN BR0/1/0 Q921: User RX <- UAf sapi=0 tei=83

Oct 14 07:16:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 83 changed to up

Oct 14 07:17:07: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=83 nr=0

Oct 14 07:17:07: ISDN BR0/1/0 Q921: User RX <- RRf sapi=0 tei=83 nr=0

Oct 14 07:17:10: ISDN BR0/1/0 Q921: User RX <- DISCp sapi=0 tei=83

Oct 14 07:17:10: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 83 changed to down

Oct 14 07:17:10: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=83

Oct 14 07:17:10: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Oct 14 07:17:20: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

Oct 14 07:32:56: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Oct 14 07:32:56: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 07:32:57: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=83

Oct 14 07:32:57: ISDN BR0/1/0 Q921: User RX <- UAf sapi=0 tei=83

Oct 14 07:32:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 83 changed to up

Oct 14 07:33:07: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=83 nr=0

Oct 14 07:33:07: ISDN BR0/1/0 Q921: User RX <- RRf sapi=0 tei=83 nr=0

Oct 14 07:33:10: ISDN BR0/1/0 Q921: User RX <- DISCp sapi=0 tei=83

Oct 14 07:33:10: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 83 changed to down

Oct 14 07:33:10: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=83

Oct 14 07:33:10: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Oct 14 07:33:20: ISDN BR0/1/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3

0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to maghisi-2007

‎10-14-2009 01:59 AM

You could enable debug bri to see if L1 activation comes from router or network.

Anyway, there are no unwanted calls and that is what matters, you can ignore the activations.

maghisi-2007
Level 1
Level 1
In response to paolo bevilacqua

‎10-14-2009 04:14 AM

Just to try I activate anyway debug bri:

Oct 14 11:32:56: BRI0/1/0: In state F3, Received code Activate request downstream, Info 2 received

Oct 14 11:32:56: BRI0/1/0 : changing state to F6

Oct 14 11:32:56: BRI0/1/0: In state F6, Received code Activation Indication with Priority to 8, Info 4 received

Oct 14 11:32:56: BRI0/1/0 : Sending PH-Activate to the layer 2

Oct 14 11:32:56: BRI0/1/0 : changing state to F7

Oct 14 11:32:56: dchan tx fifo flush, actual_time = 0

Oct 14 11:32:56: BRI0/1/0 : stop and reset timer t3

Oct 14 11:32:56: BRI0/1/0: In state F7, Transmitting code Activation Request, set Priority to 8

Oct 14 11:32:56: BRI0/1/0 : Sending MPH-ERROR Indication reporting recovery from error to layer2

Oct 14 11:32:56: dchan tx start

Oct 14 11:32:56: dchan tx intr

Oct 14 11:32:57: dchan tx start

Oct 14 11:32:57: dchan tx intr

Oct 14 11:32:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 83 changed to up

Oct 14 11:33:07: dchan tx start

Oct 14 11:33:07: dchan tx intr

Oct 14 11:33:10: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 83 changed to down

Oct 14 11:33:10: dchan tx start

Oct 14 11:33:10: dchan tx intr

Oct 14 11:33:20: BRI0/1/0: In state F7, Received code Activate request downstream, Info 2 received

Oct 14 11:33:20: dchan tx fifo flush, actual_time = 0

Oct 14 11:33:20: BRI0/1/0 : changing state to F6

Oct 14 11:33:20: BRI0/1/0 : Sending MPH-ERROR Indication reporting error to layer2

Oct 14 11:33:20: BRI0/1/0: In state F6, Received code unknown code

Oct 14 11:33:20: BRI0/1/0 : stop and reset timer t3

Oct 14 11:33:20: BRI0/1/0 : changing state to F3

Oct 14 11:33:20: BRI0/1/0 : Starting layer 1 T4

Oct 14 11:33:21: BRI0/1/0 : T4 expired

Oct 14 11:33:21: BRI0/1/0 : Sending PH-DEACTIVATE to layer2

Oct 14 11:33:21: BRI0/1/0 : changing state to F3BRI: disable channel B1

BRI: disable channel B2

Oct 14 11:33:21: BRI0/1/0: In state F3, Transmitting code Deactivate indication upstream

Oct 14 11:33:21: BRI0/1/0: In state F3, Received code Deactivate indication downstream

Oct 14 11:33:21: BRI0/1/0 : do nothingBRI: disable channel B1

BRI: disable channel B2

Oct 14 11:48:56: BRI0/1/0: In state F3, Received code Activate request downstream, Info 2 received

Oct 14 11:48:56: BRI0/1/0 : changing state to F6

Oct 14 11:48:56: BRI0/1/0: In state F6, Received code Activation Indication with Priority to 8, Info 4 received

Oct 14 11:48:56: BRI0/1/0 : Sending PH-Activate to the layer 2

Oct 14 11:48:56: BRI0/1/0 : changing state to F7

Oct 14 11:48:56: dchan tx fifo flush, actual_time = 0

Oct 14 11:48:56: BRI0/1/0 : stop and reset timer t3

Oct 14 11:48:56: BRI0/1/0: In state F7, Transmitting code Activation Request, set Priority to 8

Oct 14 11:48:56: BRI0/1/0 : Sending MPH-ERROR Indication reporting recovery from error to layer2

Oct 14 11:48:56: dchan tx start

Oct 14 11:48:56: dchan tx intr

Oct 14 11:48:57: dchan tx start

Oct 14 11:48:57: dchan tx intr

Oct 14 11:48:57: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 83 changed to up

Oct 14 11:49:07: dchan tx start

Oct 14 11:49:07: dchan tx intr

Oct 14 11:49:10: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 83 changed to down

Oct 14 11:49:10: dchan tx start

Oct 14 11:49:10: dchan tx intr

Oct 14 11:49:20: BRI0/1/0: In state F7, Received code Activate request downstream, Info 2 received

Oct 14 11:49:20: dchan tx fifo flush, actual_time = 0

Oct 14 11:49:20: BRI0/1/0 : changing state to F6

Oct 14 11:49:20: BRI0/1/0 : Sending MPH-ERROR Indication reporting error to layer2

Oct 14 11:49:20: BRI0/1/0: In state F6, Received code unknown code

Oct 14 11:49:20: BRI0/1/0 : stop and reset timer t3

Oct 14 11:49:20: BRI0/1/0 : changing state to F3

Oct 14 11:49:20: BRI0/1/0 : Starting layer 1 T4

Oct 14 11:49:21: BRI0/1/0 : T4 expired

Oct 14 11:49:21: BRI0/1/0 : Sending PH-DEACTIVATE to layer2

Oct 14 11:49:21: BRI0/1/0 : changing state to F3BRI: disable channel B1

BRI: disable channel B2

0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to maghisi-2007

‎10-14-2009 04:51 AM

Activation comes from network and there is nothing you can do about.

Please review your use of the rating system, because my info is 100% complete and correct, not fairly rated with "3".

maghisi-2007
Level 1
Level 1
In response to paolo bevilacqua

‎10-14-2009 05:44 AM

Excuse me for the rating system. I didn't want to be unfair. I do not often use cisco forum and I was thinking that I should give you the best rating just at the end of the conversation. Now I know I can give you the best rating at any time. When you write that activation comes from the network do you mean that is coming from the customer Lan?

0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to maghisi-2007

‎10-14-2009 06:32 AM

No, it comes from telco with no apparent reason, as mentioned you cannot do anything about, and it's not harmful in any manner.

maghisi-2007
Level 1
Level 1
In response to paolo bevilacqua

‎10-14-2009 11:39 PM

Ok thanks for all your efforts. Excuse me once again for mine previous errors. For me this conversation has been successfully closed

0 Helpful

paolo bevilacqua
Hall of Fame
Hall of Fame
In response to maghisi-2007

‎10-15-2009 04:25 AM

You are welcome, thank you for the nice rating and good luck.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card