RS/6000 3-Digit Display Codes
000 The node is in shutdown mode.
001 The initialization routine leads to a single user mode.
0c0 User Requested Dump completed successfully. You requested a dump
using the sysdumpstart command, a dump key-sequence, or the RESET
button.
ACTION:
Examine dump now or save dump for later examination.
0c1 The dump failed due to an I/O error.
0c2 User Requested Dump started. You requested a dump using the
sysdumpstart command, a dump key-sequence, or the RESET button.
ACTION:
Wait 1 minute for dump to complete and the 3-Digit Display code
to change. If the the 3-Digit Display code is still '0c2' after
1 minute, the dump has failed to complete, a partial dump may be
present. Examine dump now or save dump for later examination.
Request dump to alternate dump device.
0c3 The dump is inhibited.
0c4 The dump did not complete. A partial dump may be present.
ACTION:
Examine partial dump now or save partial dump for later
examination. Request dump to alternate dump device.
Increase size of dump media to prevent recurrence.
0c5 Dump failed to start. An unexpected error occurred while
attempting to write to the dump media.
ACTION:
Request dump to alternate dump device.
0c6 User Requested Dump to the secondary dump device requested. You
requested a dump using the sysdumpstart command or the
Ctrl-Alt-Numpad2 key sequence.
ACTION:
Make sure that the device assigned as the secondary dump device
is ready to receive the dump, then key Ctrl-Alt-Numpad2 again.
0c7 Remote dump in progress.
0c8 Dump disabled. The system configuration did not include a dump
device for the requested dump.
ACTION:
Request dump to alternate dump device.
0c9 System initiated dump started. An unexpected system halt has
occurred, dump was started automatically.
ACTION:
Wait for dump to complete, 3-digit-display will change to
flashing 888.
0cc Unknown dump failure
Note: For AIX 4.2.1 and later only.
Explanation: An error occurred dumping to the primary dump device,
and we've switched over to the secondary dump device.
System Action: Writing a system dump.
User Action: A dump started by the system is in progress. Wait at
least 1 minute for the dump to complete and for the three-digit
display value to change. If the three-digit display value changes,
find the new value on this list. If the value does not change, then
the dump did not complete due to an unexpected error.
100 BIST completed successfully, control was passed to IPL ROS.
101 Initial BIST started following RESET or POR
102 BIST started following Power-On-RESET or push button pressed.
103 BIST could not determine the system model number. The system halts.
104 BIST could not find the Common on-chip processor bus address. The
system halts.
105 BIST could not read from the on-chip sequencer EPROM. The system halts.
106 BIST detected a module failure. CBA (Common on-chip processor bus
address) not found in S&S area
111 BIST detected a module failure. On-chip sequencer stopped.
(Press button for details. Follow the steps for a flashing 888)
112 Checkstop occurred during BIST and checkstop results could not be
logged out. The system attempted to save the failure data associated
with the checkstop into NVRAM but was unsuccessful. The system halts.
113 The BIST checkstop count was greater than 1. (=3). The checkstop count
is initialized to 0 (zero) whenever the system is turned on. When a
checkstop occurs, the checkstop count is increased and a system
restart begins automatically. If the system restart is successful,
the operating system records the checkstop in the system error log
and resets the checkstop count to 0. If three consecutive checkstops
occur without a system restart completing successfully, the system
halts.
120 Progress indicator. BIST started CRC check on 875X EPROM
121 BIST detected a bad CRC on the On-chip sequencer EPROM.
122 BIST started CRC check on the On-chip sequencer EPROM.
123 BIST detected a bad CRC on the On-chip sequencer NVRAM. The system
halts.
124 BIST started CRC check on the On-chip sequencer NVRAM space.
125 BIST detected a bad CRC on the time of day NVRAM. The system halts.
126 BIST started CRC check on the time of day NVRAM.
127 BIST detected a bad CRC on the 8752 EPROM. The system halts.
130 BIST presence test started or push button stuck.
140 BIST Failed, Box Manufacturing BIST bypass - run BIST anyway.
142 BIST Failed, Box Manufacturing normal mode of operation.
143 Invalid memory configuration.
144 BIST Failed; procedure error. The system halts.
151 BIST started AIPGM test code (array initialiation on all chips).
152 BIST started DCLST test code (DC logic self test on all chips).
153 BIST started ACLST test code (AC logic self test on all chips).
154 BIST started AST test code (array self test on all chips).
160 BIST detected a missing EPOW (Early Power On Warning) connector.
The system halts.
161 - BIST being conducted on BUMP I/O
- The Bump quick I/O tests failed. The system halts.
162 - BIST being conducted on JTAG
- The JTAG tests failed. The system halts.
163 BIST being conducted on Direct I/O
164 BIST encountered an error while reading low NVRAM. The system halts.
165 BIST encountered an error while writing low NVRAM. The system halts.
166 BIST encountered an error while reading high NVRAM. The system halts.
167 BIST encountered an error while writing high NVRAM. The system halts.
168 BIST encountered an error while reading the SIO (Serial I/O) register.
The system halts.
169 BIST encountered an error while writing the SIO (Serial I/O) register.
The system halts.
170 BIST being conducted on Multi-Processor
180 - BIST logout failed or logout complete (displayed for 1 minute).
- Built-in self-test checkstop logout in progress. The system is
saving checkstop failure data into NVRAM.
182 BIST COP bus not responding
185 Checkstop occurred during BIST, 10 sec to hook up ESP before logout.
186 System logic-generated checkstop (Model 250 only)
187 BIST was unable to identify the chip release level in the
checkstop logout data. The system halts.
195 BIST checkstop logout completed. The system successfully saved
checkstop failure data into NVRAM.
200 Explanation: The key mode switch is in the Secure position. It must
be in the Normal position to load the operating system and in the
Service position to load Diagnostics or AIX Install/Maintenance.
System Action: Sensing key-switch position.
User Action: Turn the key mode switch to the correct position. After
you do this, the value in the three-digit display should change.
201 Checkstop occurred during IPL. The system halts. FATAL
202 Machine_check_handler. Unexpected machine check interrupt FATAL
203 Data_Storage_Interrupt_handler FATAL
204 Instruction_Storage_Interrupt_handler FATAL
205 External_Interrupt_handler FATAL
206 Alignment_Interrupt_handler FATAL
207 Program_Interrupt_handler FATAL
208 - Floating_Point_Unavailable_handler FATAL
- Machine check due to an L2 uncorrectable ECC. FATAL
209 - Reserved_900_handler FATAL
- RSC2 POST - same LED value as Reserved_900_hdlr
20c RS2 L2 Cache detected (error if stays solid for 5 secs)
210 SVC_1000_handler (SVC = switched virtual circuit) FATAL
211 IPL ROM CRC miscompare during IPL FATAL
212 - RAMPOST Processor Bad FATAL
- RAMPOST Memory Configuration Reisters failure FATAL
213 - Memory Card failure or Processor Planar Bad FATAL
- RAMPOST full/hfwd & byte Load & Store failure FATAL
- RAMPOST failed. Memory cannot be configured because the system
could not detect any good memory. FATAL
214 - Power status register failed FATAL
- RAMPOST PIO Load and Store circuitry failure FATAL
- An I/O planar failure has been detected. The power status
register, the time-of-day clock, or NVRAM on the I/O planar has
failed. FATAL
215 - A low voltage condition is present FATAL
Explanation: Progress indicator. The level of voltage supplied
to the system is too low to continue a system restart.
System Action: The system monitors the voltage level. When the
voltage is correct, the system continues with its system restart.
User Action: Check that the power cable is correctly attached to
the system and to the electrical outlet. Check that power is
available at the electrical outlet.
- RAMPOST ECC Generation circuitry failure FATAL
216 - RAMPOST ECC Correction circuitry failure FATAL
- IPL ROM code being uncompressed into memory. If the uncompression
fails, the system halts.
217 - RAMPOST Bit Steering Logic failure FATAL
- End of Bootlist - same LED as Bit Steer Logic Fail. The system
continues to loop through the boot devices list.
218 - RAM POST testing for 1 MB of good memory
- RAMPOST 1 Meg of good memory not found, address/remap fail FATAL
219 RAMPOST bit_map_generation FATAL
21c RS2 L2 Cache POST completed. L2 cache not detected as part of
systems configuration (when LED persists for 2 seconds).
220 - ROM scan selected for ipl
- IPL Control Block being initialized.
221 NVRAM CRC miscompare occurred while trying to boot the AIX
Operating (Mode Switch in NORMAL position.) For systems with an
internal direct attached hard file, IPL ROM attempted to boot
from this hardfile before halting with this 3-Digit Display
code.
ACTION:
If the system halts with this value in the 3-Digit Display, boot
and run diagnostics to determine if there is an NVRAM failure.
The system automatically reinitializes NVRAM when you boot
diagnostics (or AIX Install/ Maintenance, or AIX Maintenance
Mode) so a subsequent attempt to boot the AIX Operating System
should not result in the system halting with this 3-Digit Display
code. The system does not automatically restore the contents of
NVRAM which you may have added, e.g. IPL device lists, you will
need to restore this information using whatever means you
originally used to create it. To restore a NVRAM that has been
customized, use the bootlist command. Use the date command to
reset the system clock, and then stop.
222 Explanation: Progress indicator. Attempting a Normal-mode system
restart from the standard I/O planar-attached devices specified in
the NVRAM IPL devices list.
System Action: The system retries.
User Action: If you have not rebooted, do so now.
223 Attempting a Normal-mode system restart from the SCSI-attached devices
specified in the NVRAM boot devices list.
224 - SLA selected for IPL
- Attempting a Normal-mode system restart from the 9333
High-Performance Disk Drive Subsystem devices specified in the NVRAM
boot device list.
225 - SJL or DBA (esdi hardfile) selected for IPL
- Attempting a Normal-mode system restart from the bus-attached
internal disk specified in the NVRAM boot devices list.
226 Attempting a Normal-mode system restart from Ethernet specified in
the NVRAM boot devices list.
227 Attempting a Normal-mode system restart from Token-Ring specified in
the NVRAM boot devices list.
228 Progress indicator. Attempting a Normal-mode system restart using the
expansion code devices list, but cannot restart from any of the
devices in the list.
229 A normal mode device list is present but has no entries (null
list) or none of the valid entries succeeded in ipl
ACTION:
If the system halts with this value in the three digit display,
either the NVRAM device list is empty, the devices specified in
the list are not valid boot devices, or there is a problem with
the devices in the list. To determine if there is a problem with
the devices in the list, refer to the hardware problem
determination procedures in the RIOS Diagnostics Programs
Operators Guide. To modify the NVRAM device list, boot the AIX
Operating System and use the iplist command.
22c Attempting a normal mode IPL from FDDI specified in NVRAM IPL device
list.
230 Attempting a Normal-mode system restart from Family 2 Feature ROM
specified in the IPL ROM default devices list.
231 Attempting a Normal-mode system restart from Ethernet specified by
selection from ROM menus.
232 Attempting a Normal-mode system restart from the standard I/O
planar-attached devices specified in the IPL ROM default device list.
233 Attempting a Normal-mode system restart from the SCSI-attached devices
specified in the IPL ROM default device list.
234 - SLA selected for ipl
- Attempting a Normal-mode system restart from the 9333
High-Performance Disk Drive Subsystem devices specified in the IPL
ROM default device list.
235 - SJL or DBA (esdi hardfile) selected for ipl
- Attempting a Normal-mode system restart from the bus-attached
internal disk specified in the IPL ROM default device list.
236 Attempting a Normal-mode system restart from the Ethernet specified
in the IPL ROM default devices list.
237 Attempting a Normal-mode system restart from the Token-Ring specified
in the IPL ROM default devices list.
238 Attempting a Normal-mode system restart from the Token-Ring specified
by selection from ROM menus.
239 - Menu selected device (Ethernet or Token Ring) failed to boot.
- A Normal-mode menu selection failed to boot.
User Action: If the system continues to run, either the device
specified in the menu selection list is not a valid boot device, or
there is a problem with the device in the list.
To determine if there is a problem with the device, refer to
Hardware Diagnostics. If there is a hardware failure, report it to
your hardware service organization. If not, report the failure to your
software service organization, and then stop. You have completed these
procedures.
To modify the NVRAM device list, enter Maintenance mode (refer
to Accessing a System That Will Not Boot for information on loading the
Maintenance mode onto your system), and use the bootlist command, then
stop. You have completed these procedures.
23c Attempting a Normal-mode IPL from FDDI specified in IPL ROM device
list.
240 Attempting a Service-mode system restart from the Family 2 Feature ROM
specified in the NVRAM boot devices list.
241 Attempting a Normal-mode system restart from devices specified in
NVRAM boot list.
242 Attempting a Service-mode system restart from the standard I/O
planar-attached devices specified in the NVRAM boot device list.
243 Attempting a Service-mode system restart from the SCSI-attached
devices specified in NVRAM boot device list.
244 - SLA selected for ipl
- Attempting a Service-mode system restart from the 9333
High-Performance Disk Drive Subsystem devices specified in the NVRAM
boot device list.
245 - SJL or DBA (esdi hardfile) selected for ipl
- Attempting a Service-mode system restart from the bus-attached
internal disk specified in the NVRAM boot device list.
246 Attempting a Service-mode system restart from the Ethernet specified
in the NVRAM boot devices list.
247 Attempting a Service-mode system restart from the Token-Ring specified
in the NVRAM boot devices list.
248 Attempting a Service-mode system restart using the expansion code
specified in the NVRAM boot devices list.
User Action: If you have not rebooted, do so now. Otherwise, record
the SRN 101-248 in the Problem Summary Form. Report the problem to
your hardware service organization, and then stop. You have completed
these procedures. If the system continues to run, either the NVRAM
device list is empty, the devices specified in the list are not
valid boot devices, or there is a problem with one of the devices in
the list.
To determine if there is a problem with the device, refer to
Hardware Diagnostics. If there is a hardware failure, report it to
your hardware service organization. If not, report the failure to your
software service organization, and then stop. You have completed these
procedures.
To modify the NVRAM device list, enter Maintenance mode (refer
to Accessing a System That Will Not Boot for information on loading the
Maintenance mode onto your system), and use the bootlist command, then
stop. You have completed these procedures.
249 Explanation Progress indicator. Attempting a Service-mode system
restart from devices in NVRAM boot devices list, but cannot restart
from any of the devices in the list.
System Action The system retries.
User Action Either the NVRAM device list is empty, the devices
specified in the list are not valid boot devices, or there is a
problem with the devices in the list.
To determine if there is a problem with the device, refer to
Hardware Diagnostics. If there is a hardware failure, report it to
your hardware service organization. If not, report the failure to your
software service organization, and then stop. You have completed these
procedures.
To modify the NVRAM device list, enter Maintenance mode (refer
to Accessing a System That Will Not Boot for information on loading the
Maintenance mode onto your system), and use the bootlist command, then
stop. You have completed these procedures.
24c Attempting a Service-mode IPL from FDDI specified in NVRAM IPL device
list.
ACTION: See action for error code 229
250 Attempting a Service-mode system restart from the Family 2 Feature
ROM specified in the IPL ROM default devices list.
251 Attempting a Service-mode system restart from Ethernet specified by
selection from ROM menus.
252 Attempting a Service-mode system restart from the standard I/O
planar-attached devices specified in the IPL ROM default device list.
253 Attempting a Service-mode system restart from the SCSI-attached
devices specified in the IPL ROM default device list.
254 - SLA selected for ipl
- Attempting a Service-mode system restart from the 9333
High-Performance Subsystem devices specified in the IPL ROM default
device list.
255 - SJL or DBA (esdi hardfile) selected for ipl
- Attempting a Service-mode system restart from the bus-attached
internal disk specified in the IPL ROM default device list.
256 Attempting a Service-mode system restart from the Ethernet specified
in the IPL ROM default devices list.
257 Attempting a Service-mode system restart from Token-Ring specified in
the IPL ROM default devices list.
258 Attempting a Service-mode system restart from the Token-Ring specified
by selection from ROM menus.
259 Attempting a Service-mode IPL from FDDI specified by the operator.
25c Attempting a Service-mode IPL from FDDI specified in IPL ROM device
list.
260 - Explanation Progress indicator. Menus are being displayed on the
local display or terminal connected to your system.
System Action The system waits for input from the keyboard.
User Action Use the keyboard to enter the desired menu option. If
the system halts with this value displayed and there is no menu
displayed, go to Hardware Diagnostics
- NVRAM not initialized with bootlist, keyboard type and language
type even tho keyboard / display or tty connected to system
261 - Explanation No supported local system display adapter was found.
System Action The system waits for a response from an asynchronous
terminal on serial port 1.
User Action If there is an asynchronous terminal attached to serial
port 1, make sure the asynchronous terminal is ready. When the
terminal is ready, press any key on the asynchronous terminal's
keyboard, and a menu is displayed on the asynchronous terminal.
If there is a local display attached to the system and it was not
found during system restart, there may be a problem with the
display. Go to Hardware Diagnostics.
If there is no asynchronous terminal or local display, then turn
the key mode switch to the Normal mode position and then back to
Service mode. This action causes the Service mode IPL process to
resume.
- NVRAM not initialized with bootlist, keyboard type and language
type with no keyboard / display or tty connected to system
262 Attempting Network IPL, menus, no console keyboard detected
Console handlers request led value.
Explanation No local system keyboard was found.
System Action The system waits for a response from an asynchronous
keyboard on serial port 1.
User Action If there is an asynchronous terminal attached to
serial port 1, make sure the asynchronous terminal is ready. When the
terminal is ready, press any key on the asynchronous terminal's
keyboard, and a menu is displayed on the asynchronous terminal.
If there is a local keyboard attached to the system and it was not
found during system restart, there may be a problem with the keyboard.
Go to Hardware DiagnosticsIf there is no asynchronous keyboard or
local keyboard, do the following:
If the key mode switch is in Normal mode position, switch it to the
Service mode position and then back to Normal mode.
If the key mode switch is in Service mode position, switch it to the
Normal mode position and then back to Service mode.
NOTE: Check for blown planar fuses or for a corrupted boot on disk
drive
263 Attempting Normal mode system restart from Family 2 feature ROM
specified in the NVRAM boot device list
269 Stalled state - the system is unable to IPL. Cannot boot system, end of
boot list reached
270 Ethernet/FDX 10 Mbps MC adapter power-on self-test is running.
271 Mouse and mouse port POST
272 Tablet port POST
276 A 10/100 Mbps Ethernet MC adapter power-on self-test is running.
277 Auto Token-Ring LANstreamer MC 32 Adapter POST is running.
278 Video ROM scan POST
279 FDDI POST
280 3com Ethernet POST
281 Keyboard POST
282 Parallel POST
283 Serial POST
284 - 7011/220 (SGA) POST
- POWER Gt1 graphics adapter POST
285 POWER Gt3 (LEGA) graphics adapter POST
286 Token Ring POST in progress (Power On Self Test == POST)
287 - Ethernet adapter POST in progress
- Adapter card slots being queried
288 - Microchannel POST in progress. Adapter card slots are being queried.
- Family 2 bus scan
289 - Diskette POST
- Gt0 POWER graphics adapter power-on self-test is running.
290 - IO Planar test started.
- IOCC POST
291 NIO POST being executed. Standard I/O planar power-on self-test is
running.
292 SCSI POST being executed. Note: Depending on the number of SCSI devices
attached to the system, this value may be displayed for several minutes.
293 SJL or Bus Attached Internal Disk/Hard File POST being executed
294 - SLA POST
- TCW SIMM in slot J is bad. (IOCC POST is testing SIMMs.)
295 - XX3 POST (Ethernet)
- Color Graphics Display power-on self-test is running.
296 - XX2 POST (Tokenring)
- Faimily 2 Feature ROM scan POST
297 - XX1 POST
- System model number could not be determined.
- System model number does not compare between OCS and ROS FATAL
298 Attempting warm IPL
299 IPL ROS has completed loading and has passed control to
passed control to the loaded code
2e6 Explanation Progress indicator. A PCI Ultra/Wide differential SCSI
adapter is being configured.
System Action The configuration method for the SCSI controller/
adapter is being run. If an irrecoverable error occurs, the system
will halt.
User Action If the system halts with the above action, try
powering off attached SCSI devices. If this resolves the problem,
check that each SCSI device has a unique SCSI ID, and that cabling
and terminal are correct. Otherwise, go to Hardware Diagnostics
2e7 Explanation An undetermined PCI SCSI adapter is being configured.
System Action The configuration method for the SCSI controller/
adapter is being run. If an irrecoverable error occurs, the system
will halt.
User Action If the system halts with the above action, try
powering off attached SCSI devices. If this resolves the problem,
check that each SCSI device has a unique SCSI ID, and that cabling
and terminal are correct. Otherwise, go to Hardware Diagnostics
301 Flash Utility ROM test failed or checkstop occured. FATAL
302 Flash Utility ROM User prompt, move key to Service position to select
an optional Flash update. LED 302 will appear only if the keyswitch is
secure. LED 302 will display for a maximum of 4 seconds. If you wish to
perform a Flash update, then the keyswitch should be moved to the
Service position during the 4 seconds that LED 302 is displayed. If
the key is moved to the Service position, then LED 303 will be
displayed for 4 seconds. This signals the user to press the Reset
button to initiate the optional Flash
303 Flash Utility ROM User prompt, press Reset button to initiate an
optional Flash update.
System Action LED 303 will display for a maximum of 4 seconds.
User Action If you wish to initiate a Flash update, then the Reset
button should be pressed during the time that LED 303 is displayed (see
LED 302).
304 - Flash Utility ROM IOCC POST error. FATAL
- I/O planar test started.
305 Flash Utility ROM standard I/O POST running.
306 Flash Utility ROM is attempting IPL from Flash Update media device.
Insert a Flash update diskette in the diskette drive
307 Flash Utility ROM system model # doesn't compare between OCS and ROM. FA
308 Flash Utility ROM IOCC TCW memory is being tested.
309 Flash Utility ROM passed control to a Flash Update Boot Image.
311 Flash Utility ROM CRC comparison error. FATAL
312 - Flash Utility ROM RAM POST memory configuration error or no mem found
- RAM power-on self-test found processor to be bad.
313 Flash Utility ROM RAM POST failure. Memory cannot be configured because
the system could not detect any good memory. FATAL
314 An I/O planar failure has been detected. The power status register, the
time-of-day clock, or NVRAM on the I/O planar has failed.
315 Flash Utility ROM detected a low voltage condition. The level of
voltage supplied to the system is too low to continue a system restart.
318 Flash Utility ROM RAM POST is looking for 1 Mb of good memory.
319 Flash Utility ROM RAM POST bit map is being generated.
322 CRC error on Flash Image. No Flash Update performed.
323 Current Flash Image is being erased. This LED will display for
approximately 5 seconds.
324 CRC error on new Flash Image after Update was performed.
325 Flash Update sucessful and complete.
42c Waiting for Interactive Maintenance Analysis Procedures (IMAP) request.
The diagnostic program is checking to see if a CE laptop computer is
attached to perform IMAPS.
43c Waiting for Interactive Maintenance Analysis Procedures (IMAP)
connection. The diagnostic program is configuring an IMAP connection.
If the LED persists, power off the system, disconnect the CE laptop
computer, and run regular diagnostics.
500 Querying Native I/O card (NIO or SIO).
501 Querying card in slot 1.
502 Querying card in slot 2.
503 Querying card in slot 3.
504 Querying card in slot 4.
505 Querying card in slot 5.
506 Querying card in slot 6.
507 Querying card in slot 7.
508 Querying card in slot 8.
510 Starting device configuration.
511 Device configuration completed.
512 Restoring device configuration files from media.
513 Restoring basic operating system installation files from media.
516 Contacting server during network boot.
517 Mounting client remote file system during network IPL (/ and /usr).
518 Remote mount of the / (root) and /usr file systems during network
boot did not complete successfully.
That's what the book says, at least. From personal experience, but
this means that AIX can't mount necessary file systems at boot time,
for example, /var. You need to boot the system from an AIX Install
CD, get into single-user mode, aka maintenance mode, start up a
limited-function shell, and run fsck -y on all rootvg file systems,
e.g. /, /usr, /var, /tmp, /home, and maybe some others.
520 bus configuration running.
521 - /etc/init invoked cfgmgr with invalid options, /etc/init
has been corrupted or incorrectly modified. FATAL
- The /etc/inittab file has been incorrectly modified or corrupted.
522 - The configuration manager has been invoked with conflicting
options. FATAL
- The /etc/inittab file has been incorrectly modified or corrupted.
523 - The configuration manager is unable to access the ODM data base. FATAL
- The /etc/objrepos file is missing or inacessible.
524 - The configuration manager is unable to access the config
rules object in the ODM data base. FATAL
- The /etc/objrepos/Config_Rules file is missing or inacessable.
525 - The configuration manager is unable to get data from customized
device object in the ODM data base. FATAL
- The /etc/objrepos/CuDv file is missing or inacessable.
526 - The configuration manager is unable to get data from customized
device driver object in the ODM data base. FATAL
- The /etc/objrepos/CuDvDr file is missing or inacessable.
527 - The configuration manager was invoked with the Phase 1 flag,
however, running Phase 1 at this point is not permitted. FATAL
- The /sbin/rc.boot file has been incorrectly modified or corrupted.
528 - The configuration manager can't find sequence rule or no program
name was specified in the ODM data base. FATAL
- The /etc/objrepos/Config_Rules file has been incorrectly modified,
corrupted, or a program specified in the file is missing.
529 The configuration manager is unable to update ODM data or the root
file system is full.
530 The savebase command was unable to save information about the base
customized devices onto the boot device during Phase 1 of system boot.
531 - The configuration manager is unable to access the PdAt object
class. FATAL
- The /usr/lib/objrepos/PdAt file is missing or inacessible.
532 There is not enough memory for the configuration manager to
continue (malloc failure). FATAL
533 - The configuration manager could not find a configure method for
a device.
- The /usr/lib/objrepos/PdDv file has been incorrectly modified,
corrupted, or a program specified in the file is missing.
534 The configuration manager is unable to acquire ODM database lock. FATAL
535 HIPPI diagnostic interface driver being configured.
536 - The configuration manager encountered more than one sequence
rule specified in the same phase. FATAL
- The /etc/objrepos/Config_Rules has been incorrectly modified or
corrupted.
537 - The configuration manager encountered an error when invoking
the program in the sequence rule.
- The /etc/objrepos/Config_Rules has been incorrectly modified,
corrupted, or a program specified in the file is missing.
538 The configuration manager is passing control to a configuration
method.
539 The configuration method has ended and control has returned
to the configuration manager.
540 Configuring child of IEEE-1284 parallel port.
544 An ECP peripheral configure method is executing.
545 A parallel port ECP device driver is being configured.
546 IPL cannot continue due to error in customized database.
547 Rebooting after error recovery. (LED 546 precedes this LED).
548 Restbase failure.
549 Console could not be configured for the "Copy a System Dump" menu.
550 ATM LAN emulation device driver is being configured.
551 IPL Varyon of the root volume group is running.
552 IPL Varyon of the root volume group failed. The ipl_varyon command
failed with a return code not equal to 4, 7, 8, or 9 (ODM or malloc
failure).
553 - IPL Phase 1 is complete. (/etc/(un)mount missing or / or /tmp full
- The /etc/inittab file has been incorrectly modified or corrupted.
554 - Unable to define NFS swap device during network boot.
- The IPL device could not be opened or a read failed (hardware not
configured or missing).
555 - Unable to create NFS swap device during network boot.
- ODM error when trying to varyon rootvg
- Using the fsck -fp /dev/hd4 command on the root file system failed
with a nonzero return code.
556 - Unable to configure NFS swap device during network boot.
- LVM subroutine error from ipl_varyon
557 Unable to fsck or mount the root (/) filesystem
558 There is not enough memory available to continue the IPL.
559 Less than 2MB of good memory are available to load the AIX kernel.
560 An unsupported monitor is attached to the display adapter.
565 Configuring the MWAVE subsystem.
566 Configuring Namkan twinax commo card (5250 emulation)
567 Configuring High-Performance Parallel Interface (HIPPI) device driver
(fpdev).
568 Configuring High-Performance Parallel Interface (HIPPI) device driver
(fphip).
569 FCS SCSI protocol device is being configured.
570 Configuring virtual SCSI devices. The configuration method for the
SCSI protocol device driver is being run.
571 Configuring HIPPI common functions driver.
572 Configuring IPI-3 master transport driver for use with HIPPI.
573 Configuring IPI-3 slave transport driver for use with HIPPI.
574 Configuring IPI-3 transport services user interface driver.
575 Configuring IBM 9570 (FC9300) RAID 3 disk array driver.
576 Configuring vendor Async device driver.
577 Configuring vendor SCSI device driver.
578 Configuring vendor Commo device driver.
579 Configuring generic vendor device driver.
580 Configuring HIPPI TCPIP network interface driver.
581 Configuring PD TCPIP.
582 Configuring a token ring data link control.
583 Configuring a ethernet data link control.
584 Configuring a IEEE ethernet data link control (802.3).
585 Configuring a SDLC MPQP data link control.
586 Configuring a QLLC X.25 data link control.
587 Configuring a NETBIOS.
588 Configuring a BSCRW (bisync read-write).
589 SCSI target mode device being configured.
590 Configuring diskless remote paging device.
591 Configuring LVM device driver (Logical Volume Manager).
592 Configuring HFT device driver (High Function Terminal).
593 Configuring SNA device drivers.
594 Configuring Asynchronous I/O
595 Configuring X.31 pseudo device (X.25 over ISDN).
596 Configuring SNA DLC/LAPE device.
597 Configuring OCS (Outboard Communication Server).
598 Configuring OCS hosts during system reboot.
599 Configuring FDDI data link control.
5c0 Streams-based hardware drive being configured.
5c1 Streams-based X.25 protocol stack being configured.
5c2 Streams-based X.25 COMIO emulator driver being configured.
5c3 Streams-based X.25 TCP/IP interface driver being configured.
5c4 FCS adapter device being configured.
5c5 SCB network device driver for FCS is being configured.
5c6 AIX SNA channel being configured.
600 Starting network boot portion of /sbin/rc.boot
602 Configuring network parent devices.
603 /usr/lib/methods/(defsys,cfgsys, or cfgbus) failed.
604 Configuring physical network boot device.
605 Configuration of physical network boot device failed.
606 Running /usr/sbin/ifconfig on logical network boot device.
607 /usr/sbin/ifconfig failed.
608 Attempting to retrieve the client.info file with tftp. Note that a
flashing 608 indicates multiple attempt(s) to retrieve the client_info
file are occurring.
609 The client.info file does not exist or it is zero length. Verify that
the client can tftp files from the server and that the client.info
file has the proper permissions.
60c Configuring a 1.4 GB IDE disk drive.
610 Attempting remote mount of NFS system.
611 Remote mount of NFS system failed. Verify that the server is correctly
exporting the client file systems. Verify that the client.info file
contains valid entries for exported file systems and server.
612 Accessing remote files; unconfiguring network boot device.
614 Configuring local paging devices.
615 Configuration of local paging device failed.
616 Converting from diskless to dataless configuration.
617 Diskless to dataless configuration failed.
618 Configuring remote (NFS) paging devices.
619 Configuration of remote (NFS) paging device failed.
61c Configuring a 2.1 GB IDE disk drive.
620 Updating special device files and ODM in permanent filesystem
with data from boot RAM filesystem
622 Boot process configuring for operating system installation.
625 Explanation Creating a directory for local NIM mount points.
System Action Creating a directory in a SPOT that is being used to
boot a NIM client over the network.
User Action If the attempt to create the directory fails, check
the client's info file in /tftpboot on the NIM master, and verify
that the NIM_MOUNTS variable does not contain any local mount point
paths that would cause a failure when attempting to create a
directory with this path in the SPOT.
62c Configuring a 3.0 GB IDE disk drive.
63c Configuring an IDE CD ROM drive.
650 IBM SCSI disk drive drive being configured.
If the LED persists, then this most likely indicates the drive is
failing to spin up and return the full VPD data. Under normal
operations, this LED should only be seen once, just after the disk has
been configured for the first time. If the drive is functioning
correctly, AIX will use the LED value specified in the drive's VPD for
subsequent reconfigurations. If repeated IPLs or reconfigurations
continue to show this LED for a SCSI disk, there is a problem with
the disk drive.
689 Configuring a 4.5 GB Ultra-SCSI SE disk drive. The configuration
method for the SCSI Differential disk drive is being run
690 Configuring a 9.1 GB Ultra-SCSI SE disk drive. The configuration
method for the SCSI Differential disk drive is being run.
691 Configuring a Turboways 25 Mbps ATM PCI adapter.
692 Configuring a DLT-7000 drive.
693 Configuring an ISDN PCI Basic Rate adapter.
694 Configuring an ISDN MCA Basic Rate adapter.
695 Configuring an X.25 PCI Coprocessor adapter
696 Configuring a single mode 8 MB PCI ATM adapter.
697 Configuring a multi mode 1 MB PCI ATM adapter.
698 Configuring a UTP 1 MB PCI ATM adapter.
699 Configuring a 10/100 Mbs PCI Ethernet adapter.
6c8 Configuring a display device driver.
700 1.1 GB 8-bit SCSI disk drive being identified/configured.
701 1.1 GB 16-bit SCSI disk drive being identified/configured.
702 1.0 GB 16-bit DE SCSI disk drive being identified/configured.
703 2.2 GB 8-bit SCSI disk drive being identified/configured.
704 2.2 GB 16-bit SCSI disk drive being identified/configured.
705 2.2 GB 16-bit DE SCSI disk drive being identified/configured.
706 4.5 GB 16-bit SCSI disk drive being identified/configured.
707 4.5 GB 16-bit DE SCSI disk drive being identified/configured.
708 A L2 cache is being identified/configured.
710 POWER GXT150M graphics adapter being identified/configured.
711 Unknown adapter being identified/configured.
712 Special graphics slot (SGA graphics slot) identified/configured.
713 IBM ARTIC960 device is being identified/configured.
714 A video capture adapter is being identified/configured.
715 Ultimedia Services audio adapter is being identified/configured.
716 System memory is being configured.
717 The Ethernet High-Performance LAN adapter is being configured.
718 A GXT500/GXT500D display adapter is being configured.
720 Unknown Read/Write optical drive being identified/configured.
721 Unknown Disk or SCSI device being identified/configured.
722 Unknown Disk being identified/configured.
723 Unknown CDROM or SCSI device driver being identified/configured.
724 Unknown Tape being identified/configured.
725 Unknown Display being identified/configured.
726 Unknown Input device being identified/configured.
727 Unknown Async device being identified/configured.
728 Parallel Printer being identified/configured.
729 Unknown Parallel device being identified/configured.
730 Unknown diskette drive type being identified/configured.
731 PTY being identified/configured.
732 Unknown SCSI Initiator type is being configured
733 7 GB 8mm tape drive being identified/configured.
734 4x SCSI-2 640MB CD-ROM Drive
735 A 540 MB SCSI disk drive is being configured.
736 A PS/2 keyboard is being configured.
741 1080MB SCSI Disk Drive
742 A PCI Ethernet device driver is being identified or configured.
743 An IsoFDD adapter is being identified or configured.
744 A Power Management chip is being configured.
745 16GB 4mm Tape Auto Loader is being configured.
746 A PCI Fast/Wide SCSI I/O adapter or a PCI Fast/Wide differential SCSI
I/O adapter is being configured.
748 An MCA/CHRP systems keyboard/mouse adapter being configured
749 7331 model 205 tape library is being configured.
74c An ISA bus Token Ring adapter is being configured.
750 A PCI Auto LANstreamer Token Ring adapter is being configured.
754 1.1GB 16-bit fast/wide SCSI SE disk drive being configured
755 2.2GB 16-bit fast/wide SCSI SE disk drive being configured
756 4.5GB 16-bit fast/wide SCSI SE disk drive being configured
757 External 13GB 1.5M/s 1/4 inch tape drive being configured
758 A 540 MB SCSI drive is being configured.
759 A 1080 MB SCSI disk is being configured.
75c An ISA bus Ethernet adapter is being configured.
760 The SCSI adapter function of the LSA card is being configured.
761 The Ethernet adapter function of the LSA card is being configured.
762 The configuration method is running for the TB3 adapter card
772 4.5GB SCSI SE Fast/Wide Disk Drive is being identified/configured.
773 9.1GB SCSI SE Fast/Wide Disk Drive is being identified/configured.
774 A 9.1 GB SCSI Differential disk drive is being configured.
775 An MVP PCI power graphics adapter is being configured.
779 A 3D PCI graphics adapter is being configured.
77c 1.0 GB 16-bit SE SCSI disk drive being identified/configured.
780 An X.25 Interface co-processor adapter, ISA bus is being configured.
781 A 4-port multiprotocol communications controller, ISA bus is being
configured.
782 A 1.2 GB hardfile is being configured.
783 4mm DDS-2 Tape Autoloader is being configured.
784 A 2160 MB SCSI disk drive is being configured.
785 An ISA 8-port EIA 232/RS 422 adapter is being configured.
786 A GXT250P/GXT255P graphic adapter is being configured.
787 A GXT500P/GXT550P graphics adapter is being configured.
788 An Ultimedia video capture adapter is being configured.
789 A 2.6GB External Optical Drive is being configured.
790 A multi-bus integrated Ethernet adapter is being configured.
791 A 2.2 GB SCSI disk drive is being configured.
792 A 4.5 GB SCSI disk drive is being configured.
793 A 9.1 GB SCSI disk drive is being configured.
794 A 10/100 Mbps Ethernet PX MCA device driver is being identified or
configured.
795 A SysKonnect PCI FDDI adapter is being configured.
796 A SysKonnect MCA FDDI adapter is being configured.
797 Turboways 155 UTP/STP ATM Adapter being identified or configured
798 Video streamer being identified or configured
799 A 2-port WAN adapter is being configured.
7c1 A business audio subsystem is being configured.
7c2 A 1.1 GB SCSI-2 disk drive is being configure
7c4 A 2.2 GB SCSI-2 disk drive is being configured.
7c6 A 4.4 GB SCSI-2 disk drive is being configured.
800 Turboways 155 MMF ATM Adapter being identified or configured
803 The 7336 Tape Library robotics is being configured.
804 An 8X CD ROM drive is being configured.
806 A GXT800 graphics adapter is being configured.
807 A SCSI enclosure is being configured.
808 System Interface Full (SIF) configuration.
80c SSA 4-Port Adapter being identified or configured
811 Processor Complex being identified/configured or standard input/output
being configured.
812 - Common Standard Adapter Logic being identified/configured.
- System Memory being identified/configured.
813 - Battery for Time-of-Day, NVRAM, etc. being identified/configured.
- System I/O Control Logic being identified/configured.
814 NVRAM being identified/configured.
815 Floating Point Processor being identified/configured.
816 Operator Panel Logic being identified/configured.
817 Time of Day Logic being identified/configured.
818 Used by DA to report checkstop / machine checks
819 Graphics Input Device adapter being identified/configured.
81c The Power Suite graphics adapter is being identified or configured.
820 Interprocessor related testing.
821 Standard Keyboard adapter being identified/configured.
823 Standard Mouse adapter being identified/configured.
824 Standard Tablet adapter being identified/configured.
825 Standard Speaker adapter being identified/configured.
826 Serial Port 1 adapter being identified/configured.
827 Parallel port adapter being identified/configured.
828 Standard Diskette adapter being identified/configured.
829 Multimode fiber 1 MB PCI ATM adapter is being configured.
82c The Power Wave graphics adapter is being identified or configured.
830 8-port asynch adapter, EIA-232, ISA bus is being configured.
831 - 3151 adapter being identified/configured.
- Serial Port 2 being identified/configured.
834 64-Port Async Controller being identified/configured.
835 16-Port Async Concentrator being identified/configured.
836 128-Port Async Controller being identified/configured.
837 16-Port Remote Async Node (EIA-232) being identified/configured.
838 - Bitternut Ethernet adapter being identified/configured.
- Network Terminal Accelerator adapter is being identified/configured.
839 - Bitternut Connection Station being identified/configured.
- 7318 Serial Communications Server being configured.
83c SP2 high performance switch (HPS) adapter is being identified or
configured in the SP2 node
83u The configuration method is running for the TB2 adapter card.
840 A PCI Ultra/Wide SCSI adapter is being configured.
841 8-Port Async adapter (EIA-232) being identified/configured.
842 8-Port Async adapter (EIA-422A) being identified/configured.
843 8-Port Async adapter (MIL-STD 188) being identified/configured.
844 7135 Raid array controller being identified/configured. (Allthorn)
845 7135 Raid array being identified/configured. (Allthorn)
846 RADiant Array SCSI 1.3GB Disk Drive being identified/configured.
847 16-Port async Serial adapter (EIA-232) being identified/configured.
848 16-Port async Serial adapter (EIA-422) being identified/configured.
849 X.25 Communications adapter being identified/configured.
850 Token-Ring Network adapter being identified/configured.
851 - Sandpiper V-A being identified/configured.
- T1/J1 Portmaster adapter is being identified or configured.
852 Ethernet adapter being identified/configured.
853 SCSI DE I/O adapter being identified/configured.
854 3270 Connection being identified/configured.
855 4-Port Multiprotocol Controller being identified/configured.
856 A POWER RADian device driver is being configured.
857 F-serial link adapter (FSLA) being identified/configured.
858 5085/86/88 adapter being identified/configured.
859 FDDI adapter being identified/configured.
85c Token-Ring High-Performance LAN adapter is being identified/configured.
860 Twin Tailed (Harrier) adapter being identified/configured.
861 Serial Optical Channel converter being identified/configured.
862 - Block Multiplexer Channel adapter being identified/configured.
- 370 Parallel Channel adapter being identified/configured.
863 MAP adapter being identified/configured.
864 Serial Channel adapter being identified/configured.
865 ESCON or 370 Serial Channel adapter being identified/configured.
866 SCSI adapter being identified/configured.
867 Async Expansion adapter being identified/configured.
868 Integrated SCSI adapter being identified/configured. (Spock)
869 SCSI adapter being identified/configured.
870 - Serial Disk adapter being identified/configured.
- Harrier 2 adapter being identified/configured.
871 Graphics Subsystem adapter being identified/configured.
872 Grayscale Graphics adapter being identified/configured.
873 Skyway 16 Graphics adapter being identified/configured.
874 Color Graphics adapter being identified/configured.
875 - Skyway 256 Graphics adapter being identified/configured.
- Vendor generic communication adapter being configured.
876 8-Bit Color Graphics Processor being identified/configured.
877 - Power Gt3/Gt4 being identified/configured.
- LEGA Display adapter being identified/configured.
878 - Pedernales Graphics adapter being identified/configured.
- The POWER Gt4 graphics process card is being identified/configured.
879 24-bit Color Graphics Processor being identified/configured.
880 - 7011/220 Graphics adapter being identified/configured. (SGA)
- The POWER Gt1 graphics adapter is being identified or configured.
881 Channel Attached printer being identified/configured.
882 Serial Attached printer being identified/configured.
883 Pegasus Support / SCSI-2 disk drive support (Japan)
884 3117 Scanner adapter being identified/configured.
885 3118 Scanner adapter being identified/configured.
886 3119 Scanner adapter being identified/configured.
887 Integrated Ethernet adapter being identified/configured.
888 (flashing) unexpected halt. FATAL
889 - SCSI adapter being identified/configured.
- LACE SCSI DE adapter being identified/configured.
890 The SCSI-2 Fast/Wide Adapter/A or SCSI-2 Differential Fast/Wide
Adapter/A is being identified or configured. (Corvette)
891 Vendor SCSI adapter being identified/configured.
892 Vendor Display adapter being identified/configured.
893 Vendor LAN adapter being identified/configured.
894 Vendor Async/Communications adapter being identified/configured.
895 Vendor IEEE 488 adapter being identified/configured.
896 Vendor VME buss adapter being identified/configured.
897 - HATSCON 370 channel adapter being identified/configured.
- System/370 Channel Emulator/A adapter being identified/configured.
898 POWER Gt1x graphics adapter being identified/configured. (White Oak)
899 - 3490 attached tape drive (Model C11/C22) being identified/configured.
- YUMA/CALVA attachment adapter being identified/configured.
89c A Multimedia SCSI CD-ROM is being identified/configured.
8c0 Coral chip IDE ports are being configured.
8c2 An IDE CD ROM XA 2x is being configured.
8c3 A 270 MB IDE disk drive is being configured.
8c4 A 360 MB IDE disk drive is being configured.
8c5 A 540 MB IDE disk drive being configured.
8c6 A 720 MB IDE disk drive is being configured.
8c7 A 1 GB IDE disk drive is being configured.
8cc A WDC AC1270OF 270 MB IDE disk drive is being configured.
900 - Attempting to boot from tape but mksysb missing after /bootrec
- A POWER GXT110P graphics adapter is being configured.
901 Vendor SCSI device being identified/configured.
902 Vendor Display being identified/configured.
903 Vendor Async device being identified/configured.
904 Vendor Parallel device being identified/configured.
905 Vendor other device being identified/configured.
906 IBM Premier Speech Recognition adapter I being identified/configured.
907 IBM Premier Speech Recognition adapter II being identified/configured.
908 POWER GXT1000 Graphics subsystem being identified/configured. (Ruby)
909 A SCSI-2 Disk Drive LAN SCSI/adapter (LSA) is being configured.(Pegasus)
90c A DALA-3420 420 MB IDE disk is being configured.
910 A 1/4 GB Fibre Channel/266 Standard adapter is being identified or
configured.
911 A Fibre Channel/1063 adapter short wave is being configured.
912 2.0 GB SCSI DE drive being identified/configured. (Allicat)
913 1.0 GB SCSI 2E DE drive being identified/configured. (Corsair)
914 56bit 8mm DE tape drive being identified/configured. (Snobird)
915 4 GB 4mm tape drive being identified/configured. (Sonata-2)
916 Non-SCSI vendor tape drive adapter being identified/configured.
917 2 GB wide 16 bit DE SCSI disk drive is being identified/configured.
918 2 GB wide 16 bit SE SCSI disk drive is being identified/configured.
919 A multimedia audio adapter is being identified or configured.
91c A 4mm 2 GB tape drive is being configured.
920 Bridge Box being identified/configured.
921 101 key Keyboard being identified/configured.
922 102 key Keyboard being identified/configured.
923 Kanji Keyboard being identified/configured.
924 Two-Button Mouse being identified/configured.
925 Three-Button Mouse being identified/configured.
926 Tablet 5083 Model 21 being identified/configured.
927 Tablet 5083 Model 22 being identified/configured.
928 Standard Speaker being identified/configured.
929 Dials being identified/configured.
92c A DALA-3540 540 MB IDE disk is being configured.
930 Lighted programmable function keyboard (LPFK) is being identified
or configured.
931 - IP Router being identified/configured.
- 5086 Keyboard being identified/configured.
932 IP Router being identified/configured.
933 Async Planar being identified/configured.
934 Async Expansion Drawer being identified/configured.
935 1.44 MB 3.5-Inch diskette drive being identified/configured.
936 1.2 MB 5.25-Inch diskette drive being identified/configured.
937 HIPPI adapter being identified/configured.
938 122 Keyboard being identified/configured.
939 Tablet for 6 button cursor being identified/configured.
93c A DPEA-30540 540 MB IDE disk is being configured.
940 Used by memory DA
941 6180 plotter being identified/configured.
942 Power GXT 100 graphics adapter being identified/configured. (Baby Blue)
943 Progress indicator: 3480 and 3490 control units attached to a
System/370 Channel Emulator/A adapter are identified or configured.
944 100MB ATM adapter being configured
945 1GB SCSI 16bit differential disk drive being identified or configured.
946 Serial port 3 adapter is being identified or configured.
947 Progress indicator. A 730MB SCSI disk drive is being configured.
948 Portable disk drive being identified/configured.
949 Unknown direct bus-attached device being identified/configured.
94c A WDC AC2540H 540 MB IDE disk is being configured.
950 Unknown SCSI Options being identified/configured.
951 670 MB SCSI disk drive being identified/configured.
952 355 MB SCSI disk drive being identified/configured.
953 320 MB SCSI disk drive being identified/configured.
954 400 MB SCSI disk drive being identified/configured.
955 857 MB SCSI disk drive being identified/configured.
956 670 MB SCSI disk drive electronics card being identified/configured.
957 - Direct Bus Attached disk drive being identified/configured.
- 120 MB Bus Attached disk drive being identified/configured.
958 160 MB Bus Attached disk drive being identified/configured.
959 160 MB SCSI disk drive being identified/configured.
95c A WDC AC2700H 730 MB IDE disk is being configured.
960 1.37 GB SCSI disk drive being identified/configured. (Wannamingo
961 Route 66 - 2 Port Serial adapter being identified/configured.
962 Route 66 - Ethernet adapter being identified/configured.
963 SCSI Scanner (2456) adapter being identified/configured.
965 Route 66 - Token Ring adapter being identified/configured.
967 An Xpoint Ethernet adapter is being configured.
968 - 1.0 GB SCSI disk drive being identified/configured. (Corsair)
- 160 MB disk drive being identified/configured.
96c A DPEA-30810 810 MB IDE disk is being configured.
970 0.5-Inch 9-Track tape drive being identified/configured.
971 150 MB 0.25-Inch tape drive being identified/configured.
972 2.3 GB 8mm SCSI tape drive being identified/configured.
973 Other SCSI tape drive being identified/configured.
974 CDROM drive being identified/configured.
975 ERIMO R/W Optical drive being identified/configured.
976 RISC System 6000 SCSI I/O Controller Initiator
977 - M-Audio capture and playback adapter being identified/configured.
- ACPA adapter being identified/configured.
978 IEEE 488 adapter being identified/configured.
979 7246 SBS Frame Buffer adapter being identified/configured.
97c A DPEA-301080 1080 MB IDE disk drive is being configured.
980 - ISDN Basic adapter being identified/configured. (Athens/Pegasus)
- TBO-IBM Switching Network Interface adapter being identified/
configured.
981 - ISDN Primary adapter being identified/configured. (Athens/Sparta)
- 540 MB SCSI-2 disk drive being identified/configured. (AKAGI / UTE)
982 Graphics Visulation Server adapter being identified/configured .
983 XGA graphics adapter being identified/configured .
984 - ISDN port being identified/configured.
- SPITFIRE SCSI disk drive 1GB being identified/configured.
985 M-Video adapter being identified/configured. (VCA)
986 1.2GB SCSI disk drive (in 2.4GB disk unit) is being identified or
configured. (Wildcat)
987 Enhanced SCSI CD-ROM XA being identified/configured. (Atlantis MM)
988 KILLY FDDI adapter being identified/configured.
989 200 MB SCSI disk drive being identified/configured. (KAI)
98c A WDC AC31000H 2083 IDE disk drive is being identifed or configured.
990 - 5 GB 8mm SCSI tape drive being identified/configured.
- 2.0B SCSI-2 SE disk drive being identified/configured. (Allicat)
991 525 MB 1/4" SCSI tape drive being identified/configured. (Tundra)
992 4755 Crytographic adapter being identified/configured.
993 Raven File Server product being identified/configured.
994 5 GB 8mm SCSI tape drive being identified/configured. (Snobird / 990)
995 - 1/4" tape drive being identified/configured.
- 1.2 GB 1/2" SCSI tape drive being identified/configured.
(Polar/Tundra 2)
996 - 1.0 GB SCSI Tape drive being identified/configured.
- Progress indicator. Single-port, multi-protocol communication
adapter is being identified/configured.
997 FDDI adapter being identified/configured. (Foxtroft / twisted pair)
998 4mm tape drive being identified/configured. (Suite / HP)
999 - Compression adapter being identified/configured. (Ohio)
- 7137 or 3514 Disk Array subsystem being identified/configured.
99c A 2 GB SCSI disk drive is being configured.
99u The netinstall process for this node has completed.
c00 AIX Install / Maintenance loaded successfully
c01 Insert the first diagnostics or AIX Install/Maintenance diskette.
c02 Wrong diskette sequence used. REBOOT !!!
c03 The wrong diskette is in the diskette drive.
c04 The loading stopped with an irrecoverable error.
c05 A diskette error occured.
c06 The rc.boot configuration script is unable to determine type of boot.
c07 Insert the next diskette.
c08 RAM file system started incorrectly.
c09 The diskette drive is reading or writing a diskette.
c10 Platform-specific bootinfo command not in boot image.
c20 Low Level Debugger activated. An unexpected system halt has
occurred, and you have configured the system to activate the low
level debugger instead of doing a dump.
ACTION:
You can run debugger commands, including requesting a dump. When
you exit the debugger, the LED code will change, find the new LED
code in this list.
c21 The ifconfig command was unable to configure the network for the
client network host to boot.
c22 The tftp command was unable to read the client's ClientHostName.info
file during a client network boot.
c23 NFS qfsinstall failed for client network boot.
c24 Unable to read the client's ClientHostName.info file during client
network boot.
c25 Client did not mount miniroot during network install.
c26 Client did not mount the /usr file system during network boot.
c27 - Attempting to boot from device other than tok(0-3) or ent(0-3).
- The boot device returned from the bootinfo -b command is not valid.
c28 The system is unable to set the attributes of the network device.
c29 The system was unable to configure the network device.
c31 If no console has been configured, the system halts with this
value in the three-digit-display and the system displays
instructions for choosing a console on the native display.
System initialization and configuration will continue after
you choose a console.
If you are starting the system in SERVICE mode and the system
does not have a display or the display is not working and you
are unable to choose a console, system initialization and
configuration will complete without a console configured if you
turn the keyswitch to the NORMAL position.
c32 The console is a high function terminal (HFT). (Informational only)
c33 The console is a TTY. (Informational only)
c34 The console is a file. (Informational only)
c40 Configuration files are being restored. Extracting data files from
media. This LED displays briefly on the panel.
c41 Could not determine the boot type or device.
c42 Extracting data from diskette.
c43 Could not access the boot or installation tape.
c44 Initializing installation database with target disk information.
c45 Cannot configure the console.
c46 Normal installation processing.
c47 Could not create a physical volume identifier (PVID) on disk.
c48 Prompting you for input.
c49 Could not create or form the JFS log.
c50 Creating root volume group on target disks.
c51 No paging devices were found.
c52 Changing from RAM enviroment to disk enviroment.
c53 Not enough space in the /tmp directory to do a preservsation install.
c54 Installing either BOS or additional packages.
c55 Could not remove the specified logical volume in a preservation install.
c56 Running user-defined customization.
c57 Failure to restore BOS.
c58 Displaying message to turn the key.
c59 Could not copy either device special files, device ODM, or
volume group information from RAM to disk.
c61 Failed to create the boot image.
c70 Problem Mounting diagnostics CDROM disk in standalone mode.
c99 Diagnostics have completed. This code is only used when there
is no console.
EEE (hex 14 14 14) reserved for FAA to do a reset to control pqnel
This displays as a big E with the top bar missing
u00 Problem
Meaning: Invalid bootp_response specified in install_info file.
Action: Issue setup_server on the boot server and reboot the node.
u01 Information
Meaning: Getting the boot information
u02 Information
Meaning: Configuring the boot network
u03 Problem
Meaning: tftp of /tftpboot/.install_info file from the
boot/install server failed.
Action: Check to see if the install_info file exists on the
boot/install server. Issue setup_server if it does not
exist. If it exists, see Chapter 15, "Diagnosing Boot
Problems".
u04 Information
Meaning: Expanding .install_info file variables for use in
rc.boot
u05 Problem
Meaning: tftp of /usr/lpp/ssp/install/backup/config.bff file
failed.
Action: Check to see if the config.bff file is on the boot/install
server. If it exists, see Chapter 15, "Diagnosing Boot
Problems".
u06 Information
Meaning: Starting to setup the display
u07 Information
Meaning: Exiting phase 1 network boot.
u20 Problem
Meaning: tftp of the /usr/lpp/ssp/install/backup/dispdskt.bff file
failed.
Action: Check to see if the dispdskt.bff file is on the
boot/install server. If it exists, see Chapter 15,
"Diagnosing Boot Problems".
u21 Information
Meaning: Reconfiguring the network
u22 Information
Meaning: Replacing the default network boot ODM cfgrules
u23 Information
Meaning: Issuing config manager (cfgmgr)
u24 Information
Meaning: Reconfiguring the network
u25 Information
Meaning: Issuing config manager again (cfgmgr)
u26 Information
Meaning: Configuring the console (cfgcon)
u30 Problem
Meaning: tftp of the
/usr/lpp/ssp/install/backup/instmaint.diskette file
failed.
Action: Check to see if the instmaint.diskette file is on the
boot/install server. If it exists, see Chapter 15,
"Diagnosing Boot Problems".
u31 Information
Meaning: Restoring the files in the instmaint.diskette backup
file.
u32 Information
Meaning: Configuring tape drives, if any.
u33 Problem
Meaning: Invoking mk_autoinst_files to create the files necessary
to proceed with the automatic netinstall. Possible
corruption of the /usr/lpp/ssp/install/bin/config.bff
file.
Action: Issue restore -Tvf /usr/lpp/ssp/install/backup/config.bff
on the boot/install server to see if the mk_autoinst_files
file is in the backup file, config.bff. If it exists
then, the data in the /tftpboot/.install_info file
must be corrupted. Issue setup_server on the boot/install
server and reboot the the node.
u34 Information
Meaning: Exiting prepare_auto_install routine
u50 Information
Meaning: Beginning rc.boot phase 2 - get the boot information and
expand the install_info variables.
u51 Information
Meaning: The node has been recognized as a uni-processor, and
bos.rte.up is about to be installed.
u52 Information
Meaning: The node has been recognized as a high node, bos.rte.mp
is about to be installed.
u53 Information
Meaning: Installing the ssp.ha feature on the node.
u54 Information/Problem
Problem: u54 is issued when the installation process invokes the
AIX netinstall program bosmain to perform the install of
the AIX image. If this LED remains for an extended
period, there are two possible causes.
The first possibility is that the setup_server script
could not determine the size of the image when it created
the /tftpboot/node.install_info file. In this file, the
netinst_bosobj_size variable contains the size of the
image. Login to the boot/install server for this node and
examine this file to see if the variable contains a
number. If it does not contain a number, the installation
is continuing, but we are unable to determine the
installation percentage and u54 will be displayed until
the installation is complete.
The second possibility is that the variable is a number
and the installation has stopped because of problems with
the boot/install server.
Actions: If the netinst_bosobj_size variable was not a number,
either wait for the amount of time that it takes your
image to install (image installation times depend on the
size of the image) to see if it completes, or rerun
setup_server on the boot/install server and verify that
the netinst_bosobj_size variable was set properly prior to
Network booting the node.
If the netinst_bosobj_size was a number, refer to Chapter
14, "Diagnosing Install Problems".
u55 Problem
Problem: bosboot failed when creating a bootable image on a high
node.
Actions: Because bosboot failed, the bootable image was not
written to the IPL device, and the node cannot be booted
in its present state. The node must be installed again.
Possible causes of the boot failure are:
The lppsource directory is not properly exported on
the boot/install server.
NFS is not running on the boot/install server.
bos.rte.mp is not found in the lppsource directory on
the boot/install server.
u56 Problem
Meaning: If the node is a /usr client, the /usr filesystem is
mounted here. Possible problems with the mount.
Action: Check to see if the /usr filesystem is exported properly
on the /usr server. The server and client addresses that
are being used are documented in the boot servers
/tftpboot/.install_info file (usr_server_ip and
usr_client_ip variables). Verify that the server has
exported the /usr filesystem to the client. Also verify
that the nfs daemons: mountd, rpc.lockd, and rpc.statd are
running on the server. The TCP/IP inetd and portmap
daemons must be running as well.
If you find that required daemons are not running, restart
the daemons on the server. Reboot the node to reinstall
the system.
If you find that the lan the node is attempting to mount
over is not the intended or expected interface, issue
splstdata -u to list data /usr client information and
splstdata -b to list data boot server information to
determine the boot/install server and /usr server
structure that is currently defined.
The spbootins command or the SMIT interface on the control
workstation may be used to redefine this structure. Once
the new definition is complete, reinstall the node.
u57 Information
Meaning: Restoring the .config_info file.
u59 Information
Meaning: Configuring the node using the config_node script.
u60 Information
Meaning: Creating the files /etc/ssp/server_name,
/etc/ssp/server_hostname, /etc/ssp/reliable_hostname, and
/etc/ssp/cw_name.
u61 Problem
Meaning: tftp of the /etc/SDR_dest_info file from the boot/install
server has failed. The tftp may fail if the
/etc/SDR_dest_info file does not exist on the boot/install
server or the permissions do not have read access for all.
Action: Check to see if the /etc/SDR_dest_info file is on the
boot/install server. If it exists, see Chapter 15,
"Diagnosing Boot Problems".
u62 Information
Meaning: Creating the /etc/firstboot file. rc.boot tftp's the
/usr/lpp/ssp/install/config/script.cust file from the
boot/install server and executes it. This led comes from
the beginning of this file.
u63 Problem
Meaning: tftp of the /usr/lpp/ssp/install/config/script.cust file
from the boot/install server has failed. The tftp may
fail if the script.cust file does not exist on the
boot/install server or the permissions do not allow read
access for all. For /usr clients, the u63 may indicate a
portmap or NFS failure on the /usr server.
Action: Check whether the script.cust file is on the boot/install
server. If it exists, see Chapter 15, "Diagnosing Boot
Problems". For /usr clients, verify that NFS and portmap
resources are running on the /usr server. If not running,
they can be started with startsrc -g nfs and startsrc -g
portmap. Once NFS and the portmapper are running, the
nodes hung at u63 need to have the install restarted. The
easiest way is to do a network boot.
u64 Problem
Meaning: tftp of /usr/lpp/ssp/install/config/rc.boot.config from
the boot/install server, and execution of rc.boot.config,
failed. The tftp may fail if the rc.boot.config file does
not exist or the permissions do not allow read access for
all.
Action: Check to see if the rc.boot.config file is on the
boot/install server. If it exists, see Chapter 15,
"Diagnosing Boot Problems".
u65 Information
Meaning: The install/customize/maintenance has been completed and
the node is rebooting by issuing shutdown -Fr.
Action: You may open a console to check on the node or reboot the
node.
u66 Information
Meaning: Setting clock on node
u67 Information
Meaning: Copying kerberos configuration file (/etc/krb.conf) from
boot-server
u68 Information
Meaning: Copying kerberos realms file (/etc/krb.realms) from
boot-server
u69 Information
Meaning: Copying kerberos server key file (/etc/krb_srvtab) from
boot-server
u70 Information
Meaning: Beginning of rc.boot setup.
u71 Information
Meaning: Start of boot process for a network boot.
u72 Information
Meaning: Beginning of initialization for rc.boot.
u73 Information
Meaning: Copying ksrvutil program
(/usr/lpp/ssp/kerberos/bin/ksrvutil) from boot-server
u74 Information
Meaning: Executing ksrvutil program
(/usr/lpp/ssp/kerberos/bin/ksrvutil) to change server keys
u75 Information
Meaning: Copying rcmdtgt program (/usr/lpp/ssp/rcmd/bin/rcmdtgt)
from boot-server
u76 Information
Meaning: Copying rsh (kshell client) program
(/usr/lpp/ssp/rcmd/bin/rsh) from boot-server
u77 Information
Meaning: Executing rcmdtgt program (/usr/lpp/ssp/rcmd/bin/rcmdtgt)
to get kerberos ticket
u78 Information
Meaning: Executing rsh to complete node processing on boot-server
u79 Information
Meaning: tftp of the files /tftpboot/script.cust and
tftpboot/tuning.cust from the NIM Master.
u80 Information
Meaning: Installing the ssp.clients feature on the node.
u81 Information
Meaning: Installing the ssp.basic feature on the node.
u82 Information
Meaning: Installing the ssp.sysctl feature on the node.
u83 Information
Meaning: Installing the ssp.sysman feature on the node.
u84 Information
Meaning: Installing the ssp.css feature on the node.
u85 Information
Meaning: Installing the ssp.jm feature on the boot/install server.
u86 Information
Meaning: Creating the /etc/firstboot file on the node and running
the /tftpboot/tuning.cust script.
u87 Information
Meaning: Running the /tftpboot/script.cust script on the node.
u88 Problem
Meaning: rc.boot has determined that the bootp_response for the
node being installed is set to disk. The
/tftpboot/.install_info file (on the boot/install
server) has the bootp_response field that was used by
rc.boot. The /etc/bootptab file has this node enabled for
a network boot. This is an invalid combination. The
valid network bootp responses are install, customize, and
maintenance.
Action: To check the bootp response issue splstdata -b on the
control workstation. If this does not show disk as the
bootp response, then issue setup_server on the
boot/install server and reboot the node.
After running setup_server you can check the /etc/bootptab
file to see if the node in question is commented out (the
line with this node has a # in the first character).
u89 Problem
Meaning: The /usr client adapter field (usr_client_adapter) has an
invalid value in it. The usr_client_adapter supported
fields are Ethernet and Token Ring.
Action: Issue splstdata -u to determine the current value
specified for the /usr client adapter that is selected.
Use the spbootins command or the SMIT interface on the
control workstation may be used to redefine this value and
reboot the node.
u90 Information
Meaning: Use the bootinfo command to get the boot information and
initialize variable for rc.boot
u91 Information
Meaning: Gathering of boot information is complete.
u92 Information
Meaning: Determining the boot network information.
u93 Information
Meaning: Issuing ifconfig for the boot network.
u94 Information
Meaning: The /usr client network is not the boot network. Issuing
ifconfig to configure the network to mount /usr.
u95 Information
Meaning: Boot network configuration is complete
u98 Information
Meaning: Starting bosmain for maintenance option.
u99 Problem
Meaning: Invalid bootp_response specified in install_info file.
Action: Issue setup_server on the boot/install server and reboot
the node.
888 The system has halted
---- LED.TXT 10/27/97 author: Mandar Mirashi. mandar@hpserv.pok.ibm.com -----