|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] IBM got back to me on the cause of the problem. The answer they gave me worked. I'll quote IBM here: "The key to this problem is with the configuration of the 2838 line description vs the ETH Switch box. - Tom will email Guy a KB doc 6654625 that will explain and bottom line is that the ETH line description LINESPEED should = *AUTO DUPLEX should = *AUTO These will allow the 2838 card to sync up with the switch it is attach to (assuming the switch is set to negotiate. Since there are currently collisions on the ETH running the commtrace slows the line down just enuf to prevent the collisions and thereby allowing throughput to be faster with the commtrace running." If you or anyone wants a copy of document 6645625, it's at http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/99 0a2cc52f1fb76186256665004727bf?OpenDocument&Highlight=0,6654625 or I can email it to you. The document covers more that the 2838 Ethernet adapter which we use. Guy Murphy murphyfa@uiuc.edu UDIS at the University of Illinois 217-333-8670 http://www.heisercoaching.com -----Original Message----- From: chris.whisonant@comporium.com [mailto:chris.whisonant@comporium.com] Sent: Thursday, October 04, 2001 10:21 AM To: midrange-l@midrange.com Cc: StanWilburn@comporium.com; Johnny.Helms@comporium.com; gwbowers@bellsouth.net Subject: Re: FTP Conundrum with Communication Trace I just tested this and here are my results: With no trace on a development machine (model 270, v5r1), I put a file from my pc at 544.69Kbytes/sec. I started a trace and put the file at 2863.66Kbytes/sec. I stopped and deleted the trace and put the file at 680.74Kbytes/sec. On our production machine (model 720, v4r4), I first put file with no trace at 389.10Kbytes/sec. After starting the trace, I put the file at 1330.83Kbytes/sec. After ending and deleting the trace, the figure went to 437.43Kbytes/sec. Seems like this is not just v5r1. Thanks, Chris Whisonant "I started a comm trace on the V5R1 machine to see if I could see anything in the trace that would account for the slow speed. As soon as I started the trace, the transfer rates went to 1400-1800 Kbytes/sec. When I stop and delete the trace, the rates go back to 55-65 Kbytes/sec. This morning I decide to test a PC to V5R1 file transfer. The PC is not on the same switch. Without an active comm trace, the speed was 310 Kbytes/sec. With an active trace, the rate was 730 Kbytes/sec. This is so bizarre. It seems as though V5R1 ftp needs an audience to perform better. Is this happening to anyone else? Guy Murphy" _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.