Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:dpi:dpi_components:platform:dpi_inst_spec:dpi_lag:start [2024/01/26 11:37] – atereschenko | en:dpi:dpi_components:platform:dpi_inst_spec:dpi_lag:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Bypass Work at the aggregated channels Etherchannel/ | ||
| - | {{indexmenu_n> | ||
| - | 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: | ||
| - | < | ||
| - | 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 < | ||
| - | 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:// | ||
| - | or tuning the LACP (fast switchover). | ||