CSCwu34390 CX Script: Added new rule to check if Fabric BFD is enable…#393
Open
weinjason wants to merge 1 commit into
Open
CSCwu34390 CX Script: Added new rule to check if Fabric BFD is enable…#393weinjason wants to merge 1 commit into
weinjason wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…d on ISIS
Fabric BFD (BFD on ISIS) is not recommended,. The operational benefit of enabling Fabric BFD is minimal to none, while the potential adverse impact is significantly higher. The key reasons are outlined below:
ISIS runs over directly connected sub-interfaces
In a leaf-spine fabric, ISIS peers are directly connected sub-interfaces. If a peer device (leaf or spine) goes down, the physical link also goes down, which triggers Layer-1 convergence. In such scenarios—representing the vast majority of failure cases—BFD does not provide any additional convergence benefit.
Risk of false BFD flaps:
BFD is susceptible to false flaps even when there is no actual network path issue. This can occur when BFD packets do not receive sufficient CPU cycles, especially during periods of high CPU utilization by other processes (for example, during tech-support collections). Such false BFD flaps directly impact ISIS adjacencies. Since ISIS is a critical control-plane protocol for the entire fabric, instability at this level can have a widespread and severe impact across the data-center network
Solution:
In pre-upgrade script, added new rule to check if Fabric BFD is enabled on ISIS. If it is enabled, fail the validation and recommend the user to disable it before upgrade or downgrade.