Troubleshooting keyboard and mouse issues - IBM BladeCenter
Troubleshooting keyboard and mouse issues - IBM BladeCenter
Troubleshooting keyboard and mouse issues - IBM BladeCenter
Source |
---|
RETAIN tip: H192034
Symptom |
---|
How to troubleshoot mouse and keyboard issues on BladeCenter systems.
Affected configurations |
---|
The system may be any of the following IBM servers:
- BladeCenter Chassis, type 7967, any model
- BladeCenter Chassis, type 8677, any model
- BladeCenter H, type 7989, any model
- BladeCenter H, type 8852, any model
- BladeCenter HS20, type 1883, any model
- BladeCenter HS20, type 1884, any model
- BladeCenter HS20, type 7981, any model
- BladeCenter HS20, type 8678, any model
- BladeCenter HS20, type 8832, any model
- BladeCenter HS20, type 8843, any model
- BladeCenter HS21 XM, type 1915, any model
- BladeCenter HS21 XM, type 7995, any model
- BladeCenter HS21, type 1885, any model
- BladeCenter HS21, type 8853, any model
- BladeCenter HS40, type 8839, any model
- BladeCenter HT, type 8740, any model
- BladeCenter HT, type 8750, any model
- BladeCenter JS20, type 8842, any model
- BladeCenter JS21, type 7988, any model
- BladeCenter JS21, type 8844, any model
- BladeCenter LS20, type 8850, any model
- BladeCenter LS21, type 7971, any model
- BladeCenter LS41, type 7972, any model
- BladeCenter QS20, type 0200, any model
- BladeCenter QS21, type 0792, any model
This tip is not option specific.
This tip is not software specific.
Troubleshooting keyboard and mouse problems on IBM BladeCenters |
---|
Keyboard, video, and mouse services are provided to the blades via redundant USB buses inside the chassis. One bus connects Management Module (MM) 1, all the blades and the media tray.
The second bus connects MM 2, all the blades and the media tray. There are four USB multiplexes (muxes) that connect blades 1-4, 5-8, 9-12, and 13-14 into the redundant buses.
This document is for troubleshooting keyboard and mouse problems that occur when attached locally to the BladeCenter or via remote control. The first step in troubleshooting these issues is to determine whether the problem occurs remotely or locally, then choose the correct symptom. Issues that occur both remotely and locally should be considered local issues.
Note: For local keyboard/mouse issues on a BladeCenter (Type 8677) chassis with a MM, read RETAIN Tip 185739 before continuing. Advanced Management Modules (AMM) are not affected by that RETAIN Tip.
Local keyboard and/or mouse problems on all blades in a chassis with one MM |
---|
- Restart the MM. If that resolves the problem, check the IBM support site for MM updates that might address keyboard and mouse issues.
- Move the MM to the second slot. If the problem resolves, move the the MM back to the original slot and contact IBM support with the results of that test.
- If swapping MM did not resolve the issue, remove the media tray. If that resolves the problem, swap this media tray with the media tray in a known working chassis. Contact IBM support with the results of that swap. If another chassis is not available, open the tray and disconnect all cables inside the tray and re-install the media tray. Contact IBM support with the results of that test.
Local keyboard and/or mouse problems on all blades in a chassis with two MMs |
---|
- Restart the MM. If that resolves the problem, check the IBM support site for MM updates that might address keyboard and mouse issues.
- Failover the primary MM to the standby MM. If the problem resolves, remove the standby MM and test both MMs in both slots. This testing should point to either an MM that fails in both slots or a singly slot which causes a failure for both MMs. Contact IBM support with the results of those tests.
- If swapping MM did not resolve the issue, remove the media tray. If that resolves the problem, swap this media tray with the media tray in a known working chassis. Contact IBM support with the results of that swap. If another chassis is not available, contact IBM support.
Local Keyboard and/or mouse problems on some blades, but not others |
---|
- Move the MM to the second slot, or failover the primary MM to the standby MM. If the problem resolves, skip to the symptom "Keyboard and/or mouse problems on all blades."
- If the problem is only occurring on one blade, move that blade to a slot served be a different USB mux. If the problem continues, swap the hard drive of this blade with a blade of the same type which is not having problems. This will determine whether the problem is connected to the Operating System. Contact IBM support if the problem stays with the blade.
- If the problem is occurring on multiple blades, the first step is to verify whether all the blades having problems connect to the same mux. See the layout above to verify this. If they are not on the same USB mux, repeat the process in step two for each blade having problems.
- For problems with multiple blades connecting to the same mux, remove all blades connecting to that mux, then insert them one at a time. If the problem returns when a particular blade is inserted, try that blade in a slot served by a different USB mux. If the problem follows this blade to another USB mux, remove the blade and mark it suspect. Continue this process for any blade showing problems, then contact IBM support.
- If the process in step 4 indicates that any blade connecting to a particular mux has problems, remove the media tray from the chassis. Contact IBM support with the results of this test.
Remote keyboard and mouse respond slowly or jump around the screen |
---|
- High latency network connections or slow workstations can cause the mouse to be jumpy. To mitigate this behavior, configure the blade operating system to move the mouse more slowly.
- Connect to multiple chassis with the same workstation, and to the same chassis with multiple workstations. These tests will verify whether the common denominator is the workstation or the chassis.
- Connect the workstation directly to the MM and start remote control. If the problem resolves, the network is causing the issue. Consult a network specialist for the next troubleshooting steps.
- If the problem still occurs when the workstation is connected directly to an MM, remove the currently installed version of Java and install an updated version. Incomplete removal of Java can lead to unpredictable results in the remote control session.
- Contact IBM support with the results of the tests above for further troubleshooting.
Contact your appropriate Support Center for your geography.
In the United States, contact 1-800-IBM-SERV (1-800-426-7378).
The IBM Directory of Worldwide Contacts is available from the following URL:
http://www.ibm.com/planetwide/