| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
I'm trying to get console Manager configured as part of a demo for the
upcoming POLYCENTER announcement. I just want to set up the system
such that a process sends dummy messages out one tty line (/dev/tty1)
and that is picked up by CM over the other tty line (/dev/tty0).
Currently I'm having several problems with CM....
Configuration:
Console Manager Pre-SSB kit
RISC/ULTRIX V4.2A
DECstation5000/240
Problems:
1. CM can't locate any scan files. (I have a *difficult* time
believing the pre-ssb kit didn't include any sample scan files.)
The config editor doesn't know of any. Where would they be?
2. I can't get a reliable terminal connection from tty00 to tty01
to work with CM! Connects from one serial port to the other
end up with *garbage* on the screen. It only clears up when I
go to the "Options" then "General..." pulldown menus on the
DECterm and set it up to VT100. Once I get the text to make
sense, the stuff that's in the log files is gibberish.
What is wrong ?! This is rather urgent (and important for Console
Manager, too) so any assistance will be gratefully accepted.
/doug
More info:
The 'serviced system' (polyw2) is in the database as attached to /dev/tty00
# ps -d -S polyw2
POLYCENTER Console Manager Summary
polyw2
System ............: polyw2 Enabled: Yes Line status: OK
In use by .........: -
Parent pid ........: 2386 System pid: 2388 Uptime: 0 00:20:51
Connection type....: Direct
Terminal ..........: /dev/tty00 (vt100) secure: N Getty: /etc/getty
std.9600
Log file ..........: /var/cm/logs/polyw2CM_polyw2.LOG
Logging device ....: 24.98% Full, Warning at 80.00%, Archive at 95.00%
Archive location ..: /var/cm/archive/ (24.98% Full)
Last Archive ......: None
Scan Profile ......: None
Lines of data .....: 53 Bytes: 714
Event total .......: ?
Crit: 0 Maj: 0 Min: 0 Warn: 0 Clr: 0 Ind: 0
<portion of /etc/ttys attached>
# more /etc/ttys
# @(#)ttys 4.1 (ULTRIX) 7/2/90
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 off secure # console terminal
tty00 "/etc/getty std.9600" vt100 off nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
<end of /etc/ttys excert>
Thanks in advance, \
doug
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 60.1 | It worked for me!! | OPG::SIMON | Tue Feb 02 1993 09:37 | 105 | |
Hi Doug,
I have just tried to set up the same thing as you wanted on a
DECstation 5000/200 and it worked for me.
Here is what I did after looping tty00 and tty01 ports on back of system
box.
1) Edit /etc/ttys and make sure that the off flag is set for tty00
and tty01
2) kill -1 1 to clear down gettys etc.
3) Edit cm with cm -e
4) create system hard01 (type direct speed 9600 device /dev/tty01)
selected Icon to use and scan profile.
5) Verify database and exit
6) cm_startup.
7) cm -m hard01 worked.
So that bit is ok.
I then turned the /dev/tty00 back on by editing /etc/ttys and kill -1 1.
I then did cm -c hard01 from shell and I got a connection. The looped back
connection gave me the login prompt for the machine.
All well and good.
I then tried to use the csp program I sent you.
1) Turn off /dev/tty00 in /etc/ttys and kill -1 1.
2) Use the csp program to send data to the /dev/tty00 as follows:
o Set the port up (csp does not do this for you)
stty 9600 pass8 > /dev/tty00
o Create the lock file so csp will loop.
touch csp.lk
o Send data with csp.
csp -s 279.script -t tty00 -r 20
This will read blocks of the file 279.script output them to /dev/tty00
and sleep random numbers of seconds up to 20, between data blocks.
I then did cm -m hard01 and I see the blocks of data coming out on the line.
I did not set up any event filters for this experiment.
Here is the ascii dump of the system record for the hard01 system.
ADD_SYSTEM:
NAME: hard01
INFO:
ALIAS:
CONNECTION_TYPE: DIRECT
TERMINAL_DEVICE: /dev/tty01
TERMINAL_SPEED: 9600
SCAN_NAME: UNIX System V
ICON_FILE: DECsystem_5100.ICON
LOG_DATA: Y
LOG_DIRECTORY: /var/cm/logs/
ENABLED: Y
END:
Here is the system status record:
POLYCENTER Console Manager Summary
hard01
System ............: hard01 Enabled: Yes Line status: OK
In use by .........: -
Parent pid ........: 22818 System pid: 22819 Uptime: 0 00:26:48
Connection type....: Direct
Terminal ..........: /dev/tty01 (vt200) secure: N Getty: /etc/getty 8bit.9600
Log file ..........: /var/cm/logs/CM_hard01.LOG
Logging device ....: 45.73% Full, Warning at 80.00%, Archive at 95.00%
Archive location ..: /var/cm/archive/ (84.98% Full)
Last Archive ......: None performed
Scan Profile ......: UNIX System V
Lines of data .....: 1.7K Bytes: 48.3K
Event total .......: 62
Crit: 4 Maj: 23 Min: 34 Warn: 1 Clr: 0 Ind: 0
Hope all this helps. Give me a ring if you still have problems.
Cheers Simon....
| |||||
| 60.2 | I feel much better now... | MCDOUG::MCPHERSON | pre-retinal integration | Tue Feb 02 1993 14:10 | 20 |
Got it! It now works.
Thanks for your p[atience and fine instructions, Simon. Next time you're in
Littleton I'll buy you a drink!
The following things helped:
- Setting the ports to 'off' /etc/ttys
- getting the magic incantation to tell the terminal to strip 8-bit
(in case you can't tell, I'm not what one would consider a 'UNIX
person... ;^)
BTW: I found the scan files soon after I entered the base note. Don't know
what went wrong with the installation... It didn't have that problem with the
EFT2 kit... Oh well.
The script works fine, hopefully I'll have some events and action routines
sending events to MCC before the day is out!
thanks again!
/doug
| |||||