Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!linus!philabs!cmcl2!seismo!lll-crg!ucdavis!ucbvax!cca-unix.arpa!emacs!infinet!wanginst!decvax!mcnc!ncsu!uvacs!edison!wjs
From: wjs@edison.UUCP
Newsgroups: mod.computers.vax
Subject: Re: interpreting show err reports for terminal ports
Message-ID: <8510291648.AA00587@edison.UUCP>
Date: Tue, 29-Oct-85 11:48:09 EST
Article-I.D.: edison.8510291648.AA00587
Posted: Tue Oct 29 11:48:09 1985
Date-Received: Sun, 10-Nov-85 04:04:32 EST
References: <4573@cca.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12
Approved: info-vax@ucbvax.berkeley.edu




Normally, the terminal drive generates these errors. However, the terminal
driver never logs them into the errorlog. The errors could mean that
you have a bad port or distribution panel. A reboot will clear the error
count, however, you may want to make sure all your cables are plugged in
correctly. I guess it is possible to have a bad terminal generate bad signals
which could be interpreted as an error. So, you might want to use another
terminal to check the port. Use another port to check the terminal. If you
pay for maintenance, you may just give the maintenance folks a call and
let them look at it. Anyway, It the problem persit, do not ignore it.