+ Post New Thread
Results 1 to 4 of 4
Hardware Thread, Teaming NICS in Technical; Never done it before but we are getting a bottleneck on one of our servers, we have 4 broadcom NetXtreme ...
  1. #1
    jsnetman's Avatar
    Join Date
    Oct 2007
    Posts
    887
    Thank Post
    23
    Thanked 134 Times in 126 Posts
    Rep Power
    39

    Teaming NICS

    Never done it before but we are getting a bottleneck on one of our servers, we have 4 broadcom NetXtreme II per server and thought about teaming them.

    I have a very basic questions on how to do.

    Do all the nics need an IP address and subnet before I team, or because its creating a virtual NIC I just need the one IP address on one NIC ?

  2. #2


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,627
    Thank Post
    275
    Thanked 777 Times in 604 Posts
    Rep Power
    223
    Quote Originally Posted by jsnetman View Post
    Do all the nics need an IP address and subnet before I team, or because its creating a virtual NIC I just need the one IP address on one NIC ?
    Just one ip for the resulting virtual nic.

  3. Thanks to pete from:

    jsnetman (11th February 2010)

  4. #3
    jsnetman's Avatar
    Join Date
    Oct 2007
    Posts
    887
    Thank Post
    23
    Thanked 134 Times in 126 Posts
    Rep Power
    39
    Just one ip for the resulting virtual nic
    so presently one of my nics has an IP, are you saying I should remove this before doing the team. And the re-enter it on the virtual nic ?

  5. #4


    Join Date
    Oct 2006
    Posts
    3,411
    Thank Post
    184
    Thanked 356 Times in 285 Posts
    Rep Power
    148
    windows yeah?

    No just do it. The bonding software isnt amazing but its straight forward enough. You do need to decide which type of bonding you are going to do though; LACP (802.3ad) is by far the best but the connecting switch needs to support it.

    This is for linux but the explanations of how the different types works is the same. (There may be types that arnt supported in windows, cant remember off the top of my head)

    balance-rr or 0

    Round-robin policy: Transmit packets in sequential
    order from the first available slave through the
    last. This mode provides load balancing and fault
    tolerance.

    active-backup or 1

    Active-backup policy: Only one slave in the bond is
    active. A different slave becomes active if, and only
    if, the active slave fails. The bond's MAC address is
    externally visible on only one port (network adapter)
    to avoid confusing the switch.

    In bonding version 2.6.2 or later, when a failover
    occurs in active-backup mode, bonding will issue one
    or more gratuitous ARPs on the newly active slave.
    One gratutious ARP is issued for the bonding master
    interface and each VLAN interfaces configured above
    it, provided that the interface has at least one IP
    address configured. Gratuitous ARPs issued for VLAN
    interfaces are tagged with the appropriate VLAN id.

    This mode provides fault tolerance. The primary
    option, documented below, affects the behavior of this
    mode.

    balance-xor or 2

    XOR policy: Transmit based on the selected transmit
    hash policy. The default policy is a simple [(source
    MAC address XOR'd with destination MAC address) modulo
    slave count]. Alternate transmit policies may be
    selected via the xmit_hash_policy option, described
    below.

    This mode provides load balancing and fault tolerance.

    broadcast or 3

    Broadcast policy: transmits everything on all slave
    interfaces. This mode provides fault tolerance.

    802.3ad or 4

    IEEE 802.3ad Dynamic link aggregation. Creates
    aggregation groups that share the same speed and
    duplex settings. Utilizes all slaves in the active
    aggregator according to the 802.3ad specification.

    Slave selection for outgoing traffic is done according
    to the transmit hash policy, which may be changed from
    the default simple XOR policy via the xmit_hash_policy
    option, documented below. Note that not all transmit
    policies may be 802.3ad compliant, particularly in
    regards to the packet mis-ordering requirements of
    section 43.2.4 of the 802.3ad standard. Differing
    peer implementations will have varying tolerances for
    noncompliance.

    Prerequisites:

    1. Ethtool support in the base drivers for retrieving
    the speed and duplex of each slave.

    2. A switch that supports IEEE 802.3ad Dynamic link
    aggregation.

    Most switches will require some type of configuration
    to enable 802.3ad mode.
    http://www.cyberciti.biz/howto/quest...iver-howto.php
    Last edited by j17sparky; 11th February 2010 at 05:55 PM.

  6. Thanks to j17sparky from:

    jsnetman (11th February 2010)

SHARE:
+ Post New Thread

Similar Threads

  1. teaming intel nics
    By projector1 in forum How do you do....it?
    Replies: 5
    Last Post: 24th November 2009, 11:17 AM
  2. Teaming network cards for Citrix
    By KWestos in forum Thin Client and Virtual Machines
    Replies: 2
    Last Post: 19th May 2009, 10:20 AM
  3. Teaming Network Cards
    By KWestos in forum Wireless Networks
    Replies: 3
    Last Post: 14th May 2009, 10:54 PM
  4. Teaming the Intel NIC
    By kanagk in forum Wireless Networks
    Replies: 5
    Last Post: 2nd March 2009, 04:45 PM
  5. Teaming Intel NICs to a Netgear GSM7224 L2 switch
    By tjb in forum Wireless Networks
    Replies: 6
    Last Post: 5th August 2008, 12:53 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •