SRNs are listed in the
RS/6000
Eserver
pSeries Diagnostic Information for Multiple Bus Systems
.
FRU isolation
For a list of error codes and recommended actions for each code, see Chapter 5, “Error code to FRU
index”, on page 125. These actions can refer to Chapter 12, “Parts information”, on page 373, Chapter 3,
“Maintenance Analysis Procedures (MAPs)”, on page 39, or provide informational message and directions.
If a replacement part is indicated, direct reference is made to the part name. The respective AIX and
physical location codes are listed for each occurrence as required. For a list of locations codes, see
“Location codes” on page 17.
To look up part numbers and view component diagrams, see Chapter 12, “Parts information”, on page 373.
The beginning of that chapter provides a parts index with the customer replacement units (CRUs) and the
predominant field replaceable units (FRUs) listed by name. The remainder of the chapter provides
illustrations of the various assemblies and components that make up the system.
FRU identify LEDs
This system is configured with an arrangement of LEDs that help identify various components of the
system. These include, but are not limited to the following:
v
RIO port identify LED (not supported)
v
Various FRU identify LEDs
– Power subsystem FRUs
– CEC subsystem FRUs
– I/O subsystem FRUs
– PCI-X adapter identify LED
– DASD identify LED
See “Component LEDs” on page 384.
Any identify LED in the system can be flashed when the system is in the failed state with power on by
using the service processor LED Control Menu contained in the “System information menu” on page 268.
Any identify LED in the system can also be flashed by using the
″
Identify and Attention Indicators
″
task
through diagnostics. The procedure to operate the
″
Identify and Attention Indicators
″
task in diagnostics is
outlined in the
RS/6000
Eserver
pSeries Diagnostic Information for Multiple Bus Systems
.
Remote error notification (call home)
The NAS Gateway 500 is a high-reliability device that includes advanced monitoring of critical
components. When certain error events occur, notifications can be sent to monitoring facilities (for
example, IBM Service). The NAS Gateway 500 supports two methods for doing this.
The first method is the Electronic Service Agent (ESA), which is a pre-loaded application on the NAS
Gateway 500. The second method is through the service processor. The service processor, as a
self-contained independent processor, does not depend on the functioning of the operation system and
can be used to report some errors that the ESA cannot.
Chapter 2. Problem determination overview
35
Summary of Contents for TotalStorage NAS Gateway 500
Page 1: ...IBM TotalStorage NAS Gateway 500 Service Guide GY27 0418 00 ...
Page 2: ......
Page 3: ...IBM TotalStorage NAS Gateway 500 Service Guide GY27 0418 00 ...
Page 16: ...xiv NAS Gateway 500 Service Guide ...
Page 20: ...xviii NAS Gateway 500 Service Guide ...
Page 36: ...System logic flow Note Not all components are supported 16 NAS Gateway 500 Service Guide ...
Page 52: ...32 NAS Gateway 500 Service Guide ...
Page 58: ...38 NAS Gateway 500 Service Guide ...
Page 112: ...92 NAS Gateway 500 Service Guide ...
Page 266: ...246 NAS Gateway 500 Service Guide ...
Page 326: ...306 NAS Gateway 500 Service Guide ...
Page 353: ...Chapter 11 Removal and replacement procedures 333 ...
Page 392: ...372 NAS Gateway 500 Service Guide ...
Page 402: ...382 NAS Gateway 500 Service Guide ...
Page 412: ...392 NAS Gateway 500 Service Guide ...
Page 440: ...420 NAS Gateway 500 Service Guide ...
Page 446: ...426 NAS Gateway 500 Service Guide ...
Page 448: ...428 NAS Gateway 500 Service Guide ...
Page 466: ...446 NAS Gateway 500 Service Guide ...
Page 469: ......
Page 470: ... Printed in U S A GY27 0418 00 ...
Page 471: ...Spine information IBM TotalStorage NAS Gateway 500 NAS Gateway 500 Service Guide GY27 0418 00 ...