• Patch Panel Spreadsheet Template

CDP/LLDP goes straight to the control plane and is directly acted on, unlike the vast majority of user-generated traffic. On the other hand CDP greatly aids network maintenance, particularly moves/adds/changes. We get a lot of those so we ameliorate the risks by careful ACLs and keep a careful eye on what's going on. The risk/benefit trade-off for us is that CDP/LLDP are worth it. That's not always going to be the case depending on the situation.

Fill in Your Own Patchbay Design with this XLSX Spreadsheet and return to Mr. Patchbay via email. Templates have been created for our Laser / Inkjet printable labels if you do not have the EasyMark software. The templates use Microsoft Word, and are in a table design. After you have downloaded the template, be sure to save it to your computer for future use. If you need any additional assistance please contact our. Can anyone post an example or send a link to an example on how do you document all the connectionss in a rack with a switch and patch panel? Is it just 2 tables switch patch panel port goes to. If your spreadsheet has a line item for each PC-to-jack connection, each jack-to-patch panel connection, and each patch panel-to-switch port connection.

Rule #2: No Certification Brain Dumps / Cheating. Rule #3: No BlogSpam / Traffic re-direction. Rule #4: No Low Quality Posts. Rule #5: No Early Career Advice. Rule #6: Homework / Educational Questions must display effort. In general, we don't.

It's not perfect but I can't think of a better but still practical alternative. CDP and LLDP do give away potentially useful information to an attacker, such as management IP address of the switch and VLAN tag information. They're also potentially paths for DoS attachs; I used to have a Polycom conference phone that would lock a Cat4500 solid due to a fault that caused it to generate malformed CDP replies. CDP/LLDP goes straight to the control plane and is directly acted on, unlike the vast majority of user-generated traffic. Shrew soft vpn.

On the other hand CDP greatly aids network maintenance, particularly moves/adds/changes. We get a lot of those so we ameliorate the risks by careful ACLs and keep a careful eye on what's going on. The risk/benefit trade-off for us is that CDP/LLDP are worth it. That's not always going to be the case depending on the situation.

I have a medium sized network with over a dozen sites and this is what I use for documentation on an almost daily basis. - Visio for an overall network topology detailing equipments (name model), their management IP, and any WAN links with circuit ID and bandwidth. - Visio for uplink between stack switches detailing which ports and what etherchannel group they belong to.

- Spreadsheet for NAT info on my firewalls including public DNS. - Spreadsheet for rack layout at all my sites. - Used to have a spreadsheet detailing switchport info, but it got unwieldy. Ended up using Cacti with MACTrack for automated port scanning and a wealth of other info. - Spreadsheet for QoS settings.

This topic has been discussed at length, please use the search feature. • Topics regarding senior-level networking career progression are permitted. This subreddit does NOT allow: • Home Networking Topics. • We aren't here to troubleshoot your 'advanced' video game latency issues.

I've been trying to escape workign with this particular team for a few years now, but it always comes back, because no-one else seem to be able to do it for long and not loose their sanity. I'll describe how I do it as best I can. First off, I don't like Visio or excel spreadsheets. I work for a larger organization and no one seems to know where the latest version is. For my team, the goal of the documentation is to reduce the time it takes a Network Engineer to solve a problem. With that said, all of my network documentation is in Solarwinds (which also covers all of our network monitoring, network configuration management, net-flow, and IP address management.) Think of Solarwinds as an interactive web based Visio diagram. Our first diagram when we open the website is a list of all 70 of our locations, and how they are basically connected.

In this example, this is a singular patch panel with 48 RJ-45 ports. Steps taken: • Devices > Assets > Patch Panel Model > Add • Add name, port type, # of ports etc.

You can download this article’s template file using the link to the right. What to Document The first question to ask when deciding to create a port mapping is which details should you record. The answer completely depends on your specific environment and what you plan to do with the documentation. Different requirements demand different data to be collected. I recommend you identify what you would like to do with this documentation before collecting and creating it. All that being said, the template linked to on this post contains a baseline of the most common data points which can provide a solid starting point. Type This field details the layer-1 and layer-2 media and protocols used on the wire.

Monitored PDUs Monitored PDUs remotely monitor voltage, frequency, and load levels via a built-in network connection. Switched PDUs Switched PDUs can securely control individual outlets remotely to enable the rebooting of unresponsive equipment to minimize downtime. Auto Transfer Switch (ATS) PDUs ATS PDUs provide redundant power to connected equipment with separate primary and secondary power sources. Hot-Swap PDUs Hot-Swap PDUs have dual input power cables to enable live-replacement of select UPS systems with no power interruption to connected equipment.

Also, is this more of a Server Room post? If so, mods please move, or I can repost. I may be alone in this, but I don't see a lot of point documenting port VLAN mappings.

Too bad, document it the next time, mkay? Downsides include that maintaining that documentation base is quite a lot of (tedious) work, which is not helped by the systems awful (and i mean: really, really awful.

In my experience, it takes longer to check the docs, and update the docs when you make a change, than it does to simply look at the switch configuration. Looking at the switch config also avoids the scope that a temporary change by a contractor (don't ask about access control at the site), config reversion due to a failure to save config changes followed by a power outage (don't ask about switch UPS) or human error updating the documentation offer for causing incidents. I think there has to be a happy middle ground. Documentation is to feed understanding of the installation and help speed configuration, management and troubleshooting. It is not to be used for configuration backup and restore. You should have a real config management solution for that.

Patch Panel Spreadsheet Template

In theory, I want a google map that has every one of my sites where I can zoom on each building and get a floor plan and list the com rooms and zoom into the comm rooms and see the switches and then zoom to the ports and see the devices connected to it. Stuff like that is possible but improbable to actually implement. Stuff like mapping endpoints to jack ports to patchpannel location to switchports is near impossible in a multiple location enviornment when you dont have physical control over who changes what. Mlan wrote:I have asked this question before to various people, especially in regard to network documentation that would meet compliance initiatives, and I have yet to get a solid answer.