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

Patch Panel Position in Rack Space #1953

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

Originally created by @Shogun8 on GitHub (Aug 18, 2018).

Environment

  • Python version:
  • NetBox version: 06eed1e03dfc (v2.3.3)

Proposed Functionality

Changing the way that the patch panels in a rack are positionally aligned.

In the current version, a panel is positioned in the rack according to bottom left screw of the device: it's position enumeration is "The lowest-numbered unit occupied by the device ." I propose that the positioning of devices in the rack should be in alignment with the ANSI TIA-606-b-5.1.3.1.3.1 standard (please review figure 9) which proposes that it is the TOP left screw of the patch panel that is positionally aligned, rather than the bottom.
For instance a 3u patch panel that is located in the top of a 42u rack, would be in position 42, and not in position 40.

Originally created by @Shogun8 on GitHub (Aug 18, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: <!-- Example: 3.5.4 --> * NetBox version: 06eed1e03dfc (v2.3.3) <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Changing the way that the patch panels in a rack are positionally aligned. In the current version, a panel is positioned in the rack according to bottom left screw of the device: it's position enumeration is "The lowest-numbered unit occupied by the device ." I propose that the positioning of devices in the rack should be in alignment with the ANSI TIA-606-b-5.1.3.1.3.1 standard (please review figure 9) which proposes that it is the TOP left screw of the patch panel that is positionally aligned, rather than the bottom. For instance a 3u patch panel that is located in the top of a 42u rack, would be in position 42, and not in position 40. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ### Use Case ---> <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ### Database Changes ---> <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) ### External Dependencies --->
adam closed this issue 2025-12-29 17:20:52 +01:00
adam commented 2025-12-29 17:20:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 20, 2018):

This would be a completely arbitrary change requiring substantial modification to the rack elevation logic while yielding no practical benefit.

Also, NetBox does not currently support modeling patch panels (a feature to be introduced in v2.5).

@jeremystretch commented on GitHub (Aug 20, 2018): This would be a completely arbitrary change requiring substantial modification to the rack elevation logic while yielding no practical benefit. Also, NetBox does not currently support modeling patch panels (a feature to be introduced in v2.5).
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#1953
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?