This is a concept solution for network administrators to make changes in network cable connection under control. I show you my idea how to use developer tools like Git and VSCode to managing network cable connections, switches, patch panels, and cabinets. Logging changes is simple from today.
We could use simply text file in Markdown format (for quite nice PDF creation to create report) and observe changes with git. Is it too simple? No. I spent many hours to find a free graphic solution to write down connections and changes in LAN. And one day...
It seems to me that it will meet my expectations.
I use following set of tools (you can choose yours):
How it works
With a simply text file with Git we have a tool with following features:
- History of commits
- Preview of markdown file
- Export PDF file from markdown
- Planning chances in TODO section
- Highlighting string - part of selected panel, switch, etc.
SourceTree(or similar tool) to see committed changes
grepto see device connection in large file.
- Preview modification in Code.
OK, but how?
Use a text file
Pure text in markdown format
I put in two sections:
- Uplink Direction (to remember always using one direction: from endpoint to the switch)
- TODO. For planned changes. To copypastying.
It should be planned for using text tools in the future (like grep for example).
| source ||||| destination | | -------------------------------------------------|-|-|-|-|-| | Room002 | pc-0409 | S3.P7/12 | IP.38/1 | | Room005 | pc-0406 | S3.P7/14 | IP.38/2 |
You should have constant naming conventions. Think about the future. Do I have to talk about it?
Socket signing policy
S2.P2/4 || | |___ port (1,23...) || |_____ patchpanel (P2,P10...) ||________ cabinet number (1,2,...) |_________ server rack cabinet (S)