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

Front/Rear Port Support for Power #10083

New Issue
Closed
opened 2025-12-29 21:26:41 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:26:41 +01:00
Owner
Copy Link

Originally created by @adaemmer on GitHub (Aug 13, 2024).

Originally assigned to: @arthanson on GitHub.

NetBox version

v4.0.8

Feature type

Change to existing functionality

Proposed functionality

It shall be possible to route power through front port / rear port connection panel. Currently this is not possible for power connections.

Use case

We have some maintenance connection panels in our racks and for some use cases we have a power patched through.

Database changes

I guess there need to be some changes, but I not that deep into the schema.

External dependencies

No new dependencies.

Originally created by @adaemmer on GitHub (Aug 13, 2024). Originally assigned to: @arthanson on GitHub. ### NetBox version v4.0.8 ### Feature type Change to existing functionality ### Proposed functionality It shall be possible to route power through front port / rear port connection panel. Currently this is not possible for power connections. ### Use case We have some maintenance connection panels in our racks and for some use cases we have a power patched through. ### Database changes I guess there need to be some changes, but I not that deep into the schema. ### External dependencies No new dependencies.
adam added the type: featurestatus: revisions needed labels 2025-12-29 21:26:41 +01:00
adam closed this issue 2025-12-29 21:26:41 +01:00
adam commented 2025-12-29 21:26:42 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Aug 13, 2024):

I assume this use case should already be possible, using Power Ports and Outlets. You can create them with a 1:1 or 1:n mapping. However, the cable trace will stop at this device and traverse as for front/rear ports.

@alehaa commented on GitHub (Aug 13, 2024): I assume this use case should already be possible, using Power Ports and Outlets. You can create them with a 1:1 or 1:n mapping. However, the cable trace will stop at this device and traverse as for front/rear ports.
adam commented 2025-12-29 21:26:42 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Aug 14, 2024):

@adaemmer is the power trace through the front/rear ports the main thing you are looking for? Can you please update the feature request and provide some additional details?

@arthanson commented on GitHub (Aug 14, 2024): @adaemmer is the power trace through the front/rear ports the main thing you are looking for? Can you please update the feature request and provide some additional details?
adam commented 2025-12-29 21:26:42 +01:00
Author
Owner
Copy Link

@adaemmer commented on GitHub (Aug 14, 2024):

@alehaa yes, this will do the trick, thank for clarifying and sorry for creating an issue for this.
@arthanson power trace was on hold with us for reasons I don't remember but as @alehaa pointed me to the existing solution I close this issue. Thanks for your comment.

@adaemmer commented on GitHub (Aug 14, 2024): @alehaa yes, this will do the trick, thank for clarifying and sorry for creating an issue for this. @arthanson power trace was on hold with us for reasons I don't remember but as @alehaa pointed me to the existing solution I close this issue. Thanks for your comment.
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 status: revisions needed 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#10083
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?