Isolation procedures

Isolation procedures are used together with diagnostic programs, which are part of server firmware.

If a server is connected to a management console, these procedures are available on the management console. Use the management console procedures to continue isolating the problem. If the server does not have a management console and you are directed to perform an isolation procedure, the procedures documented here are needed to continue isolating a problem.

The procedures and functions of the HMC Enhanced + Tech Preview (Pre-GA) login option and interface type, which was provided with the Hardware Management Console (HMC) version 8.2.0, are the same as the HMC Enhanced+ login option and interface type that is provided with HMC version 8.3.0 and later. Only the HMC Enhanced+ is referred to in the documentation, but that content also applies to the HMC Enhanced + Tech Preview (Pre-GA) interface.

Communication isolation procedure
Isolate a communications failure.
Disk unit isolation procedure
Provides a procedure to isolate a failure in a disk unit.
EMX0 PCIe3 expansion drawer isolation procedures
Use the following procedures to resolve a problem with an EMX0 PCIe3 expansion drawer.
Intermittent isolation procedures
These procedures help you to correct an intermittent problem.
I/O processor isolation procedures
Isolate a failure in the multiple function I/O card.
Licensed Internal Code isolation procedures
Use this section to isolate Licensed Internal Code problems.
Logical partition isolation procedure
Identify logical partition (LPAR) configuration conditions and the associated corrective actions.
Operations console isolation procedures
These procedures help you to isolate a failure with the Operations Console.
PCI bus isolation procedures
Use PCI bus isolation procedures if there is not a management console attached to the server. If the server is connected to a management console, use the procedures that are available on the management console to continue FRU isolation.
Power isolation procedures
Use power isolation procedures for isolating a problem in the power system. Use isolation procedures if there is not a management console attached to the server. If the server is connected to a management console, use the procedures that are available on the management console to continue FRU isolation.
Router isolation procedures
These procedures serve as a guide to the correct isolation procedures from the reference code tables.
Serial-attached SCSI isolation procedures
Use serial-attached SCSI (SAS) isolation procedures when a management console is not attached to the server. If the server is connected to a management console, use the procedures that are available on the management console to continue FRU isolation.
Service processor isolation procedures
Use service processor isolation procedures if there is not a management console attached to the server. If the server is connected to a management console, use the procedures that are available on the management console to continue FRU isolation.
Tape unit isolation procedures
This topic contains the procedures necessary to isolate a failure in a tape device.
Twinaxial workstation I/O processor isolation procedure
Use the procedure below to isolate a failure which has been detected by the twinaxial workstation I/O processor. If you are using a personal computer, an emulation program must be installed and working.
Workstation adapter isolation procedure
Isolates a failure that is detected by the workstation adapter, and is used when no display is available with which to perform on-line problem analysis.
Workstation adapter console isolation procedure
Contains the procedure necessary to isolate a failure that is detected by the workstation adapter console.
Isolating problems on servers that run AIX or Linux
Use the procedures for AIX® or Linux servers if there is not a management console attached to the server. If the server is connected to a management console, use the procedures that are available on the management console to continue FRU isolation.

Last updated: Wed, June 19, 2019