Intel SBXL52 Hardware Maintenance Manual - Page 35

POST error logs, Viewing error logs from the Configuration/Setup Utility program

Get Intel SBXL52 - Server Compute Blade PDF manuals and user guides View all Intel SBXL52 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

Use the light path diagnostics feature to identify system errors quickly. See the "Light path diagnostics* feature overview" on page 24 for more information. POST error logs When you turn on the server, it performs a series of tests to check the operation of server components and some of the options that are installed in the blade server. This series of tests is called the power-on self-test, or POST. If POST finishes without detecting any problems, a single beep sounds, and the first screen of your operating system or application program appears. If POST detects a problem, more than one beep sounds, and an error message appears on your screen. See "Beep symptoms" on page 69 and "POST error codes" on page 76 for more information. Notes: 1. If you have a power-on password set, you must type the password and press Enter, when prompted, before POST will continue. 2. A single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After you correct the cause of the first error message, the other error messages usually will not occur the next time you run the test. The POST error log contains the three most recent error codes and messages that the system generated during POST. The System Error log refers you to the management module log, which can be accessed through the SBCE unit. Viewing error logs from the Configuration/Setup Utility program Start the Configuration/Setup Utility program; then, select Error Logs from the main menu. See "Using the Configuration/Setup Utility program" on page 11 for more information. Diagnostic programs and error messages The server diagnostic programs are stored in ROM on the system board. These programs are the primary method of testing the major components of your server. Diagnostic error messages indicate that a problem exists; they are not intended to be used to identify a failing part. Troubleshooting and servicing of complex problems that are indicated by error messages should be performed by trained service personnel. Sometimes the first error to occur causes additional errors. In this case, the blade server displays more than one error message. Always follow the suggested action instructions for the first error message that appears. The following sections contain the error codes that might appear in the detailed test log and summary log when the diagnostic programs are run. The error code format is as follows: fff-ttt-iii-date-cc-text message where: fff is the three-digit function code that indicates the function being tested when the error occurred. For example, function code 089 is for the microprocessor. Diagnostics 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
Diagnostics
21
Use the light path diagnostics feature to identify system errors quickly. See the “Light path
diagnostics* feature overview” on page 24 for more information.
POST error logs
When you turn on the server, it performs a series of tests to check the operation of server
components and some of the options that are installed in the blade server. This series of tests is
called the power-on self-test, or POST.
If POST finishes without detecting any problems, a single beep sounds, and the first screen of your
operating system or application program appears.
If POST detects a problem, more than one beep sounds, and an error message appears on your
screen. See “Beep symptoms” on page 69 and “POST error codes” on page 76 for more information.
Notes:
1.
If you have a power-on password set, you must type the password and press Enter, when
prompted, before POST will continue.
2.
A single problem might cause several error messages. When this occurs, work to correct the
cause of the first error message. After you correct the cause of the first error message, the other
error messages usually will not occur the next time you run the test.
The POST error log contains the three most recent error codes and messages that the system
generated during POST. The System Error log refers you to the management module log, which can
be accessed through the SBCE unit.
Viewing error logs from the Configuration/Setup Utility program
Start the Configuration/Setup Utility program; then, select
Error Logs
from the main menu. See
“Using the Configuration/Setup Utility program” on page 11 for more information.
Diagnostic programs and error messages
The server diagnostic programs are stored in ROM on the system board. These programs are the
primary method of testing the major components of your server.
Diagnostic error messages indicate that a problem exists; they are not intended to be used to identify
a failing part. Troubleshooting and servicing of complex problems that are indicated by error
messages should be performed by trained service personnel.
Sometimes the first error to occur causes additional errors. In this case, the blade server displays
more than one error message. Always follow the suggested action instructions for the
first
error
message that appears.
The following sections contain the error codes that might appear in the detailed test log and
summary log when the diagnostic programs are run.
The error code format is as follows:
fff-ttt-iii-date-cc-text message
where:
fff
is the three-digit function code that indicates the function being tested when the
error occurred. For example, function code 089 is for the microprocessor.