Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Strange TTY Output

Status
Not open for further replies.

NY105

Technical User
Jul 6, 2011
41
US
Hello All,

I have allot of "000000" output to my TTY's at random. This seems to be more prevelant as the day goes on as calls increase. I already disconnected all my TTY's one at a time to see if was a TTY issue and it's not. I suspect something with CNi or 3PE since in LD 135 it has OOS messages and 0 = CP local bus parity threshold exceeded. OK, if I am on the right track, what does that mean and where do I go to fix it or can I?
 
I checked and no Traffic reports are selected or turned on for any TTY's
 
pick one tty you will monitor and remove OSN from the user programming if if it's there.(if you don't need 911 notification on the TTY)

On-Site Notification

but if you have errors if you stat Health, then you might be on the right track.



__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius
 
Thanks, but what am I looking for as far as health. I know the higher the health number the better. I stat the health and everything looks good. I do however see a CNIP 0 9 1 disabled and there is no pysical port for it and it will not enable because of no port. This may be the problem, but how to do I get rid of it to see.
 
well if you have a Single group system, you should normally see

CNIP 0 9 1 (out of service)
and
CNIP 1 9 1 (out of service)

as this would represent group 1 (and a single group system has only group 0)


as to the "0" you are getting, it could be the device you are on (laptop, or modem... etc) you said that you are getting the "0" on every TTY port, did you use the same laptop to test each port?

also, are you using a serial to usb converter? some low end ones cause strange characters to show up.

if you are connected to the CPSI ports off the cpu, I don't think anything on the system would affect your serial connection other than the cable you are using and the terminating device (ie. laptop or dumb terminal)

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius
 
Yes, I agree with your assessment of the CNIP after doing some reading. The TTY I am using is on computer with serial connection using Putty. This connection is also going over a Cat 5 cable about 25 Ft from a TTY Paddelboard. What is weird is that I did disconnect this cable from the PaddleBoard and still have the same issue on the other TTY's. I also disconected every other TTY one at a time and the same thing. I only have three TTY connections. one is my terminal of Cat 5 serial, the other is to the Web Server in the Switch room over a serial connection and the CDR output to MicroCall. I am at a loss on this one. It also seems that when calls are generated I get more of these darn zeros.

 
well, if all the problem connections are on the same paddle board, it might be the paddle board.

but i would test right off the active CPU tty (CPSI) either J25 or J21 (or if CPPIV processor, serial off the face plate) that way you are not using any paddle board and just using the serial port of the processor.

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius
 
Sorry for not getting back for awhile, have been on leave. Multi-user is turned on and there is only one connection to the paddle board. The rest are connected to a QSDI card.
 
Is the card a qpc841? If so there was a vintage issue with the new releases.
 
The c is the bad vintage. We changed ours to d. Having said that I kept one of my c cards and have since had to use it in order to get some ttys working because the d went bad. I did put a d back in after it came in but I didn't have one at the time. The c worked in the meantime. No troubles.
 
I removed the QSDI card and still have the same problem. I am at a loss.
 
Try
Terminal type: VT100 9600 Baud 7 odd 1 Flow none
(or whatever the bps is for the port)

or maybe the length of the cable is too long?

show us a printout of one of you TTYs from ADAN also

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius
 
Here is a screen capture of the problem.

TTY 08 SCH MTC BUG OSN 11:01
OVL111 BKGD 44
>
AUD000
000000000000000000000000000000
DTC001

000000
DTC001


DTC001

000000000000
DTC001


TIM429 12:00 13/4/2012 CPU 0

AUD000
000000
DTC001

000000000000
DTC001

000000000000
DTC001

000000
DTC001

000000
TIM429 13:00 13/4/2012 CPU 0
000000
AUD000
000000000000
DTC001

000000000000000000
TIM429 13:26 13/4/2012 CPU 0
 
NY105, did this start when you changed from the DCH daughter boards to the MSDL card?(from below)

****************************************************

NY105 (TechnicalUser)
23 Mar 12 13:28
If anyone is interested in the fix here goes. The DCH daughterbaords on the NT5D12's where bad. I removed them and installed an external MSDL card for my DCH's and when I turned them back on evertything was working like it should. No more hardware faults on either DCH or MSDL. The only thing left I have to figure out is why am I getting "000000" on all my TTY's. Last mystery to solve on this one.
****************************************************

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius
 
No, this was going on before that. At the time I thought the DCH's where also causing this problem. Now my DCH's are good and I am left with this problem. I really do beleive it has something to with calls though. Thru-out the night it runs clean because noone is at work, but as soon as the day starts I see these zeros. So, I am convinced it has something to with calls being generated somewhere causing this problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top