| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick [2026/02/02 14:44] – old revision restored (2025/05/23 14:02) elena.krasnobryzh | en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick [2026/05/14 14:02] (current) – [Configuring LAG] elena.krasnobryzh |
|---|
| LAGs can include either regular ports or on-stick ports, no mixing is allowed. LAG on on-stick is organized on the base (physical) port. LAG is implemented in fastDPI at logical level: there is no single bond device, inside fastDPI work is done with ports as before. | LAGs can include either regular ports or on-stick ports, no mixing is allowed. LAG on on-stick is organized on the base (physical) port. LAG is implemented in fastDPI at logical level: there is no single bond device, inside fastDPI work is done with ports as before. |
| |
| <note important>The maximum number of ports in a LAG is 12.</note> | <note important>The maximum number of ports in a LAG is 18.</note> |
| |
| 3 different configurations are possible: | 3 different configurations are possible: |
| ''system_id'' - MAC address is the ''system_id'' of this LAG. If not specified, "arp_mac" is used.\\ | ''system_id'' - MAC address is the ''system_id'' of this LAG. If not specified, "arp_mac" is used.\\ |
| ''priority'' - system priority for this LAG, number in the range 1 - 65535, default is 32768.\\ | ''priority'' - system priority for this LAG, number in the range 1 - 65535, default is 32768.\\ |
| ''short_timeout'' - short (off) or long (on) LACP timeout. | ''short_timeout'' - short (on) or long (off) LACP timeout. |
| |
| ====Applying balancing to outgoing LAG traffic==== | ====Applying balancing to outgoing LAG traffic==== |
| The type of the applied balancing algorithm is specified by the ''lag.balance_algo'' parameter: | The type of the applied balancing algorithm is specified by the ''lag.balance_algo'' parameter: |
| * ''0'' - balancing by internal ''session_id'' (default balancing). The ''session_id'' is used as the hash. | * ''-1'' — without load balancing — the packet is sent to the paired bridge port |
| * ''1'' - no balancing - the packet will be sent to the paired bridge port. | * ''0'' (default) — load balancing by internal ''session_id'' (default balancing). ''session_id'' is used as the hash |
| * ''2'' - hash from ''flow key <srcIP, dstIP, srcPort, dstPort, proto>''. If there is no flow - balance by ''session_id'' | * ''1'' — hash based on ''flow key <srcIP, dstIP, srcPort, dstPort, proto>''. if there is no ''flow'', balancing is performed by ''session_id'' |
| | |
| Additional hash configuration parameters in the ''lag'' section: ''hash_seed'', ''hash_offset'', ''hash_bits''\\ How many significant bits we take from the 64-bit hash during balancing. The balancing algorithm in the general case looks like this: | Additional hash configuration parameters in the ''lag'' section: ''hash_seed'', ''hash_offset'', ''hash_bits''\\ How many significant bits we take from the 64-bit hash during balancing. The balancing algorithm in the general case looks like this: |
