POWER7 information

SIP4144

Use this procedure to resolve problems with multipath connections.

This procedure is used to resolve the following configuration errors:

Configuration error, incorrect multipath connection (SRC xxxx4030)
Configuration error, incomplete multipath connection between adapter and enclosure detected (SRC xxxx4040)

The possible causes are:

Incorrect cabling to device enclosure.
Note: Pay special attention to the requirement that a YI-cable must be routed along the right side of the rack frame (as viewed from the rear) when connecting to a disk expansion unit. Review the device enclosure cabling and correct the cabling as required. To see example device configurations with serial attached SCSI (SAS) cabling, see Serial-attached SCSI cable planning, in the Site and hardware planning .
A failed connection caused by a failing component in the SAS fabric between, and including, the adapter and device enclosure.

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. 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 backplane and use a cache RAID and dual IOA enablement card to enable storage adapter write cache and dual storage I/O adapter (IOA) mode. For these configurations, replacement of the cache RAID and dual IOA enablement card is unlikely to solve a SAS-related problem because the SAS interface logic is on the system backplane.
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: When SAS fabric problems exist, do not replace RAID adapters without assistance from your service provider. Because the adapter might contain non-volatile write cache data and configuration data for the attached disk arrays, additional problems can be created by replacing an adapter. Follow appropriate service procedures when replacing the cache RAID and dual IOA Enablement Card. Incorrect removal can result in data loss or a nondual storage IOA mode of operation.

Was the SRC xxxx4030?
No:

Go to step 4.

Yes:

Go to step 2.
Review the device enclosure cabling and correct the cabling as required for the device or device enclosure attached to the identified adapter port. To see example device configurations with SAS cabling, see Serial-attached SCSI cable planning, in the Site and hardware planning information.
Perform the following steps to cause the adapter to rediscover the devices and connections:
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.
Did the error recur?
No:

This ends the procedure.

Yes:

Contact your hardware service provider. This ends the procedure.
The SRC is xxxx4040. Is the IBM® i operating system at Version 6.1.1 or later?
- No: Continue with the next step.
- Yes: Go to step 6.
Determine whether 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) screen, select Start a Service Tool 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: Go to step 7.
  - 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. 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:
1. Use Hardware Service Manager to re-IPL the virtual I/O processor that is associated with this adapter.
2. Vary on any other resources attached to the virtual I/O processor.
Note: At this point, ignore any problems found and continue with the next step.
Determine if the problem still exists for the adapter that logged this error by examining the SAS connections by performing the actions in step 5 or step 6 again.
Do all expected devices appear in the list and are all paths marked as Operational?
No

Go to step 9.

Yes

This ends the procedure.
Go to SAS fabric identification. Then continue with the next step.
To determine if the problem still exists for the adapter that logged this error, examine the SAS connections by performing the actions in step 5 or step 6 again. Do all expected devices appear in the list and are all paths marked as Operational?
No:

Go to step 9.

Yes:

This ends the procedure.

Send feedback Rate this page

Last updated: Thu, July 23, 2015