MAP 4152

Use this MAP to resolve device bus fabric problems.

Use this MAP to resolve the following problems:
  • Device bus fabric error (SRN nnnn – 4100)
  • Temporary device bus fabric error (SRN nnnn – 4101)
The possible causes are:
  • A failed connection caused by a failing component in the SAS fabric between, and including, the adapter and device enclosure.
  • A failed connection caused by a failing component within the device enclosure, including the device itself.

Considerations:

  • Remove power from the system before connecting and disconnecting cables or devices, as appropriate, to prevent hardware damage or erroneous diagnostic results.
  • Some systems have the disk enclosure or removable media enclosure integrated in the system with no cables. For these configurations, the SAS connections are integrated onto the system boards. A failed connection can be the result of a failed system board or integrated device enclosure.
  • Some systems have SAS RAID adapters integrated onto the system boards and use a cache RAID - dual IOA enablement card (for example, FC5662) to enable storage adapter write cache and dual storage I/O adapter (IOA) mode (HA RAID mode). For these configurations, replacement of the Cache RAID - dual IOA enablement card is unlikely to solve a SAS-related problem because the SAS interface logic is on the system board. Additionally, appropriate service procedures must be followed when replacing the Cache RAID - dual IOA enablement card since removal of this card can cause data loss if incorrectly performed and can also result in a nondual storage IOA (non-HA) mode of operation.
  • When using SAS adapters in either an HA two-system RAID or HA single-system RAID configuration, ensure that the actions taken in this MAP are against the primary adapter (not the secondary adapter).
  • An adapter reset might occur during the system verification step of this procedure. To avoid potential data loss, reconstruct any degraded disk arrays if possible, before performing system verification.
Attention: When SAS fabric problems exist, obtain assistance from your hardware service provider before performing any of the following actions:
  • Before you replace a RAID adapter: Because the adapter might contain nonvolatile write cache data and configuration data for the attached disk arrays, additional problems can be created by replacing an adapter.
  • Before you remove functioning disks in a disk array: The disk array might become degraded or failed and additional problems might be created if functioning disks are removed from a disk array.

Step 4152-1

Determine if the problem still exists for the adapter that logged this error by examining the SAS connections as follows:

  1. Start the IBM® SAS Disk Array Manager.
    1. Start Diagnostics and select Task Selection on the Function Selection display.
    2. Select RAID Array Manager.
    3. Select IBM SAS Disk Array Manager.
  2. Select Diagnostics and Recovery Options.
  3. Select Show SAS Controller Physical Resources.
  4. Select Show Fabric Path Graphical View.

Do all expected devices appear in the list and are all paths marked as Operational?

No
Go to Step 4152-2.
Yes
Go to Step 4152-6.

Step 4152-2

Run diagnostics in system verification mode on the adapter to rediscover the devices and connections.

  1. Start Diagnostics and select Task Selection on the Function Selection display.
  2. Select Run Diagnostics.
  3. Select the adapter resource.
  4. Select System Verification.
Note: Disregard any trouble found for now, and continue with the next step.

Step 4152-3

Determine if the problem still exists for the adapter that logged this error by examining the SAS connections as follows:

  1. Start the IBM SAS Disk Array Manager.
    1. Start Diagnostics and select Task Selection on the Function Selection display.
    2. Select RAID Array Manager.
    3. Select IBM SAS Disk Array Manager.
  2. Select Diagnostics and Recovery Options.
  3. Select Show SAS Controller Physical Resources.
  4. Select Show Fabric Path Graphical View.
  5. Select a device with a path that is not Operational (if one exists) to obtain additional details about the full path from the adapter port to the device. See Viewing SAS fabric path information for an example of how this additional detail can be used to help isolate where in the path the problem exists.

Do all expected devices appear in the list and are all paths marked as Operational?

No
Go to Step 4152-4.
Yes
Go to Step 4152-6.

Step 4152-4

Go to SAS fabric identification. Then continue with the next step.

Step 4152-5

Determine if the problem still exists for the adapter that logged this error by examining the SAS connections as follows:

  1. Start the IBM SAS Disk Array Manager.
    1. Start Diagnostics and select Task Selection on the Function Selection display.
    2. Select RAID Array Manager.
    3. Select IBM SAS Disk Array Manager.
  2. Select Diagnostics and Recovery Options.
  3. Select Show SAS Controller Physical Resources.
  4. Select Show Fabric Path Graphical View.
  5. Select a device with a path that is not Operational (if one exists) to obtain additional details about the full path from the adapter port to the device. See Viewing SAS fabric path information for an example of how this additional detail can be used to help isolate where in the path the problem exists.

Do all expected devices appear in the list and are all paths marked as Operational?

No
Go to Step 4152-4.
Yes
Go to Step 4152-6.

Step 4152-6

When the problem is resolved, see the removal and replacement procedures topic for the system unit on which you are working and do the "Verifying the repair" procedure.

Parent topic: Isolating problems on servers that run AIX or Linux


Last updated: Wed, June 19, 2019