Network Administration / Network Design and Documentation

Network documentation outline

Items necessary for good network documentation

1. Identification of servers, workstations, printers, routers, switches, etc.
1. IP addresses
2. NetBIOS/Host names
3. MAC addresses
2. Description of each device on the network, including make, model, serial number, and printouts from system inventory software (such as Belarc Advisor)
3. Network topology diagrams, including placement of servers, routers, switches, firewalls, IDS, etc.
1. Physical and logical diagrams
2. Layer 3 networking diagrams, including backbone and WAN links
4. Internet provider information
1. Description of link(s)
2. Contacts and support numbers
3. Terms of service
5. List of supported network operating systems (Win2K Server, NT4, NetWare 5, Linux, etc.)
6. List of supported client operating systems (Win2K Pro, Win98, MacOS, Linux, etc.)
7. List of supported network protocols (TCP/IP, IPX/SPX, AppleTalk, NetBEUI, etc.)
8. DHCP server settings, including scopes and options
9. Network security settings
1. Firewall configuration (including TCP and UDP ports open)
2. Router access lists
10. Troubleshooting history/administrator's activity log
1. Common problems and resolutions
2. Installation history
11. Network baseline information
1. Traffic flow and network utilization
2. Bandwidth utilization
3. Percent of collisions
4. Average server and workstation CPU utilization
5. Average server and workstation memory utilization
12. Fault tolerance mechanisms in place
1. Disk redundancy (e.g., RAID arrays)
2. Tape backup plan, including rotation and off-site storage
3. Clustering and failover systems
13. Physical location documentation
1. Building map
2. Room numbers
3. Availability of access keys
4. Unusual configuration information
14. Policies and procedures
1. Naming conventions

• Workstations and servers (NetBIOS and host names)
• Network equipment (e.g., routers and switches)
• Active Directory
• DNS

1. Points of contacts (IT director, administrators, help desk, etc.)
2. Disaster recovery plan

• Vendor phone numbers for support
• Remote access plan for administrators
• Higher-up administrator or consultant on call
• Virus prevention/recovery plan

1. Copies of maintenance plans, warranty agreements, and tech support contacts
2. Software licensing information
3. User rights policies, including Internet and e-mail usage