PRI issues, D-channel wont complete Layer 2 connection with far end

[donaldbabcock]

As stated we have a PRI that is down. All hardware on both sides, our switch and far end carrier switch, tests fine. The local provider and the carrier have tested the equipment in between and everything is clean and programmed correctly as ESF/B8ZS the entire way through.

Our PRI span comes up but when the D channel tries and establishes the connection to the far end it cycles through the following messeage:

DCH054 DCH: 28 EST REMOTE TIME:

Here is a few print outs of how we are setup and what is going on:

PRT


TYPE ADAN DCH 28




ADAN DCH 28

CTYP MSDL

MG_CARD 004 0 06

PORT 1

DES FTS2001

USR PRI

DCHL 28

OTBF 32

PARM RS422 DTE

DRAT 64KC

CLOK EXT

IFC D100

SIDE USR

CNEG 1

RLS ID 26

RCAP

MBGA NO

OVLR NO

OVLS NO

T200 3

T203 10

N200 3

N201 260

K 7



REQ ****


>

OVL000

>LD 21


PT1000



REQ: PRT


TYPE: RDB


CUST 0


ROUT 28




TYPE RDB

CUST 00

ROUT 28

DES FTS2001

TKTP TIE

M911P NO

ESN NO

RPA NO

CNVT NO

SAT NO

IDEF NET

RCLS EXT

VTRK NO

NODE

DTRK YES

BRIP NO

DGTP PRI

ISDN YES

MODE PRA

IFC D100

SBN NO

PNI 00000

NCNA YES

NCRD NO

CHTY BCH

CTYP UKWN

INAC NO

ISAR NO

CPUB OFF

DAPC NO

BCOT 0

DSEL VOD

PTYP PRI

AUTO NO

DNIS NO

DCDR NO

ICOG IAO

PREM NO

SRCH LIN

TRMB YES

STEP

ACOD 690

TCPP NO

PII NO

TARG

CLEN 1

BILN NO

OABS

INST 404

ANTK

SIGO STD

MFC NO

ICIS YES

OGIS YES

PTUT 0

TIMR ICF 512

OGF 512

EOD 13952

NRD 10112

DDL 70

ODT 4096

RGV 640

GTO 896





PAGE 002



GTI 896

SFB 3

NBS 2048

NBL 4096

TFD 0

DTD NO

SCDT NO

2 DT NO

DRNG NO

CDR YES

INC YES

LAST NO

QREC NO

OAL YES

AIA NO

OAN YES

OPD NO

NDP EXC 0

CDRX NO

NATL YES

SSL

CFWR NO

IDOP NO

MUS NO

PANS YES

FRL 0 0

FRL 1 0

FRL 2 0

FRL 3 0

FRL 4 0

FRL 5 0

FRL 6 0

FRL 7 0

AUTH YES

TDET NO

TTBL 0

ATAN NO

PLEV 2

OPR NO

ALRM NO

ART 0

TIDY 7199928 28

SGRP 0

CCBA NO

ARDN NO

AACR NO



>LD 96

DCH000


.ENL DCH 28

.STAT DCH 28

DCH 028 : SDCH RST AUTO
DES : FTS2001
.PLOG DCH 28

.
DCH: 28 MAINT CONFIRM TIME: 8:56:33
COUNTER VALUE
PLOG CLEARED
STAT DCH 28

DCH 028 : OPER AEST AUTO
DES : FTS2001
.
DCH055 DCH: 28 RLS NO RESPONSE TIME: 8:56:37 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:37 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:39 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:39 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:41 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:41 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:43 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:43 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:43 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:45 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:45 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:47 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:47 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:49 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:49 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:51 27/11/2013

DCH054 DCH: 28 EST REMOTE TIME: 8:56:51 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:53 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:53 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:55 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:55 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:57 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:57 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:57 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:59 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:56:59 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:57:01 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:57:01 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:57:03 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:57:03 27/11/2013
DCH054 DCH: 28 EST REMOTE TIME: 8:57:05 27/11/2013 DIS
DCH054 DCH: 28 EST REMOTE TIME: 8:57:05 27/11/2013 DCH 28
DCH054 DCH: 28 EST REMOTE TIME: 8:57:07 27/11/2013

.PLOG DCH 28

.
DCH: 28 MAINT CONFIRM TIME: 8:57:11
COUNTER VALUE
2 31
3 1


DCH055 DCH: 28 RLS CONFIRM TIME: 8:57:13 27/11/2013

STAT DCH 28

DCH 028 : DSBL RST AUTO
DES : FTS2001

From looking at the D channel log the distant end is telling my switch to re-establish the link for the D channel so it tries to. This will repeat until the counter fills (255 times) and then it will stop trying to establish the link. Also as seen on counter 3 we are sending SABME but not getting a reply back. Every few minutes this runs it will pop a counter 25 which if i understand it correctly the link was setup my switch said it was ready to receive but never got anything back and the re-establishment loop continues.

The carrier switch is setup as interface DMS250 which is the only thing that seems to be different between the two at first glance. According to the carrier this wont be an issue as all DMS interfaces use the same language it's just how many end devices the switch link handles.

Any thoughts or suggestions would be appreaciated as this has been down for almost a week now and is our only Long-Distance circuit we have.

 

[PERRYPJ]

Is this a new install or was it working

OLD ROLMEN WORKING ON NORTELS AND AVAYA

 

[bhassell2000]

Can you loop it back to yourself and have the D channel establish and get message Release Wrong Mode?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[donaldbabcock]

This is an existing circuit that has been working error free for awhile. We have performed all available hardware tests with no issues noted. I'll double check the local loopback results as that was done last week.

 

[donaldbabcock]

The first part of this is with a loop back plug on the back of the MSDL



DCH000

.stat dch 28


DCH010





.

.

DCH009



stat dch 28


DCH 028 : DSBL RST AUTO

DES : FTS2001

.enl dch 28


.stat dch 28


DCH 028 : DSBL RST AUTO

DES : FTS2001

.stat dch 28


DCH 028 : DSBL RST AUTO

DES : FTS2001

.enl dch

DCH1019 28 0F3344FB 00000003

28


.stat dch 28


DCH 028 : SDCH RST AUTO

DES : FTS2001

.stat e d

DCH055 DCH: 28 RLS RED ALRM TIME: 10:28:41 27/11/2013

ch 28


DCH 028 : OPER RLS AUTO

DES : FTS2001

.enl test 28


.

DCH057 DCH: 28 TEST TIME: 10:28:47 27/11/2013

stat c dch 28


DCH 028 : OPER TST IDLE IDLE AUTO

DES : FTS2001

.enl llb 28


.stat dch 28


DCH 028 : OPER TST LLB LLB AUTO

DES : FTS2001

.test llb 28


.

DCH: 28 DU TEST CONFIRM TIME: 10:29:01

TEST: PASS



DCH: 28 XDU TEST CONFIRM TIME: 10:29:01

TEST: PASS

dis llb 28


.dis test 28


.

DCH055 DCH: 28 RLS RED ALRM TIME: 10:29:07 27/11/2013

est dch 28


.stat dch 28

DCH055 DCH: 28 RLS RED ALRM TIME: 10:29:17 27/11/2013




DCH 028 : OPER RLS AUTO

DES : FTS2001



The next part is with the T1 card in local loopback mode:

stat dch 28


DCH 028 : DSBL RST AUTO

DES : FTS2001

.enl dch 28


.stat dch 28


DCH 028 : SDCH RST AUTO

DES : FTS2001

.stat dch 28


DCH 028 : OPER REST AUTO

DES : FTS2001

.stat dch

DCH055 DCH: 28 RLS NO RESPONSE TIME: 10:31:19 27/11/2013

28


DCH 028 : OPER RLS AUTO

DES : FTS2001

.

DCH054 DCH: 28 EST REMOTE TIME: 10:31:21 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:31:23 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:31:23 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:31:25 27/11/2013

stat dch 28


DCH 028 : OPER EST ACTV AUTO

DES : FTS2001

.stat dch 28


DCH 028 : OPER EST ACTV AUTO

DES : FTS2001

.

DCH055 DCH: 28 RLS NO RESPONSE TIME: 10:31:47 27/11/2013

stat dch 28


DCH 028 : OPER AEST AUTO

DES : FTS2001

.

DCH055 DCH: 28 RLS NO RESPONSE TIME: 10:31:53 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:05 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:05 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:07 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:07 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:09 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:09 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:11 27/11/2013



DCH054 DCH: 28 EST REMOTE TIME: 10:32:11 27/11/2013

dis

DCH054 DCH: 28 EST REMOTE TIME: 10:32:13 27/11/2013

dch 28

DCH054 DCH: 28 EST REMOTE TIME: 10:32:13 27/11/2013




.stat dch 28


DCH 028 : OPER ARLS AUTO

DES : FTS2001

.stat dch

DCH055 DCH: 28 RLS CONFIRM TIME: 10:32:19 27/11/2013



28


DCH 028 : DSBL RST AUTO

DES : FTS2001

.

 

[donaldbabcock]

I never got the "Release wrong mode" indication. Can you explain the process for doing the loop back that you are referring to? The above loopback test of the MSDL is the only one that I am aware of.

 

[KCFLHRC]

If this is a TMDI card then I would disable it, force download it, disable it, enable it and then enable the carrier in lD 60. I would use a loopback plug and put it on the cable right at the NIU and see if you get RLS Wrong Mode, you should.

 

[donaldbabcock]

This is not a TMDI card. It is a PRI card residing on a daughter board on the MSDL port 6.

We disconnect the smartjack between the PBX and the T1 (from the lcoal carrier) and we do not get Release Wrong Mode. We get Rls No Response.

 

[KCFLHRC]

First of all a PRI card is never a daughter board on an MSDL card. You can however have a MSDL daughter board on a PRI Card, NT5D12, is that what you have? When you disconnect from the smart jack you will need to put a loop back plug on the cable towards your PBX to see the RLS Wrong Mode.

 

[donaldbabcock]

When disconnecting from the Smartjack we put a Loopback plug inline but do not get the Release Wrong Mode. What we get is Reslease No Response.

 

[bhassell2000]

when the loop back plus is on did you turn down the span and the enable it?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[bhassell2000]

It may take a minute or two before the wrong mode comes up, that tells you your wiring and equipment are good

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[357951258]

Did you check ovl 73 ?

It is mff or crc
Standart is aff
so try crc

Ld 73

REQ prt
TYPE PRI2
FEAT LPTI
LOOP NN
MFF AFF (Default) alternate crc

 

[donaldbabcock]

After a lot of troubleshooting and borrowing an ISDN/PRI tester we identified the problem as a hardware issue in our switch. It was one of the following: bad msdl, bad slot on the PRI gateway, or bad port on the back plane. We tested the backplane fine. We permormed after hours maintenance on the PBX last night and swapped out the questionable MSDL card and the d-channel was able to connect and all channels are now idle.

Thanks for all the assistance.

 

[donaldbabcock]

After a lot of troubleshooting and borrowing an ISDN/PRI tester we identified the problem as a hardware issue in our switch. It was one of the following: bad msdl, bad slot on the PRI gateway, or bad port on the back plane. We tested the backplane fine. We permormed after hours maintenance on the PBX last night and swapped out the questionable MSDL card and the d-channel was able to connect and all channels are now idle.

Thanks for all the assistance.

 

[Firebird Scrambler]

I'm guessing that you have a CS1000e system?. Problems I've had with PRI circuits not working tend to be either the carrier or that the Cabinet isn't synced correctly with the main processor. Have you been into LD 73 and checked the Clocking programming and then go into LD 60 and see if the PRI card is "locked" OK?.

You might even have a faulty clocking card. In the UK, we use ISDN 30 and the PRI cards tend to be a NTBK50AA with daughterboard NTBK51AA. The Clocking card (I think) is a NTAK20.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[donaldbabcock]

Yes, I've been in LD 73 and checked the clocking. We have clocking setup and it was locked to the correct slot. All our PRI's use external clocking so that was checked as well early on during the troubleshooting and was ruled out.