64 Service Manual (AA-RS2ED-TE, July 2004)

Diagnostics

82 Director 2/64 Service Manual

Was an event code 400, or 411, or 413 observed at the director Event Log (HAFM

appliance) or at the Embedded Web Server Event Log?

YES NO

↓ Analysis for the failure is not described in this MAP. Go to “MAP

0000: Start MAP” on page 46. Exit MAP.

Table 7 lists event codes, brief explanations of the codes, and the associated steps

that describe fault isolation procedures.

POST/IPL diagnostics detected an FRU failure as indicated by an event code 400

with supplementary event data.

1. At the Hardware View, click Logs > Event Log. The Event Log displays.

2. Examine the first two bytes (0 and 1) of event data.

Byte 0 is an FRU code that indicates the failed component. Byte 1 is the slot

number of the failed FRU (00 for a nonredundant FRU, 00 or 01 for redundant

FRUs, and 00 through 15 for UPM cards).

Table 8 lists byte 0 FRU codes and associated steps that describe fault

isolation procedures.

Table 7: MAP 0200: Event Codes

Event Code Explanation Action

400 Power-up diagnostic failure. Go to step 4

411 Firmware fault. Go to step 11

413 Backup CTP2 card POST

failure.

Go to step 12

Table 8: Byte 0 FRU Codes

Byte 0 Failed FRU Action

01 Backplane. Go to step 5

02 CTP2 card. Go to step 6

03 SBAR assembly. Go to step 7