POWER7 information

SIP3146

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

If you need additional information for failing part numbers, location codes, or removal and replacement procedures, see Part locations and location codes. Select your machine type and model number to find additional location codes, part numbers, or replacement procedures for your system.

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: Do not remove functioning disk units in a disk array 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 steps:
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 the Hardware Service Manager to determine the resource name of the adapter that is controlling this disk unit. The logical bus number of the disk-unit logical resource might be useful in determining the adapter resource name.
Is the IBM® i operating system at Version 6.1.1 or later?
- No: Continue with the next step.
- Yes: Go to step 4.
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 press Enter.
2. Select Display/Alter/Dump > Display/Alter storage > Licensed Internal Code (LIC) data > Advanced Analysis.
3. Type FABQUERY on the entry line and then select it with option 1.
4. On the Specify Advanced Analysis Options display, 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 display and typing -SUB 01 -IOA DCxx -DSP 2 in the Options field, where DCxx is the adapter resource name. Press Enter.
  Are all of the following statements true?
  - All expected devices appear in the list.
  - All paths are marked as Operational.
  - None of the paths are blank.
  - No: Go to step 5.
  - Yes: The error condition no longer exists. This ends the procedure.
Determine whether a problem still exists for the DCxx adapter resource that logged this error by examining the SAS connections. See Viewing SAS fabric path information. Are all of the following statements true?
- All expected devices appear in the list.
- All paths are marked as Operational.
- None of the paths are blank.
- 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 the system partition to temporarily hang. Wait until the system bypasses the temporary hang.
1. Use the logical resources IO debug option in 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 that are attached to the virtual I/O processor.
To determine whether the problem still exists for the adapter that logged this error, check the product activity log to determine whether any new errors were logged for the same resource that was identified in step 1. Also, examine the SAS connections by performing the actions in step 3 or step 4 again. Are all of the following statements true?
- All expected devices appear in the list.
- All paths are marked as Operational.
- None of the paths are blank.
- No new errors are logged in the product activity log for the resource.
- 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) and then continue with step 8. 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, device enclosure, and any additional device enclosures connected to the device enclosure. Perform the following steps:
  1. Using Hardware Service Manager packaging resources, perform adapter concurrent maintenance to power off the adapter slot, or power off the system or partition.
  2. Reseat the cables.
  3. Using Hardware Service Manager packaging resources, perform 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, and any cables between the device enclosure and additional device enclosures connected to the device enclosure. Perform the following steps:
  1. Using Hardware Service Manager packaging resources, perform adapter concurrent maintenance to power off the adapter slot, or power off the system or partition.
  2. Replace the cables.
  3. Using Hardware Service Manager packaging resources, perform adapter concurrent maintenance to power on the adapter slot, or power on the system or partition.
- Replace the internal device enclosure or see the service documentation for an external expansion unit. 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 failing items. See SASEXP and DEVBPLN for possible failing items to replace.
  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 device.
- Contact your service provider.
To determine whether the problem still exists for the adapter that logged this error, check the product activity log to determine whether any new errors were logged for the same resource that was identified in step 1. Also, examine the SAS connections by performing the actions in step 3 or step 4 again. Are all of the following statements true?
- All expected devices appear in the list.
- All paths are marked as Operational.
- None of the paths are blank.
- No new errors are logged in the product activity log for the resource.
- No: Go to step 7.
- Yes: The error condition no longer exists. This ends the procedure.

Send feedback Rate this page

Last updated: Thu, July 23, 2015