Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!ig!agate!ucbvax!UCBCMSA.BITNET!CLIFF From: CLIFF@UCBCMSA.BITNET (Cliff Frost {415} 642-5360) Newsgroups: comp.sys.proteon Subject: [ Op err 8704 hst 0 nt 2 int Pro/0] Message-ID: <8809220110.AA04255@devvax.TN.CORNELL.EDU> Date: 22 Sep 88 00:38:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 23 Tom, Thank you! That is exactly the kind of information I was looking for. We've seen clumps of these error msgs twice, and both times the symptoms were different from what your note describes. 1) The first time, all the gateways had very large numbers of 'output refused', and no significant numbers of either 'output bad format' or 'input parity errors'. We isolated the problem to a particular p3280 by transfering large files back and forth through each gateway (one direction would always fail--sending along the ring in the way that went through the bad p3280). 2) The second time only one gateway was putting out the 'Op err' msgs, and it had large numbers of 'output refused' messages. Again, it was a flakey p3280. So, in no case have we seen any 'input parity error' or 'output bad format' counters go up along with this 8704 msg, only 'output refused'. I guess this just shows there's more than one way to skin a network... Thanks again, Cliff