Bypass Work at the aggregated channels Etherchannel/LAG/LACP [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

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

    • Differences

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

    Link to this comparison view

    en:dpi:dpi_components:platform:dpi_inst_spec:dpi_lag [2018/03/22 06:31] – created lexx26en:dpi:dpi_components:platform:dpi_inst_spec:dpi_lag [2024/09/26 15:29] (current) – external edit 127.0.0.1
    Line 1: Line 1:
    -====== dpi_lag ======+====== Bypass Work at the aggregated channels Etherchannel/LAG/LACP ====== 
     +{{indexmenu_n>4}} 
     +Switching to bypass and back occurs link flapping. In that case, when all the links on one DPI platform some switches treate as lost of all connections and as a result LAG is rebuilded.\\ 
     +It is recommended to set delay between switching for switch links one by one: 
     +<code>bypass_link_delay=5</code> 
     +It helps avoid downtime during regular shutdowns and restarts DPI ((at power failure or server failure bypass switch to happen anyway almost simultaneously)) 
     + 
     +Keep in mind that when the connection between dpi and a switch dropped Only one link in the chain of the two kommutator1 <-link1-> dpi <-link2-> kommutator2 is brocken. 
     +This is detected for a long time under standard LACP settings (default is 30 seconds). 
     +For the fast detection of such disconnections should be used additional protocols - [[http://nag.ru/articles/article/23120/lag-i-sredstva-obnarujeniya-problem.html|BFD]], 
     +or tuning the LACP (fast switchover).