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

Add Missing Backplane Ethernet Types for Interfaces #9363

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

Originally created by @sleepinggenius2 on GitHub (Mar 16, 2024).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.7.4

Feature type

Data model extension

Proposed functionality

When #10356 was implemented, it seems the IEEE 802.3cb standard was not included for 2.5G and 5G Backplane Ethernet. I propose adding 2.5GBASE-KX and 5GBASE-KR interface types to support this standard.

Use case

Add support for devices using 2.5G and 5G Backplane Ethernet. I came across a device model in our network that is using 2.5G Ethernet across the backplane and found that type was missing. I have not encountered 5G yet, but it seems to make sense to include it as well, as they are both part of the same standard.

Database changes

None

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (Mar 16, 2024). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.7.4 ### Feature type Data model extension ### Proposed functionality When #10356 was implemented, it seems the IEEE 802.3cb standard was not included for 2.5G and 5G Backplane Ethernet. I propose adding 2.5GBASE-KX and 5GBASE-KR interface types to support this standard. ### Use case Add support for devices using 2.5G and 5G Backplane Ethernet. I came across a device model in our network that is using 2.5G Ethernet across the backplane and found that type was missing. I have not encountered 5G yet, but it seems to make sense to include it as well, as they are both part of the same standard. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:49:00 +01:00
adam closed this issue 2025-12-29 20:49:00 +01:00
adam commented 2025-12-29 20:49:00 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Apr 2, 2024):

I just found that the newer cards for the same device do support 5G, so I do have a use case for that as well now.

@sleepinggenius2 commented on GitHub (Apr 2, 2024): I just found that the newer cards for the same device do support 5G, so I do have a use case for that as well now.
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 status: accepted 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#9363
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?