Chap13

33
Chapter Chapter Thirteen Thirteen Maintaining and Maintaining and Upgrading a Upgrading a Network Network

description

 

Transcript of Chap13

Page 1: Chap13

Chapter ThirteenChapter ThirteenMaintaining and Maintaining and

Upgrading a NetworkUpgrading a Network

Page 2: Chap13

ObjectivesObjectives

Perform a baseline analysis to determine Perform a baseline analysis to determine the state of your networkthe state of your network

Plan and follow regular hardware and Plan and follow regular hardware and software maintenance routinessoftware maintenance routines

Describe the steps involved in upgrading Describe the steps involved in upgrading network operating system softwarenetwork operating system software

Page 3: Chap13

ObjectivesObjectives

Describe the steps involved in adding or Describe the steps involved in adding or upgrading the network hardwareupgrading the network hardware

Address the potential pitfalls of making Address the potential pitfalls of making changes to the networkchanges to the network

Research networking trends to plan future Research networking trends to plan future networking upgradesnetworking upgrades

Page 4: Chap13

Keeping TrackKeeping Track

BaseliningBaselining Measuring and recording a network’s current state of Measuring and recording a network’s current state of

operationoperation

Figure 13-1: Baseline of daily network traffic

Page 5: Chap13

Keeping TrackKeeping Track

Asset managementAsset management System of identifying and tracking the System of identifying and tracking the

hardware and software on your networkhardware and software on your network

Change managementChange management Use your change management system to Use your change management system to

record any changes resulting from network record any changes resulting from network maintenance or upgradesmaintenance or upgrades

Page 6: Chap13

Software ChangesSoftware Changes

General steps for software changesGeneral steps for software changes Determine whether the change is necessaryDetermine whether the change is necessary Research the purpose of the change and its Research the purpose of the change and its

potential effects on other programspotential effects on other programs Determine whether the change should apply to Determine whether the change should apply to

some or all user and whether it will be distributed some or all user and whether it will be distributed centrally or machine-by-machinecentrally or machine-by-machine

If you decide to implement the change, notify If you decide to implement the change, notify system administrators, help desk personnel, and system administrators, help desk personnel, and usersusers

Page 7: Chap13

Software ChangesSoftware Changes

General steps for software changes (cont.)General steps for software changes (cont.) Back up current system or software before Back up current system or software before

making any modificationsmaking any modifications Prevent users from accessing the system or part Prevent users from accessing the system or part

of the system being alteredof the system being altered Keep the upgrade instructions handy and follow Keep the upgrade instructions handy and follow

them during installation of the patch or revisionthem during installation of the patch or revision Make the changeMake the change

Page 8: Chap13

Software ChangesSoftware Changes

General steps for software changes (cont.)General steps for software changes (cont.) Test the system fully after the change, preferably Test the system fully after the change, preferably

exercising the software as a typical user wouldexercising the software as a typical user would If the change was successful, reenable access to the If the change was successful, reenable access to the

systemsystem If unsuccessful, revert to previous system version of If unsuccessful, revert to previous system version of

the softwarethe software Inform system administrators, help desk personnel, Inform system administrators, help desk personnel,

and users when the change is completeand users when the change is complete Record the change in the change management Record the change in the change management

systemsystem

Page 9: Chap13

Software ChangesSoftware Changes

PatchPatch Improvement or enhancement to a particular Improvement or enhancement to a particular

piece of a software programpiece of a software program Service packService pack

Term Microsoft uses for its significant patches for Term Microsoft uses for its significant patches for Windows 2000 ServerWindows 2000 Server

Page 10: Chap13

Software ChangesSoftware Changes

UpgradeUpgrade Major change to existing codeMajor change to existing code May or may not be offered free from a vendorMay or may not be offered free from a vendor May or may not be comprehensive enough to May or may not be comprehensive enough to

substitute for the original programsubstitute for the original program In general, upgrades are designed to add In general, upgrades are designed to add

functionality and fix functionality and fix bugsbugs

Page 11: Chap13

Software ChangesSoftware Changes

Client upgradesClient upgrades An upgrade to the client program replaces the An upgrade to the client program replaces the

existing client programexisting client program In general, upgrades are designed to add In general, upgrades are designed to add

functionality and fix bugs in the previous functionality and fix bugs in the previous version of the clientversion of the client

A client upgrade may be transparent to users A client upgrade may be transparent to users or may completely change the appearance of or may completely change the appearance of the network login interfacethe network login interface

Page 12: Chap13

Software ChangesSoftware Changes

Application upgradesApplication upgrades Represent modifications to all or part of a Represent modifications to all or part of a

program that are designed to enhance program that are designed to enhance functionality or fix problems related to functionality or fix problems related to softwaresoftware

Apply to software shared by clients on the Apply to software shared by clients on the networknetwork

Page 13: Chap13

Considerations for Network Considerations for Network Operating System UpgradesOperating System Upgrades

Effect on user IDs, groups, rights, and Effect on user IDs, groups, rights, and policiespoliciesEffect on file, printer, and directory access on Effect on file, printer, and directory access on the serverthe serverEffect on applications or client interactions on Effect on applications or client interactions on the serverthe serverEffect on configuration files, protocols, and Effect on configuration files, protocols, and services running on the serverservices running on the serverAffect on the server’s interaction with other Affect on the server’s interaction with other devices on the networkdevices on the network

Page 14: Chap13

Considerations for Network Considerations for Network Operating System UpgradesOperating System Upgrades

Accurately test the upgrade software in Accurately test the upgrade software in simulated environmentsimulated environmentTake advantage of the new operating system to Take advantage of the new operating system to make your system more efficientmake your system more efficientSupport arrangement with the operating Support arrangement with the operating system’s manufacturer if help is needed during system’s manufacturer if help is needed during the midst of the upgradethe midst of the upgradeAllot enough time to perform the upgradeAllot enough time to perform the upgradeEnsure that users, help desk personnel, and Ensure that users, help desk personnel, and system administrators understand how the system administrators understand how the upgrade will affect their daily operations and upgrade will affect their daily operations and support burdenssupport burdens

Page 15: Chap13

Steps for NOS UpgradeSteps for NOS Upgrade

ResearchResearch

ProposalProposal Questions to answer during evaluationQuestions to answer during evaluation Names of personnel to assist with evaluation Names of personnel to assist with evaluation

and final approvaland final approval Rough timeline and plan for implementing the Rough timeline and plan for implementing the

change if it is approvedchange if it is approved Rough project plan for implementing the Rough project plan for implementing the

change if it is approvedchange if it is approved

Page 16: Chap13

Steps for NOS UpgradeSteps for NOS Upgrade

Proposal (cont.)Proposal (cont.) Cost considerationsCost considerations Review of the short- and long-term benefits of Review of the short- and long-term benefits of

the upgradethe upgrade Review of the risks involved in the upgradeReview of the risks involved in the upgrade Recommendation for or against performing Recommendation for or against performing

the operating system upgradethe operating system upgrade Plan for purchasing the software and Plan for purchasing the software and

implementing the changeimplementing the change

Page 17: Chap13

Steps for NOS UpgradeSteps for NOS Upgrade

EvaluationEvaluation

TrainingTraining

Pre-implementationPre-implementation

ImplementationImplementation

Post-implementationPost-implementation

Page 18: Chap13

Reversing a Software UpgradeReversing a Software Upgrade

BacklevelingBackleveling Process of reverting to a previous version of software Process of reverting to a previous version of software

after attempting to upgrade itafter attempting to upgrade it

Table 13-1: Reversing a software upgrade

Page 19: Chap13

Hardware and Physical Plant Hardware and Physical Plant ChangesChanges

Guide for changing network hardware:Guide for changing network hardware: Determine whether the upgrade is necessaryDetermine whether the upgrade is necessary Research the upgrade’s potential effects on other Research the upgrade’s potential effects on other

devices, functions, and usersdevices, functions, and users If you decide to implement the change, notify If you decide to implement the change, notify

system administrators, help desk personnel, and system administrators, help desk personnel, and users and schedule it during off-hoursusers and schedule it during off-hours

If possible, back up the current hardware’s If possible, back up the current hardware’s configurationconfiguration

Page 20: Chap13

Hardware and Physical Plant Hardware and Physical Plant ChangesChanges

Guide for changing network hardware (cont.):Guide for changing network hardware (cont.): Prevent users from accessing the system or part Prevent users from accessing the system or part

of the system that you are changingof the system that you are changing Keep the installation instructions and hardware Keep the installation instructions and hardware

documentation handydocumentation handy Implement the changeImplement the change Test the hardware fully after the change, Test the hardware fully after the change,

preferably putting a higher load on the device preferably putting a higher load on the device than it would incur during normal use in your than it would incur during normal use in your organizationorganization

Page 21: Chap13

Hardware and Physical Plant Hardware and Physical Plant ChangesChanges

Guide for changing network hardware (cont.):Guide for changing network hardware (cont.): If the change was successful, reenable access to If the change was successful, reenable access to

the devicethe device If unsuccessful, isolate the device or reinsert the If unsuccessful, isolate the device or reinsert the

old deviceold device Inform system administrators, help desk Inform system administrators, help desk

personnel, and users when the change is personnel, and users when the change is completecomplete

Record your change in the change management Record your change in the change management systemsystem

Page 22: Chap13

Adding or Upgrading EquipmentAdding or Upgrading Equipment

Networked workstationNetworked workstation Perhaps the simplest device to addPerhaps the simplest device to add

Networked printerNetworked printer Slightly more complex than adding a Slightly more complex than adding a

networked printernetworked printer

HubHub Don’t have to worry about down time or Don’t have to worry about down time or

notifying users when adding a new hub, notifying users when adding a new hub, because it cannot affect anyone until it is in usebecause it cannot affect anyone until it is in use

Page 23: Chap13

Adding or Upgrading EquipmentAdding or Upgrading Equipment

ServerServer Server addition or upgrade can be trickyServer addition or upgrade can be tricky

Switches or routersSwitches or routers The most complex type of additions or The most complex type of additions or

changes to a network design for several changes to a network design for several reasonsreasons

Page 24: Chap13

Adding or Upgrading EquipmentAdding or Upgrading Equipment

The best way to safely gain experience with The best way to safely gain experience with adding, upgrading, or repairing devices is to adding, upgrading, or repairing devices is to experiment with devices that are not currently experiment with devices that are not currently used on a networkused on a network

Bear in mind that adding a new processor to Bear in mind that adding a new processor to a server, a new NIC to a router, or more a server, a new NIC to a router, or more memory to a printer may affect your service memory to a printer may affect your service or warranty agreement with the manufactureror warranty agreement with the manufacturer

Page 25: Chap13

Cabling Upgrades andCabling Upgrades andBackbone UpgradesBackbone Upgrades

Cabling upgradesCabling upgrades May require significant planning and time to May require significant planning and time to

implement, dependent on the size of your implement, dependent on the size of your networknetwork

Backbone upgradesBackbone upgrades The most comprehensive and complex The most comprehensive and complex

upgrade involving network hardwareupgrade involving network hardware

Page 26: Chap13

Reversing Hardware ChangesReversing Hardware Changes

As with software changes, you should provide a As with software changes, you should provide a way to reverse the hardware upgrade and way to reverse the hardware upgrade and reinstall the old hardware if necessaryreinstall the old hardware if necessary

Keep the old component safe, as you not only Keep the old component safe, as you not only might you need to put it back in the device, but might you need to put it back in the device, but you might also need to refer to it for informationyou might also need to refer to it for information

Page 27: Chap13

Managing Growth and ChangeManaging Growth and Change

Factors that might influence currently Factors that might influence currently developing trends in networking technology:developing trends in networking technology: Faster data processing and transmission will Faster data processing and transmission will

bring network access to more people in less timebring network access to more people in less time More comprehensive integration means that more More comprehensive integration means that more

products sold by different vendors will work well products sold by different vendors will work well togethertogether

Open standards will make networking careers Open standards will make networking careers less specialized and probably more interestingless specialized and probably more interesting

Page 28: Chap13

Managing Growth and ChangeManaging Growth and Change

Factors that might influence currently Factors that might influence currently developing trends in networking technology developing trends in networking technology (cont.):(cont.): Greater accessibility will bring technology to more Greater accessibility will bring technology to more

usersusers Smarter devices will contribute to each of the Smarter devices will contribute to each of the

trends mentioned, enabling the development of trends mentioned, enabling the development of faster, more open standards and providing faster, more open standards and providing greater accessibilitygreater accessibility

Page 29: Chap13

Researching Network TrendsResearching Network Trends

If not a significant change, the best way If not a significant change, the best way to evaluate networking technology is to to evaluate networking technology is to test it in your organizationtest it in your organization

With drastic or expensive upgrades that With drastic or expensive upgrades that you cannot afford to test first, rely on you cannot afford to test first, rely on someone else who has experience with someone else who has experience with the technologythe technology

Newsgroups on the Web can provide Newsgroups on the Web can provide valuable information, toovaluable information, too

Page 30: Chap13

Chapter SummaryChapter Summary

In every aspect of networking, keeping accurate and In every aspect of networking, keeping accurate and updated documentation will reduce troubleshooting time and updated documentation will reduce troubleshooting time and help you manage the network more effectivelyhelp you manage the network more effectively

Practice of measuring and recording your network’s current Practice of measuring and recording your network’s current state of operation is called baseliningstate of operation is called baselining

An asset management system includes an inventory of the An asset management system includes an inventory of the total number of components on the network as well as each total number of components on the network as well as each device’s configuration files, model number, serial number, device’s configuration files, model number, serial number, location on the network, and a technical contact for supportlocation on the network, and a technical contact for support

Document any changes to a network as the result of Document any changes to a network as the result of maintenance or upgrades in a change management systemmaintenance or upgrades in a change management system

Page 31: Chap13

Chapter SummaryChapter Summary

No matter what type of software upgrade performed, No matter what type of software upgrade performed, you should generally follow the same processyou should generally follow the same processA patch is an enhancement or improvement to a A patch is an enhancement or improvement to a part of a software program, often distributed at no part of a software program, often distributed at no charge by software vendors to fix a bug in their code charge by software vendors to fix a bug in their code or to add slightly more functionalityor to add slightly more functionalityA software upgrade represents a major change to A software upgrade represents a major change to the existing codethe existing codePerhaps the most critical type of software upgrade Perhaps the most critical type of software upgrade you’ll perform comprises an upgrade to your you’ll perform comprises an upgrade to your network operating systemnetwork operating system

Page 32: Chap13

Chapter SummaryChapter Summary

If the software upgrade you perform causes If the software upgrade you perform causes problems to your existing systems(s), you should problems to your existing systems(s), you should know how to reverse the processknow how to reverse the processHardware and physical plant changes may be Hardware and physical plant changes may be required when your network has problemsrequired when your network has problemsEach type of device added to or upgraded on the Each type of device added to or upgraded on the network will have its own preparation and network will have its own preparation and implementation requirementsimplementation requirementsCabling upgrades may require significant planning Cabling upgrades may require significant planning and time to implement, depending on the size of and time to implement, depending on the size of your networkyour network

Page 33: Chap13

Chapter SummaryChapter Summary

The most comprehensive and complex The most comprehensive and complex upgrade involving network hardware is a upgrade involving network hardware is a backbone upgradebackbone upgrade

You should know how to reverse the You should know how to reverse the hardware upgrade and replace it with the old hardware upgrade and replace it with the old hardwarehardware

The best way to evaluate networking The best way to evaluate networking technology is to test it in your organizationtechnology is to test it in your organization