I do a combination of a spreadsheet and a diagram. The diagram is basically a map designed to show the coding/labelling scheme of the patch panels and ports. The Spreadsheet acts as a legend for the map so that it isn't cluttered with connecting lines. A tend to go PP-A-1 or SW-A-1 with PP designating patch panel and SW designating switch, the letter shows the position on the rack in sequence and the number is port number. You can also save Visio diagrams as JPEGs for portability just keep the original for editing purposes. Hi all; As a phone tech from last century I'd like to give my two cents worth on this. In the good old days we used to provide a double accounting approach, that is, each end point had the other end point noted.

Interface descriptions? One-to-one numbering between switches and panels? Jump to content. How Do You Guys Document Patch-Panel to Switchport? May 01, 2014 Standard way of documenting switch port / patch. Of course a spreadsheet springs to mind and. Manage your patch panels efficiently and effectively; Support templates for fiber, Ethernet, or any patch panel type; Load cabling data using spreadsheet imports. Creating patch panels from scratch in device42: an example. Before we add the patch panel, we need to create the template. In this example.

Sticking with the whole telecoms feel a jumper between two pairs would be recorded in two places. For example at the mainframe of a building - the point where the incoming cable from the telephone exchange (Central Office for those in the US) terminates into a building I would have receorded the following: In the mainframe record book I would have the two entries as follows: Main cable Pair - Jumpered to - Riser Pair, and Riser Pair - Jumpered to - Main cable Pair. Each record would be in a different section of the record book as each vertical (whether Krone, or 101 blocks or solder tags) is considered a record space. What I would suggest to you, and I have attached an empty excel spreadsheet for you all to look over, is an excel version of this. Further I would suggest a naming version similar to: Location1-Location2-HardwareType-Number.Port_Number such that something in building 1, floor 1, on the Coreswitch 0, port 1 would show as: bld1-fl1-csw-0. Panasonic Network Camera Recorder License Branch more. p1.

What you use for your terminology is up to you, but stick with something that anyone using a little bit of common sense, a vizio diagram and your record in excel or whatever, should be able to figure this out. Ideally a master codex that provides the understanding to unlock your hardware or asset naming scheme would be ideal. And I agree with Jen and her P-Touch (or Dymo Lable Maker for that matter) approach. Label everything in your comms rooms. Treo Fitness V109 Pdf Merge. Take a look at the spreadsheet (it is unlocked and open for your use) that is attached and let me know if anything is unclear. Hope this helps everyone in the community. I was going to chime in here but everybody beat me to the diagram + spreadsheet approach.

I find that different types of documentation require different formatting or tools. 10 Easy Lessons Blues Harmonica Rapidshare Free. I don't like the maintenance involved in most methods. Too much overhead.