RIOIP01 Section-1: Main task
Procedure
- Were you directed here while working on a B700xxxx reference
code?
- Yes, go to step 4.
- No, continue with the next step.
- Are you working on a 520 or 570?
- Yes, go to step 4.
- No, continue with the next step.
- Were you sent here from a B600xxxx reference code?
- Yes, use the serviceable event view and the system service documentation to search for a B700xxxx reference code with the same last four characters reported at approximately the same time. If you find one, perform service on that reference code first, and when you close that problem, close this one as well. If you do not find one, continue with the next step.
- No, continue with the next step.
- Before powering down any system unit or expansion unit, work with the customer to end all subsystems in all of the partitions using each partition's console.
- From the partition control panel, IPL the system or partition
to Dedicated Service Tools (DST). Attention: Do not use function 21!
- Are all system and expansion units on the loop powered
on?
- Yes, go to step 8.
- No, continue with the next step.
- Perform the following:
- Power on all system and expansion units on the loop. If a frame cannot be powered on, perform the RIOIP01 Section-5: Cannot power on unit subtask below, and then continue with step 8.
- Was the HSL link error cleared up when the frames were
powered back on?
- Yes, go to Verifying the repair.
- No, continue with the next step.
- Perform the following:
- Access the Service Action Log (SAL) entry for this error; the field replaceable units (FRUs) should be listed there. Look for part numbers and descriptions for the FRUs containing the HSL port for two frames. There should also be a FRU for the cable between them. The locations information for the FRUs is the location of the failed ports on the failed link.
- Record the loop number from the SAL (if it is displayed
there in one of the FRU descriptions) or from the first four characters
of word 7 of the reference code. Go to Converting the loop number
to NIC port location labels to determine which HSL/RIO cables on the
system you are working with. Is this information in the
SAL?
- Yes, continue with the next step.
- No, perform RIOIP01 Section-6: Manually detecting the failed link below, and then continue with the next step of the main task.
- Is the cable connecting the failed ports an optical cable?
- Yes, continue with the next step.
- No, go to step 11.
- Perform the following:
- Clean the HSL cable connectors and ports using the tools and procedures in symbolic FRU OPT_CLN.
- To determine if cleaning the connectors and ports solved
the problem, perform RIOIP01 Section-6: Manually detecting the failed link below and return
to this point. Did the ports you were working on have a status of
"failed"?
- Yes, continue with the next step.
- No, the problem is fixed. Go to Verifying the repair. This ends the procedure.
- There are now three cases to consider. Continue
with the appropriate subtask of this procedure:
- The ports on both ends of the failed link are in different system units on the loop.
- The port on one end of the failed link is in a system unit and the port on the other end is in an I/O unit.
- The ports on both ends of the failed link are in an I/O unit.