![]() ![]() Particularly infrastructure assets and support contractsīecomes critical in larger environments with lots of support staffĬritical network documentation Layer 1 and 2 diagramĪ Layer 1 diagram shows the physical connections between the critical pieces of network infrastructure. Particularly useful during implementation This is more useful for explaining your security than for troubleshootingīecomes critical if you run a cloud of any complexity Particularly useful if the drops are not numbered the same as the desk locationsīecomes critical if you run a routing protocol of any complexity ![]() This could be a tool rather than a spreadsheet to allow easy sharing Sometimes this is done within a trouble ticketing system So the actual documents you need will vary depending on the network, but the following table shows the relative importance of a typical network. But in a bigger network, you need to follow the general principle that somebody else will need to support this thing one day and you want to be remembered positively. ![]() It might be enough to put everything in a single diagram. The short answer is that it should include everything that’s relevant-but what that means varies between networks.įor example, in a really small network with one switch and a firewall, and perhaps a single wireless access point, there isn’t much to document. Everybody agrees network documentation is extremely important, but there tends not to be a lot of agreement on what that documentation should include. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |