POWER7 information

Linux server or Linux partition symptoms

Use the following tables to find the symptom you are experiencing. If you cannot find your symptom, contact your next level of support.

Choose the description that best describes your situation:

You have a service action to perform
Integrated Virtualization Manager (IVM) problem
An LED is not operating as expected
Control (operator) panel problems
Reference codes
Management consoles
There is a display or monitor problem (for example, distortion or blurring)
Power and cooling problems
Other symptoms or problems

You have a service action to perform

Symptom	What you should do:
You have an open service event in the service action event log.	Go to Starting a repair action.
You have parts to exchange or a corrective action to perform.	Go to the remove and replace procedures for your specific system. Go to Close of call procedure.
You need to verify that a part exchange or corrective action corrected the problem.	Go to Verifying the repair. Go to the Close of call procedure.
You need to verify correct system operation.	Go to Verifying the repair. Go to the Close of call procedure.

Integrated Virtualization Manager (IVM) problem

Symptom	What you should do:
The partitions do not activate - partition configuration is damaged	Restore the partition configuration data using IVM. See Backing up and restoring partition data
Other partition problems when the server is managed by IVM	Perform Troubleshooting with the Integrated Virtualization Manager

An LED is not operating as expected

Symptom	What you should do:
The system attention LED on the control panel is on.	Go to Linux fast-path problem isolation.
The rack identify LED does not operate properly.	Go to the Linux fast-path problem isolation.
The rack indicator LED does not turn on, but a drawer identify LED is on.	Make sure the rack indicator LED is properly mounted to the rack. Make sure that the rack identify LED is properly cabled to the bus bar on the rack and to the drawer identify LED connector. Replace the following parts one at a time: Rack LED to bus bar cable LED bus bar to drawer cable LED bus bar Contact your next level of support

Control (operator) panel problems

Symptom	What you should do:
01 does not appear in the upper-left corner of the operator panel display after the power is connected and before pressing the power-on button. Other symptoms appear in the operator panel display or LEDs before the power on button is pressed.	Go to Power problems.
A bouncing or scrolling ball (moving row of dots) remains on the operator panel display, or the operator panel display is filled with dashes or blocks.	Verify that the operator panel connections to the system backplane are connected and properly seated. Also, reseat the Service Processor card. If a client computer (such as a PC with Ethernet capability and a Web browser) is available, connect it to the service processor in the server that is displaying the symptom. To connect a personal computer with Ethernet capability and a Web browser, or an ASCII terminal, to access the Advanced System Management Interface (ASMI), go to Managing your server using the Advanced System Management Interface. If you can successfully access the ASMI, replace the operator panel assembly. Refer to Finding parts, locations, and addresses to determine the part number and correct exchange procedure. If you cannot successfully access the ASMI, replace the service processor. Refer to Finding parts, locations, and addresses to determine the part number and correct exchange procedure. If you do not have a PC or ASCII terminal, replace the following one at a time (go to Finding parts, locations, and addresses to determine the part number and correct exchange procedure): Operator panel assembly. Service processor.
You have a blank display on the operator panel. Other LEDs on the operator panel appear to behave normally.	Verify that the operator panel connections to the system backplane are connected and properly seated. If a client computer (such as a PC with Ethernet capability and a Web browser) is available, connect it to the service processor in the server that is displaying the symptom. To connect a personal computer with Ethernet capability and a Web browser, or an ASCII terminal, to access the Advanced System Management Interface (ASMI), go to Managing your server using the Advanced System Management Interface. If you can successfully access the ASMI, replace the operator panel assembly. Refer to Finding parts, locations, and addresses to determine the part number and correct exchange procedure. If you cannot successfully access the ASMI, replace the service processor. Refer to Finding parts, locations, and addresses to determine the part number and correct exchange procedure. If you do not have a PC or ASCII terminal, replace the following one at a time (go to Finding parts, locations, and addresses to determine the part number and correct exchange procedure): Control (operator) panel assembly. Service processor.
You have a blank display on the operator panel. Other LEDs on the operator panel are off.	Go to Power problems.

Reference codes

Symptom	What you should do:
You have an 8-digit error code displayed.	Look up the reference code in the Reference codes section of the information center. Note: If the repair for this code does not involve replacing a FRU (for instance, running an AIX® command that fixes the problem or changing a hot-pluggable FRU), then update the AIX error log after the problem is resolved by performing the following steps: In the online diagnostics, select Task SelectionLog Repair Action. Select resource sysplanar0. On systems with a fault indicator LED, this changes the "fault indicator" LED from the "fault" state to the "normal" state.
The system stops with an 8-digit error code displayed when booting.	Look up the reference code in the Reference codes section of the information center.
The system stops and a 4-digit code displays on the control panel that does not begin with 0 or 2.	Look up the reference code in the Reference codes section of the information center.
The system stops and a 4-digit code displays on the control panel that begins with 0 or 2 is displayed in the operator panel display.	Record SRN 101-xxxx where xxxx is the 4-digit code displayed in the control panel, then look up this reference code in the Reference codes section of the information center. Follow the instructions given in the Description and Action column for your SRN.
The system stops and a 3-digit number displays on the control panel.	Add 101– to the left of the three digits to create an SRN, then look up this reference code in the Reference codes section of the information center. Follow the instructions given in the Description and Action column for your SRN. If there is a location code displayed under the 3-digit error code, look at the location to see if it matches the failing component that the SRN pointed to. If they do not match, perform the action given in the error code table. If the problem still exists, then replace the failing component from the location code. If there is a location code displayed under the 3-digit error code, record the location code. Record SRN 101-xxx, where xxx is the 3-digit number displayed in the operator panel display, then look up this reference code in the Reference codes section of the information center. Follow the instructions given in the Description and Action column for your SRN.

Management consoles

Symptom	What you should do:
The management console cannot be used to manage a managed system, or the connection to the managed system is failing.	If the managed system is operating normally (no error codes or other symptoms), the management console might have a problem, or the connection to the managed system might be damaged or incorrectly cabled. Do the following: Check the connections between the management console and the managed system. Correct any cabling errors if found. If another cable is available, connect it in place of the existing cables and refresh the management console interface. You may have to wait up to 30 seconds for the managed system to reconnect. Verify that any connected management console is connected to the managed system by checking the Management Environment of the management console. Note: The managed system must have power connected and the system running, or waiting for a power-on instruction (`01` is in the upper-left corner of the operator panel.) If the managed system does not appear in the Navigation area of the management console Management Environment, the management console or the connection to the managed system might be failing. Go to the For HMC: Managing the HMC section. For SDMC: Managing the SDMC section. There might be a problem with the service processor card or the system backplane. If you cannot fix the problem using the HMC tests in the Managing the HMC section: If you cannot fix the problem using the SDMC tests in the Managing the SDMC section: Replace the service processor card. Refer to the remove and replace procedures for your specific system. Replace the management console system backplane. Refer to the remove and replace procedures for your specific system.
The management console (HMC only) cannot call out using the attached modem and the customer's telephone line.	If the managed system is operating normally (no error codes or other symptoms), the management console might have a problem, or the connection to the modem and telephone line might have a problem. Do the following: Check the connections between the management console, the modem, and the telephone line. Correct any cabling errors, if found. Go to the Managing your server using the Hardware Management Console section.

Symptom

What you should do:

The management console cannot be used to manage a managed system, or the connection to the managed system is failing.

If the managed system is operating normally (no error codes or other symptoms), the management console might have a problem, or the connection to the managed system might be damaged or incorrectly cabled. Do the following:

Check the connections between the management console and the managed system. Correct any cabling errors if found. If another cable is available, connect it in place of the existing cables and refresh the management console interface. You may have to wait up to 30 seconds for the managed system to reconnect.
Verify that any connected management console is connected to the managed system by checking the Management Environment of the management console.
Note: The managed system must have power connected and the system running, or waiting for a power-on instruction (01 is in the upper-left corner of the operator panel.)

If the managed system does not appear in the Navigation area of the management console Management Environment, the management console or the connection to the managed system might be failing.
Go to the
- For HMC: Managing the HMC section.
- For SDMC: Managing the SDMC section.
There might be a problem with the service processor card or the system backplane.
If you cannot fix the problem using the HMC tests in the Managing the HMC section:

If you cannot fix the problem using the SDMC tests in the Managing the SDMC section:
1. Replace the service processor card. Refer to the remove and replace procedures for your specific system.
2. Replace the management console system backplane. Refer to the remove and replace procedures for your specific system.

The management console (HMC only) cannot call out using the attached modem and the customer's telephone line.

If the managed system is operating normally (no error codes or other symptoms), the management console might have a problem, or the connection to the modem and telephone line might have a problem. Do the following:

Check the connections between the management console, the modem, and the telephone line. Correct any cabling errors, if found.
Go to the Managing your server using the Hardware Management Console section.

There is a display problem (for example, distortion or blurring)

Symptom	What you should do:
All display problems.	If you are using the management console: Hardware Management Console: Go to the Managing the HMC section. Systems Director Management Console: Go to the Managing the SDMC section. If you are using a graphics display: Go to the problem determination procedures for the display. If you do not find a problem: Replace the graphics display adapter. Refer to the remove and replace procedures for your specific system. Replace the backplane into which the graphics display adapter is plugged. Refer to the remove and replace procedures for your specific system.
There appears to be a display problem (distortion, blurring, and so on)	Go to the problem determination procedures for the display.

Symptom

What you should do:

All display problems.

If you are using the management console:
- Hardware Management Console: Go to the Managing the HMC section.
- Systems Director Management Console: Go to the Managing the SDMC section.
If you are using a graphics display:
1. Go to the problem determination procedures for the display.
2. If you do not find a problem:
  - Replace the graphics display adapter. Refer to the remove and replace procedures for your specific system.
  - Replace the backplane into which the graphics display adapter is plugged. Refer to the remove and replace procedures for your specific system.

There appears to be a display problem (distortion, blurring, and so on)

Go to the problem determination procedures for the display.

Power and cooling problems

Symptom	What you should do:
The system will not power on and no error codes are available.	Go to Power problems.
The power LEDs on the operator panel and the power supply do not come on or stay on.	Check the service processor error log. Go to Power problems.
The power LEDs on the operator panel and the power supply come on and stay on, but the system does not power on.	Check the service processor error log. Go to Power problems.
A rack or a rack-mounted unit will not power on.	Check the service processor error log. Go to Power problems.
The cooling fan(s) do not come on, or come on but do not stay on.	Check the service processor error log. Go to Power problems.
The system attention LED on the operator panel is on and there is no error code displayed.	Check the service processor error log. Go to Power problems.

Other symptoms or problems

Symptom	What you should do:
The system stopped and a code is displayed on the operator panel.	Go to Starting a repair action.
`01` is displayed in the upper-left corner of the operator panel and the fans are off.	The service processor is ready. The system is waiting for power-on. Boot the system. If the boot is unsuccessful, and the system returns to the default display (indicated by `01` in the upper-left corner of the operator panel), go to MAP 0020: Problem determination procedure.
The operator panel displays STBY.	The service processor is ready. The server was shut down by the operating system and is still powered on. This condition can be requested by a privileged system user with no faults. Go to Starting a repair action. Note: See the service processor error log for possible operating system fault indications.
All of the system POST indicators are displayed on the firmware console, the system pauses and then restarts. The term POST indicators refers to the device mnemonics (the words `memory`, `keyboard`, `network`, `scsi`, and `speaker`) that appear on the firmware console during the power-on self-test (POST).	Go to Problems with loading and starting the operating system.
The system stops and all of the POST indicators are displayed on the firmware console. The term POST indicators refers to the device mnemonics (the words `memory`, `keyboard`, `network`, `scsi`, and `speaker`) that appear on the firmware console during the power-on self-test (POST).	Go to Problems with loading and starting the operating system.
The system stops and the message `starting software please wait...`is displayed on the firmware console.	Go to Problems with loading and starting the operating system.
The system does not respond to the password being entered or the system login prompt is displayed when booting in service mode.	If the password is being entered from the management console: For Hardware Management Console (HMC): Go to the Managing the HMC. For Systems Director Management Console (SDMC): Go to the Managing the SDMC. If the password is being entered from a keyboard attached to the system, the keyboard or its controller may be faulty. In this case, replace these parts in the following order: Keyboard Service processor If the problem is fixed, go to MAP 0410: Repair checkout.
The system stops with a prompt to enter a password.	Enter the password. You cannot continue until a correct password has been entered. When you have entered a valid password, go to the beginning of this table and wait for one of the other conditions to occur.
The system does not respond when the password is entered.	Go to Step 1020-2.
No codes are displayed on the operator panel within a few seconds of turning on the system. The operator panel is blank before the system is powered on.	Reseat the operator panel cable. If the problem is not resolved, replace in the following order: Operator panel assembly. Refer to the remove and replace procedures for your specific system Service processor. Refer to the remove and replace procedures for your specific system. If the problem is fixed, go to MAP 0410: Repair checkout. If the problem is still not corrected, go to MAP 0020: Problem determination procedure.
The SMS configuration list or boot sequence selection menu shows more SCSI devices attached to a controller/adapter than are actually attached.	A device may be set to use the same SCSI bus ID as the control adapter. Note the ID being used by the controller/adapter (this can be checked and/or changed through an SMS utility), and verify that no device attached to the controller is set to use that ID. If settings do not appear to be in conflict: Go to MAP 0020: Problem determination procedure. Replace the SCSI cable. Replace the device. Replace the SCSI adapter Note: In a "twin-tailed" configuration where there is more than one initiator device (normally another system) attached to the SCSI bus, it may be necessary to use SMS utilities to change the ID of the SCSI controller or adapter.
You suspect a cable problem.	Go to Adapters, Devices and Cables for Multiple Bus Systems.
You have a problem that does not prevent the system from booting. The operator panel is functional and the rack indicator LED operates as expected.	Go to MAP 0020: Problem determination procedure.
All other symptoms.	Go to MAP 0020: Problem determination procedure.
All other problems.	Go to MAP 0020: Problem determination procedure.
You do not have a symptom.	Go to MAP 0020: Problem determination procedure.
You have parts to exchange or a corrective action to perform.	Go to Starting a repair action. Go to Close of call procedure.
You need to verify that a part exchange or corrective action corrected the problem.	Go to MAP 0410: Repair checkout.
You need to verify correct system operation.	Go to MAP 0410: Repair checkout.
The system stopped. A POST indicator is displayed on the system console and an eight-digit error code is not displayed.	If the POST indicator represents: Memory, go to PFW 1548: Memory and processor subsystem problem isolation procedure. Keyboard Replace the keyboard. Replace the service processor, location: model dependent. Go to PFW 1548: Memory and processor subsystem problem isolation procedure. Network, go to PFW 1548: Memory and processor subsystem problem isolation procedure. SCSI, go to PFW 1548: Memory and processor subsystem problem isolation procedure. Speaker Replace the control panel. The location is model dependent; refer to Installing features. Replace the service processor. The location is model dependent. Go to PFW 1548: Memory and processor subsystem problem isolation procedure.
The diagnostic operating instructions are displayed.	Go to MAP 0020: Problem determination procedure.
The system login prompt is displayed.	If you are loading the diagnostics from a CD-ROM, you may not have pressed the correct key or you may not have pressed the key soon enough when you were trying to indicate a service mode IPL of the diagnostic programs. If this is the case, start again at the beginning of this step. Note: Perform the system shutdown procedure before turning off the system. If you are sure you pressed the correct key in a timely manner, go to Step 1020-2. If you are loading diagnostics from a Network Installation Management (NIM) server, check for the following: The bootlist on the client may be incorrect. Cstate on the NIM server may be incorrect. There may be network problems preventing you from connecting to the NIM server. Verify the settings and the status of the network. If you continue to have problems refer to Problems with loading and starting the operating system and follow the steps for network boot problems.
The System Management Services (SMS) menu is displayed when you were trying to boot standalone diagnostics.	If you are loading diagnostics from the CD-ROM, you may not have pressed the correct key when you were trying to indicate a service mode IPL of the diagnostic programs. If this is the case, try to boot the CD-ROM again and press the correct key. If you are sure you pressed the correct key, the device or media you are attempting to boot from may be faulty. Try to boot from an alternate boot device connected to the same controller as the original boot device. If the boot succeeds, replace the original boot device (for removable media devices, try the media first). If the boot fails, go to problems with loading and starting the operating system. Go to PFW 1548: Memory and processor subsystem problem isolation procedure.
The SMS boot sequence selection menu or remote IPL menu does not show all of the bootable devices in the partition or system.	If an AIX or Linux partition is being booted, verify that the devices that you expect to see in the list are assigned to this partition. If they are not, use the management console to reassign the required resources. If they are assigned to this partition, go to Problems with loading and starting the operating system to resolve the problem.

Send feedback Rate this page

Last updated: Thu, September 25, 2014