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

Add Fiber-Type "pigtail" #2603

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

Originally created by @tb-killa on GitHub (May 9, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.11

Proposed Functionality

Extend the Fiber Optic inside netbox/dcim/constants.py
with one new Value:

  • PIGTAIL

Use Case

This allows to reproduce an actual physical situation to be found.:

  • front connector is a real connector (LC/LSH/LC/SC/ST)
  • back connector is a pigtail which is spliced to a fiber cable

Database Changes

None.

External Dependencies

None.

Originally created by @tb-killa on GitHub (May 9, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss 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.6 * NetBox version: 2.5.11 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Extend the ``Fiber Optic`` inside ``netbox/dcim/constants.py`` with one new Value: - **PIGTAIL** <!-- 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 This allows to reproduce an actual physical situation to be found.: - front connector is a real connector (LC/LSH/LC/SC/ST) - back connector is a pigtail which is spliced to a fiber cable <!-- 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 None. <!-- 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 None.
adam closed this issue 2025-12-29 18:20:18 +01:00
adam commented 2025-12-29 18:20:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2019):

Are you splicing a female end directly onto each strand of the cable? Can you provide a photo?

@jeremystretch commented on GitHub (May 10, 2019): Are you splicing a female end directly onto each strand of the cable? Can you provide a photo?
adam commented 2025-12-29 18:20:19 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (May 10, 2019):

In our patchpanel we use this confected cable (sample) with open end who would be spliced inside the box to the cable.
https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcR8_-7z5SXRm7a29IecLBRTYUk0Hg8yZpLZFuMbBeLTyt9A4wfG

https://www.lxtelecom.com/images/fiber-optics/splice-tray/st-2d24e-24-cores-fiber-optic-splice-tray-longxing-d.jpg

The cable of the "pigtail" themselves terminate directly on the cable.

@tb-killa commented on GitHub (May 10, 2019): In our patchpanel we use this confected cable (sample) with open end who would be spliced inside the box to the cable. https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcR8_-7z5SXRm7a29IecLBRTYUk0Hg8yZpLZFuMbBeLTyt9A4wfG https://www.lxtelecom.com/images/fiber-optics/splice-tray/st-2d24e-24-cores-fiber-optic-splice-tray-longxing-d.jpg The cable of the "pigtail" themselves terminate directly on the cable.
adam commented 2025-12-29 18:20:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2019):

That's not a panel though. Splicing an end onto a cable just makes a longer cable.

@jeremystretch commented on GitHub (May 10, 2019): That's not a panel though. Splicing an end onto a cable just makes a longer cable.
adam commented 2025-12-29 18:20:19 +01:00
Author
Owner
Copy Link

@tioan commented on GitHub (May 10, 2019):

@tioan commented on GitHub (May 10, 2019): ![](https://www.elektro4000.de/images/product_images/popup_images/Telegaertner-Spleissbox-bestueckt-TNSB-Be-6LCD-50-OM3-198358_0.jpg)
adam commented 2025-12-29 18:20:19 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (May 10, 2019):

If you don't use ready-made connections (patch panel uses cables which have a direct plug at the front and rear), the variant I described is completely normal.

In every patch panel no matter which type of plug there is a socket with a piece of cable which is spliced onto the normal fiber optic multifiber cable by means of the box as protection.

The sense of this FR is to be able to map the right way within Netbox without representing a ST/ST on cable on ST/ST, which is absolutely not the current practice (can actually vary).

@tb-killa commented on GitHub (May 10, 2019): If you don't use ready-made connections (patch panel uses cables which have a direct plug at the front and rear), the variant I described is completely normal. In every patch panel no matter which type of plug there is a socket with a piece of cable which is spliced onto the normal fiber optic multifiber cable by means of the box as protection. The sense of this FR is to be able to map the right way within Netbox without representing a ST/ST on cable on ST/ST, which is absolutely not the current practice (can actually vary).
adam commented 2025-12-29 18:20:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2019):

Here is a typical fiber patch panel:

fiber-patch-panel

Each individual strand is terminated to a male type, which connects to a passive female-to-female coupler housed by the panel. These would be modeled as SC rear ports in NetBox. Patches (also male type) are then connected to the outside of the panel.

How does your use case differ from this?

@jeremystretch commented on GitHub (May 10, 2019): Here is a typical fiber patch panel: ![fiber-patch-panel](https://user-images.githubusercontent.com/13487278/57532086-fb9fd780-7308-11e9-9f4c-344dbf534cb7.jpg) Each individual strand is terminated to a male type, which connects to a passive female-to-female coupler housed by the panel. These would be modeled as SC rear ports in NetBox. Patches (also male type) are then connected to the outside of the panel. How does your use case differ from this?
adam commented 2025-12-29 18:20:20 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (May 10, 2019):

Each individual strand is terminated to a male type, which connects to a passive female-to-female coupler housed by the panel. These would be modeled as SC rear ports in NetBox. Patches (also male type) are then connected to the outside of the panel.

This looks cool but isn´t a normal situation because the type of patch-panel themselve is variable.

All our Patchpanel are loaded with (TYPE) adapters, ready for splicing, with prepared pigtails (per 2 m).
Splice cassettes are hinged, can be easily folded up.

Each of this individual strand is terminated to a pigtail-splice (inside the casetta) housed by the panel. These would be modeled as PIGTAIL rear port in NetBox. where you connect your "Cable" on back to the other side who is the contrary of the first ones.

@tb-killa commented on GitHub (May 10, 2019): > Each individual strand is terminated to a male type, **which connects to a passive female-to-female coupler housed by the panel. These would be modeled as SC rear ports in NetBox.** Patches (also male type) are then connected to the outside of the panel. This looks cool but isn´t a normal situation because the type of patch-panel themselve is variable. All our Patchpanel are loaded with (TYPE) adapters, ready for splicing, with prepared pigtails (per 2 m). Splice cassettes are hinged, can be easily folded up. Each of this individual strand is terminated to a pigtail-splice (inside the casetta) housed by the panel. **These would be modeled as PIGTAIL rear port in NetBox.** where you connect your "Cable" on back to the other side who is the contrary of the first ones.
adam commented 2025-12-29 18:20:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2019):

Still not following. Please provide a photo for reference.

@jeremystretch commented on GitHub (May 10, 2019): Still not following. Please provide a photo for reference.
adam commented 2025-12-29 18:20:20 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (May 10, 2019):

This video show the needing informations
https://youtu.be/rrR6IOZRPb8

@tb-killa commented on GitHub (May 10, 2019): This video show the needing informations https://youtu.be/rrR6IOZRPb8
adam commented 2025-12-29 18:20:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2019):

The video you linked shows exactly what I described.

screenshot

Each individual strand is terminated to a male type, which connects to a passive female-to-female coupler housed by the panel. These would be modeled as SC rear ports in NetBox. Patches (also male type) are then connected to the outside of the panel.

@jeremystretch commented on GitHub (May 10, 2019): The video you linked shows exactly what I described. ![screenshot](https://user-images.githubusercontent.com/13487278/57553579-f3fa2600-733c-11e9-91b4-e8c41669d463.png) > Each individual strand is terminated to a male type, which connects to a passive female-to-female coupler housed by the panel. These would be modeled as SC rear ports in NetBox. Patches (also male type) are then connected to the outside of the panel.
adam commented 2025-12-29 18:20:20 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (May 10, 2019):

This is only one example, I will show you another ones.

@tb-killa commented on GitHub (May 10, 2019): This is only one example, I will show you another ones.
adam commented 2025-12-29 18:20:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2019):

No, this has been resolved. If the model I explained doesn't work for you, NetBox simply does not fit your needs.

@jeremystretch commented on GitHub (May 10, 2019): No, this has been resolved. If the model I explained doesn't work for you, NetBox simply does not fit your needs.
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#2603
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?