Forward Error Correction on Interfaces #11250

New Issue

adam · 2025-12-29T21:42:27+01:00

adam commented

2025-12-29 21:42:27 +01:00

Originally created by @DonGiovanni83 on GitHub (Jun 2, 2025).

NetBox version

v4.2.8

Feature type

Data model extension

Proposed functionality

I propose adding a new fec_mode field to the dcim.models.device_components.Interface model. This field will allow users to define the Forward Error Correction (FEC) mode for a given interface. The field will be a nullable CharField with the following choices:

FC-FEC (FEC-74, as defined in IEEE 802.3 Clause 74)
RS-FEC (FEC-91, as defined in IEEE 802.3 Clause 91)
Auto (for auto-negotiation)

This new field should also be available in the GraphQL API.

Use case

This feature enables interface-specific FEC mode configuration, which is sometimes essential for network device configuration. Modern transceivers and switch platforms often require explicit FEC configuration to ensure compatibility and performance. By incorporating fec_mode into NetBox, users can drive consistent configuration across their infrastructure using NetBox as the source of truth.

Our concrete use case at Puzzle ITC is to match explicit FEC modes from the ISP and between devices from different vendors and platforms. See the following blog post for more context on how we manage these devices:
https://www.puzzle.ch/blog/2025/01/09/automating-networks-switches-start-of-the-journey

Database changes

A new nullable CharField will be added to the Interface model in dcim.models.device_components.

Field name: fec_mode
Choices: Auto, FC-FEC, RS-FEC
default: None
Nullable: yes

Included in the GraphQL API and forms similarly to the duplex field.

External dependencies

None

Originally created by @DonGiovanni83 on GitHub (Jun 2, 2025). ### NetBox version v4.2.8 ### Feature type Data model extension ### Proposed functionality I propose adding a new `fec_mode` field to the `dcim.models.device_components.Interface model`. This field will allow users to define the Forward Error Correction (FEC) mode for a given interface. The field will be a nullable `CharField` with the following choices: - `FC-FEC` (FEC-74, as defined in IEEE 802.3 Clause 74) - `RS-FEC` (FEC-91, as defined in IEEE 802.3 Clause 91) - `Auto` (for auto-negotiation) This new field should also be available in the GraphQL API. ### Use case This feature enables interface-specific FEC mode configuration, which is sometimes essential for network device configuration. Modern transceivers and switch platforms often require explicit FEC configuration to ensure compatibility and performance. By incorporating `fec_mode` into NetBox, users can drive consistent configuration across their infrastructure using NetBox as the source of truth. Our concrete use case at Puzzle ITC is to match explicit FEC modes from the ISP and between devices from different vendors and platforms. See the following blog post for more context on how we manage these devices: https://www.puzzle.ch/blog/2025/01/09/automating-networks-switches-start-of-the-journey ### Database changes A new nullable `CharField` will be added to the `Interface` model in `dcim.models.device_components`. Field name: `fec_mode` Choices: `Auto`, `FC-FEC`, `RS-FEC` default: `None` Nullable: yes Included in the GraphQL API and forms similarly to the duplex field. ### External dependencies None

adam added the type: feature label 2025-12-29 21:42:27 +01:00

adam closed this issue

2025-12-29 21:42:27 +01:00

adam commented

2025-12-29 21:42:27 +01:00

@DonGiovanni83 commented on GitHub (Jun 2, 2025):

I'd be happy to own this issue and submit an implementation of the feature.

@DonGiovanni83 commented on GitHub (Jun 2, 2025): I'd be happy to own this issue and submit an implementation of the feature.

adam commented

2025-12-29 21:42:27 +01:00

@jnovinger commented on GitHub (Jun 5, 2025):

@DonGiovanni83, thank you for submitting your idea. This falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.

FWIW, this can be achieved using a custom field and a custom choice set.

@jnovinger commented on GitHub (Jun 5, 2025): @DonGiovanni83, thank you for submitting your idea. This falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding. FWIW, this can be achieved using a [custom field](https://netbox.readthedocs.io/en/stable/customization/custom-fields/) and a [custom choice set](https://netbox.readthedocs.io/en/stable/customization/custom-fields/#custom-selection-fields).

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#11250