POWER5 information.

Troubleshooting problems when using the Thin Console

Learn how to solve some hardware and connection problems that might occur while using the Thin Console.

For problems concerning the Thin Console, your server, and the connection between the two, choose from the following options:

Troubleshooting hardware problems

Review the following table for hints and tips on how to resolve common problems that might occur when using the Thin Console. You can also refer to the documentation that came with your console device or see http://www.neoware.com/.

Table 1. Troubleshooting hardware problems
Symptom Problem and recovery tasks
The display of the Thin Console is completely blank. There might be a hardware problem with the Thin Console or monitor, or there might be a setup problem. Follow these steps to resolve the problem:
  1. Verify that the cabling is secure and accurate.
  2. Verify that the Thin Console and monitor are powered on.
  3. Reset the default monitor resolution setting. Refer to the documentation that came with the console device or see http://www.neoware.com/.
The keyboard is not working correctly. This might be a hardware problem or it might be that the keyboard is set to a location that does not match the current keyboard setting. Refer to the documentation that came with your console device or see http://www.neoware.com/.
You cannot view wide displays (such as spool files) using the 5250 console. Set the resolution of the Thin Console to 1024 x 768.

Troubleshooting, using the status codes

Review the following table for hints and tips on how to resolve common problems that might occur while the Thin Console is becoming active.

Table 2. Thin Console status codes
Symptom Recovery tasks
The status screen does not continue to display system status after you see 00.xx. The Thin Console is not able to find an active service processor. Complete these steps to resolve the problem:
  1. Verify that the Ethernet cable is plugged into either the HMC 1 or HMC 2 port on the back of the server.
  2. Verify that the Ethernet ports on both the server and the Thin Console are showing link-active and activity lights.
  3. Verify that the HMC port on the server is configured with either the 192.168.3.147 or the 192.168.2.147 IP address (manufacturing defaults). If the port is not configured using one of these IP addresses, see Restoring your server to factory settings.
  4. Verify that the service processor is powered on by noting whether the control panel display is active.
  5. Restart the Thin Console to see if the problem is reproducible.
  6. Isolate faulty hardware problems by using the other HMC port at the back of the server, using another Ethernet cable, or by using another Thin Console.
The status screen displays status code 10.xx, and then prompts you for the HMC access password. After entering the password, the user ID and password cannot be authenticated. Complete these steps to resolve the problem:
  1. Verify that the keyboard is set to a location that matches the current keyboard setting.
  2. Verify that the Caps Lock, Num Lock, Scroll Lock keys are off.
  3. Change the HMC access password to a new value by logging into ASMI as the administrator. See Changing ASMI passwords.
  4. Use a password with only uppercase English alphabetic characters. If this resolves the problem, contact Neoware customer support at http://www.neoware.com/support/support_request.html
The status screen does not continue to display system status after you see 10.xx or 20.xx. Complete these steps to resolve the problem:
  1. Verify that another Thin Console or an HMC is not connected alongside this Thin Console.
  2. Restart the Thin Console to see if the problem is reproducible.
The status screen does not continue to display system status after you see 30.xx. The Thin Console displays status code 30.xx until the console device is powered on and PHYP standby is reached. If the Thin Console remains in state 30.xx, then try restarting the console device. If the state is 0x0F and the status does not display system status after you see 30.xx, see Contacting IBM® service and support.
The status screen does not continue to display system status after you see 40.xx. Verify that another Thin Console or an HMC is not connected alongside this Thin Console. If so, disconnect the other console device or use it as the system console.
The status screen does not continue to display system status after you see 50.xx. Remaining in this state means that the Thin Console has completed initialization of the firmware communication and has not successfully started communication with the Licensed Internal Code in i5/OS®.
Connection progress stops at 60.00 (of 100) . The connection progress stops because console access is denied. This is normal when the console type value is not set to a 4. For instructions about how to change the console type value, see Changing consoles, interfaces, and terminals.