How to store information about switching communication lines?

Question

network hardware

Good afternoon, dear readers.

How to correctly store information about switching patch panels, optical boxes, network equipment to subscribers?

Solutions already familiar to me - Excel, Visio, drawing diagrams, cable magazines - this is all a complex, not automated process with a bunch of inconvenient nuances.

I will describe a little what the problem is - not the current moment there is no marking - only at best a signature with a pen on the patch cord tag, and then in the server rooms. There is no exact information about the crossover, each time you have to highlight the optics, call, check the UTP line, look for the subscriber's link, etc. Basically old methods.
At the moment, there are only 2 ways to store information about cross-linking - scheme and records in text information format.
Visio is a good tool, but it's meant for something a little different in my opinion. Storing information about more than... 4 or 5,000 crossovers in the form of a schema, I think is not the best solution.
Excel is an attempt to create a cable magazine, but I didn’t find another way to quickly and easily make such a semblance.
Can someone tell me if there is a finished product on this issue, where do you store information?
I ask dear readers not to react aggressively, the issue is controversial and there are many solutions, I'm just looking for a suitable solution. What I have already found: Zabbix, but this is monitoring, there is little here related to my question, The Dude is already available, but this is also not at all, MacMonitor is very close to my problem, but it is such an inconvenient and unfinished product that its use I don’t see it as comfortable enough, data center monitoring and control systems have some solutions on this issue, but this is not the same either.

Answer 1

Divide the levels, and each in its own way.
Physical - we take a building plan, draw where the subscribers' sockets are located (or not sockets, but just connectors), number them all (floor, room, socket number in the room; or another option).
In the server room we drive all the ends on the patch panel. We call everything and put it on the plate - the patch panel number, the patch panel port, the type of connection (to the subscriber, to the upstream node, or whatever), the cable (and its length, if known), which is at the second end (socket, connector , or the cable is simply coiled behind the ceiling as a reserve), the number of the socket / connector / cable end. It can be a little easier or a little more difficult, as you like. And basically everything.
Which MAC is on which port and what IP is on it (and is there an IP there at all) - this is all by any means of monitoring and / or inventory, there are many of them.
As a result, you need to change the sign only if lines are added / removed, or transferred from office to office. Well, on the diagram, change the designations and location of sockets (if someone needs it). Redevelopment of premises is also not so common, you can fix everything manually.
And monitoring will track the rest - on which port of which switch, which MAC, which IP is on it, etc.
In principle, SCS has ISO and GOST standards. Too lazy to google, but I read them, if not everything, then almost everything is written there, you just need to follow.

Answer 2

netbox look

Answer 3

I tried to solve this problem, but in the end I scored
Just because crossover is a passive state that is not automatically verified.
There are usually many times more ports on patch panels than switch ports (if not open space where you can fix jobs).
But even if there are enough switches, and each unused socket is connected to the switch port, then, for information security reasons, the port on the switch is turned off and the presence of crossover does not help in any way.
In the case when the crossover is always performed by the same person, maintaining a cable magazine (no matter what and in what) is still advisable.
But when 7 nannies are doing cross-country, this very magazine will be a complete mess. And automatic verification is not possible. All the same, do everything with your feet. So let these 7 nannies run around
. But the task of finding an active port by user is successfully solved in many ways and tools.
I am using LibreNMS. It's there out of the box. And I have no idea how to do this in Zabbix. Although no, I guess. In the case when the user blocks the port by portsecurity, my zabbix sends me an SMS with the switch number, port and poppy address that caused the event.