Solaris client logging and tracing

This topic describes the logging and tracing capabilities available on SAN File System Solaris clients.

Configure the syslog facility and select one or more SAN File System classes to enable tracing and logging on the SAN File System Solaris client.

Viewing SAN File System classes

Tracing in the SAN File System is controlled according to components called classes. A class loosely corresponds to a file system operation such as mounting or reading.

To view the classes, enter:
sanfs_ctl trace list

Enabling trace messages

The SAN File System client generates both log and trace messages, which are routed through the syslog facility on the Solaris operating system. The syslog facility captures log and trace output from the kernel as well as other operating system services.

By default, the SAN File System maintains all of its messages in an internal buffer to allow them to be recovered after a system crash. However, you can specify a destination for the messages by modifying /etc/syslog.conf.

To enable or disable logging and tracing on the Solaris client, use the sanfs_ctl command. For example, to enable tracing on all classes at the same level, enter:
sanfs_ctl trace set -level number
where number is a level of verbosity of the tracing that increases from 0 to 5.
You can also enable or disable trace messages for selected classes by entering:
sanfs_ctl trace set -class classname -level number
Where classname is the class for which you are enabling tracing, and number is the level of verbosity of the tracing that increases from 0 to 5. You can also list up to twenty classes by separating them with a comma and no spaces.

The following example messages show the format of log messages created by the Solaris client code that resides in the kernel:

Apr 29 19:30:08 gas sanfs: [ID 967454 kern.warning] WARNING: csmGetRequest:
 \tmGetServerRequest() failed.
 tmrc:7
Apr 29 19:33:39 gas sanfs: [ID 991888 kern.warning] WARNING: Lost lease with
 server 0 lease 0x3000488cde0.
Apr 29 19:34:51 gas sanfs: [ID 733070 kern.notice] NOTICE: TmProcessIdentifyResp :
 clusterId:15022 installationId:740883aae7649163

The following example messages show the format of log messages created by the Solaris FlexSAN daemon:

Apr 29 19:34:53 gas sanfsd[1007]: [ID 826785 daemon.error] Couldn't send the SCSI
 command 0x12 to device /dev/dsk/c0t1d0s2: I/O error
Apr 29 19:34:54 gas sanfsd[1007]: [ID 518328 daemon.error] Failed to add the
 disk /dev/dsk/c2t9d0s2 for /mnt/mwytank
Apr 29 19:34:54 gas sanfsd[1007]: [ID 484526 daemon.error] osDoDiscoverVols: failed
 to add device /dev/rdsk/c2t9d0s2

Parent topic: Client diagnostic tools

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.