Skip to content

Set autoneg off for t0-f2 server-facing ports in golden config#23363

Closed
sdszhang wants to merge 1 commit intosonic-net:masterfrom
sdszhang:link_training_autoneg_off
Closed

Set autoneg off for t0-f2 server-facing ports in golden config#23363
sdszhang wants to merge 1 commit intosonic-net:masterfrom
sdszhang:link_training_autoneg_off

Conversation

@sdszhang
Copy link
Copy Markdown
Contributor

@sdszhang sdszhang commented Mar 26, 2026

Description of PR

Summary:
Update golden config generation for t0-f2-d40u8 topology to set autoneg=off on server-facing ports alongside the existing link_training=on setting.

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Approach

What is the motivation for this PR?

Link training was enabled for t0-f2 server-facing ports in #23107, but autoneg was not explicitly set to off. On some branches which doesn't have the fix for #20030, autoneg can defaults to 'on', causing interfaces to fail to establish links.

How did you do it?

Added config["autoneg"] = "off" for server-facing ports in generate_t0_f2_golden_config_db() in ansible/library/generate_golden_config_db.py.

How did you verify/test it?

Verified on physical testbed with t0-f2-d40u8 topology. Server-facing interfaces come up correctly with autoneg disabled.

Any platform specific information?

Applies to t0-f2-d40u8 topology only.

Supported testbed topology if it is a new test case?

N/A

Documentation

N/A

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@github-actions github-actions bot requested review from r12f, wangxin and xwjiang-ms March 26, 2026 23:24
Signed-off-by: Dashuai Zhang <[email protected]>
@sdszhang sdszhang force-pushed the link_training_autoneg_off branch from 842fa8b to 23a809e Compare March 26, 2026 23:25
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@sdszhang sdszhang added Request for msft-202503 Branch Request for 202511 branch Request to backport a change to 202511 branch labels Mar 27, 2026
@sdszhang
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@sdszhang sdszhang closed this Mar 27, 2026
@sdszhang sdszhang removed Request for msft-202503 Branch Request for 202511 branch Request to backport a change to 202511 branch labels Mar 27, 2026
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