| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Maintenance Schedule This is best broken down into an ongoing series of chores. Some chores are done on a daily basis. Others can be on a less frequent schedule, such as weekly, monthly or even annually. As part of any best practices scheme a checklist is created, made a part of the SOP manual, and used to record entries, then filed. Almost every aspect of the network needs to be checked on an on-going basis. The only exception that is clear is playing around with working devices that are 100% solid state, with no fans. A router may be an example of this. If the device does not need a fan, then there is no fan to remove dust from. If it is working, leave it alone. The same could be said of opening monitors. The high voltage section of a monitor could cause serious bodily harm. Stay out for your own health and continued employment. A physical walk-through should include: Here you are looking for anything from uncomfortable temperatures to water on the walls or floor. Equipment is designed to operate in the same environmental conditions as human beings. A leaky pipe could rupture, dowsing the servers or printers. A visual inspection can tell you of impending trouble. Are patch cables carefully routed out of the way of traffic? Or is one cable drooping and having a chair run over it? If you walk by, and the workers just smile at you as you look around, this is a clue that all is well. Did you see a station not being used? Ask if there is some issue. You may find something as simple as nobody is using it because it locks up on heavy usage. Could it be that this unit has a defective CPU fan? Maybe. This is a clue to check it out.
Home - Table Of Contents - Contact Us CertiGuide for Network+ (http://www.CertiGuide.com/netplus/) on CertiGuide.com Version 1.0 - Version Date: November 7, 2004 Adapted with permission from a work created by Tcat Houser and Helen O’Boyle. CertiGuide.com Version © Copyright 2004 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||