Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!news.cs.indiana.edu!arizona.edu!arizona!optima.UUCP From: ric@optima.UUCP (Ric Anderson) Newsgroups: comp.dcom.sys.cisco Subject: Re: Terminal server hangs Message-ID: <3220@optima.cs.arizona.edu> Date: 15 May 91 17:21:58 GMT References: <35090@boulder.Colorado.EDU> Sender: news@cs.arizona.edu Lines: 35 From article <35090@boulder.Colorado.EDU>, by chen@cunixf.cc.columbia.edu (Bill Chen): > > > We've had and are still having the problem. We run csc/2s with > 8.1 (14) software. I don't think we've ever had it hang for up > to 2 minutes, but definitely 30 seconds. > > Bill Chen I've seen two flavors of hangs, completely unrelated. Flavor 1 involved rlogin connections to Sun systems at SunOS 4.1 and above (4.0.3 did not show the problem). The terminal session would hang for 5 seconds, and then continue. The workaround (which cisco phone support supplied) was to set ip mtu 1064 on the servers. This completely eliminated the problem. The 5 second time was a deadman timer on the Suns. It is possible thet the 30 second hang is due to the timer being longer on whatever host you have. Flavor 2 involves all terminals on a server (including the console). Basically, a user connected to a system is unaffected, but the server stops processing connect and disconnects, so if you log out, you terminal goes dead. A "send *" does appear on all terminals (including the dead ones), and you can get in to do a "send *" via telnet to one of the vty's. This appears to have been a bad processor card, as it has not reappeared since we swapped out the cpu. All of this was under 8.1(14). Ric (ric@cs.arizona.edu )