A quick example on setting up print queues over protocol translation.

Normally a VMS host will spool the print queue to an LTA device. The LTA device is created using latcp on the VMS host ie;

LATCP> create port lta203
LATCP> set port lta203:/applic/node=africa/service=africa_remote/port=1
LATCP>

There are several ways to reference the target LAT terminal server.

Normally the nodename and portname is sufficient for a DEC terminal server. But when using a Cisco as a terminal server, or for protocol translation, a service name must also be used in the LTA definition.

It is possible to connect to a cisco using the node and port name only, but the port name referenced, must physically exist on the cisco. So on a 2503 you could reference port 1 , because there is an aux port, but not port 2 or 3. On a 2509 or 2511, there are multiple ports, so they can be referenced.

I then create a printer queue using default forms

BRUVAX>init/queue/start/on=lta203: conrad_printer
BRUVAX>show queue conrad_printer/all/full
Terminal queue CONRAD_PRINTER, idle, on BRUVAX::LTA203:, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) Lowercase /OWNER=[SYSTEM] 
  /PROTECTION=(S:M,O:D,G:R,W:S)/PROCESSOR=(LATSYM)
BRUVAX>

I then need to config the local cisco router to pick up the lat connections and convert them to tcp packets. I have it intercept lat solicits looking for the node africa and the service africa_remote. In my LTA device I also specify port 1, this is OK only because my test machine actually has a port 1 , if it did not, the lat connections would not be picked up.

Africa will take the lat packets, extract the data, then send the data in a tcp packet to the host 141.245.44.2 port 4001 ......

africa

Current configuration:
!
version 11.0
!
hostname africa
!
interface Loopback0
 ip address 141.245.43.1 255.255.255.0
!
interface Ethernet0
 ip address 141.245.42.1 255.255.255.0 secondary
 ip address 171.68.143.80 255.255.255.0
 media-type 10BaseT
 lat enabled
 no mop enabled
!
interface Serial0
 no ip address
 no fair-queue
!
interface Serial1
 ip address 141.245.41.2 255.255.255.0
 bandwidth 64
!
!
ip host rund 171.68.143.249
ip route 141.245.44.0 255.255.255.0 141.245.41.1 10
!
!
translate lat AFRICA_REMOTE node AFRICA tcp 141.245.44.2 port 4001
!         
line con 0
 exec-timeout 0 0
line aux 0
 login local
 transport input lat
line vty 0 3
 login
line vty 4
 login
 rotary 1
!
end
 

then at the end of the serial link I have mellow receiving the tcp connections, and if mellow sees a tcp syn packet destined for 141.245.44.2 port 4001 , it will fork a translate process to strip the user data, build a LAT packet and send it to the LAT node CARL, looking for the service PRINTER_1 , and try to bind to the async port 1 , on CARL. If we can complete the whole link, then the print will spool. No reverse mapping is required for this.

mellow#writ t 
Building configuration...
 
Current configuration:
!
version 11.0
!
hostname mellow
!
!
interface Loopback0
 ip address 141.245.44.1 255.255.255.0
!
interface Ethernet0
 ip address 171.68.143.58 255.255.255.0
 lat enabled
!
interface Serial0
 ip address 141.245.41.1 255.255.255.0
 bandwidth 64
 no fair-queue
 clockrate 64000
!
translate tcp 141.245.44.2 port 4001 stream lat PRINTER_1 port 1 node CARL
!
line con 0
line aux 0
 transport input lat
line vty 0 4
 login
!
end
 
mellow#