Head scratching....gig or Poole please give me your thoughts

[libram11]

Ok so here's the idea , need more try ports on a 61. Here's the setup.
Version 25.15
Option 61
Msdl 8 group 0
Msdl 9 group 0
Msdl 10 group 0
Sdi cards as follows, 4 port qsdi paddle, msdl,msdl,
Tty 0 system monitor paddle port 0
Tty 1 seb and maint term paddle port 1
Tty 4 cdr (keeps blowing) paddle port 2(to be removed)
Tty 5 not assigned in cdb paddle port 3
Msdl 8-0 dch
Msdl 8-1 dch
Msdl 8-2 mm aml
Msdl 8-3 tty 8 monitoring device
Msdl 9-0 dch
Msdl 9-1 dch
Msdl 9-2
J21 cores 0-1 tty 14-15
Msdl 9-3 dch
So here is the thing, the 3rd mddl is set to ten, when I go to add a tty of any unused number 2,3,6,7,9,10,11,12,13 and enter type msdl it only comes up with the dnum of the tty I'm trying to add and port 0. Now here's the kicker, if I add tty 10 it puts it on dnum 10-0 and it works, but if I try and add try 11 which I would want on 10-1 it still shows dnum 11-0.
What am I not seeing here? No other Sdi,msdl,or qsdi in system.

 

[Telephonist]

Only port 0 on an MSDL card can be used for TTY.

 

[libram11]

That can't be true because I've got a tty on 8-3

 

[Firebird Scrambler]

I've found some old notes on MSDL configuration and some of this might be related.

There are pack addressing conflicts when MSDL packs are configured in group 6 along with other network packs in specific slots. The symptoms include the MSDL pack resetting when an NT8D17 (XCT) pack is disabled or enabled.

An example configuration where this occurs is when an MSDL pack is configured in Group 6 with the TTY or DCH parameters set to 0,1,or 2 and an XCT pack configured in loop 192. There are other configuration combinations in Group 6 that also show this symptom.

MSDL Card # Switch setting Conflicts Network card in loop #
0,1,2,3 192
4,5,6,7 193
8,9,10,11 194
12,13,14,15 195

Currently MSDL is not configured beyond unit 15 in S/W.

Recommended Action:
The work around is to move the MSDL pack to any other network group 0,1,2,3,4,5, or 7. This issue cannot be resolved by software patch – an MSDL pack change is required. This pack will be released as NT6D80AC.

HW Fix Completion Date:
The problem will be resolved by a change to the MSDL pack that will be released as an NT6D80AC. Currently the date for this hardware update is under review. A further Product Bulletin will be issued on the availability of NT6D80AC.

Another thing to be aware of is that you will run into problems if you have all 16 (0-15) TTY's and DCH configured. I had an Option 81c at release 04.50w and it took me a while to try and figure why I couldn't get any output from one of the TTY ports. I'm not sure if I was actually able to program it in but I eventually found the cause was due to having too many ports in use and I deleted the history file programming which enabled my new TTY port.



Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support

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

 

[libram11]

Appreciate firebird but all three of these msdls are group 0, and I still have tty 2,3,6,7,9,11,12, and 13 free. I don't see the problem I'm having in that ntp bulletin.

 

[StanleySteamer]

Suggest you post the ADAN print from LD 22 for us to see the whole picture.
Not sure what device is connected to TTY 8 but, as Telephonist says, you can have only one asynchronous serial device on an MSDL card.

 

[phones1]

don't know why but does this have anything to do with extended addressing? Im sure I had something like this years ago & that was the answer given by somebody who knew far more than me said!!!!

Remember if it doesn't work hit it harder

Scott UK

 

[libram11]

Here are the prints, also what doc says only one tty per MSDL I dont think ive ever heard that before, not saying its not true just where is it at?
ld 48
LNK000
.stat msdl
GROUP 0 MSDL 8: ENBL
GROUP 0 MSDL 9: ENBL
GROUP 0 MSDL 10: ENBL
.*
.*
.*
.*
OVL000
>ld 37
IOD000
.stat

TTY 0 : ENBL DES: SYSMONITOR
TTY 1 : ENBL DES: SEB
TTY 5 : ENBL DES: MDR2000
TTY 8 : ENBL DES: MSAS
TTY 10 : DSBL DES: IPBufferPass
TTY 14 : ENBL DES: TTY_CORE
TTY 15 : ENBL DES: MODEM_CORE
.****
OVL000
>ld 22
PT2000

REQ prt
TYPE adan

ADAN HIST
SIZE 30000
USER MTC BUG
ADAN TTY 0
CTYP QSDI
DNUM 0
DES SYSMONITOR
FLOW NO
USER MTC
XSM YES
TTYLOG 0
BANR YES
ADAN TTY 1
CTYP QSDI
DNUM 1
DES SEB
FLOW NO
USER MTC SCH BUG
XSM NO
TTYLOG 0
BANR YES
ADAN TTY 5
CTYP QSDI
DNUM 5
DES MDR2000
FLOW NO
USER CTY
XSM NO
ADAN TTY 8
CTYP MSDL
DNUM 8
PORT 0
DES MSAS
BPS 9600
PARM RS232 DTE
BITL 8
STOP 1
PARY NONE
FUNC
USER MTC SCH BUG
XSM NO
TTYLOG 937
BANR YES
ADAN TTY 10
CTYP MSDL
DNUM 10
PORT 0
DES IPBufferPass
BPS 9600
PARM RS232 DTE
BITL 8
STOP 1
PARY NONE
FUNC
USER MTC SCH BUG
XSM NO
TTYLOG 0
BANR YES
ADAN TTY 14
CTYP CPSI



PAGE 001

DNUM 14
PORT 0
DES TTY_CORE
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH
XSM NO
TTYLOG 0
BANR YES
ADAN TTY 15
CTYP CPSI
DNUM 15
PORT 1
DES MODEM_CORE
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH
XSM NO
TTYLOG 0
BANR YES
ADAN AML 8
CTYP MSDL
DNUM 8
PORT 1
DES mermail
BPS 9600
PARM RS232 DCE
IADR 003
RADR 001
T1 10
T2 010
N1 128
N2 08
K 7
ADAN DCH 32
CTYP MSDL
DNUM 8
PORT 2
DES BELLSOUTHPRI
USR PRI
DCHL 8
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE ATT
SIDE USR
CNEG 1
RLS ID 23
RCAP COLP
T310 120
T200 3



PAGE 002

T203 10
N200 3
N201 260
K 7
ADAN DCH 33
CTYP MSDL
DNUM 9
PORT 3
DES bellsouthpri2
USR PRI
DCHL 23
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE ATT
SIDE USR
CNEG 1
RLS ID 23
RCAP COLP
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
ADAN DCH 35
CTYP MSDL
DNUM 9
PORT 0
DES Allen_Tie_Lines
USR PRI
DCHL 9
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 23
RCAP ND2 MSDL
T200 3
T203 10
N200 3
N201 260
K 7
ADAN DCH 37
CTYP MSDL
DNUM 9
PORT 1
DES Dixontielines
USR PRI
DCHL 11
OTBF 32
PARM RS422 DTE
DRAT 64KC



PAGE 003

CLOK EXT
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 23
RCAP ND2 MSDL
T200 3
T203 10
N200 3
N201 260
K 7
ADAN DCH 38
CTYP MSDL
DNUM 9
PORT 2
DES mdctielines
USR PRI
DCHL 22
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 23
RCAP ND2 MSDL
T200 3
T203 10
N200 3
N201 260
K 7
ADAN DCH 40
CTYP MSDL
DNUM 8
PORT 3
DES SPRINT_DID
USR PRI
DCHL 10
OTBF 127
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC D100
SIDE USR
CNEG 1
RLS ID 36
RCAP ND2
T200 3
T203 10
N200 3
N201 260
K 7

REQ

 

[hawks]

Yes only Port 0 can be used for TTY, even if you look at your TTY 8 it is on Port 0 of DNUM 8. The following is from "Circuit Card Description and Installation"

The MSDL card provides one monitor port and four programmable serial ports that can be configured for the following various interfaces and combinations of interfaces:
• synchronous ports 0–3
• asynchronous port 0

Hope this helps

 

[libram11]

how have I never run into this before lol. Thanks guys for the input. I'll do some rearranging.