[ansible][minigraph] add support for adding autonegotiation in minigraph templates and fanout EOS#13990
Conversation
minigraph templates Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
prgeor
left a comment
There was a problem hiding this comment.
@vdahiya12 do we need more changes to enable AN on EOS?
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
ansible/vars/topo_t0-116.yml
Outdated
| vm_offset: 3 | ||
| DUT: | ||
| autoneg_interfaces: | ||
| intfs: [13, 14, 15, 16, 17, 18, 19, 20] |
There was a problem hiding this comment.
Since auto negotiation needs to be matched between DUT and fanout ports. This definition means that both DUT and fanout configuration need to be updated while deploying minigraph. An extra step needs to be added to after deploy minigraph to configure fanout ports accordingly.
There was a problem hiding this comment.
discussed offline, resolved
There was a problem hiding this comment.
why 8 interfaces? i thought we said half of them an/lt, and half of none an/lt?
There was a problem hiding this comment.
changed it to 4 ports
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
| <a:Name>FECDisabled</a:Name> | ||
| <a:Reference i:nil="true"/> | ||
| <a:Value>True</a:Value> |
There was a problem hiding this comment.
@vdahiya12 disabling FEC when AN is enabled, I would suggest to use msft_an_enabled. Also keep autoneg_enabled for only enabling AN which can be used in future
There was a problem hiding this comment.
@vdahiya12 In future each SKU needs to be updated to parse the device connection if onboarded for AN testbed?
There was a problem hiding this comment.
yes, every template will need to be enhanced
| switchport mode dot1q-tunnel | ||
| switchport access vlan {{ device_port_vlans[inventory_hostname][intf]['vlanids'] }} | ||
| {% if device_conn[inventory_hostname][intf]['speed'] == "100000" %} | ||
| {% if device_conn[inventory_hostname][intf]['speed'] == "100000" and device_conn[inventory_hostname][intf]['autoneg']|lower == "off" %} |
There was a problem hiding this comment.
@vdahiya12 Why are we restricting to 100G only?
There was a problem hiding this comment.
there is no restriction here, only if speed is 100000 and autoneg is off, then we keep fec as reed-solomon
There was a problem hiding this comment.
add the peer device check
There was a problem hiding this comment.
@vdahiya12 prevent configuration of RS FEC if msft_an_lt is enabled?
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (sonic-net#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (sonic-net#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (sonic-net#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
|
@vdahiya12 PR conflicts with 202305 branch |
|
Cherry-pick PR to 202405: #15172 |
|
@vdahiya12 PR conflicts with 202311 branch |
…aph templates and fanout EOS (#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (sonic-net#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (sonic-net#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (sonic-net#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (sonic-net#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…aph templates and fanout EOS (#13990) (#15196) * [ansible][minigraph] add support for adding autonegotiation in minigraph templates and fanout EOS (#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com> * [ansible][minigraph] enhance template for adding autonegotiation in Mellanox and add EOS 7260 template changes (#15004) Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com> * [ansible][minigraph] Fix minigraph template for devices which have autoneg enabled but the topo file does not contain autoneg interfaces (#15134) This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section. Key Changes: * The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None. * This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None. This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
…ph templates and fanout EOS (#13990) (#15197) * [ansible][minigraph] add support for adding autonegotiation in minigraph templates and fanout EOS (#13990) These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible Two things are required for autoneg support 1. autoneg_enabled : True must be enabled in inventory files 2. t0 topo file must have a port list for autoneg Example: intfs : [1, 2, 3, 4, 5, 6, 7, 8] With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com> * [ansible][minigraph] enhance template for adding autonegotiation in Mellanox and add EOS 7260 template changes (#15004) Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com> * [ansible][minigraph] Fix minigraph template for devices which have autoneg enabled but the topo file does not contain autoneg interfaces (#15134) This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section. Key Changes: * The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None. * This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None. This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list Signed-off-by: Vaibhav Dahiya <vdahiya@microsoft.com>
Description of PR
These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible
Two things are required for autoneg support
must be enabled in inventory files
Example:
intfs : [1, 2, 3, 4, 5, 6, 7, 8]
With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation