Skip to content
This repository has been archived by the owner on Nov 13, 2023. It is now read-only.

Support path restoration when leaf-spine links go down #55

Open
ccascone opened this issue Aug 27, 2019 · 2 comments
Open

Support path restoration when leaf-spine links go down #55

ccascone opened this issue Aug 27, 2019 · 2 comments
Assignees
@Yi-Tseng
Labels
enhancement New feature or request

Comments

@ccascone
Copy link
Collaborator

We should see the ECMP group updated with one bucket removed
@ccascone ccascone self-assigned this Aug 27, 2019
@ccascone ccascone added the enhancement New feature or request label Aug 29, 2019
@ccascone ccascone assigned Yi-Tseng and unassigned ccascone Aug 30, 2019
@pudelkoM
Copy link
Contributor

Some deployed bcm and bf binaries are without the SFP fix. This causes crashed when cables are removed.

We should make sure all binaries are up-to-date.

@ccascone
Copy link
Collaborator Author

As of now, path restoration is not supported because the routing app component doesn't compute e2e paths when routing across spines. Packets destinated to other leaves are hashed to all spines, ignoring wether a spine as a link to the destination leaf or not.

@ccascone ccascone changed the title Try failure recovery by unplugging one leaf-spine link Support path restoration when leaf-spine links go down Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Yi-Tseng Yi-Tseng

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Yi-Tseng @ccascone @pudelkoM