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

Cable without termination (pre-patched) #6449

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

Originally created by @mchlrv on GitHub (May 4, 2022).

NetBox version

v3.0.8

Feature type

New functionality

Proposed functionality

We pre-patch all our switches in the datacenter with fibers, but they are not terminated anywhere yet. After a new cross connect is requested and terminated at a patch panel, we raise a smart hands and ask the field engineer of the datacenter to patch the new cross connect using our pre-patched and labeled fiber after which the cable is connected.

So it would be helpful to have a functionality to have a cable connected to an interface on a device (switch) but not have it terminated on the B-side yet as this is cable is reserved / planned for future use.

Use case

By allowing this we can already note the cable specifications (type, label, color, length) in Netbox and only have to select a B side once it is being used.

Database changes

  • Add cable status: reserved (future use)
  • Don't make B side mandatory

External dependencies

No response

Originally created by @mchlrv on GitHub (May 4, 2022). ### NetBox version v3.0.8 ### Feature type New functionality ### Proposed functionality We pre-patch all our switches in the datacenter with fibers, but they are not terminated anywhere yet. After a new cross connect is requested and terminated at a patch panel, we raise a smart hands and ask the field engineer of the datacenter to patch the new cross connect using our pre-patched and labeled fiber after which the cable is connected. So it would be helpful to have a functionality to have a cable connected to an interface on a device (switch) but not have it terminated on the B-side yet as this is cable is reserved / planned for future use. ### Use case By allowing this we can already note the cable specifications (type, label, color, length) in Netbox and only have to select a B side once it is being used. ### Database changes - Add cable status: reserved (future use) - Don't make B side mandatory ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:40:51 +01:00
adam closed this issue 2025-12-29 19:40:51 +01:00
adam commented 2025-12-29 19:40:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 5, 2022):

#9102 is currently under development and will result in a significant overhaul of the entire cabling model in NetBox. While we're not taking any additional feature requests in this area at this time, I invite you to experiment with the new model once it has been finalized in the NetBox v3.3 beta (due in August) and provide your feedback prior to the final v3.3 release. Thanks!

@jeremystretch commented on GitHub (May 5, 2022): #9102 is currently under development and will result in a significant overhaul of the entire cabling model in NetBox. While we're not taking any additional feature requests in this area at this time, I invite you to experiment with the new model once it has been finalized in the NetBox v3.3 beta (due in August) and provide your feedback prior to the final v3.3 release. Thanks!
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 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#6449
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?