Sun Storage 5210 NAS Appliance
 
Sun Storage 5310 NAS Appliance
 

GCS>Sun Microsystems>Storage - Disk>Network Attached Storage
 

To allow the Sun StorEdge[TM] 5210/5310 NAS Appliance to deliver its syslog
messages to a remote syslog host running Solaris[TM] Operating System, and save a
local copy, perform the following steps.

STEP 1:

Verify that the Sun StorEdge 5210/5310 NAS Appliance has been configured to
deliver the syslog messages to a remote host. This is done either by the
command line interface, or the web based graphical user interface(GUI).

COMMAND LINE:

• Enter the letter preceeding the selection for "DNS & SYSLOGD"
• Choose 1 for "Edit fields"
• Press the return key, until the cursor is in the "Network System Logger
  (SYSLOGD)" section of the screen
• Set the "Enable" field to "Yes' by entering a 'Y'
• Provide the IP address or hostname of the Solaris syslog host
• Choose the appropriate facility to deliver the messages.
  The facility Local0 through Local7 make an ideal facility to use.
• Decide which "Log Type" will be delivered to the syslog host.
  The user can select any or all of the "log types" which range from
  info and debug level to emergency. Set the field preceeding the
  particular log type to "Yes" or "No" depending on user preference.
• A "Local Log" can be enabled here as well. Set the "Local Log" to "Yes"
  provide a local path (which can be on a share or export) and logfile
  name, number of archives for this log and maximum size of log file before
  current log file is archived.
• When all configuration is complete, enter "7" to save the changes

GUI:

• Make the following selections from the left hand window pane
  Monitoring and Notification
  View System Events
  Set Up Logging
• Check the box preceeding "Enable Remote Syslogd"
• Provide the IP address or hostname of the Solaris syslog host
• Choose the appropriate facility to be used to deliver the messages
  from the "Facilities" dropdown list
  The facility Local0 through Local7 make an ideal facility to use.
• Decide which "Log Type" will be delivered to the syslog host.
  The user can select any or all of the "log types" which range from
  info and debug level to emergency. Check the box preceeding the
  particular log type to enable it.
• A "Local Log" can be enabled here as well. Check the box preceeding
  "Local Log", Fill in the path and name for a local syslog file,
  the number of archives for this log and maximum size of log file before
  current log file is archived.
• When all configuration is complete, Press the "Apply" button to save the
  changes

NOTE: There is no need to re-boot the Sun StorEdge 5210/5310 NAS Appliance after
making syslogd changes.

STEP 2:

The system designated as the syslog host, contains its own syslog configuration
file - /etc/syslog.conf . An entry must be added to this file, so the Sun
StorEdge 5210/5310 NAS Appliance can send messages to this host.

A configuration entry is composed of two TAB-separated fields:

• the selector
• the action.

The selector field contains the <facility.level> information, and the action
field indicates where to forward the message.

In the case of the Sun StorEdge 5210/5310 NAS Appliance5210/5310, the facility
typically is one of local0-local7. The level is one of the following:

• emerg
• crit
• warning
• info
• alert
• err
• notice
• debug

The action field is usually a file, located in the /var/adm directory, for
example: /var/adm/5310.messages.

Here is an example of a syslog host's syslog.conf file.

 syslog host /etc/syslog.conf file entry (tab separated):
#ident  "@(#)syslog.conf  1.5  98/12/14 SMI"   /* SunOS 5.0 */
#
# Copyright (c) 1991-1998 by Sun Microsystems, Inc.
# All rights reserved.
#
# syslog configuration file.
#
# This file is processed by m4 so be careful to quote (`') names
# that match m4 reserved words.   Also, within ifdef's, arguments
# containing commas must be quoted.
#
*.err;kern.notice;auth.notice			/dev/console
*.err;kern.debug;daemon.notice;mail.crit	/var/adm/messages

 *.alert;kern.err;daemon.err			operator
*.alert						root

 *.emerg						*

 # if a non-loghost machine chooses to have authentication messages
# sent to the loghost machine, un-comment out the following line:
#auth.notice			ifdef(`LOGHOST', /var/log/authlog, @loghost)

 mail.debug			ifdef(`LOGHOST', /var/log/syslog, @loghost)
local6.info					 /var/adm/5310.log

In the above example, the Sun StorEdge 5210/5310 NAS Appliance messages, are
being received by this syslog host, under the local6 facility. All Sun StorEdge
5210/5310 NAS Appliance messages, of level info and above, will be received by
this facility. These syslog messages are being delivered to the
/var/adm/5310.log file.

NOTE: The administrator is responsible for creating the file that will be used
to capture the Sun StorEdge 5210/5310 NAS Appliance messages. To create
this file, run a command similar to the following:

        touch /var/adm/5310.log   

NOTE: If changes are made to the syslog.conf file, the syslogd daemon must be
stopped and restarted - use the following command:

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

Test the syslog host logging, by issuing the following command:

  #>logger -p local6.notice message_from_syslog_host

This message should appear in the destination file: /var/adm/5310.log as
specified in the /etc/syslog.conf file. This test proves that the syslog host is
capable of receiving and logging messages of the <facility.level>, specified in
the /etc/syslog.conf file. It does not guarantee that the remote messages from
the 5210/5310 NAS array will be logged.

STEP 3:

On startup, the syslogd daemon reads a second file, which contains default
parameters for the daemon. The file is /etc/default/syslogd.
This file contains the field LOG_FROM_REMOTE. By default, this is set to YES,
which allows the syslogd daemon to receive remote messages. If this field is set
to NO, the Sun StorEdge 5210/5310 NAS Appliance will still try to deliver the
syslog messages to the syslog host, but will be unsuccessful.

The final thing to verify, is that the startup script /etc/init.d/syslog is not
running syslog -t , as this will also prevent the loghost from receiving
messages from the Sun StorEdge 5210/5310 NAS Appliance, even if
/etc/default/syslogd has LOG_FROM_REMOTE=YES

If all of the above have been performed, the Sun StorEdge 5210/5310 NAS
Appliance, will now deliver syslog messages to the named host and store them in
the specified file, as well as store a copy in a file local to the Sun StorEdge
5210/5310 NAS Appliance itself. This information is very useful in troubleshooting.

This solution has no attachment