Add interface-type 1000BaseBX20-D, 1000BaseBX20-U and 1000BaseBX40-D 1000BaseBX40-U #1046

New Issue

MrUnknownDE · 2026-04-05T20:03:16+02:00

MrUnknownDE commented

2026-04-05 20:03:16 +02:00

Originally created by @xkilian on 10/16/2025

NetBox version

v4.4.2

Feature type

Data model extension

Proposed functionality

Add new interface types that are commonly used related to 1000BaseBX.

1000BaseBX20-D
1000BaseBX20-U
1000BaseBX40-D
1000BaseBX40-U
10GBaseBX20-D
10GBaseBX20-U
10GBaseBX40-D
10GBaseBX40-U

Use case

Commnly used in enterprise environments with Cisco, Alcatel and other vendors supported SFPs.
The SFPs are physical different for U and D as they use two different wavelengths for transmit and receive.
It is important to know which type of 1000BaseX SFP is slotted in the equipement,1000BaseBX is a general term that means either a 1000BaseBX-U or 1000BaseBX-D.

As stated below in the comments, 4.4.1 now supports 1000BaseBX-D and U, but I will leave the description above for reference.

Even though they are not an official standard, they are standard in the sense that they are generally available from most manufacturers and need to be tracked the same way as the base case (10GbaseBX-U/D and 1000BaseBX-U/D).

Database changes

Announce that users should migrate their 1000BaseBX interfaces to the appropriate 1000BaseBX-D or U.
Eventually deprecate 1000BaseBX.

External dependencies

No response

*Originally created by @xkilian on 10/16/2025* ### NetBox version v4.4.2 ### Feature type Data model extension ### Proposed functionality Add new interface types that are commonly used related to 1000BaseBX. 1000BaseBX20-D 1000BaseBX20-U 1000BaseBX40-D 1000BaseBX40-U 10GBaseBX20-D 10GBaseBX20-U 10GBaseBX40-D 10GBaseBX40-U ### Use case Commnly used in enterprise environments with Cisco, Alcatel and other vendors supported SFPs. The SFPs are physical different for U and D as they use two different wavelengths for transmit and receive. It is important to know which type of 1000BaseX SFP is slotted in the equipement,1000BaseBX is a general term that means either a 1000BaseBX-U or 1000BaseBX-D. As stated below in the comments, 4.4.1 now supports 1000BaseBX-D and U, but I will leave the description above for reference. Even though they are not an official standard, they are standard in the sense that they are generally available from most manufacturers and need to be tracked the same way as the base case (10GbaseBX-U/D and 1000BaseBX-U/D). ### Database changes Announce that users should migrate their 1000BaseBX interfaces to the appropriate 1000BaseBX-D or U. Eventually deprecate 1000BaseBX. ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-05 20:03:16 +02:00

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 pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed 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 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 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 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#1046