If they are not alpha-numeric identified, get ready to spend some time. Start with a comprehensive details showing all connections between your patch panels and switches. Work back to the end points from there. Quivern, Inc. I generally have a spreadsheet or a database for this. There's no way to do this without physically going to the room and tracing out the cables, though, and no guarantee that a closet monkey won't come along and mess it all up, either. Having a floor plan diagram in Visio with every drop clearly labeled is an absolute essential.
Doesn't matter how you label them, just pick a scheme that makes sense I've used different ones in different scenarios , label everything, and go from there. Just don't do what one place did and label the ports with the name of the person whose computer the port went to. Five years later someone will be in there looking at the panel and wondering "Who the hell is Jeff? You would be better off if it's a small amount to get a second person and start toning out the lines.
Yes, you can unplug and document what lights up, but tone generator and probe is pretty damn fast. Beyond that, there isn't any way to map it to a specific port on a patch panel.
It's a layer 1 device, literally it's just matching pins from one side to the other. Unless you intercept all the traffic coming across it from layer 1 to layer 7, then you won't know exactly what it is. Pretty much what I expected, I didn't really think there would be any magical software like that, unfortunately. Communications Etc. They do make some managed patch panels like the panview patch panels from panduit. They would help out with this, but that would require a much more extensive rack job than just tracing the current patch cords you have.
To continue this discussion, please ask a new question. So how about a visio libre draw of P1 - P48 for each switch and panel, and then drawn lines to each?
For the documentation I used Dia to do a diagram. It only maps where the trunks are. I never got in to the weeds mapping patch panel jacks to switch ports. I do them with RackTables. With it, you can document your rack, servers, networks and other devices. You'll have to configure it manually though, but I know with your skills that you'll be able configure it better than mine.
With one look, you'll get a view of what resides in your rack, a deeper inspection will reveal what is connected to what, it's up to you on how detailed you wanted to be. However, I have to be creative on the patchpanel side, I had to double the ports, one in front and one at the back. You can also configure what details to show to other users. I have my 2 colleagues have access but can not view some server details like usernames and passwords which I made similar to normal fields.
The rest should only keep this person informed. Otherwise it could be a mess. Since no one is trully responsible, data will be filled in a hurry and mistakes cannot be avoided. In my opinion, data must be filled in a spreadsheet file because it's the easiest and fastest way to update them.
0コメント