Solved!
Go to SolutionUsing BMC console redirection through SOL proxy hangs SAC
I installed SOL proxy on the PC which is in the same LAN with the server in question (R320). I can connect to the BMC console redirection. If I for example do "Reboot and activate console redirection" I have access to the console (eg I could enter BIOS and change settings).
However once the R320 boots into Windows 2008 R2 there is SAC to load on the console.
It prints SAC version and goes to prompt "SAC>" and thats it. there is no interaction with the telnet any more. whatever i press on the remote keyboard nothing works. the prompt just there and I can terminate session but killing the telnet client.
I used Putty.
I also tried stock Windows telnet and went to 'Activate console redirection' connected to the R320 and got small string of garbage chars and thats it (I think it was SAC again as Windows was booted on the R320 at that moment).
Whats wrong with it?
I have R320 with BMC. I enabled SOL. I installed BMC utils and see SOL service running on Windows.
I want remote console redirection of that R320. The OS IP : 192.168.1.21 and iDRAC IP : 192.168.1.20
If I try to telnet from remote PC into R320 using telnet 192.168.1.21 623 I got telnet login, I type user root and the password. And I got "Error (0xa5):Authentication failure"
If I run SOL proxy on the PC I try to connect from and then telnet 127.0.0.1 then the login works fine and I then can connect to R320 console remotely.
Why cant I run SOL on the server itself ?
Both - the PC and the server are in the same LAN - 192.168.1.xxx
DELL-Chris H
7 Practitioner
•
9682 Posts
•
48046 Points
2908
0
Posted July 11th, 2012 14:00
Maxima120,
Verify this information for me.
Select “Console Redirection” in the main screen and press the Enter key to bring up the configuration menu. Next, verify the following settings:
• Console Redirection: Serial Port 1
• Failsafe Baud Rate: 19200
• Remote Terminal Type: VT100/VT220
• Redirection After Boot: Enabled
Pressing the Esc key twice restores the setup screen, saves
changes, and exits.
You can use this link and on page 4 is a walkthrough - www.dell.com/.../ps4q05-20040205-Hoke-OE.pdf
Configure IPMI/BMC settings for console redirection.
While the server is powering up during POST, press Ctrl+E when the BMC configuration is displayed. This action
brings up the Intelligent Platform Management Interface/baseboard management controller (IPMI/BMC) setup screen.
You should then ensure that “IPMI Over LAN” is set to “On.”
Configure IPMI LAN settings.
Next, select “IPMI LAN Channel” and press the Enter key to
bring up the configuration menu. You should configure the IP address settings of the BMC NIC as desired
for the LAN.
Or you can use DHCP.
Configure BMC user accounts.
In the console redirection screen, select “User Configuration”
and verify the user settings: the administrator account should be
enabled; the administrator username should be “root”; and the
password should be “calvin.”
Installing the BMC SOL proxy component.
The BMC SOL proxy program is provided on the Dell OpenManage Systems Management CD that ships with Dell PowerEdge servers.
When installation begins, an InstallShield wizard walks administrators through the setup process.
Verify that the NIC designated as “NIC1” on the server is connected to the same LAN as the system
that hosts the SOL proxy. Only NIC1 is used for shared BMC-NIC connectivity.
When the Select Components screen is displayed,
You can select “OSA SOL Manager” to install that component. They should use the default values for the SOL proxy port and session settings. After installation concludes, administrators must restart the
system on which the SOL proxy component is installed.
DELL-Chris H
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!
maxima120
47 Posts
2908
1
Posted July 14th, 2012 07:00
After a bit of googling I found that:
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.