LD17 Meridian-1 Node Type. Frame Slips.

[agpham]

I am getting frame slips on my TIE trunk due to the fact the Nortel is Node Type is User and Tie PBX is NET.

Under NI-2 interface, SIDE prompt is available to set as either USER or NET.

I've tried both DMS100 and 5ESS and that prompt is not available. Is this setting hidden elsewhere?

Here's my LD 60 LCNT dump:

PRI LOOP 4
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -023
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000

 

[senk1s]

check ld73 and make sure the thresholds are not too low ...
and make sure the clock on usr end is said to track the primary reference

if making these changes ...generally good to reset the link

 

[agpham]

It's tracking the primary reference:

REQ prt
TYPE ddb

CC0 1
PREF CC0 1
SREF CC0 FREE RUN

TRSH 00
RALM 3
BIPC 2
LFAC 3
BIPV 3 2
SRTK 5 30
SRNT 15 3
LFAL 17 511
SRIM 1
SRMM 2
ICS

Here's the CEQU:

CEQU
MPED 8D
SUPL 000 004 008 012
016 032 036 040
044 048 064 068
072 P096
XCT 000
CONF 029 030 031 062
094 095

DLOP NUM DCH FRM LCMT YALM T1TE TRSH
TRK 03 24 D3 AMI DG2 0 00
PRI 01 23 ESF B8S FDL 0 00
02 24 ESF B8S FDL 0 00
04 23 ESF B8S FDL 0 00
MISP


I'm at a lost here, I'm getting frame slips and believe the solution is to make the Nortel the network side (NET) and the Cisco the CPE side (USER) but can't find where to configure it.

 

[wdhb]

this is programmed in your d-ch data

ADAN DCH 12
CTYP MSDL
DNUM 11
PORT 3
DES Waitakere_Lp_19
USR PRI
DCHL 19
OTBF 16
PARM RS422 DTE
DRAT 64KC
CLOK EXT
NASA YES
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 25
RCAP ND2 NCT MSDL
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7

 

[Avaya911PLM]

OK first off, USR and NET on the DCH have nothing to do with clocking. This parameter controls who is the master or slave DCH controller. This has to do with Information Element formating, and who is in charge in the case of a messaging conflict.

The design rule most people use is that the NET side of the DCH should be th eone that is more towards the 'core' of the network. If the Cisco is more in the center from a topology standpoint, then it should be the NET. If the M1 is more inthe middle, and the Cisco sits behind it, then the Cisco should be the USR side.

Now for CLOCKING

The Meridian applies the clocking bits to ALL T1 interfaces. It is up to the far end to decide if it wants to use those or not. In LD 73 you define which spans your clock controller should clock to, again assuming that clocking is there.

Again, you need to be careful when you design network clocking. You want to try to point clocking back to a common source, or at least to a common Stratum. If the Cisco is looking one way, and the M1 is lookng the other way, then the span between them is likely to slip if the Nortel's clock source differs too much from the one Cisco is using.


--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[johnpoole]

one side must be user and one side must be net..otherwise it will not come up. didn't see enough config to answer all your questions. a threshold value tells the switch at what alarm count to take the t out of service and does not add or subtract from the counters. if my switch is net the far end needs to clock off of me, i then clock off or my ld carrier. if the far end is clocking off of a remote switch, local pri, or worse freerun, i will get slips. slips are most common when a network configration has more then one "master clock" ..

john poole
bellsouth business
columbia,sc

 

[agpham]

I found the problem this morning, the Cisco's clock was free running and I changed it to point to the Nortel. We are now synch'ed and no frame slips. Thanks everyone!