<?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 Re: Flow Paradox in Communications and Wireless</title>
    <link>https://community.hpe.com/t5/communications-and-wireless/flow-paradox/m-p/2903507#M917</link>
    <description>If A's main job is to talk to D then 10 half is good enough.  In fact I have run into problems in a similar situation by trying to run 100 Full on the A-B link.  I had a second device on the A - B LAN and they both needed to use the B-C link (a T1) at the same time.  When I set A1 to 100 full it would fill the router's input queue with so many packets that A2's processes became timing out.  Setting it back to 10half solved the time out problem.&lt;BR /&gt;&lt;BR /&gt;The only time 100 full would help is if it needed to talk quickly to another local computer or if there were a lot of incoming broadcast traffic from the local LAN (in which case you might want to try 10 full first).&lt;BR /&gt;&lt;BR /&gt;Ron</description>
    <pubDate>Thu, 13 Feb 2003 15:59:32 GMT</pubDate>
    <dc:creator>Ron Kinner</dc:creator>
    <dc:date>2003-02-13T15:59:32Z</dc:date>
    <item>
      <title>Flow Paradox</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/flow-paradox/m-p/2903505#M915</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have network like this&lt;BR /&gt;&lt;BR /&gt;|A|------|B|------|C|-----|D|&lt;BR /&gt;&lt;BR /&gt;Between Node B and Node C the speed is 10 Mbps, Half-duplex and i cannot change it.&lt;BR /&gt;&lt;BR /&gt;My question is to what speed/flow combinations should be set from node A to node B and node C to node D that will ensure the maximum bandwidth performance between node A and node D.&lt;BR /&gt;&lt;BR /&gt;100/FD or 100/HD or 10/HD ?&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;&lt;BR /&gt;U.SivaKumar&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 13 Feb 2003 08:12:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/flow-paradox/m-p/2903505#M915</guid>
      <dc:creator>U.SivaKumar_2</dc:creator>
      <dc:date>2003-02-13T08:12:08Z</dc:date>
    </item>
    <item>
      <title>Re: Flow Paradox</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/flow-paradox/m-p/2903506#M916</link>
      <description>Hi, Siv&lt;BR /&gt;&lt;BR /&gt;I choose 10/HD. &lt;BR /&gt;&lt;BR /&gt;anyhow ifyou set 100/FD between other nodes, link between B to C has the constraints</description>
      <pubDate>Thu, 13 Feb 2003 08:27:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/flow-paradox/m-p/2903506#M916</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2003-02-13T08:27:35Z</dc:date>
    </item>
    <item>
      <title>Re: Flow Paradox</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/flow-paradox/m-p/2903507#M917</link>
      <description>If A's main job is to talk to D then 10 half is good enough.  In fact I have run into problems in a similar situation by trying to run 100 Full on the A-B link.  I had a second device on the A - B LAN and they both needed to use the B-C link (a T1) at the same time.  When I set A1 to 100 full it would fill the router's input queue with so many packets that A2's processes became timing out.  Setting it back to 10half solved the time out problem.&lt;BR /&gt;&lt;BR /&gt;The only time 100 full would help is if it needed to talk quickly to another local computer or if there were a lot of incoming broadcast traffic from the local LAN (in which case you might want to try 10 full first).&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Thu, 13 Feb 2003 15:59:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/flow-paradox/m-p/2903507#M917</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2003-02-13T15:59:32Z</dc:date>
    </item>
  </channel>
</rss>

