TMDI Issues

[CommoGuy101]

Hello All,
I am having some issues enabling a TMDI card.
I have built the DLOP in the CEQU
Built the DCH
Created the Route
Add the TIE members
Clocking is set up

stat TMDI and I see:
.stat tmdi
TMDI 000 0 1 ENBL
TMDI 000 0 2 ENBL
TMDI 004 1 4 MAN DSBL

I have tried to enl TMDI 4 1 1 FDL
At that point I don't see any .......
or an OK
Just sits there and does nothing.
I am able to **** out but it never does the loading
I have tried various TMDI cards and get the same results.
Thought about doing a INI in the morning.
Am I missing something?
Any thoughts.

Thank you,
CommoGuy101

 

[Firebird Scrambler]

This record shows how to remove it

Problem
Unable to remove the entry against DLOP in LD 17 CEQU_DATA

Answer
Difficulty in using slot 4 on Succession 1000S for a new software build

The only reference to slot 4 was in the CEQU_DATA (LD 17) as below
* DLOP NUM DCH FRM TMDI LCMT YALM T1TE TRSH
* PRI 04 24 ESF YES B8S FDL 0 00

Trying to OUT the DLOP entry gave SCH5589 as below

*>LD 17
*CFN000
*MEM AVAIL: (U/P): 572738 USED U P: 543942 62967 TOT: 1179647
*SCH5066
*
*DCH AVAIL: 76 USED: 4 TOT: 80
*TMDI D-CHANNELS AVAIL: 64 USED: 0 TOT: 64
*AML AVAIL: 14 USED: 2 TOT: 16
*REQ CHG
*TYPE CEQU
*DDCS
*TDS
*CONF
*DTDT
*DLOP X04
*
*SCH5589

Doing a STAT TDMI in LD 48 gave the following
*LNK000
*.STAT TMDI 4
*TMDI 4: MAN DSBL
* DITI 4 DIS PORT 0

To cease the DLOP entry - manually disable the TDMI pack for 4 and the in LD17 remove the 04 entry against DLOP

###############################################

Problem
CS1000: MSDL enable fails at release 7.50

Answer
From time to time complaints are coming in from sites that when they try to enable a TMDI or a MSDL that the enable command just hangs and will not do anything.
During lab testing and code review it was found that RESET_WAIT_UNTIL is loaded from 2 different sources depending on the command issued. Depending on the current TOD2SEC and RTCLOCK values RESET_WAIT_UNTIL may cause an extremely long wait when trying to enable after a command that loads RESET_WAIT_UNTIL with the opposite type of timestamp from what is expected. For example, the SLFT command loads the RESET_WAIT_UNTIL with TOD2SEC, but ENL FDL command expects RESET_WAIT_UNTIL to be loaded with RTCLOCK.

The problem occurs when TOD2SEC is greater than RTCLOCK, and you run the SLFT command, then try to ENL FDL the TMDI or MSDL, the RESET_WAIT_UNTIL will be such that the wait time is incredibly long before the download can start.
Currently the problem may be worked around by using the RST command since it sets RESET_WAIT_UNTIL with RTCLOCK.

However there is one case where attempting the download after the RST command sets RESET_WAIT_UNTIL with TOD2SEC again causing it to hang again.

SETUP and ACTIONS performed to cause the problem:
HARDWARE and DATA SETUP:
CS1K with MSDL and TMDI cards

ACTIONS:
1. At any time disable a MSDL or TMDI, then do a SLFT, then do an ENL FDL.

EXPECTED RESULTS:
1. Enable command starts promptly with the download

ACTUAL RESULTS:
1. At times the download never starts.
Example: On site this occurred when RTCLOCK was C487E783 and RESET_WAIT_UNTIL and TOD2SEC was 000C9886.

Notes
The patch should be used along with MGC patch MPLR31779 (included in MGCCCD03)

The problem TMDI card & DCH should be removed and recreated again after patch installation

Due to the method of operation required to create a patch back from the next release, this patch will introduce extra delay. This is normal for this patch and will be corrected in future releases by the actual fix.

After a few seconds the patch will output a message indicating that the longest wait period is started. The message is as follows and will occur several times only the first time should have the full 40 second wait time.

INFO1807 PLEASE WAIT UP TO 40 SECONDS FOR CARD RESPONSE

I think patch mplr32057 rls 7.50Q was issued to fix it.








Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.myfreesites.net

linkedin

 

[CommoGuy101]

I originally built this on 0 1 5 and was getting the same issues.
So I moved it to an open slot 4 1 4, after outing everything and then re-adding it all.
I still get the same results.

Are there specific slots I am to use for TMDI?

 

[KCFLHRC]

the command you need to use is RST TMDI X

 

[CommoGuy101]

When I do the RST TMDI 4 1 4 I do get the OK
However if after that I try to ENL TMDI 4 1 4 FDL it just sits there.
After it sits there for so long, I am able to **** out of the load but nothing has taken.
I have let it timeout as well.
Still don't get a n active TMDI


.stat tmdi
TMDI 000 0 1 ENBL
TMDI 000 0 2 ENBL
TMDI 004 1 4 MAN DSBL

.stat dch
DCH 004 : OPER EST ACTV AUTO DES : WELNES
DCH 006 : OPER EST ACTV AUTO DES : Public_ISDN
DCH 010 : OPER EST ACTV AUTO DES : NRS
DCH 050 : DSBL RST AUTO DES : CISCO

 

[KCFLHRC]

After you do the RST command it takes a long time no initiate the self test and complete, just let it sit after the command, hopefully it completes

 

[KCFLHRC]

What kind of cabinet is this? Chassis, Cabinet etc

 

[CommoGuy101]

After the RST command, I have done the slft tmdi 4 1 4 and all passes

SELFTESTS PASSED
CARDID= NTRB21AA

How can I determine what type of cabinet, chassis?

 

[CommoGuy101]

REQ iss

VERSION 4021

System type is - Communication Server 1000E/CP PM
CP PM - Pentium M 1.4 GHz

IPMGs Registered: 3
IPMGs Unregistered: 0
IPMGs Configured/unregistered: 0

RELEASE 7
ISSUE 00 Q +
IDLE_SET_DISPLAY Lodi Community Hospital

IPMG TYPE CSP/SW MSP APP FPGA BOOT DBL1 DBL2

0 0 MGC BD05 AB02 BA15 AA22 BA15 DSP1AB07 DSP2AB07
0 1 MGC BD05 AB02 BA15 AA22 BA15 DSP1AB07 DSP2AB07
4 1 MGC BD05 AB02 BA15 AA22 BA15 DSP1AB07 DSP2AB07

 

[KCFLHRC]

If you physically look at the system are the cards vertical or horizontal? Vertical it's a cabinet horizontal it's a chassis. I'm assuming this is the only TMDI in 4 1 and if so you will need a clock controller also

 

[Wanebo]

What version of software do you have?

Ever since 7.6 came out we had to do the full rst tmdi and slft tmdi before we could force download (fdl) and successfully enable (enl) any of the TMDI's on any of our CS1K's. Something version wise apparently changed and skipping either step just wouldn't work anymore.

 

[CommoGuy101]

Release 7 is what I see
I have done in this order
RST TMDI 4 1 1
SLFT TMDI 4 1 1 (test pass)
ENL TMDI 4 1 1 FDL

Hate doing an INI and not sure that will even solve it.

 

[CommoGuy101]

Sorry
That is 4 1 4 for the TMDI

 

[CommoGuy101]

After I did n INI, I was able to successfully FDL the TMDI card.
I can enable the loop and Dchannel and perform a loop back
Now I am at the point where I think I need to do the clocking.
I have placed this TMDI in a carrier that no other PRI is installed or a clocking source
I don't have a CC daughter board on the TMDI card.
Do I need to get one to allow it to work in that carrier?

Also if I can free up a slot in 0 0 then I can just move everything to that carrier, would that eliminate me needing a CC
I already have 2 in that carrier.
What would I need to do after moving everything to that carrier to allow clocking?


Thank you
CommoGuy101

 

[KCFLHRC]

You need a clock controller in each media gateway supporting a T-1 or PRI. And yes, you could move it to 0 0 and not need the CC since the clocking is already established in that media gateway, nothing to do for that clocking. But if you leave it in 4 1 then yes you need the CC

 

[CommoGuy101]

Thank you all for your assistance.
I moved everything over to the carrier with clocking and all is fully operational.