bonding question

omghai2u · 08-04-2009, 10:11 AM

i have a server with 2 ethernet ports that im tring to setup mode 4 bonding,

eth2 and eth3 are the bonded ports and they are on the nvidia forcedeth driver

i have setup the HP switch for LACP and the switch recognises the bonded connection.

However, it seems that eth2 is used only for Tx and eth3 is used only for Rx. Its like its running in half duplex?? I can use the connection fine but i cant get them to cooperate in full speed...

This is the bond in rc.inet1.conf , the rest of the interfaces are blank:

Code:

IFNAME[4]="bond0"
IPADDR[4]="10.1.1.3"
NETMASK[4]="255.255.255.0"
USE_DHCP[4]=""
DHCP_HOSTNAME[4]=""

and this is rc.bond which is run by rc.M on boot

Code:

#!/bin/sh

case "$1" in
  'start')
    echo "Starting Bonding..."
    modprobe bonding mode=4 miimon=100
    modprobe forcedeth
    ifconfig bond0 up
    ifenslave bond0 eth2
    ifenslave bond0 eth3
  ;;
  'stop')
    ifconfig bond0 down
    rmmod bonding
    rmmod forcedeth
  ;;
  *)
    echo "Usage: $0 {start|stop}"
  ;;
esac

what am i doing wrong??

ap0calypse · 08-04-2009, 10:24 AM

What does "cat /proc/net/bonding/bond0" give back to you?

omghai2u · 08-04-2009, 10:40 AM

Quote:

Originally Posted by ap0calypse

What does "cat /proc/net/bonding/bond0" give back to you?

Code:

Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
        Aggregator ID: 1
        Number of ports: 2
        Actor Key: 9
        Partner Key: 2
        Partner Mac Address: 00:16:b9:c7:9f:70

Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:1b:fc:d4:24:dc
Aggregator ID: 1

Slave Interface: eth3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:1b:fc:d4:91:09
Aggregator ID: 1

David1357 · 08-04-2009, 10:54 AM

Quote:

Originally Posted by omghai2u

However, it seems that eth2 is used only for Tx and eth3 is used only for Rx. Its like its running in half duplex?

Maybe your problem is the hashing policy. From "linux/Documentation/networking/bonding.txt":

Code:

                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.

Try using "mode=0" (the default) and see if you get better results:

Code:

        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.

omghai2u · 08-06-2009, 10:45 AM

mode 0 works ok, ive tried both hashing modes without any change. also tried a clean install of slackware64. im guessing its just the nvidia forcedeth driver or the hardware that's not totally compatible.