Network+ 2005 In Depth (P25) docx

reverse an upgrade. If you must backlevel a network operating system upgrade, you should also
consult with experienced professionals about the best approach for your network environment.
Table 15-1 Reversing a software upgrade
Type of Upgrade Options for Reversing
Operating system patch Use the patch’s automatic uninstall utility.
Client software upgrade Use the upgrade’s automatic uninstall utility or reinstall the previous
version of the client on top of the upgrade.
Shared application upgrade Use the application’s automatic uninstall utility or maintain a complete
copy of the previous installation of the application and reinstall it over
the upgrade.
Operating system upgrade Prior to the upgrade, make a complete backup of the system; to back-
level, restore entire system from the backup; uninstall an operating sys-
tem upgrade only as a last resort.
Hardware and Physical Plant Changes
Hardware and physical plant changes may be required when a network component fails or mal-
functions, but more often they are performed as part of an upgrade to increase capacity, improve
performance, or add functionality to the network. In this section, you will learn about the sim-
plest and most popular form of hardware change—adding more of what you already use, such
as adding four more switches to the backbone or adding 10 new networked printers. You also
learn about more complex hardware changes, such as replacing the entire network backbone
with a more robust system.
Many of the same issues apply to hardware changes as apply to software changes. In particu-
lar, proper planning is the key to a successful upgrade. When considering a change to your net-
work hardware, use the following steps as a guide:
1. Determine whether the change is necessary.
2. Research the upgrade’s potential effects on other devices, functions, and users.
3. If you decide to implement the change, notify system administrators, help desk personnel,
and users, and schedule it during off-hours (unless it is an emergency).
4. If possible, back up the current hardware’s configuration. Most hardware (for example,
routers, switches, and servers) has a configuration that you can easily copy to a disk.
In other cases (for example, networked printers), you may have to print the hardware’s

configuration.
5. Prevent users from accessing the system or the part of the system that you are changing.
692 Chapter 15
IMPLEMENTING AND MANAGING NETWORKS
6. Keep the installation instructions and hardware documentation handy.
7. Implement the change.
8. Test the hardware fully after the change, preferably putting a higher load on the
device than it would incur during normal use in your organization. Note any unin-
tended or unanticipated consequences of the change.
9. If the change was successful, re-enable access to the device. If it was unsuccessful, iso-
late the device or reinsert the old device, if possible.
10. Inform system administrators, help desk personnel, and users when the change is
complete. If it was not successful, explain why.
11. Record your change in the change management system.
Adding or Upgrading Equipment
The difficulty involved in adding or upgrading hardware on your network depends largely on
whether you have used the hardware in the past. For instance, if your organization always uses
Cisco switches, adding one more Cisco switch to your second-floor telecommunications closet
may take only a few minutes and cause absolutely no disruption of service to your users. On
the other hand, even if your company uses Cisco switches, adding a Cisco VPN router to your
network may be an entirely new experience. You should research, evaluate, and test any unfa-
miliar piece of equipment that you intend to add or upgrade on your network, even if it is
manufactured by a vendor that supplies much of your other hardware.
With the rapid changes in the hardware industry, you may not be able to purchase identical
hardware even from one quarter to the next. If consistency is a concern—for example, if your
technical staff is familiar with only one brand and model of printer, and you do not have the
time or money to retrain personnel—you would be wise to purchase as much hardware as pos-
sible in a single order. If this approach is not feasible, purchase equipment from vendors with
familiar products and solid reputations.
Each type of device that you add or upgrade on the network will have different preparation and

implementation requirements. Knowing exactly how to handle the changes requires not only a
close reading of the manufacturer’s instructions, but also some experience with the type of net-
working equipment at hand. The following list provides a very general overview of how you
might approach adding or upgrading devices on the network, from the least disruptive to the
most complex types of equipment. The devices at the bottom of the list are not only the most
disruptive and complex to add or upgrade, but also the most difficult to remove or backlevel.
◆ Networked workstation—A networked workstation is perhaps the simplest device to
add. It directly affects only a few users, and does not alter network access for anyone
else. If your organization has a standard networked workstation configuration (for
example, a disk image—a compressed snapshot of the workstation’s contents—on
the server), adding a networked workstation will be a quick operation as well. You
can successfully add a networked workstation without notifying users or support
staff and without worrying about downtime.
Chapter 15 693
HARDWARE AND PHYSICAL PLANT CHANGES
◆ Networked printer—A networked printer is easy to add to your network, too. Adding this
equipment is slightly more complex than adding a networked workstation, however,
because of its unique configuration process and because it is shared. Although it affects
multiple users, a networked printer does not typically perform a mission-critical function
in an organization, so the length of time required to install one does not usually affect
productivity. Thus, although you should notify the affected users of a networked printer
addition, you do not need to notify all users and support staff. Likewise, you do not need
to restrict access to the network or worry about downtime in this instance.
◆ Hub or access point—A single hub or access point might service as few as one or as
many as 64 users. You do not have to worry about downtime or notifying users when
adding a new hub or access point, because it cannot affect anyone until it is actually
in use. However, if you are upgrading or swapping out an existing hub or access
point, you must notify the affected users, because the upgrade or swap will create
downtime. In addition, you must consider the traffic and addressing implications of
adding or upgrading a hub or access point. For example, if you need to expand the

capacity of a TCP/IP-based network segment from 24 users to 60 users, you can
easily enough swap your 24-port hub with a 64-port hub. But before doing so, make
sure that the segment has been allotted enough free IP addresses to service 60 users;
otherwise, these users will not be able to access the network.
◆ Server—A server addition or upgrade can be tricky. Typically, this type of change (unless
it is the replacement of a minor component) requires a great deal of foresight and plan-
ning. Before installing a new server, you need to consider the hardware and connectivity
implications of the change, as well as issues relating to the NOS. Even if you are adding a
server that will not be used immediately, you still need to plan for its installation. It’s
preferable to add the server while network traffic is low or nonexistent. You should also
restrict access to the new server; otherwise, one of your users could find the server while
browsing the network and try to save files to it or run an application from it.
Upgrading the hardware (such as a NIC or memory) on an existing server may
require nearly as much planning as adding an entirely new server. Schedule upgrades
to an existing server for off-hours, so that you can shut down the server without
inconveniencing any users who rely on it.
◆ Switches and routers—Changing or adding switches or routers to a network design is
more complicated for several reasons. First, this type of change can be physically dis-
ruptive—for example, it might require the installation of new racks or other support
frames in your telecommunications room. Second, switches and routers usually affect
many users—and might affect all users—on the network. For instance, if you must
replace the Internet gateway for your organization’s headquarters, you will cut every
user’s access to the Internet in the process (unless you have redundant gateways,
which is the optimal setup if you rely on the Internet for mission-critical services).
You should notify all users on the network about the impending change, even if you
don’t think they will be affected—sometimes a router or switch may have unin-
694 Chapter 15
IMPLEMENTING AND MANAGING NETWORKS
tended effects on segments of the network other than the one it services. In addi-
tion, you should plan at least weeks in advance for switch or router changes and

expect at least several hours of downtime. Because switches and routers are expen-
sive, take extraordinary care when handling and configuring the equipment. Also,
because switches and routers serve different purposes, you should rely on the manu-
facturer’s documentation to guide you through the installation process.
Chapter 15 695
HARDWARE AND PHYSICAL PLANT CHANGES
Bear in mind that adding a new processor to a server, a new NIC to a router, or more
memory to a printer may affect your service or warranty agreement with the manufac-
turer. Before purchasing any components to add or replace in your network devices,
check your agreement for stipulations that might apply. You may be allowed to add
only components made by the same manufacturer, or risk losing all support from that
manufacturer.
CAUTION
Above all, keep safety in mind when you upgrade or install hardware on a network. Never tin-
ker with the insides of a device that is turned on. Make sure that all cords and devices are stowed
safely out of the way and cannot cause trips or falls. Avoid wearing jewelry, scarves, or very
loose clothing when you work on equipment; if you have long hair, tie it back. Not only will
you prevent injury this way, but you will also be less distracted. By removing metal jewelry, you
may prevent damage to the equipment caused by a short if the metal touches a circuit. If the
equipment is heavy (such as a large switch or server), do not try to lift it by yourself. Finally,
to protect the equipment from damage, follow the manufacturer’s temperature, ventilation, anti-
static, and moisture guidelines.
Cabling Upgrades
Cabling upgrades (unless they involve the replacement of a single faulty patch cable) may
require significant planning and time to implement, depending on the size of your network.
Remember from Chapter 12 that troubleshooting cabling problems may be difficult because
the cable layout may be undocumented and poorly planned, particularly if it was installed years
before and survived intact despite building changes and network growth. For the same reason,
an enterprise-wide cabling upgrade is complex. The best way to ensure that future upgrades go
smoothly is to carefully document the existing cable before making any upgrades. If this assess-

ment is not possible, you may have to compile your documentation as you upgrade the exist-
ing cabling.
Because a change of this magnitude affects all users on the network, you should upgrade the network
cabling in phases. Perhaps you can schedule an upgrade of the first-floor east wing of your building
one weekend, then the first-floor west wing of your building the next, and so on. Weigh the impor-
tance of the upgrade against its potential for disruption. For example, if the Payroll Department is
processing end-of-month checks and having no difficulties other than somewhat slow response
time, it is not critical to take away its access to install CAT 6 wiring. On the other hand, if the
building maintenance staff needs a 1-Gbps connection to run a new HVAC control system, you
will probably make it a priority to take down this access temporarily and replace the wiring. In this
case, not only must you replace the wiring, but you may also need to replace hubs and NICs.
For the most part, only organizations that run very small networks are able to upgrade or install their
own network cabling. Most other organizations rely on contractors who specialize in this service.
Nevertheless, as a networking professional you should know how to run a cable across a room, either
under a raised floor or through a ceiling plenum, in order to connect a device to the network.
Backbone Upgrades
The most comprehensive and complex upgrade involving network hardware is a backbone
upgrade. Recall that the network backbone represents the main conduit for data on LANs and
WANs, connecting major routers, servers, and switches. A backbone upgrade requires not only
a great deal of planning, but also the efforts of several personnel (and possibly contractors) and
a significant investment. You may upgrade parts of the backbone—a NIC in a router or a sec-
tion of cabling, for example—at any time, but upgrading the entire backbone changes the whole
network.
Examples of backbone upgrades include migrating from Token Ring to Ethernet, migrating
from a slower technology to a faster one, and replacing routers with switches (to make use of
VLANs, for example). Such upgrades may satisfy a variety of needs: a need for faster through-
put, a physical move or renovation, a more reliable network, greater security, more consistent stan-
dards, support of a new application, or greater cost-effectiveness. For example, the need for faster
throughput may prompt an upgrade from an older Ethernet technology to Gigabit Ethernet. Like-
wise, the need to support videoconferencing may require a backbone upgrade from CAT 5 to fiber-

optic cable.
If you recall the cabling and hardware required for different networking technologies (as
explained in Chapters 3 and 6), you get an idea of how far-reaching a backbone upgrade can
be. For example, to convert from Token Ring to Ethernet, you must replace or upgrade connectiv-
ity equipment such as hubs (or MAUs), switches, and routers. In addition, you must replace
the NIC in every workstation and printer on the network and change the configuration for
each device so that it works with Ethernet rather than Token Ring. For a small network, this
effort may not be more than a weekend’s work. For a network of thousands of users, such an
upgrade requires the services of a dedicated team.
Because backbone upgrades are expensive and time-consuming, the first step in approaching
such a project is to justify it. Will the benefits outweigh the costs? Can the upgrade wait a year
or more? If so, you might be wise to wait and find out whether a cheaper or better technical
solution becomes available later. Don’t try to wait until the technology “settles down,” because
networking progress never stands still. On the other hand, do wait to implement brand-new
technology until you can find out how it has worked on other networks similar to your own or
until the manufacturer eliminates most of the bugs.
696 Chapter 15
IMPLEMENTING AND MANAGING NETWORKS
The second step is to determine which kind of backbone design to implement. To make this
decision, you must analyze the future capacity needs of your network, decide whether you
want a distributed or collapsed backbone, determine whether you want to rely on switches or
routers, decide whether to use subnetting and to what extent, and so on. Although some of
these predictions will be guesswork, you can minimize the variables by examining the history
of your organization’s growth and needs.
After designing your backbone upgrade, develop a project plan to accomplish the upgrade.
Given that you don’t upgrade your backbone every day, you might want to contract this work
to a firm that specializes in network design and upgrades. In that case, you will draft an RFP
(request for proposal) to specify what that contractor should do. Regardless of whether you
employ specialists, your project plan should include a logical process for upgrading the back-
bone one section at a time (if possible). Because this process causes network outages, deter-

mine how best to proceed based on users’ needs. Choose a time when usage is low (such as
over a holiday) to perform your upgrade.
Reversing Hardware Changes
As with software changes, you should provide a way to reverse the hardware upgrade and rein-
stall the old hardware if necessary. If you are replacing a faulty component or device, this
restoration, of course, is not possible. If you are upgrading a component in a device, on the other
hand, you should keep the old component safe (for example, keep NICs in static-resistant
containers) and nearby. Not only might you need to put it back in the device, but you might
also need to refer to it for information. For example, if you have not documented the neces-
sary jumper settings for an interface card in a switch, the old card might indicate the jumper
settings needed on your new card. Even if the device seems to be operating well with the new
component, keep the old component for a while, especially if it is the only one of its kind at
your organization.
Chapter Summary
◆ Project management is the practice of managing staff, budget, timelines, and other
resources and variables so as to complete a specific goal within given bounds. The person
who designs the project plan and oversees the project is the project manager. A project
needs a plan, and also participants, funding, a specific means of communication, definitive
processes, contingency plans, and a testing and evaluation phase.
◆ The first step in project management is to conduct a feasibility study. A feasibility
study determines whether a proposed project fits within an organization’s budget,
time, and staff restrictions. It also attempts to weigh the benefits and costs of under-
taking a project.
◆ A needs assessment is the process of clarifying the reasons and objectives for a pro-
posed change. It involves interviewing users and other stakeholders and comparing
their perceptions to factual data. In addition, it may involve analyzing network
Chapter 15 697
CHAPTER SUMMARY
baseline data. Your goal in performing a needs assessment is to decide whether the
change is worthwhile and necessary and to determine the appropriate scope and

nature of the change.
◆ Project goals help keep a project on track. They are also necessary later for evaluat-
ing whether a project was successful. Project managers typically begin with a broad
goal, then narrow it down into specific goals that contribute to the larger goal.
◆ A project plan describes how the details of a managed project are organized. It
divides tasks and subtasks, dependencies, resource allocation, timelines, and mile-
stones. Project plans may take the form of a simple text or spreadsheet document for
small projects. Larger projects, however, often require the use of project management
software (such as Microsoft Project).
◆ When implementing a major network change, communicate with users about how
their access to the network will be affected; for how long their access to the network
will be affected; how their data will be protected during the change; whether you
will provide any means for users to access the network during the change; and
whether the change requires them to learn new skills.
◆ The best way to evaluate a large-scale network or systems implementation is to first
test it on a small scale on a pilot network. Although a pilot network differs from the
enterprise-wide network, it should mimic it closely enough to represent the larger
network’s hardware, software, connectivity, unique configurations, and load.
◆ Network management involves assessing, monitoring, and maintaining network
devices and connections.
◆ Baselining includes keeping a history of network performance, the physical topology,
logical topology, number of devices on the network, operating systems and protocols
in use, and number and type of applications in use. In other words, it provides a
complete picture of the network’s current state. Baselining provides the basis for
determining what types of changes might improve the network and for later evaluat-
ing how successful the improvements were.
◆ Assessing a network’s status on an ongoing basis includes performance management,
or monitoring how well links and devices are keeping up with the demands placed
on them, and fault management, or the detection and signaling of device, link, or
component faults.

◆ Network management applications typically use SNMP (Simple Network Manage-
ment Protocol) to communicate with agents running on managed devices. Agents
may report information on a device’s components or status (such as utilization or
performance).
◆ An asset management system includes an inventory of the total number of compo-
nents on the network as well as each device’s configuration files, model number, ser-
ial number, location on the network, and technical support contact. In addition, it
records every piece of software purchased by your organization, its version number,
vendor, and technical support contact.
698 Chapter 15
IMPLEMENTING AND MANAGING NETWORKS
◆ A patch is an enhancement or improvement to a part of a software application, often dis-
tributed at no charge by software vendors to fix a bug in their code or to add slightly more
functionality. Patches differ from revisions and software upgrades because they change
only part of the software application, leaving most of the code untouched.
◆ Make it a policy to keep informed about patches to your network software, whether
they involve the operating system, an application, or a client software. If you work in
a large organization with several servers, routers, and other devices, you may want to
assign one network administrator to manage patches for the servers, another to
manage patches for the printers, and so on.
◆ A software upgrade represents a major change to the existing code, which may or
may not be offered free from a vendor and may or may not be comprehensive
enough to substitute for the original application. An upgrade to the client software
replaces the existing client software so as to add functionality and fix bugs found in
the previous version.
◆ Before upgrading client software, carefully read the instructions that accompany the
upgrade to find out how best to apply it, whether it depends on any previous
upgrades, whether it requires any special preparation, and how its changes will affect
users. Client upgrades typically overwrite some system files on the workstation, so
their installation may affect other applications adversely.

◆ Like client upgrades, application upgrades consist of modifications to all or part of
an application that are designed to enhance functionality or fix problems with the
software. Application upgrades, however, affect software applications shared by
clients on the network.
◆ Perhaps the most critical type of software upgrade you’ll perform comprises an
upgrade to your network operating system. This effort usually involves significant,
potentially drastic, changes to the operation of your servers and clients. As such, it
requires plenty of forethought, product research, and rigorous testing before you
implement it. In fact, for any network with more than a few users, you should create
and follow a project plan for this undertaking.
◆ The process of upgrading an NOS should include research, proposal, evaluation,
training, pre-implementation, implementation, and post-implementation phases.
◆ You should plan for the possibility that a software upgrade might harm your existing
system (or systems), and be prepared to reverse the process. The restoration of a pre-
vious version of software after an attempted upgrade is known as backleveling.
◆ Hardware and physical plant changes may be required when your network has prob-
lems. More often, however, they are performed as part of a move to increase capac-
ity, improve performance, or add functionality to the network.
◆ Research, evaluate, and test any unfamiliar piece of equipment you intend to add or
upgrade on your network, even if it is manufactured by a vendor that supplies much
of your other hardware. The process of implementing a hardware upgrade is very
similar to that of carrying out a software upgrade, including notifying users and
preparing to bring the system down during the change.
Chapter 15 699
CHAPTER SUMMARY
◆ Cabling upgrades are simpler and less error-prone if a network’s cable plant is well
documented. Also make sure to document new cable infrastructure after making
changes. When embarking on a major cabling upgrade, such as a backbone replace-
ment, it is advisable to upgrade the infrastructure in phases.
◆ The most comprehensive and complex upgrade involving network hardware is a

backbone upgrade. The network backbone serves as the main conduit for data on
LANs and WANs, connecting major routers, servers, and/or switches. A backbone
upgrade not only requires a great deal of time to plan, but also the efforts of several
staff members (and possibly contractors) and a significant investment.
◆ You should provide a way to reverse a hardware upgrade and replace it with the old
hardware. If you are upgrading a component in a device, keep the old component
safe (for example, keep NICs in static-resistant containers) and nearby. Not only
might you need to put it back in the device, but you might also need to refer to it for
information.
Key Terms
agent—A software routine that collects data about a managed device’s operation and provides
it to the network management application running on the console.
asset management—The process of identifying and tracking an organization’s assets, such as
hardware and software.
backleveling—The process of reverting to a previous version of a software application after
attempting to upgrade it.
bug—A flaw in software or hardware that causes it to malfunction.
contingency planning—The process of identifying steps that minimize the risk of unforeseen cir-
cumstances endangering the quality or timeliness of the project’s goals.
fault management—The detection and signaling of device, link, or component faults.
feasibility study—A study that determines the costs and benefits of a project and attempts to pre-
dict whether the project will result in a favorable outcome (for example, whether it will achieve its
goal without imposing excessive cost or time burdens on the organization).
Gantt chart—A popular method of depicting when projects begin and end along a horizontal time-
line.
Management Information Base—See MIB.
MIB (Management Information Base)—A database used in network management that contains a
device’s definitions of managed objects and their data.
milestone—A reference point that marks the completion of a major task or group of tasks in a pro-
ject and contributes to measuring the project’s progress.

700 Chapter 15
IMPLEMENTING AND MANAGING NETWORKS
MRTG (Multi Router Traffic Grapher)—A command-line utility that uses SNMP to poll devices,
collects data in a log file, and then generates HTML-based views of the data. MRTG is freely dis-
tributed software originally written by Tobias Oetiker, a networking professional who in the early
1990s saw a need for a tool to regularly measure the status of his organization’s WAN link.
Multi Router Traffic Grapher—See MRTG.
needs assessment—The process of clarifying the reasons and objectives for a proposed change to
determine whether the change is worthwhile and necessary, and to elucidate the scope and nature of
the proposed change.
network management—The assessment, monitoring, and maintenance of the devices and connec-
tions on a network.
patch—A correction, improvement, or enhancement to part of a software application, often distrib-
uted at no charge by software vendors to fix a bug in their code or to add slightly more functional-
ity.
performance management—The ongoing assessment of how well network links, devices, and com-
ponents keep up with demands on them.
pilot network—A small-scale network that stands in for the larger network. A pilot network may
be used to evaluate the effects of network changes or additions.
polling—A network management application’s regular collection of data from managed devices.
predecessor—A task in a project that must be completed before other tasks can begin.
project management—The practice of managing staff, budget, timelines, and other resources
and variables to complete a specific goal within given bounds.
project plan—The way in which details of a managed project (for example, the timeline and
the significant tasks) are organized. Some project plans are created via special project planning
software, such as Microsoft Project.
service pack—A significant patch to one of the Microsoft Windows operating systems.
Simple Network Management Protocol—See SNMP.
SNMP (Simple Network Management Protocol)—An Application layer protocol in the
TCP/IP suite used to convey data regarding the status of managed devices on a network.

sponsor—A person in a position of authority who supports a project and who can lobby for
budget increases necessary to complete the project, appeal to a group of managers to extend a
project’s deadline, and assist with negotiating vendor contracts.
stakeholder—Any person who may be affected by a project, for better or for worse. A stake-
holder may be a project participant, user, manager, or vendor.
upgrade—A major change to the existing code in a software application, which may or may
not be offered free from a vendor, and may or may not be comprehensive enough to substitute
for the original application.
Chapter 15 701
KEY TERMS
Review Questions
1. A _________________________ is the process of clarifying the reasons and objec-
tives underlying a proposed change.
a. patch assessment
b. needs assessment
c. milestone
d. feasibility study
2. Which of the following refers to the correction, improvement, or enhancement to a
particular piece of a software application?
a. Milestone
b. Service pack
c. Gantt chart
d. Patch
3. _________________________ represent modifications to all or part of an application
that are designed to enhance functionality or fix problems related to software.
a. Application upgrades
b. Shared application upgrades
c. Project plans
d. Feasibility studies
4. _________________________ is necessary to ensure that all participants understand

the project’s goals, encourage teamwork, avoid duplicate efforts, and allow learning
from prior mistakes.
a. Contingency planning
b. Testing and evaluation
c. Communication
d. Setting timelines
5. _________________________ involves identifying and tracking the hardware and
software on your network.
a. Needs assessment
b. Contingency planning
c. Fault management
d. Asset management
702 Chapter 15
IMPLEMENTING AND MANAGING NETWORKS
6. True or false? Migrating from a Token Ring network to Ethernet is an example of a
backbone upgrade.
7. True or false? A contingency plan is a popular method for depicting when projects
begin and end along a horizontal timeline.
8. True or false? You do not have to worry about downtime or notifying users when
adding a new hub or access point, because it cannot affect anyone until it is actually in
use.
9. True or false? The detection and signaling of device, link, or component faults is
known as performance management.
10. True or false? A small-scale network that stands in for a larger network is sometimes
called a pilot network.
11. A(n) _________________________ is a reference point that marks the completion of
a major task or group of tasks in the project and contributes to measuring the project’s
progress.
12. A(n) _________________________ outlines the costs and benefits of the project and
attempts to predict whether it will result in a favorable outcome.

13. _________________________ is the process of identifying steps that minimize the
risk of unforeseen events that could affect the quality or timeliness of the project’s
goals.
14. The process of reverting to a previous version of software after attempting to upgrade
is known as _________________________.
15. _________________________ is the practice of managing staff, budget, timelines,
and other resources and variables to achieve a specific goal within given bounds.
Chapter 15 703
REVIEW QUESTIONS
This page intentionally left blank
Network+
Examination
Objectives
Appendix A
This book covers all of the Network+ examination objectives, which were
released by CompTIA (the Computing Technology Industry Association)
in 2005. The official list of objectives is available at CompTIA’s Web site,
www.comptia.org. For your reference, the following table lists each exam
objective and the chapter of this book that explains the objective, plus the
amount of the exam that will cover each certification domain. Each objec-
tive belongs to one of four domains (or main topics) of networking exper-
tise. For example, the objective of recognizing an RJ-45 connector belongs
to the “Media and Topologies” domain, which accounts for 20% of the
exam’s content.
Domain 1.0 Media and Topologies—
20% of Examination
Table A-1 Network+ Examination Objectives—Media and Topologies
Objective Chapter
1.1 Recognize the following logical or physical network topologies given a
diagram, schematic or description:

Star 1, 6, 7
Bus 1, 6, 7
Mesh 7
Ring 1, 6, 7
1.2 Specify the main features of 802.2 (Logical Link Control), 802.3
(Ethernet), 802.5 (token ring), 802.11 (wireless), and FDDI (Fiber Distributed
Data Interface) networking technologies, including:
Speed 3, 6
Access method (CSMA / CA (Carrier Sense Multiple Access / Collision
Avoidance) and CSMA / CD (Carrier Sense Multiple Access / Collision
Detection)) 3, 6
Topology 6
Media 3, 6
1.3 Specify the characteristics (For example: speed, length, topology, and cable
type) of the following cable standards:
10BASE-T and 10BASE-FL 3
100BASE-TX and 100BASE-FX 3
1000BASE-T, 1000BASE-CX, 1000BASE-SX and 1000BASE-LX 3
10 GBASE-SR, 10 GBASE-LR and 10 GBASE-ER 3
1.4 Recognize the following media connectors and describe their uses:
RJ-11 (Registered Jack) 3, Appendix C
RJ-45 (Registered Jack) 3, Appendix C
F-Type 3, Appendix C
ST (Straight Tip) 3, Appendix C
Table A-1 Continued
Objective Chapter
SC (Subscriber Connector or Standard Connector) 3, Appendix C
IEEE 1394 (FireWire) 5, Appendix C
Fiber LC (Local Connector) 3, Appendix C
MT-RJ (Mechanical Transfer Registered Jack) 3, Appendix C

USB (Universal Serial Bus) 5, Appendix C
1.5 Recognize the following media types and describe their uses:
Category 3, 5, 5e, and 6 3
UTP (Unshielded Twisted Pair) 3
STP (Shielded Twisted Pair) 3
Coaxial cable 3
SMF (Single Mode Fiber) optic cable 3
MMF (Multimode Fiber) optic cable 3
1.6 Identify the purposes, features and functions of the following network
components:
Hubs 3, 5
Switches 5, 7
Bridges 5
Routers 5, 11, 14
Gateways 5, 11, 14
CSU / DSU (Channel Service Unit / Data Service Unit) 7
NICs (Network Interface Cards) 1, 5
ISDN (Integrated Services Digital Network) adapters 7
WAPs (Wireless Access Points) 3, 5, 6
Modems 3, 7
Transceivers (media converters) 3
Firewalls 5, 14
1.7 Specify the general characteristics (For example: carrier speed, frequency,
transmission type and topology) of the following wireless technologies:
802.11 (Frequency hopping spread spectrum) 3, 6
802.11x(Direct sequence spread spectrum) 3, 6
Infrared 3, 6
Bluetooth 3, 6
1.8 Identify factors which affect the range and speed of wireless service (For
example: interference, antenna type and environmental factors). 3

Appendix A 707
DOMAIN 1.0 MEDIA AND TOPOLOGIES
Domain 2.0 Protocols and Standards—
20% of Examination
Table A-2 Network+ Examination Objectives—Protocols and Standards
Objective Chapter
2.1 Identify a MAC (Media Access Control) address and its parts. 2
2.2 Identify the seven layers of the OSI (Open Systems Interconnect) model
and their functions. 2
2.3 Identify the OSI (Open Systems Interconnect) layers at which the
following network components operate:
Hubs 2, 5
Switches 5
Bridges 5
Routers 2, 5
NICs (Network Interface Cards) 2, 5
WAPs (Wireless Access Points) 3, 5
2.4 Differentiate between the following network protocols in terms of routing,
addressing schemes, interoperability and naming conventions:
IPX / SPX (Internetwork Packet Exchange / Sequence Packet Exchange) 4
NetBEUI (Network Basic Input / Output System Extended User Interface) 4
AppleTalk / AppleTalk over IP (Internet Protocol) 4
TCP / IP (Transmission Control Protocol / Internet Protocol) 4, 11
2.5 Identify the components and structure of IP (Internet Protocol) addresses
(IPv4, IPv6) and the required setting for connections across the Internet. 4, 11
2.6 Identify classful IP (Internet Protocol) ranges and their subnet masks (For
example: Class A, B and C). 4, 11
2.7 Identify the purpose of subnetting. 4, 11
2.8 Identify the differences between private and public network addressing
schemes. 11

2.9 Identify and differentiate between the following IP (Internet Protocol)
addressing methods:
Static 3
Dynamic 3
Self-assigned (APIPA (Automatic Private Internet Protocol Addressing)) 3
708 Appendix A
NETWORK+ EXAMINATION OBJECTIVES
Table A-2 Continued
Objective Chapter
2.10 Define the purpose, function and use of the following protocols used in
the TCP/IP (Transmission Control Protocol/Internet Protocol) suite:
TCP (Transmission Control Protocol) 2, 4
UDP (User Datagram Protocol) 2, 4
FTP (File Transfer Protocol) 4
SFTP (Secure File Transfer Protocol) 14
TFTP (Trivial File Transfer Protocol) 4
SMTP (Simple Mail Transfer Protocol) 11
HTTP (Hypertext Transfer Protocol) 2, 4
HTTPS (Hypertext Transfer Protocol Secure) 14
POP3 / IMAP4 (Post Office Protocol version 3 / Internet Message Access
Protocol version 4) 11
Telnet 4
SSH (Secure Shell) 14
ICMP (Internet Control Message Protocol) 4
ARP / RARP (Address Resolution Protocol/Reverse Address Resolution
Protocol) 4
NTP (Network Time Protocol) 4
NNTP (Network News Transport Protocol) 4
SCP (Secure Copy Protocol) 14
LDAP (Lightweight Directory Access Protocol) 8

IGMP (Internet Group Multicast Protocol) 4
LPR (Line Printer Remote) 9
2.11 Define the function of TCP / UDP (Transmission Control Protocol / User
Datagram Protocol) ports. 4
2.12 Identify the well-known ports associated with the following commonly
used services and protocols: 4
20 FTP (File Transfer Protocol) 4
21 FTP (File Transfer Protocol) 4
22 SSH (Secure Shell) 4
23 Telnet 4
25 SMTP (Simple Mail Transfer Protocol) 4
53 DNS (Domain Name Service) 4
69 TFTP (Trivial File Transfer Protocol) 4
80 HTTP (Hypertext Transfer Protocol) 4
110 POP3 (Post Office Protocol version 3) 4
119 NNTP (Network News Transport Protocol) 4
Appendix A 709
DOMAIN 2.0 PROTOCOLS AND STANDARDS
Table A-2 Continued
Objective Chapter
123 NTP (Network Time Protocol) 4
143 IMAP4 (Internet Message Access Protocol version 4) 4
443 HTTPS (Hypertext Transfer Protocol Secure) 4
2.13 Identify the purpose of network services and protocols (For example:
DNS (Domain Name Service), NAT (Network Address Translation), ICS
(Internet Connection Sharing), WINS (Windows Internet Name Service),
SNMP (Simple Network Management Protocol), NFS (Network File
System), Zeroconf (Zero configuration), SMB (Server Message Block), AFP
(Apple File Protocol), LPD (Line Printer Daemon) and Samba). 4, 8, 9, 11, 14, 15
2.14 Identify the basic characteristics (For example: speed, capacity and

media) of the following WAN (Wide Area Networks) technologies:
Packet switching 6
Circuit switching 6
ISDN (Integrated Services Digital Network) 7
FDDI (Fiber Distributed Data Interface) 6
T1 (T Carrier level 1) / E1 / J1 7
T3 (T Carrier level 3) / E3 / J3 7
OCx (Optical Carrier) 7
X.25 7
2.15 Identify the basic characteristics of the following internet access
technologies:
xDSL (Digital Subscriber Line) 7
Broadband Cable (Cable modem) 7
POTS / PSTN (Plain Old Telephone Service / Public Switched Telephone
Network) 7
Satellite 7
Wireless 7
2.16 Define the function of the following remote access protocols and services:
RAS (Remote Access Service) 7
PPP (Point-to-Point Protocol) 7
SLIP (Serial Line Internet Protocol) 7
PPPoE (Point-to-Point Protocol over Ethernet) 7
PPTP (Point-to-Point Tunneling Protocol) 7
VPN (Virtual Private Network) 7
RDP (Remote Desktop Protocol) 7
710 Appendix A
NETWORK+ EXAMINATION OBJECTIVES
Table A-2 Continued
Objective Chapter
2.17 Identify the following security protocols and describe their purpose and

function:
IPSec (Internet Protocol Security) 14
L2TP (Layer 2 Tunneling Protocol) 7
SSL (Secure Sockets Layer) 14
WEP (Wired Equivalent Privacy) 14
WPA (Wi-Fi Protected Access) 14
802.1x 14
2.18 Identify authentication protocols (For example: CHAP (Challenge
Handshake Authentication Protocol), MS-CHAP (Microsoft Challenge
Handshake Authentication Protocol), PAP (Password Authentication Protocol),
RADIUS (Remote Authentication Dial-In User Service), Kerberos and EAP
(Extensible Authentication Protocol)). 14
Domain 3.0 Network Implementation—
25% of Examination
Table A-3 Network+ Examination Objectives—Network Implementation
Objective Chapter
3.1 Identify the basic capabilities (For example: client support, interoperability,
authentication, file and print services, application support and security) of the
following server operating systems to access network resources:
UNIX / Linux / Mac OS X Server 9
Netware 10
Windows 8
Appleshare IP (Internet Protocol) 9
3.2 Identify the basic capabilities needed for client workstations to connect to
and use network resources (For example: media, network protocols and peer and
server services). 3, 4, 8
3.3 Identify the appropriate tool for a given wiring task (For example: wire
crimper, media tester / certifier, punch down tool or tone generator). 3
Appendix A 711
DOMAIN 3.0 NETWORK IMPLEMENTATION

Table A-3 Network+ Examination Objectives—Network Implementation
Objective Chapter
3.4 Given a remote connectivity scenario comprised of a protocol, an
authentication scheme, and physical connectivity, configure the connection.
Includes connection to the following servers:
UNIX / Linux / MAC OS X Server 4, 8, 9, 10
Netware 4,8,9,10
Windows 4, 8, 9, 10
Appleshare IP (Internet Protocol) 4, 8, 9, 10
3.5 Identify the purpose, benefits and characteristics of using a firewall. 14
3.6 Identify the purpose, benefits and characteristics of using a proxy service. 14
3.7 Given a connectivity scenario, determine the impact on network
functionality of a particular security implementation (For example: port
blocking/filtering, authentication and encryption). 14
3.8 Identify the main characteristics of VLANs (Virtual Local Area Networks). 5
3.9 Identify the main characteristics and purpose of extranets and intranets. 11
3.10 Identify the purpose, benefits and characteristics of using antivirus software. 13
3.11 Identify the purpose and characteristics of fault tolerance:
Power 13
Link redundancy 13
Storage 13
Services 13
3.12 Identify the purpose and characteristics of disaster recovery:
Backup / restore 13
Offsite storage 13
Hot and cold spares 13
Hot, warm and cold sites 13
712 Appendix A
NETWORK+ EXAMINATION OBJECTIVES
Domain 4.0 Network Support—

35% of Examination
Table A-4 Network+ Examination Objectives—Network Support
Objective Chapter
4.1 Given a troubleshooting scenario, select the appropriate network utility from
the following:
Tracert / traceroute 11
ping 4, 11
arp 4
netstat 11
nbtstat 11
ipconfig / ifconfig 4, 11
winipcfg 11
nslookup / dig 11
4.2 Given output from a network diagnostic utility (For example: those utilities
listed in objective 4.1), identify the utility and interpret the output. 4, 11
4.3 Given a network scenario, interpret visual indicators (For example: link
LEDs (Light Emitting Diodes) and collision LEDs (Light Emitting Diodes))
to determine the nature of a stated problem. 5
4.4 Given a troubleshooting scenario involving a client accessing remote
network services, identify the cause of the problem (For example: file services,
print services, authentication failure, protocol configuration, physical
connectivity and SOHO (Small Office / Home Office) router). 7, 12
4.5 Given a troubleshooting scenario between a client and the following
server environments, identify the cause of a stated problem:
UNIX / Linux / Mac OS X Server 9, 12
Netware 10, 12
Windows 8, 12
Appleshare IP (Internet Protocol) 8, 12
4.6 Given a scenario, determine the impact of modifying, adding or removing
network services (For example: DHCP (Dynamic Host Configuration Protocol),

DNS (Domain Name Service) and WINS (Windows Internet Name Service))
for network resources and users. 4, 12
Appendix A 713
DOMAIN 4.0 NETWORK SUPPORT
Table A-4 Continued
Objective Chapter
4.7 Given a troubleshooting scenario involving a network with a particular
physical topology (For example: bus, star, mesh or ring) and including a
network diagram, identify the network area affected and the cause of the stated
failure. 6, 12
4.8 Given a network troubleshooting scenario involving an infrastructure (For
example: wired or wireless) problem, identify the cause of a stated problem
(For example: bad media, interference, network hardware or environment). 4, 12
4.9 Given a network problem scenario, select an appropriate course of action
based on a logical troubleshooting strategy. This strategy can include the
following steps:
1. Identify the symptoms and potential causes 12
2. Identify the affected area 12
3. Establish what has changed 12
4. Select the most probable cause 12
5. Implement an action plan and solution including potential effects 12
6. Test the result 12
7. Identify the results and effects of the solution 12
8. Document the solution and process 12
714 Appendix A
NETWORK+ EXAMINATION OBJECTIVES
Network+
Practice Exam
Appendix B
The following exam contains questions similar in content and format to

what you will encounter on CompTIA’s Network+ certification exam. The
exam consists of 65 questions, all of which are multiple choice. Some ques-
tions have more than one answer, and some questions require that you study
a figure to determine the right answer.The questions are in no particular
order.The number of questions on each topic reflects the weighting that
CompTIA assigned to these topics in their 2005 exam objectives. If you
want to simulate taking the CompTIA Network+ certification exam, you
should allow yourself 90 minutes to answer all of the questions.
716 Appendix B
NETWORK+ PRACTICE EXAM
1. What TCP/IP utility would you use to determine the number of hops between two
routers?
a. FTP
b. Nslookup
c. Nbtstat
d. Tracert
e. Telnet
2. You are the network administrator for a NetWare 6.5 network that runs the TCP/IP
protocol. A new user in your organization can log on to the NetWare server, but can-
not retrieve her spreadsheet files.Which two of the following situations could be the
cause of her problem?
a. She has entered the wrong user name or password.
b. She does not have permission to read files in the directory where the spread-
sheets are stored.
c. Her network cable is not inserted into her workstation’s NIC.
d. She does not have permission to view files on the volume where the spread-
sheets are stored.
e. The DHCP settings in her workstation’s TCP/IP configuration are incorrect.
3. Which of the following figures reflects the type of physical topology commonly used
on a 100BASE-TX network?

a.
b.