Other Event Logs And General Diagnostic Tools; Building Up The System - HP Integrity cx2600 Maintenance Manual

Hp integrity cx2600 operations and maintenance guide
Hide thumbs Also See for Integrity cx2600:
Table of Contents

Advertisement

Figure 4-3 Offline Diagnostic Main Menu
***************************************************************************
******
******
******
****** (C) Copyright Hewlett-Packard Co 1993-2003
******
******
****** HP shall not be liable for any damages resulting from the
****** use of this program.
****** ******
******
******
******
******
***************************************************************************
Type HELP for command information.
ODE> ls
Modules on this boot media are:
filename
-----------------------------------------------------------------------------
CIODIAG2.EFI
CPUDIAG.EFI
IODIAG.EFI
MAPPER.EFI
MEMDIAG.EFI
PERFVER.EFI
PLUTODIAG.EFI
COPYUTIL.EFI
DFDUTIL.EFI
FCFUPDATE.EFI
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
each troubleshooting step, clear the logs to ensure that you analyze only valid information.
68
Troubleshooting
Offline Diagnostic Environment
All Rights Reserved
TC Version B.00.10
SysLib Version B.00.06
Mapfile Version B.01.05
type
size
created
TM
642560
06/06/2003 Core IO diagnostic
TM
737280
06/06/2003 Processor diagnostic
TM
143872
06/06/2003 Runs selftests on I/O modules
TM
1653248
06/06/2003 System mapping utility
TM
263168
06/06/2003 Memory diagnostic
TM
814592
06/06/2003 Runs ROM-based selftests on peripherals
TM
514560
06/06/2003 SBA/LBA diagnostic
TM
1041920
06/06/2003 Disk-to-tape copy utility
TM
850432
06/06/2003 Disk firmware download utility
TM
608256
06/06/2003 FW Update Utility for Fibre Channel
"Event Logs for Troubleshooting Diagnostics" (page
******
******
******
******
******
******
******
******
******
******
description
******
******
64). After

Advertisement

Table of Contents
loading

Table of Contents