IBM @Server pSeries 630 6E4, Руководство по обслуживанию

Страница: 368 / 651

If there are no other error codes or indications of a problem, the A806 (loss of surveillance
heartbeat) was a temporary condition and has been resolved; the B1xx4699 code is then an
informational message only. If the problem persists:
1. Run diagnostics on the serial port on the HMC.
2. Replace the primary I/O book, location U1.18-P1-H2.
Values of A009 and A719 of bytes 68 and 69 in the AIX error log entry or the first two bytes of word 13 in
the service processor error log entry are also informational entries:
A009: The system received a power-off request at runtime from the HMC, or the white button on the
operator panel was used to power down the system at runtime.
A719: Primary power failed; the system switched to battery backup power.
The following values of bytes 68 and 69, or the first half of word 13, indicate an internal error
occurred in the capacity upgrade on demand (CUoD) firmware or hardware that was corrected. No
action is required by the customer or service representative.
C101, C103, C104, C109, C10B, C10C, C10D, C10E, C10F, C110, C112, C113, C114, C115,
C116, C117, C118, C11A, C11F, C120, C121, C122, C123, C124, C125, C126, C127, C128, C129,
C12A, C12B, C12C, C12D, C12E, C12F, C130, C131, C132, C133, C134, C135, C136, C138,
C13B, C13C, C140, C141, C142, C143, C144, C145, C146, C147, C149, C14A, C14B, C14C,
C14D, C14E, C14F, C150, C151, C152, C153, C154, C155, C156, C158, C159
For all other values of bytes 68 and 69, or the first two bytes of word 13, do the following:
1. Check for system firmware updates.
2. Reset the service processor by activating the pinhole reset switch on the operator panel.
3. Call service support.
Error Code B1xx 8FF0
The following error code was moved out of the Common Firmware Error Code table because of the size of
the description column.
Error Code Description: Action/ Possible Failing FRU:
B1xx 8FF0 Informational message No action required. (The data in these informational log entries
may be used by support personnel to gather additional debug
information.)
For complete information regarding this error code, read through this entire section.
If the managed server is down, go to the service processor error log and find the error log entry containing
B1xx 8FF0. Examine the first two bytes of word 13 of the detailed entry information.
If the managed server is running, do the following:
v
Examine the AIX error log entry containing B1xx 8FF0. This is a FIRMWARE_EVENT error with an
identifier of A6D1BD62.
v
In the detail data, find the string B1xx 8FF0. (If present, it will be at byte 60 of the detail data.)
v Move forward 8 bytes to bytes 68 and 69; this is the value of word 13 in the service processor error log
entry.
If the system is running Linux, examine the Linux system log. The line(s) in the extended data that begin
with <4>RTAS: Log Debug: 04 contain the error code in the next 8 hex characters. (This error code is also
known as word 11). Each 4 bytes after the error code in the Linux extended data are another word. The 4
bytes after the error code are word 12 and the next four bytes are word 13. An example of the Linux
extended data, and finding words 11, 12, and 13, is shown in MAP 1321, step 1321-28, and step 1321-29,
in this service guide.
348
Eserver
pSeries 630 Model 6C4 and Model 6E4 Service Guide