MAP 3244

Use this MAP to resolve the following problems:

• Configuration error: incorrect multipath connection (SRN nnnn-4030) for a PCIe2 or a PCIe3 controller.
• Configuration error: incomplete multipath connection between the controller and the enclosure detected (SRN nnnn-4040) for a PCIe2 or a PCIe3 controller.

The possible causes follow:

• Incorrect cabling to device enclosure.
  Note: Pay special attention to the requirement that a Y0 cable, YI cable, or Xcable must be routed along the right side of the rack frame, as viewed from the rear, when connecting to a disk expansion drawer. Review the device enclosure cabling and correct the cabling as required.
• A failed connection caused by a failing component in the SAS fabric between, and including, the controller and device enclosure.

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 and a failed connection can be the result of a failed system board or integrated device enclosure.
• When using SAS adapters in either a high availability (HA) two-system RAID or HA single-system RAID configuration, ensure that the actions taken in this MAP are against the primary adapter and not the secondary adapter.
• Before doing the system verification action in this map, reconstruct any degraded disk arrays if possible. This action helps avoid potential data loss that might result from the adapter being reset during the system verification action taken in this map.

Step 3244-1

Was the SRN nnnn-4030?

No

Go to Step 3244-5.

Yes

Go to Step 3244-2.

Step 3244-2

Using the resource found in the step 2, see SAS resource locations to understand how to identify the controller's port that the device, or device enclosure, is attached.

For example, if the resource is equal to 0004FFFF, port 04 on the adapter is used to attach the device or device enclosure that is experiencing the problem.

Step 3244-3

Review the device enclosure cabling and correct the cabling as required. To see examples of device configurations with SAS cabling, see Serial attached SCSI cable planning.

Step 3244-4

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.

Step 3244-5

The SRN is nnnn-4040.

Determine if a 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 > IBM SAS Disk Array Manager.
2. Select Diagnostics and Recovery Options.
3. Select Show SAS Controller Physical Resources > Show Fabric Path Graphical View.

Step 3244-6

Run diagnostics in System Verification mode on the adapter to rediscover the devices and connection:.

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.

Step 3244-7

Determine whether 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 > IBM SAS Disk Array Manager.
2. Select Diagnostics and Recovery Options > Show SAS Controller Physical Resources > Show Fabric Path Graphical View.
3. Select a device with a path that is not marked 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 3244-8.

Yes

Go to Step 3244-10.

Step 3244-8

After the problem persists, some corrective action is needed to resolve the problem. Proceed by doing the following steps:

1. Power off the system or logical partition.
2. Perform only one of the following corrective actions, which are listed in the order of preference. If one of the corrective actions was previously attempted, proceed to the next action in the list.
   Note: Prior to replacing parts, consider using a complete shutdown and power-off of the entire system, including any external device enclosures, to reset all possible failing components. This action might correct the problem without replacing parts.
   • Reseat cables on the adapter and the device enclosure.
   • Replace the cable from the adapter to the device enclosure.
   • Replace the internal device enclosure or see the service documentation for the external expansion drawer to determine which field replaceable unit (FRU) to replace that might contain the SAS expander.
   • Replace the adapter.
   • Contact your hardware service provider.
3. Power on the system or logical partition.
   Note: In some situations, it might be acceptable to unconfigure and reconfigure the adapter instead of powering off and powering on the system or logical partition.

Step 3244-9

Determine whether 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 > IBM SAS Disk Array Manager.
2. Select Diagnostics and Recovery Options > Show SAS Controller Physical Resources > Show Fabric Path Graphical View.
3. Select a device with a path that is not marked as 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 3244-8.

Yes

Go to Step 3244-10.

Step 3244-10

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.