Users Guide

Known Issues and Frequently Asked Questions 69
Known Issues and Frequently Asked Questions
This section discusses known issues with using the BMC Management Utility, along with frequently
asked questions.
Known Issues
General Issues
• You must assign a valid BMC user name and password before you can connect to your system's
BMC using the BMC Management Utility. If you do not explicitly provide a valid BMC user name
and password when using the BMC Management Utility to log in to your system's BMC, the
BMC firmware will use a null user name and null password as defaults, resulting in a "Login Not
Authorized" error.
SOL Proxy Issues
• SOL Proxy on IP port 623 allows connections from a Web browser. However, if you connect from a
Web browser, SOL Proxy displays only jumbled and unusable data. You must close the Web
session and connect through a telnet connection to run the application.
• Microsoft
®
SAC does not implement hardware control flow. Therefore, when console redirection
is enabled with EMS SAC, you will see corrupted data. As SAC does not implement hardware flow
control, you are unable to effectively use SOL Proxy to activate console redirection to EMS SAC.
This can result in corrupted screen output caused by missed characters. Slower baud rates correct
this situation and still provide good user experience.
IPMI Shell Issues
• If you type "ipmish" from any directory other than the directory where the BMU is installed, you
will receive a "command not found" error from DOS. This is because the BMU install directory is
not included in the system search path. You can execute IPMISH directly by specifying a fully
qualified path or by first navigating to the BMC directory and then executing the command.. You
may also manually add the BMU install directory to the execution search path.