Community discussions

 
losta
just joined
Topic Author
Posts: 2
Joined: Thu Jun 06, 2019 8:00 pm

802.3ad CCR1036 <-> MA5683T

Thu Jun 06, 2019 8:37 pm

Hi, we have a LACP of 2 interfaces between router CCR1036 and OLT Huawei MA5683T

In the router it is seen how in RX we receive traffic correctly from the OLT, but the router in TX we only send through an interface.

The configuration is this:
Router_Bonding.JPG
You do not have the required permissions to view the files attached to this post.
 
sindy
Forum Guru
Forum Guru
Posts: 3811
Joined: Mon Dec 04, 2017 9:19 pm

Re: 802.3ad CCR1036 <-> MA5683T

Sat Jun 08, 2019 10:16 pm

Due to issues many protocol stacks have if packets arrive in non-sequential order, most slave-choosing strategies on the bonded interfaces look at source and destination MAC and IP addresses and even L4 protocol ports and use the same slave link for all frames with the same transmit hash. So with Transmit Hash Policy set to layer2, as probably all frames you send come from just a single source MAC address (of the router) at your end, and all go towards a single destination MAC (of the gateway) at the remote end of the LAG (bond), there is no wonder that all frames use the same slave link. So change the transmit-hash-policy to layer-2-and-3 or maybe even to layer-3-and-4 and you should see both slave links to be used in Tx direction.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.
 
losta
just joined
Topic Author
Posts: 2
Joined: Thu Jun 06, 2019 8:00 pm

Re: 802.3ad CCR1036 <-> MA5683T

Sun Jun 09, 2019 10:04 am

Due to issues many protocol stacks have if packets arrive in non-sequential order, most slave-choosing strategies on the bonded interfaces look at source and destination MAC and IP addresses and even L4 protocol ports and use the same slave link for all frames with the same transmit hash. So with Transmit Hash Policy set to layer2, as probably all frames you send come from just a single source MAC address (of the router) at your end, and all go towards a single destination MAC (of the gateway) at the remote end of the LAG (bond), there is no wonder that all frames use the same slave link. So change the transmit-hash-policy to layer-2-and-3 or maybe even to layer-3-and-4 and you should see both slave links to be used in Tx direction.

Thanks, everything works now correctly.

Who is online

Users browsing this forum: No registered users and 93 guests