HP Integrated Lights-Out 3 - Manual (Page 222)

Num Lock out of sync between iLO and Shared Remote Console
When you log in to a Shared Remote Console session, the Num Lock setting might be out of sync
between iLO and some of the Remote Console sessions.
Solution: Select Keyboard
→Num Lock in the Remote Console to synchronize the Num Lock settings.
Keystrokes repeat unintentionally during Remote Console session
When you are using the .NET IRC or Java IRC, a keystroke might repeat unintentionally during a
Remote Console session.
Solution 1: Identify and fix problems that might cause network latency.
Solution 2: Adjust the following settings on the remote machine:
•
Increase the typematic delay—This setting controls the delay before a character repeats when
you press and hold a key on the keyboard.
•
Decrease the typematic rate—This setting controls the rate at which a character repeats when
you press and hold a key on the keyboard.
NOTE: The exact name of the setting varies depending on the OS you are using. For more
information about changing the typematic delay and rate, see your OS documentation.
Session leader does not receive connection request when .NET IRC is in replay mode
Solution: When a Remote Console session leader plays captured video data, the .NET IRC does
not display the Deny or Accept message when another user attempts to access or share the .NET
IRC. Instead, the new .NET IRC session waits and eventually times out. If you require access to the
.NET IRC, and your request times out, contact the other user or use the Remote Console Acquire
feature to take control of the IRC. For instructions, see
“Acquiring the Remote Console” (page 118) .
Keyboard LED does not work correctly
The client keyboard LED does not reflect the true state of the keyboard lock keys. The Caps Lock,
Num Lock, and Scroll Lock keys are fully functional when you are using the keyboard options in
the Remote Console.
Inactive .NET IRC
The iLO .NET IRC might become inactive or disconnect during periods of high activity. .NET IRC
activity slows before becoming inactive. Symptoms of an affected .NET IRC include the following:
•
The .NET IRC display is not updated.
•
Keyboard and mouse activity is not recorded.
•
Shared Remote Console requests do not register.
Although you can replay a captured file on an inactive .NET IRC, the active state of the .NET IRC
is not restored.
This issue might occur when multiple users are logged in to iLO, a Virtual Media session is connected
and is performing a continuous copy operation, or a .NET IRC session is open. The Virtual Media
continuous copy operation takes priority and, consequently, the .NET IRC loses synchronization.
Eventually, the Virtual Media connection resets multiple times and causes the USB media drive for
the OS to lose synchronization with the Virtual Media client.
Solution: Reconnect to the .NET IRC and the Virtual Media. If possible, reduce the number of
simultaneous iLO user sessions. If necessary, reset iLO. (The server does not need to be reset.)
222 Troubleshooting