Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!csn!boulder!daemon
From: BILLW@mathom.cisco.com (WilliamChops Westfield)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: need help on cisco terminal server
Message-ID: <33459@boulder.Colorado.EDU>
Date: 20 Mar 91 04:27:50 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 25


    1.  I would like to "event log" all activities that coming from 
	ethernet to serial ports for trouble shotting. (I have 
	no login on all ports).

For trouble shooting, "debug modem" causes messages to be printed on
the console (or lines with "terminal monitor") when modem state changes
occur.  (including new connections, and connections dropping, stepping
to the next line in the rotary, etc).  "debug tcp" and "debug telnet"
provide similar data on tcp events and telnet negotiations.


    2.  I would like to test all 32 lines to make sure physically they
	are OK. (With rotary, I always get the first available one
	and I can't select a certain line.)

You can connect to a particular port even if it is in a rotary group,
as long as it is not already in use.  Connectng to port 2008 gets you
port 8 (well, 10) even if port 8 (10) is in a rotary group with a bunch
of other ports.  Of course, if the port is busy, you will end up stepping
to the next port in the rotary group...

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