Ability to add devices with front ports only without explicit mapping to rear-ports #21830
Description
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