karent@pyuxp.uucp (25833-Karen Theisen(F510)m000) (03/19/91)
I installed a cisco terminal server that has one ethernet board and 32 serial lines. This device is dedicated for printing. Therefore, I have all 32 lines configured as modem callout and no login. I also group them into four rotaries, each to a micom node (becasue all our printers are off micom nodes and we don't want to reconnect all printers). Anyway, two things that I would like to do and don't know the best way to do it: 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). 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.) Any info on an easy way to do the above will be highly appreciated!!! Karen Theisen (908) 699-5161 karent@bcr.bellcore.com
BILLW@mathom.cisco.com (WilliamChops Westfield) (03/20/91)
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. -------