Skip to content

[dualtor] multi-nexthop route HLD#1256

Merged
prsunny merged 2 commits intosonic-net:masterfrom
Ndancejic:multi-nexthop-hld
May 3, 2023
Merged

[dualtor] multi-nexthop route HLD#1256
prsunny merged 2 commits intosonic-net:masterfrom
Ndancejic:multi-nexthop-hld

Conversation

@Ndancejic
Copy link
Contributor

Signed-off-by: Nikola Dancejic nikola.dancejic@live.com

Signed-off-by: Nikola Dancejic <nikola.dancejic@live.com>
Ndancejic added a commit to Ndancejic/sonic-swss that referenced this pull request Feb 14, 2023
What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
Ndancejic added a commit to Ndancejic/sonic-swss that referenced this pull request Mar 7, 2023
What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
Ndancejic added a commit to Ndancejic/sonic-swss that referenced this pull request Mar 7, 2023
What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
Ndancejic added a commit to Ndancejic/sonic-swss that referenced this pull request Mar 14, 2023
What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
prsunny pushed a commit to sonic-net/sonic-swss that referenced this pull request Mar 28, 2023
* [muxorch] handling multiple mux nexthops for route

What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256
prsunny pushed a commit to sonic-net/sonic-swss that referenced this pull request Apr 10, 2023
* [muxorch] handling multiple mux nexthops for route

What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
yxieca pushed a commit to sonic-net/sonic-swss that referenced this pull request Apr 19, 2023
* [muxorch] handling multiple mux nexthops for route

What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
@prsunny prsunny merged commit 1c1ab15 into sonic-net:master May 3, 2023
Janetxxx pushed a commit to Janetxxx/sonic-swss that referenced this pull request Nov 10, 2025
* [muxorch] handling multiple mux nexthops for route

What I did: added logic to handle when a route points to a nexthop
group with mux neighbors. In this case, only one active neighbor, or the
tunnel nexthop will be programmed to the ASIC.

Why I did it: having a route with multiple mux neighbors caused a data
loop which lead to packet loss when different neighbors were in
different states.

How I did it: added logic to update routes when a route is changed, a
mux neighbor is changed, or there is a mux state change.

HLD: sonic-net/SONiC#1256

Signed-off-by: Nikola Dancejic <ndancejic@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants