Error Prevention Guide August 2003 (First Edition) Part Number 335894-001 HP CONFIDENTIAL Writer: Ted Weiman File Name: 335894-1.
© 2003 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
Contents Abstract.......................................................................................................... 5 Audience Assumptions ................................................................................ 5 Preparing for Changes.................................................................................. 5 Minimizing the Impact of Changes .............................................................. 6 Version Control .............................................................
Abstract This guide provides information to help you avoid future system problems. While many of the pointers provided are common-sense suggestions, these prevention tasks are too important to overlook. Audience Assumptions This guide is for the person who installs, administers, and troubleshoots servers. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
• Be sure that you allow enough time to make the changes. • Check for potential device conflicts before adding a device. • If a fixed cable tray or other cable routing system is available for the server, using this system can help prevent loose cabling and damage to cables that can result from improper disconnection. Minimizing the Impact of Changes Version Control Keep track of new versions of system software with the version control feature of Insight Manager 7.
Using a Methodology Following a set of procedures when using the server can help prevent problems, or make troubleshooting easier if problems do occur. • Use uniform naming conventions for the servers, such as names that denote server location. Uniform naming conventions help when trying to remember often overlooked details that can hold the key to resolving a crisis. • Use unique IDs or names for the devices. You can reduce the risk of components competing for the same resource if you have a list.
• Create a problem resolution notebook. When problems do occur, keep a log of the actions you took to resolve them. This could help you solve the same problem more quickly in the future. System configuration, Survey Utility, and Array Diagnostic Utility (ADU) printouts, as well as utility diskettes, can also be stored with the resolution notebook. This information can save a great deal of time in the future and ensure accuracy, especially when dealing with future part replacement.
• Be sure the server does not share a power line with high-current machines, such as laser printers, air conditioners, copiers, and coffee machines, or ungrounded power strips. • Periodically check AC grounded (earthed) outlets to see if they are in need of repair. • Take the system cover off, and then remove any dust buildup with a can of compressed air, tighten any loose connections, reseat boards, and inspect any cables for frays.
Power disruptions take many forms, including power surges and sags, high-voltage spikes, switching transients, brownouts, and complete power failure. When a power disruption occurs, check the server for signs of data damage, data loss, file corruption, and hardware damage. The difficulty of dealing with power fluctuations is that the damage is not always immediately noticeable; thus, problems may not be noticed until long after the power disruption has occurred.
Power Supply Considerations After you determine the appropriate amount of power for the server, install the power supplies needed for the level of redundancy you require.
• Do not expose a hard drive to products, such as monitors or speakers, that have magnetic fields. • Do not expose a drive to temperature extremes or liquids. Preventing Electrostatic Damage Many electronic components are sensitive to electrostatic discharge (ESD). Circuitry design and structure determine the degree of sensitivity.
Cleaning Drives DAT Drives Clean the tape heads of the drive regularly with a cleaning cartridge to maintain the integrity of backup data. For optimum performance and to prevent the loss of data, HP recommends that you incorporate a cleaning cycle into your backup routine. As a general guideline, you should clean the tape heads after every fifth backup cartridge.
