cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
113
Views
5
Helpful
3
Replies
Highlighted
Beginner

802.3ad bonding not distributing traffic.

Hey. I have 2 slaves, eno1 and eth1 configured into bond LACP with layer 2+3. I am having problems with the traffic both on upload and download not distributing. I have tested download from multible sources but it still maxes out at around 1 Gbps in total. The same thing goes for upload where I have tried the upload speed from 4 different sources in different countries. You can see my bonding information below. What I mean with this is that if try to download 1 file, it maxes out at 100MB/s, but when I download 4 different files from different sources each file maxes out at around 25MB/s each.

 

~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

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

802.3ad info
LACP rate: fast
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 00:25:90:fc:74:98
Active Aggregator Info:
        Aggregator ID: 1
        Number of ports: 1
        Actor Key: 9
        Partner Key: 1
        Partner Mac Address: 00:00:00:00:00:00

Slave Interface: eno1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:25:90:fc:74:98
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: churned
Actor Churned Count: 0
Partner Churned Count: 1
details actor lacp pdu:
    system priority: 65535
    system mac address: 00:25:90:fc:74:98
    port key: 9
    port priority: 255
    port number: 1
    port state: 79
details partner lacp pdu:
    system priority: 65535
    system mac address: 00:00:00:00:00:00
    oper key: 1
    port priority: 255
    port number: 1
    port state: 1

Slave Interface: eth0
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 00:25:90:f9:72:52
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: churned
Partner Churn State: churned
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
    system priority: 65535
    system mac address: 00:25:90:fc:74:98
    port key: 0
    port priority: 255
    port number: 2
    port state: 71
details partner lacp pdu:
    system priority: 65535
    system mac address: 00:00:00:00:00:00
    oper key: 1
    port priority: 255
    port number: 1
    port state: 1

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:25:90:fc:74:99
Slave queue ID: 0
Aggregator ID: 3
Actor Churn State: churned
Partner Churn State: churned
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
    system priority: 65535
    system mac address: 00:25:90:fc:74:98
    port key: 9
    port priority: 255
    port number: 3
    port state: 71
details partner lacp pdu:
    system priority: 65535
    system mac address: 00:00:00:00:00:00
    oper key: 1
    port priority: 255
    port number: 1
    port state: 1

 

3 REPLIES 3
VIP Expert

Re: 802.3ad bonding not distributing traffic.

What you describe is often due to a less than optimal hashing algorithm choice.
Beginner

Re: 802.3ad bonding not distributing traffic.

I am using Transmit Hash Policy: layer2+3
VIP Expert

Re: 802.3ad bonding not distributing traffic.

I'm unsure exactly what that hash policy uses, but for example, a common "fail" is traffic between a pair of hosts because MACs and IPs remain the same. Some higher end Cisco switches support also hashing L4, i.e. UDP/TCP port numbers.
CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards