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

Circuit with two endpoints (and associated cross-connects) #417

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

Originally created by @kirk444 on GitHub (Sep 6, 2016).

Forgive me if I am just misunderstanding how this works, as I am new to netbox. It seems like the "circuits" feature is only really useful for a DIA circuit, or something else with only one endpoint.

The majority of my circuits are from site "A" to site "Z". Each site has a cross-connect associated with it. For example, a wave circuit from Equinix CH2 to Equinix NY4 will have a cross-connect/patch-panel at CH2, and another at NY4. The current implementation seems to limit me to one cross-connect and one patch-panel field.

It seems like a circuit (or at least some subset of circuits) should support an "A" and "Z" side cross-connect (at a minimum, there are situations where one circuit has 3, or even 4, associated cross-connects).

Originally created by @kirk444 on GitHub (Sep 6, 2016). Forgive me if I am just misunderstanding how this works, as I am new to netbox. It seems like the "circuits" feature is only really useful for a DIA circuit, or something else with only one endpoint. The majority of my circuits are from site "A" to site "Z". Each site has a cross-connect associated with it. For example, a wave circuit from Equinix CH2 to Equinix NY4 will have a cross-connect/patch-panel at CH2, and another at NY4. The current implementation seems to limit me to one cross-connect and one patch-panel field. It seems like a circuit (or at least some subset of circuits) should support an "A" and "Z" side cross-connect (at a minimum, there are situations where one circuit has 3, or even 4, associated cross-connects).
adam closed this issue 2025-12-29 16:21:51 +01:00
adam commented 2025-12-29 16:21:52 +01:00
Author
Owner
Copy Link

@zachmoody commented on GitHub (Sep 6, 2016):

You're not missing anything. That feature is on the roadmap in #49 .

@zachmoody commented on GitHub (Sep 6, 2016): You're not missing anything. That feature is on the roadmap in #49 .
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#417
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?