Clearing The Event Logs; Post; Post Error Codes - IBM x3250 M3 Problem Determination And Service Manual

Clearing the event logs

To clear the event logs, complete the following steps.
Note: The POST event log is automatically cleared each time the server is
restarted.
1. Turn on the server.
2. When the prompt <F1> Setup is displayed, press F1. If you have set both a
3. Use one of the following procedures:

POST

When you turn on the server, it performs a series of tests to check the operation of
the server components and some optional devices in the server. This series of tests
is called the power-on self-test, or POST.
Note: This server does not use beep codes for server status.
If a power-on password is set, you must type the password and press Enter, when
you are prompted, for POST to run.
If POST detects a problem, an error message is displayed. See "POST error codes"
for more information.

POST error codes

The following table describes the POST error codes and suggested actions to
correct the detected problems. These errors can appear as severe, warning, or
informational.
24
IBM System x3250 M3 Types 4251, 4252, and 4261: Problem Determination and Service Guide
Table 3. Methods for viewing event logs (continued)
Condition
The server is not hung and is not connected
to a network.
The server is hung.
power-on password and an administrator password, you must type the
administrator password to view the error logs.
v To clear the IMM system-event log, select System Event Logs --> System
Event Log. Select Clear System Event Log; then, press Enter twice.
Action
Use IPMItool locally to view the system-event
log.
v If DSA Preboot is installed, restart the
server and press F2 to start DSA Preboot
and view the event logs.
v If DSA Preboot is not installed, insert the
DSA Preboot CD and restart the server to
start DSA Preboot and view the event
logs.
v Alternatively, you can restart the server
and press F1 to start the Setup utility and
view the POST event log or system-event
log. For more information, see "Viewing
event logs without restarting the server" on
page 22.