08-04-2008 12:04 AM - edited 03-03-2019 11:00 PM
Hello,
I have a problem to configure a Serial Interface connected to a ISDN PRI.
The Layer 1 is up, the layer 2 is inTEI_Assigned state, but I can't making any calls trough thsi interface.
I receive this message all the 11 seconds:
Q931: Ux_DLRelInd: DL_REL_IND received from L2
If someone have any idea on this problem?
Thanks in advance for your help,
GWKoneHQ#sh isdn status
ISDN Serial0/1/0:15 interface
dsl 2, interface ISDN Switchtype = primary-net5
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 2 CCBs = 0
The Free Channel Mask: 0xFFFF7FFF
Number of L2 Discards = 0, L2 Session ID = 39
Total Allocated ISDN CCBs = 2
GWKoneHQ# sh controllers e1
E1 0/1/0 is up.
Applique type is Channelized E1 - balanced
Description: PRIMARIO VODAFONE
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20040802, FPGA: 13, spm_count = 0
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (607 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
2 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
188 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
188 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
GWKoneHQ#sh debug
The following ISDN debugs are enabled on DSL 2:
debug isdn error is ON.
debug isdn q921 is ON. (filter is OFF)
debug isdn q931 is ON. (filter is OFF)
Aug 4 07:58:04.860: ISDN Se0/1/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 4 07:58:04.860: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:05.860: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:06.860: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:07.860: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:08.860: ISDN Se0/1/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 4 07:58:13.860: ISDN Se0/1/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 4 07:58:13.860: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:14.860: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:15.860: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:16.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:17.861: ISDN Se0/1/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 4 07:58:22.861: ISDN Se0/1/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 4 07:58:22.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:23.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:24.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:25.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:26.861: ISDN Se0/1/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 4 07:58:31.861: ISDN Se0/1/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 4 07:58:31.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:32.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:33.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:34.861: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Aug 4 07:58:35.861: ISDN Se0/1/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
08-04-2008 06:10 AM
You are no in the multframe established state, so layer 2 is not up. This is confirmed by the q921 debug logs - when the router sends a SABME, the network should immediately respond with a UA (unnumbered acknowledgement). You will to call up the telco and scream at them.
Typically the telco will say the problem is with your equipment before they can even be bothered to check theirs so you need some way to confirm how E1/T1 interface.
If you want to confirm your hardware is OK, do the following :
1) Configure TS 16 on the controller as a channel-group
\\
2)\ Enable CDP and run 'debug cdp packet'
3) Use a RJ45 E1/T1 loopback to connect the TX and RX pairs (pins 1--4, 2--5)
4) CDP debugs show packets out and in and confirm if the controller is working
!
controller E1 1/1
channel-group 0 timeslots 16
!
*Aug 23 1:03:46.586: CDP-PA: version 2 packet sent out on Serial1/1:0
*Aug 23 1:03:46.626: CDP-PA: Packet received from multi-9-7 on interface Serial 1/1:0
*Aug 23 1:03:46.626: **Entry found in cache**
multi-9-7#sh cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
multi-9-7 Ser 1/1:0 147 R S I 3825 Ser 1/1:0
multi-9-7#
08-04-2008 10:55 PM
Thanks for your help,
I'm sure my controller work, because I have connected another E1 Line from another TELCO, and it's working fine...
So I will to contact the Telco to know more about this problem,
12-16-2008 11:59 AM
What was the outcome on this. I'm having an issue bringing up a circuit with the same logs.
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide