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

Pre-patched cable without termination for future use #7723

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

Originally created by @mchlrv on GitHub (Mar 6, 2023).

NetBox version

v3.4.5

Feature type

New functionality

Proposed functionality

This is basically the reopening of issue #9300 which has been closed due to overhaul of the entire cabling model at that time. Looking at the new model it still doesn't seem possible to define pre-patched cables without a termination point.

We pre-patch all our switches in the datacenter with fibers, but they are not terminated anywhere yet as cross connects will be installed on a request basis. 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 (Mar 6, 2023). ### NetBox version v3.4.5 ### Feature type New functionality ### Proposed functionality This is basically the reopening of issue #9300 which has been closed due to overhaul of the entire cabling model at that time. Looking at the new model it still doesn't seem possible to define pre-patched cables without a termination point. We pre-patch all our switches in the datacenter with fibers, but they are not terminated anywhere yet as cross connects will be installed on a request basis. 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: featurepending closurestatus: under review labels 2025-12-29 20:27:30 +01:00
adam closed this issue 2025-12-29 20:27:30 +01:00
adam commented 2025-12-29 20:27:31 +01:00
Author
Owner
Copy Link

@xkilian commented on GitHub (Mar 6, 2023):

I would suggest a slider to manually choose to remove de B side connection obligation.
This way, the current default remains and is desirable IMO.

@xkilian commented on GitHub (Mar 6, 2023): I would suggest a slider to manually choose to remove de B side connection obligation. This way, the current default remains and is desirable IMO.
adam commented 2025-12-29 20:27:32 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 15, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 15, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:27:32 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 15, 2023):

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 15, 2023): 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 status: under review 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#7723
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?