starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add InfiniBand NDR 400 Gbps port type #11222

New Issue
Closed
opened 2025-12-29 21:42:08 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:42:08 +01:00
Owner
Copy Link

Originally created by @msv837 on GitHub (May 27, 2025).

NetBox version

v3.7.8

Feature type

Other

Proposed functionality

ur QM9700 1U NDR 400Gbps InfiniBand Switch System (https://docs.nvidia.com/networking/display/qm97x0pub/introduction) has 64 ports with NDR 400Gbps, so we would like to have added the options "NDR (400 Gbps)" to the choice list for the Interface Type. Something like

TYPE_INFINIBAND_NDR = 'infiniband-ndr-400'
(TYPE_INFINIBAND_NDR, 'NDR (400 Gbps)'),

in the https://github.com/netbox-community/netbox/blob/main/netbox/dcim/choices.py

I am not sure, if these settings is enough or there are anywhere else, which will need to get a change for it to work.

Use case

For now we have only the options to select "NDR (100 Gbps)" , which is not ideal as the port on the Nvidia switch is "NDR (400 Gbps)", so we would like to have this option added to the Netbox, so we have a clear picture of our servers and swithces.

Database changes

No response

External dependencies

No response

Originally created by @msv837 on GitHub (May 27, 2025). ### NetBox version v3.7.8 ### Feature type Other ### Proposed functionality ur QM9700 1U NDR 400Gbps InfiniBand Switch System (https://docs.nvidia.com/networking/display/qm97x0pub/introduction) has 64 ports with NDR 400Gbps, so we would like to have added the options "NDR (400 Gbps)" to the choice list for the Interface Type. Something like TYPE_INFINIBAND_NDR = 'infiniband-ndr-400' (TYPE_INFINIBAND_NDR, 'NDR (400 Gbps)'), in the https://github.com/netbox-community/netbox/blob/main/netbox/dcim/choices.py I am not sure, if these settings is enough or there are anywhere else, which will need to get a change for it to work. ### Use case For now we have only the options to select "NDR (100 Gbps)" , which is not ideal as the port on the Nvidia switch is "NDR (400 Gbps)", so we would like to have this option added to the Netbox, so we have a clear picture of our servers and swithces. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 21:42:08 +01:00
adam closed this issue 2025-12-29 21:42:08 +01:00
adam commented 2025-12-29 21:42:09 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 29, 2025):

If implementing needs to double-check the spec and do some research, confirm that this is for multi-channel implementation of NDR (4 x 100 Gig) and not GDR.

@arthanson commented on GitHub (May 29, 2025): If implementing needs to double-check the spec and do some research, confirm that this is for multi-channel implementation of NDR (4 x 100 Gig) and not GDR.
adam commented 2025-12-29 21:42:09 +01:00
Author
Owner
Copy Link

@msv837 commented on GitHub (Jun 7, 2025):

Hi Arthur

I had a little vacation and just saw this email now. I can confirm, that it is a multi-channel implementation of NDR (4 x 100 Gig).

Bets regards,
Jørn Jensen
UCPH

From: Arthur Hanson @.>
Sent: 29. maj 2025 19:20
To: netbox-community/netbox @.>
Cc: Jørn Jensen @.>; Author @.>
Subject: Re: [netbox-community/netbox] Add InfiniBand NDR 400 Gbps port type (Issue #19586)

Du får ikke ofte mails fra @.@.>. Få mere at vide om, hvorfor dette er vigtigthttps://aka.ms/LearnAboutSenderIdentification

[https://avatars.githubusercontent.com/u/99642?s=20&v=4]arthanson left a comment (netbox-community/netbox#19586)https://github.com/netbox-community/netbox/issues/19586#issuecomment-2920061494

If implementing needs to double-check the spec and do some research, confirm that this is for multi-channel implementation of NDR (4 x 100 Gig) and not GDR.

—
Reply to this email directly, view it on GitHubhttps://github.com/netbox-community/netbox/issues/19586#issuecomment-2920061494, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASMWZX3VHW3YSVW5FTAMURD3A46TZAVCNFSM6AAAAAB6ADNN66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRQGA3DCNBZGQ.
You are receiving this because you authored the thread.Message ID: @.@.>>

@msv837 commented on GitHub (Jun 7, 2025): Hi Arthur I had a little vacation and just saw this email now. I can confirm, that it is a multi-channel implementation of NDR (4 x 100 Gig). Bets regards, Jørn Jensen UCPH From: Arthur Hanson ***@***.***> Sent: 29. maj 2025 19:20 To: netbox-community/netbox ***@***.***> Cc: Jørn Jensen ***@***.***>; Author ***@***.***> Subject: Re: [netbox-community/netbox] Add InfiniBand NDR 400 Gbps port type (Issue #19586) Du får ikke ofte mails fra ***@***.******@***.***>. Få mere at vide om, hvorfor dette er vigtigt<https://aka.ms/LearnAboutSenderIdentification> [https://avatars.githubusercontent.com/u/99642?s=20&v=4]arthanson left a comment (netbox-community/netbox#19586)<https://github.com/netbox-community/netbox/issues/19586#issuecomment-2920061494> If implementing needs to double-check the spec and do some research, confirm that this is for multi-channel implementation of NDR (4 x 100 Gig) and not GDR. — Reply to this email directly, view it on GitHub<https://github.com/netbox-community/netbox/issues/19586#issuecomment-2920061494>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASMWZX3VHW3YSVW5FTAMURD3A46TZAVCNFSM6AAAAAB6ADNN66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRQGA3DCNBZGQ>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
adam commented 2025-12-29 21:42:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 6, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 6, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:42:10 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 6, 2025):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 6, 2025): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: low pending closure status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11222
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?