would like to verify FDL on MSDL Card for TTY

[Telecomguy333]

Lost access to TTY port "0" on 4-port MSDL card in CS1000M after a Sysload.

We were running on Core 1 prior to the Sysload, now running on Core 0. After PBX booted up we lost OVL access on the TTY port used for remote access and alarms notifications . We're receiving alarm notifications on the TTY port, just unable to connect for switch OVL access. We're using a Teleboss850 for remote administration and alarms.

Have tried FDL in LD 37, but did not see dots ".............." I was expecting (years since I've performed an FDL), but received the following output.


******************************************
>OVL021 BKGD
>
>SDL100 BUSY
>
>OVL021 BKGD
>
>OVL100 BUSY
>
>SDL000 SDI )MSDL 7), Version 51, Maint Mode
>
>Downloading DCH Reason:Forced
>
>SDL000 DCH (MSDL 7), Version 72, Maint Mode
>
>OK
********************************************

So TTY is enabled but still have no access to OVL, but receiving alarms from the TTY port. The TTY is configured for 9600, 8,N,1, RS232 DCE, w/Flow Control. The DIP switches on the MSDL Card for Port 0 are OFF/OFF, default values for port 0. Just odd the remote access via the TTY worked prior to the Sysload. Does anyone know if there are known problems with certain MSDL card versions failing after Sysloads?


-Telecomguy333

 

[phones1]

Ok a couple of suggestions from memory. I thought FDL for a msdl was in LD 48 & I didn't think you had to do it for a big switch (I maybe wrong), TTY0 I thought was located directly on the CP card so if you've got you device directly connected to CP1 port 0 (comm1 I think) you won't be able to get to it as this as this processor (CORE 1) is now in STANDBY mode, I think youi may have to do one of two things. 1, move the connection to the current active core or. 2, Force a swap of the cores so that CORE 1 is the active side.

Still I maybe wrong as you post didn't have all the info

Remember if it doesn't work hit it harder

Scott UK

 

[bhassell2000]

Try the FDL in LD96 06 LD48 ENL MSDL 7 FDL

Thanks,

Buddy

Linked in Profile

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

 

[Telecomguy333]

We have maintenance terminals connected to CORE for local administration. We have this TTY port configured as DNUM 7, Network Group 2 for remote administration an monitoring. The TTY was once configured for vendor hosted Site Event Buffer box that I re-used for Teleboss 850 which has worked for the past 5 years.

Also add that the CS1000 PBX has not been INI'd or Sysloaded in past 5 years. We performed the Sysload to resolve issues with Network Loops auto disabling overnight.

I read in NTPs that FDL could be performed in LD37, LD48 and LD96. Given there is no D-Ch associated to the TTY I performed the from LD37. I'll try an FDL from LD48.

 

[RickyPone]

Looks like it's downloading the database as a dch. I've never had to download for an SDI device like a teleboss. Have you pulled the card to check all of the switches? What is it an nt8d60?

 

[KCFLHRC]

Those TTY's on Port 0 of the MSDL cards are a little flakey sometimes. I would disable the tty and enable if you haven't. If you are receiving alarms over that port I'm guessing the disable/enable may fix it. But give it a chance to respond to the commands, it acts differently than the Core TTY's

 

[KCFLHRC]

Are there functioning D-Channels on that card also?

 

[RickyPone]

I would put a laptop on it and send a test to it from another working tty. Just make sure that the baud/parity/bits is set correctly. If it's a qsdi card and depending on your release I think it has to be a D vintage. If it's an msdl pack I suspect your just seeing the dch port trying to download. But you're correct thinking you should see rows of dots while it it's downloading.

 

[Telecomguy333]

So full disclosure there is a D-Channel configured on Port 2 of the MSDL card but is no longer in use and is kept disabled.

The MSDL card is a NT6D80AB Rlse01, I've disabled it and re-seated it, performed FDL in LD37. I was out of office yesterday but picked up a DB9 null modem to connect my laptop to Port 0 on the MSDL card to see if I get the character response for testing output.

DIP Switch settings on MSDL card for port "0" are OFF/OFF for DCE/DTE and the round dial TENS/ONES is set to 0/7 for DNUM 7.

Will report back after I'm able to connect my laptop to the MSDL port.

 

[Telecomguy333]

After hooking laptop to MSDL Port 0 (TTY_7) I received "IOD0333 7" across the maintenance terminal which translates to "Port is now operational"

I received the following output on maintenance terminal but no characters/output on my laptop connected to MSDL Port 0, TTY_7.

>SDI: 7 Entering Test State
>SDI: 7 Ring Transmit Buffer Test Passed
>SDI: 7 Expedited Transmit Buffer Passed
>SDI: 7 Screen Test Passed (as mentioned above, no characters on the laptop screen while connected to MSDL Port 0, TTY_7.

I'm at a loss, I have another MSDL card ordered and should have it next week and will update the thread.

I appreciate everyone's input and help troubleshooting this.

Have a Great Weekend!!

 

[RickyPone]

From a good port enter tty x to test the suspect port.

 

[Telecomguy333]

RickyPone - thanks for feedback, tried 'output test' from a working maintenance terminal but did not get anything on my laptop connected to the bad TTY 07 PORT 2. I should have a replacement card tomorrow or Wed.