HP D6030A - NetServer - E50 User manual

HP NetServer DiagTools
Error Reference and User Guide
Printed in September 1998

ii
Notice
The information contained in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not
limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-
Packard shall not be liable for errors contained herein or for incidental or consequential damages in
connection with the furnishing, performance, or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not
furnished by Hewlett-Packard.
This document contains proprietary information that is protected by copyright. All rights are reserved. No
part of this document may be photocopied, reproduced, or translated to another language without the prior
written consent of Hewlett-Packard Company.
Pentium II® is a registered trademark of Intel Corporation.
Windows®is a registered trademark of Microsoft in the U.S. and other countries.
CompuServe™ is a U.S. trademark of CompuServe, Inc.
Hewlett-Packard Company
Network Server Division
P.O. Box 58059, Technical Marketing
Santa Clara, CA 95052-8059 USA
© Copyright 1998, Hewlett-Packard Company.
Audience Assumptions
This guide is for the person who installs, administers, and troubleshoots LAN servers. Hewlett-Packard
Company assumes you are qualified in the servicing of computer equipment and trained in recognizing
hazards in products with hazardous energy levels.

iii
Contents
1 DiagTools Overview......................................................................................1
Introduction to Hardware Diagnostic Tools......................................................1
DiagTools Requirements and Capabilities......................................................1
DiagTools Requirements............................................................................1
DiagTools Capabilities................................................................................2
DiagTools User Interface Modes: Graphical or Text-Based ........................3
Hardware Detection........................................................................................3
Overview of Hardware Detection................................................................3
What is Detected........................................................................................3
About Error Messages....................................................................................3
Advantages and Limitations of Hardware Diagnostics.....................................3
Latest Version of the Software and the Documentation ..............................4
2 Preparing to Run DiagTools.........................................................................5
Begin with Simple Troubleshooting.................................................................5
Starting Troubleshooting............................................................................5
Preparations for Running DiagTools...............................................................5
DiagTools Can Be Installed with the Utility Partition ...................................5
Preparing for Remote Operation ................................................................6
How to Make a DiagTools Diskette with a Windows System......................6
Shall I Use the Diskette or the Utility Partition?...............................................6
3 Running DiagTools in the Graphical Mode (from Diskette)........................9
Bring the NetServer Down..............................................................................9
Starting the Graphical Mode from Diskette.....................................................9
Starting Configuration Detection...............................................................10
Running the Basic Tests...............................................................................10
Interpreting Basic Test Results.....................................................................11
Running the Advanced System Tests...........................................................12
Advanced System Test Menus and Options.............................................12
Reviewing Results: Running the Viewers......................................................13
Reviewing Results: Saving and Printing the Support Ticket..........................13
To Create A Support Ticket......................................................................14
Troubleshooting When Devices are not Detected.........................................14
Processor and Memory Non Detected Troubleshooting............................14
SCSI Device Non Detected Troubleshooting............................................15
4 Running DiagTools in the Text Mode (from the Utility Partition).............17
Preparation in Advance................................................................................17
Before You Begin: A Note on Running DiagTools on a Distant Server..........17
Accessing the Utility Partition on a Local Machine....................................17
Select the Utility Partition.............................................................................18
Main Menu in Text Mode..............................................................................18
Running the Basic Tests...............................................................................18
Interpreting Basic Test Results.....................................................................19
Running the Advanced System Tests...........................................................19
Advanced System Test Menus and Options.............................................19

iv
Getting a Configuration Report.....................................................................21
Reviewing Results: Running the Viewers......................................................22
Reviewing Results: Saving and Printing the Support Ticket..........................22
To Create A Support Ticket......................................................................23
Troubleshooting When Devices are not Detected.........................................23
Processor and Memory Non Detected Troubleshooting............................23
SCSI Device Non Detected Troubleshooting............................................24
5 Error Message Reference............................................................................25
Error Messages and Their Sources...............................................................25
The System Tests....................................................................................25
Memory Test Menu..................................................................................43
FDD (Flexible Disk Drive or Floppy) Tests ...............................................49
KBD (Keyboard) Tests..............................................................................51
SCSI Device Tests...................................................................................52
Misc Tests................................................................................................57
Video Test................................................................................................59
IDE CD-ROM...........................................................................................59
Multiprocessor Test..................................................................................60
A Test Menus..................................................................................................69
Basic Test Menus.........................................................................................69
Advanced System Tests...............................................................................70
B Test Descriptions........................................................................................71
Test Descriptions..........................................................................................71
System Test Menu...................................................................................71
Memory Test Menu..................................................................................73
FDD (Flexible Disk Drive or Floppy) Tests ...............................................74
KBD (Keyboard) Tests..............................................................................75
SCSI Device Tests...................................................................................75
SCSI Disk Tests.......................................................................................75
SCSI Tape Unit Tests...............................................................................76
SCSI CDROM Tests.................................................................................76
Misc Tests................................................................................................76
Video Test................................................................................................77
IDE CD-ROM...........................................................................................77
C Batch Menu.................................................................................................79
Batch Menu..............................................................................................79
Index ...............................................................................................................81

1
1 DiagTools Overview
Introduction to Hardware Diagnostic Tools
The purpose of hardware diagnostic software is to provide tools for checking serious hardware problems. By
design, offline diagnostics execute simple tests of each hardware component in turn. Usually, such tests
create assurance that hardware is not the source of system problems. This allows the user to focus energy on
configuration problems, network problems, and software problems.
If hardware problems are confirmed, diagnostic tools can sometimes detect and diagnose the source of the
problem. In addition, diagnostic tools can capture information that allows support agents to quickly assess
the condition of system components.
To be most effective, offline diagnostics must be used in the context of a wider trouble-shooting procedure.
(See Chapter 2 for more information on troubleshooting.)
DiagTools Requirements and Capabilities
DiagTools Requirements
Running DiagTools requires a system which is capable of booting up from a flexible diskette (floppy drive).
Two blank, formatted flexible diskettes may be required. One diskette is needed to run DiagTools in
graphical mode, and another is recommended for use in saving the Support Ticket.
Systems Supported
DiagTools for HP NetServers is supplied on the HP NetServer Navigator CD-ROM version L:14:00 and
greater, and runs on the following models1:
•HP NetServer LC 3 and subsequent models2
•HP NetServer LH 3 and subsequent models2
•HP NetServer LPr and subsequent models2
•HP NetServer LXr 8000 and subsequent models2
Notes 1If a system is not supported, when you attempt to run DiagTools, a message is
displayed:
Incompatible-PC
2Consult the readme file named DTREADME (on the DiagTools diskette or use the
MISC menu in the Advanced screen), to determine which systems are supported by a
particular version of DiagTools.
For the latest information on systems and accessories that support DiagTools, see the DTREADME file
located on the diskette. (See “How to Make a DiagTools Diskette with a Windows System” in Chapter 2.

Chapter 1 DiagTools Overview
2
DiagTools Capabilities
DiagTools for HP NetServers is a set of off-line diagnostic tests, including tests for system and processor
components, memory and storage elements, ports, and input/output devices. The DiagTools files are located
on the HP NetServer Navigator. To prepare DiagTools for use, the user may either
•transfer it to diskette and restart the server from the floppy drive
•install the Utility Partition and run DiagTools from the hard disk (which also reboots the server)
DiagTools checks key NetServer components, and a menu of Advanced System Tests is available for
individual and batch testing. DiagTools has the capability to check the functionality of the components
listed in Table 1-1.
Table 1-1. Components Checked by DiagTools
• system board • processors (CPUs)
• memory modules • hard disk modules & associated
controllers
• flexible disks & controller • keyboard controller
• serial ports & controller • parallel ports & controller
• tape drives & associated
controllers • CD-ROM drives & controller
Since DiagTools is an off-line diagnostic test series, it does not use the main network operating system
(NOS) of the HP NetServer. The alternate DiagTools OS has far fewer features than the full-fledged NOS.
Thus, its capabilities are limited to a set of basic tests and a series of more advanced tests. (DiagTools does
not, for instance, allow user access to NOS error logs.) In addition, DiagTools does not use any tests which
might write over and thus destroy user data. Tests which require user inputs or decisions are left to the
advanced series.
You can use DiagTools to support trouble-shooting to carry out the tasks listed below:
•display a high-level list of hardware detected in the system under test
•save and print a detailed list of hardware components
•conduct a basic test of components listed in the system inventory
•display “PASSED” or “FAILED” overall results of basic tests
•record detailed test results of basic system tests to a file called the Support Ticket
•display a menu of Advanced System Tests
•select and run one or a series of Advanced System Tests
•add the record of results of Advanced System Tests to the record of basic tests
•view a list to locate the meaning of a specific error code
•view one or more steps to help confirm and isolate error conditions
•browse the Support Ticket, which contains the detailed inventories and test results
If you have TopTools remote management software installed and configured for use with DiagTools, you
can accomplish any of the above tasks remotely. In order to do so, install the text-based DiagTools on the
Utility Partition of the system to be tested, and use ERA and RMC to access the partition and redirect the
console.

Chapter 1 DiagTools Overview
3
DiagTools User Interface Modes: Graphical or Text-Based
DiagTools has two different types of interface modes. The graphical interface operates from a DiagTools
diskette made while HP NetServer Navigator is running. The text-based mode operates when the Utility
Partition is installed. To run DiagTools remotely, it must be installed in the Utility Partition of the
NetServer to be tested. For more details, see the section of chapter 2 entitled “Preparing for Remote
Operation” and the section of chapter N entitled “Running DiagTools Remotely.”
Hardware Detection
Overview of Hardware Detection
Hardware detection determines which tests are appropriate for your HP NetServer. For example, if your
server has an IDE or SCSI hard disk, the boot sector of the disk will be checked as part of the basic system
test.
In the Advanced System Tests, some functions will be disabled if they are not appropriate for your
NetServer. For example, if you do not have a SCSI controller (or if your SCSI controller is not responding),
the SCSI menu in the Advanced System Tests will be disabled.
What is Detected
A list of items detected is shown in Table 3-1.
About Error Messages
Each error message in DiagTools is designated by a hexadecimal number, a short note on the type of error,
and a list of one or more steps the user can take in response. When you run a test, it exercises many aspects
of the hardware, so the number of possible error messages exceeds 300. Most of these are encountered
rarely, if ever.
You can view error codes on line from the Misc Menu of the Advanced System Tests, or you can refer to
Chapter 5 of this guide, which lists the error messages in order.
Advantages and Limitations of Hardware Diagnostics
Off-line diagnostic software is useful in making sure that hardware has been eliminated as the cause for
possible system problems. Such diagnostic tools can easily be shipped with a server, and they are easy to
use.
However, limitations for off-line diagnostic software mean that it should be used only by experienced
personnel who can take a wider view of its limitations, which include:
•rebooting the server one or more times whenever off-line diagnostics are run
•an offline diagnostic runs on the system under test so it cannot control and observe all aspects of that
system
•no access to network operating system error logs, since the NOS is not operating at the same time as
the diagnostic tools
•ability to test only a single component at a time (Batch testing can overcome this to some degree.)
•use of only non-destructive tests limits the exercising of system components, especially storage
devices

Chapter 1 DiagTools Overview
4
•inability to indicate problems with wrongly configured systems or the network
•inability to boot to systems that cannot boot to DOS
Latest Version of the Software and the Documentation
You can get information about the latest version of the software as well as the most current documentation
at the following web address:
www.hp.com/go/netserver

5
2 Preparing to Run DiagTools
Begin with Simple Troubleshooting
Generally, you use DiagTools during installation to ensure that hardware components are fully functional.
You may also use DiagTools if you are having problems with a particular server. In this case, you might use
DiagTools to check whether all of the server’s detectable components are found by DiagTools.
CAUTION DiagTools can only be used off-line. This means you must reboot the HP NetServer you
will be running DiagTools on. If possible, alert users and gracefully shut down network
operations before rebooting.
Starting Troubleshooting
Before you reboot your server to use DiagTools, do the steps listed below:
1. Log onto the network operating system and check the NOS Event or Message Log. If there are error
messages, use the NOS documentation or support facilities to find out what the messages mean. Take
corrective action on network operating system errors before taking the other troubleshooting steps
below.
2. If you have HP TopTools or HP OpenView, check the event (alarm) logs and ensure you have taken
corrective action if required.
3. Consult the HP Documentation CD which came with your system. It contains HP Information
Assistant, including the system user manual (with a troubleshooting chapter) and a generic
troubleshooting checklist. Ensure you have followed the recommendations in these two sources.
4. Finally, if you have not located the trouble in one of these steps, you may wish to run DiagTools. To
do so, follow the steps in the detailed descriptions in the next two sections. These steps include:
◊Use HP Navigator to create a DiagTools flexible diskette, unless it is installed on the Utility
Partition
◊Run DiagTools from the flexible diskette, or from the Utility Partition (either way involves
rebooting the server)
◊Review results by recording a Support Ticket or by viewing the Misc Menu in the Advanced
System Test Menu.
Preparations for Running DiagTools
Depending upon the configuration choices you made when you installed your HP NetServer, there are two
options for running DiagTools.
DiagTools Can Be Installed with the Utility Partition
To install the Utility Partition, restart the NetServer with the HP NetServer Navigator CD-ROM in the CD
drive. Once the boot screens scroll by, the Welcome Screen identifies Navigator and a list of menu buttons
is presented. Choose Configuration Assistant and use Custom configuration, Other, and then specify you
want the Utility Partition to be installed.

Chapter 2 Preparing to Run DiagTools
6
Once the installation is complete, the Utility Partition (with DiagTools included) will be ready for use. See
chapter 4, “Running DiagTools in the Text Mode” for information on how to run DiagTools from the
Utility Partition.
Preparing for Remote Operation
If you want to operate DiagTools across the network on a distant machine, prepare for operation by setting
up the Utility Partition on the distant machine and installing pcANYWHERE on your system.
Accessing the Utility Partition on a Local Machine
In order to use DiagTools on a NetServer running in a remote location, you need
•A Utility Partition, installed during the setup of the NetServer, which has DiagTools as an option
(See the HP Remote Administrator Guide)
and one of the options outlined in Table 2-1.
Table 2-1. Top Tools RMC or Integrated RA Options
Option Console (Near) NetServer (Far) Program Location
Top Tools Remote
Management Card Modem Modem Web Browser
Windows NT or 95
with Dialup
Networking
installed and running
on the Console
Integrated Remote
Assistant
(Integrated RA)
Modem Modem connected to
the Management
Port on the System
Board
pcANYWHERE32 installed and running
on the Console
How to Make a DiagTools Diskette with a Windows System
If you want to operate DiagTools without rebooting to the Utility Partition, make a diskette and copy the
necessary files to it from the Diskette Library.
One blank, formatted flexible diskette is required. Create the DiagTools flexible diskette as follows:
1. Place the HP NetServer Navigator CD-ROM into the CD drive of an MS Windows client. Close the
drive and allow the CD to autostart. This may take a few seconds.
2. A diskette library is presented. Highlight DiagTools. Then choose “Make Diskette.”
3. When the diskette is completed, remove it from the drive. Choose Exit and then press ENTER to exit
HP Navigator.
NOTE You can also make a DiagTools boot diskette when booting from the HP NetServer
Navigator CD-ROM. Select the NetServer Utilities menu and choose DiagTools Diskette.
Shall I Use the Diskette or the UtilityPartition?
When you use DiagTools from a diskette, the interface is graphical. The text is easier to read and more
colorful. When you use DiagTools from the Utility Partition (including remotely), you are presented with a
text-based interface. Though DiagTools operates equally well with either interface, most users prefer the
convenience and usability advantages of running DiagTools from the diskette.
Remotely, DiagTools only runs from the Utility Partition on the NetServer under test.