Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!uwvax!tank!ncar!boulder!tramp!jeff From: jeff@tramp.Colorado.EDU (Jefferson W. Christy) Newsgroups: comp.dcom.lans Subject: Re: CISCO terminal server users, please help Message-ID: <9111@boulder.Colorado.EDU> Date: 31 May 89 14:25:52 GMT References: <5137@charon.unm.edu> <5159@b11.ingr.com> Sender: news@boulder.Colorado.EDU Reply-To: jeff@tramp.Colorado.EDU (Jefferson W. Christy) Organization: University of Colorado, Boulder Lines: 28 In article <5159@b11.ingr.com> jeff@b11.ingr.com (Jeff Kilpatrick) writes: >In article , ron@ron.rutgers.edu (Ron Natalie) writes: > >> speed mismatch. Cisco can do flow control on either on one of >> the RS-232 spare pins or with XON/XOFF. It's configurable per > ^^^^^^^^^^^^^^^^^^^^^ > > Do they support RTS/CTS or are they doing something proprietary(sp?)? The ASM/2 terminal server from Cisco does support flow hardware flow control on RTS/CTS, if you don't need modem-style handshaking. If however, the line is configured to use modem control, then the CTS input is used for this purpose and hardware flow-control is not an option. The limiting factor is that each terminal line is supported on only six pins (RD, TD, GND, RI, DTR, and CTS). I might add that we use the ASM/2 to interface our async data switch (ISN) with our campus ethernet, and we have been very pleased with Cisco, both in terms of flexibility and reliability. Jeff Christy Computing and Network Services Univ. of Colo., Boulder _ /| Inet: jeff@tramp.colorado.edu \`o_O' uucp: ...!boulder!tramp!jeff ( ) U Just goes to show, you don't ever know...