Sunteți pe pagina 1din 15

Chapter 12, Administering Change

Chapter 12, Lesson 1


Documenting a Running Network
1. Documentation
A. Preparing and maintaining network records are essential tasks that will
pay off when changes are necessary to a network.
B. Provides information about how the network should look and perform,
as well as where to seek help if there are problems.
C. Developed for maintenance, upgrading, and troubleshooting.
D. Documentation should contain:
1. A map of the entire network, including the locations of all hardware and
details of the cabling.
2. Server information, including the data on each server and the schedule
and locations of backups.
3. Software information, such as licensing and support details.
4. Essential names and telephone numbers for vendors, suppliers,
contractors, and other helpful contacts.
5. Copies of all service agreements.
6. A record of all problems, their symptoms and solutions, including dates,
contacts, procedures, and results.
E. Should be thorough, well organized, and stored where it is readily
available.

2. Establishing a Baseline
A. A baseline is documentation of the networks normal operating values.
B. Establish a baseline as soon as the network is operational.
C. Update the baseline whenever users, hardware, or software are added
to or subtracted from the system.
D. Baseline performance values can identify future needs for network
modifications.
E. Understanding how a healthy network functions is as important as
knowing how to solve problems after the network has failed.
F. Must be established over time before anything goes wrong.
G. Steps necessary to establish a baseline:
1. Record the model, serial number, and location of the servers,
workstations, and routers.
2. Record the warranty information for each device, and note where all such
warranty information is stored.
3. Make a copy of important system files such as AUTOEXEC.BAT and
CONFIG.SYS, as well as a complete set of system backup tapes.
4. Create a map of the network, noting the approximate distance between the
workstations and the server.
5. Documentation of cable runs can facilitate building inspections and help
to demonstrate compliance with regulations, such as fire codes, that
prescribe rules for cables placed in the plenum area of a building.
H. Helps to establish and identify:
1. Daily network utilization patterns
2. Bottlenecks
3. Heavy usage patterns
4. Different protocol traffic patterns

3. Documenting Network Performance


A. Overview
1. Establish a network performance baseline after verification that all
network connections are correct, all hardware is operational, and any
necessary system fine-tuning has been accomplished.
2. Network performance includes:
a. Servers
b. Server NICs
c. Cable connections to the NICs
d. Hubs
e. Cable runs
f. Routers
g. RJ-45 wall plates
h. Workstation NICs
3. Tools are available to help administrators document network
performance, including network monitors, protocol analyzers, and other
utilities.
B. Network Monitors
1. Overview
a. Tool that captures and filters data packets and analyzes network
activity.
b. Takes practice to quickly analyze the network performance statistics.
c. Software manufacturers offer network monitors.
2. Protocol Analyzers
a. Tool that keeps track of network statistics.
b. Can capture bad frames and isolate their source.
c. Can be helpful for a company that has a large network with highly
trained staff.
d. Can be inexpensive software programs that run on existing networked
computers.
e. More advanced and expensive protocol analyzers are special-purpose
portable computers that can be connected to any physical portion of
the network to better isolate data-transmission problems.
3. Packet Internet Groper (Ping)
a. A TCP/IP utility to test network connections.
b. Works by sending a message to a remote computer.

2 Outline, Chapter 12
Networking Essentials Plus, Third Edition
c. If the remote computer receives the message, it responds with a reply
message.
d. Reply message consists of:
(1) Workstations IP address
(2) Number of bytes in the message
(3) How long it took to reply in milliseconds (ms)
(4) Length of Time-To-Live (TTL) in seconds
e. The message Request timed out, means the remote workstation did
not respond before the TTL time expired.
f. Heavy network traffic or physical disconnection in the route to the
remote workstation can cause Request timed out.
4. Tracert
a. Utility that documents network performance.
b. UNIX equivalent is also called traceroute.
c. Identifies the route and number of hops the packet of data took to
arrive to at its destination.
C. Other TCP/IP Software Tools
1. Ipconfig
a. Diagnostic command that displays all current TCP/IP network
configuration values.
b. Useful for systems running Dynamic Host Configuration Protocol
(DHCP); allows users to determine how DHCP has configured
TCP/IP.
2. Winipcfg
a. Windows 95 and Windows 98 troubleshooting utility that enables
users to access information about TCP/IP and NIC settings.
b. Displays the following settings for each NIC installed:
(1) Physical address
(2) IP address
(3) Subnet mask
(4) Default gateway settings
3. Netstat
a. Available only if TCP/IP protocol is installed.
b. Utility lists:
(1) Connections and listening ports
(2) Ethernet statistics
(3) Addresses and port numbers
(4) Protocol connections and statistics
(5) Contents of the routing table
4. Nbtstat
a. Available only if TCP/IP protocol is installed.
b. Displays protocol statistics and current TCP/IP connections using
NetBIOS over TCP/IP.
c. Displays both client and server sessions.

Outline, Chapter 12 3
Networking Essentials Plus, Third Edition
(1) Listing the remote computers by IP address only.
(2) Attempts to convert the remote computer IP address to a name
using the HOSTS file.
d. Utility lists:
(1) Remote computers name table
(2) Remote computers name table using its IP address
(3) Contents of the NetBIOS name cache, giving the IP address of
each name
(4) Local NetBIOS names
(5) Name resolution statistics for Windows networking name
resolution

4. Bottlenecks
A. Overview
1. Network activities involve the coordinated actions of several devices.
2. Devices take a certain amount of time to perform transactions.
3. Devices using noticeably more CPU time result in poor performance.
4. Performance monitoring helps identify the problem device and bottleneck.
5. Administrator identifies devices taking too much time to perform tasks.
6. Bottlenecks usually indicate a need to upgrade a portion of the network.
B. Devices that often become bottlenecks:
1. CPUs
2. Memory
3. NICs
4. Disk controllers
5. Network media
C. Reasons a device becomes a bottleneck:
1. Inefficient use
2. Using other resources or CPU time more than it should
3. Too slow
4. Does not have the capacity to handle the load placed on it

5. Documenting Server Performance


A. Overview
1. Affected by an increase in the number of users on the system.
2. Comparing current performance statistics to initial baseline reveals faults.
3. Poor performance clues may come from end users first.
4. End users familiarity with system response is a good indicator of server
performance.
B. Performance Monitors
1. Track server performance on a network and can monitor several system
functions.
2. Observe the performance of a remote system and alert the system
administrator to server conditions that need attention.
3. Can transfer data to other performance tools.

4 Outline, Chapter 12
Networking Essentials Plus, Third Edition
C. Indicators that help locate and isolate problems with server
performance:
1. Demand for server resources
2. Areas of data congestion
3. Activity of an individual process

6. Total System Management


A. Overview
1. System management software complements other system management
utilities found in the NOS.
2. Vendors have developed utilities that do for system management what
performance monitors have done for system monitoring.
3. System management applications provide centralized management for
distributed systems programs.
4. System management software provides centralized administration of
computers in a WAN and includes:
a. Collecting hardware and software inventory information
b. Distributing and installing software
c. Sharing network applications
d. Troubleshooting hardware and software problems
B. Examples using Microsofts Systems Management Server (SMS)
include:
1. Inventory Management
a. Software collects and maintains an inventory of hardware and
software for each computer and stores it in a database.
b. Typical inventory items include the type of CPU, amount of RAM,
hard disk size, operating system, and application software for each
component installed.
2. Software Distribution
a. A utility that can install and configure new software or upgrade
previously installed software directly on a client.
b. Used to run commands, such as virus scan, on clients.
3. Shared Application Management
a. Shared applications that can be distributed to a server for clients to
access.
b. Management software builds folders on each client that contain other
folders and program icons that represent the shared applications.
c. These applications are actually stored on the server.
4. Remote Control and Network Monitor
a. Help Desk software and diagnostic utilities allow administrators to
control and monitor remote clients directly.
b. Diagnostic utilities allow administrators to view a clients current
configuration.

7. Maintaining a Network History


A. Networks Written Record

Outline, Chapter 12 5
Networking Essentials Plus, Third Edition
1. Indicates significant performance or equipment issues that real-time
monitoring might miss.
2. Provides a background to compare against current information.
B. Logbook
1. Important that all information be recorded in only one shared logbook.
2. Invaluable for tracing a performance problem or resolving network issues
related to system growth.
3. Network documentation should be easy to read and access.
4. Graphics and hand-drawn sketches can be very helpful.
5. History can be either logged online or in a notebook.
6. Storing on a hard disk can cause difficulties if the computer or disk
crashes.
C. Log Records Include:
1. Purchase and installation dates and descriptions
2. Complete information about key individuals, such as contractors
responsible for installation
3. Vendor, model, and warranty information, including serial numbers
4. Installation process and its results
5. Initial and subsequent network configurations
6. Network usage policies and procedures
7. Network resources and drive assignments
8. Copies of crucial network configuration files, such as CONFGI.SYS and
AUTOEXEC.BAT files
9. Unusual application program configurations
10. Particular computer, board, or peripheral settings
11. Problems and their solutions
12. Hardware or software changes
13. Activities that affect the topology or architecture
Chapter 12, Lesson 2
Upgrading a Network
1. Overview
A. Document the network, record the performance baseline, and identify
the need for an upgrade.
B. Determine which network elements can be upgraded and assess the
costs and benefits of doing so.

2. Deciding to Upgrade a Network


A. Timing the Upgrade
1. Addition of new programs and devices to a network is usually a slow
process.
2. Need to upgrade might not be immediately apparent, but will evolve
slowly over time.
3. Documenting network performance and listening to end users will help
determine when the time has come to upgrade the network.

6 Outline, Chapter 12
Networking Essentials Plus, Third Edition
4. If the response time of the CPU and network devices is too slow to
adequately handle increased user demand and the requirements of new
software.
5. Growing demands for resources might necessitate an upgrade.
6. Administrator can refer to the original network plan to review the types of
applications the network was initially intended to run.
B. Upgrading Network Architecture and Media
1. When to upgrade from copper-based media to fiber-optic media:
a. If devices have been added that create large amounts of electrical
interference.
b. If the size and number of networked buildings are expanding.
c. Fiber-optic media can be used for cable runs between remote
buildings.
d. If online conferencing or advanced Web applications at the desktop are
introduced.
2. Cost of fiber-optic media
a. Price is dropping, but installation of fiber-optic cable requires a
trained technician, which is an added expense.
b. NICs, hubs, and other network hardware will need to be upgraded at
the same time.
c. New network maintenance expenses are likely to arise that were not
incurred with simple, copper-based media.
3. Other options
a. Microwave send-and-receive station between the two buildings.
b. Use of microwave components in a network requires either line-of-
sight between the two stations or access to repeaters.
4. Other considerations
a. Consider the negative aspects of a potential upgrade as well as the
benefits.
b. In microwave networking, meteorological conditions merit
consideration: fog, rain, and snow can weaken and distort a microwave
signal.
C. Upgrading from a Peer-to-Peer to a Server-Based Network
1. The following indicate a need to upgrade to a server-based network:
a. Current peer-to-peer network causes inappropriate access to secure
information.
b. Organizational expansion.
c. Users having difficulty administering their own workstations.
d. Need for a dedicated file server.
e. Only one person understands how the network operates.
2. An upgrade to a server-based network will provide these benefits:
a. Network can handle more users.
b. Sensitive data will be secure from unauthorized users.
c. A knowledgeable network administrator can assist users.
d. Data backups will be easier to schedule and perform.

Outline, Chapter 12 7
Networking Essentials Plus, Third Edition
e. Workload of multiple servers can be balanced for better efficiency.
f. Servers can be physically isolated for additional security.
g. Servers that handle complex tasks can be upgraded for top
performance.
h. More advanced users can have their network components upgraded for
top performance.
3. By compiling supporting documentation that identifies areas in which
system performance needs to improve, network administrators can build a
case for appropriate change.

3. Server-Based Networks
A. Overview
1. Can be costly and difficult, although the advantages will frequently
outweigh the disadvantages.
2. A new server can be a good information-technology investment.
3. Benefits include faster processing of requests and the ability to handle
more users and run more sophisticated software applications.
4. Can consist of a single device or several servers that have been
interconnected for increased processing power.
B. Deciding to Upgrade a Server
1. Initial Considerations
a. Symptoms point to the need for a server upgrade.
b. Compare initial baseline values with the current values.
c. Start with the component of the server that is taking more time to
complete the task than it should.
d. Consult the servers manufacturer for information about the latest
products and choices for the network.
2. CPU and Memory
a. If the servers CPU requires extra time to exchange data between
memory and the disks, there might not be enough memory available for
the CPU to function efficiently.
b. If the CPU is busy over 80 percent of the time, the CPU or the amount
of memory might need to be upgraded.
c. Server Input/Output (I/O) devices can fail gradually.
d. Result is that requests for processor time from the device to the CPU
increase.
e. Servers should have enough RAM, disk space, and processing power
to allow end users to run their software applications efficiently without
having to wait for the server to retrieve, process, or store information.
3. NIC
a. Rise in the frequency of requests might indicate a failing controller.
b. Even if the controller and network cards are not failing, there could be
a benefit from upgrading to faster components.
c. If end users are complaining of slow system response and server
components are operating well, the problem might lie in an increase of
data received by the server.

8 Outline, Chapter 12
Networking Essentials Plus, Third Edition
d. As new employees are added and the amount of work per employee
increases, the maximum capacity of the network throughput might
soon be reached.
e. It is important to monitor network usage.
4. Disk Drives
a. Performance monitoring tools can check individual disks for excessive
activity.
b. When a disk has a slow response due to excess activity, balance disk
access by moving data to another disk.
5. Cost Considerations
a. The cost of servers is falling, and processing power continues to rise,
which can present a justification for proposing a general server
upgrade.
b. Despite falling costs, upgrading the server can be expensive, so it is
important to research the options carefully.
C. How to Upgrade a Server
1. Until recently, an engineer was needed to set up a medium-sized
computer.
2. Today, computers are assembled at the factory and often shipped with an
operating system installed on the hard drive.
3. A person experienced in setting up and installing personal computers
should be able to install a server.
4. This person will need a good understanding of how to work with electrical
components and the basics of network administration.
5. Hazards exist, such as the risk of electric shock and accidental damage to
the sensitive electronic components in a server.
6. It is important to avoid damaging sensitive components such as memory
modules, CPUs, controllers, and disk drives.
7. Using a wrist-grounding device or other antistatic equipment will reduce
the possibility that a static electric discharge will damage the equipment.
8. Some vendors require that one of their employees be present to confirm
that the server is operational before they will activate the warranty.
9. Use the computers on-board diagnostic utilities to confirm that the
memory and disk drives are operational.
10. Install and configure the servers NOS, then connect the NIC cable to the
network and try to contact a remote host.
D. Confirming a Server Upgrade
1. When the server is turned on, the boot sequence diagnostics utility
confirms that the memory amount is correct and that the system can
recognize all the attached disk drives and devices.
2. The server OS is booted and displays correctly.
3. The control panel displays the correct information for internal and
external devices.
4. It is possible to ping a remote host by name and IP address.

Outline, Chapter 12 9
Networking Essentials Plus, Third Edition
4. Workstations
A. Deciding to Upgrade a Workstation
1. Easier to accomplish and less expensive than upgrading the server.
2. Can be a sound investment as user demands on the network increase.
3. In a server-based network, the client workstation processes information
that has been retrieved from the server.
4. Upgrading a workstations processor and adding to its RAM and disk
capacity can increase the workstations performance.
5. These upgrades are not usually difficult or expensive.
B. How to Upgrade a Workstation
1. Manufacturers include basic information about how to install the
components.
2. Device vendors usually have additional information about upgrading or
they offer onsite support.
3. Consider upgrading only the internal components.
4. If installing a complete replacement workstation, the administrator needs
to verify that the correct version of the client operating system is installed.
5. Old NIC can be used in the new workstation.
6. Steps used to upgrade a server also apply to a workstation upgrade:
a. Use caution during the staging process.
b. Avoid static electric discharge.
c. Configure the client version of the NOS.
d. Test for a successful network connection.
C. Confirming a Workstation Upgrade
1. When the workstation is turned on, the boot sequence diagnostic utility
displays the correct amount of RAM, and the workstation recognizes all
drives and devices.
2. Client workstations OS boots up correctly.
3. NOS diagnostic utilities confirm that the memory and disk drives are
operational.
4. Configure the workstation version of the NOS.
5. Control panel displays the correct information for internal and external
devices.
6. To conclude the workstation upgrade, try to ping a remote host and log on
to the server.

5. Network Interface Card (NIC)


A. Deciding to Upgrade a NIC
1. NICs are usually upgraded at the same time the server is replaced.
2. A slow NIC in the server can cause a bottleneck as data is leaving.
3. When the NIC is upgraded, data can move faster from the server to the
network media and ultimately to the workstation.
4. Workstation and server NICs need to be upgraded.
B. How to Upgrade a NIC

10 Outline, Chapter 12
Networking Essentials Plus, Third Edition
1. Confirm that the card to be installed is the correct version for the
workstation.
2. Read the manufacturers installation instructions.
3. Use antistatic procedures.
4. Handle the NIC carefully.
5. Line up the pins carefully and connect.
6. Check for a successful network connection.
C. Confirming a NIC Upgrade
1. Physical installation of the NIC should occur without difficulty.
2. Network properties control panel should display the correct information
about the NICs.
3. It should be possible to ping a remote host.

6. Network Media
A. Deciding to Upgrade Network Media
1. Requires considerable technical expertise and experience.
2. Seek advice from a network professional before undertaking such an
upgrade.
3. Environmental factors can be causes for upgrade.
4. Cost for both the media and installation can be high.
5. Factors can exist that will require different types of media on the same
network.
6. Research and identify the various types of media available, make a
preliminary decision, then consult network professionals before making a
final choice for the type and installation of the upgraded network media.
7. Benefits of upgraded network media are faster data transfer and reduction
of bottlenecks of data from device to device.
B. How to Upgrade Network Media
1. Copper cable can be installed by someone without special training.
2. Fiber-optic cable requires a trained installer to plan and connect
workstations, server, and routers.
3. Small wireless networks can be installed by following the manufacturers
instructions.
4. Advanced wireless networks or microwave networks require trained
installers.
C. How to Confirm a Network Media Upgrade
1. Media should be installed without sharp bends and away from sources of
electromagnetic interference.
2. Media should meet or exceed the fire code, especially in the plenum area.
3. Connections from the workstation to the routers to the server should be
complete.
4. Network performance monitor should have normal readings.
5. It should be possible to ping a remote host.

Outline, Chapter 12 11
Networking Essentials Plus, Third Edition
7. Upgrading the Routers, Brouters, Bridges, and Repeaters
A. Upgrade to route traffic more efficiently and expand a network.
B. Consult a network professional or router vendor during research.
C. Although these devices can be very expensive, efficient use of routers
can expand the network and provide increased network traffic
throughput.
D. Confirm the upgrade by having a trained installer perform any
diagnostics needed to confirm the complete connection from server to
router to workstation.
Chapter 12, Lesson 3
Moving a Network
1. Planning the Move
A. Planning is the key to moving a network successfully.
B. Plan has to be communicated to the users in advance so that they
know what to expect.
C. How long the network can afford to be down is an important factor in
planning and timing the move.
D. When the network cannot afford any downtime:
1. New network should be operational before the old one is disconnected.
2. Duplication of equipment at the old and new sites will be necessary.
3. New components need to be set up and tested before network goes live.
E. Identify tasks and establish an orderly and sequential timetable.
F. Identify the person responsible for carrying out each task.
G. Planning Phase Questions.
1. When will the new site be available?
2. When is the target move date?
3. When will the data be backed up before the move?
4. Who will back up the data?
5. Is the existing equipment attached to the floor or a wall?
6. At what time will all users be disconnected from the old network?
7. Who will be responsible for turning off the old system?
8. How much cable is needed?
9. Who will install the new cable? Are professional computer
uninstallers/installers needed?
10. Who will confirm that the cable runs meet local building codes?
11. Will lifting equipment be needed to move the server?
12. Are vehicles available to transport the equipment?
13. Is the power supply adequate in the new building?
14. Are the appropriate power outlets installed?
15. Will someone be on call to troubleshoot if the network fails to start?
16. Is there a source from which equipment replacements can be purchased if
anything is damaged.
17. Who will turn on the new network?

12 Outline, Chapter 12
Networking Essentials Plus, Third Edition
18. Who will test the workstations?
19. How will the network be tested after the move?

2. Making the Move


A. Overview
1. Requires coordination of people and equipment.
2. If the network can afford to be down for two or three days, it will not be
necessary to have an identical system running at the new location during
the move.
3. When moving a network for which down time is not possible, the new
facility must be operational before the old network is turned off.
B. Steps that need to be taken to move a network:
1. Notify users in advance when the system will not be available.
2. Encourage end users to make a backup of their hard drives.
3. Ask end users to label the peripheral device cables connected to the back
of their workstations.
4. Ask end users to disconnect their workstations from the power source and
to disconnect peripheral device cables from the backs of their
workstations.
5. Ask end users to leave the peripheral device cables attached to devices
and place the cables on top of the devices.
6. Ask movers to supply a cart to move equipment from the desktop to the
truck.
7. Secure equipment to be moved with shipping blankets and cushioning
between devices. Use original shipping containers when available.
8. Place the devices and backup media in an area away from magnetic fields
and motors.
9. Upon arrival at the new facility, use a cart to transport devices from the
truck to the desktop.
10. Install the peripheral device cables to the workstation.
11. Turn on the peripheral devices and network connection.
12. Turn on the workstations.
13. Install the server.
14. Inform the end users when the system will be available.

3. Verifying the Network After the Move


A. Overview
1. When devices are moved, the danger that internal and external
components will be damaged increases.
2. After the network has been installed, confirm that the network and all the
devices are communicating.
B. Where Downtime Is Acceptable
1. Servers
a. Server can be backed up, turned off, disconnected, packed, shipped,
unpacked, connected, turned on, restored and tested in a few hours.

Outline, Chapter 12 13
Networking Essentials Plus, Third Edition
b. Boot sequence diagnostics and the control panel settings should be
used to confirm that the server has the same configuration as before
the move.
c. Remote host should be pinged to confirm the network is operational.
d. Network monitor should be used to confirm that the throughput of data
is adequate.
2. Workstations
a. Should be connected to all peripherals and to the network.
b. Computer connected to a different subnet of the network should be
pinged.
c. Control panel settings should be confirmed as correct.
3. NICs
a. Can be checked during installation of the server and workstations.
b. Check the network interface settings within the NOS.
c. Ping a remote host.
d. Check network monitor for data throughput problems.
4. Network Media
a. The new network media will most likely be in place before the
hardware is relocated.
b. Test the media by installing two workstations and pinging them from
various locations within the new network.
c. Use network monitor before and after the relocation to confirm that the
network is operating correctly.
C. Where Downtime Is Unacceptable
1. Servers
a. Server on the new network must be staged, installed, configured, and
tested before the old network is turned off.
b. Old and new networks will run in tandem for a brief period.
c. When performance of the new servers and network is satisfactory, the
old server can be turned off and migrated to the new network as
needed.
2. Workstations
a. All workstation components in the new network must be set up and
tested before the old network is turned off.
b. Old network workstations should be migrated to the new network as
needed.
3. NICs
a. New network must be set up and tested before the old network can be
turned off.
b. NIC for the workstation and the server should be tested before the old
and new networks run in tandem.
4. Network Media
a. The network media should be installed and tested before the relocation
date.

14 Outline, Chapter 12
Networking Essentials Plus, Third Edition
b. Network monitor should be used before, during, and after the move to
confirm that the network is operating correctly.

Outline, Chapter 12 15
Networking Essentials Plus, Third Edition

S-ar putea să vă placă și