starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Netbox - Adding information for a circuit running through 1 rack to another #577

New Issue
Closed
opened 2025-12-29 16:23:28 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:23:28 +01:00
Owner
Copy Link

Originally created by @himanisilva on GitHub (Dec 13, 2016).

Currently I am adding information on Netbox on Patch ports. There are circuits which runs from one rack to another rack (internally). when trying to add details it is duplicate circuits as I cannot add information on either the A -end or Z-end. Is there anywhere I could add this sort of information in the circuit?

Originally created by @himanisilva on GitHub (Dec 13, 2016). Currently I am adding information on Netbox on Patch ports. There are circuits which runs from one rack to another rack (internally). when trying to add details it is duplicate circuits as I cannot add information on either the A -end or Z-end. Is there anywhere I could add this sort of information in the circuit?
adam closed this issue 2025-12-29 16:23:28 +01:00
adam commented 2025-12-29 16:23:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2016):

Work is underway on #49 to extend the Circuit model to connect two discrete interfaces. However, data circuits typically run between buildings, not adjacent racks. Are you sure you want to represent this connection using a circuit (with a provider and circuit ID)? If you just want to establish a connection, you can create a regular interface connection.

@jeremystretch commented on GitHub (Dec 13, 2016): Work is underway on #49 to extend the Circuit model to connect two discrete interfaces. However, data circuits typically run between buildings, not adjacent racks. Are you sure you want to represent this connection using a circuit (with a provider and circuit ID)? If you just want to establish a connection, you can create a regular interface connection.
adam commented 2025-12-29 16:23:28 +01:00
Author
Owner
Copy Link

@himanisilva commented on GitHub (Dec 13, 2016):

Thank you for your response. The cross connects goes from one rack to another and in a regular interface there are no options to add the cross connect information or the patch panel information. That is the reason why I was trying to use a circuit instead. Also I have Inter rack cross connects which are not used but its for backups. Is there any best practices you suggest for this sort of issue? Your feedback is very helpful as I am new to Netbox.
Thank you.

@himanisilva commented on GitHub (Dec 13, 2016): Thank you for your response. The cross connects goes from one rack to another and in a regular interface there are no options to add the cross connect information or the patch panel information. That is the reason why I was trying to use a circuit instead. Also I have Inter rack cross connects which are not used but its for backups. Is there any best practices you suggest for this sort of issue? Your feedback is very helpful as I am new to Netbox. Thank you.
adam commented 2025-12-29 16:23:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 14, 2016):

You probably want to stick with normal interface connections. We don't yet have the ability to track cross-connect information in NetBox, but it's on the roadmap.

@jeremystretch commented on GitHub (Dec 14, 2016): You probably want to stick with normal interface connections. We don't yet have the ability to track cross-connect information in NetBox, but it's on the roadmap.
adam commented 2025-12-29 16:23:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 15, 2016):

Going to close this out, but if you need any more help please post on the mailing list.

@jeremystretch commented on GitHub (Dec 15, 2016): Going to close this out, but if you need any more help please post on the [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss).
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#577
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?