Use this procedure to resolve problems with multipath connections.
About this task
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.
- 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.
Procedure
- 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:
Note: Performing this step
causes the system partition to temporarily hang. Wait until the system
bypasses the temporary hang.
-
Use the logical resources I/O debug option in Hardware Service Manager to perform another IPL
of the virtual I/O processor that is associated with this adapter.
- 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. 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:
- Use Hardware Service Manager to re-IPL the virtual I/O processor
that is associated with this adapter.
- 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 4 again.
Do all expected devices appear in the list and are
all paths marked as Operational?
- No
- Go to step 7.
- 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 4 again.
Do all expected devices appear in the list and are all paths
marked as Operational?
- No:
- Go to step 7.
- Yes:
- This ends the procedure.