A month ago, I posted here to ask for some help about Network Deployment (Previous Post). Being a Developer, Network deployment is not my strongest skill. But after going through it myself, and with tremendous help from various people (Data Electricians and IT Redditors) and a lot of time researching, I was able to successfully deploy a network on a new building! I know the post was not popular if at all, but I would like to thank the redditors that provided their time and advice. :)
The physical deployment took about 3 days. There was roughly 2 weeks worth of preparation which included research and ordering. Included was obviously creating VLANs and securing the network and enabling logging etc. I have not included that below as configuration will be different for each device/brand topology.
Here is quick mock-up guide for those who may find themselves in the same position as I was (hopefully never):
1.) Create a scope on what it is going to be and what it is you are going to need in order to deploy your network. How many static (approx.)? Guests (approx.)? Telephones (VoIp)? Conference Rooms (Video Streaming)? How much is the budget?
2.) Before asking/going for a survey/inspection, ensure you have some tools with you.
a. Network Cable Tester
b. Various Screwdrivers/Phillips
c. Cable ties
d. Flash Light
e. Label Maker (or a Marker and a Painter’s Tape or both!)
f. Tape Measure
g. Ladder
h. **Vacuum (only if it is an old/existing Data Cab)**
i. Documentation (in writing or digital)
3.) Request survey/inspection of the building and the building plan (you want to look for the electrical plan if possible). Note: I liaised with our OH&S who was a former Civil Engineer/Tradie/Builder. I am lucky in this regard as he took over the safety inspection for every single floor and also hired the appropriate people to fix and replace things. This included the wiring. You may need to hire a building inspector to do that part or you may not.
4.) Begin your survey/inspection when safe to do so. Check the Data Cabinet. Clean up and replace/remove/fix things. Begin testing of every single port against the Patch Panel. Mark/label the ports and number them accordingly (if it wasn’t done so). Mark the patch panel as well to make it easier to visualize things.
5.) Roughly measure the distances of the switch to the patch panel so you can buy (or make one yourself [ How To Make RJ45 Network Patch Cables - Cat 5E and Cat 6 - YouTube ]) appropriate length of ethernet cables and also the amount you will need.
6.) Create a documentation of things from steps 4 and 5 as appropriate.
7.) Begin creating a list of things to order. With my particular situation (for one floor in particular):
a. 2 Wireless Access Points
b. 1 Switch (48 Port)
c. 50 pcs. 1 Meter Cat6 cables (because the Patch Panel actually runs in Cat6)
d. 10 pcs. 2 meter Cat6 cables (for those that need the extra length, then cut to size)
Note: Do test your systems if they are working before working live
8.) When wiring the Data Cabinet, it is a good idea to have some visualization on how you would tackle the situation. Plan out which Ports from the Patch Panel would go. I highly suggest to keep a note as you go along so you do not lose track of which Patch Panel Port actually goes into your switch, especially if you decide not to go 1:1 (like I did). Take your time.
Network Deployment Complete - sort of!
9.) Monitor your network and look at the logs. Ask your users and make changes/fixes etc. as needed.
And that is it! My experience/simple walkthrough guide for a basic network deployment!
P.S. the pictures reflect the network deployment at about 98% completion. The end product is cleaner. Also, this is a very "simple" network deployment, all things considered. But I wanted to share my experience and learning from it for those who may face a similar scenario or situation. It is NOT intended to reflect a super-perfect-top-shelf-super-professional-I-AM-A-NETWORKING-GOD-BOW-TO-ME-MORTALS guide. But a resource of sorts for those who need some structure and simple guide for a simple/basic network deployment.
No comments:
Post a Comment