SIP3145

Use this procedure to resolve the following problem: Unsupported enclosure function detected (SRC xxxx4110).

The possible causes are:
  • Device enclosure or adapter code levels are not up to date.
  • Unsupported type of device enclosure or device. For example, this error can occur if a SATA device, such as a DVD drive, is attached to certain levels of a CCIN 57B4 adapter. The initial levels of the CCIN 57B4 adapter did not support SATA devices. To determine whether an adapter supports SATA devices, see PCIe2 SAS RAID card comparison or PCIe3 SAS RAID card comparison.
Considerations:

To prevent hardware damage or erroneous diagnostic results, remove power from the system as appropriate before connecting and disconnecting cables or devices.

  1. Identify the affected adapter and its port by examining the product activity log. Perform the following steps:
    1. Access SST or DST.
    2. Access the product activity log and record address information.
      If a type D IPL was not performed to get to SST or 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 that is reporting the problem. There may be more than one port listed because 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 labeled on the adapter tailstock.
      If a type 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-xxxx:
      BBBB
      Hexadecimal offsets 4C and 4D
      xxxx
      Not used

      In order to interpret the hexadecimal information to get device addresses, see Examples: Obtaining additional 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 because 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 labeled on the adapter tailstock.

    3. Determine the location of the adapter that reported the problem. Go to Addresses and find the following items:
      • The card slot that is identified by the 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. Check for the latest PTFs for the device enclosure or adapter and apply them. If you need assistance finding PTFs, contact your next level of support. If unsupported device enclosures or devices are attached, then either remove or replace them with supported device enclosures or devices.

    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.

  3. 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 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.



Last updated: Wed, June 19, 2019