User`s guide

System Troubleshooting and Diagnostics

This chapter provides troubleshooting information for the two primary

diagnostic methods: online, interpreting error logs to isolate the FRU; and

ofﬂine, interpreting ROM-based diagnostic messages to isolate the FRU.

In addition, the chapter provides information on testing DSSI storage devices,

using MOP Ethernet functions to isolate errors, and interpreting UETP

failures.

The chapter concludes with a section on running loopback tests to test the

console port, embedded Ethernet ports, Embedded DSSI busses, and Q–bus

modules.

5.1 Basic Troubleshooting Flow

Before troubleshooting any system problem, check the site maintenance log for

the system’s service history. Be sure to ask the system manager the following

questions:

• Has the system been used before and did it work correctly?

• Have changes (changes to hardware, updates to ﬁrmware or software) been

made to the system recently?

• What is the state of the system—is it on line or off line?

If the system is off line and you are not able to bring it up, use the ofﬂine

diagnostic tools, such as RBDs, MDM, and LEDs.

If the system is on line, use the online diagnostic tools, such as error logs,

crash dumps, UETP, and other log ﬁles.

Four common problems occur when you make a change to the system:

• Incorrect cabling

• Module conﬁguration errors (incorrect CSR addresses and interrupt

vectors)

• Incorrect grant continuity

System Troubleshooting and Diagnostics 5–1