[Enhancement] Patch Panel & Cross-Connect tracking #96

Closed
opened 2025-12-29 15:32:41 +01:00 by adam · 2 comments
Owner

Originally created by @ryanmerolle on GitHub (Jun 30, 2016).

This may be unnecessary, but single patch panel & cross-connect fields are not always idle given the multiple patch panels or cross-connects you may need for a circuit to be patched to your equipment.

Example: 350 East Cermak in Chicago has many co-location vendors in the same building. At times you may need to setup cross-connects from a carrier's Equinix cage to a TELX meet-me-room to your own cage.

It may also be useful to map out patchpanels in a rack similar to the way you would map out switch ports from a port and rack capacity perspective.

Originally created by @ryanmerolle on GitHub (Jun 30, 2016). This may be unnecessary, but single patch panel & cross-connect fields are not always idle given the multiple patch panels or cross-connects you may need for a circuit to be patched to your equipment. **Example:** 350 East Cermak in Chicago has many co-location vendors in the same building. At times you may need to setup cross-connects from a carrier's Equinix cage to a TELX meet-me-room to your own cage. It may also be useful to map out patchpanels in a rack similar to the way you would map out switch ports from a port and rack capacity perspective.
adam closed this issue 2025-12-29 15:32:41 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jun 30, 2016):

This is roadmapped in #20

@jeremystretch commented on GitHub (Jun 30, 2016): This is roadmapped in #20
Author
Owner

@ryanmerolle commented on GitHub (Jun 30, 2016):

Sorry I missed this!

@ryanmerolle commented on GitHub (Jun 30, 2016): Sorry I missed this!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#96