<?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: HP Teaming NICs on Proliant Server in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329999#M32372</link>
    <description>Check your controls in the team properties, if you're using Transmit LB you should not have a problem, but switch-assisted will certaily cause this type of problem if not properly configured.&lt;BR /&gt;&lt;BR /&gt;This also sounds like it could be a STP (SpanTree) issue.  I'd check with the network team if you have one.  If not, and you're not sure about the mgt of those 3500s I'd just use AFT (Fail on fault) and go back to one.  Your recieve speeds will be the same, transmit down a little, but you're still fault tolerant.</description>
    <pubDate>Tue, 13 Jul 2004 09:46:11 GMT</pubDate>
    <dc:creator>Bill Parker_3</dc:creator>
    <dc:date>2004-07-13T09:46:11Z</dc:date>
    <item>
      <title>HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329996#M32369</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;I'm using a number of ML370 G3 and DL360 servers. We've built them using Smartstart 7.01 and Windows Server 2003 Standard edition.&lt;BR /&gt;&lt;BR /&gt;After installation is complete the configuration of the HP Teaming defaults to load balancing. In the past (using an older version of Smartstart) it defaulted to Fault Tolerance. All's fine since we want Load Balancing anyway. Each of the nics are connected to separate Cisco 3500 series Catalyst switches (but I dont think that's important). &lt;BR /&gt;&lt;BR /&gt;The problem I have is that network performance is poor. It is noticeably slower with both interfaces connected than just one. Additionally ICMP (ping etc) is very sporadic. Sometimes it will go into phases of not working and the only way to kick it back into action is to disconnect / reconnect  the network leads. &lt;BR /&gt;&lt;BR /&gt;This is not limited to the one server and is not common to one switch or subnet. &lt;BR /&gt;&lt;BR /&gt;I suspect that it is something to do with the new version of the HP Teaming software as we have a number of W2000 servers running using Loadbalancing without issue.&lt;BR /&gt;&lt;BR /&gt;Any help that you can offer would be appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Geoff Collins</description>
      <pubDate>Tue, 13 Jul 2004 08:59:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329996#M32369</guid>
      <dc:creator>Geoff Collins</dc:creator>
      <dc:date>2004-07-13T08:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329997#M32370</link>
      <description>Geoff:&lt;BR /&gt;&lt;BR /&gt;Here is the latest version of the Teaming Util (version 7.60 dated April 14, 2004):&lt;BR /&gt;&lt;A href="http://h18000.www1.hp.com/support/files/server/us/download/19608.html" target="_blank"&gt;http://h18000.www1.hp.com/support/files/server/us/download/19608.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You may need to update the driver versions for the NIC's as well:&lt;BR /&gt;&lt;A href="http://h18000.www1.hp.com/support/files/server/us/locate/69_4307.html#12" target="_blank"&gt;http://h18000.www1.hp.com/support/files/server/us/locate/69_4307.html#12&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18000.www1.hp.com/support/files/server/us/locate/69_4764.html#12" target="_blank"&gt;http://h18000.www1.hp.com/support/files/server/us/locate/69_4764.html#12&lt;/A&gt;</description>
      <pubDate>Tue, 13 Jul 2004 09:12:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329997#M32370</guid>
      <dc:creator>JohnWRuffo</dc:creator>
      <dc:date>2004-07-13T09:12:47Z</dc:date>
    </item>
    <item>
      <title>Re: HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329998#M32371</link>
      <description>Thanks - I'll try that and let you know...&lt;BR /&gt;&lt;BR /&gt;Geoff</description>
      <pubDate>Tue, 13 Jul 2004 09:29:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329998#M32371</guid>
      <dc:creator>Geoff Collins</dc:creator>
      <dc:date>2004-07-13T09:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329999#M32372</link>
      <description>Check your controls in the team properties, if you're using Transmit LB you should not have a problem, but switch-assisted will certaily cause this type of problem if not properly configured.&lt;BR /&gt;&lt;BR /&gt;This also sounds like it could be a STP (SpanTree) issue.  I'd check with the network team if you have one.  If not, and you're not sure about the mgt of those 3500s I'd just use AFT (Fail on fault) and go back to one.  Your recieve speeds will be the same, transmit down a little, but you're still fault tolerant.</description>
      <pubDate>Tue, 13 Jul 2004 09:46:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3329999#M32372</guid>
      <dc:creator>Bill Parker_3</dc:creator>
      <dc:date>2004-07-13T09:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330000#M32373</link>
      <description>Hmmm&lt;BR /&gt;&lt;BR /&gt;I'm already on LB Transmit, so it can't be that. The drivers didnt seem to make any difference but I'm not that surprised since the issue isnt listed in the fix list... &lt;BR /&gt;&lt;BR /&gt;What is the potenetial issue with Spanning tree?&lt;BR /&gt;&lt;BR /&gt;Cheers for your help&lt;BR /&gt;&lt;BR /&gt;Geoff</description>
      <pubDate>Tue, 13 Jul 2004 10:01:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330000#M32373</guid>
      <dc:creator>Geoff Collins</dc:creator>
      <dc:date>2004-07-13T10:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330001#M32374</link>
      <description>Have you checked the switch port configuration, particularily in respect to etherchannel. LB in the HP teaming utility is the same as FEC in the cisco world.</description>
      <pubDate>Mon, 19 Jul 2004 21:58:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330001#M32374</guid>
      <dc:creator>Craig Conway_1</dc:creator>
      <dc:date>2004-07-19T21:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330002#M32375</link>
      <description>Thanks&lt;BR /&gt;&lt;BR /&gt;I found this solution in Microsoft KB. I like more to solve problems, than to prevent from error messages. But it seems to be the only solution for now. I upgraded the NIC driver and the network configuration utility (Rel. 7.7), but this does not help:-(</description>
      <pubDate>Mon, 20 Sep 2004 05:52:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330002#M32375</guid>
      <dc:creator>Schlumpf Christoph</dc:creator>
      <dc:date>2004-09-20T05:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: HP Teaming NICs on Proliant Server</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330003#M32376</link>
      <description>Craig Conway wrote:&lt;BR /&gt;..."LB in the HP teaming utility is the same as FEC in the cisco world"...&lt;BR /&gt;can anybody explain it?</description>
      <pubDate>Tue, 19 Sep 2006 10:41:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-teaming-nics-on-proliant-server/m-p/3330003#M32376</guid>
      <dc:creator>Marcelo Pagano</dc:creator>
      <dc:date>2006-09-19T10:41:48Z</dc:date>
    </item>
  </channel>
</rss>

