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

Add "splice" type for rear ports #4268

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

Originally created by @JonathonReinhart on GitHub (Nov 11, 2020).

Originally assigned to: @JonathonReinhart on GitHub.

Thanks a lot for building such an awesome tool! This is a minor request.

Environment

  • Python version: v3.? (netbox-docker)
  • NetBox version: v2.9.8

Proposed Functionality

For rear (or front, I suppose) ports, please consider adding a Splice Type under Fiber Optic.

When modeling a typical enterprise copper cable plant, we have patch panels with 8P8C front ports and 110 punch rear ports. This accurately matches the real world.

But fiber patch panels are often installed by splicing the cable run to the back of an e.g. LC connector.

There is no Splice type connector. I'm forced to pick one (e.g. LC), which doesn't reflect the real world. It's not a big deal to work around, but it seems like it wouldn't be too much work to add another type either.

Use Case

When modeling fiber cable plants, there will often be splices.

Consider the most simple case:

  • Rack 1
    • Fiber patch panel 1.1
      • Front port 1: LC connector
      • Rear port 1: Splice
  • Rack 2
    • Fiber patch panel 2.1
      • Front port 1: LC connector
      • Rear port 1: Splice

The two "splice" rear ports would be connected together.

Database Changes

No new models or fields required.

External Dependencies

n/a

Originally created by @JonathonReinhart on GitHub (Nov 11, 2020). Originally assigned to: @JonathonReinhart on GitHub. Thanks a lot for building such an awesome tool! This is a minor request. ### Environment * Python version: v3.? (netbox-docker) * NetBox version: v2.9.8 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality For rear (or front, I suppose) ports, please consider adding a `Splice` Type under `Fiber Optic`. When modeling a typical enterprise copper cable plant, we have patch panels with 8P8C front ports and 110 punch rear ports. This accurately matches the real world. But fiber patch panels are often installed by splicing the cable run to the back of an e.g. LC connector. There is no `Splice` type connector. I'm forced to pick one (e.g. LC), which doesn't reflect the real world. It's not a big deal to work around, but it seems like it wouldn't be too much work to add another type either. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case When modeling fiber cable plants, there will often be splices. Consider the most simple case: - Rack 1 - Fiber patch panel 1.1 - Front port 1: LC connector - Rear port 1: Splice - Rack 2 - Fiber patch panel 2.1 - Front port 1: LC connector - Rear port 1: Splice The two "splice" rear ports would be connected together. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes No new models or fields required. - Add new port type [here](https://github.com/netbox-community/netbox/blob/8ba50d0cf2eeb04ba3cc8b800a142b4bd06c6858/netbox/dcim/choices.py#L816-L832) - Add new choice [here](https://github.com/netbox-community/netbox/blob/8ba50d0cf2eeb04ba3cc8b800a142b4bd06c6858/netbox/dcim/choices.py#L848-L860) - May need to augment [this migration](https://github.com/netbox-community/netbox/blob/3eb2d45e8deedfc71cfba9a3c2f919df760b6dca/netbox/dcim/migrations/0082_3569_port_fields.py) <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies n/a
adam added the status: acceptedtype: feature labels 2025-12-29 18:34:19 +01:00
adam closed this issue 2025-12-29 18:34:19 +01:00
adam commented 2025-12-29 18:34:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 12, 2020):

May need to augment this migration

FYI this isn't necessary: The migration only deals with types that existed before the migration was written.

@jeremystretch commented on GitHub (Nov 12, 2020): > May need to augment this migration FYI this isn't necessary: The migration only deals with types that existed before the migration was written.
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#4268
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?