Ability to add devices with front ports only without explicit mapping to rear-ports #13

New Issue

MrUnknownDE · 2026-04-05T16:21:12+02:00

MrUnknownDE commented

2026-04-05 16:21:12 +02:00

Originally created by @n3wtype on 4/2/2026

NetBox version

v.4.5.6

Feature type

New functionality

Proposed functionality

We would like to manage patch panels within netbox as fixed device-types. We would like to store schemas for common patch panel types we uses e.g. LC/APC_16, LC/PC_24 etc the same way as we manage devices and interfaces, so during creation of device of given device type proper interfaces are getting created.

Use case

Unfortunately we are unable to do that without defining explicit rear-port mapping. In our use case we have patch panels for DC interconnects with fixed amount of front ports, not connected to anything, being ready for future use. No rear ports are used at this point. Once we order new services they are getting connected to patch panel in form of splices, one time it could be 2J toward MMR to terminate service, other time 16J toward some other rack.

With current model we have to create empty patch panel and with no front and rear ports and populate it as we go, even though its front ports are fixed. It would be more convenient for as to have front ports pre-populated according to reality and then map number of front ports to splice, once service is ordered. It would lessen workload and would easier to track number of free ports this way.

Alternatively I could think pre-populating front and rear ports as one-to-one mapping. However, such approach is an overkill for our use case. Let's say we order 8J from DC to interconnect some other rack or 2J cross-conect to terminate service. It is convenient to us to threat it as a whole as a single circuit. This is the way the service is ordered and referenced later during communication with DC.

Database changes

No response

External dependencies

No response

*Originally created by @n3wtype on 4/2/2026* ### NetBox version v.4.5.6 ### Feature type New functionality ### Proposed functionality We would like to manage patch panels within netbox as fixed device-types. We would like to store schemas for common patch panel types we uses e.g. LC/APC_16, LC/PC_24 etc the same way as we manage devices and interfaces, so during creation of device of given device type proper interfaces are getting created. ### Use case Unfortunately we are unable to do that without defining explicit rear-port mapping. In our use case we have patch panels for DC interconnects with fixed amount of front ports, not connected to anything, being ready for future use. No rear ports are used at this point. Once we order new services they are getting connected to patch panel in form of splices, one time it could be 2J toward MMR to terminate service, other time 16J toward some other rack. With current model we have to create empty patch panel and with no front and rear ports and populate it as we go, even though its front ports are fixed. It would be more convenient for as to have front ports pre-populated according to reality and then map number of front ports to splice, once service is ordered. It would lessen workload and would easier to track number of free ports this way. Alternatively I could think pre-populating front and rear ports as one-to-one mapping. However, such approach is an overkill for our use case. Let's say we order 8J from DC to interconnect some other rack or 2J cross-conect to terminate service. It is convenient to us to threat it as a whole as a single circuit. This is the way the service is ordered and referenced later during communication with DC. ### Database changes _No response_ ### External dependencies _No response_

MrUnknownDE added the status: needs triage netbox status: needs triage type: feature netbox netbox netbox netbox netbox type: feature labels 2026-04-05 16:21:12 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label netbox netbox netbox netbox netbox netbox status: needs triage status: needs triage type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#13