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 links to other areas #1505

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

Originally created by @xonacs on GitHub (Jan 22, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

We are using the Circuit IDs to also log Power Circuits, IP Bandwidth Circuits etc. Currently, circuits are linked to an A/Z side but cannot be linked to anything else, such as devices, IP prefix etc.

As an example, we have the PDUs which we would like to link to these Power Circuits. We would also like to link such Circuits with the rack numbers.

We tried to add custom fields to racks/devices/prefixes to have this info. To eliminate double entry it would be good if we could choose a drop down list from a list of circuits for a custom field.

Originally created by @xonacs on GitHub (Jan 22, 2018). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> We are using the Circuit IDs to also log Power Circuits, IP Bandwidth Circuits etc. Currently, circuits are linked to an A/Z side but cannot be linked to anything else, such as devices, IP prefix etc. As an example, we have the PDUs which we would like to link to these Power Circuits. We would also like to link such Circuits with the rack numbers. We tried to add custom fields to racks/devices/prefixes to have this info. To eliminate double entry it would be good if we could choose a drop down list from a list of circuits for a custom field.
adam closed this issue 2025-12-29 16:32:32 +01:00
adam commented 2025-12-29 16:32:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 22, 2018):

Currently, circuits are linked to an A/Z side but cannot be linked to anything else, such as devices, IP prefix etc.

Each side of a circuit can be terminated to a device interface, via which it can be associated with an IP address.

As an example, we have the PDUs which we would like to link to these Power Circuits. We would also like to link such Circuits with the rack numbers.

Circuits represent only physical data links and are not related to power. NetBox does not currently support modeling power distribution; see #54.

@jeremystretch commented on GitHub (Jan 22, 2018): > Currently, circuits are linked to an A/Z side but cannot be linked to anything else, such as devices, IP prefix etc. Each side of a circuit can be terminated to a device interface, via which it can be associated with an IP address. > As an example, we have the PDUs which we would like to link to these Power Circuits. We would also like to link such Circuits with the rack numbers. Circuits represent only physical data links and are not related to power. NetBox does not currently support modeling power distribution; see #54.
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#1505
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?