Network technologies and trends

Jun 19 2008   1:52PM GMT

Sample Campus Network Documentation Policy

Yasir Irfan Yasir Irfan Profile: Yasir Irfan

Network Documentation Policy
1.0 Overview
This network documentation policy is an internal IT policy and defines the requirements for
network documentation. This policy defines the level of network documentation required such as
documentation of which switch ports connect to what rooms and computers. It defines who will
have access to read network documentation and who will have access to change it. It also defines
who will be notified when changes are made to the network.
2.0 Purpose
This policy is designed to provide for network stability by ensuring that network documentation
is complete and current. This policy should complement disaster management and recovery by
ensuring that documentation is available in the event that systems should need to be rebuilt. This
policy will help reduce troubleshooting time by ensuring that appropriate personnel are notified
when changes are made to the network.
3.0 Documentation
The network structure and configuration shall be documented and provide the following
information:
1. IP addresses of all devices on the network with static IP addresses.
2. Server documentation on all servers as outlined in the “Server Documentation”
document.
3. Network drawings showing:
a) The locations and IP addresses of all hubs, switches, routers, and firewalls on the
network.
b) The various security zones on the network and devices that control access
between them.
c) The locations of every network drop and the associated switch and port on the
switch supplying that connection.
d) The interrelationship between all network devices showing lines running between
the network devices.
e) All subnets on the network and their relationships including the range of IP
addresses on all subnets and net mask information.
f) All wide area network (WAN) or metropolitan area network (MAN) information
including network devices connecting them and IP addresses of connecting
devices.
4. Configuration information on all network devices including:
a) Switches
b) Routers
c) Firewalls
5. Configuration shall include but not be limited to:
a) IP Address
b) Netmask
c) Default gateway
d) DNS server IP addresses for primary and secondary DNS servers.
e) Any relevant WINS server information.
6. Network connection information including:
a) Type of connection to the internet or other WAN/MAN including T1,T3, frame
relay.
b) Provider of internet/WAN/MAN connection and contact information for sales and
support.
c) Configuration information including net mask, network ID, and gateway.
d) Physical location of where the cabling enters the building and circuit number.
4.0 Access
The IT networking and some enterprise security staff shall have full access to all network
documentation. The IT networking staff shall have the ability to read and modify network
documentation. Designated enterprise security staff shall have access to read and change network
documentation but those not designated with change access cannot change it. Help desk staff
shall have read access to network documentation.
5.0 Change Notification
The help desk staff, server administration staff, application developer staff, and IT management
shall be notified when network changes are made including.
a) Reboot of a network device including switches, routers, and firewalls.
b) Changes of rules or configuration of a network device including switches, routers, and
firewalls.
c) Upgrades to any software on any network device.
d) Additions of any software on any network device.
Notification shall be through email to designated groups of people.
6.0 Documentation Review
The network or IT manager shall ensure that network documentation is kept current by
performing a monthly review of documentation or designating a staff member to perform a
review. The remedy or help desk requests within the last month should be reviewed to help
determine whether any network changes were made. Also any current or completed projects
affecting network settings should be reviewed to determine whether there were any network
changes made to support the project.
7.0 Storage Locations
Network documentation shall be kept either in written form or electronic form in a minimum of
two places. It should be kept in two facilities at least two miles apart so that if one facility is
destroyed, information from the other facility may be used to help construct the IT infrastructure.
Information in both facilities should be updated monthly at the time of the documentation
review.

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: