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

Add support for "Y" adaptor power cables #4839

New Issue
Closed
opened 2025-12-29 19:21:07 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:21:07 +01:00
Owner
Copy Link

Originally created by @taupehat on GitHub (Apr 27, 2021).

NetBox version

v2.11.1

Feature type

Change to existing functionality

Proposed functionality

  • Create a cable type "Power (Y type)"
  • When this cable type is used, allow multiple power ports to connect to the same outlet
  • Calculate power draw to that outlet to be the sum of both ports attached to the cable

Use case

It's occasionally necessary to use a Y adaptor to power both power supplies on a device when not enough outlets are available. Example of such a Y adaptor:
https://www.tripplite.com/computer-power-extension-cord-y-splitter-cable-10a-18awg-iec-320-c14-to-2x-iec-320-c13-6-ft~P0040062C13

Currently there is no acceptable way to model this cable type within Netbox.

Database changes

No response

External dependencies

No response

Originally created by @taupehat on GitHub (Apr 27, 2021). ### NetBox version v2.11.1 ### Feature type Change to existing functionality ### Proposed functionality - Create a cable type "Power (Y type)" - When this cable type is used, allow multiple power ports to connect to the same outlet - Calculate power draw to that outlet to be the sum of both ports attached to the cable ### Use case It's occasionally necessary to use a Y adaptor to power both power supplies on a device when not enough outlets are available. Example of such a Y adaptor: https://www.tripplite.com/computer-power-extension-cord-y-splitter-cable-10a-18awg-iec-320-c14-to-2x-iec-320-c13-6-ft~P0040062C13 Currently there is no acceptable way to model this cable type within Netbox. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:21:08 +01:00
adam closed this issue 2025-12-29 19:21:08 +01:00
adam commented 2025-12-29 19:21:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 28, 2021):

Implementing this will likely require overhauling the cable model completely. Which isn't to say we won't do it; just setting expectations. However, we may want to re-cast this as general support for multi-point cabling, as I suspect there's a high degree of overlap with modeling breakout cables (e.g. a 40GE interface connected to four channelized 10GE interfaces).

@jeremystretch commented on GitHub (Apr 28, 2021): Implementing this will likely require overhauling the cable model completely. Which isn't to say we won't do it; just setting expectations. However, we may want to re-cast this as general support for multi-point cabling, as I suspect there's a high degree of overlap with modeling breakout cables (e.g. a 40GE interface connected to four channelized 10GE interfaces).
adam commented 2025-12-29 19:21:08 +01:00
Author
Owner
Copy Link

@xkilian commented on GitHub (Apr 28, 2021):

Great idea Jeremy to make it generic, there are a few other use cases where this pops up. Ex. Copper cabling for telephony that use these types of Y cables.

@xkilian commented on GitHub (Apr 28, 2021): Great idea Jeremy to make it generic, there are a few other use cases where this pops up. Ex. Copper cabling for telephony that use these types of Y cables.
adam commented 2025-12-29 19:21:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 28, 2021):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 28, 2021): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:21:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 1, 2021):

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 (Aug 1, 2021): 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 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#4839
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?