Some of the best practices as a network engineer to optimize the network is to implement a monitoring system that alerts an engineer for any down or security breach. It is important to be able to know if there is a down than know after users complain. Also by having a monitoring system, the troubleshooting becomes a lot easier and can help identifying an issue. Engineers must be intuitive to each troubleshooting and value customer feedback for getting to the root cause. Most users would not be proficient with IT systems. It is important to see what is really occurring.
Another important thing an engineer should be considering to optimize the network is to leave records regarding the network infrastructure and revise changes accordingly. As a network engineer it is critical to have the correct documentation done for various reasons. Documentation for engineers include network layer 2 diagram for physical connection, network layer 3 diagram for logical infrastructure, IP Address list including IP Addresses used for the infrastructure, access listing, routing table, and so on. Without correct documentation, it can create huge delays in troubleshooting because engineers must start over and understand the network infrastructure to troubleshoot from the start.
Another issue is that without correct documentation, it would be difficult to scale the network and apply upgrades in the future. Not all upgrades are done by the network administrator responsible for the network infrastructure. There are times that network engineers must consider asking a vendor specialist to take care portion of the network that just can’t be done by the company network engineer. With the uncorrected network diagram can create huge and permanent issues in the network infrastructure, by vendor implementation and fixing it can be costly. Network designed must be planned beforehand with the correct documentation.