Although network documentation is always a good idea, it’s especially important for service providers and value-added resellers (VARs). Documenting your customers’ networks can make the troubleshooting process much more efficient when problems arise.
These same network documents can also help you spot areas of your customers’ networks that may need to be upgraded, giving you the possibility of earning extra revenue. Finally, good network documentation proves that you adhere to industry best practices, and could be your best defense should a customer ever file litigation against you for something network-related.
The following must be documented;
- Create a networkdocumentation policy
A network documentation policy should detail what aspects of a network need to be documented, especially each server. A documentation policy also communicates to each administrator exactly what is expected of them regarding the documentation process.
- Create a network topology diagram
Ideally, you want this map of the network’s topology to include each network segment, the routers connecting the various segments, and the servers, gateways and other major pieces of networking hardware that are connected to each segment. For larger networks, you may have to create a general segment map and make more specific maps of each individual segment.
- Document server names, roles and IP addresses
While the information included in a network topology diagram is not necessarily specific, there is certain information that you should include for each server, even if that information has to be placed in an appendix. For each server, list the server’s name, its IP address and the role that the server is performing (DNS, DHCP, mail server, etc.). Keep in mind that a server may be assigned multiple IP addresses or have multiple NICs, so you should document that information too.
Leave a Reply
You must be logged in to post a comment.