Additionnal speed for infiniband choices. Adding the 4x and more. #393

New Issue

MrUnknownDE · 2026-04-05T16:29:12+02:00

MrUnknownDE commented

2026-04-05 16:29:12 +02:00

Originally created by @lefebric on 2/9/2026

NetBox version

v4.5.2

Feature type

Data model extension

Proposed functionality

Hi, in the choices for Infiniband, could the 4x be added to the choices. Infiniband almost always consider the 4x speed by default. See the roadmap for IB ( https://www.infinibandta.org/infiniband-roadmap/ ). The choices.py file could look like:

    TYPE_INFINIBAND_EDR = 'infiniband-edr'
    TYPE_INFINIBAND_EDR4x = 'infiniband-edr4x'
    TYPE_INFINIBAND_HDR = 'infiniband-hdr'
    TYPE_INFINIBAND_HDR4x = 'infiniband-hdr4x'
    TYPE_INFINIBAND_NDR = 'infiniband-ndr'
    TYPE_INFINIBAND_NDR4x = 'infiniband-ndr4x'

                (TYPE_INFINIBAND_EDR, 'EDR (25 Gbps)'),
                (TYPE_INFINIBAND_EDR4x, 'EDR x4 (100 Gbps)'),
                (TYPE_INFINIBAND_HDR, 'HDR (50 Gbps)'),
                (TYPE_INFINIBAND_HDR4x, 'HDR x4 (200 Gbps)'),
                (TYPE_INFINIBAND_NDR, 'NDR (100 Gbps)'),
                (TYPE_INFINIBAND_NDR4x, 'NDR x4 (400 Gbps)'),

I understand some of this was rejected in the past due to lack evidence of these speed, I'm hopping with the road-map would be be sufficient. To future proof the infiniband speed XDR, GDR and LDR should be added too and to be really thorough I suggest adding the 2x, 8x and 16x speed too, sort of like

                (TYPE_INFINIBAND_NDR, 'NDR (100 Gbps)'),
                (TYPE_INFINIBAND_NDR2x, 'NDR x2 (200 Gbps)'),
                (TYPE_INFINIBAND_NDR4x, 'NDR x4 (400 Gbps)'),
                (TYPE_INFINIBAND_NDR8x, 'NDR x8 (800 Gbps)'),
                (TYPE_INFINIBAND_NDR16x, 'NDR x16 (1600 Gbps)'),

For all the "DR" speed. Seeing how many were added for Ethernet Speed, I don't see why Infiniband shouldn't have all the choices too.

As an extra note, the base speed for XDR is 200 Gbps, not 250Gbps has it is now in the netbox/netbox/dcim/choices.py file

Use case

This will allow user of netbox to properly document devices with Infiniband network. In A network it is possible to have a switch with with HDR4x (200Gbps) ports and connect via a split cable to 2 servers with HDR2x (100Gbps). But with infiniband, it is not recommended to mix "DR's" so connecting to servers with the same cable to a server with EDR4x (100Gbps) could work but would not be advisable. I got an angry call by a boss checking inventory and because my choices were limited to ether EDR (25Gbps) or NDR (100Gbps) for the infiniband card, and got confused because the card is and EDR4x so either the speed was not right or the "DR" was not right.

Database changes

This will allow user of netbox to properly document devices with Infiniband network. In A network it is possible to have a switch with with HDR4x (200Gbps) ports and connect via a split cable to 2 servers with HDR2x (100Gbps). But with infiniband, it is not recommended to mix "DR's" so connecting to servers with the same cable to a server with EDR4x (100Gbps) could work but would not be advisable. I got an angry call by a boss checking inventory and because my choices were limited to ether EDR (25Gbps) or NDR (100Gbps) for the infiniband card, and got confused because the card is and EDR4x so either the speed was not right or the "DR" was not right.

External dependencies

No response

*Originally created by @lefebric on 2/9/2026* ### NetBox version v4.5.2 ### Feature type Data model extension ### Proposed functionality Hi, in the choices for Infiniband, could the 4x be added to the choices. Infiniband almost always consider the 4x speed by default. See the roadmap for IB ( https://www.infinibandta.org/infiniband-roadmap/ ). The choices.py file could look like: ``` TYPE_INFINIBAND_EDR = 'infiniband-edr' TYPE_INFINIBAND_EDR4x = 'infiniband-edr4x' TYPE_INFINIBAND_HDR = 'infiniband-hdr' TYPE_INFINIBAND_HDR4x = 'infiniband-hdr4x' TYPE_INFINIBAND_NDR = 'infiniband-ndr' TYPE_INFINIBAND_NDR4x = 'infiniband-ndr4x' (TYPE_INFINIBAND_EDR, 'EDR (25 Gbps)'), (TYPE_INFINIBAND_EDR4x, 'EDR x4 (100 Gbps)'), (TYPE_INFINIBAND_HDR, 'HDR (50 Gbps)'), (TYPE_INFINIBAND_HDR4x, 'HDR x4 (200 Gbps)'), (TYPE_INFINIBAND_NDR, 'NDR (100 Gbps)'), (TYPE_INFINIBAND_NDR4x, 'NDR x4 (400 Gbps)'), ``` I understand some of this was rejected in the past due to lack evidence of these speed, I'm hopping with the road-map would be be sufficient. To future proof the infiniband speed XDR, GDR and LDR should be added too and to be really thorough I suggest adding the 2x, 8x and 16x speed too, sort of like ``` (TYPE_INFINIBAND_NDR, 'NDR (100 Gbps)'), (TYPE_INFINIBAND_NDR2x, 'NDR x2 (200 Gbps)'), (TYPE_INFINIBAND_NDR4x, 'NDR x4 (400 Gbps)'), (TYPE_INFINIBAND_NDR8x, 'NDR x8 (800 Gbps)'), (TYPE_INFINIBAND_NDR16x, 'NDR x16 (1600 Gbps)'), ``` For all the "DR" speed. Seeing how many were added for Ethernet Speed, I don't see why Infiniband shouldn't have all the choices too. As an extra note, the base speed for XDR is 200 Gbps, not 250Gbps has it is now in the netbox/netbox/dcim/choices.py file ### Use case This will allow user of netbox to properly document devices with Infiniband network. In A network it is possible to have a switch with with HDR4x (200Gbps) ports and connect via a split cable to 2 servers with HDR2x (100Gbps). But with infiniband, it is not recommended to mix "DR's" so connecting to servers with the same cable to a server with EDR4x (100Gbps) could work but would not be advisable. I got an angry call by a boss checking inventory and because my choices were limited to ether EDR (25Gbps) or NDR (100Gbps) for the infiniband card, and got confused because the card is and EDR4x so either the speed was not right or the "DR" was not right. ### Database changes This will allow user of netbox to properly document devices with Infiniband network. In A network it is possible to have a switch with with HDR4x (200Gbps) ports and connect via a split cable to 2 servers with HDR2x (100Gbps). But with infiniband, it is not recommended to mix "DR's" so connecting to servers with the same cable to a server with EDR4x (100Gbps) could work but would not be advisable. I got an angry call by a boss checking inventory and because my choices were limited to ether EDR (25Gbps) or NDR (100Gbps) for the infiniband card, and got confused because the card is and EDR4x so either the speed was not right or the "DR" was not right. ### External dependencies _No response_

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#393