Skip to content

Fix front-end bandwidth unit: Mbps → Gbps in ND GB200-v6 and ND GB300-v6 series#460

Open
Aleda wants to merge 1 commit into
MicrosoftDocs:mainfrom
Aleda:fix/front-end-bandwidth-unit-gbps
Open

Fix front-end bandwidth unit: Mbps → Gbps in ND GB200-v6 and ND GB300-v6 series#460
Aleda wants to merge 1 commit into
MicrosoftDocs:mainfrom
Aleda:fix/front-end-bandwidth-unit-gbps

Conversation

@Aleda

@Aleda Aleda commented May 13, 2026

Copy link
Copy Markdown

Summary

The Network spec tables in nd-gb300-v6-series.md and nd-gb200-v6-series.md label the front-end bandwidth column as Max Front-end Bandwidth (Mbps) with a value of 160. The unit is incorrect — it should be Gbps.

Why

Change

Column header only; values are unchanged.

File Before After
nd-gb300-v6-series.md Max Front-end Bandwidth (Mbps) Max Front-end Bandwidth (Gbps)
nd-gb200-v6-series.md Max Front-end Bandwidth (Mbps) Max Front-end Bandwidth (Gbps)

If the intended bandwidth for this VM family is something other than 160 Gbps, please advise and I can adjust the value as well.

The Network tables for ND GB200-v6 and ND GB300-v6 list Max Front-end Bandwidth with unit (Mbps) while the value 160 refers to Gbps, consistent with comparable HPC/GPU SKUs and the Scale-Up/Scale-Out columns in the same tables. Update the column header unit only; values are unchanged.
@Aleda

Aleda commented May 13, 2026

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 6524789:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/sizes/gpu-accelerated/nd-gb200-v6-series.md ✅Succeeded
articles/virtual-machines/sizes/gpu-accelerated/nd-gb300-v6-series.md ✅Succeeded

For more details, please refer to the build report.

@prmerger-automator

Copy link
Copy Markdown
Contributor

@Aleda : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-regandowner

Copy link
Copy Markdown
Contributor

@iamwilliew

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged C+L Pull Request Review Team label label May 13, 2026
@prmerger-automator

Copy link
Copy Markdown
Contributor

@Aleda : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@github-actions

Copy link
Copy Markdown

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions Bot added the inactive This PR is inactive for more than 14 days label May 27, 2026
@prmerger-automator

Copy link
Copy Markdown
Contributor

@Aleda : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aq-pr-triaged C+L Pull Request Review Team label azure-virtual-machines/svc Change sent to author do-not-merge inactive This PR is inactive for more than 14 days sizes/subsvc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants