6,534
edits
Changes
Sectioned →Serial console: , some typos fixed
== Serial console ==
Here is a description of a common routine, that is necessary to set up a serial console.
=== Hardware setup ===
First of all you should make sure that your node has a serial port. If there is no such port then
unfortunately this way is not for you. Then you need to find second node with a serial port on it.This node will be used to collect logs from your primary mashine. Further you need to acquireso-called null modem cable and it must be long enough to connect two mashines in question.
In your boot loader add the following kernel parameters:
<pre>
console=ttyS0,11500 console=tty0
</pre>
For example , in GRUB boot loader it looks like such strings in configuration file <tt>/boot/grub/grub.conf</tt> it looks like this in :
<pre>
title Fedora Core (2.6.16-026test014.1-smp)
initrd /initrd-2.6.16-026test014.1-smp.img
</pre>
Kernel loaded with such parameters will send all kernel messages to /dev/ttyS0 (first serial port, a.k.a. COM1). If you have several ports, make sure that your null modem cable is connected to the appropriate port. ==== Receiving side ====On the second node you should turn on run any software that can log from /dev/ttyS0.
It can be usual
<pre>
or something more sophisticated: syslogd, watchtty etc.
==== Port setup ====One more important thing. 115200 in the example above is the rate of emiting emitting port. Also recieving Recieving port must also work at equal the same rate.To For example, to tune ttyS0 rate use stty programlike this:
<pre>
stty 115200 < /dev/ttyS0
</pre>
Some other serial port parameters, like parity, number of stop bits etc. should also be the same on both sides.
== Netconsole ==