<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Weird ftp problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936282#M112710</link>
    <description>Folks,&lt;BR /&gt;&lt;BR /&gt;I am facing this problem -&amp;gt;&lt;BR /&gt;&lt;BR /&gt;When we invoke a huge ftp file transfer appx 1.7G file from system A (which is a K Class, HPUX 11.0 server) to an IBM Mainframe, the tranmit takes too longs, almost 5 times as much, compared to receive from IBM MainFrame to system A. Tested with both Get/Put in either direction with BIN modes, the problem remains the same. &lt;BR /&gt;&lt;BR /&gt;Observation so far :&lt;BR /&gt;&lt;BR /&gt;- Binary mode or Ascii mode does, same problem&lt;BR /&gt;-Lan Interface is set to 100FDX on Sys A and MainFrame&lt;BR /&gt;- System A to another system B (Hpux) works great both get/put of the same file&lt;BR /&gt;- No disk full conditions on System A or MainFrame&lt;BR /&gt;- Latest ftp/ftpd patch PHNE_23949 was  already installed&lt;BR /&gt;&lt;BR /&gt;Any clues ?? IBM MainFrame uses EBCDIC ( instead of ASCII) Any pointer to solve this will be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;&lt;BR /&gt;-Q4U&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 26 Mar 2003 15:50:38 GMT</pubDate>
    <dc:creator>Q4you</dc:creator>
    <dc:date>2003-03-26T15:50:38Z</dc:date>
    <item>
      <title>Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936282#M112710</link>
      <description>Folks,&lt;BR /&gt;&lt;BR /&gt;I am facing this problem -&amp;gt;&lt;BR /&gt;&lt;BR /&gt;When we invoke a huge ftp file transfer appx 1.7G file from system A (which is a K Class, HPUX 11.0 server) to an IBM Mainframe, the tranmit takes too longs, almost 5 times as much, compared to receive from IBM MainFrame to system A. Tested with both Get/Put in either direction with BIN modes, the problem remains the same. &lt;BR /&gt;&lt;BR /&gt;Observation so far :&lt;BR /&gt;&lt;BR /&gt;- Binary mode or Ascii mode does, same problem&lt;BR /&gt;-Lan Interface is set to 100FDX on Sys A and MainFrame&lt;BR /&gt;- System A to another system B (Hpux) works great both get/put of the same file&lt;BR /&gt;- No disk full conditions on System A or MainFrame&lt;BR /&gt;- Latest ftp/ftpd patch PHNE_23949 was  already installed&lt;BR /&gt;&lt;BR /&gt;Any clues ?? IBM MainFrame uses EBCDIC ( instead of ASCII) Any pointer to solve this will be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;&lt;BR /&gt;-Q4U&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Mar 2003 15:50:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936282#M112710</guid>
      <dc:creator>Q4you</dc:creator>
      <dc:date>2003-03-26T15:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936283#M112711</link>
      <description>Weve seen this problem before, some sort of timeout ocurring. We found the answer was to leave a ping running the whole time of the ftp and this seemed to keep the ftp transfer 'alive' and it didnt timeout. Try it.&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Mar 2003 15:53:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936283#M112711</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-03-26T15:53:18Z</dc:date>
    </item>
    <item>
      <title>Re: Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936284#M112712</link>
      <description>Hello Q,&lt;BR /&gt;&lt;BR /&gt;We had a similar problem here last year.  We have some K-class boxes in remote sites that our IBM mainframe sends large files to daily via ftp.  We had a couple of sites that were really slow.  We suffered through packet traces and analyzed patches on our end, and our mainframe guys tried a couple of different versions of the TCP/IP stack.  Finally, our network guys made a change somewhere and everything was fine after that.&lt;BR /&gt;&lt;BR /&gt;Have you tried doing a packet dump on your K box while you are doing the ftp?  It might give you some clue about what is happening.  I'd look for the size of the packets and also to see if you are having lots of retransmissions.  The ftp program on the mainframe should handle your ASCII to EBCDIC conversions, which is nice.  I'd hate to have to be the five billionth person to write one of those translators.  :)&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Mar 2003 16:00:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936284#M112712</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-03-26T16:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936285#M112713</link>
      <description>Might want to check your network switch.&lt;BR /&gt;&lt;BR /&gt;If its produced by Cisco, and set to auto negotiate it can cause this problem.&lt;BR /&gt;&lt;BR /&gt;Are you setting your lan speed settings in /etc/rc.config.d/hpbtlanconf  ?&lt;BR /&gt;&lt;BR /&gt;Here are mine.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HP_BTLAN_INTERFACE_NAME[0]=lan0&lt;BR /&gt;HP_BTLAN_STATION_ADDRESS[0]=&lt;BR /&gt;HP_BTLAN_SPEED[0]=10HD&lt;BR /&gt;HP_BTLAN_INTERFACE_NAME[1]=lan1&lt;BR /&gt;HP_BTLAN_STATION_ADDRESS[1]=&lt;BR /&gt;HP_BTLAN_SPEED[1]=100FD&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Have the swith admin chedk the speed of the port you are plugged into.  If it differs from your lanadmin -x readings, ask the administrator to hard code the settings and turn off auto negotiate.&lt;BR /&gt;&lt;BR /&gt;reboot server, try it again.  It might work bettter this time.&lt;BR /&gt;&lt;BR /&gt;If you need details, post further details/questions.&lt;BR /&gt;&lt;BR /&gt;Hope I helped.&lt;BR /&gt;&lt;BR /&gt;Note: I have had this issue though it was messing with Ignite transfers, it would have made ftp a nightmare had I not resovled it.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Mar 2003 16:05:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936285#M112713</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-03-26T16:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936286#M112714</link>
      <description>Thanks Stephan, JP and steve for your response.&lt;BR /&gt;&lt;BR /&gt;Stephan : Is that true ? Can't believe it, will try first thing tomorrow !!!&lt;BR /&gt;&lt;BR /&gt;JP : How do you packet trace on the HPUX ?&lt;BR /&gt;&lt;BR /&gt;Steve : Yes, we have locked our LAN interfaces to 100FDX on lan card as well as on switch.&lt;BR /&gt;&lt;BR /&gt;Some more tests were done..After starting ftp..it ramps up, avgs appx 2mb/sec for sometime and all of a sudden..BOOM..it dies down to 0 B/sec..it stays like that for 2 to 5 minutes and ramps up again...and slows down..we get appx 500KB/sec ( which is very slow compared to other servers which avgs appx 3 to 6 MB/sec) and ultimately the files gets transfered. &lt;BR /&gt;&lt;BR /&gt;To eliminate and disk bottleneck, sending file from host A to "NULL" on the Mainframe. Did not help, though.</description>
      <pubDate>Fri, 28 Mar 2003 03:30:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936286#M112714</guid>
      <dc:creator>Q4you</dc:creator>
      <dc:date>2003-03-28T03:30:25Z</dc:date>
    </item>
    <item>
      <title>Re: Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936287#M112715</link>
      <description>We had exactly the same problem.  Our mainframe collegues did 'something' on their box (patch, config ... dunno), but the problem was fixed.</description>
      <pubDate>Fri, 28 Mar 2003 08:37:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936287#M112715</guid>
      <dc:creator>Systeemingenieurs Infoc</dc:creator>
      <dc:date>2003-03-28T08:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936288#M112716</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Take a look at the 'nettl' and the 'netfmt' commands.  They will do the tracing and reporting for you.  Also, you can get some third party products such as Ethereal.&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Mar 2003 13:47:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936288#M112716</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-03-28T13:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: Weird ftp problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936289#M112717</link>
      <description>It may sound illogical, but after, many many test iterations not pointing to any firm conclusion, decided to give a shot by changing the Lan interface card. &lt;BR /&gt;&lt;BR /&gt;And that fixed it !!&lt;BR /&gt;&lt;BR /&gt;Thanks to all.</description>
      <pubDate>Sun, 06 Apr 2003 20:16:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/weird-ftp-problem/m-p/2936289#M112717</guid>
      <dc:creator>Q4you</dc:creator>
      <dc:date>2003-04-06T20:16:12Z</dc:date>
    </item>
  </channel>
</rss>

