Replies: 1 comment
|
NetBox does not currently have a native conduit/pathway object. A The second model does split the cable record, but NetBox path tracing continues through paired pass-through ports, so the end-to-end logical trace is not interrupted. It is appropriate only when those are real connection/splice points. If boxes and conduits are just waypoints, use Locations for the boxes where helpful and add a structured custom field (or plugin/custom object if you need capacity, occupancy, and ordered traversal). Modeling every waypoint as a patch panel would imply terminations that do not exist and make maintenance data misleading. Cable/path behavior: https://netbox.readthedocs.io/en/stable/models/dcim/cable/#tracing-cables |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone, I need to define the physical passage of a cable, specifically I need to mark that a cable passes through a conduit and through which conduit boxes.
I've thought of setting every junction box as a simple patch panel and the conduits as cable bundles, but this means interrupting the virtual cable at every junction box, is there any better way or something I've not seen on the various options?
All reactions