Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cable properties missing #962

Open
jmcbxl opened this issue Oct 7, 2017 · 2 comments
Open

Cable properties missing #962

jmcbxl opened this issue Oct 7, 2017 · 2 comments

Comments

@jmcbxl
Copy link

jmcbxl commented Oct 7, 2017

Data about cabling is currently stored by using fields in "fac_ports table". Doing so requires to store some informations twice in the port table : "connected port", "connected device", "notes" need to be stored at each end of the cable.
Should be better to implement a "fac_cable" table and refering the cable by it's internal id.

This would allow some more possibilities for managing cabling :

  • fields for length, labels, electrical properties, connector type, ...
  • generating unique labeling much more easily
  • keep track of a cable that is not connected at one or both sides (either in the rack or in a box for future use, ...)
@miaxon
Copy link

miaxon commented Oct 12, 2017

very good idea.

@0smansen
Copy link

I totally agree. Label property will fill the gap which I suffer at cabling. And also this field should be placed in "View cable path" diagram and reports like "Network Map Viewer". Using notes in connection is not a useful workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants