[comp.dcom.sys.cisco] ASM Terminal Server and uucp

cathyf@brazos.rice.edu (Catherine A. Foulston) (10/09/90)

Is anybody successfully using a cisco terminal server with uucp?  If so,
I'd be very interested in hearing what you had to do to get it working.

We have an ASM that we're trying to do uucp through.  Something is causing
the uucicos to stop talking partway through a conversation, maybe as if
the terminal server is stopping transmission.  Because we have two very
different modems connected to the server, and both show the problem, we
think it is somehow caused by the terminal server.  It looks as if only
some files are affected, but when a particular file is affected,
transmission will always fail for that file.  

I have turned off all flowcontrol and set databits to 8 and set no escape
character.  Maybe I have left something out of the line configuration?
Any suggestions will be appreciated.  Thanks,

	Cathy
-- 
Cathy Foulston + cathyf@rice.edu + Rice University, Network & Systems Support

BILLW@mathom.cisco.com (WilliamChops Westfield) (10/10/90)

Sigh.  Usually, I try to put more useful information in the messages
I send out.  I guess I'll have to try again...

    Is anybody successfully using a cisco terminal server with uucp?  If so,
    I'd be very interested in hearing what you had to do to get it working.

    I have turned off all flowcontrol and set databits to 8 and set no escape
    character.  Maybe I have left something out of the line configuration?

You might want "telnet transparent" also.  Note that the "terminal download"
exec command changes all of these parameters with one command.  "autohangup"
will cause the terminal server to hang up when the last connection has been
closed, which is useful since uucp apparently doesn't know how to do any
"post logout" commands...

In general, both the terminal server and the host will be happier if
you establish a stream connection directly to the uucp-over-tcp port
on the unix system (this way you avoid a pty on the unix host!).  In
this case, the commands on the terminal server would look something like:

	TS>terminal download
	TS>terminal autohangup
	TS>telnet unixsystem uucp /stream


Bill Westfield
cisco Systems.
-------

jerry@OLIVEY.ATC.OLIVETTI.COM (Jerry Aguirre) (10/10/90)

Here is what works for me (4.3BSD UUCP):

host Any ACU 2400 14155551212 ord:~5--ord:~2--ord:~2--ord:~2--ord:~2--ord: secret ipA> ter\sno\shold ipA> ter\sno\sesc ipA> host ogin: myname ssword: mypasswd

Of course you will need to change "host", the phone number, "secret",
"myname", "mypasswd", and perhaps the baud rate.  I think it was the
"ter no hold" and "ter no esc" that you really wanted to know about.

I have had mixed results running UUCP over telnet.  Some connections
just don't seem transparrent enough to handle it and then a particular
file will always hang.  If your version of UUCP allows specifying the
protocol used you might try using the "f" protocol instead of the "g".
It was designed for 7 bit connections that don't handle binary
transfers.  Of course many versions of UUCP don't come with the "f"
protocol compiled in (damn them).

					Jerry