. Keepass for passwords. Visio for network layout/design. Sharepoint Wiki for Static IPs, printer links, AP links, Check lists, supplier & support contacts,.
Sharepoint calendar for Application maintenance agreement expiry, etc. Spiceworks tickets for any change you make/made. Word doc for each server and their roles/purpose (with revisions).Word doc for Backup strategy/procedure. Spreadsheet for purchases (with macros). Disaster recovery document (whatever app you use, make sure you got hard copy). Most importantly.
Have you installed app called Spiceworks? From what i heard, it helps a lot. Spiceworkers are awesome too. I use Evernote to make notes whenever I am installing/configuring something. It's very helpful when you sit down to document and you share with your team if needed.
Hope that helps. Make sure you have a beer every night in this process. That helps too. I use Visio, Excel, and for tracking IP addresses Solar Winds IP Address Tracker which is free!!! I need to get our department to use Keepass but right now it's a password Excel spreadsheet.
We were just fortunate enough to recable our old buildings and replace all our switches, so at that point I built a spreadsheet that goes from patch panel, patch panel port, switch, switch number, port number, and now I'm going thru each switch and recording the users plugged into every port by MAC address (and then search Spiceworks for which desktop/user it is). Ofcourse keeping up with it is the big issue, and telling everyone else in the department not to move a patch cable in the closet or I will KILL them!!!! I use a MediaWiki to document my network/It infrastructure. Pages for each server, how-to and procedures, solutions to common problems, disaster recovery plans, service utility providers, maintenance schedules, software licensing/install procedures/troubleshooting, etc. I also have a few spreadsheets with long lists of phone numbers, and one for IP addresses, but I really should add those to the Wiki. DokuWiki is another good option, can even be hosted/run from a thumb drive and stores most of the info in plain-text so you can even get to it if your webserver is busted. NOTE: If you are doing your documentation digitally, you might want to print out hard copies of certain things, such as phone numbers for utility providers and disaster recovery procedures, in case your network is down and you can't get to the digital documentation.
I have one for the physical network structure; port numbers, patch panels numbers, Switch IP addresses, switch names, etc. I have one for the server structure: colour of patch cables, Switch port numbers, data type (iLO or Data), server IP's, iLO IP's, which VM's are on which ESX server, etc. I have one for the power structure.
I have twin UPS's and most servers have twin power supplies, so I've documented which supply goes to which UPS and which single power device goes to which UPS. This is so I can easily see what's effected if the UPS trips to battery, of if I need to down one to replace batteries. I have similar Visio diagrams for the VOIP set-up too. Bhasha wrote:. Keepass for passwords. Visio for network layout/design.
Sharepoint Wiki for Static IPs, printer links, AP links, Check lists, supplier & support contacts,. Sharepoint calendar for Application maintenance agreement expiry, etc. Spiceworks tickets for any change you make/made. Word doc for each server and their roles/purpose (with revisions).Word doc for Backup strategy/procedure. Spreadsheet for purchases (with macros). Disaster recovery document (whatever app you use, make sure you got hard copy).
Most importantly. Have you installed app called Spiceworks?
From what i heard, it helps a lot. Spiceworkers are awesome too. I use Evernote to make notes whenever I am installing/configuring something. It's very helpful when you sit down to document and you share with your team if needed. Hope that helps. Make sure you have a beer every night in this process.
Patch Panel Spreadsheet For Bills Free
That helps too. Hahaha:) Curious what macros do you use?
Contents. In this chapter, we will take a step by step approach to create patch panels from scratch to end result. The goal The example is simpler in nature, but this will cover the basics of how to add patch panel connections in device42.
End goal is:. Patch Panel A is connected to Patch panel B: Panel A Panel B. Patch panel A is patched to switch-01. Patch panel B is patched to devices in the same rack as Panel B. This will give us devices connectivity with switch ports. Creating Patch panel models Before we add the patch panel, we need to create the template.
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. For the model. Save Creating patch panels.
Go to Devices Assets Add. Give name Panel A, choose type “Patch Panel”, Choose the model created above. Save Repeat the same steps for Panel B, just change the name to Panel B in step 2.
Adding the Back connections or termination. Go to Tools Templates & Bulk Operations Panel Back Connectivity. choose Panel A, Port From: 1, Port To: 48 and Panel B, Port From: 1 and optionally, cable type. Click Continue. Now Panel A and Panel B are terminated to each other. Patching switch ports to panel A In this example, ports from switch-01 are patched to Panel A. (You can create switch ports in bulk using switch templates as discussed under ) The tedious way to do this will be to add each switch port to each panel port.
But we are not going to do that. Recommended way to do the same is to use API Excel import option added in v5.2.0. Steps:.
Go to Tools Import API Import(xls). Download sample excel file from “Create or update patch panel ports” in that page. Our columns will look like this: number patchpanelid switch switchport. Add the rows for panel port #, panel ID(available from Asset list view/from APIs/or get using Hover over in the status bar), switch name and switch port name. Import the Sheet. Upon import, you can see the switch ports connections on Panel A.
Patching devices to panel B In this step, we will use the same sample excel sheet downloaded in step above. Column layout will be a little different and will look like this: number patchpanelid device objlabel1 Once we add the values to excel and import it, the panel B will show following. Patch panel layout Now if you go to Patch panel layout for Panel B and hover over any port or device, you will see the full visual path for that port. Switch port level connectivity You will see the patch panel connectivity from each switch port view as well.
Device level connectivity Similarly, in the device view/edit page, you will see the patch panel connection under the tab “other”. This concludes our chapter on how to create a patch panel layout in device42.