Implementing Preventative maintenance
Design your network Maintain your network Prepare your network for failure
Design your network
Design your network
There are three steps to designing a network to minimise the chance of failure
Do it right
Allocating sufficient time to correct installation and set-up of network components is the most effective element of preventative maintenance. No matter if equipment is supposed to work, could work, or even has worked in the past, it cannot be considered correctly installed until it has been adequately tested.

So what do I do?
  • Before making any changes to your network, plan the changes on paper.
  • Install a firewall.
  • Install antivirus software
  • Check that the network equipment is installed in such a way as to minimise the chances of physical damage.



Duplicate it
Once any network element has been installed and tested, then duplicate it wherever possible. There are three areas of duplication to keep in mind:

Installed equipment
For each type of device on your network consider buying an exactly matching spare item. The main advantage is to provide a means to quickly replace a faulty or suspect device. This may not always be possible for more expensive items and is probably more appropriate where you have multiple items such as workstations installed. When determining what spare equipment to purchase, consider the following questions:
  • How critical is the device? Can your network manage without it? And for how long?
  • How many devices of this type are there? Is it possible to reconfigure (borrow) existing equipment to temporarily cover the loss?
  • Can you have a reciprocal arrangement with other local schools?

Redundancy
  • Wherever possible, copy data. Consider keeping data only on the server and install a RAID array to ensure that data is not lost.
  • Connections should be resilient to failure. Consider how data might travel around the network if cables are damaged or a switch fails. Are there multiple paths to each device? Are there fallbacks for the Internet connection?

Implementation
Where possible, configure items the same way. Create a software image of a workstation that you know is working well and use it to build new (and repair faulty) workstations
Doing something the same way every time has several benefits:
  • You achieve quicker and more thorough testing of the configuration
  • If you do something the same way each time, the configuration gets fully tested until all the issues can be resolved and the set up is as smooth as it can be. The more testing you perform, the sooner any problems should show up and the easier it is to make things right.
  • Fixes and upgrades are easier.
  • When there is a requirement to fix or upgrade a component, it is far easier to do it for one configuration than it is for multiple variants.
By doing it as right as possible the first time, you can make components work better for longer periods of time than if you implement ‘quick and dirty’ shortcuts. Duplicating implementations allows configurations to be tested more quickly and thoroughly than doing custom configurations, and it makes fixes and upgrades much easier to implement.

So what do I do?
  • Ensure that all critical network components have duplication or fail-safe built in
  • Set up a RAID system (or Raid)
  • Implement a backup and restore process for all data on your network
  • Develop an image for computers on your network and use that image to install new computers
Document it
Documenting the configuration of your network and the set up of its components gives you a strong base from which maintain, upgrade and fix it.

Unless there is access to a great deal of information about each component of a network, it is almost impossible to maintain it.
  • If you don't know which directory an application is in, how can you upgrade it?
  • If you don't know what the address settings are for the network interface card (NIC) how can you configure the new network driver?
  • If you don't know which make and model of NIC the computer has, how can you know what driver to use, let alone how to configure it?
  • If you don't know where the network outlets are and what their numbers are, how can you move or add equipment?

This information has to be known in order for there to be any maintenance of the system. It can either be done on an ongoing, systematic basis, or else be done in a panic at the last minute. One way or the other, you have to write down the information before you can make any plans, purchase any equipment, or implement any fixes or changes. Having it in your head is not enough.

Documenting a system is not a one-time affair. The network keeps changing and it is important to keep track of its current status.  Use FITS Change Management to ensure that all ICT infrastructure changes you make minimise the possibility of introducing additional incidents and problems. Change Management will also help you keep your ICT equipment records up to date in your configuration-management database.

If you do it right, duplicate it and document it, there is every reason to expect a reasonably well running and maintainable network. Even if you don't do it right or duplicate it, you have a good chance of ultimate success as long as you document what you are doing. The more documenting you do, the more reliable and maintainable your network becomes. The less documenting you do, the less reliable and maintainable your network becomes.

So what do I do?
  • Collect together in one safe place all manufacturers’ manuals and instructions that came with the equipment. Cross-reference each document to the equipment to which it relates.
  • Create physical topology and logical topology maps of the network set up.
  • Manage any ICT infrastructure changes to the network components, layout or set up (see Change Management).
Maintain your network
Maintain your network
Anetwork is not just computers; network maintenance is therefore not just concerned with blowing dust out of PCs. Each component of the network (cabling, server, workstation, peripheral and so on) has its own special usage and maintenance concerns that must be dealt with in order to provide maximum network reliability.
Items that require regular attention include:
  • maintaining PC workstations
  • maintaining Apple workstations (AP3138)
  • maintaining servers (AP3139)
  • maintaining printers and scanners
  • maintaining switches, hubs and routers (AP3141)
  • maintaining cabling.
So what do I do?
  • Set up a maintenance schedule for the network components and identify responsibility for carrying out the listed tasks. (AP3143)
Setting up a maintenance schedule
see toolkit for
Determining when to carry out maintenance
Automating preventative maintenance
Preventative maintenance schedule
Prepare your network for failure
While proper preventative maintenance of any sort provides the opportunity to detect and correct problems before they become incidents, it cannot prevent all failures.
However, by following the advice in this guide you will be able to establish an effective preventative maintenance programme that will minimise the effects of problems when they do occur. It will also put you in a position to rectify incidents with a minimum of fuss, outlay and disruption to the users of your network.
So what do I do?
There are measures you can take to ensure that, when components fail, you can repair the network in the fastest possible time. These include: