jmr1@Ra.MsState.Edu (Mike Rackley) (05/23/91)
The following is the best lead I've had on what might be at the root of our problem. It turns out our MCI ethernet board WAS running microcode version 1.7. I got a 1.8 board in this afternoon and installed it. I will report the results to this list as soon as possible. Mike Rackley, Mississippi State University Internet: jmr1@CC.MsState.Edu Bitnet: JMR1@MsState Phone: (601)325-7028 FAX: (601)325-8921 -----------------------Begin included message------------------------------ Date: Wed, 15 May 91 09:11:16 -0500 From: spurgeon@sirius.cc.utexas.edu (Charles E. Spurgeon) Posted-Date: Wed, 15 May 91 09:11:16 -0500 Message-Id: <9105151411.AA09025@sirius.cc.utexas.edu> To: jmr1@Ra.MsState.Edu Subject: Re: Terminal server hangs Newsgroups: comp.dcom.sys.cisco In-Reply-To: <35086@boulder.Colorado.EDU> Organization: UTexas Computation Center, Austin, Texas Just out of curiosity, what version of microcode are your terminal servers running on their Ethernet interface? A "sh cont mci" should emit the version information. The tipoff is a number of "line down restarts" (or something like that) shown in the MCI controller stats. We had all manner of problems with version 1.7 microcode on Ethernet MCIs that were attached to busy networks. 30 second to 2 minute long hangs of our routers were common. The fix was to upgrade to v1.8 code on the MCIs. -ces --------------------------End included message------------------------------