OT: How to document a network?

Perhaps someone could help.
Does anyone know of a website that explains what items should be documented
for a network?
Things that I can think of for example are, each computers IP address, it's
OS, memory and processor. Also the wiring diagram of the network, domain
name and the like.
I have been charged with this project and need to get it right.

Maybe someone knows of a template of sorts that I can find that will make
this easier?

Thanks so much!

Hosh wrote:
> Does anyone know of a website that explains what items should be
> documented for a network?

Although to be honest I do not have any experience with this, but I thought
of a tool which might come in handy:
http://www.nagios.org
the only drawback might be that it runs on linux.
This tool monitors your network for failures and such. As you can see on the
screenshots page ( http://www.nagios.org/screenshot.php ) it also gives
quite a nice roadmap to your network, which might be nice to add to your
documents perhaps.

--
"Wisdom lies not in obtaining knowledge, but in using it in the right way"
- kroesjnov

http://www.securitydatabase.net
http://www.mostly-harmless.nl
http://www.outerbrains.nl
email: (E-Mail Removed)rnet (remove inter to reply)
UIN: 85685870
MSN: (E-Mail Removed)

"Hosh" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Perhaps someone could help.
> Does anyone know of a website that explains what items should be documented
> for a network?
> ...
> I have been charged with this project and need to get it right.
>
> Maybe someone knows of a template of sorts that I can find that will make
> this easier? ...

There's a book called "The Backup Book" (http://www.backupbook.com)
that goes through all the steps required for documenting a network and
preparing for systems continuity through any type of emergency.

One of the documentation tools used in the book is LANsurveyor,
<disclaimer>a tool made by Neon Software, the company I work
for.</disclaimer>

LANsurveyor automatically diagrams a network, including which nodes
are connected to each managed switches/hub. That's one piece. Then,
there's a special report in LANsurveyor called Backup Profiler, which
documents PCI cards, RAM, CPUs, disks, IP addresses, connectivity, and
more so you can be prepared to re-create everything, just in case.
That's one of the other key pieces you need.

Even if you don't purchase LANsurveyor, you can use it to get the
template you need to by using the free trial software:

http://www.neon.com/LSwin.html

I hope this helps.

Craig