HP B6191-90015a User Manual

Diagnostic/IPR Media User's Guide

PA-RISC Computer Systems

B6191-90015a

June 1999

Legal Notices

The information contained in this document is subject to change without notice.

Hewlett-Pac kard makes no warranty of any kind with regard to this manual, including , but not limited to, the implied warranties of merchantability and ﬁtness for a particular purpose. Hewlett-P ac kard shall not be liable for errors contained herein or direct, indirect,

special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws.

Corporate Ofﬁces:

Hewlett-Packard Co. 3000 Hanover St. Palo Alto, CA 94304

Use, duplication or disclosure by the U.S. Government Department of Defense is subject to restrictions as set forth in paragraph (b)(3)(ii) of the Rights in Technical Data and Software clause in FAR 52.227-7013.

Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR

52.227-19(c)(1,2). Use of this manual and ﬂexible disc(s), compact disc(s), or tape cartridge(s) supplied for

this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited.

A copy of the speciﬁc warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Ofﬁce.

UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.

© Copyright 1979, 1980, 1983, 1985-1990 Regents of the University of California. This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California.

the University of Colorado, a body corporate. PostScript is a trademark of Adobe Systems, Inc. Intel is a registered trademark and Intel 80386 is a trademark of Intel Corporation.

a trademark of the Massachussetts Institute of Technology. MS-DOS and Microsoft are U.S. registered trademarks of Microsoft Corporation. OSF/Motif is a trademark of the Open Software Foundation, Inc. in the U.S. and other

countries. Certiﬁcation for conformance with OSF/Motif user environment pending.

Contents

1. Diagnostic/IPR Media Product Overview

Design of the Diagnostic/IPR Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Media Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2. Hardware Support Tools Overview

Support Tools Manager (STM) System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Initial System Loader (ISL) Standalone Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Hardware Support Tools Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Will the OS boot?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Will ISL boot from the main disk? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Will the Diagnostic/IPR Media boot? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Which online tools should be used? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3. Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

How to Run ODE's Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Test Module Manager (TMMGR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Running TMMGR. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Updating Processor Firmware Using the Diagnostic/IPR Media . . . . . . . . . . . . . . . . . . . . . . 30

4. Support Tools Manager (STM)

Running STM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Three Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

System Map and Device Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

System Map in xstm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

System Map in mstm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

System Map in cstm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Kinds of Support Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Menus and Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

xstm Menus and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

mstm Menus and Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

cstm Menus and Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Getting Result Information (Logs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Remote Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Distributed Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Improving Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Kinds of Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Exercisers sometimes enter a "Hung" state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

The user interface will not connect to a machine.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

A device in the STM map is "Unknown" or its icon is blank. . . . . . . . . . . . . . . . . . . . . . . . . 52

Slow response to user commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

SCSI Tape and Disk Tools report SCSI commands as failed in the Test Activity Logs. . . . 53

No tools are available for a particular device.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

The "Device — >Select Class" command did not work.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Contents

5. Using the Diagnostic/IPR Media to Install Diagnostics on Your System

Support Tools Manager (HP-UX 9000 Series 800/700) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

EMS Hardware Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

HP Predictive Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

How the Process Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

What HP Predictive Support Covers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

LIF-LOAD (HP-UX 9000 Series 800 and 700 Systems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Installing Online Support Tools from the Diagnostic/IPR Media (CD-ROM) . . . . . . . . . . . . .61

A. Disk Copy Utility — To make an image of a disk after install or upgrade (HP-UX 10.x

to 11.x)

Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Quick Start Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Executing COPYUTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

B. EMS Hardware Monitors

Enabling Hardware Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Printing History

Table 1

June 1999 ..... Edition 1

This printing date and part number indicate the current edition. The printing date changes when a new edition is printed. (Minor corrections and updates which are incorporated at reprint do not cause the date to change.) The part number changes when extensive technical changes are incorporated.

New editions of this manual will incorporate all material updated since the previous edition.

Internal Date: May 28, 1999 HP Printing Division:

Systems Supportability Lab Hewlett-Packard Co. 19091 Pruneridge Ave. Cupertino, CA 95014Printing History

About This Manual

The Diagnostic/IPR Media performs two functions:

• The Diagnostic/IPR Media is the swinstall format distribution media for the following hardware support products for 10.01, 10.10, 10.20, 10.30, and 11.x HP-UX systems; it is also the update format distribution media for the 9.04 and 9.07 HP-UX systems)

• Online diagnostics subsystem)

• Support Tools Manager (HP-UX 10.x and 11.x))

• EMS Hardware Monitors (HP-UX 10.20 and 11.x only)

• HP Predictive Support tools (Series 800 only)

• LIF-resident ofﬂine diagnostics

• IPR patches

• It is the platform for running ofﬂine diagnostics for all PA-RISC systems.

This manual is intended to provide an overview of how to use the Diagnostic Media for these two functions.

The following is a summary of the contents of the chapters in this manual:

Chapter 1 Diagnostic/IPR Media product overview Chapter 2 Hardware support tools overview

NOTE Chapter 2, “Hardware Support Tools Overview,” provides a simpliﬁed

approach to starting the hardware problem solving process, using the tools provided on the Diagnostic/IPR Media. This is not intended as a comprehensive troubleshooting guide, nor as a tutorial on the products themselves. It is merely intended as an aid in beginning the process, and in explaining brieﬂy how the various tools can be used.

Chapter 3 Using the Diagnostic/IPR Media to run ofﬂine diagnostics Chapter 4 Support Tools Manager (STM) Chapter 5 Using the Diagnostic/IPR Media to install the diagnostic products on your

system

Appendix A Disk Copy Utility - To make an image of a disk after install or upgrade

(HP-UX to 11.x)

Appendix B EMS Hardware Monitors

Problem Reporting. If you have any problems with the software or documentation, please contact your local Hewlett-Packard Sales Ofﬁce or Customer Service Center.

Reader Comments. We welcome your comments about our documentation. If you have editorial suggestions or recommended improvements for this document, please write to us. You can reach us through e-mail at: hardwaredocs@cup.hp.com or by sending your letter to: Information Engineering Group, M/S 5657, Hewlett-Packard Company, 8000 Foothills Blvd, Roseville, CA 95747-6588 USA.

Please include the following information in your message:

• Title of the manual you are referencing.

• Manual part number (from the title page).

• Edition number or publication date (from the title page).

• Your name.

• Your company's name. SERIOUS ERRORS, such as technical inaccuracies that may render a program or a

hardware device inoperative, should be reported to your HP Response Center or directly to a Support Engineer.

Current Information on the Web. This manual contains information that was current at the time of publication.

For the most current information on Support Tools, see our Web site, “Systems Hardware, Diagnostics, and Monitoring, ” athttp://www.docs.hp.com/hpux/systems/. This Web site also contains additional documents, such as tutorials, quick reference guides, and release information.

Diagnostic/IPR Media Product Overview

1 Diagnostic/IPR Media Product Overview

The Diagnostic/IPR Media allows you to diagnose and ﬁx problems when the operating system cannot be booted from the system disk. The Diagnostic/IPR Media runs on minimal hardware, with or without the system disk.

The Diagnostic/IPR Media performs two functions:

• Online diagnostics subsystem

• Support Tools Manager (HP-UX 10.x and 11.x))

• EMS Hardware Monitors (HP-UX 10.20 and 11.x only)

• HP Predictive Support tools (Series 800 only)

• LIF-resident ofﬂine diagnostics

• IPR patches

• It is the platform for running ofﬂine diagnostics for all PA-RISC systems.

The Diagnostic/IPR Media is primarily intended for HP-UX systems; however , it is used for running ofﬂine diagnostics on MPE/iX systems.

NOTE If you have an HP Hardware and Software Support Agreement, then

be sure to install HP Predictive Support along with the HP-UX Support Tools. For details, see the HP Predictive Support/UX User's

Guide (part number: H2571-90008).

Chapter 1 11

Diagnostic/IPR Media Product Overview

Design of the Diagnostic/IPR Media

The following subsections discuss the physical layout of the Diagnostic/IPR Media.

Media Layout

The Diagnostic/IPR Media contains Software Distributor (SD) bundles, which contain all of the online tools to be loaded onto your system, including the following:

• Online diagnostics subsystem)

• Support Tools Manager (HP-UX 10.x and 11.x))

• EMS Hardware Monitors (HP-UX 10.20 and 11.x only)

• HP Predictive Support tools (Series 800 only)

• LIF-resident ofﬂine diagnostics

• IPR patches In general terms, the Diagnostic/IPR Media is organized as follows (details of organization

for your particular media type may vary):

12 Chapter 1

Hardware Support Tools Overview

2 Hardware Support Tools Overview

The purpose of this chapter is to give a brief high-level overview of the recommended use of HP hardware support tools. This is not intended as a comprehensive troubleshooting guide, nor as a tutorial on the products themselves. It is merely intended as an aid in beginning the process, and in explaining brieﬂy how the various tools can be used.

There are several support tools platforms provided by HP, each targeted at a different troubleshooting situation or type of user. A brief description of these products follows. In addition, each system provides a help facility to assist users in getting started, determining what tools are available and how to run them, etc.

For the HP-UX 10.01, 10.10, 10.20, 10.30, and 11.x releases, the Support Tools Manager (STM) diagnostic systems is available. The STM diagnostic system is the diagnostic system used for information, veriﬁcation, and diagnosis. The STM system provides a map of the system, and lets you know what tools are available for each component, at the time it is accessed.

NOTE Included on the Diagnostic/IPR Media are the EMS Hardware Monitors -- an

important new tool for maintaining system availability. The EMS hardware monitors allow you to monitor the operation of a wide variety of hardware products and be alerted immediately if any failure or other unusual event occurs.

For more information, see Appendix B, “EMS Hardware Monitors.” in this manual.

Chapter 2 13

Hardware Support Tools Overview

Support Tools Manager (STM) System

The Support Tools Manager (STM) is an online support tools platform that is currently available on HP9000 series 700 and 800 machines. STM provides automatic conﬁguration mapping, and a set of veriﬁers, exercisers, information modules, expert tools, utilities, and ﬁrmware update tools for various devices on HP-UX systems. STM provides three user interfaces: a graphical interface for X-based terminals (XSTM), a menu interface for HP ASCII terminals (MSTM), and a command line interface for all ASCII terminals (CSTM). The graphical and menu interfaces are designed to be intuitive and usable by novices. The command line interface is provided mainly as a convenient method of driving STM via scripts. STM is invoked via the "xstm", "mstm", or "cstm" commands, depending on which interface is desired.

The STM veriﬁers are designed to quickly determine whether or not a speciﬁc device is operational by performing tasks similar in nature to the way applications use the device. No license is required to run the veriﬁers.

The STM exercisers are designed to stress devices in order to facilitate the reproduction of intermittent problems. The exercisers on HP-UX 9.X systems require a license to run.

The STM information modules create a log of information speciﬁc to one device, including:

• The product identiﬁer

• A description of the device

• The hardware path to the device

• The vendor

• On-board log information (if applicable)

• Miscellaneous information associated with the device Typically, the ﬁrmware revision code, if ﬁrmware is present in the device, will also be

displayed. The STM expert tools are device speciﬁc troubleshooting utilities for use by sophisticated

users. Their functionality varies from tool to tool, but they are intended to be interactive, and rely on you to provide information necessary to perform a particular task. These tools require you to have the appropriate license if you wish to run them.

The STM utilities are support tools which are not device speciﬁc. Current tools include log viewing and disk backup tools.

The STM ﬁrmware update tool initiates the ﬁrmware update process for a selected device. Most require that you have the appropriate license in order to run them.

14 Chapter 2

Hardware Support Tools Overview

Initial System Loader (ISL) Standalone Environment

The ISL standalone environment consists of the Initial System Loader, ISL-based tools which run directly from ISL, and the Ofﬂine Diagnostic Environment (ODE). On most PA-RISC machines, ISL is the ﬁrst program run after execution of the ﬁrmware. ISL implements a command line interface which allows the user to obtain information on the bootup characteristics of the system; to modify these characteristics; and to load and execute programs such as the operating system, ISL-based tools, and the Ofﬂine Diagnostics Environment.

ISL-based tools consist of a set of diagnostics that diagnose the Central Processing Unit (CPU), memory, and portions of the I/O system on older series 700, 800, and 900 machines; and the Ofﬂine Diagnostics Environment (ODE).

The Ofﬂine Diagnostics Environment is an ofﬂine support tools platform that is run from ISL and is available on series 700, 800, and 900 machines. ODE provides a common user-friendly interface for diagnostics and utilities developed to run in this environment. Diagnostics and utilities provided under ODE include:

• MAPPER - a utility for mapping out the physical layout of the SPU and its peripherals

• IOTEST - a utility for testing I/O cards using IODC

• PERFVER - a utility for testing peripherals attached to the boot path

• A set of diagnostics/utilities for testing disks.

• A set of diagnostics for testing CPU, memory, and selected I/O modules.

A license is required to run most of the ODE diagnostics and utilities. The main purpose of the ofﬂine tools is to enable the user to troubleshoot a system which

cannot be tested via the online tools, generally because a hardware problem exists which prevents the system from booting. The ofﬂine environment is also useful for some types of testing in which it is not desirable to have to boot the system ﬁrst, as is often the case in manufacturing applications.

Chapter 2 15

Hardware Support Tools Overview

Hardware Support Tools Usage

Each one of the products described above plays a role in the overall system troubleshooting strategy. Figure 2-1 contains a simple ﬂow diagram that outlines the intended use of the hardware support tools. Please note that this diagram is not intended to cover every aspect and corner case of system troubleshooting, but rather to provide an overall picture of what roles the various products play in troubleshooting systems.

As can be seen from the ﬂow diagram, the basic assumption is that if the system can boot to the operating system prompt, it is generally desirable to do so. In a majority of cases, the system is probably already booted and it is not desirable to take it down to run diagnostics. If there are problems with the hardware, the online support tools should be used to attempt to troubleshoot them. If the system will not boot, the ofﬂine tools from the Diagnostic/IPR Media should be used to troubleshoot the problem with the intent of getting the system to boot again. Once booted, the online tools can be used if any further testing is desired.

Of course, before altering the state of a system that is exhibiting problems, it is crucial to record any error messages, symptoms, etc., before proceeding. This information may be very valuable later on in determining what action to take to isolate the problem cause.

The following key decisions drive the troubleshooting strategy as outlined in the ﬂow diagram:

Will the OS boot?

This step determines whether or not the online versus ofﬂine support tools can be used. If the OS cannot boot, the ofﬂine tools are the only option. If the OS can boot, the recommendation is to use the online tools. Of course, the user still has the option of taking down the system and using the ofﬂine tools if it is so desired.

Will ISL boot from the main disk?

If the machine will boot to ISL from the main disk, the user would typically run the ofﬂine tools to troubleshoot the problem that is preventing the system from booting to the OS. The hardware problems that would be common here would be problems with the boot disk or other disks on the system that are used during boot; problems with the boot path that only manifest themselves under a load; conﬁguration problems, etc. Great care must be taken when running the ODE disk tools, since they can alter data on the disk. Backups of all OS and user ﬁles should be available, in case they need to be restored after the disk is repaired.

After ODE has been run and any problems that were encountered are ﬁxed, the user should again try to boot to the OS. If boot is successful, the online tools can be used for any further testing that is desired. If the OS will still not boot, the user should continue the troubleshooting process by turning to the Diagnostic/IPR Media.

16 Chapter 2

Figure 2-1 Hardware Support Tools Usage Flow Diagram

Hardware Support Tools Overview

Hardware Support Tools Usage

Will the Diagnostic/IPR Media boot?

If the machine will not boot to ISL from the main disk, or even if it will boot ISL, but still won't boot the OS, the user has little choice but to either start sw apping suspect hardware , using the error codes displayed on the front panel LEDs and console error messages for guidance, or attempt to boot from the Diagnostic/IPR Media. This decision is likely to be

Chapter 2 17

Hardware Support Tools Overview

Hardware Support Tools Usage

inﬂuenced by the type of machine that is having the problem and the error symptoms. If the user is troubleshooting a high-end server with many Field Replaceable Units (FRUs), it is usually beneﬁcial to use the Diagnostic/IPR Media approach to try and isolate the most likely failing FRU. If, on the other hand, the machine is a workstation with CPU, memory, and I/O all in one FRU, it may be desirable at this point to just replace the board and see if that takes care of the problem.

If the user elects to boot from the Diagnostic/IPR Media, and does so successfully, the problem is likely to be with the main disk or the I/O path to it, although it could still be a memory or SPU problem that is not manifested in the Diagnostic/IPR Media environment. In this case, the tools on the Diagnostic/IPR Media should be used to test the SPU, boot path components, the main disk and, if necessary, perform data recovery operations on the main disk.

If the machine will not even boot to ISL from the Diagnostic/IPR Media, the front panel LEDs and console error messages should contain error information that may help to isolate the most probable cause. The typical approach at this point is to go to a minimum conﬁguration (e.g., just the boot device and the console) and start swapping hardware to try to get to the point where the system can at least boot ISL.

Which online tools should be used?

If the system can be booted to the OS, the user has several online tools available to troubleshoot problems. The following are the strategic uses for each set of tools:

1. STM veriﬁers are useful primarily for ﬁnding reproducible problems that are causing a particular device to fail. They will run a quick veriﬁcation on selected devices and indicate whether they are basically functioning properly or not. This type of testing is probably most useful when new hardware is added or conﬁguration changes have been made and need to be veriﬁed.

2. STM exercisers are designed to help the user reproduce intermittent problems by stressing various system components and devices. In general, if the user has no good evidence that seems to indicate where the problem is, the exercisers should be used to try and isolate the problem to a speciﬁc device or area of the system.

3. STM diagnostics provide fault isolation capabilities for some devices. Typically, diagnostics are only available for hardware which comprises numerous FRUs.

4. STM information tools provide comprehensive information about speciﬁc devices. They typically also provide basic veriﬁcation that the device is responding.

5. STM expert tools are used for interactive testing of a particular device, in order to isolate a particular problem.

NOTE Included on the Diagnostic/IPR Media are the EMS Hardware Monitors -- an

18 Chapter 2

Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

3 Using the Diagnostic/IPR Media to Run

Ofﬂine Diagnostics

The Ofﬂine Diagnostics Environment (ODE) consists of a Test Controller (TC), a System Library (SysLib), and any number of Test Modules (TMs), all resident on the Diagnostic/IPR Media in the LIF. It provides you with a consistent interface for executing the ISL-based support tools from the Diagnostic/IPR Media, in the event that your system is ofﬂine.

The TC provides the user with two basic interfaces: a pure command-line interface for expert users, and a menu-oriented interface for less experienced users. In the command-line interface, users can select and run speciﬁc tests and/or utilities. In the menu-oriented interface, users select speciﬁc hardware modules to test, and do not have to know which diagnostic is associated with a particular module.

NOTE ODE utilities like MAPPER and FUPDATE (formerly UPDATE) can only be run

from the command-line interface.

Figure 3-1 provides a graphic representation of the relationship that exists between the ODE Test Controller (TC) and the underlying Test Modules (TMs):

Figure 3-1 Relationship Between ODE Test Controller and Test Modules

NOTE To see ISL-based programs, type ls at the ISL prompt. To see ODE-based

programs, start ODE from the ISL prompt, and then type ls at the ODE prompt.

Chapter 3 19

Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

NOTE Changes to Ofﬂine Diagnostics as of June 1999 (IPR 9906):

• The UPDATE utility for ODE has been replaced by FUPDATE. FUPDATE is backward compatible with existing computer systems

• For 64-bit systems like N-Class, there will be a different version of the ofﬂine diagnostic programs. The 64-bit version will have a “2” appended to its name. For example, the 64-bit version of MAPPER is MAPPER2.

• The ODE module TMMGR (TM Manager) will only be updated to support new 32-bit systems (such as the J5000, J7000, C3000, and B1000). TMMGR will NOT be updated to support new 64-bit systems (such as the L-Class and N-Class).

20 Chapter 3

Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

How to Run ODE's Command Line Interface

To start ODE's command line interface, do the following:

1. If you are at the PDC prompt (e.g., BOOTADMIN>), type search for a list of bootable devices:

BOOTADMIN>search

2. Select the tape or CD device, depending upon your Diagnostic/IPR Media, and boot from that device:

BOOTADMIN>boot SCSI.3.3

3. At the ISL> prompt, type the following:

ISL>ODE

The following prompt will then be displayed:

ODE>

4. Type the following, for a list of available commands with a capsule description of each:

ODE>help

The following information will be displayed:

MAIN HELP SCREEN Basic Commands HELP Prints detailed information to the screen, when "help <command>"

or "help <var>" is typed LS List modules available on boot medium <Module_Name> Load and initialize a module by typing its name

RUN Run a module (after setting desired environment variables) Control-Y|Control-C Abort an ODE command; pause a module run RESUME Restart a paused module DISPLOG After running a module, display contents of a log EXIT Return to next higher level prompt

Environmental Variables

SHOWSTATE Display the value of the following environment variables:

LOOP Run a test this many times ERRPRINT [ON|OFF] Print low-level error messages to console (primarily for manufacturing use) ERRNUM [ON|OFF] Print one-line, numbered errors to the console ERRPAUSE [ON|OFF] Pause module upon error detection ERRONLY [ON|OFF] Print ONLY error messages; disable non-error

and isolation message printing

INFOPRINT [ON|OFF] Print informational messages to the console ISOPRINT [ON|OFF] Print fault isolation messages to the console

ISOPAUSE [ON|OFF] Pause module when isolation message is generated LOGSIZE Set the size of a message log DEFAULT Reset environment variables to default state

(For more help, type "help module_name")

5. For more information on any of these commands or options, type help <command> or help <var>, as appropriate.

6. To list the ODE modules that will run on the current SPU, type ls at the ODE prompt.

Chapter 3 21

Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

How to Run ODE's Command Line Interface

7. Select the test module on the LIF that you wish to run, and decide whether you wish to run it interactively, or non-interactively.

8. If you wish to run interactively, type the following at the ODE prompt:

ODE><module_name>

This command loads the module from LIF into memory, and initializes it, displaying the module_name prompt:

MODULE_NAME>

To run interactively, type help for a list of commands which are valid for use with selected module:

MODULE_NAME>help

9. To run non-interactively, type the following at the ODE prompt:

ODE>run module_name

22 Chapter 3

Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

Test Module Manager (TMMGR) .

TMMGR (pronounced TM Manager) is a special ODE module that implements an ease-of-use user interface for ODE. TMMGR is a hybrid menu/command interface that enables the user to test speciﬁc hardware modules without having to know which diagnostic to load and launch — instead, the user simply selects from a menu the speciﬁc hardware module to test, and the appropriate diagnostic is executed. TMMGR provides the user with a consistent set of commands, as well as context-sensitive help. Note, TMMGR can only be run from the Support CD-ROM.

NOTE As of the June 1999 release (IPR 9906), the ODE module TMMGR (TM

Manager) will only be updated to support new 32-bit systems (such as the J5000, J7000, C3000, and B1000). TMMGR will NOT be updated to support new 64-bit systems (such as the L-Class and N-Class).

Running TMMGR

To launch TMMGR, enter the following:

ODE>MENU

After TMMGR loads and conﬁgures the system (this may take several minutes), it allows the user to interact with ODE through several different screens. Following is a brief summary of each screen:

System Screen The system screen is the ﬁrst screen displayed to the user. It provides a

map of all hardware modules in the system and allows the user to select and test sets of modules.

Test Screen A test screen displays a list of tests for a particular module. It allows the

user to select and run a set of tests for a speciﬁc module.

Logging Screen The logging screen displays of log of all test activity. The user can use

this screen to get detailed error or isolation information from a particular TM.

Environment Screen The environment screen displays a list of environment variables

accessible to the user. From this screen the user can adjust certain aspects of TMMGR.

For all screens, the set of available user commands is displayed across the top of the display. These are the only commands that can be entered at the command prompt. To get a summary of each available command, use the HELP command with no parameter. To display detailed information about a speciﬁc command, use the HELP command with the command's name as the parameter. Note, some screens may contain more than one page of information. To displa y the previous or subsequent page , use thePREV or NEXT commands or their respective shortcuts, Ctrl-P or Ctrl-N. To quickly go to the ﬁrst or last page of a

Chapter 3 23

Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

Test Module Manager (TMMGR) .

screen, use the FIRST or LAST commands. User commands at the command prompt may be chained together using a semicolon as a separator. For example, to select items 1 and 5 and then run them, the following could be entered at the command prompt:

Command-> select 1 5;run <cr>

System Screen

Below is an example of the system screen:

Commands: EXIT, NEXT, LAST, LOG, ENV, RUN, SELECT, INFO, REFRESH, HELP

** HP 9000/712 **

Selection Module/Device Path Status

1 Processor [1 Found] N/A 2 * Memory [1 Controller Found] READY 3 Builtin Graphics 1 N/A 4 * Core Bus Adapter 2 READY 5 * Core SCSI 2/0/1 READY 6 * Core LAN 2/0/2 READY 7 * Core RS-232 2/0/4 READY 8 * Core Centronics 2/0/6 READY

9 * Audio 2/0/8 READY 10 * Core Floppy 2/0/10 READY 11 * Core PS/2 2/0/11 READY 12 * Core PS/2 2/0/12 READY 13 * Core Bus Adapter 6 READY

%< Page 1 of 2 > %< Test Loops Completed: 0 > Command->

The system screen shows a map of the computer system displaying a short description of each HP- architected module, its architected path, and its status. The status ﬁeld gives information about the test state of the hardware module. The status ﬁeld may have the following values:

N/A The TM for this module is not available. Either the TM does not exist on

the LIF volume, or the TM is unable to be executed.

READY No tests for this module have been launched. The TM for this module is

ready for execution.

PASSED All tests run on this module passed. FAILED One or more tests run on this module failed. ABORTED The user aborted test execution, or all tests run were aborted by the

system SKIPPED Tests for this module were launched, but all were skipped. An asterisk next to a selection number indicates that this module is selected for testing.

The set of all selected modules will be tested when the user executes the RUN command. Use the SELECT command to alter the set of selected modules. To launch the tests for all selected modules, enter RUN at the command prompt. This will run all default or

24 Chapter 3

Using the Diagnostic/IPR Media to Run Ofﬂine Diagnostics

Test Module Manager (TMMGR) .

user-selected tests for all selected hardware modules. Note, not all available tests for a module may be considered default. At any time the user may hit Ctrl-C to abort test execution. To do detailed testing on just one particular module , one can enter the module's selection number at the command prompt. This will cause the module's test screen to be displayed.

Test Screen

Below is an example test screen:

Commands: EXIT, LOG, ENV, RUN, SELECT, INFO, REFRESH, HELP

** Memory Controller@9**

Test Description Status

1 * Single Bit Error Test READY 2 * Walking Ones Test READY 3 * Refresh Test READY 4 * Read Hammer Write Test READY 5 * Write Hammer Read Test READY 6 * Full Address Test READY 7 * Marching Ones Test READY 8 * Pseudorandom Architected Test READY 9 * Binary Tree Test READY

%< Page 1 of 1 > %< Test Loops Completed: 0 > Command->

The test screen displays all the tests for a selected module and indicates which ones are selected for testing. By default, not all tests may be tagged. For example, tests that require special loopback connectors may not be selected by default. Therefore, if one wants to ensure that a speciﬁc set of tests is run for a particular module, one should enter the test screen for that module and select the appropriate tests. The test screen also displays the status of each test. The status ﬁeld may have the following values:

READY This test has not been run. It is ready for execution. PASSED The test passed. FAILED The test failed. ABORTED The user aborted test execution, or the test was aborted by the system SKIPPED The test was skipped.

The user can execute the RUN command to run the set of selected tests. At any time the user may hit Ctrl-C to abort test execution. Use the EXIT command to return to the system screen. The current set of selected tests will be preserved. Thus, on a subsequent RUN from the system screen, only the user-selected tests will be executed.

Chapter 3 25

+ 56 hidden pages