It is highly recommended to configure a 'loghost' on a Sun Fire platform so that
all messages that are logged in the System Controller's NVRAM buffer will not be
lost and will get stored on an assigned admin workstation somewhere on the network.

To do this, it will be necessary to configure the 'loghost' from the
System Controller (SC) by setting the IP address of the admin 
workstation and then configure the syslog.conf file on the admin
workstation itself.

1. On the System Controller (SC) of the Sun Fire platform, do the following:

You will first need to log on to the SC either by telnet or tip hardwire
through the serial cable and then issue the following command (just
hit ENTER to confirm the default choices until you get to the 'loghost' parameters):

r12-1a:SC> setupplatform
[...]
Loghosts
--------
Loghost []: 172.16.40.10:local0
[...]

This setting will send the platform messages with facility local0
to the admin workstation with IP address 172.16.40.10.
local0 is used to differentiate messages coming from the platform.

It's also possible to leave out the setting :local0, but if this is done, it
will be impossible to separate messages coming from the platform and domains
into different messages files on the admin workstation. All messages
will be logged in the /var/adm/messages of the admin workstation.

NOTE: when the syntax IP:localx is used, :localx will not be
shown when issuing the 'showplatform' or 'showdomain' command. 
showplatform and showdomain don't echo the :localx setting.

For domains, setup the loghost the same way but use the 'setupdomain'
command:

r12-1a:A> setupdomain
[...]
Loghosts
--------
Loghost []: 172.16.40.10:local1
[...]

r12-1a:B> setupdomain
[...]
Loghosts
--------
Loghost []: 172.16.40.10:local2
[...]

NOTE: local10 and higher are not allowed and won't work.

2. On the admin workstation, do the following:

Now, you need to configure the syslog.conf file on of the admin 
workstation to split messages in specific messages files. To do this, 
create the following message files, and simply add the following lines in
/etc/syslog.conf:

% rlogin 172.16.40.10 -l root

# touch /var/adm/messages.platform
# touch /var/adm/messages.domainA
# touch /var/adm/messages.domainB

# vi /etc/syslog.conf

[...]
#
# non-loghost machines will use the following lines to cause "user"
# log messages to be logged locally.
#
ifdef(`LOGHOST', ,
user.err                                        /dev/sysmsg
user.err                                        /var/adm/messages
user.alert                                      `root, operator'
user.emerg                                      *
)
local0.notice   /var/adm/messages.platform      => ADD THIS LINE 
local1.notice   /var/adm/messages.domainA       => ADD THIS LINE 
local2.notice   /var/adm/messages.domainB       => ADD THIS LINE

Then restart the syslog daemon:

# /etc/init.d/syslog stop
# /etc/init.d/syslog start

3. To test that your loghost configurations are working correctly, do the following:

To test the platform shell loghost file, remove a fan tray for 5 seconds and
then re-insert. You should see the messages appear in the /var/adm/messages.platform
file.

To test the domain shell loghost files, from the domain shell, do a "setkeyswitch on"
command and watch the output from LPOST appear in the domain shell's loghost file.            

Transferred from "French Sunsolve" collection by george.bolduc@sun.com

DOCUMENT ID : 1189
SYNOPSIS : Serengeti: How to configure a loghost ?
SUBMITTER : lboschet@france
CREATION DATE : 06/03/01
LAST MODIFIER : lboschet@france
LAST MODIFICATION DATE : 07/03/01