From: Tomasz N. <tno...@ne...> - 2009-08-01 23:02:43
|
Hello, I have couple Intel SR1550 server platforms and I use IPMI and SOL on them sucessfully. They all have the same config: # BIOS settings: Console Redirection [Serial Port B] Flow Control [RTS/CTS] Baud Rate [19.2k] Terminal Type [VT-100] Legacy OS Redirection [Enabled] # sol info Info: SOL parameter 'Payload Channel (7)' not supported - defaulting to 0x0e Info: SOL parameter 'Payload Port (8)' not supported - defaulting to 623 Set in progress : set-complete Enabled : true Force Encryption : true Force Authentication : true Privilege Level : ADMINISTRATOR Character Accumulate Level (ms) : 20 Character Send Threshold : 50 Retry Count : 6 Retry Interval (ms) : 20 Volatile Bit Rate (kbps) : IPMI-Over-Serial-Setting Non-Volatile Bit Rate (kbps) : 19.2 Payload Channel : 14 (0x0e) Payload Port : 623 # grub.conf [...] module /boot/vmlinuz-2.6.18-128.1.10.el5xen ro root=LABEL=/ [...] xencons=ttyS1 console=tty console=ttyS1,19200n8 [...] So to sum up; I get whole BIOS POST (serial port B) and system boot messages (ttyS1 - COM2) on serial-over-lan console with no problems. Lately I've bought new Intel platform - SR1625. This is Nehalem arch with S5520 board. So I've tried to configure IPMI and SOL the same way as above but the problem was I've been getting through SOL only BIOS POST messages. Once grub has been taking control over the boot process - SOL has been freezing. After many hours of tests I've figured out that if I change kernel Grub configuration from ttyS1 to ttyS0, then I see also OS boot messages. So my question is why/how come does it work in such configuration (bios: serial B, system: ttyS0) and what shell I do if I'd like to change it to ttyS1 as on other machines and see boot messages again. TIA. PS. The only difference in SOL configuraction is: Payload Channel : 14 which seems to be default in BMC of Intel SR1550. On new Intel SR1625 I get:: Payload Channel : 1 (0x01) with no additional default channel errors. -- Tomek |