diff --git a/doc/Incremental IP LAG Update.md b/doc/Incremental IP LAG Update.md index 5a5d223623c..7ec77cbf033 100644 --- a/doc/Incremental IP LAG Update.md +++ b/doc/Incremental IP LAG Update.md @@ -100,6 +100,7 @@ PORTCHANNEL|{{port_channel_name}} "mtu": {{mtu_value}} "min_links": {{min_links_value}} "fall_back": {{true|false}} + "fast_rate": {{true|false}} ``` ##### Schema ``` diff --git a/doc/incremental-update-ip-lag/Incremental IP LAG Update.md b/doc/incremental-update-ip-lag/Incremental IP LAG Update.md index 87342f6905e..7006f652d17 100644 --- a/doc/incremental-update-ip-lag/Incremental IP LAG Update.md +++ b/doc/incremental-update-ip-lag/Incremental IP LAG Update.md @@ -96,6 +96,7 @@ PORTCHANNEL|{{port_channel_name}} "mtu": {{mtu_value}} "min_links": {{min_links_value}} "fall_back": {{true|false}} + "fast_rate": {{true|false}} ``` #### 2.1.4 PORTCHANNEL_INTERFACE Table ``` diff --git a/doc/mclag/MCLAG_Enhancements_HLD.md b/doc/mclag/MCLAG_Enhancements_HLD.md index ded353c3522..c6dd36d1e81 100644 --- a/doc/mclag/MCLAG_Enhancements_HLD.md +++ b/doc/mclag/MCLAG_Enhancements_HLD.md @@ -399,6 +399,8 @@ In the current implementation, in normal operation, a port isolation filter is a In this enhancement, acknowledgements are added to interface state notifications in ICCP, and these are used to ensure that the remote filter is applied before enabling traffic on the upcoming MCLAG member interface(s), thereby eliminating the possibility of loops and duplicates. +By default LACP use slow rate, in this case keep alive messages send every 30 seconds and linkdown will be detected in 60-90 seconds, so traffic can be lost during this time. LACP also has fast rate, in this case keep alive messages send every 1 second and linkdown will be detected in 2-3 seconds, so it can significantly reduce downtime. LACP rate can be configured on [portchannel](https://github.com/novikauanton/sonic-utilities/blob/feature/add-lacp-rate-to-portchannel/doc/Command-Reference.md#portchannel-config-commands). + ### 3.3.2 MCLAG configuration change handling ICCP is extended to dynamically handle changes in MCLAG configurations. In the current implementation, MCLAG config attributes local ip, peer ip, peer interface and MCLAG interface configuration has to be done prior to bringing up ICCP docker. To handle configuration changes, MclagSyncd subscribes to CONFIG_DB MCLAG changes, saves configuration data in internal cache and notifies ICCPd. In this enhancement, Pre-provisioning support for MCLAG interfaces and peer interfaces is added.