Setting up the loghost
Sun Confidential: Internal Only
59
SunService Sun Microsystems, Inc. All Rights Reserved. Enterprise Services
Setting up the loghost
The System Controller provides the capability of sending platform and
domain error messages to a syslog host. Since the system controller can
only buffer 4k of error messages, it is
essential
that a loghost be setup to
ensure that important messages are not lost.
You will be prompted for a loghost and facility level when you run
setupplatform and setupdomain.
Loghosts
--------------------------------------
Loghost []: 172.16.40.40
Log Facility [local0]:
Edit
syslog.conf
on the admin workstation
Add the following to the
/etc/syslog.conf
, file making sure they
correspond to the settings on the platform.
local0.notice
/var/log/messages.platform
local1.notice /var/log/messages.domain-A
local2.notice /var/log/messages.domain-B
local3.notice /var/log/messages.domain-C
local4.notice /var/log/messages.domain-D
The above entries must be separated by tabs, otherwise syslogd fails to work.
Make sure the above files exist (touch them first) then stop & start the
syslogd using the
/etc/init.d/syslog
script
syslog Parsing Tools
One of the problems with SC logging, is managing multiple platforms.
Solaris has 8 facility levels; an F6800 with 4 domains will use 5, leaving us
the problem of where to put the logs from a second F6800, for example.
The solution is to use a syslog parsing tool. An example is sclogger. With
sclogger, all the messages get mapped to a common facility, and sclogger
splits the messages into appropriate files. Load the parsing tools from
http://pts-americas.west/esg/msg/techinfo/platform/sun_fire/tools/
