-
Notifications
You must be signed in to change notification settings - Fork 819
Handling deletion of Port Channel before deletion of its members #1062
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
Changes from 3 commits
219d78b
828719e
b36079f
b716b97
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4838,6 +4838,8 @@ Command takes two optional arguements given below. | |
| 1) min-links - minimum number of links required to bring up the portchannel | ||
| 2) fallback - true/false. LACP fallback feature can be enabled / disabled. When it is set to true, only one member port will be selected as active per portchannel during fallback mode. Refer https://github.com/Azure/SONiC/blob/master/doc/lag/LACP%20Fallback%20Feature%20for%20SONiC_v0.5.md for more details about fallback feature. | ||
|
|
||
| A portchannel can be deleted only if it does not have any members or the members are already deleted. When a user tries to delete a portchannel and the portchannel still has one or more members that exist, the deletion of portchannel is blocked. | ||
|
||
|
|
||
| - Usage: | ||
| ``` | ||
| config portchannel (add | del) <portchannel_name> [min-links <num_min_links>] [fallback (true | false)] | ||
|
|
||
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.
replace 'Portchannel' with 'Port channel'.