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

Allow different equipment to be installed front and rear on the same rack position level #8580

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

Originally created by @smarteyesi on GitHub (Sep 6, 2023).

NetBox version

v3.6.0

Feature type

Change to existing functionality

Proposed functionality

Allow different devices to be installed in front and rear.

With short-depth devices, it is possible to put a patch panel in the rear while putting another device in the front.

Use case

With short-depth devices, it is possible to put a patch panel in the rear while putting another device in the front.

Example:
42U-front: 48x port switch
42U-rear: 8x ports power distribution unit (PDU)

both are having the same rack position namelijk 42, but its a different device in the front and the rear

Database changes

the tool pathfinder resolves this problem by allowing different levels (up to 4) for front and rear so you can place/view another device depending on the level.

External dependencies

no external dependencies are required

Originally created by @smarteyesi on GitHub (Sep 6, 2023). ### NetBox version v3.6.0 ### Feature type Change to existing functionality ### Proposed functionality Allow different devices to be installed in front and rear. With short-depth devices, it is possible to put a patch panel in the rear while putting another device in the front. ### Use case With short-depth devices, it is possible to put a patch panel in the rear while putting another device in the front. Example: 42U-front: 48x port switch 42U-rear: 8x ports power distribution unit (PDU) both are having the same rack position namelijk 42, but its a different device in the front and the rear ### Database changes the tool pathfinder resolves this problem by allowing different levels (up to 4) for front and rear so you can place/view another device depending on the level. ### External dependencies no external dependencies are required
adam added the type: feature label 2025-12-29 20:38:26 +01:00
adam closed this issue 2025-12-29 20:38:26 +01:00
adam commented 2025-12-29 20:38:27 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Sep 6, 2023):

Hello!

If I've understood your request correctly, this is already possible today with NetBox. When you're creating a device type, if you specify that it's "Full Depth", then it will occupy both front and rear faces of the rack when installed.

However, if you create a device that's not marked as "Full Depth", then it'll only occupy one face.

If you're looking for something more than that, please clarify.

@pv2b commented on GitHub (Sep 6, 2023): Hello! If I've understood your request correctly, this is already possible today with NetBox. When you're creating a device type, if you specify that it's "Full Depth", then it will occupy both front and rear faces of the rack when installed. However, if you create a device that's not marked as "Full Depth", then it'll only occupy one face. If you're looking for something more than that, please clarify.
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 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#8580
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?