Table 2. Troubleshooting charts (continued)
Device | Suggested action |
|
|
The customer interface card (FRU number 59P6629) is not compatible with the JS20 | |
configured with a JS20 blade | blade server and must be replaced with the latest level FRU. |
server but works with a HSxx | Note: The customer interface card installed in the BladeCenter is listed as the |
blade server. | "media tray" instead of the "customer interface card" on the Hardware VPD view of |
| the |
| customer interface card. Replace the customer interface card with the latest level, |
| see Chapter 7, “Parts listing, BladeCenter Type 8677 and 1881,” on page 79for the |
| correct FRU number. |
|
|
Some components do not | The green status dot for a component is not automatically a link to environmental |
report environmental status | information (temperature and voltage) for the component. Only the management |
(temperature, voltage). | module and blade servers have environmental information, and only the green dot for |
| those components contains a link to environmental information. |
|
|
Switching KVM control | If a blade server is under heavy load, it can take several minutes before it |
between blade servers gives | enumerates the USB devices connected to it. If control of the KVM and media tray is |
USB device error. | switched away from the blade server before this enumeration is complete, a USB |
| device installation error might be displayed. Do not switch KVM control between |
| blade servers until the mouse and keyboard are both working on the blade server |
| that has control of the KVM and media tray. |
|
|
“Unsafe Removal of Device” | Before switching ownership of the media tray to another blade server, safely stop the |
error message appears on | media tray devices on the blade server that currently owns the media tray, similar to |
blade server running | the following: |
Microsoft Windows 2000. | 1. |
| |
| bottom right of the screen. |
| 2. Select USB Floppy, and click Stop. |
| 3. Select USB Mass Storage Device, and click Stop. |
| 4. Click Close. |
| You can now safely switch ownership of the media tray to another blade server. |
|
|
“Media not found” error | Attempting to access the mounted optical drive or diskette drive (media tray) after it |
message and other file | has been switched to another blade server results in I/O errors, even if the media tray |
system error occur on a blade | has been switched back. |
server running Linux or DOS. | Note: Because the BladeCenter unit uses a USB bus to communicate with the media |
| tray devices, switching ownership of the media tray to another blade server is the |
| same as unplugging a USB device. |
| v If a blade server tries to access the optical drive after it has been switched to |
| another blade server, a “Media not found” error occurs. |
| v If a blade server is running a DOS environment, such as when updating firmware |
| on the blade server, the firmware can be interrupted or corrupted when the media |
| tray is switched away; you might need to call for service on the blade server. |
| v If a file handle was left open by switching the media tray away, the system |
| administrator will not be able to do a clean unmount (umount command) unless the |
| unmount is forced by umount command parameters (“lazy umount”). |
| v If the system administrator is sharing out the optical drive for multiple users, that |
| network share is broken. |
| Before switching ownership of the media tray to another blade server, ensure that the |
| optical drive and diskette drive are not mounted for the current blade server owner |
| (check for open file handles and sharing out). If a firmware update is taking place on |
| the blade server, do not switch the media tray to another blade server. |
|
|
Chapter 6.