cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
664
Views
0
Helpful
4
Replies

Help ISDN issue

jcutler0622
Level 1
Level 1

This has been set up to dial back to our DBU router. Do these configs look correct. These are the errors that I am getting in the routers log.Could this be a service provider issue or a mis-config issue. Please help ASAP. I will rate.

%ISDN-6-LAYER2DOWN: Layer 2 for Interface Se3/2:23, TEI 0 changed to down

%ISDN-6-LAYER2UP: Layer 2 for Interface Se3/2:23, TEI 0 changed to up

Remote site

interface BRI0/0

description Dial Backup to <router hostname> Dialer 251

ip address x.x.x.x x.x.x.x

encapsulation ppp

ip summary-address eigrp 100 x.x.x.x x.x.x.x 5

carrier-delay msec 0

dialer idle-timeout 30

dialer string <number>

dialer load-threshold 1 outbound

dialer watch-disable 15

dialer watch-group 1

dialer-group 1

isdn switch-type basic-net3

ppp authentication chap

ppp multilink

end

interface Dialer XXX

description Dialer-Profile for <rtr name> (Dialer-xxx)

ip unnumbered Loopback251

encapsulation ppp

ip summary-address eigrp 100 x.x.x.x x.x.x.x 5

ip summary-address eigrp 100 x.x.x.x x.x.x.x 175

ip policy route-map < policy name>

dialer pool 251

dialer remote-name <rtr hostname>

dialer idle-timeout 0

dialer string <Number>

dialer load-threshold 1 outbound

dialer max-call 2

dialer-group 1

no peer default ip address

no cdp enable

ppp authentication chap

ppp multilink

end

4 Replies 4

pciaccio
Level 4
Level 4

Josh:

The errors that you are seeing is referring to the D-Channel off the ISDN PRI T-1 that you must have. Probably the line is configured wrong or the line is down from the carrier. You need to do a show controller T-1 for the port and see if you are getting any errors or alarms off the T-1. Can you provide the configuration off the router with the T-1. Just the T-1 config and ISDN configs...Thanks...

This is the layer 2 debug output that I got.

Jan 23 08:24:27.855: ISDN Se2/2:23 Q921: User TX -> RRp sapi=0 tei=0 nr=126

Jan 23 08:24:27.859: ISDN Se2/2:23 Q921: User RX <- RRf sapi=0 tei=0 nr=114

Jan 23 08:24:28.659: ISDN Se2/3:23 Q921: User TX -> RRp sapi=0 tei=0 nr=8

Jan 23 08:24:28.663: ISDN Se2/3:23 Q921: User RX <- RRf sapi=0 tei=0 nr=100

Jan 23 08:24:32.775: ISDN Se3/2:23 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 23 08:24:32.923: ISDN Se3/2:23 Q921: User RX <- RRp sapi=0 tei=0 nr=0

Jan 23 08:24:32.927: ISDN Se3/2:23 Q921: User TX -> RRf sapi=0 tei=0 nr=0

Jan 23 08:24:33.775: ISDN Se3/2:23 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 23 08:24:34.775: ISDN Se3/2:23 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 23 08:24:35.775: ISDN Se3/2:23 Q921: User TX -> RRp sapi=0 tei=0 nr=0

Jan 23 08:24:36.775: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:37.775: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:38.063: ISDN Se2/0:23 Q921: User TX -> RRp sapi=0 tei=0 nr=72

Jan 23 08:24:38.067: ISDN Se2/0:23 Q921: User RX <- RRf sapi=0 tei=0 nr=117

Jan 23 08:24:38.775: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:39.775: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:40.775: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se3/2:23, TEI 0 changed to down

Jan 23 08:24:40.779: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:41.687: ISDN Se3/0:23 Q921: User TX -> RRp sapi=0 tei=0 nr=110

Jan 23 08:24:41.691: ISDN Se3/0:23 Q921: User RX <- RRf sapi=0 tei=0 nr=57

Jan 23 08:24:41.779: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:42.779: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:43.779: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:44.779: ISDN Se3/2:23 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 23 08:24:44.783: ISDN Se3/2:23 Q921: User RX <- UAf sapi=0 tei=0

Jan 23 08:24:44.783: %ISDN-6-LAYER2UP: Layer 2 for Interface Se3/2:23, TEI 0 changed to up

Jan 23 08:24:45.367: ISDN Se2/1:23 Q921: User TX -> RRp sapi=0 tei=0 nr=79

Jan 23 08:24:45.371: ISDN Se2/1:23 Q921: User RX <- RRf sapi=0 tei=0 nr=127

Jan 23 08:24:47.207: ISDN Se4/0:23 Q921: User TX -> RRp sapi=0 tei=0 nr=41

Jan 23 08:24:47.211: ISDN Se4/0:23 Q921: User RX <- RRf sapi=0 tei=0 nr=22

Jan 23 08:24:47.583: ISDN Se3/1:23 Q921: User TX -> RRp sapi=0 tei=0 nr=12

Jan 23 08:24:47.587: ISDN Se3/1:23 Q921: User RX <- RRf sapi=0 tei=0 nr=124

Jan 23 08:24:47.591: ISDN Se3/3:23 Q921: User TX -> RRp sapi=0 tei=0 nr=116

Jan 23 08:24:47.595: ISDN Se3/3:23 Q921: User RX <- RRf sapi=0 tei=0 nr=2

The T-1 configs haven't changed they are the same they have been for a year. It was the ISDN congigs that were changed. This seems to be bouncing for the past couple days every 2-5 min. I opened a tkt with the lec they stated they couldn't loop our csu. Do you think this is a layer 2 issue and not a config issue?

This could be a layer 1 or layer 2 issue. Can you please provide the configurations for both routers...

It looks to be a LEC problem. The only reason I would suspect a mis-config is someone changed the config on the same day that it started having a problem. I am on the phone with the lec now trying to resolve this issue. Thank you very much for your help I will let you know how it goes.

Review Cisco Networking products for a $25 gift card