Display codes (LEDs)

This post provides descriptions for the numbers and characters that display on the operator panel and descriptions of the location codes used to identify a particular item. Information is available about the following codes:

AIX Location Codes

Note:

AIX logical location codes can still be seen and supported under various AIX commands and functions. However, the Diagnostic screens and menus display physical location codes for resources when running versions 5.2.0 and later. For these systems, refer to Physical Location Codes.

The basic formats of the AIX location codes are as follows:

For non-SCSI devices/drives:
```
AB-CD-EF-GH
```
For SCSI devices/drives:
```
AB-CD-EF-G,H
```

For planars, cards, and non-SCSI devices, the location code is defined as follows:

AB-CD-EF-GH
 |  |  |  |
 |  |  |  Device/FRU/Port ID
 |  |  Connector ID
 |  devfunc Number, Adapter Number or Physical Location
 Bus Type or PCI Parent Bus

The AB value identifies a bus type or PCI parent bus as assigned by the firmware.
The CD value identifies adapter number, adapter's devfunc number, or physical location. The devfunc number is defined as the PCI device number times 8, plus the function number.
The EF value identifies a connector.
The GH value identifies a port, address, device, or FRU.

Adapters and cards are identified only with AB-CD. The possible values for AB are:

00	Processor bus
01	ISA bus
02	EISA bus
03	MCA bus
04	PCI bus used in the case where the PCI bus cannot be identified
05	PCMCIA buses
xy	For PCI adapters where x is equal to or greater than 1. The x and y are characters in the range of 0-9, A-H, J-N, P-Z (O, I, and lower case are omitted) and are equal to the parent bus's ibm, aix-loc Open Firmware Property.

The possible values for CD depend on the adapter or card are as follows:

For pluggable PCI adapters/cards, CD is the device's devfunc number (PCI device number times 8, plus the function number). The C and D are characters in the range of 0-9, and A-F (hex numbers). This allows the location code to uniquely identify multiple adapters on individual PCI cards. For pluggable ISA adapters, CD is equal to the order in which the ISA cards defined or configured, either by SMIT or the ISA Adapter Configuration Service Aid.

For integrated ISA adapters, CD is equal to a unique code identifying the ISA adapter. In most cases, this is equal to the adapter's physical location code. In cases where a physical location code is not available, CD is FF.
EF is the connector ID. It is used to identify a connector on the adapter to which a resource is attached.
GH is used to identify a port, device, or FRU. For example:
- For async devices, GH defines the port on the fanout box. The values are 00 to 15.
- For a diskette drive, H defines either diskette drive 1 or 2. G is always 0.
- For all other devices, GH is equal to 00.

For the integrated adapters, EF-GH is the same as the definition for the pluggable adapters. For example, the location code for a diskette drive is 01-D1-00-00. A second diskette drive is 01-D1-00-01.

For SCSI devices, the location code is defined as:

AB-CD-EF-G,H
 |  |  | | |
 |  |  | | Logical Unit address of the SCSI Device
 |  |  | Control Unit Address of the SCSI Device
 |  |  Connector ID
 |  devfunc Number, Adapter Number or Physical Location
 Bus Type or PCI Parent Bus

Where:

AB-CD-EF are the same as non-SCSI devices.
G defines the control unit address of the device. Values of 0 to 15 are valid.
H defines the logical unit address of the device. Values of 0 to 255 are valid.

There is also a bus location code that is generated as '00-xxxxxxxx' where xxxxxxxx is equivalent to the node's unit address. Refer to the system unit service guide for additional information.

Location Codes for CHRP Model Architecture System Units

Note:: You need to know which system architecture the system unit on which you are working uses. If you are working with a RSPC model use the Location Codes for RSPC Model Architecture System Units. If you do not know which model you have, refer to Determining System Architecture in Diagnostic Information for Multiple Bus Systems before proceeding.

The (CHRP) system unit uses Physical Location Codes in conjunction with AIX Location Codes to provide mapping of the failing field replaceable units. The location codes are produced by the system unit's firmware and the AIX operating system.

Diagnostic Load Progress Indicators

Note:: Some systems might produce 4-digit codes. If the leftmost digit of a 4-digit code is 0, use the three rightmost digits.

c00: AIX Install/Maintenance loaded successfully.
c01: Insert the first diagnostic diskette.
c02: Diskettes inserted out of sequence.
c03: The wrong diskette is in diskette drive.
c04: The loading stopped with an irrecoverable error.
c05: A diskette error occurred.
c06: The rc.boot configuration shell script is unable to determine type of boot.
c07: Insert the next diagnostic diskette.
c08: RAM file system started incorrectly.
c09: The diskette drive is reading or writing a diskette.
c20: An unexpected halt occurred, and the system is configured to enter the kernel debug program instead of entering a system dump.
c21: The ifconfig command was unable to configure the network for the client network host.
c22: The tftp command was unable to read client's ClientHostName info file during a client network boot.
c24: Unable to read client's ClientHostName.info file during a client network boot.
c25: Client did not mount remote miniroot during network install.
c26: Client did not mount the /usr file system during the network boot.
c29: The system was unable to configure the network device.
c31: Select the console display for the diagnostics. To select No console display, set the key mode switch to Normal then to Service. The diagnostic programs then load and run the diagnostics automatically. If you continue to get the message, check the cables and make sure you are using the serial port.
c32: A directly attached display (HFT) was selected.
c33: A TTY terminal attached to serial ports S1 or S2 was selected.
c34: A file was selected. The console messages store in a file.
c35: No console found.
c40: Configuration files are being restored.
c41: Could not determine the boot type or device.
c42: Extracting data files from diskette.
c43: Cannot access the boot/install 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 environment to disk environment.
c53: Not enough space in the /tmp directory to do a preservation installation.
c54: Installing either BOS or additional packages.
c55: Could not remove the specified logical volume in a preservation installation.
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.
c62: Loading platform dependent debug files.
c63: Loading platform dependent data files.
c64: Failed to load platform dependent data files.
c70: Problem Mounting diagnostic CD-ROM disc.
c99: Diagnostics have completed. This code is only used when there is no console.
Fxx: (xx is any number) Refer to Firmware chapter of the service manual.

Dump Progress Indicators (Dump Status Codes)

The following dump progress indicators, or dump status codes, are part of a Type 102 message.

Note:: When a lowercase c is listed, it displays in the lower half of the character position. Some systems produce 4-digit codes, the two leftmost positions can have a blanks or zeros. Use the two rightmost digits.

0c0: The dump completed successfully.
0c1: The dump failed due to an I/O error.
0c2: A dump, requested by the user, is started.
0c3: The dump is inhibited.
0c4: The dump device is not large enough.
0c5: The dump did not start, or the dump crashed.
0c6: Dumping to a secondary dump device.
0c7: Reserved.
0c8: The dump function is disabled.
0c9: A dump is in progress.
0cc: Unknown dump failure

Crash Codes

Note:: Some systems may produce 4-digit codes. If the leftmost digit of a 4-digit code is 0, use the three rightmost digits.

The crash codes that follow are part of a Type 102 message. These crash codes are grouped into three categories:

Category 1: Dump analysis is the appropriate first action in Problem Determination, begin the Problem Determination process with software support.
Category 2: Dump analysis most likely will not aid in Problem Determination, begin the Problem Determination process with hardware support.
Category 3: Both software and hardware support may be needed in Problem Determination, go to MAP 0070: 888 Sequence in Operator Panel Display in Diagnostic Information for Multiple Bus Systemsto assist in problem isolation.

Category 1

300: Data storage interrupt from the processor.
32x: Data storage interrupt because of an I/O exception from IOCC.
38x: Data storage interrupt because of an I/O exception from SLA.
400: Instruction storage interrupt.
700: Program interrupt.

Category 2

200: Machine check because of a memory bus error.
201: Machine check because of a memory timeout.
202: Machine check because of a memory card failure.
203: Machine check because of a out of range address.
204: Machine check because of an attempt to write to ROS.
205: Machine check because of an uncorrectable address parity.
206: Machine check because of an uncorrectable ECC error.
207: Machine check because of an unidentified error.
208: Machine check due to an L2 uncorrectable ECC.
500: External interrupt because of a scrub memory bus error.
501: External interrupt because of an unidentified error.
51x: External interrupt because of a DMA memory bus error.
52x: External interrupt because of an IOCC channel check.
53x: External interrupt from an IOCC bus timeout; x represents the IOCC number.
54x: External interrupt because of an IOCC keyboard check.
800: Floating point is not available.

Category 3

000: Unexpected system interrupt.
558: There is not enough memory to continue the IPL.
600: AIX 4.3.3.3 and above: Alignment Interrupt. If pre-AIX 4.3.3.3: AIX has crashed because the Portability Assist Layer (PAL) for this machine type has detected a problem.
605: AIX has crashed because the Portability Assist Layer (PAL) for this machine type has detected a problem (AIX 4.3.3.3 and above).

Operator Panel Display Numbers

This page contains a list of the various numbers and characters that display in the operator panel display. There are three categories of numbers and characters. The first group tracks the progress of the configuration program. The second group tracks the progress of the diagnostics. The third group provides information about messages that follow an 888 sequence.

Configuration Program Indicators

The numbers in this list display on the operator panel as the system loads the operating system and prepares the hardware by loading software drivers.

Note:: Some systems may produce 4-digit codes. If the leftmost digit of a 4-digit code is 0, use the three rightmost digits.

2E6: The PCI Differential Ultra SCSI adapter or the Universal PCI Differential Ultra SCSI adapter being configured.
2E7: Configuration method unable to determine if the SCSI adapter type is SE or DE type.
440: 9.1GB Ultra SCSI Disk Drive being identified or configured.
441: 18.2GB Ultra SCSI Disk Drive being identified or configured.
444: 2-Port Multiprotocol PCI Adapter (ASIC) being identified or configured.
447: PCI 64-bit Fibre Channel Arbitrated Loop Adapter being configured.
500: Querying Standard I/O slot.
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.
518: Remote mount of the root (/) and /usr file systems failed during network boot.
520: Bus configuration running.
521: /etc/init invoked cfgmgr with invalid options; /etc/inithas been corrupted or incorrectly modified (irrecoverable error).
522: The configuration manager has been invoked with conflicting options (irrecoverable error).
523: The configuration manager is unable to access the ODM database (irrecoverable error).
524: The configuration manager is unable to access the config.rules object in the ODM database (irrecoverable error).
525: The configuration manager is unable to get data from a customized device object in the ODM database (irrecoverable error).
526: The configuration manager is unable to get data from a customized device driver object in the ODM database ( irrecoverable error).
527: The configuration manager was invoked with the phase 1 flag; running phase 1 at this point is not permitted (irrecoverable error).
528: The configuration manager cannot find sequence rule, or no program name was specified in the ODM database (irrecoverable error).
529: The configuration manager is unable to update ODM data (irrecoverable error).
530: The program savebase returned an error.
531: The configuration manager is unable to access the PdAt object class (irrecoverable error).
532: There is not enough memory to continue (malloc failure); irrecoverable error.
533: The configuration manager could not find a configuration method for a device.
534: The configuration manager is unable to acquire database lock (irrecoverable error).
535: HIPPI diagnostics interface driver being configured.
536: The configuration manager encountered more than one sequence rule specified in the same phase (irrecoverable error).
537: The configuration manager encountered an error when invoking the program in the sequence rule.
538: The configuration manager is going to invoke a configuration method.
539: The configuration method has terminated, and control has returned to the configuration manager.
541: A DLT tape device is being configured.
549: Console could not be configured for the Copy a System Dump Menu.
551: IPL vary-on is running.
552: IPL vary-on failed.
553: IPL phase 1 is complete.
554: The boot device could not be opened or read, or unable to define NFS swap device during network boot.
555: An ODM error occurred when trying to vary-on the rootvg, or unable to create an NFS swap device during network boot.
556: Logical Volume Manager encountered error during IPL vary-on.
557: The root filesystem does not mount.
558: There is not enough memory to continue the system IPL.
559: Less than 2 M bytes of good memory are available to load the AIX kernel.
569: FCS SCSI protocol device is being configured (32 bits).
570: Virtual SCSI devices being configured.
571: HIPPI common function device driver being configured.
572: HIPPI IPI-3 master transport driver being configured.
573: HIPPI IPI-3 slave transport driver being configured.
574: HIPPI IPI-3 transport services user interface device driver being configured.
575: A 9570 disk-array driver being configured.
576: Generic async device driver being configured.
577: Generic SCSI device driver being configured.
578: Generic commo device driver being configured.
579: Device driver being configured for a generic device.
580: HIPPI TCPIP network interface driver being configured.
581: Configuring TCP/IP.
582: Configuring Token-Ring data link control.
583: Configuring an Ethernet data link control.
584: Configuring an IEEE Ethernet data link control.
585: Configuring an SDLC MPQP data link control.
586: Configuring a QLLC X.25 data link control.
587: Configuring a NETBIOS.
588: Configuring a Bisync Read-Write (BSCRW).
589: SCSI target mode device being configured.
590: Diskless remote paging device being configured.
591: Configuring an LVM device driver.
592: Configuring an HFT device driver.
593: Configuring SNA device drivers.
594: Asynchronous I/O being defined or configured.
595: X.31 pseudo-device being configured.
596: SNA DLC/LAPE pseudo-device being configured.
597: OCS software being configured.
598: OCS hosts being configured during system reboot.
599: Configuring FDDI data link control.
59B: FCS SCSI protocol device being configured (64 bits).
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 driver being configured.
5C5: SCB network device driver for FCS 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, /usr/lib/methods/cfgsys, or /usr/lib/methods/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.
60B: 18.2GB 68-pin LVD SCSI Disk Drive being configured.
610: Attempting remote mount of NFS file system.
611: Remote mount of the NFS file system failed.
612: Accessing remote files; unconfiguring network boot device.
614: Configuring local paging devices.
615: Configuration of a 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 a remote (NFS) paging device failed.
61B: 36.4GB 80-pin LVD SCSI Disk Drive being configured.
61D: 36.4GB 80-pin LVD SCSI Disk Drive being configured.
61E: 18.2GB 68-pin LVD SCSI Disk Drive being configured.
620: Updating special device files and ODM in permanent filesystem with data from boot RAM filesystem.
621: 9.1 GB LVD 80-pin SCSI Drive being configured.
622: Boot process configuring for operating system installation.
62D: 9.1GB 68-pin LVD SCSI Disk Drive being configured.
62E: 9.1GB 68-pin LVD SCSI Disk Drive being configured.
636: TURBROWAYS 622 Mbps PCI MMF ATM Adapter.
637: Dual Channel PCI-2 Ultra2 SCSI Adapter being configured.
638: 4.5GB Ultra SCSI Single Ended Disk Drive being configured.
639: 9.1GB 10K RPM Ultra SCSI Disk Drive (68-pin).
63A: See 62D.
63B: 9.1GB 80-pin LVD SCSI Disk Drive being configured.
63C: See 60B.
63D: 18.2GB 80-pin LVD SCSI Disk Drive being configured.
63E: 36.4GB 68-pin LVD SCSI Disk Drive being configured.
63F: See 61B.
640: 9.1GB 10K RPM Ultra SCSI Disk Drive (80-pin).
646: High-Speed Token-Ring PCI Adapter being configured.
64A: See 62E.
64B: 9.1GB 80-pin LVD SCSI Disk Drive being configured.
64C: See 61E.
64D: 18.2 GB LVD 80-pin Drive/Carrier being configured.
64E: 36.4GB 68-pin LVD SCSI Disk Drive being configured.
64F: See 61D.
650: IBM SCSD disk drive being configured.
653: 18.2GB Ultra-SCSI 16-bit Disk Drive being configured.
655: GXT130P Graphics adapter being configured.
657: GXT2000P graphics adapter being configured.
658: PCI Fibre Channel Disk Subsystem Controller being identified or configured.
659: 2102 Fibre Channel Disk Subsystem Controller Drawer being identified or configured.
660: 2102 Fibre Channel Disk Array being identified or configured.
662: Ultra2 Integrated SCSI controller.
663: The ARTIC960RxD Digital Trunk Quad PCI Adapter or the ARTIC960RxF Digital Trunk Resource Adapter being configured.
664: 32x (MAX) SCSI-2 CD-ROM drive being configured.
667: PCI 3-Channel Ultra2 SCSI RAID Adapter being configured.
669: PCI Gigabit Ethernet Adapter being configured.
66C: 10/100/1000 Base-T EthernetPCI Adapter.
66D: PCI 4-Channel Ultra-3 SCSI RAID Adapter.
66E: 4.7 GB DVD-RAM drive.
674: ESCON^(R) Channel PCI Adapter being configured.
677: PCI 32-bit Fibre Channel Arbitrated Loop Adapter being configured.
67B: PCI Cryptographic Coprocessor being configured.
682: 20x (MAX) SCSI-2 CD-ROM Drive being configured.
689: 4.5GB Ultra SCSI Single Ended Disk Drive being configured.
68C: 20 GB 4-mm Tape Drive being configured.
68E: POWER GXT6000P PCI Graphics Adapter.
690: 9.1GB Ultra SCSI Single Ended Disk Drive being configured.
69b: 64-bit/66MHz PCI ATM 155 MMF PCI adapter being configured.
69d: 64-bit/66MHz PCI ATM 155 UTP PCI adapter being configured.
6CC: SSA disk drive being configured.
700: A 1.1 GB 8-bit SCSI disk drive being identified or configured.
701: A 1.1 GB 16-bit SCSI disk drive being identified or configured.
702: A 1.1 GB 16-bit differential SCSI disk drive being identified or configured.
703: A 2.2 GB 8-bit SCSI disk drive being identified or configured.
704: A 2.2 GB 16-bit SCSI disk drive being identified or configured.
705: The configuration method for the 2.2 GB 16-bit differential SCSI disk drive is being run. If an irrecoverable error occurs, the system halts.
706: A 4.5 GB 16-bit SCSI disk drive being identified or configured.
707: A 4.5 GB 16-bit differential SCSI disk drive being identified or configured.
708: A L2 cache being identified or configured.
710: POWER GXT150M graphics adapter being identified or configured.
711: Unknown adapter being identified or configured.
712: Graphics slot bus configuration is executing.
713: The IBM ARTIC960 device being configured.
714: A video capture adapter being configured.
715: The Ultramedia Services audio adapter being configured. (this number displays briefly on the panel).
717: TP Ethernet Adapter being configured.
718: GXT500 Graphics Adapter being configured.
720: Unknown read/write optical drive type being configured.
721: Unknown disk or SCSI device being identified or configured.
722: Unknown disk being identified or configured.
723: Unknown CD-ROM being identified or configured.
724: Unknown tape drive being identified or configured.
725: Unknown display adapter being identified or configured.
726: Unknown input device being identified or configured.
727: Unknown async device being identified or configured.
728: Parallel printer being identified or configured.
729: Unknown parallel device being identified or configured.
730: Unknown diskette drive being identified or configured.
731: PTY being identified or configured.
732: Unknown SCSI initiator type being configured.
733: 7GB 8 mm tape drive being configured.
734: 4x SCSI-2 640 MB CD-ROM Drive being configured.
736: Quiet Touch keyboard and speaker cable being configured.
741: 1080 MB SCSI Disk Drive being configured.
745: 16GB 4 mm Tape Auto Loader being configured.
746: SCSI-2 Fast/Wide PCI Adapter being configured.
747: SCSI-2 Differential Fast/Wide PCI Adapter being configured.
749: 7331 Model 205 Tape Library being configured.
751: SCSI 32-bit SE F/W RAID Adapter being configured.
754: 1.1GB 16-bit SCSI disk drive being configured.
755: 2.2GB 16-bit SCSI disk drive being configured.
756: 4.5GB 16-bit SCSI disk drive being configured.
757: External 13GB 1.5M/s 1/4 inch tape being configured.
763: SP Switch MX Adapter being configured.
764: SP System Attachment Adapter being configured.
772: 4.5GB SCSI F/W Disk Drive being configured.
773: 9.1GB SCSI F/W Disk Drive being configured.
774: 9.1GB External SCSI Disk Drive being configured.
776: PCI Token-Ring Adapter being identified or configured.
777: 10/100 Ethernet Tx PCI Adapter being identified or configured.
778: POWER GXT3000P 3D PCI Graphics adapter being configured.
77B: 4-Port 10/100 Ethernet Tx PCI Adapter being identified or configured.
77c: A 1.0 GB 16-bit SCSI disk drive being identified or configured.
783: 4 mm DDS-2 Tape Autoloader being configured.
789: 2.6 GB External Optical Drive being configured.
78B: POWER GXT4000P PCI Graphics Adapter.
78C: PCI bus configuration executing.
78D: GXT300P 2D Graphics adapter being configured.
790: Multi-bus Integrated Ethernet Adapter being identified or configured.
797: TURBOWAYS^(R) 155 UTP/STP ATM Adapter being identified or configured.
798: Video streamer adapter being identified or configured.
799: 2-Port Multiprotocol PCI adapter being identified or configured.
79c: ISA bus configuration executing.
7C0: CPU/System Interface being configured.
7C1: Business Audio Subsystem being identified or configured.
7cc: PCMCIA bus configuration executing.
800: TURBOWAYS 155 MMF ATM Adapter being identified or configured.
803: 7336 Tape Library robotics being configured.
804: 8x Speed SCSI-2 CD-ROM Drive being configured.
806: POWER GXT800 PCI Graphics adapter being configured.
807: SCSI Device Enclosure being configured.
80c: SSA 4-Port Adapter being identified or configured.
811: Processor complex being identified or configured.
812: Memory being identified or configured.
813: Battery for time-of-day, NVRAM, and so on being identified or configured, or system I/O control logic being identified or configured.
814: NVRAM being identified or configured.
815: Floating-point processor test.
816: Operator panel logic being identified or configured.
817: Time-of-day logic being identified or configured.
819: Graphics input device adapter being identified or configured.
821: Standard keyboard adapter being identified or configured.
823: Standard mouse adapter being identified or configured.
824: Standard tablet adapter being identified or configured.
825: Standard speaker adapter being identified or configured.
826: Serial Port 1 adapter being identified or configured.
827: Parallel port adapter being identified or configured.
828: Standard diskette adapter being identified or configured.
831: 3151 adapter being identified or configured, or Serial Port 2 being identified or configured.
834: 64-port async controller being identified or configured.
835: 16-port async concentrator being identified or configured.
836: 128-port async controller being identified or configured.
837: 16-port remote async node being identified or configured.
838: Network Terminal Accelerator Adapter being identified or configured.
839: 7318 Serial Communications Server being configured.
840: PCI Single-Ended Ultra SCSI Adapter being configured.
841: 8-port async adapter (EIA-232) being identified or configured.
842: 8-port async adapter (EIA-422A) being identified or configured.
843: 8-port async adapter (MIL-STD 188) being identified or configured.
844: 7135 RAIDiant Array disk drive subsystem controller being identified or configured.
845: 7135 RAIDiant Array disk drive subsystem drawer being identified or configured.
846: RAIDiant Array SCSI 1.3GB Disk Drive being configured.
847: 16-port serial adapter (EIA-232) being identified or configured.
848: 16-port serial adapter (EIA-422) being identified or configured.
849: X.25 Interface Coprocessor/2 adapter being identified or configured.
850: Token-Ring network adapter being identified or configured.
851: T1/J1 Portmaster^(R) adapter being identified or configured.
852: Ethernet adapter being identified or configured.
854: 3270 Host Connection Program/6000 connection being identified or configured.
855: Portmaster Adapter/A being identified or configured.
857: FSLA adapter being identified or configured.
858: 5085/5086/5088 adapter being identified or configured.
859: FDDI adapter being identified or configured.
85c: Token-Ring High-Performance LAN adapter being identified or configured.
861: Optical adapter being identified or configured.
862: Block Multiplexer Channel Adapter being identified or configured.
865: ESCON Channel Adapter or emulator being identified or configured.
866: SCSI adapter being identified or configured.
867: Async expansion adapter being identified or configured.
868: SCSI adapter being identified or configured.
869: SCSI adapter being identified or configured.
870: Serial disk drive adapter being identified or configured.
871: Graphics subsystem adapter being identified or configured.
872: Grayscale graphics adapter being identified or configured.
874: Color graphics adapter being identified or configured.
875: Vendor generic communication adapter being configured.
876: 8-bit color graphics processor being identified or configured.
877: POWER Gt3^(TM)/POWER Gt4^(TM) being identified or configured.
878: POWER Gt4 graphics processor card being configured.
879: 24-bit color graphics card, MEV2 being configured.
880: POWER Gt1^(TM) adapter being identified or configured.
887: Integrated Ethernet adapter being identified or configured.
889: SCSI adapter being identified or configured.
890: SCSI-2 Differential Fast/Wide and Single-Ended Fast/Wide Adapter/A being configured.
891: Vendor SCSI adapter being identified or configured.
892: Vendor display adapter being identified or configured.
893: Vendor LAN adapter being identified or configured.
894: Vendor async/communications adapter being identified or configured.
895: Vendor IEEE 488 adapter being identified or configured.
896: Vendor VME bus adapter being identified or configured.
897: S/370^(TM) Channel Emulator adapter being identified or configured.
898: POWER Gt1x^(TM) graphics adapter being identified or configured.
899: 3490 attached tape drive being identified or configured.
89c: A multimedia SCSI CD-ROM being identified or configured.
900: GXT110P Graphics Adapter being identified or configured.
901: Vendor SCSI device being identified or configured.
902: Vendor display device being identified or configured.
903: Vendor async device being identified or configured.
904: Vendor parallel device being identified or configured.
905: Vendor other device being identified or configured.
908: POWER GXT1000 Graphics subsystem being identified or configured.
910: 1/4GB Fiber Channel/266 Standard Adapter being identified or configured.
911: Fiber Channel/1063 Adapter Short Wave being configured.
912: 2.0GB SCSI-2 differential disk drive being identified or configured.
913: 1.0GB differential disk drive being identified or configured.
914: 5GB 8 mm differential tape drive being identified or configured.
915: 4GB 4 mm tape drive being identified or configured.
916: Non-SCSI vendor tape adapter being identified or configured.
917: A 2.0 GB 16-bit differential SCSI disk drive being identified or configured.
918: A 2 GB 16-bit single-ended SCSI disk drive being identified or configured.
920: Bridge Box being identified or configured.
921: 101 keyboard being identified or configured.
922: 102 keyboard being identified or configured.
923: Kanji keyboard being identified or configured.
924: Two-button mouse being identified or configured.
925: Three-button mouse being identified or configured.
926: 5083 tablet being identified or configured.
927: 5083 tablet being identified or configured.
928: Standard speaker being identified or configured.
929: Dials being identified or configured.
930: Lighted program function keys (LPFK) being identified or configured.
931: IP router being identified or configured.
933: Async planar being identified or configured.
934: Async expansion drawer being identified or configured.
935: 3.5-inch diskette drive being identified or configured.
936: 5.25-inch diskette drive being identified or configured.
937: An HIPPI adapter being configured.
938: Serial HIPPI PCI adapter being configured.
942: POWER GXT 100 graphics adapter being identified or configured.
943: A 3480 or 3490 control unit attached to a System/370 Channel Emulator/A adapter are being identified or configured.
944: 100MB ATM adapter being identified or configured.
945: 1.0GB SCSI differential disk drive being identified or configured.
946: Serial port 3 adapter being identified or configured.
947: A 730MB SCSI disk drive being configured.
948: Portable disk drive being identified or configured.
949: Unknown direct bus-attach device being identified or configured.
950: Missing SCSI device being identified or configured.
951: 670MB SCSI disk drive being identified or configured.
952: 355MB SCSI disk drive being identified or configured.
953: 320MB SCSI disk drive being identified or configured.
954: 400MB SCSI disk drive being identified or configured.
955: 857MB SCSI disk drive being identified or configured.
956: 670MB SCSI disk drive electronics card being identified or configured.
957: 120 MB DBA disk drive being identified or configured.
958: 160 MB DBA disk drive being identified or configured.
959: 160 MB SCSI disk drive being identified or configured.
960: 1.37GB SCSI disk drive being identified or configured.
964: Internal 20 GB 8 mm tape drive identified or configured.
968: 1.0 GB SCSI disk drive being identified or configured.
970: Half-inch, 9-track tape drive being identified or configured.
971: 150 MB 1/4-inch tape drive being identified or configured.
972: 2.3 GB 8 mm SCSI tape drive being identified or configured.
973: Other SCSI tape drive being identified or configured.
974: CD-ROM drive being identified or configured.
975: An optical disk drive being identified or configured.
977: M-Audio Capture and Playback Adapter being identified or configured.
981: 540MB SCSI-2 single-ended disk drive being identified or configured.
984: 1GB 8-bit disk drive being identified or configured.
985: M-Video Capture Adapter being identified or configured.
986: 2.4GB SCSI disk drive being identified or configured.
987: An Enhanced SCSI CD-ROM drive being identified or configured.
989: 200MB SCSI disk drive being identified or configured.
990: 2.0GB SCSI-2 single-ended disk drive being identified or configured.
991: 525MB 1/4-inch cartridge tape drive being identified or configured.
994: 5 GB 8 mm tape drive being identified or configured.
995: 1.2GB 1/4 inch cartridge tape drive being identified or configured.
996: A single-port, multiprotocol communications adapter being identified or configured.
997: FDDI adapter being identified or configured.
998: 2.0 GB 4 mm tape drive being identified or configured.
999: 7137 or 3514 Disk Array Subsystem being configured.
D46: Token-Ring cable
D81: T2 Ethernet Adapter being configured.
2530: 10/100 Mbps Ethernet PCI Adapter II being configured.

Physical Location Codes

Note:

Diagnostic Versions 5.2.0 and later display physical location codes for all resources. Diagnostic versions earlier than 5.2.0 show a mixture of physical location codes and AIX location codes. As an example, under diagnostics version 5.2.0 might display a resource as:

ent0            P2/E1    IBM 10/100  Mbps Ethernet PCI adapter

The P2/E1 is the physical location code indicating an Ethernet port built into the P2 planar.
whereas, in versions prior to 5.2.0, the resource might be shown as:

 ent0            10-60    IBM 10/100  Mbps Ethernet PCI adapter

The 10-60 is an AIX location code indicating a PCI parent bus of 10, and a devfunc number of 60 (for more information , see AIX Location Codes).
These physical location codes can appear in many places while running diagnostics; for instance, within resource menus, SRNs, or specific service aids.

Physical location codes provide a mapping of logical functions in a platform (or expansion sites for logical functions, such as connectors or ports) to their specific locations within the physical structure of the platform.

Location Code Format

The format for the location code is a string of alphanumeric characters separated by a dash (-), slash (/), pound sign (#), or period (.). The base location is all of the information before the slash (/) or pound sign (#). It identifies a device that is connected or plugged into the parent. Extended location information follows the slash (/). It identifies a device that is part of the parent, a connector, or a cable. Cable information follows the pound sign (#). It identifies a cable that is connected to the parent. The following are examples:

P1 identifies system planar P1.
U1-P1 also identifies system planar P1 in a rack or drawer unit.
P2 identifies an I/O planar (including all integrated I/O devices).
P1-C1 identifies a CPU card C1 plugged into planar P1.
P1-M2 identifies a memory card or SIMM M2 plugged into planar P1.
P2/K1 identifies a keyboard port controller (with connector) connected to planar P2.
P1-K1 identifies a keyboard attached to connector K1 on planar P1.
P1/S1 identifies serial port 1 controller on planar P1, the connector for serial port 1, or the cable attached to connector S1.
P1-I2/E3 identifies; Ethernet controller 3 on the card plugged into slot 2 (I2) on planar P1, the connector for Ethernet controller 3, or the cable attached to Ethernet controller 3.
P1-I2#E3 identifies; the cable attached to Ethernet controller 3 plugged into slot 2 (I2) on planar P1.

The period (.) is used to identify sub-locations such as memory DIMMs on a base memory card or a specific SCSI address. The following are examples:

P1-M1.4 identifies DIMM 4 on memory card 1 on planar 1.
U1-P1-M2.12 identifies DIMM 12 on memory card in slot 2 on the system planar.
P1-C1.1 identifies CPU 1 on CPU card 1 on planar 1.
P2/Z1-A3.1 identifies a SCSI device with a SCSI address of LUN 1 at SCSI ID 3 attached to SCSI bus 1 from planar 2.
P1-I2#E3.2 identifies the second cable in a series of cables attached to Ethernet controller 3 in slot 2 (I2) on planar 1.

Depending on the AIX and firmware levels, AIX Diagnostics may include extended location information when identifying a planar or card. The extended location information or cable information is always included when identifying a cable or connector. Location codes with extended location information that display without a description identifying the devices, always identify the cable attached to the port.

Physical Location Code Standard Prefixes

The following table lists the assigned values for the location type prefixes. In most cases, the prefix value assignments were chosen to provide some mnemonic characteristic, so that they would be easier to remember. The underlined characters in the description field are intended to illustrate this mnemonic relationship.

Description	Prefix Value (n=instance #)
Rack or drawer unit	Un
Drawer unit mounted in a rack	Un.n (U0.n if rack cannot be sensed by firmware)
Single enclosure platform	(No enclosure location code)
Planar (backplane, system, I/O)	Pn
Planar riser card, extender	Pn.n
Power/voltage supply, voltage regulator, backup battery	Vn
Fan/sensor	Fn
LED/LCD operator panel or Logical device address n relative to adapter port	Ln
CPU/cache card (or pluggable module if on planar)	Cn
CPU/cache module on CPU card (if pluggable)	Cn.n
Memory card or SIMM/DIMM on planar	Mn
Memory SIMM/DIMM on memory card	Mn.n
Other extra-function base system cards (for example, service processor)	Xn
I/O adapter	In
Pluggable modules or daughter cards on I/O adapter	In.n
Device in Bay n	Dn
Ports/Connectors:
Graphics/video connector	Gn
Keyboard/keyboard connector	Kn
Mouse/mouse connector	On
Serial port	Sn
Parallel port	Rn
Ethernet connector	En
Token Ring connector	Tn
SCSI (pronounced scuzzy) connector	Zn
Other I/O ports or connectors	Qn
SCSI device addresses (including SSA (Serial Storage Architecture))
Primary address (SCSI control unit ID)	An
Primary and secondary address (SCSI ID and LUN (Logical Unit Number))	An.n
SCSI device location in SCSI Enclosure Services (SES)
SCSI bank	Bn
SCSI bank and bay	Bn.n
Undefined prefixes (reserved)	H, J, N, Y
Unique device address, this address remains constant independent of which port the device is attached to.	Wn

Location Codes for RSPC Model Architecture System Units

Notes:

RSPC systems are only supported with AIX or Diagnostic versions below 5.2.0
You need to know which system architecture the system unit on which you are working uses. If you are working with a CHRP model, use the Location Codes for CHRP Model Architecture System Units. If you do not know which model you have, refer to Determining System Architecture in Diagnostic Information for Multiple Bus Systems before proceeding.

Because the same diagnostic programs are used on all system units, a location code is used to physically locate a failing device or unit. The location code is displayed along with the service request number (SRN) when the diagnostic programs isolate a failure. If the location code is not known, you can run the Display Previous Diagnostic Results service aid to display the results of the last time the diagnostic programs were run.

The basic format of the system unit's location code is:

AB-CD-EF-GH  non-SCSI
AB-CD-EF-G,H  SCSI

For planars, cards, and non-SCSI devices, the location code is defined as follows:

AB-CD-EF-GH
 |  |  |  |
 |  |  |  Device/FRU/Port ID
 |  |  Connector ID
 |  Slot or Adapter Number
 Bus Type

AB identifies a bus type.
CD identifies a slot or adapter number.
EF is the connector identifier, used to identify the adapter connector to which a resource is attached.
GH identifies a port, address, memory module, device, or FRU. GH has several meanings depending upon the resource type, they are as follows:
- For memory cards, GH defines a memory module. Values for GH are 1 through 16. For systems that have memory modules that plug directly into the system planar, the location code is 00-00-00-GH where GH is the memory module slot. For systems that have memory cards with memory modules, the location code is 00-CD-EF-GH, where CD is the card slot and GH is the memory module slot.
- For L2 caches, GH defines the cache. Values for GH are 1 through 16.
- For PCMCIA devices, GH defines the PCMCIA. Values for GH are 1 through 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 integrated adapters, EF-GH is the same as the definition for a pluggable adapter. For example, the location code for a diskette drive is 01-A0-00-00. A second diskette drive is 01-A0-00-01.

For SCSI, the location code is defined as follows:

AB-CD-EF-G,H
 |  |  | | |
 |  |  | | Logical Unit Address of SCSI Device
 |  |  | Control Unit Address of SCSI Device
 |  |  Connector ID
 |  Slot or Adapter Number
 Bus Type

Where:

AB-CD-EF are the same as non-SCSI devices.
G defines the control unit address of the device. Values of 0 to 15 are valid.
H defines the logical unit address of the device. Values of 0 to 255 are valid.

Adapters and cards are identified with only AB-CD. The possible values for AB are as follows:

 00   for processor bus
 01   for ISA buses
 04   for PCI buses
 05   for PCMCIA buses (not supported on 7024)

The possible values for CD depend on the adapter or card.

For pluggable adapters or cards, this is a two-digit slot number in the range from 01 to 99. However, in the case of ISA cards these numbers do not actually correspond to the physical slot numbers. They simply are based on the order in which the ISA cards are defined or configured, either by SMIT or the ISA Adapter Configuration Service Aid.

For integrated adapters, the first character (C) is a letter in the range from A to Z. This letter is based on the order in which the integrated adapters are defined in residual data. This ensures unique location codes for the integrated adapters. The second character (D) is set to 0.

Refer to the following RSPC location code examples:

Processor-PCI bus
 00-00       PCI bus
Memory module in system planar
 00-00-00-01
Memory module in card
 00-0A-00-01
Integrated PCI adapters
 04-A0 ISA bus (Integrated PCI-ISA bridge)
 04-B0 Secondary PCI bus (Integrated PCI-PCI bridge)
 04-C0 Integrated PCI SCSI controller
Non-integrated PCI adapters
 04-01 Any PCI card in slot 1
 04-02 Any PCI card in slot 2
Integrated ISA adapters
 01-A0 Diskette adapter
 01-B0 Parallel port adapter
 01-C0 Serial port 1 adapter
 01-D0 Serial port 2 adapter
 01-E0 Keyboard adapter
 01-F0 Mouse adapter
Non-integrated ISA adapters
 01-01 First ISA card defined/configured
 01-02 Second ISA card defined/configured
 01-03 Third ISA card defined/configured
 01-04 Fourth ISA card defined/configured
Device attached to SCSI controller
 04-C0-01-4,0 Device attached to Integrated PCI SCSI controller