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

Fiber data modelling: multi-strand cables, port types #4558

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

Originally created by @robbat2 on GitHub (Feb 12, 2021).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.10.4

Proposed Functionality

Improve the PortType & CableType choices to capture more detail in high-density cabling.
MPO connectors come in multiple densities, and connector variations, which must be mated correctly for intended functionality.

  • Fiber cabling should be expanded to include number of fibers & polarity (A/B/C/D)
  • MPO connectors should capture male/female and fiber count
  • Counts: 8,12,16,24,32,48,72,96,144

Use Case

Be able to accurate model advanced fiber types.

Database Changes

Probably need to debate this part; some of this absolutely could be implemented with just more port types, and more cable types, but is that the right way long-term? Should ports and cables get extra fields instead?

External Dependencies

None

Originally created by @robbat2 on GitHub (Feb 12, 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.6.9 * NetBox version: 2.10.4 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Improve the PortType & CableType choices to capture more detail in high-density cabling. MPO connectors come in multiple densities, and connector variations, which must be mated correctly for intended functionality. - Fiber cabling should be expanded to include number of fibers & polarity (A/B/C/D) - MPO connectors should capture male/female and fiber count - Counts: 8,12,16,24,32,48,72,96,144 <!-- 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 Be able to accurate model advanced fiber types. <!-- 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 Probably need to debate this part; some of this absolutely could be implemented with just more port types, and more cable types, but is that the right way long-term? Should ports and cables get extra fields instead? <!-- 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 added the pending closure label 2025-12-29 18:37:36 +01:00
adam closed this issue 2025-12-29 18:37:36 +01:00
adam commented 2025-12-29 18:37:36 +01:00
Author
Owner
Copy Link

@BarbarossaTM commented on GitHub (Apr 1, 2021):

This might be an option to model patch panels as well if you attach a multi-strand cable with say 48 cores (-> 1 rear port) to 24 LC/SC duplex front ports. Then you have only one cable between the panels which happens to model reality as well. :)

@BarbarossaTM commented on GitHub (Apr 1, 2021): This might be an option to model patch panels as well if you attach a multi-strand cable with say 48 cores (-> 1 rear port) to 24 LC/SC duplex front ports. Then you have only one cable between the panels which happens to model reality as well. :)
adam commented 2025-12-29 18:37:36 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 1, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 1, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:37:36 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 2, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jul 2, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure
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#4558
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?