[comp.sys.proteon] ftp rgb files over Pronet-80

sting@laotse.cam.nist.gov (s. ting) (02/28/90)

   We have a ProNET-80 fiber ring on campus. Many P4200s are attached to
 the ring through p3280s. Ethernets are connected to those P4200s.  One 
 scientist here tried to ftp his three image files (3-dimensional) from his HP
 running unix on one Ethernet to another host on a different Ethernet through the 
 ring.  The ftp always stuck.  But, with same hosts involved, no problems with
 ftping at all for other files no matter the file sizes and binary or ascii.
 
   I observed on p4200 many "Op err 8704 hst xxx" messages like below being pumped out
 as soon as the ftping of any one rgb file began. Those messages did not appear while
 we tried other different files. 
   
   Op err 8704 hst 376 nt 0 int Pro/0
   Op err 8704 hst 376 nt 0 int Pro/0
   Op err 8704 hst 376 nt 0 int Pro/0
   Op err 8704 hst 376 nt 0 int Pro/0
   Op err 8704 hst 376 nt 0 int Pro/0
   Op err 8704 hst 376 nt 0 int Pro/0
   Op err 8704 hst 376 nt 0 int Pro/0


  So, it appears that ProNET-80 has something to do with it.  Does anyone have similar
experience or know what is going on?



  Michael Ting, 
  NIST, (301) 975-3802

tvm@proteon.com (Tom Miceli) (02/28/90)

Mike,
	How many P4200's do you have on the P-80 ring? One of the
modems is probably out of alignment. What you need to do is CLEAR
network stats on all routers, transfer the file, then look at the
interface stats for the P-80's on the router. Look for the router with
the largest number of INPUT PARITY ERRORS. Either the Fiber modem or
the P-80 interface in that router may be out of alignment. Let us know
what happens.

Tom Miceli,
Mgr Tech Support

CLIFF@UCBCMSA.BITNET (Cliff Frost {415} 642-5360) (02/28/90)

Michael,
I suspect that your p80 ring has the classic data-dependent problem.
You can test it by sending files or pings through the ring that have
the data pattern hex 33, or hex EE, or any of a few others.

With anonymous ftp to jade.berkeley.edu you can get two programs that
may help you detect where the failing component is.  The ping.c and
netout.c programs in the pub directory there both take an argument
to specify a data pattern to fill your packets with.

Ping tests the entire ring, while netout sends data to the TCP
discard port on the remote host and so you can use it to exercise
discreet individual segments.

Proteon Customer Service should be able to help you with this, but
if you like you can call me and I'll be happy to discuss it as well.

        Cliff Frost                   (415) 642-5360
        Central Computing Services    <cliff@berkeley.edu>
        University of California      CLIFF AT UCBCMSA
        Berkeley, CA 94720