-
Notifications
You must be signed in to change notification settings - Fork 648
Permanent isolate a fabric port if it repeatedly flapping. #3933
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Permanent isolate a fabric port if it repeatedly flapping. #3933
Conversation
…the isolate and unisolate states.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…the isolate and unisolate states. Signed-off-by: jfeng <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…the isolate and unisolate states. Signed-off-by: jfeng <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…the isolate and unisolate states. Signed-off-by: jfeng <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…the isolate and unisolate states. Signed-off-by: jfeng <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…the isolate and unisolate states. Signed-off-by: jfeng <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
vmittal-msft
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Are CLI changes already available to isolate/unisolate link manually ?
|
@jfeng-arista please rebase |
yes, already there |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
If a fabric port repeatedly and rapidly transitions between the isolate and unisolate states, resulting in instability, the algorithm places the link in a permanent isolated state. Currently, the threshold for triggering this condition is when a link flaps three times within a two-hour period.
Recovery from this state requires manual user intervention via a CLI command:
config fabric port unisolate -n asicX --force
HLD change is at:
sonic-net/SONiC#2085
What I did
Why I did it
How I verified it
Details if related