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

After you enter the command, the screen changes from graphics mode to text mode, displaying
the screen.
•
For SLES, press F2 and the down arrow from the text console. The text mode is selected and
the screen appears.
Unable to pass data through SSH terminal
If you use an SSH terminal to access the text console, SSH might intercept keystroke data and not
pass the action to the text-based Remote Console. When this occurs, it appears as if the keystroke
did not perform its function.
Solution: Disable any SSH terminal shortcuts.
VSP-driven selection during the serial timeout window sends output to BIOS redirect
instead of VSP
The /etc/grub.conf file includes an option for a serial timeout window (terminal
--timeout=10 serial console
). This setting provides a window of time to select a key stroke
on the VSP or on the VGA console, and then the menu is output to the corresponding device. The
BIOS serial redirect intercepts VSP keystrokes during this timeout window.
Solution: To work around this issue, do not press a key for a VSP-driven selection during the
10-second timeout or turn off BIOS redirection to the VSP.
Scrolling and text appear irregular during BIOS redirection
During BIOS redirection, the scrolling might not work properly. When you enter commands in
RBSU, the text might overwrite itself on the bottom line of the terminal window.
Solution: The BIOS expects and controls a fixed 80x24 character window. When redirected to
the serial port, the BIOS still expects and controls a fixed 80x24 character window. If the VSP
client being used (SSH, HyperTerminal, or other terminal emulator) can resize the window to a
size other than 80x24, scrolling becomes confused and the screen output appears garbled. To
avoid this issue, configure the terminal emulator for a window size of exactly 80x24.
Troubleshooting miscellaneous issues
The following sections discuss troubleshooting miscellaneous hardware or software issues.
Cookie sharing between browser instances and iLO
iLO uses browser session cookies to distinguish between individual logins—each browser window
appears as a separate user login—while sharing the same active session with iLO. Multiple logins
can confuse the browser. This may appear to be an iLO issue, but it is typical browser behavior.
Several processes can cause a browser to open additional windows. Browser windows opened
from an open browser represent different aspects of the same program in memory. Consequently,
each browser window shares properties with the parent, including cookies.
Shared instances
When iLO opens another browser window (for example, the Remote Console or a help file), this
window shares the same connection to iLO and the session cookie.
The iLO web server makes URL decisions based on each request received. For example, if a request
does not have access rights, it is redirected to the login page, regardless of the original request.
Web server-based redirection, selecting File
→New→Window, or pressing Ctrl+N opens a duplicate
instance of the original browser.
226 Troubleshooting