Skip to content

[ansible][minigraph] add support for adding autonegotiation in minigraph templates and fanout EOS (#13990)#15196

Merged
wangxin merged 3 commits intosonic-net:202311from
vdahiya12:vdahiya-fix-202311-pr1
Oct 29, 2024
Merged

[ansible][minigraph] add support for adding autonegotiation in minigraph templates and fanout EOS (#13990)#15196
wangxin merged 3 commits intosonic-net:202311from
vdahiya12:vdahiya-fix-202311-pr1

Conversation

@vdahiya12
Copy link
Copy Markdown
Contributor

@vdahiya12 vdahiya12 commented Oct 26, 2024

cherry-pick #13990
cherry-pick #15134
cherry-pick #15004

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

Description of PR

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405

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

…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 <[email protected]>
…ellanox and add EOS 7260 template changes (sonic-net#15004)

Signed-off-by: Vaibhav Dahiya <[email protected]>
…toneg enabled but the topo file does not contain autoneg interfaces (sonic-net#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 <[email protected]>
@wangxin wangxin merged commit 37b0993 into sonic-net:202311 Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants