eden@fallout.uucp (Robert Eden) (04/17/91)
I'm been having trouble using a CISCO CPT (ver 8.2.3) to connect a
VAX print queue (LAT) to a printer connected to an X25 PAD. These
are the 3 ways I've found to do it and their associated problems.
All setups use the standard VMS configuration on a LTA line.
Case 1: connect to service myprinter
on the CPT: X29 PROFILE noecho 2:0
TRANSLATE LAT myprinter X25 99999 profile noecho quiet max-users 1
Case 2: connect to port 101
on the CPT: X25 HOST myprinter 99999
line vty 99
no exec
autohost myprinter
Case 3: connect to port 101
on the CPT: X29 PROFILE noecho 2:0
TRANSLATE LAT myprinter X25 99999 profile noecho quiet max-users 1
line VTY 99
no exec
autohost myprinter
Case 1 doesn't work because it can't handle queued requests. The CPT
returns a INSUFFICIENT RESOURCES error instead of queueing the request.
You can't use the LATSYM symbiont or share the print queue between nodes.
It would work if you wanted to dedicate a printer to a single node.
Case 2 eats up ETHERNET bandwidth by echoing all TEXT back to the VAX.
The X29 profile appears to be the only way to change Cisco's default
X.3 parameters from a autoconnected session.
Case 3 properly queues LAT connect requests to VTY 99 (/NODE=xxx/PORT=101)
doesn't echo the text back to the VAX (uses the X.3 profile)
but, it eats up virtual terminal space by causing a second connection.
Is there a cleaner way???? (like a TRANSLATE QUEUEING option?)
--
-------------------------------------------------------------------------
Robert Eden 817-897-0491 EDEN@fallout.uucp
Commanche Peak Steam Electric Station Glen Rose, TX
^^^^^^^^^^^^^^^^^^^^^ politicese for a nuke plant
-------------------------------------------------------------------------