Network documentation should ONLY contain network documentation! PART 2

In continuation with the topic "Network documentation should ONLY contain network documentation!" Here is Part 2... ResearchResearch, the process of acquiring data in the efforts of solving a problem.

This can result in a pile of printouts. NetworkDNA should only contain the resulting HOWTO document for problem resolution, not all of the data that was required to create the HOWTO.

Confused??? In compliance with the concept of "building blocks for network recovery" if there is something you need to do to your system, or individual pc's to make them work... you will need that process again when trying to get back to this point. I am the type of person who keeps everything... I keep this type of research in a file cabinet in a folder by software product.

Disclaimer: Blog contents express the viewpoints of their independent authors and
are not reviewed for correctness or accuracy by
Toolbox for IT. Any opinions, comments, solutions or other commentary
expressed by blog authors are not endorsed or recommended by
Toolbox for IT
or any vendor. If you feel a blog entry is inappropriate,
click here to notify
Toolbox for IT.

Follow one Network Engineer, rich in experience with network design, implementation, and administration of peer-to-peer, single ...
more

Follow one Network Engineer, rich in experience with network design, implementation, and administration of peer-to-peer, single server, and multi-location WAN networks, as he shares the methodologies of a new network documentation standard, NetworkDNA, and provides processes, structures, and best practices that will assist you in your own network documentation efforts.
less

Receive the latest blog posts:

Share Your Perspective

Share your professional knowledge and experience with peers. Start a blog on Toolbox for IT today!