Configuring on-stick and LAG/LACP [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick [2024/09/26 15:29] – created - external edit 127.0.0.1en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick [2026/02/02 14:45] (current) – [Applying balancing to outgoing LAG traffic] elena.krasnobryzh
Line 134: Line 134:
 ====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:
Line 184: Line 184:
 in_dev=subs1:subs2 in_dev=subs1:subs2
 out_dev=inet1:inet2</code> out_dev=inet1:inet2</code>
 +
 +=====Diagnosis=====
 +LACP diagnostics is performed using the pcap entry. To do this, the parameter ''pcap'' must be added to the LAG description.\\
 +Parameter values: 
 +  * on — enable pcap recording
 +  * off — disable pcap recording
 +<code bash>
 +# tracing (writing to pcap) of LACP packets of the given LAG
 +    #pcap=on
 +</code>
 +
 +<note important>Logging is enabled via the ''bras_trace'' parameter. See the [[en:dpi:bras_bng:cli:bras_l2_vlan_trace]] section for possible values.</note>