MAP 0285

Use this MAP to handle SRN A23-001 and ssss-640 (where ssss is the 3 or 4 digit Failing Function Code (FFC) of an SCSD drive) to check the path from adapter to device.

For more information about failing part numbers, location codes, or removal and replacement procedures, see Part locations and location codes. Select your machine type and model number to see applicable procedures for your system.

Note: Not all devices support MPIO. Before proceeding with this MAP, make sure that the devices on both ends of the missing path support MPIO.
  • Step 0285-1

    Look at the problem report screen for the missing path. After the resource name and FRU, the next column identifies the missing path between resources (for example, scsi0 -> hdisk1). This indicates the missing path between the two resources, scsi0 (the parent resource) and hdisk1 (the child resource).

    Is the cabling present between the two resources?
    No
    Go to Step 0285-2.
    Yes
    Go to Step 0285-4.
    Note: In the following MAP steps, if no path previously existed between a parent and child device, the child device will have to be changed from the defined to the available state, otherwise you will be unable to select the child device to which you want to establish a path.
  • Step 0285-2
    1. Power off the system.
    2. Connect the correct cable between the two resources.
    3. Power on the system.
    4. At the command line, type smitty mpio.
    5. Choose MPIO Path Management.
    6. Select Enable Paths.
    7. Select Enable Paths for a Device.
    8. In the Device Name selection, choose the name of the child device (the device at the end of the path).
    9. In the Paths to Enable selection, select the missing path (between the parent and child device).
    10. Press Enter.
    Did the smitty menu complete with no errors?
    No
    Go to Step 0285-4.
    Yes
    Go to Step 0285-3.
  • Step 0285-3

    To verify that the device path is present, rerun diag -a.

    When the resource list displays, select the child resource that had the missing path. If the letter P is shown in front of the resource, you still have a path problem. If no letter P is shown in front of the resource or if the system returns to the command prompt or you get a message without the resource list being displayed, then the problem has been resolved.

    Do you still have a path problem?
    No
    Go to Verifying a repair.
    Yes
    Go to Step 0285-4.
  • Step 0285-4
    1. Power off the system.
    2. Reseat the cables between the device and the adapter that have the missing path.
    3. Power on the system.
    4. At the command line, type smitty mpio.
    5. Choose MPIO Path Management.
    6. Select Enable Paths.
    7. Select Enable Paths for a Device.
    8. In the Device Name selection, choose the name of the child device (the device at the end of the path).
    9. In the Paths to Enable selection, select the missing path (between the parent and child device).
    10. Press Enter.
    Did the smitty menu complete with no errors?
    No
    Go to Step 0285-6.
    Yes
    Go to Step 0285-5.
  • Step 0285-5

    To verify that the device path is present, rerun diag -a

    When the resource list displays, select the child resource that had the missing path. If the letter P is shown in front of the resource, you still have a path problem. If no letter P is shown in front of the resource or if the system returns to the command prompt or you get a message without the resource list being displayed, then the problem has been resolved.

    Do you still have a path problem?
    No
    Go to Verifying a repair.
    Yes
    Go to Step 0285-6.
  • Step 0285-6

    You may have a problem with the driver interface or connector on either the parent or child device.

    1. Power off the system (see the system service information if necessary).
    2. Remove the cables to the parent device.
    3. Replace the cables that go between the parent and child device (if present).
    4. Reattach the cables to the parent device.
    5. Power on the system.
    6. At the command line, type smitty mpio.
    7. Choose MPIO Path Management.
    8. Select Enable Paths.
    9. Select Enable Paths for a Device.
    10. In the Device Name selection, choose the name of the child device (the device at the end of the path).
    11. In the Paths to Enable selection, select the missing path (between the parent and child device).
    12. Press Enter.
    Did the smitty menu complete with no errors?
    No
    Go to Step 0285-7.
    Yes
    Go to Step 0285-8.
  • Step 0285-7

    To verify that the device path is present, rerun diag -a.

    When the resource list displays, select the child resource that had the missing path. If the letter P is shown in front of the resource, you still have a path problem. If the letter P is not shown in front of the resource, or if the system returns to the command prompt, or you get a message without the resource list being displayed, then the problem has been resolved.

    Do you still have a problem?

    No
    Go to Verifying a repair.
    Yes
    Go to Step 0285-8.
  • Step 0285-8

    You may have a problem with the driver interface or connector on either the parent or child device.

    1. Power off the system.
    2. Remove the cables to the parent device.
    3. Replace the parent device.
    4. Reattach the cables to the parent device.
    5. Power on the system.
    6. At the command line, type smitty mpio.
    7. Choose MPIO Path Management.
    8. Select Enable Paths.
    9. Select Enable Paths for a Device.
    10. In the Device Name selection, choose the name of the child device (the device at the end of the path).
    11. In the Paths to Enable selection, select the missing path (between the parent and child device).
    12. Press Enter.
    Did the smitty menu complete with no errors?
    No
    Go to Step 0285-9.
    Yes
    Go to Step 0285-10.
  • Step 0285-9

    To verify that the device path is present, rerun diag -a.

    When the resource list displays, select the child resource that had the missing path. If the letter P is shown in front of the resource, you still have a path problem. If no letter P is shown in front of the resource or if the system returns to the command prompt or you get a message without the resource list being displayed, then the problem has been resolved.

    Do you still have a path problem?
    No
    Go to Verifying a repair.
    Yes
    Go to Step 0285-10.
  • Step 0285-10

    You may have a problem with the driver interface or connector on the child device.

    1. Power off the system.
    2. Remove the cables to the child device.
    3. Replace the child device (in the case of a SCSI or SAF-TE backplane, replace the backplane first, followed by the child device).
    4. Reattach the cables to the child device.
    5. Power on the system.
    6. At the command line, type smitty mpio.
    7. Choose MPIO Path Management.
    8. Select Enable Paths.
    9. Select Enable Paths for a Device.
    10. In the Device Name selection, choose the name of the child device (the device at the end of the path).
    11. In the Paths to Enable selection, select the missing path (between the parent and child device).
    12. Press Enter.
    Did the smitty menu complete with no errors?
    No
    Neither the cabling, nor the parent, nor the child seem to be causing the problem. Contact your service support structure.
    Yes
    Go to Step 0285-11.
  • Step 0285-11

    Rerun diag -a to verify that the device path is present.

    When the resource list displays, select the child resource that had the missing path. If the letter P is shown in front of the resource, you still have a path problem. If no letter P is shown in front of the resource or if the system returns to the command prompt or you get a message without the resource list being displayed, then the problem has been resolved.

    Do you still have a path problem?
    No
    Go to Verifying a repair.
    Yes
    Neither the cabling, nor the parent, nor the child seem to be causing the problem. Contact your service support structure.
Parent topic: Isolating problems on servers that run AIX or Linux


Last updated: Wed, June 19, 2019