Committing The Temp System Firmware Image; Solving Shared Bladecenter Resource Problems - IBM PS703 Service Manual

Committing the TEMP system firmware image

After updating the system firmware and successfully starting up the blade server from the TEMP image,
copy the TEMP image to the PERM image using the diagnostics program commit function.
Note: If you install the server firmware update permanently by committing the temporary firmware level
from the temporary side to the permanent side, the temporary and permanent sides contain the same
level of firmware. You cannot return to the level that was previously on the permanent side.
1. Load the diagnostics program. See "Running the diagnostics program" on page 179.
2. From the Function Selection menu, select Task Selection and press Enter.
3. From the Tasks Selection List menu, select Update and Manage System Flash and press Enter.
4. From the Update and Manage System Flash menu, select Commit the Temporary Image and press
Enter.
5. When the commit function is complete, press F3 until the Diagnostic Operating Instructions screen is
displayed; then press F3 again to exit the diagnostic program.

Solving shared BladeCenter resource problems

Problems with BladeCenter shared resources might appear to be in the blade server, but might actually be
a problem in a BladeCenter unit component.
This information provides procedures to help you isolate blade server problems from shared BladeCenter
resource problems.
If the problem is thought to be with a shared resource, see the online information center or the Problem
Determination and Service Guide or the Hardware Maintenance Manual and Troubleshooting Guide for your
BladeCenter unit, or see the documentation for BladeCenter unit components for additional information.
If the problem cannot be solved, see "Solving undetermined problems" on page 223.
To check the general function of shared BladeCenter resources, complete the following operations.
1. Verify that the BladeCenter unit has the required power modules installed and is connected to a
working power source.
2. Verify that power management is set correctly for your BladeCenter unit configuration.
3. Verify whether the problem is being experienced on more than one blade server.
4. Perform a test of the failing function on a blade server that is known to be operational.
5. Try the blade server in a different blade bay.
6. Try a blade server that is known to be operational in the blade bay with the failing blade server.
7. Verify that the blade server and the monitor are powered on.
8. Check for problems with the media tray (removable media drives and USB ports), as described in
"Solving shared media tray problems" on page 220.
9. Check for network connection problems, as described in "Solving shared network connection
problems" on page 221.
219
Chapter 2. Diagnostics