The basic steps to replace a DECserver with a Cisco 2509, 2511, etc..
The VAX system can have applications or printer queueus that wish to talk to remote Lat devices, so we define a "port" or "LTA device" on the VAX system to point at the remote Lat destination.
ALPHIE>mc latcp LATCP> create port lta300 LATCP> set port lta300/node=munch/port=5 LATCP> exit ALPHIE>mc latcp show port lta300 Local Port Name: _LTA300: Local Port Type: Application (Queued) Local Port State: Inactive Connected Link: Target Port Name: 5 Actual Port Name: Target Node Name: MUNCH Actual Node Name: Target Service Name: Actual Service Name:
The Cisco commserver munch, has *nothing* defined. It simply runs an image that contains Lat.
munch#show ver
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JS-L), Version 11.2(10a)P, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Wed 03-Dec-97 00:03 by ccai
Image text-base: 0x03040A00, data-base: 0x00001000
munch#show run
Building configuration...
Current configuration:
!
version 11.2
service timestamps debug datetime msec
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname munch
!
!
interface Ethernet0
ip address 172.17.242.134 255.255.248.0
!
!
line con 0
exec-timeout 0 0
line 2 5
transport input all
line vty 0 4
password stuff
login
munch#
If I now ask the Application to connect to that port, it then signals the Lat software to make a connection to the remote Lat device ...
ALPHIE> ALPHIE>set h/dte lta300: %REM-I-TOQUIT, connection established Press Ctrl/\ to quit, Ctrl/@ for command mode
If I check the port status on the Vax system
ALPHIE>mc latcp show port lta300 Local Port Name: _LTA300: Local Port Type: Application (Queued) Local Port State: Active Connected Link: LAT$LINK Target Port Name: 3 Actual Port Name: 3 Target Node Name: MUNCH Actual Node Name: MUNCH Target Service Name: Actual Service Name:
It is active and in use
And on the Commserver
munch#who
Line User Host(s) Idle Location
* 0 con 0 idle 00:25:24
3 tty 3 idle 00:00:58 ALPHIE
munch#show lat sess
tty3, virtual tty from host ALPHIE
Session data:
Name , Remote Id 1, Local Id 1
Remote credits 63, Local credits 0, Advertised Credits 4
Flags: none
Max Data Slot 254, Max Attn Slot 1, Stop Reason 0
Remote Node data:
Node "ALPHIE", usage 1, Interface Ethernet0, Address aa00.0400.1728
Ident: @sys$manager:announce.txt
Timer 309, sequence 240, changes 247, flags 0x0, protocol 5.2
Facility 0, Product code 3, Product version 2
Recv 94/66/306, Xmit 66/36/230, 0 Dups, 0 ReXmit
Bad messages: 0, Bad slots: 0, Solicits accepted: 5
Solicits rejected: 1, Multiple nodes: 0
Groups: 0
Service classes: 1
and the debug shows us
munch#debug lat event LAT event debugging is on munch# *Mar 1 22:52:05.070: LAT: Host Initiated connection from ALPHIE to :3, sc=1 *Mar 1 22:52:05.078: LAT3: created new inbound session *Mar 1 22:52:05.094: LAT3: Host-initiated connection complete *Mar 1 22:52:05.098: LAT3: DataB: +FlowIn +FlowOut Parity 2A Mode Interactive(0) Speed *9600/*9600 *Mar 1 22:52:05.102: LAT3: DataB ignored munch#
Now we close the connection when complete.
munch# *Mar 1 22:52:14.278: LAT3: Unknown signal 0x4 *Mar 1 22:52:14.278: LAT3: Session stopped, reason = User requested disconnect (1)
However, if there is a problem with the port name or node name being
requested we get an error message on the Vax application....
Note the change in port name .
ALPHIE>mc latcp show port lta300 Local Port Name: _LTA300: Local Port Type: Application (Queued) Local Port State: Inactive Connected Link: Target Port Name: PORT_3 Actual Port Name: Target Node Name: MUNCH Actual Node Name: Target Service Name: Actual Service Name: ALPHIE>set h/dte lta300: %REM-I-TOQUIT, connection established Press Ctrl/\ to quit, Ctrl/@ for command mode %REM-E-PORTRXERR, port receive error -SYSTEM-F-HANGUP, data set hang-up %REM-S-END, control returned to node ALPHIE %SYSTEM-F-HANGUP, data set hang-up ALPHIE> munch# *Mar 1 22:53:32.614: LAT: Host Initiated connection from ALPHIE to :PORT_3, sc=1
Notice the wrong port name.
When having problems talking to the async interface, line status is not
normally an issue. We will queue up Lat connections.
munch#show line 3
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns
3 TTY 9600/9600 - - - - - 4 0 0/0
Line 3, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600, no parity, 2 stopbits, 8 databits
Status: Ready
Capabilities: none
Modem state: Ready
Special Chars: Escape Hold Stop Start Disconnect Activation
^^x none - - none
Timeouts: Idle EXEC Idle Session Modem Answer Session Dispatch
00:10:00 never none not set
Idle Session Disconnect Warning
never
Modem type is unknown.
Session limit is not set.
Time since activation: never
Editing is enabled.
History is enabled, history size is 10.
DNS resolution in show commands is enabled
Full user help is disabled
Allowed transports are lat pad v120 mop telnet rlogin nasi. Preferred is lat.
No output characters are padded
No special data dispatching characters
Group codes: 0
Modem hardware state: noCTS noDSR DTR RTS
If I tie up that line via a telnet session
munch#show int e 0
Ethernet0 is up, line protocol is up
Hardware is Lance, address is 0060.5cf3.8a67 (bia 0060.5cf3.8a67)
Internet address is 172.17.242.134/21
etc ....
munch#telnet 172.17.242.134 2003
Trying 172.17.242.134, 2003 ... Open
munch#who
Line User Host(s) Idle Location
* 0 con 0 172.17.242.134 00:00:01
3 tty 3 idle 00:00:03 172.17.242.134
Then try to connect to that port via Lat.
ALPHIE>set h/dte lta300 %REM-I-TOQUIT, connection established Press Ctrl/\ to quit, Ctrl/@ for command mode *Mar 1 23:02:52.806: LAT: Host Initiated connection from ALPHIE to :3, sc=1 [Resuming connection 1 to 172.17.242.134 ... ]
The Lat connection is queued up
munch#show entry
1 waiting 00:00:23 for port 3 from LAT node ALPHIE
munch#
When I release the telnet session
munch#exit (You have open connections) [confirm] Closing: 172.17.242.134 !
The Lat connection is granted ..
*Mar 1 23:03:59.758: LAT3: created new inbound session
*Mar 1 23:03:59.774: LAT3: Host-initiated connection complete
*Mar 1 23:03:59.778: LAT3: DataB: +FlowIn +FlowOut Parity 2A Mode Interactive(0) Speed *9600/*9600
*Mar 1 23:03:59.782: LAT3: DataB ignored
munch>
munch>who
Line User Host(s) Idle Location
* 0 con 0 idle 23:04:36
3 tty 3 idle 00:00:36 ALPHIE
If your async devices are outputting any signals before the application or Print symbiont connects to the port, then it might be that the Cisco is starting a loginout process on the async interface, in which case the command
line 0 8 no exec
Would stop the loginout (or exec) process from starting and using up that line.