[K12OSN] Documenting the Network

[David L. Willson]

Shapes you might need for doing drawings with OO Draw.

http://www.lautman.net/mark/coo/index.html

--David

----- "Rob Owens" <rowens at ptd.net> wrote:

> OpenOffice Draw has similar abilities, although I don't know if it's
> got the same pre-built graphics for routers, etc.
> 
> -Rob
> 
> On Thu, Mar 19, 2009 at 11:52:56AM -0600, David L. Willson wrote:
> > dia can be used to create basic network maps with switches, routers,
> servers, etc.  Not sure if that's already been mentioned or not.  I
> hear Kivio does this sort of thing, too, but I haven't used it.
> > 
> > David L. Willson
> > Trainer, Engineer, Enthusiast
> > MCT, MCSE, Linux+
> > tel://720.333.LANS
> > Freeing people from the tyranny (or whatevery) of Microsofty-ness,
> one at a time.
> > 
> > ----- "\"Terrell Prudé Jr.\"" <microman at cmosnetworks.com> wrote:
> > 
> > > j.w. thomas wrote:
> > > 
> > > How do you guys document your networking environment?
> > > 
> > > I am the sole admin of a small system, and it just seems bad
> practice
> > > for the sole repository of all that info to be my head. For one,
> my
> > > head is notoriously unreliable for that sort of thing. Also, it
> can't
> > > be backed up.
> > > 
> > > Right now I have a small setup with a firewall, an ltsp server,
> five
> > > clients, a wireless connection, and a stand-alone workstation.
> More to
> > > come later (printers, more services, etc).
> > > 
> > > I'm planning to fire up an svn server to use as a repo for all
> the
> > > /etc directories on all the machines. I also have a text file
> with
> > > descriptions of every technical detail I could think to put in
> it:
> > > equipment specs, models, location, function, wireless encryption
> keys,
> > > power feeds (i.e., ups or not), ip addresses, services, etc.
> > > 
> > > I intend to draw a network map tonight, and I'm going to print
> that
> > > and the text file out and keep them in the network closet, maybe
> > > hanging on the wall. I'm also thinking that I will write the root
> > > passwords down on a piece of paper, seal it in an envelope, and
> put it
> > > in the network closet. That might seem like a bad idea, but if
> they
> > > can get in the network closet, they can already pwn the system. A
> > > sealed envelope would provide for an easy way to get the info
> should
> > > something happen to me, and would provide a pretty decent
> indication
> > > that the info had been accessed. Kind of an "In case of
> emergency,
> > > break glass" approach.
> > > 
> > > Is there a better way to store all this info? Maybe some software
> > > (FLOSS only please) has been written to deal with this already?
> What
> > > do you guys do?
> > > 
> > > 
> > > 
> > > I draw pictures and type up a description. Then this stuff goes in
> a
> > > file labeled "Network Documentation." Yeah, I know, low-tech, but
> it
> > > works very, very well.
> > > 
> > > --TP
> > > 
> > > _______________________________
> > > Do you GNU ?
> > > Microsoft Free since 2003 --the ultimate antivirus protection!
> > > 
> > > 
> > > _______________________________________________
> > > K12OSN mailing list
> > > K12OSN at redhat.com
> > > https://www.redhat.com/mailman/listinfo/k12osn
> > > For more info see <http://www.k12os.org>
> > 
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN at redhat.com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>