rate doesn't match the eth-trunk bandwidth on s5720

chenhui · Created Jun 27, 2019 12:59:23

@user_3445655 hi,
that's normal, when the traffic is from one end user to another user, the traffic will be hashed to one interface, so the rate doesn't exceed the physical link bandwidth.
if you want to hash the traffic to all the links, you could adjust the hash algorythm to per packet rather than per flow. in that scenario, the packets may be out-of-order.

chenhui · Created Jun 27, 2019 12:59:23

@user_3445655 hi,
that's normal, when the traffic is from one end user to another user, the traffic will be hashed to one interface, so the rate doesn't exceed the physical link bandwidth.
if you want to hash the traffic to all the links, you could adjust the hash algorythm to per packet rather than per flow. in that scenario, the packets may be out-of-order.

rate doesn't match the eth-trunk bandwidth on s5720

Recommended answer

Third Party’s Trade Secret

My Followers

Enterprise

Consumer

Corporate

Carriers

rate doesn't match the eth-trunk bandwidth on s5720

Recommended answer

Third Party’s Trade Secret

My Followers