Problem
How do I set up two system serial consoles for remote access, in case of system panics, or to be able to administer two machines from one console?
Solution
To configure a serial console for remote access, take these steps:
1. Attach a serial cable between the COM1 ports of the two systems. Use a null modem if necessary to establish bi-directional connectivity.
2. To configure both systems for serial console, add a line to /etc/default/boot:
SYSTTY=1Add a line to /usr/lib/uucp/Devices (if other lines already exist which refer to tty1a or tty1A, place this after them):
Direct tty1a - 9600 directModify existing "tty1a" entries in /etc/conf/init.d/sio and
/etc/inittab:Se1a:234:respawn:/etc/getty -n tty1a mModify existing "tty1A" entries in /etc/conf/init.d/sio and /etc/inittab. Change "respawn" to "off", if necessary.
3. If desired, you can link the kernel debugger into both systems. To do this, change "N" to "Y" in /etc/conf/sdevice.d/scodb and run:
/etc/conf/cf.d/link_unix -n (once, the first time scodb is added)
/etc/conf/cf.d/link_unix -y4. Verify serial console operation on both systems by rebooting that
system and observing the boot process from the other. That is:systemA# cu -l tty1a directsystemB!login: rootPassword:... now logged into systemBsystemB# shutdown -g0 -y... shuts down, then after a moment gives boot prompt:
Boot
: [return]... and systemB boots, under systemA's serial controlNext, repeat this in the other direction.
5. Optional:To have each system normally boot with the video console, omit "SYSTTY=1" from /etc/default/boot. Then, to use a serial console during a particular boot, enter "systty=1" directly at the boot prompt on the video console:
Boot
: defbootstr systty=1The boot prompt now moves to the serial port. You must be physically present at the video console to accomplish this, of course.
It is also possible to add "systty=sio" (not "1") to an existing boot command line. For instance, edit /etc/default/boot, copy the DEFBOOTSTR line, change its name, and add "systty=sio":
DEFBOOTSTR=hd(40)unix swap=hd(41) dump=hd(41) root=hd(42)SERIALCONS=hd(40)unix swap=hd(41) dump=hd(41) root=hd(42) systty=sioNow, entering "serialcons" at the video console's boot prompt will cause the kernel to use a serial console.
It is also possible to remotely reboot a system by first logging into it, adding "SYSTTY=1" to /etc/default/boot, then rebooting. For this to work, autoboot must be enabled (AUTOBOOT=YES in /etc/default/boot).
Note: Problems can occur if another device is bootable ahead of the hard drive (for example, a floppy or CD-ROM). It may be necessary to change BIOS settings prior to the first attempt.
To have scodb take control very early in the boot process, run /etc/conf/pack.d/scodb/bin/modtunes and set MAINDB=true.
To log one system's console activity to a file on the other, simply copy the contents of the serial port:
cat /dev/tty1a > /usr/spool/buddy-console-logIt may be necessary to disable logins on the local system's serial port.
See also
ta109287, "How do I set up a serial console on SCO OpenServer 5?"
ta109310, "Gathering information when SCO OpenServer 5.0.4 system panics but does not produce a valid dump or the system hangs."
http://osr5doc.xinuos.com (/etc/default/boot, kernel command lines, scodb documentation, user-level scodb doc, dump manipulator, kernel profiler)
http://chac.sco.com/TopicViews/HDKhome.html (UW7 HDK on scodb,
scodb quick reference)