Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Network Documentation

  • 23-04-2006 04:42PM
    #1
    Cork Skate
    Registered Users, Registered Users 2 Posts: 884 ✭✭✭


    Hi there,

    I am looking to find a few good websites that deal with Network Documentation. I have searched here and theres nothing and there is nothing of substance when i search on Google.

    Given that its such an important part, i actually thought there would be a bit more on it. Does anyone have any ideas on this?

    Any help would be great !!
    Cheers


Comments

  • #2
    ntlbell
    Registered Users, Registered Users 2 Posts: 16,287 ✭✭✭✭ntlbell


    What do you want to know exactly?


  • #3
    Cork Skate
    Registered Users, Registered Users 2 Posts: 884 ✭✭✭Cork Skate


    ntlbell wrote:
    What do you want to know exactly?

    Maybe some samples/templates .... what should be considered to be put in, what does it need to cover, in what kind of detail etc. I want to explain to a novice why it is so important to keep documentation and more importantly why it needs to be up to date. Anything and everything really.


  • #4
    ntlbell
    Registered Users, Registered Users 2 Posts: 16,287 ✭✭✭✭ntlbell


    Cork Skate wrote:
    Maybe some samples/templates .... what should be considered to be put in, what does it need to cover, in what kind of detail etc. I want to explain to a novice why it is so important to keep documentation and more importantly why it needs to be up to date. Anything and everything really.

    "It depends"

    The easiest way is probably start of with a network diagram, I usually start with the outer network and work my way in.

    what should be considered? _everything_ basically it should include every bit of information you would need to rebuild the network from scratch.

    The amount of detail would depend on how complex it is, but again _everything_ you would need to know to rebuild it from scratch or troubleshoot any part of the network.

    floor plans.
    physical/logical diagrams
    Hardware/Configs

    you get the idea...


  • #5
    Static M.e.
    Registered Users, Registered Users 2 Posts: 3,099 ✭✭✭Static M.e.


    I find Visio very good for network diagrams.
    Also try the SANS site you might find some worth while info

    As was mentioned for what to put in your network doc.
    You should put everything you need if you had to construct your network from the beginning tomorrow.
    I typically include alot of network diagrams (mostly because I like playing with Visio and hate typing) The different configs of the routers, switchs, ports, bandwidth, IP addresses of all firewalls, Switchs, Routers. From the public side and internal.
    Your DMZ config, Your mail config..
    If you wanted you could really put down a massive all inclusive document stating your firewall rules, why you allow somethings why not others. Also you could backup your routers and note any static routes you have enabled over the years.

    If you find anything you think usefull in your search post it back here. Incase you find something we have missed.

    Good luck


Advertisement