QNAP LACP Trunk on Aruba not working on Outgoing Traffic

Discussion on setting up QNAP NAS products.
Post Reply
mohamed.nasr
First post
Posts: 1
Joined: Sun Aug 25, 2019 11:02 pm

QNAP LACP Trunk on Aruba not working on Outgoing Traffic

Post by mohamed.nasr » Sun Aug 25, 2019 11:11 pm

I have a 2530 Aruba Switch with 4 ports as LACP trunk connected to QNAP with 4 NICs configured as a 802.3ad dynamic trunk When 2 clients try to write or copy a file to the QNAP each one gets 100 MB/s speed so the aggregation is working and i can see in QNAP resource monitor that two NICs are utilized. But when both clients try to copy from the QNAP, then only one NIC is used and both clients are copying data at 50 MB/s.

Is there anything that could cause such behavior? copying to QNAP is fast and using aggregation but copying from QNAP is not?

- Incoming Traffic to QNAP is distributed across more than one NIC (LACP Works) - Outgoing Traffic to QNAP only uses one NIC at all times (LACP not working)

- "cat /proc/net/bonding/bond0" Shows:

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: slow
Min links: 0
Aggregator selection policy (ad_select): stable

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 3
Permanent HW addr: 24:5e:be:27:e1:2b
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 1
Partner Churned Count: 1

Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 3
Permanent HW addr: 24:5e:be:27:e1:2c
Slave queue ID: 0
Aggregator ID: 4
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 1

Post Reply

Return to “Turbo Station Installation & Setup”