MAP 0054: PCI-X SCSI Bus Problems

Use this MAP to determine which FRUs may need to be replaced in order to solve a SCSI bus-related problem on a PCI-X SCSI or PCI-X SCSI RAID adapter.

Purpose of This MAP

Use the following to determine which FRUs may need to be replaced in order to solve a SCSI bus-related problem on a PCI-X SCSI or PCI-X SCSI RAID adapter.

Considerations

Remove power from the system before connecting and disconnecting cables or devices, as appropriate, to prevent hardware damage or erroneous diagnostic results.
Note that some systems have SCSI and PCI-X bus interface logic integrated onto the system boards and use a pluggable RAID enablement card (a non-PCI form factor card) for these SCSI/PCI-X busses. An example of such a RAID enablement card is FC 5709. For these configurations, replacement of the RAID enablement card is unlikely to solve a SCSI bus-related problem, since the SCSI bus interface logic is on the system board.
Some adapters provide two connectors, one internal and one external, for each SCSI bus. For this type of adapter, it is not acceptable to use both connectors for the same SCSI bus at the same time. SCSI bus problems are likely to occur if this is done. However, it is acceptable to use an internal connector for one SCSI bus and an external connector for another SCSI bus. The internal and external connectors are labeled to indicate which SCSI bus they correspond to.

Attention: Replacing RAID adapters is not recommended without assistance from your service support structure when SCSI bus problems exist. Because the adapter may contain non-volatile write cache data and configuration data for the attached disk arrays, additional problems can be created by replacing an adapter when SCSI bus problems exist.

Removing functioning disks in a disk array is not recommended without assistance from your service support structure. A disk array may become degraded or failed if functioning disks are removed, and additional problems may be created.

Follow the steps in this MAP to isolate a PCI-X SCSI bus problem.

Step 0054-1
Identify the SCSI bus on which the problem is occurring on by examining the hardware error log. To view the hardware error log, do the following:
1. Invoke diagnostics and select Task Selection on the Function Selection screen.
2. Select Display Hardware Error Report.
3. Choose one of the following options:
  - If the type of adapter is not known, select Display Hardware Errors for Any Resource.
  - If the adapter is a PCI-X SCSI adapter, select Display Hardware Errors for PCI-X SCSI Adapters.
  - If the adapter is a PCI-X SCSI RAID adapter, select Display Hardware Errors for PCI-X SCSI RAID Adapters.
4. Select the resource, or select All Resources if the resource is not known.
  Note:
  
  If you had previously selected Display Hardware Errors for Any Resource, then select All Resources.
5. On the Error Summary screen, look for an entry with a SRN corresponding to the problem which sent you here, and select it.
  Note:
  
  If multiple entries exist for the SRN it could be that some entries are old or that the problem has occurred on multiple entities (adapters, disk arrays, and/or devices). Older entries can be ignored; however, this MAP may need to be used multiple times if the same problem has occurred on multiple entities.
6. Select the hardware error log to view.
While viewing the hardware error log, under the Detail Data and SENSE DATA headings, identify the first four bytes of the hexadecimal data (for example, nnnn nnnn nnnn nnnn ...). The four bytes identified in the error log can be interpreted as:
```
00bb ssLL  
```
where:
- bb, when not FF, identifies the adapter's SCSI bus
- ss, when not FF, identifies the SCSI ID of a device
- LL, when not FF, identifies the logical unit number (LUN) of a device
Go to Step 0540-2.
Step 0054-2
Are the last two bytes of the four bytes identified in Step 0540-1, equal to FFFF (for example, 00bb FFFF, where bb identifies the adapter's SCSI bus)?

NO

Go to Step 0540-4.

YES

Go to Step 0540-3.
Step 0054-3
While the error persists, replace the components of the failing SCSI bus in the following order:
1. Cable on bus bb (if present)
2. Adapter (if SCSI bus interface logic is on the adapter) or system board (if SCSI bus interface logic is on the system board)
To replace a component, and see if the problem was corrected, do the following:
1. Follow the removal and replacement procedure for the component as previously described in this step.
2. Run diagnostics in system verification mode on the adapter.
When the problem is resolved, go to Verifying a repair.
Step 0054-4
Are the last two bytes of the four bytes identified in Step 0540-1, equal to FF00 (for example, 00bb FF00, where bb identifies the adapter's SCSI bus)?

NO

Go to Step 0540-6.

YES

Go to Step 0540-5.
Step 0054-5
While the error persists, replace the components of the failing SCSI bus in the following order:
1. Cable on bus bb (if present)
2. Adapter (if SCSI bus interface logic is on the adapter) or system board (if the SCSI bus interface logic is on the system board)
3. DASD backplane attached to bus bb (if present)
To replace a component, and see if the problem was corrected, do the following:
1. Follow the removal and replacement procedure for the component as previously described in this step.
2. Run diagnostics in system verification mode on the adapter.
When the problem is resolved, go to Verifying a repair.
Step 0054-6
While the error persists, replace the components of the failing SCSI bus in the following order:
1. Device on bus bb with SCSI ID ss
2. Cable on bus bb (if present)
3. Adapter (if SCSI bus interface logic is on the adapter) or system board (if SCSI bus interface logic is on the system board)
To replace a component and see if the problem was corrected, do the following:
1. Follow the removal and replacement procedure for the component as previously described in this step.
2. Run diagnostics in system verification mode on the adapter.
When the problem is resolved, go to Verifying a repair.