You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening this issue to track the research and development into creating a better approach to cable tracking in NetBox. Although many of the details need to be refined, the high-level approach will be to model discrete cable paths individually for each connected object. For example, consider the following topology:
There are two end-to-end connections present, both via cable 3:
Iface 1 <---> Iface 2
Iface 3 <---> Iface 4
Currently, these connections are conveyed only on the four individual interfaces. A more robust approach would record each of the four unidirectional end-to-end connections individually, as:
This approach ensures that we can immediately query all potentially affected points along a path any time any single component within the path changes. For example, if cable 2 is deleted, we know immediately that paths 1 and 2 need to be updated.
Justification
There are several drawbacks to the current model, as evidenced by numerous bug reports over the past few major releases. Rather than continue playing whack-a-mole chasing down errant behaviors individually, we should commit the time and effort to devising a new holistic approach.
The text was updated successfully, but these errors were encountered:
This would permit reporting on connexions passing through a patch panel or cable. Good for creating provising reports for new patch panels.
Also useful for tracking down what broke during a fiber optic cable cut and to prioritize fusions to restore service.
Proposed Changes
I'm opening this issue to track the research and development into creating a better approach to cable tracking in NetBox. Although many of the details need to be refined, the high-level approach will be to model discrete cable paths individually for each connected object. For example, consider the following topology:
There are two end-to-end connections present, both via cable 3:
Currently, these connections are conveyed only on the four individual interfaces. A more robust approach would record each of the four unidirectional end-to-end connections individually, as:
This approach ensures that we can immediately query all potentially affected points along a path any time any single component within the path changes. For example, if cable 2 is deleted, we know immediately that paths 1 and 2 need to be updated.
Justification
There are several drawbacks to the current model, as evidenced by numerous bug reports over the past few major releases. Rather than continue playing whack-a-mole chasing down errant behaviors individually, we should commit the time and effort to devising a new holistic approach.
The text was updated successfully, but these errors were encountered: