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

Automatic Calculation of effective Logical Link Speeds/Bandwidth #11488

New Issue
Closed
opened 2025-12-29 21:45:57 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:45:57 +01:00
Owner
Copy Link

Originally created by @0lini on GitHub (Aug 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 GitHub (Aug 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_
adam added the type: feature label 2025-12-29 21:45:57 +01:00
adam closed this issue 2025-12-29 21:45:57 +01:00
adam commented 2025-12-29 21:45:58 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Aug 21, 2025):

@0lini , thank you for submitting your idea. Although the proposed functionality falls outside the current scope of NetBox's core feature set, it may make a good candidate for a NetBox plugin, and we encourage you to pursue its development and a standalone project. Please reach out via Github Discussions or Slack channel if you need any assistance.

@jnovinger commented on GitHub (Aug 21, 2025): @0lini , thank you for submitting your idea. Although the proposed functionality falls outside the current scope of NetBox's core feature set, it may make a good candidate for a [NetBox plugin](https://netbox.readthedocs.io/en/stable/plugins/), and we encourage you to pursue its development and a standalone project. Please reach out [via Github Discussions or Slack channel](https://github.com/netbox-community/netbox/wiki) if you need any assistance.
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 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#11488
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?