-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[minigraph.py]: Add support for parsing mux cable #5676
[minigraph.py]: Add support for parsing mux cable #5676
Conversation
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
* Previous behavior was to set `mux_cable_connection = 'none'` if the port was not connected to a mux cable Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
do we need to differentiate U and L for a mux cable port? what is the motivation here? can this be true or false? |
@lguohan the minigraph will list the @vdahiya12 for visibility |
retest broadcom please |
@lguohan Can the Cli request to change the active TOR to be U or L, if not we can omit this ? |
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
191b817
retest vsimage please |
Find LogicalLinks in minigraph and parse the port information. A new field called `mux_cable` is added to each port's entry in the Port table in config DB: ``` PORT|Ethernet0: { "alias": "Ethernet4/1" ... "mux_cable": "true" } ``` If a mux cable is present on a port, the value for `mux_cable` will be `"true"`. If no mux cable is present, the attribute will either be omitted (default behavior) or set to `"false"`.
Signed-off-by: Lawrence Lee lawlee@microsoft.com
- Why I did it
- How I did it
Find LogicalLinks in minigraph and parse the port information. A new field called
mux_cable
is added to each port's entry in the Port table in config DB:If a mux cable is present on a port, the value for
mux_cable
will be"true"
. If no mux cable is present, the attribute will either be omitted (default behavior) or set to"false"
.- How to verify it
Run sonic-config-engine tests
- Which release branch to backport (provide reason below if selected)
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)