SIP3146

Use this procedure to resolve the configuration error: Incomplete multipath connection between enclosures and device detected (SRC xxxx4041).

The possible cause is a failed connection caused by a failing component within the device enclosure, including the device itself.

Note: The adapter is not a likely cause of this problem.

Considerations:

Power off the system, partition, or card slot before connecting and disconnecting cables or devices, as appropriate, to prevent hardware damage.
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.
Some configurations involve a serial attached SCSI (SAS) adapter connecting to internal SAS disk enclosures within a system using a cable card. Keep in mind that when the procedure refers to a device enclosure, it could be referring to the internal SAS disk slots or media slots. Also, when the procedure refers to a cable, it could include a cable card.
When using SAS adapters in a Dual Storage IOA configuration, ensure that the actions taken in this procedure are against the primary adapter (that is, not the secondary adapter).

Attention: Removing functioning disk units in a disk array is not recommended without assistance from your service provider. If functioning disk units are removed, a disk array might become unprotected or failed and additional problems could be created.

Determine the resource name of the adapter that reported the problem by performing the following:
1. Access SST or DST.
2. Access the product activity log and record the resource name that this error is logged against. If the resource name is an adapter resource name, use it and continue with the next step. If the resource name is a disk unit resource name, use Hardware Service Manager to determine the resource name of the adapter that is controlling this disk unit.
Determine if a problem still exists for the adapter that logged this error by examining the SAS connections as follows:
1. On the System Service Tools (SST) display, select Start a Service Tool, and then press Enter.
2. Select Display/Alter/Dump.
3. Select Display/Alter storage.
4. Select Licensed Internal Code (LIC) data.
5. Select Advanced Analysis.
6. Type FABQUERY on the entry line and then select it with option 1.
7. On the Specify Advanced Analysis Options screen, type -SUB 01 -IOA DCxx -DSP 0 in the Options field, where DCxx is the adapter resource name. Press Enter.
  Note: More information is available by returning to the Specify Advanced Analysis Options screen and typing -SUB 01 -IOA DCxx -DSP 2 in the Options field, where DCxx is the adapter resource name. Press Enter.
  Do all expected devices appear in the list and are all paths marked as Operational?
  - No: Continue with the next step.
  - Yes: The error condition no longer exists. This ends the procedure.
Perform the following steps to cause the adapter to rediscover the devices and connections:
Note: Performing this step causes your system partition to temporarily hang when using the i5/OS® operating system. Be patient, the system does work itself past the temporary hang.
1. Use Hardware Service Manager to perform another IPL of the virtual I/O processor that is associated with this adapter.
2. Vary on any other resources attached to the virtual I/O processor.
To determine if the problem still exists for the adapter that logged this error, examine the SAS connections by performing the actions in step 2 again. Do all expected devices appear in the list and are all paths marked as Operational?
- No: Continue with the next step.
- Yes: The error condition no longer exists. This ends the procedure.
Perform only one of the following corrective actions (listed in the order of preference). If one of the corrective actions has previously been attempted, proceed to the next one in the list.
- Review the device enclosure cabling and correct the cabling as required. To see example device configurations with SAS cabling, see Serial-attached SCSI cable planning, in the Site and hardware planning information.
- Reseat the cables, if present, on the adapter and the device enclosure. Perform the following steps:
  1. Use adapter concurrent maintenance to power off the adapter slot, or power off the system or partition.
  2. Reseat the cables.
  3. Use adapter concurrent maintenance to power on the adapter slot, or power on the system or partition.
- Replace the cable, if present, from the adapter to the device enclosure. Perform the following steps:
  1. Use adapter concurrent maintenance to power off the adapter slot, or power off the system or partition.
  2. Replace the cables.
  3. Use adapter concurrent maintenance to power on the adapter slot, or power on the system or partition.
- Replace the internal device enclosure or refer to the service documentation for an external expansion drawer. Perform the following steps:
  1. Power off the system or partition. If the enclosure is external, use adapter concurrent maintenance instead to power off the adapter slot.
  2. Replace the device enclosure.
  3. Power on the system or partition. If the enclosure is external, adapter concurrent maintenance can be used instead to power on the adapter slot.
- Replace the adapter. The procedure to replace the adapter can be found in PCI adapter .
- Contact your service provider.
To determine if the problem still exists for the adapter that logged this error, examine the SAS connections by performing the actions in step 2 again. Do all expected devices appear in the list and are all paths marked as Operational?
- No: Go to step 5.
- Yes: The error condition no longer exists. This ends the procedure..