J/SHS

TLE/TVL-ICT (Computer System

Servicing)
Learning Activity Sheet
Quarter 2 – L.O. 4 Inspect
and Test the Configured
Computer Networks

Documentation Procedures

REGION VI – WESTERN VISAYAS

1
 Quarter 2, Week 8
TLE/TVL – CSS Grade 12
Activity Sheet No. 8
First Edition, 2020

Published in the Philippines

By the Department of Education
Region 6 – Western Visayas

Republic Act 8293, section 176 states that: No copyright shall subsist in any
work of the Government of the Philippines. However, prior approval of the government
agency or office wherein the work is created shall be necessary for exploitation of such
work for profit. Such agency or office may, among other things, impose as a condition
the payment of royalties.

This Learning Activity Sheet is developed by DepEd Region 6 – Western

Visayas.

ALL RIGHTS RESERVED. No part of this learning resource may be reproduced

or transmitted in any form or by any means electronic or mechanical without written
permission from the DepEd Regional Office 6 – Western Visayas.

Development Team of CSS Learning Activity Sheet

Writer : Hope T. Mosquera / Allan Montenegro
Illustrators :
Editor : Allan Montenegro
Layout Artist :
Schools Division Quality Assurance Team:
Schubert Anthony C. Sialongo
Edward E. Baña
Allan B. Montenegro
Michelle P. Jordan
Division of Antique Management Team:
Felisa B. Beriong, CESO VI
Corazon C. Tingson
Gaudencio C. Riego, PhD
Schubert Anthony C. Sialongo
Edward E. Baña
Regional Management Team
Ma. Gemma M. Ledesma,
Dr. Josilyn S. Solana,
Dr. Elena P. Gonzaga,
Mr. Donald T. Genine,
(Learning Area EPS)

2
Introductory Message
Welcome to Computer System Servicing NCII for Grade 10!

The Learning Activity Sheet is a product of the collaborative efforts of the

Schools Division of Antique and DepEd Regional Office VI - Western Visayas through
the Curriculum and Learning Management Division (CLMD). This is developed to guide
the learning facilitators (teachers, parents and responsible adults) in helping the learners
meet the standards set by the K to 12 Basic Education Curriculum.

The Learning Activity Sheet is self-directed instructional materials aimed to

guide the learners in accomplishing activities at their own pace and time using the
contextualized resources in the community. This will also assist the learners in acquiring
the lifelong learning skills, knowledge and attitudes for productivity and employment.

For learning facilitator:

The Computer System Servicing NCII Activity Sheet will help you facilitate the
teaching-learning activities specified in each Most Essential Learning Competency
(MELC) with minimal or no face-to-face encounter between you and learner. This will be
made available to the learners with the references/links to ease the independent learning.

For the learner:

The Computer System Servicing NCII Activity Sheet is developed to help you
continue learning even if you are not in school. This learning material provides you with
meaningful and engaging activities for independent learning. Being an active learner,
carefully read and understand the instructions then perform the activities and answer the
assessments. This will be returned to your facilitator on the agreed schedule

3
 Learning Activity Sheets (LAS)

Name of Learner: ___________________________________________________

Grade and Section:_______________________________ Date: ______________

COMPUTER SYSTEM SERVING NCII ACTIVITY SHEET

Documentation Procedure

I. Documentation Procedure
TLE_IACSS9-12SUCN-IIf-j-36
✓ 4.4 Prepare reports according to company requirements
✓ 4.5 Complete reports according to company requirements

II. Background Information for Learners

Although network
documentation is always a
good idea, it's especially
important for service providers
and value-added resellers.
Documenting your customers'
networks can make the
troubleshooting process much
more efficient when problems
arise. These same network
documents can help you spot
areas of your
customers' networks that may
need to be upgraded, possibly
providing you with extra
revenue. Finally, good network
documentation proves that you
adhere to industry best
practices, and it could be your best defence should a customer ever file litigation against
you for something network-related.

What Is Network Documentation?

Network documentation is a type of specialised technical documentation. It is the
practice of keeping records relating to the networks of computers that the customer is
using. This documentation gives a glimpse to the administrators about the look of the
network, its performance and where to troubleshoot when issues arise. Complete
network documentation, along with a comprehensive network diagram, will help you
reach your intended goals.

4
Benefits of Network Documentation
There are many benefits of network documentation, especially for service providers:
• It allows for efficient handling of issues when they arise.
• It also points out those areas of the client network that require upgrading.
• It will become your best defense if ever a client files a network-related complaint
against you.

Network Documentation Checklist and Best Practices

Step 1: Create a network documentation policy
A network documentation policy should detail what aspects of a network need to be
documented, especially each server. A documentation policy also communicates to
each administrator exactly what is expected of them regarding the documentation
process.

Step 2: Create a network topology diagram

Ideally, you want this map of the network's topology to include each network segment,
the routers connecting the various segments, and the servers, gateways and other
major pieces of networking hardware that are connected to each segment. For larger
networks, you may have to create a general segment map and make more specific
maps of each individual segment.

Step 3: Document server names, roles and IP addresses

While the information included in a network topology diagram is not necessarily
specific, there is certain information that you should include for each server, even if that
information has to be placed in an appendix. For each server, list the server's name, its
IP address and the role the server performs (domain name system, Dynamic Host
Configuration Protocol, mail server, etc.). Keep in mind that a server may be assigned
multiple IP addresses or have multiple network interface cards, so you should
document that information too.

Step 4: Create a change log for each server

When a server fails, the failure can often be traced to a recent change. As a part of the
network documentation, consider making a log book for each server for documenting
changes such as patch and application installations and modified security settings. Not
only will the log help you troubleshoot future problems, but it can also help you rebuild
the server in the event of a catastrophic failure.

Step 5: Document software versions and proof of licenses

Document the applications and their versions running on each server. You might also
include a copy of the software license or a receipt within this documentation just in case
your customer becomes involved in a software audit.

5
Step 6: Document hardware components
I have talked about documenting individual servers, but it's equally important to
document switches, routers, gateways and other networking hardware. The
documentation should include information such as the following:
✓ How is the device connected to the network?
✓ How is the device configured?
✓ Does a backup of the configuration exist?
✓ What firmware revision is the device running?
✓ Is the device configured to use a password? Don't include the actual password,
but you can include a password hint or a reference to the password being written
in a notebook that is stored in the safe.

Step 7: Document the Active Directory

I could probably write a book on Active Directory documentation, but here are a few
things that you should consider documenting:
✓ The names of the domains in the forest.
✓ The Active Directory site structure.
✓ Where the various servers exist within the Active Directory hierarchy.
✓ The location and contents of each group policy.
✓ Any external trusts that may exist.

Step 8: Document your backup procedures

Backup is your customer's best defence against a catastrophe, but it will do little good if
nobody can figure out how to use it. Be sure to document the backup software
used and its version (very important). You will also want to document the tape rotation
scheme, a general description of what's included in each backup job and where the
backup tapes are stored.

Step 9: Label everything

I once had a client ask me to do a consulting project for them. They gave me a
thorough and well-written copy of their network documentation to review ahead of time.
But when I got on site, I realized that none of the hardware was labelled. All of the
servers looked identical, and there was no way to differentiate between them.

Get a label maker and label all servers, critical hardware components (gateways,
routers, etc.) and the most important cables. This will make it easy to identify the
various pieces of hardware listed in your network document.

Step 10: Evaluate your documentation

The last step in this network documentation checklist is to evaluate your documentation
to make sure it's sufficient for you and your customer's needs. Think of your network
6
documentation as a critical part of your disaster recovery strategy. When the first
draft of your documentation is complete, you must ask yourself if it's good enough to
help someone with no prior knowledge of the setup to rebuild the network from scratch
in the event of a catastrophe. If the answer is yes, then you've done a good job on the
documentation.

III. For additional information you may visit the following references:
https://searchitchannel.techtarget.com/feature/Channel-Checklist-10-steps-for-
network-documentation, Retrieved on December 12, 2020, 9:12 AM
https://dorksdelivered.com.au/it-solutions/how-to-create-network-documentation-best-
practices-checklist, Retrieved on December 12, 2020, 9:29 AM

IV. Activity Proper

1. Directions/ Instructions

a. Choose an institution or Business Company that has an existing network

infrastructure,
b. Draw the existing Network Topology; and
c. Gather technical information and supply available data needed in the table
below.

2. Exercises / Activities
2.1 Network Documentation
DSL Settings
ISP
Modem
DSL IP
Mask
Gateway
DNS
SMTP
POP3
LAN Settings
Domain
Network
Mask
Gateway
DNS
WINS
Servers
Printers
Static PC’s
Etc.
DHCP
Switches
PPTP

7
 Routers

IP Address Host Name Description Location

2.2 Refer to this criteria for your score.

Criteria Percentage Score

Originality of format lay-out of the
40%
documentation
Content of the report 30%
Accuracy 20%
Presentation 10%

PERFORMANCE RATING