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

ST split fiber to same ports #4517

New Issue
Closed
opened 2025-12-29 18:36:54 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:36:54 +01:00
Owner
Copy Link

Originally created by @nikor30 on GitHub (Jan 29, 2021).

Environment

  • Python version: 3
  • NetBox version: v2.10.3

Proposed Functionality

Sometimes, it is necessary to indicate that one cable (fiber cable) in a switch is connected to two different ports in a patch panel. It should be possible to do that. You can see more information in the "Use Case" section.
Use Case

Use Case

One fiber cable on one switch interface is connected to port1 in the patch panel but the second fiber cable is connected to port4 in the patch panel. We can fill this situation in NetBox. This is often habbening on ST panels etc.

grafik

Database Changes

External Dependencies

Originally created by @nikor30 on GitHub (Jan 29, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3 * NetBox version: v2.10.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Sometimes, it is necessary to indicate that one cable (fiber cable) in a switch is connected to two different ports in a patch panel. It should be possible to do that. You can see more information in the "Use Case" section. Use Case <!-- 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 One fiber cable on one switch interface is connected to port1 in the patch panel but the second fiber cable is connected to port4 in the patch panel. We can fill this situation in NetBox. This is often habbening on ST panels etc. ![grafik](https://user-images.githubusercontent.com/4319444/106306913-fc0b9f00-625e-11eb-9b6f-02a8fe298998.png) <!-- 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 <!-- 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
adam closed this issue 2025-12-29 18:36:54 +01:00
adam commented 2025-12-29 18:36:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 29, 2021):

It should be possible to do that.

This feature request is not actionable without a detailed implementation proposal. Please elaborate on the specific data model changes being proposed.

@jeremystretch commented on GitHub (Jan 29, 2021): > It should be possible to do that. This feature request is not actionable without a detailed implementation proposal. Please elaborate on the specific data model changes being proposed.
adam commented 2025-12-29 18:36:55 +01:00
Author
Owner
Copy Link

@nikor30 commented on GitHub (Feb 9, 2021):

Hi, a what ? Can you give me a sample how the implementation proposal should look like ?

Regards Niko

@nikor30 commented on GitHub (Feb 9, 2021): Hi, a what ? Can you give me a sample how the implementation proposal should look like ? Regards Niko
adam commented 2025-12-29 18:36:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 17, 2021):

There are hundreds (if not thousands) of feature requests here on GitHub that you can use as examples. I'm closing this for now due to the lack of activity, but you're welcome to request that it be reopened if you put the time into drafting a sufficiently detailed proposal.

@jeremystretch commented on GitHub (Mar 17, 2021): There are hundreds (if not thousands) of feature requests here on GitHub that you can use as examples. I'm closing this for now due to the lack of activity, but you're welcome to request that it be reopened if you put the time into drafting a sufficiently detailed proposal.
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
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#4517
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?