<?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: bl460c teaming issue in Networking</title>
    <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132351#M1999</link>
    <description>hi,&lt;BR /&gt;i spoke today with HP ,the switch 3020 has no support to any teaming mode beside NLB while at this method only one nic is active,so they told me that if i want to use any other method i need to upgrade to 3120.&lt;BR /&gt;thank you for your fast support,&lt;BR /&gt;erspectfully,&lt;BR /&gt;avi azerrad&lt;BR /&gt;</description>
    <pubDate>Thu, 02 Oct 2008 14:56:36 GMT</pubDate>
    <dc:creator>AviAzerrad</dc:creator>
    <dc:date>2008-10-02T14:56:36Z</dc:date>
    <item>
      <title>bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132344#M1992</link>
      <description>hi,&lt;BR /&gt;we are using bl 460c blades with built-in 4 cisco ethernet switches..&lt;BR /&gt;each blade has 4 nic cards by default and each nic is directly connected to the cisco switches (each nic to a specific cisco switch).&lt;BR /&gt;now,all the 4 cisco switches are directly connected (2 ports from every cisco switch in internal ports 17+18) to our backbone switch "catalyst 4506" ,here is the built-in cisco configuration:&lt;BR /&gt;&lt;BR /&gt;"interface Port-channel1&lt;BR /&gt;&lt;BR /&gt;interface GigabitEthernet0/17&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/18&lt;BR /&gt;channel-group 1 mode on"&lt;BR /&gt;&lt;BR /&gt;now here is our cisco backbone 4506 configuration :&lt;BR /&gt;interface Port-channel10&lt;BR /&gt;description Connect to HP_Blade_Center&lt;BR /&gt;switchport&lt;BR /&gt;switchport access vlan 110&lt;BR /&gt;switchport mode access&lt;BR /&gt;&lt;BR /&gt;interface GigabitEthernet4/36&lt;BR /&gt;switchport access vlan 110&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 10 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet4/37&lt;BR /&gt;switchport access vlan 110&lt;BR /&gt;switchport mode access&lt;BR /&gt;channel-group 10 mode on"&lt;BR /&gt;so we configured those configuration from each built-in cisco switch to our backbone..&lt;BR /&gt;so now i am asking :&lt;BR /&gt;1. for best performance this is the best configuration between cisco built-in switch to our cisco 4506 backbone ?&lt;BR /&gt;2. why i cannot perform windows teaming ? every time when i am trying to add members to teaming i am getting flipping errors from the hp cisco switch and network errors and i may lose connections to me blades ? what is wrong ?&lt;BR /&gt;3.for best performance in windows env (best mb/sec) which method of teaming i need ?&lt;BR /&gt;&lt;BR /&gt;respectfully,&lt;BR /&gt;avi azerrad</description>
      <pubDate>Mon, 29 Sep 2008 04:11:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132344#M1992</guid>
      <dc:creator>AviAzerrad</dc:creator>
      <dc:date>2008-09-29T04:11:26Z</dc:date>
    </item>
    <item>
      <title>Re: bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132345#M1993</link>
      <description>Hello,&lt;BR /&gt;What type on enclosure are you using? C3000 or C7000? How many blades are you using?</description>
      <pubDate>Mon, 29 Sep 2008 12:44:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132345#M1993</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2008-09-29T12:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132346#M1994</link>
      <description>cx 7000&lt;BR /&gt;and internal built-in switch model "Model number                    : WS-CBS3020-HPQ"&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Oct 2008 17:18:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132346#M1994</guid>
      <dc:creator>AviAzerrad</dc:creator>
      <dc:date>2008-10-01T17:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132347#M1995</link>
      <description>1 - Thats a good configuration to the upstream switch, 2GB etherchannel from each blade switch&lt;BR /&gt;&lt;BR /&gt;2 - As far as I can see the ports 17 and 18 are on Vlan 1, not vlan 110 as the upstream switch ports, therefore the NICS wont be able to get the heartbeat of the team&lt;BR /&gt;&lt;BR /&gt;3 - Since each NIC goes to a different switch, and the switch is not stacking capable, the options will be NFT or TLB team. Best option will be TLB, but is not possible to increase RX, it will only increase TX.&lt;BR /&gt;&lt;BR /&gt;rgds</description>
      <pubDate>Wed, 01 Oct 2008 17:27:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132347#M1995</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2008-10-01T17:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132348#M1996</link>
      <description>dear Lmm&lt;BR /&gt;my servers vlan name is 110 ,and the cisco built-in switch is directly connected to my backbone that are using vlan 110 ,in every cisco built-n switch (all the 4) ports 17-18 are directly connected to my backbone,here is the cisco built-in configuration:"&lt;BR /&gt;no file verify auto&lt;BR /&gt;spanning-tree mode pvst&lt;BR /&gt;spanning-tree extend system-id&lt;BR /&gt;!&lt;BR /&gt;vlan internal allocation policy ascending&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel1&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0&lt;BR /&gt; ip address 172.16.0.56 255.255.254.0&lt;BR /&gt; no ip route-cache&lt;BR /&gt; shutdown&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/1&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/2&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/3&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/4&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/5&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/6&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/7&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/8&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/9&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/10&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/11&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/12&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/13&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/14&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/15&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/16&lt;BR /&gt; speed 1000&lt;BR /&gt; spanning-tree portfast&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/17&lt;BR /&gt; channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/18&lt;BR /&gt; channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/19&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/20&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/21&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/22&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/23&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/24&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt; ip address 172.16.0.56 255.255.254.0&lt;BR /&gt; no ip route-cache&lt;BR /&gt;!&lt;BR /&gt;interface Vlan10&lt;BR /&gt; no ip address&lt;BR /&gt; no ip route-cache&lt;BR /&gt;!&lt;BR /&gt;ip default-gateway 172.16.1.19&lt;BR /&gt;ip http server&lt;BR /&gt;snmp-server community public RO"&lt;BR /&gt;&lt;BR /&gt;vlan 1 is only for the managment ip .&lt;BR /&gt;&lt;BR /&gt;respectfully,&lt;BR /&gt;avi azerrad&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Oct 2008 03:27:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132348#M1996</guid>
      <dc:creator>AviAzerrad</dc:creator>
      <dc:date>2008-10-02T03:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132349#M1997</link>
      <description>If the server vlan is 110, then the downlinks port where the servers are connected must be on that vlan:&lt;BR /&gt;&lt;BR /&gt;interface GigabitEthernet0/6&lt;BR /&gt;speed 1000&lt;BR /&gt;switchport mode acess&lt;BR /&gt;switchport access vlan 110&lt;BR /&gt;spanning-tree portfas&lt;BR /&gt;&lt;BR /&gt;and then you need to carry both vlan 1 and 110 to the upstream switch, which means the etherchannel must be a trunk (IEEE 802.1q):&lt;BR /&gt;&lt;BR /&gt;interface GigabitEthernet0/17&lt;BR /&gt;Switchport mode truk&lt;BR /&gt;switchport trunk allowed vlan 1, 110 (Optional)&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;&lt;BR /&gt;Then it will carry traffic for both vlans, vlan 110 tagged, and vlan 1 unttaged since its the native vlan.&lt;BR /&gt;&lt;BR /&gt;Same for the upstream switch ports where the&lt;BR /&gt;3020 is connecting to.&lt;BR /&gt;&lt;BR /&gt;rgds,</description>
      <pubDate>Thu, 02 Oct 2008 14:01:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132349#M1997</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2008-10-02T14:01:51Z</dc:date>
    </item>
    <item>
      <title>Re: bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132350#M1998</link>
      <description>hi,&lt;BR /&gt;i spoke today with HP ,the switch 3020 has no support to any teaming mode beside NLB while at this method only one nic is active,so they told me that if i want to use any other method i need to upgrade to 3120.&lt;BR /&gt;thank you for your fast support,&lt;BR /&gt;erspectfully,&lt;BR /&gt;avi azerrad&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Oct 2008 14:48:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132350#M1998</guid>
      <dc:creator>AviAzerrad</dc:creator>
      <dc:date>2008-10-02T14:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: bl460c teaming issue</title>
      <link>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132351#M1999</link>
      <description>hi,&lt;BR /&gt;i spoke today with HP ,the switch 3020 has no support to any teaming mode beside NLB while at this method only one nic is active,so they told me that if i want to use any other method i need to upgrade to 3120.&lt;BR /&gt;thank you for your fast support,&lt;BR /&gt;erspectfully,&lt;BR /&gt;avi azerrad&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Oct 2008 14:56:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/bl460c-teaming-issue/m-p/5132351#M1999</guid>
      <dc:creator>AviAzerrad</dc:creator>
      <dc:date>2008-10-02T14:56:36Z</dc:date>
    </item>
  </channel>
</rss>

