Automatic Calculation of effective Logical Link Speeds/Bandwidth #1446

New Issue

MrUnknownDE · 2026-04-06T01:41:48+02:00

MrUnknownDE commented

2026-04-06 01:41:48 +02:00

Originally created by @0lini on 8/15/2025

NetBox version

v.4.3.6

Feature type

Data model extension

Proposed functionality

I propose adding functionality to automatically determine and display the effective speed of logical links (e.g., LAGs, aggregated interfaces, routed links, or cross-site logical connections) by calculating the lowest common denominator across all components in the path.

Use case

In complex networks, the effective speed of a logical link is often limited by the slowest component in its path—this could be an interface, a cable, or any intermediate connection. NetBox currently requires manual entry of logical link speeds, making it easy to miss these bottlenecks.

Automatically calculating the lowest common denominator across all related components would:

Reveal hidden capacity bottlenecks.
Ensure documentation reflects actual performance limits.
Help engineers plan upgrades and troubleshoot issues faster.

Database changes

Introduce a way to store maximum supported speeds for different cable types, with the option to adjust based on length where applicable.

External dependencies

No response

*Originally created by @0lini on 8/15/2025* ### NetBox version v.4.3.6 ### Feature type Data model extension ### Proposed functionality I propose adding functionality to automatically determine and display the effective speed of logical links (e.g., LAGs, aggregated interfaces, routed links, or cross-site logical connections) by calculating the lowest common denominator across all components in the path. ### Use case In complex networks, the effective speed of a logical link is often limited by the slowest component in its path—this could be an interface, a cable, or any intermediate connection. NetBox currently requires manual entry of logical link speeds, making it easy to miss these bottlenecks. Automatically calculating the lowest common denominator across all related components would: - Reveal hidden capacity bottlenecks. - Ensure documentation reflects actual performance limits. - Help engineers plan upgrades and troubleshoot issues faster. ### Database changes Introduce a way to store maximum supported speeds for different cable types, with the option to adjust based on length where applicable. ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-06 01:41:48 +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 type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature 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#1446