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

Swap Terminating Ends of Cable #3887

New Issue
Closed
opened 2025-12-29 18:31:47 +01:00 by adam · 10 comments
adam commented 2025-12-29 18:31:47 +01:00
Owner
Copy Link

Originally created by @iunderwood on GitHub (Jul 23, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.8.8

Proposed Functionality

Add the capability to swap the A and Z end of a terminating cable.

Use Case

Connecting two devices together is great, but it would be nice to be able to swap the A and Z ends of a connection for the presentation of data uniformity.

For instance, when I build out a cable plant from an IDF to an MDF, I might build that cable out starting from a point in my IDF, and terminating that in my MDF. That makes the A end in the IDF, when it's really in the MDF. It would be handy to just swap the ends without having to delete and rebuilt the whole cable.

Database Changes

None that I am aware of.

External Dependencies

None that I am aware of.

Originally created by @iunderwood on GitHub (Jul 23, 2020). ### Environment * Python version: 3.6.8 * NetBox version: 2.8.8 ### Proposed Functionality Add the capability to swap the A and Z end of a terminating cable. ### Use Case Connecting two devices together is great, but it would be nice to be able to swap the A and Z ends of a connection for the presentation of data uniformity. For instance, when I build out a cable plant from an IDF to an MDF, I might build that cable out starting from a point in my IDF, and terminating that in my MDF. That makes the A end in the IDF, when it's really in the MDF. It would be handy to just swap the ends without having to delete and rebuilt the whole cable. ### Database Changes None that I am aware of. ### External Dependencies None that I am aware of.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 18:31:47 +01:00
adam closed this issue 2025-12-29 18:31:47 +01:00
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 23, 2020):

Cables do not imply any direction: there are A and B ends, however these are arbitrary designations and exist as unique values solely to accommodate two terminations. The NetBox UI intentionally does not reveal to the user which end of a cable receives which designation.

@jeremystretch commented on GitHub (Jul 23, 2020): Cables do not imply any direction: there are A and B ends, however these are arbitrary designations and exist as unique values solely to accommodate two terminations. The NetBox UI intentionally does not reveal to the user which end of a cable receives which designation.
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@iunderwood commented on GitHub (Jul 23, 2020):

The observation of the A and B ends comes up in the cable list.

I found I built some cables starting in one of my IDFs to the MDF in question and some in the other direction. It would be nice to make these more uniform without having to rebuild the cable.

It is not a high-priority feature request.

@iunderwood commented on GitHub (Jul 23, 2020): The observation of the A and B ends comes up in the cable list. I found I built some cables starting in one of my IDFs to the MDF in question and some in the other direction. It would be nice to make these more uniform without having to rebuild the cable. It is not a high-priority feature request.
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 24, 2020):

The observation of the A and B ends comes up in the cable list.

That's true, but again, these don't indicate a particular direction. For instance, the Cable model could just as easily use an alternate approach where up to two terminations are assigned to a cable, as opposed using discrete fields on the model. In such a case, we'd still likely label the columns "A" and "B" just to differentiate between them. (I'm not suggesting we're going to do this in the future, but it's a possibility.)

@jeremystretch commented on GitHub (Jul 24, 2020): > The observation of the A and B ends comes up in the cable list. That's true, but again, these don't indicate a particular direction. For instance, the Cable model could just as easily use an alternate approach where up to two terminations are assigned to a cable, as opposed using discrete fields on the model. In such a case, we'd still likely label the columns "A" and "B" just to differentiate between them. (I'm not suggesting we're going to do this in the future, but it's a possibility.)
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@wols commented on GitHub (Jul 26, 2020):

This is a nice feature and I see two use cases:

  • a form of consitend documentation (@iunderwood: A is MDF, B is IDF ever)
  • users - like me - can map the signal direction (A: source, B: destination)
    -- I have a lot of cables between IN/OUT interfaces
@wols commented on GitHub (Jul 26, 2020): This is a nice feature and I see two use cases: - a form of _consitend_ documentation (@iunderwood: A is MDF, B is IDF ever) - users - like me - can map the signal direction (A: source, B: destination) -- I have a lot of cables between IN/OUT interfaces
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@cpmills1975 commented on GitHub (Jul 27, 2020):

IT tends to attract people with certain diverse characteristics.

I've seen people get quite upset at others for using the switch as the A end when it should have been the server or vice versa. Providing a simple means to swap ends would serve to placate some emotions!

@cpmills1975 commented on GitHub (Jul 27, 2020): IT tends to attract people with certain diverse characteristics. I've seen people get quite upset at others for using the switch as the A end when it should have been the server or vice versa. Providing a simple means to swap ends would serve to placate some emotions!
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@iunderwood commented on GitHub (Aug 4, 2020):

@cpmills1975 - Never underestimate how much someone can be affected by their CDO.

@iunderwood commented on GitHub (Aug 4, 2020): @cpmills1975 - Never underestimate how much someone can be affected by their [CDO](https://www.urbandictionary.com/define.php?term=CDO).
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 18, 2020):

Blocked by #4900

@jeremystretch commented on GitHub (Aug 18, 2020): Blocked by #4900
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@cpmills1975 commented on GitHub (Mar 25, 2021):

Is this still blocked?

@cpmills1975 commented on GitHub (Mar 25, 2021): Is this still blocked?
adam commented 2025-12-29 18:31:48 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 21, 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 (Jul 21, 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 18:31:49 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 20, 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 20, 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 status: needs owner 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#3887
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?