External serial port doesn't work after SOL activated on R710

Frank Wang wg at yarbs.cn
Tue Sep 22 02:43:26 CDT 2009

  I made my conclusion too early. I still got NUT alert mail this morning
when the server was powered on again. I've checked the BIOS external
port setting was mysteriously modified to "Remote Access Device" again
WITHOUT OMSA installed.
The OS of the server is Centos-5.3-x86_64 with kernel 2.6.18-164.el5. For
serial console, I've only modified /boot/grub/grub.conf, /etc/inittab and
  serial --unit=1 --speed=115200 --word=8 --parity=no --stop=1
  terminal --timeout=5 console serial
  Title CentOS (2.6.18-164.el5)
    root (hd0,0)
    kernel ... console=tty0 console=ttyS1,115200n8

  s1:2345:respawn:/sbin/agetty -f /etc/issue 115200 ttyS1 vt100


   The related BIOS serial settings:
Serial Communication .......... On with Console Redirection via COM2
Serial Port Address ........... Serial Device1=COM1,Serial Device2=COM2
External Serial Connector ..... Serial Device1
Failsafe Baud Rate ............ 115200
Remote Terminal Type .......... VT100/VT220
Redirection After Boot ........ Disabled
   The automatically altered option is the External Serial Connector.
Other BIOS settings are default except the CPU Virtualization
Technology is enabled.

   The related NUT config file /etc/ups/ups.conf
        driver = apcsmart
        port = /dev/ttyS0
        sdtype = 1
        desc = "For all test servers"

    The main applications on the server are Oracle 10g2, Weblogic 8.1 and
VMware-Server-2.0.1. Is there anything we did wrong?

On Tue, September 22, 2009 1:28 am, Frank Wang wrote:
>     The setting was changed to "Remote Access Device" this time, and it's
> caused by the "Redirection After Boot" option in BIOS serial settings.
> Disable it makes both NUT and SOL happy. I rebooted the server, and
> everything works like a charm.
> Then I installed OMSA-6.1.0-648, rebooted, and NUT stopped working
> immediately. The external port was automatically modified to "Remote
> Access Device" again. Uninstall OMSA and revert the external serial
> connector to the COM1 device make everything works again.
>     It turned out the OMSA-6.1.0-648 is the culprit. It will automatically
> change the BIOS external serial port setting if Serial console
> enabled.

More information about the Linux-PowerEdge mailing list