RS/6000 3-Digit Display Codes
The following data was shamelessly stolen from the AIXTOOLS conferencing
disk. It was the LED.TXT file from the LEDMON PACKAGE.
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 According to this Toronto web page, 0c1 means
"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.
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.
104 BIST could not find the CBA.
105 BIST could not read from the OCS EPROM.
106 | BIST detected a module failure. CBA not found in S&S area
111 | BIST detected a module failure. (Press button for details)
112 Checkstop occurred during BIST and checkstop results could not be
logged out.
113 The BIST checkstop count was greater than 1. (=3)
120 BIST started CRC check on 875X EPROM
121 BIST detected a bad CRC on the OCS EPROM.
122 BIST started CRC check on the OCS EPROM.
123 BIST detected a bad CRC on the OCS NVRAM.
124 BIST started CRC check on the OCS NVRAM space.
125 BIST detected a bad CRC on the time of day NVRAM.
126 BIST started CRC check on the time of day NVRAM.
127 BIST detected a bad CRC on the 8752 EPROM
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.
144 BIST Failed.
151 BIST started AIPGM test code (array initialization 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.
164 BIST encountered an error while reading low NVRAM.
165 BIST encountered an error while writing low NVRAM.
166 BIST encountered an error while reading high NVRAM.
167 BIST encountered an error while writing high NVRAM.
168 BIST encountered an error while reading the SIO (Serial I/O) register.
169 BIST encountered an error while writing the SIO (Serial I/O) register.
180 BIST logout failed or logout complete (displayed for 1 minute).
185 Checkstop occurred during BIST, 10 sec to hook up ESP before logout.
186 |
187 BIST was unable to identify the chip release level in the
checkstop logout data.
195 BIST logout completed.
*********************************************************************
* POST POST POST POST POST POST POST POST POST POST POST *
*********************************************************************
200 You tried to boot the system with the Mode Switch in the SECURE position
201 Checkstop occurred during IPL. FATAL
202 Machine_check_handler 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
209 Reserved_900_handler FATAL
209 RSC2 POST - same LED value as Reserved_900_hdlr
20C | RS2 L2 Cache detected
210 SVC_1000_handler FATAL
211 IPL ROM CRC miscompare during IPL FATAL
212 Processor Planar Bad FATAL
212 RAMPOST Memory Configuration Reisters failure FATAL
213 Memory Card failure or Processor Planar Bad FATAL
213 RAMPOST full/hfwd & byte Load & Store failure FATAL
214 Power status register failed FATAL
214 RAMPOST PIO Load and Store circuitry failure FATAL
215 A low voltage condition is present FATAL
215 RAMPOST ECC Generation circuitry failure FATAL
216 RAMPOST ECC Correction circuitry failure FATAL
216 IPL ROM code being uncompressed into memory
217 RAMPOST Bit Steering Logic failure FATAL
217 End of Bootlist - same LED as Bit Steer Logic Fail
218 RAM POST testing for 1 MB of good memory
218 RAMPOST 1 Meg of good memory not found, address/remap fail FATAL
219 RAMPOST bit_map_generation FATAL
21C | RS2 L2 Cache post completed
/* Normal mode Default path selection from NVRAM IPL Device List
220 ROM scan selected for ipl
220 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.
222 Native I/O selected for ipl
223 SCSI devices selected for ipl
224 SLA selected for ipl
225 SJL or DBA (esdi hardfile) selected for ipl
226 Ethernet selected for ipl
227 Token Ring selected for ipl
228 expansion code selected for ipl
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 FDDI selected for ipl
/* Normal mode Default path selection from ROM IPL Device List
230 ROM scan selected for ipl
231 Ethernet chosen from menus
232 Native I/O selected for ipl
233 SCSI devices selected for ipl
234 SLA selected for ipl
234 9333 subsystem device selected for ipl
235 SJL or DBA (esdi hardfile) selected for ipl
236 Ethernet selected for ipl
237 Token Ring selected for ipl
238 Token Ring selected for ipl from menus
239 Menu selected device (Ethernet or Token Ring) failed to boot.
23C FDDI selected for ipl
/* Service mode Default path selection from NVRAM IPL Device List
240 ROM scan selected for ipl
241 devices specified in NVRAM IPL Devices List
242 Native I/O selected for ipl
243 SCSI devices selected for ipl
244 SLA selected for ipl
244 9333 subsystem device selected for ipl
245 SJL or DBA (esdi hardfile) selected for ipl
246 Ethernet selected for ipl
247 Token Ring selected for ipl
248 expansion code selected for ipl
249 a service mode device list is present but has no entries (null
list) or none of the valid entries succeeded in ipl
24C FDDI selected for ipl
ACTION: See action for error code 229
/* Service mode Default path selection from ROM IPL Device List
250 ROM scan selected for ipl
251 Ethernet chosen from menus
252 Native I/O selected for ipl
253 SCSI devices selected for ipl
254 SLA selected for ipl
254 9333 subsystem device selected for ipl
255 SJL or DBA (esdi hardfile) selected for ipl
256 Ethernet selected for ipl
257 Token Ring selected for ipl
258 Token Ring selected for ipl from menus
259 FDDI selected for ipl from menus
25C FDDI selected for ipl
260 Attempting Network IPL, menus and information present on screen
260 call to the user interface
260 NVRAM not initialized with bootlist, keyboard type and language
type even though keyboard / display or tty connected to system
261 Attempting Network IPL, menus, no console display detected
261 Console handlers request led value
261 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
262 Console handlers request led value
263 Attempting Normal mode system restart from Family 2 feature ROM
specified in the NVRAM boot device list
270 |
271 Mouse and mouse port POST
272 Tablet port POST
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
284 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 POST in progress
287 | Adapter card slots being queried
288 Microchannel POST in progress
288 Family 2 bus scan
289 Diskette POST
290 IO Planar Bad
290 IOCC POST
291 NIO POST being executed
292 SCSI POST being executed
293 SJL or Bus Attached Internal Hard File POST being executed
294 SLA POST
295 XX3 POST (Ethernet)
296 XX2 POST (Tokenring)
296 ROM scan POST
297 XX1 POST
297 System model number could not be determined.
297 | System model number does not compare between OCS and ROS FATAL
| Attempting a software IPL
298 Attempting warm IPL
299 IPL ROS has completed loading and has passed control to
passed control to the loaded code
301 | Flash Utility ROM test failed or checkstop occurred. FATAL
302 | Flash Utility ROM User prompt, move key to Service position.
303 | Flash Utility ROM User prompt, press Reset button.
304 | Flash Utility ROM IOCC POST error. FATAL
305 | Flash Utility ROM standard I/O POST running.
306 | Flash Utility ROM is attempting IPL from Flash Update media device.
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 config error or no memory found FATAL
313 | Flash Utility ROM RAM POST failure. FATAL
314 | Flash Utility ROM Power status register failed. FATAL
315 | Flash Utility ROM detected a low voltage condition.
318 | Flash Utility ROM RAM POST is looking for 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.
324 | CRC error on new Flash Image after Update was performed.
325 | Flash Update successful and complete.
*********************************************************************
* LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST LPOST *
*********************************************************************
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.
520 bus configuration running.
521 /etc/init invoked cfgmgr with invalid options, /etc/init
has been corrupted or incorrectly modified. FATAL
521 The /etc/inittab file has been incorrectly modified or corrupted.
522 The configuration manager has been invoked with conflicting
options. FATAL
522 The /etc/inittab file has been incorrectly modified or corrupted.
523 The configuration manager is unable to access the ODM data base. FATAL
523 The /etc/objrepos file is missing or inaccessible.
524 The configuration manager is unable to access the config
rules object in the ODM data base. FATAL
524 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
525 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
526 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
527 The /sbir/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
528 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 program 'savebase' returned an error.
531 The configuration manager is unable to access the PdAt object
class. FATAL
531 The /usr/lib/objrepos/PdAt file is missing or inacessable.
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.
533 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 data base lock. FATAL
535 HIPPI diagnostic interface being configured.
536 The configuration manager encountered more than one sequence
rule specified in the same phase. FATAL
536 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.
537 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.
549 Not documented, but a call to the Support Center one day informed
me that it meant that AIX has prompted the console and is waiting
for an answer to the question, "What should be done with the
system dump?" Evidently, AIX had previously crashed and there is
not enough room in the default directory AIX is suppose to copy
the dump to (normally /var/adm/ras), and is asking you if you
want to copy it to diskette (ha-ha!) or tape, if one's attached,
or to discard it.
551 IPL Varyon of the root volume group is running.
552 IPL Varyon of the root volume group failed.
553 IPL Phase 1 is complete. (/etc/(un)mount missing or / or /tmp full
553 The /etc/inittab file has been incorrectly modified or corrupted.
554 Unable to define NFS swap device during network boot.
555 Unable to create NFS swap device during network boot.
555 ODM error when trying to varyon rootvg
556 Unable to configure NFS swap device during network boot.
556 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.
570 Configuring virtual SCSI devices.
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.
581 Configuring 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.
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 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.
609 | The client.info file does not exist or it is zero length.
610 | Attempting remote mount of NFS system.
611 | Remote mount of NFS system failed.
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.
620 | Updating special device files and ODM in permanent filesystem
| with data from RAM filesystem
622 | Boot process configuring for operating system installation.
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.
720 Unknown Read/Write optical drive being identified/configured.
721 Unknown Disk being identified/configured.
721 Unknown SCSI device being identified/configured.
722 Unknown Disk being identified/configured.
723 Unknown CDROM 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
733 | 7 GB 8mm tape drive being identified/configured.
77C | 1.0 GB 16-bit SCSI disk drive being identified/configured.
80C Configuring Serial Raid drives (evidently RAJ)
811 Processor Complex being identified/configured.
812 Common Standard Adapter Logic being identified/configured.
812 Memory being identified/configured.
813 Battery for Time-of-Day, NVRAM, etc. being identified/configured.
813 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.
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.
831 3151 adapter being identified/configured.
831 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 128-Port Remote Async Node (EIA-232) being identified/configured.
838 Bitternut Ethernet adapter being identified/configured.
839 Bitternut Connection Station being identified/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)
847 16-Port Serial adapter (EIA-232) being identified/configured.
848 16-Port 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.
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.
857 FSLA adapter 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.
862 370 Parallel Channel adapter being identified/configured.
863 MAP adapter being identified/configured.
864 Serial Channel adapter being identified/configured.
865 370 Serial Channel adapter being identified/configured.
866 SCSI adapter being identified/configured.
867 Async Expansion adapter being identified/configured.
868 SCSI adapter being identified/configured. (Spock)
869 SCSI adapter being identified/configured.
870 Serial Disk adapter being identified/configured.
870 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.
876 8-Bit Color Graphics Processor being identified/configured.
877 Power Gt3/Gt4 being identified/configured.
877 LEGA Display adapter being identified/configured.
878 Pedernales Graphics adapter being identified/configured.
879 24-bit Color Graphics Processor being identified/configured.
880 7011/220 Graphics adapter being identified/configured. (SGA)
881 Channel Attached printer being identified/configured.
882 Serial Attached printer being identified/configured.
883 Pegasus 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.
889 LACE SCSI DE adapter being identified/configured.
890 | Fast/Wide (Diff) SCSI adapter being identified/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.
898 | POWER Gt1x graphics adapter being identified/configured. (White Oak)
899 | 3490 attached tape drive being identified/configured.
899 YUMA/CALVA attachment adapter being identified/configured.
89C | A Multimedia SCSI CD-ROM is being identified/configured.
900 ??? Attempting to boot from tape but mksysb missing after /bootrec
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 PEGASUS LSA (LAN SCSI) adapter being identified/configured.
910 FCS 1/4 speed adapter being identified/configured.
911 FCS full speed adapter being identified/configured.
912 | 2.0 GB DE drive being identified/configured. (Allicat)
913 | 1.0 GB 2E DE drive being identified/configured. (Corsair)
914 | 5 GB 8mm DE tape drive being identified/configured. (Snobird)
915 | 4 GB tape drive being identified/configured. (Sonata-2)
916 | Non-SCSI vendor tape drive being identified/configured.
917 | 2 GB wide DE SCSI disk drive is being identified/configured.
918 | 2 GB wide DE SCSI disk drive is being identified/configured.
920 Bridge Box being identified/configured.
921 Keyboard 101 being identified/configured.
922 Keyboard 102 being identified/configured.
923 Keyboard Kanji 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.
930 Lighted Program Function Keys (LPFK) keyboard being
931 IP Router being identified/configured.
931 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.
(delete)940 7372 plotter being identified/configured.
940 Used by memory DA
941 6180 plotter being identified/configured.
(delete)942 6184 plotter being identified/configured.
942 | Power GXT 100 graphics adapter being identified/configured. (Baby Blue)
(delete)943 6186 plotter being identified/configured.
943 |
(delete)944 6180 plotter Model 11 being identified/configured.
(delete)945 5084 plotter Model 1 being identified/configured.
(delete)946 5084 plotter Model 2 being identified/configured.
(delete)947 5084 plotter Model 3 being identified/configured.
948 Portable disk drive being identified/configured.
949 Unknown direct buss-attached device being identified/configured.
950 Missing 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.
957 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.
960 1.37 GB SCSI disk drive being identified/configured. (Wannamingo
(delete)961 ASCII 14-Inch terminal being identified/configured.
961 Route 66 - 2 Port Serial adapter being identified/configured.
(delete)962 3161 terminal being identified/configured.
962 Route 66 - Ethernet adapter being identified/configured.
(delete)963 3163 terminal being identified/configured.
963 SCSI Scanner (2456) adapter being identified/configured.
965 Route 66 - Token Ring adapter being identified/configured.
968 1.0 GB SCSI disk drive being identified/configured. (Corsair)
968 160 MB disk drive being identified/configured.
970 .5-Inch 9-Track tape drive being identified/configured.
971 150 MB .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.
977 ACPA adapter being identified/configured.
978 IEEE 488 adapter being identified/configured.
979 7246 SBS Frame Buffer adapter being identified/configured.
(delete)980 4216 printer being identified/configured.
980 ISDN Basic adapter being identified/configured. (Athens/Pegasus)
980 IBM Switching Network Interface adapter being identified/configured.
(delete)981 3812 printer being identified/configured.
981 ISDN Primary adapter being identified/configured. (Athens/Sparta)
981 | 540 MB SCSI-2 disk drive being identified/configured. (AKAGI / UTE)
(delete)982 3852 printer being identified/configured.
982 Graphics Visualization Server adapter being identified/configured .
(delete)983 4201 printer being identified/configured.
983 XGA graphics adapter being identified/configured .
(delete)984 4202 printer being identified/configured.
984 ISDN port being identified/configured.
984 SPITFIRE SCSI disk drive 1GB being identified/configured.
(delete)985 4207 printer being identified/configured.
985 M-Video adapter being identified/configured. (VCA)
(delete)986 4208 printer being identified/configured.
986 2.4 GB SCSI disk drive being identified/configured. (Wildcat)
987 CD-ROM XA being identified/configured. (Atlantis MM)
988 KILLY FDDI adapter being identified/configured.
(delete)989 4224 printer being identified/configured.
989 200 MB SCSI disk drive being identified/configured. (KAI)
(delete)990 4234 printer being identified/configured.
990 5 GB 8mm SCSI tape drive being identified/configured.
990 | 2.0B SCSI-2 SE disk drive being identified/configured. (Allicat)
(delete)991 Tryon printer being identified/configured.
991 525 MB 1/4" SCSI tape drive being identified/configured. (Tundra)
(delete)992 5202 Printer being identified/configured.
992 4755 Crytographic adapter being identified/configured.
(delete)993 5204 Printer 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.
995 1.2 GB 1/4" SCSI tape drive being identified/configured.(Polar/Tundra 2)
996 1.0 GB SCSI Tape drive being identified/configured.
996 MP/A adapter being identified/configured.
996 | Progress indicator. Single-port, multi-protocol communication
adapter is being identified/configured.
997 FDDI adapter being identified/configured. (Foxtroft / twisted pair)
(delete)998 Chief printer being identified/configured.
998 4mm tape drive being identified/configured. (Suite / HP)
(delete)999 Raintree Printer being identified/configured.
999 Compression adapter being identified/configured. (Ohio)
999 | 7137 or 3514 Disk Array subsystem being identified/configured.
c00 AIX Install / Maintenance loaded correctly.
c01 Insert the first diagnostics 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 occurred.
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.
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).
c28 The system is unable to set the attributes of the network device.
c29 The system is 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 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.
c41 | Could not determine the boot type or device.
c42 | Extracting data from diskette.
c43 | Diagboot cannot be accessed.
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 environment to disk environment.
c53 | Not enough space in the /tmp directory to do a preservation 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.
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
-----------------------------------------------------------------------
SP1 - 9076 error codes from Al Dix in Harrisburg, PA.
-----------------------------------------------------------------------
unn | SP2-specific LED values (page 299 Admin guide SH26-2486)
u00 | Invalid bootp_response in install_info file
u01 | Getting boot information
u02 | Configuring the boot network
u03 | tftp of /tftpboot/.install_info from boot install serve r failed
u04 | Expanding .install_info variables for use in rc.boot
u05 | tftp of /usr/lpp/ssp/install/backup/config.bff file failed
u06 | Starting to setup the display
u07 | Exiting phase 1 network boot
u20 | tftp of /usr/lpp/ssp/install/backup/dispdskt.bff file failed
u21 | Reconfiguring the network
u22 | Replacing the default network boot ODM cfgrules
u23 | Issuing config manager (cfgmgr)
u24 | Reconfiguring the network
u25 | Issuing config manager again (cfgmgr)
u26 | Configuring the console (cfgcon)
u30 | tftp of /usr/lpp/ssp/install/backup/instmaint.diskette failed
u31 | Restoring files in instmaint.diskette backup file
u32 | Configuring tape drives, if any
u33 | Invoking mk_autoinst_files to proceed with automatic netinsta ll
| (possible corruption of /usr/lpp/ssp/install/bin/config.bff)
u34 | Exiting prepare_auto_install routine
u50 | Beginning rc.boot phase 2 (get boot info & expand install_in fo
u54 | bosmain has been invoked to perform the netinstall
u56 | if node is /usr client, /usr filesystem mounted here
u61 | tftp of /etc/SDR_dest_info from boot/install server failed
u62 | Creating the /etc/firstboot file
u63 | tftp of /usr/lpp/ssp/install/config/firstboot.ssp from server f ailed
u64 | tftp of /usr/lpp/ssp/install/config/rc.boot.config from server failed
u65 | install/customize/maint has completed now rebooting (shutdown - Fr)
u70 | Beginning of rc.boot setup
u71 | Start of boot process for a network boot
u72 | Beginning of initialization for rc.boot
u88 | rc.boot determined that bootp_response is set to disk (invalid)
u89 | /usr client field (usr_client_adapter) has an invalid value
u90 | Use bootinfo cmd to get boot info and initialize for rc.boot
u91 | Gathering of boot information is complete
u92 | Determining the boot network information
u93 | Issuing ifconfig for the boot network
u94 | /usr not boot network, issuing ifconfig to mount /usr
u95 | Boot network configuration is complete
u98 | Starting bosmain for maintenance option
u99 | Invalid bootp_response specified in install_info file
-----------------------------------------------------------------------
SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT_SYSTEM_HALT
-----------------------------------------------------------------------
888 The system has halted
A flashing 888 is displayed in the 3-Digit Display by the system to
indicate that there is a message to be displayed in the 3-Digit Display.
You will use the RESET button to display the message which is encoded as
a string of 3-Digit Display codes. (Pressing the RESET button under
these circumstances WILL NOT IPL the system).
Turn the Mode Switch to the NORMAL position or the SERVICE position and
press the RESET button to display the first code in the string, record
this code in the space provided on the Problem Summary Form and then
press the RESET button again to display the next code. Continue
displaying and recording codes in this manner until flashing 888 is
displayed again. You may display the error information again if
necessary.
The first code following the 888 indicates what type of information is
contained in the remainder of the string. Find this code in the
following table:
-----------------------------------------------------------------------
New Release 4 Power On Self Test (POST) notes
CODE Description
102 - a system crash message is being displayed.
103 - a diagnostic message is being displayed. This is the number that
should be used when reporting a problem.
104 - a manufacturing message is being displayed.
105 - a encoded diagnostic message is being displayed.
-----------------------------------------------------------------------
CODE TYPE OF MESSAGE
---- -----------------------------------------------------
102 Unexpected System Halt during normal operation.
System Crash Codes
For unexpected system halts the string of 3-Digit Display codes
has the following format:
888 102 mmm ddd
Where mmm is a code indicating the cause of the halt and ddd is a
code indicating whether a system dump was obtained.
The following table lists possible values for 'mmm' and their
causes. If the system halts with one of the following values in
the 3-Digit Display, perform the hardware problem determination
procedures in the IBM RIOS Diagnostics Programs Operators Guide.
If the hardware problem determination procedures return an SRN,
record that SRN on item 4 of the Problem Summary Form. If
hardware problem determination procedures do not return an SRN,
record SRN 101-mmm on item 4 of the Problem Summary Form. Report
the problem to your service organization. If a dump was
obtained, copy the dump to removable media and be prepared to
make it available to your service organization.
mmm cause of halt
--- ---------------------------------
000 Unexpected system interrupt.
200 Machine check due to Memory Bus Error (RAS/CAS Parity)
201 Machine check due to Memory Timeout.
202 Machine check due to Memory Card Failure.
203 Machine check due to Address Exception (Address out of range).
204 Machine check due to Attempted Store into ROS.
205 Machine check due to Uncorrectable ECC due to Address Parity.
206 Machine check due to Uncorrectable ECC.
207 Machine check due to Undefined Error.
| 208 Machine check due to an L2 Uncorrectable ECC.
300 Data Storage Interrupt - Processor Type.
32x Data Storage Interrupt - I/O Exception - IOCC. The
number represented by 'x' is the BUID.
38x Data Storage Interrupt - I/O Exception - SLA.
The number represented by 'x' is the BUID.
400 Instruction Storage Interrupt.
500 External Interrupt - Scrub - Memory Bus Error (RAS/CAS Parity)
501 External Interrupt - Undefined Error
51x External Interrupt - DMA - Memory Bus Error (RAS/CAS Parity)
52x External Interrupt - IOCC Type - Channel Check.
53x External Interrupt - IOCC Type - Bus Timeout.
54x External Interrupt - IOCC Type - Keyboard External.
The number represented by 'x' is the IOCC number.
558 There is not enough memory available to continue the IPL.
700 Program Interrupt
800 Floating Point Unavailable.
The following table lists possible values for 'ddd'.
ddd dump status
--- ---------------------------------
0c0 User requested dump completed successfully.
0c2 User requested dump started.
0c3 The dump is inhibited.
0c4 The dump did not complete. A partial dump may be present.
0c5 The dump program could not access the dump device.
0c6 User Requested Dump to the secondary dump device requested.
0c7 Reserved.
0c8 The dump function is disabled, no primary dump device configured
0c9 A dump is in process.
c20 Low Level Debugger started.
103 Diagnostic Message
Diagnostic messages are displayed in the 3-Digit Display
in the following circumstances:
When a failure is detected that prevents the completion
of IPL.
When the console display is not present or it is
unavailable because of a display or adapter failure.
The string of 3-Digit Display codes identifies the SRN (Service
Request Number) and up to four FRUs (Field Replaceable Units).
The string of 3-Digit Display codes has the following format:
888 103 sss rrr c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx c02 1yy ...
sss rrr is the Service Request Number, record this number on
item 4 of the Problem Summary Form.
A B | C D | E F | G H Eight-digit location code
c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx First FRU location code
c02 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx Second FRU location code
c03 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx Third FRU location code
c04 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx Fourth FRU location code
if a ccx (x is between 2 and 9) then the next display code(s)
following are the differences from the previous c01 ... code.
c01 100 200 300 401 500 601 700 800 cc2 602 ... ...
is the same as
c01 100 200 300 401 500 601 700 800
c02 100 200 300 401 500 602 700 800
...
where the above xx locations correspond to
xx - value xx - value xx - value xx - value
00 = 0 11 = A 21 = K 31 = U
01 = 1 12 = B 22 = L 32 = V
02 = 2 13 = C 23 = M 33 = W
03 = 3 14 = D 24 = N 34 = X
04 = 4 15 = E 25 = O 35 = Y
05 = 5 16 = F 26 = P 36 = Z
06 = 6 17 = G 27 = Q
07 = 7 18 = H 28 = R
08 = 8 19 = I 29 = S
09 = 9 20 = J 30 = T
Location code format for non-SCSI devices
AB - CD - EF - GH
|| | | |
|| | | +- Async port number or FRU location on a card or
|| | | planar.
|| | |
|| | +------ Connector number on an adapter or planar.
|| |
|| +----------- Slot number of the adapter, memory card, or
|| adapter for an identified device.
||
|+--------------- Always 0 on workstations. Drawer ID or slot
| number of the adapter that drives the drawer
| in a rack-type system.
+---------------- Always 0
Location code format for SCSI devices
AB - CD - EF - GH
| || | ||
| || | |+ Always 0
| || | |
| || | +- SCSI address of the device. See Service
| || | Guide for physical location of device.
| || |
| || +------ Always 00
| ||
| |+---------- Slot number of the SCSI controller. For IBM
| | 7012 Direct Buss Attached Disk, 7 denotes rear
| | drive location and 8 denotes front location.
| +----------- Always 0
|
+---------------- Always 00
Location code format for IBM 9333 High Performance Disk Drive Subsystems
AB - CD - EF - GH
|| || || ||
|| || || |+ Compartment number 0 through 3
|| || || +- Always 0
|| || ||
|| || |+----- Adapter connector 0 through 3
|| || +------ Always 0
|| ||
|| |+---------- Adapter slot 1 through 8 in CPU drawer or system unit.
| || +----------- System I/O bus identifier
||
| |+--------------- Always 0
| +---------------- System unit identifier
Location code table
Pair Value Description
AB 00 Workstation-type unit
00 CPU drawer in a rack-type system unit
00 SCSI device drawer in a rack-type system unit
00 SCSI disk drawer in a rack-type system unit
01 Async expansion adapter in slot 1 of CPU drawer
02 Async expansion adapter in slot 2 of CPU drawer
03 Async expansion adapter in slot 3 of CPU drawer
04 Async expansion adapter in slot 4 of CPU drawer
05 Async expansion adapter in slot 5 of CPU drawer
06 Async expansion adapter in slot 6 of CPU drawer
07 Async expansion adapter in slot 7 of CPU drawer
08 This is invalid. Slot 8 should contain SCSI adapter.
CD 00 CPU planar
00 Standard I/O planar
00 A device attached to the standard I/O planar
01 Adapter in slot 1 of the I/O planar
02 Adapter in slot 2 of the I/O planar
03 Adapter in slot 3 of the I/O planar
04 Adapter in slot 4 of the I/O planar
05 Adapter in slot 5 of the I/O planar
06 Adapter in slot 6 of the I/O planar
07 Adapter in slot 7 of the I/O planar
08 Adapter in slot 8 of the I/O planar
07 Read Direct Buss Attached Disk Drive (IBM 7012)
08 Front Direct Buss Attached Disk Drive (IBM 7012)
0A Memory card in slot A on the CPU planar
0B Memory card in slot B on the CPU planar
0C Memory card in slot C on the CPU planar
0D Memory card in slot D on the CPU planar
0E Memory card in slot E on the CPU planar
0F Memory card in slot F on the CPU planar
0G Memory card in slot G on the CPU planar
0H Memory card in slot H on the CPU planar
| 0J Graphics adapter slot
| 0J TCW SIMM socket
| 0K TCW SIMM socket
| 10 Second I/O planar
| 11 Adapter in slot 1 of the second I/O planar
| 12 Adapter in slot 2 of the second I/O planar
| 13 Adapter in slot 3 of the second I/O planar
| 14 Adapter in slot 4 of the second I/O planar
| 15 Adapter in slot 5 of the second I/O planar
| 16 Adapter in slot 6 of the second I/O planar
| 17 Adapter in slot 7 of the second I/O planar
| 18 Adapter in slot 8 of the second I/O planar
AA Serial Optic Converter in slot AA of system/CPU planar
AB Serial Optic Converter in slot AB of system/CPU planar
EF 00 Does not have a connector or software was not
able to identify the connector number
01 The number of the connector on an adapter card,
through 04 distribution box, or planar
0D Internal diskette connector on the std. I/O planar
| 0E Built-in Ethernet adapter
0K Keyboard connector on the std. I/O planar
0M Mouse connector on the std. I/O planar
0P Parallel printer connector on the std. I/O planar
0T Tablet connector on the std. I/O planar
S1 Serial port 1 connector on the std. I/O planar
S2 Serial port 2 connector on the std. I/O planar
| 11 Remote async node 1 on line 1
| 12 Remote async node 2 on line 1
| 13 Remote async node 3 on line 1
| 14 Remote async node 4 on line 1
1A Port A of the Serial Optic Converter in slot AA of the CPU
1B Port B of the Serial Optic Converter in slot AA of the CPU
| 21 Remote async node 1 on line 2
| 22 Remote async node 2 on line 2
| 23 Remote async node 3 on line 2
| 24 Remote async node 4 on line 2
2A Port A of the Serial Optic Converter in slot AB of the CPU
2B Port B of the Serial Optic Converter in slot AB of the CPU
GH 00 For devices other than those listed here
00 Port addresses for 8 port async, 16 port async,
through 15 and 16 port concentrator boxes
01 Diskette drive 1 attached to standard I/O planar
02 Diskette drive 2 attached to standard I/O planar
01 Memmory SIMM in location 1 on memory card
02 Memmory SIMM in location 2 on memory card
03 Memmory SIMM in location 3 on memory card
04 Memmory SIMM in location 4 on memory card
05 Memmory SIMM in location 5 on memory card
06 Memmory SIMM in location 6 on memory card
07 Memmory SIMM in location 7 on memory card
08 Memmory SIMM in location 8 on memory card
00 SCSI device set to address 0
10 SCSI device set to address 1
20 SCSI device set to address 2
30 SCSI device set to address 3
40 SCSI device set to address 4
50 SCSI device set to address 5
60 SCSI device set to address 6
| 0A Video RAM in slot A of the graphics adapter
| 0B Video RAM in slot B of the graphics adapter
| 0C Video RAM in slot C of the graphics adapter
| 0D Video RAM in slot D of the graphics adapter
| 0E Video RAM in slot E of the graphics adapter
| 0F Video RAM in slot F of the graphics adapter
| 0G Video RAM in slot G of the graphics adapter
| 0H Video RAM in slot H of the graphics adapter
| 0J Video RAM in slot J of the graphics adapter
| 0K Video RAM in slot K of the graphics adapter
-----------------------------------------------------------------------
New Release 4 Location Identification Information
RISC/6000 product family is a family of systems that consists of a rack
configuration, a tower configuration, and a table-top configuration...
External boxes, rack drawers, portable files, etc. can be attached to
the system. FRUs can be located in any of these units. To locate a FRU
the CE needs to know the following information:
* For rack the following are needed:
- rack
- drawer
- slot if adapter, memory card, or SLA
- I/O planar
- physical location if a device such as a hard file or diskette
- location on card for memory simms.
* For a tower and table-top the following are needed:
- slot if adapter, memory card, or SLA
- physical location if a device such as a hard file or diskette
- location on card for memory simms.
* For external boxes and devices the following are needed:
- external box or device
- slot if adapter
- physical location if a device such as a hard file or diskette
Software can identify the following location information:
* the system type
* adapter slot
* I/O planar
* memory slot
* SLA slot
* SCSI Address
* The adapter an external device or external box is attached to.
Software can NOT identify the following location information:
* rack
* drawer
* SCSI device's physical location
* Diskette Drive physical location
The Location Code is defined as:
AB-CD-EF-GH
For planars, cards, and non-SCSI devices
the Location Code is defined as:
AB - CD - EF - GH
| || | |
| || | Device/FRU/Port ID
| || |
| || Connector ID
| ||
| |Slot ID
| Channel/Bus
|
Drawer ID
where:
* AB is the Drawer ID
It is used to identify CPU and Async Drawers.
For CPU Drawers and non-rack systems AB is 00.
For Async Drawers, A identifies the Channel/Bus (I/O Planar) and B
identifies the Slot ID of the Async Adapter that attaches to the drawer.
This corresponds to the CD value of the Async Adapter Location Code.
* CD is the Channel/Bus and Slot ID.
It is used to identify the location of an adapter, memory card, or SLA
- For CPU Cards that attach to the system bus, C will be equal to 0. D
will identify the slot ID. D will be equal to the slot letter. Slots
should be numbered starting with the letter P.
- For microchannel adapters, C identifies the Channel/Bus (I/O Planar)
and D identifies the Slot ID. For systems with 2 planars, C is equal
to 0 for the first I/O Planar and 1 for the second I/O Planar.
- For GIO and SIO adapters that attach to the system bus, C identifies
the Channel/Bis and D identifies the slot ID. C will be equal to A
for the first GIO bus, B for the second GIO bus etc. D will be equal
to the slot number. Slots should be numbered starting with 1.
- For integrated adapters, C identifies the planar and D is 0.
- For memory, C (Channel/Bus) is equal to 0 and D is equal to the slot
number (A to H) for cards on non-Salmon systems and SIMMs on Salmon
systems (220).
- For devices, CD is equal to the CD value of the adapter which the
device attaches too.
- For a SLA card, C identifies the Channel/Bus (1) and D identifies
the slot (A or B).
* EF is the Connector ID.
It is used to identify the adapter connector that a resource is attached
too.
If the external connectors are not labeled, then they should be numbered
from 1 to n starting at the top of the card. The top of the card is
defined as the side opposite the connector that plugs into the bus.
Some examples of connectors are:
- The 64 port connectors should be 01 to 04.
- The GIO connectors should be 01 and 02.
- The 8 port and 16 port connector should be 01.
- S1 and S2 should be used for the NIO Serial connectors.
- 0P should be used for the NIO parallel connector.
- 0K should be used for the NIO keyboard connector.
- 0M should be used for the NIO mouse connector.
- 0T should be used for the NIO tablet connector.
- 0D should be used for the NIO diskette connector.
- The SLA connectors should be 01 and 02.
* GH is the Port/Device/FRU ID
It is used to identify a port, device, or a FRU. GH has several meanings
depending upon the resource type. They are:
- For memory cards GH defines a memory SIMM.
Values for GH are 1, 2...or 16.
- For caches GH defines the cache. Values are 1,2...or 16.
- For PCMIAs GH defines the PCMIA. Values are 1,2...or 16.
- For async devices GH defines the port on the fanout box.
Values are 00 to 15.
- For a diskette drive H defines which diskette drive 1 or 2. G is
always 0.
- For all other devices GH is equal to 00.
For SCSI devices (including Harrier disks) the Location Code is defined as:
AB - CD - EF - GH
| || | ||
| || | |Logical Unit Address of SCSI Device
| || | Control Unit Address of SCSI Device
| || |
| || Connector ID
| ||
| |Slot ID of SCSI Controller or Serial Disk Adapter
| Channel/Bus of SCSI Controller or Serial Disk Adapter
|
Drawer ID of SCSI Controller
where:
* AB is the Drawer ID that contains the adapter.
AB is always equal to 00 at release 1 and 2.
* C is the Channel/Bus (I/O Planar) for the adapter and D is the Slot ID
for the adapter. If the SCSI Controller is integrated, then CD is 00.
* EF is the Connector ID that the Device is attached too.
* CD-EF can be used as the Drawer ID.
* G defines the Control Unit address of the device.
* H defines the Logical Unit address of the device.
SCSI device drawers should be labeled with the CD-EF value of the device
location code.
Some examples of Location Codes are:
* A CPU drawer is:
00
* An async drawer attached to the async adapter in slot 1 of the first
I/O Planar is:
01
The drawer should be labeled 01.
* An async drawer attached to the async adapter in slot 4 of the second
I/O Planar is:
14
The drawer should be labeled 14.
* A TTY device attached to port 13 of a fanout box attached to the second
connector of a 64 port card in slot 5 of an async drawer attached to the
async adapter in slot 3 of the second I/O Planar is:
13-05-02-13
The TTY device should be labeled 13-05-02-13.
* A TTY device attached to port 5 of a fanout box attached to an 8-port
card in slot 6 of a deskside system is:
00-06-01-05
* A fanout box attached to second connector of a 64 port card in slot 8
of an async drawer attached to the async adapter in slot 3 of the first
I/O Planar is:
03-08-02
The fanout box should be labeled 03-08-02.
* A 64 port card in slot 5 of an async drawer attached to the async adapter
in slot 7 of the second I/O Planar is:
17-05
* An internal SCSI device attached to SCSI adapter in slot 2 of a desktop
system with a Control Unit Address of 3 and a Logical Unit address of 1 is:
00-02-00-31
The device should be labeled 00-02-00-31.
* An external SCSI device in a drawer attached to SCSI adapter in slot 2 of
the second I/O Planar with a Control Unit Address of 3 and a Logical
Unit address of 1 is:
00-12-00-31
The drawer should be labeled 00-12-00-31.
* An external SCSI device in a drawer attached to SCSI adapter in slot 2
of the second I/O Planar with a Control Unit Address of 3 and a Logical
Unit address of 1 is:
00-12-00-31
The drawer should be labeled 00-12-00-31.
* An external device in a drawer attached to the third port of a Serial
Disk Adapter in slot 6 of the second I/O Planar with a Control Unit
Address of 3 and a Logical Unit address of 1 is:
00-16-02-31
The drawer should be labeled 16-02.
* The first diskette drive attached to the NIO is
00-00-0D-01
* The second diskette drive attached to the NIO is
00-00-0D-02
* The keyboard attached to the NIO is
00-00-0K
* A display attached to the display adapter in slot 2 of the CPU drawer is:
00-02-01
* The fourth memory SIMM on the memory card in slot D of the CPU is
00-0D-00-04
-----------------------------------------------------------------------
New Release 2 and Release 3 '105' error codes
105 Diagnostic Message
Diagnostic messages are displayed in the 3-Digit Display
in the following circumstances:
888 105 1xx 2xx 3xx 4xx ==> encoded SRN (Service Request Number)
c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx c02 1yy ... (failure(s))
The 105 error codes are decoded using the 103 xx location
translate table from the previous section.
The c01 ..., c02 ..., error codes are decoded the same as 103
codes
note that the main difference between 103 and 105 errors are that
105 errors are encoded SRN's and 103 errors are not.
888 103 sss rrr ==> SRN
c01 1xx 2xx 3xx 4xx 5xx 6xx 7xx 8xx c02 1yy ... (failure(s))
-----------------------------------------------------------------------
New Release 2 and Release 3 '103' error codes for SRN's
The new service request numbers are of the form 120 000 to 129 999
displayed as 12x xyy. Where xx provides 100 numbers to uniquely identify
the planar type and yy provides 100 numbers to uniquely identify the test
that failed.
For the definition of xx, please refer MODEL ID definitions. xx will
identify a failing CPU planar or a failing IO planar. If it is not clear
which planar is causing the problem, the OCS will identify the FRU with
the highest probability of causing the known error.
The definition of xx is as follows:
(also available using the AIX command "uname -m | cut -c7-8"
Product/Model Model ID
Number
(System) (xx)
| 7011/220 (Salmon) 41
| 7011/22? (Cabeza) 45
7011/22G
7011/22W
7011/M20 43
| 7012/315 78
7012/320 31
7012/320H 35
7012/330 35 (possibly 16)
| 7012/340 37 (Stilwell 30ns)
| 7012/34? 39 (Stilwell 40ns)
7012/350 38
7012/350 or 355 77
7012/360 or 365 76
7012/370 or 375 75
| 7013/510 78
7013/520 30
| 7013/520H 34
7013/530 10
7013/530H 18
| 7013/540 14 (possibly 11)
7013/550 1C
| 7013/550H 5C
| 7013/550L 77
7013/560 5C
7013/570 67
7013/580 66
| 7015/930 20 (possibly 02)
| 7015/950(E) 2E
7015/970(/B) 63
7015/980(/B) 64
| 7016/720 or 730 10 (same as a 7013/530)
| 7018/740 or 741 30
| Gomez 30ns 9xx 60
| Gomez 16ns 9xx 61
| Gomez 24ns 9xx 62
| Desktop IO 9xx 85
| Rack IO 9xx 86
| Tower IO 9xx 87
| Desktop IO 9xx 88
| Porcupine 65
| AS400 Accelerator 50
The definition of yy is as follows:
yy FRU Description
60 I/O Missing EPOW connector
27 CPU Bad CRC on 87C51FC Eprom
23 I/O Bad CRC on OCS NVRAM space
25 I/O Bad CRC on the Time of Day (TOD) RAM
03 CPU Model ID not found
04 CPU COP Buss Address (CBA) not found
06 CPU COP Buss Address (CBA) not found in Seed / Signature area
11 CPU Fatal Built In Self Test (BIST) error
87 CPU Can't find DD level of chip in logout area
12 CPU Checkstop occurred, but can't logout state of machine
13 CPU 3 Checkstops have occurred
If a BIST error occurs, the SRN will be followed by a 'ccc 104'. The
'ccc' indicates that there is more information available, and the '104'
indicates that the information that follows relates to an OCS BIST failure.
Bist failures are indicated by the chip COP Buss Address followed by
the failure code. The format for each chip that fails BIST operation is
as follows:
xxx cyy... where xxx is the Cop Buss Address of the failing chip and yy
is the actual failure encountered. The 'c' has no meaning presently.
COP BUSS ADDRESSES (xxx):
The chips supported are:
DCU0 = 010 COMBO1 = 029 FPU = 001 SLA1 = 077
DCU1 = 042 COMBO2 = 061 FXPT = 002 SLA2 = 109
DCU2 = 074 IOCC1 = 093 ICU = 003
DCU3 = 106 IOCC2 = 125 SCU = 004
XIO1 = 205
XIO2 = 237
BIST FAILURES (cyy):
The following failures that can occur are:
0 No failure at all
1 DC Logic Self Test failed
2 AC logic self test failed
4 Array self test failed
8 The DD level could not be determined
16 The chip is not present or responding on the COP Buss
32 An equipment incompatibility exists between this chip and another
Any combination of these failures are possible and are displayed in
the decimal radix by the OCS as a BIST failure. For example, suppose
a chip passes AC Logic Self Test (ACLST) but failed Array Self Test
(AST), then the fail code displayed would be a 04. If the chip failed
both ACLST and AST, then the fail code would be 06.
EXAMPLES:
1) Error: Missing EPOW connector on 350
Sequence of numbers : 888 103 123 860 888 103 123 860 ...
2) Error: Bad CRC on Time of Day (TOD) RAM of Sacasil
Sequence of numbers : 888 103 128 625 888 103 128 625 ...
3) Error: BIST failures on Porcupine
ICU chip failed AST (003 c04)
FPU chip failed ACLST and DD level could not be determined
(001 c10)
DCU1 chip not responding on the COP Buss (042 c16)
Sequence of numbers : 888 103 126 511 ccc 104 003 c04 001 c10
042 c16 ... 888 ...
-----------------------------------------------------------------------
The new service request numbers are of the form 140 000 to 149 999
displayed as 14x xyy. Where xx provides 100 numbers to uniquely identify
the planar type and yy provides 100 numbers to uniquely identify the test
that failed.
For the definition of xx, please refer to section previous titled
"New Release 2 and Release 3 '103' error codes for SRN's"
The definition of yy is as follows:
Release 1 LED's Revised Flashing "888" LED's
211 888 103 14x x11 c01 100 200
212 888 103 14x x12 c01 100 200
214 888 103 14x x14 c01 100 200 300 400 c02 100 200
215 888 103 14x x15 c01 100 200 c02 100 200 300 400
290 888 103 14x x90 c01 100 200 c02 100 200 300 400
297 888 103 14x x97 c01 100 200
TCW SIMM FRU failure 888 103 14x x94 c01 100 200 300 420
-----------------------------------------------------------------------
INSTALL LED SEQUENCE -- AIX 3.2 -- Manufacturing Test
During the boot-up and installation of AIX during the manufacturing
test process, the 3-digit LED is used to indicate process status.
This guide explains what the LEDs indicate.
DISKETTE BOOT PROCESS
Boot off the diskette
:u: This LED indicates a catastrophic failure.
During diskette boot, it is probably indicative of a memory,
CPU, or I/O slot problem.
U3 This is indicative of an unknown or unexpected failure.
On early 340 models, it has been caused by
corruption of data during parallel port transfer.
*********************************************************************
U1 Running preconfiguration
01C - CFGMGR -f -d successful
02C - CFGMGR -f -d failure
This step sets up the database that AIX uses to keep track
of which devices are in the system.
010 - Swap out 1st boot diskette, insert 2nd boot diskette
0C0 - Wrong diskette inserted
C03 - Reading 2nd boot diskette
C04 - Setting up base devices
3C - ODMADD successful
4C - ODMADD failure
This step sets up the serial and parallel ports in the device
database.
5C - CFGMGR -s -d successful
6C - CFGMGR -s -d failure
This step runs the configuration manager so that the serial and
parallel ports runs as required.
7C - mkdev of tty0 successful
8C - mkdev of tty0 failed
This step sets up serial port #1.
9C - mkdev of tty1 successful
10C - mkdev of tty1 failed
This step sets up serial port #2. Serial port #2 is used to
communicate with the tester.
11C - MFGCONF successful
12C - MFGCONF failure
This step configures the parallel port for AIX download.
13C - SYSINFO.MFG file made successfully
14C - STSINFO.MFG file make failed
CCC - Attempt to send message 0 to the tester
Message 0 is a message from the system which says to the
tester, "Hey, I'm alive! What do you want me to do?".
C00 - Message 0 acknowledge received from tester
A C00 on the LED display indicates that the system received an
acknowledge from the tester.
C11 - Received message 11 from tester
A C11 means that the system received a message 11 from the
tester. This means that the tester is ready to send the AIX2
file to the system.
C01 - Attempt to send message 01 to tester
A C01 led means that the system is sending a message 01 to
the tester. Message 01 means "go ahead, send me that AIX
file".
C02 - Running the AIX install program
19C - Configuring hardfiles
20C - Cannot "find" any hardfiles
21C - MKROOTVG successful
22C - MKROOTVG failure
This step sets up the root logical volume. In other words,
the install code is setting up the initial subdirectories on
the primary hardfile.
23C - DELETELVS successful
24C - DELETELVS failure
This step cleans up the hardfiles in preparation for the
AIX load.
25C - CREATELVS successful
26C - CREATELVS failure
This step creates the logical volume system. In other works,
other subdirectories are being set up on one or more
hardfiles.
27C - POPLVS successful
28C - POPLVS failure
This step sets up the file system. In other words, set up
some parameters for the newly built subdirectories.
CCC - Attempt to send message 0 to the tester
Message 0 is a message from the system which says to the
tester, "Hey, I'm alive! What do you want me to do?".
C00 - Message 0 acknowledge received from tester
A C00 on the LED display indicates that the system received an
acknowledge from the tester.
C11 - Received message 11 from tester
A C11 means that the system received a message 11 from the
tester. This means that the tester is ready to send the AIX3
file to the system.
C01 - Attempt to send message 01 to tester
A C01 led means that the system is sending a message 01 to
the tester. Message 01 means "go ahead, send me that AIX
file".
C02 - Running the AIX install program
29C - MKBOOT successful
30C - MKBOOT failure
This step creates the section of code which will allow the
system to reboot off the hardfile after the yellow button is
pushed.
31C - DD wrote boot image to boot logical volume
32C - DD failure
This step writes the bootable section of code to the primary
hardfile.
33C - MKBOOT updated NORMAL IPL list successfully
34C - MKBOOT failed to update NORMAL IPL list
This step updates information on the primary hardfile
required for the hardfile reboot when the keylock is in
the normal position
35C - MKBOOT updated SERVICE IPL list successfully
36C - MKBOOT failed to update SERVICE IPL list
This step updates information on the primary hardfile
required for the reboot when the keylock is in
the service position
37C - BOOTLIST updated NORMAL NVRAM IPL list successfully
38C - BOOTLIST failed to update NORMAL NVRAM list
This step updates information in the NVRAM required for the
hardfile reboot when the keylock is in the normal position
39C - BOOTLIST updated SERVICE NVRAM IPL list successfully
40C - BOOTLIST failed to update SERVICE NVRAM list
This step updates information in the NVRAM required for the
hardfile reboot when the keylock is in the normal position
CCC - Attempt to send message 0 to the tester
Message 0 is a message from the system which says to the
tester, "Hey, I'm alive! What do you want me to do?".
C00 - Message 0 acknowledge received from tester
A C00 on the LED display indicates that the system received an
acknowledge from the tester.
C12 - Received message 12 from tester
A C12 means that the system received a message 12 from the
tester. This means that the tester is telling the system to
prepare for a reboot.
666 - Ready for reboot
HARDFILE BOOT PROCESS
Boot off the primary hardfile LY
Note: Many of these steps are identical to the diskette boot process
01C - ODMCREATE successful (Same as diskette boot)
02C - ODMCREATE failure (Same as diskette boot)
03C - ODMADD successful (Same as diskette boot)
04C - ODMADD failure (Same as diskette boot)
05C - CFGMGR -f -d successful (Same as diskette boot)
06C - CFGMGR -f -d failure (Same as diskette boot)
07C - Found the boot disk
08C - Can't find boot disk
09C - IMPORTVG successful Define the hardfile logical
10C - IMPORTVG failure characteristics to the LVM.
11C - VARYONVG successful "Turn on" the hardfile
12C - VARYONVG failure
13C - FSCK successful Check the file system
14C - FSCK failure
15C - ODMADD TTY successful Add the serial device to the
16C - ODMADD TTY failure device database.
17C - CFGMGR -s -d successful Configure the serial device
18C - CFGMGR -s -d failure
19C - CHGCONS tty0 successful Further configure the TTY device
20C - CHGCONS tty0 failure
21C - CFGCON successful More serial port
22C - CFGCON failure configuration
23C - MKDEV tty successful Create the TTY device
24C - MKDEV tty failure
25C - MFGCONF successful Configure other devices
26C - MFGCONF failure
33C - ODMDELETE successful Delete previous hardfile
34C - ODMDELETE failure information
31C - ODMADD scsidev successful Set up hardfiles
32C - ODMADD scsidev failure
======================================================================
This list was mainly stolen from numerous documents, modified to be
sequential, and added from personal notes. Many thanks to those
people that sent me soft and hard copies to collate into this one.
To the best of my knowledge, the information here is accurate
but not necessarily the latest, up to date version. This document
should be considered IBM Internal Use Only because of internal code
names and acronyms used.
Interesting manuals to have on hand:
SC23-2204-XX Problem Solving Guide
SA23-2631-XX Diagnostic Programs : Operator Guide
SA23-2632-XX Diagnostic Programs : Service Guide
SA23-2629-XX Service Request Number / Cross Reference / Ver 2.2
SA23-2643-XX Hardware Technical Reference / General Information
SA23-2646-XX Hardware Technical Reference / Options and Devices
Wally Tuten, TUTEN at AUSTIN
3.8.5 Location Identification