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

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • ODT export
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • ODT export
  • Backlinks

    • Differences

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

    Link to this comparison view

    Both sides previous revisionPrevious revision
    Next revision    		Previous revision
    en:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick [2026/02/02 13:05] – [LACP port aggregation] elena.krasnobryzhen:dpi:dpi_components:platform:dpi_inst_spec:dpi_onstick [2026/03/19 07:45] (current) – [Configuring LAG] elena.krasnobryzh
    Line 89: Line 89:
     </code> </code>
     Allowable values of the ''lacp'' parameter:\\ Allowable values of the ''lacp'' parameter:\\
    -  * ''-1'' — without load balancing — the packet is sent to the paired bridge port +  * 0 (default) - LACP is disabled, SSG does not hold LAG, but freely skips it 
    -  * ''0'' (default) — load balancing by internal ''session_id''. ''session_id'' is used as the hash +  * 1 - LAG in passive mode: we don't send periodic LACPDUs, but we respond to LACPDUs that arrive 
    -  * ''1'' — hash based on ''flow key <srcIP, dstIP, srcPort, dstPort, proto>''. if there is no ''flow'', balancing is performed by ''session_id''+  * 2 - LAG in active mode: we send periodic LACPDUs.
     <note>The aggregation traces the traffic balancing.</note> <note>The aggregation traces the traffic balancing.</note>
      
    Line 97: Line 97:
     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:
    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: