Hewlett-Packard Integrity cx2600 Maintenance Manual
Download Maintenance manual of HP Integrity cx2600 Server for Free or View it Online on All-Guides.com.
Figure 4-3 Offline Diagnostic Main Menu
***************************************************************************
****** ******
****** Offline Diagnostic Environment ******
****** ******
****** (C) Copyright Hewlett-Packard Co 1993-2003 ******
****** All Rights Reserved ******
****** ******
****** HP shall not be liable for any damages resulting from the ******
****** use of this program. ******
****** ******
****** TC Version B.00.10 ******
****** SysLib Version B.00.06 ******
****** Mapfile Version B.01.05 ******
****** ******
***************************************************************************
Type HELP for command information.
ODE> ls
Modules on this boot media are:
filename type size created description
-----------------------------------------------------------------------------
CIODIAG2.EFI TM 642560 06/06/2003 Core IO diagnostic
CPUDIAG.EFI TM 737280 06/06/2003 Processor diagnostic
IODIAG.EFI TM 143872 06/06/2003 Runs selftests on I/O modules
MAPPER.EFI TM 1653248 06/06/2003 System mapping utility
MEMDIAG.EFI TM 263168 06/06/2003 Memory diagnostic
PERFVER.EFI TM 814592 06/06/2003 Runs ROM-based selftests on peripherals
PLUTODIAG.EFI TM 514560 06/06/2003 SBA/LBA diagnostic
COPYUTIL.EFI TM 1041920 06/06/2003 Disk-to-tape copy utility
DFDUTIL.EFI TM 850432 06/06/2003 Disk firmware download utility
FCFUPDATE.EFI TM 608256 06/06/2003 FW Update Utility for Fibre Channel
ODE>
Other Event Logs and General Diagnostic Tools
This section describes other general diagnostic tools that will be provided for your HP Server
and how to generate other event logs for troubleshooting diagnosis.
• A general diagnostic tool that is available to support your HP Server is the MCA analyzer
• Event logs not generated by the management processor include:
— Machine check abort log (MCA)
— Corrected machine check log (CMC)
— Corrected platform error log (CPE)
To access these logs type in at the shell> command line prompt:
errdump mca
errdump cmc
errdump cpe
Building Up the System
Before you can build up the system, you must first identify the failing CRU.
To identify a failing CRU, follow these steps:
1. Reduce the server to the minimum hardware configuration by disconnecting power and
removing unwanted assemblies.
2. Install assemblies one-at-a-time and check system status.
3. After each assembly is installed, apply power and observe the server for symptoms and
fault indications. If possible, install only known good assemblies.
You must be familiar with error messages, system logs, and accessing logs. For information about
accessing and using logs, see “Event Logs for Troubleshooting Diagnostics” (page 64). After
each troubleshooting step, clear the logs to ensure that you analyze only valid information.
68 Troubleshooting