astronowbot

• Corning Fiber Patch Panel
• Patch Panel Cat6

Enterprise Networking Routers, Switches, Firewalls and other Data Networking infrastructure discussions welcomed. New Visitors are encouraged to read our.

Patch panel documentation. The diagram is basically a map designed to show the coding/labelling scheme of the patch panels and ports. The Spreadsheet acts as a. 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.

Corning Fiber Patch Panel

This subreddit allows:. Enterprise & Business Networking topics such as:. Design. Troubleshooting. Best Practices.

Patch Panel Cat6

Educational Topics & Questions are allowed with following guidelines:. Enterprise /Data Center /SP /Business networking related. No Homework Topics without detailed, and specific questions.

Networking Career Topics are allowed with following guidelines:. Topics asking for information about getting into the networking field will be removed. 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.

Home Networks, even complex ones are best discussed elsewhere like. HomeLab discussions, as a tool for learning & certifications are welcomed. Braindump / Certification Cheating.

These topics pollute our industry and devalue the hard work of others. These posts will be deleted without mercy. Blogspam / Traffic Redirection.

This sub prefers to share knowledge within the sub community. Directing our members to resources elsewhere is closely monitored.

You may announce the existence of your blog/YouTube Channel. You may share a URL to a blog that answers questions already in discussion. But harassing members to check out your content will not be tolerated. Low-quality posts.

Any post that fails to display a minimal level of effort prior to asking for help is at risk of being Locked or Deleted. We expect our members to treat each other as fellow professionals. Professionals research & troubleshoot before they ask others for help. Please review to avoid this issue.

Early-Career Advice. This sub-reddit is dedicated to higher-level, more senior networking topics. Duolabs cas 3 plus interface software.

and are all available for early-career discussions. We don't do your homework for you. Don't ask us what we would buy for a given project. Don't ask us how to subnet. Show us how you think you should solve those issues, and we will validate or offer enhancement to your initial attempt. Recommended & Related Sub-Reddits: Related IRC Channels.

Rule #1: No Home Networking. 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. My colleague (and me, kind of) is looking for some software that will replace a tatty old book that lists all of our patch panels and their connectivity - mainly interested in tracking the backend fiber connections not the endpoint connections.

Excel would be a step up, but ideally we want something that can be used as a 'master' source of info from where we could, ideally, throw out a set of PDFs or 'something' printable for going out doing jobs. Ideally if you want to patch from A to B the software would tell you, and visualize, that you need to go via X, Y, and Z (think small campus with 100 or so patch locations). There seems surprisingly little that jumps out, so maybe there isn't, maybe we're just searching for the wrong thing - we've found racktables and device42 and a few 'contact us for pricing' options but nothing jumps out as the leader at this. What's everyone doing please? I basically started with a HUGE page (architectural E sized paper) and 1':32' scaling. Then, I downloaded some visio stencils for the appropriate HP switches and racks.

Then I drew some rooms to get a sense of relational position. Then, in each room, I drew some racks with the appropriate gear loaded in the racks. Then, I drew in all the fiber connections between each patch panel and the core switching room. Then, I created a set of objects that became those port-covers. At the scale I drew at, 0.1pt font is still about 2.5 times the height of a single switch port, so I drew out all the numbers from 0-9 at approximately 0.007 pt font. I then made basically one port cover for each vlan number in use and gave them different colors for backgrounds.

Then I copy/pasted them around to 'set the VLAN' on each port. It took me about 20 hours total to make this document. I have a copy of it printed out next to me on the wall printed in landscape on a 60 inch plotter (60x84). Each of the rooms ends up being a 8.5x11 piece of paper at that zoom and I can read individual port vlans at that scale. There's a void in the market between 'spreadsheet' and 'price on application'.

I'd go with a set of spreadsheets, one spreadsheet per room, one tab per panel. Each building in its own directory, and that directory is where you also store all the installation invoices and test results. Within a room name your racks A, B, C. Then number the panel by rack unit (they start with 1 at the lowest RU and count up).

In a large room imagine A-Z along one wall and A-Z along another wall at floor tile spacing (900mm) and name the rack by its position on the grid. It's tradition not to use letters I and O.

I've seen mid-sized universities run from well organized spreadsheets. Commscope makes ImVision-Ipatch. It's software and hardware, literally lights up your cable paths and everything. I have used over a dozen different systems. Here's how I feel about all of them (including all listed here): I prefer removing my own organs with a spoon to using any 'system' to manage cable paths or patch panels. That goes for all of these systems listed here. 100% of our engineers and tech's can mentally map or physically walk a path with millions of less hours per year and $s wasted on trying to keep software up to date with everything you have added.

Just put good labels on the things when you install them, and plan where panels go before you place them. My current job is the only one where I have seen labels that are adequate You know looking at any label anywhere on the path, everywhere it jumps. Serial numbers for devices at either side, location of where every cable starts/ends, etc. Good labels are 10 trillion times better than any other system. Have a strong planning and validation phase, and everything else comes naturally. Especially beware these systems when it comes to decomm time.

We are forced to use these systems, a different system at each datacenter. 90% of our outages, and 90% of our RGEs exist because of these systems. If you really need a system, put a couple months into learning a web development language and a database and roll your own. We did that too and hated it less than everything else.