SIP3143

Use this procedure to resolve the following problem: Configuration error, connections exceed adapter design limits (SRC xxxx4020)

The possible causes are:

Considerations:

  1. Identify the affected adapter and its port by examining the Product Activity Log. Perform the following:
    1. Access SST/DST.
      • If you can enter a command at the console, access system service tools (SST). See System Service Tools (SST).
      • If you cannot enter a command at the console, perform an IPL to DST. See Performing an IPL to DST.
      • If you cannot perform a type A or B IPL, perform a type D IPL from removable media.
    2. Access the Product Activity Log and record address information.
      If a D IPL was NOT performed to get to SST/DST:
      The log information is formatted. Access the Product Activity Log and display the SRC that sent you here. Press the F9 key for Address Information. This is the adapter address. Then, press F12 to cancel and return to the previous screen. Then press the F4 key to view the "Additional Information" to record the formatted log information. The Adapter Port field indicates the port on the adapter reporting the problem. There may be more than one port listed, since multiple ports map to the same physical connector. For example, ports 0 through 3 map to the first physical connector, 4 through 7 map to the second physical connector, and so on. The port numbers are labelled on the adapter tailstock.
      If a D IPL was performed to get to DST:
      The log information is not formatted. Access the Product Activity Log and display the SRC that sent you here. The direct select address (DSA) of the adapter is in the format BBBB-Cc-bb:
      BBBB
      hexadecimal offsets 4C and 4D
      Cc
      hexadecimal offset 51
      bb
      hexadecimal offset 4F

      In order to interpret the hexadecimal information to get device addresses, see More information from hexadecimal reports. The Adapter Port field indicates the port on the adapter reporting the problem. There might be more than one port listed, since multiple ports map to the same physical connector. For example, ports 0 through 3 map to the first physical connector, 4 through 7 map to the second physical connector, and so on. The port numbers are labelled on the adapter tailstock.

    3. Determine the location of the adapter that reported the problem. See Locating FRUs and find the diagram of the system unit, or the expansion unit. Then find the following:
      • The card slot that is identified by the adapter direct select address (DSA).
      • The physical connector identified by the port number found on the adapter tailstock.
      Have you determined the location of the adapter and its port?
      • No: Ask your next level of support for assistance. This ends the procedure.
      • Yes: Continue with the next step.
  2. Reduce the number of cascaded device enclosures. Device enclosures may only be cascaded one level deep, and only in certain configurations. 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 Guide, order number SA76-0091.
  3. Perform the following 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.
    Did the error reoccur?
    No:
    This ends the procedure.
    Yes:
    Contact your hardware service provider. This ends the procedure.