Sun Storage 5210 NAS Appliance
 
Sun Storage 5220 NAS Appliance
 
Sun Storage 5310 NAS Appliance
 
Sun Storage 5320 NAS Gateway/Cluster System
 
Sun Storage 5320 NAS Appliance
 
Sun Storage 5310 NAS Gateway System
 

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

Symptoms:

• Troubleshooting
• Data collection
  

Purpose/scope:

The purpose of this document is to list the data that should be collected when a Sun StorageTek[TM] NAS case is received. Data collected as outlined below will help in better understanding and troubleshootingthe problem,  which in turn can expedite the resolution of the issue.

1. Diagnostic E-Mail
   Diagnostic E-mail contains all details of the System setup and configuration. Diagnostic mail also contains boot logs, system logs and logs of any panic events that have occurred. Note that system logs collected by the diagnostic mail are volatile. A limited amount of messages are stored in memory, using a circular buffer, and these are lost if a NAS appliance is rebooted. See below for information on archiving this log data. If this has not already been set up, it is important to capture the diagnostic as soon as possible after the event you are trying to capture.
   Please read the <Document: 1002401.1> on how to collect diagnostic e-mail.
2. Syslogs
   As noted above system logs are kept in a circular buffer. The logs can be viewed from telnet/webadmin/CLI and are collected by Diagnostic mail. To archive these logs and capture system log data long-term, it is possible to setup the syslog to redirect the logs to a file or a loghost. Do not use /cvol or /dvol for this purpose. If present, the logging path or server can be determined from Diagnostic E-Mail or show output (display environment variables) on the NAS. From the output of show command look for "syslogd.filename=<pathname_file>". This file would contain all system logs and should be collected for troubleshooting.
3. Boot Logs
   Each time NAS/Gateway appliance boots, the initial portion of the system log is captured to the bootlog file. These files show various boot time information. "bootlog" file are created under /cvol/log and most recent eleven log files are saved named as "bootlog", "bootlog.0", ... "bootlog.10". These are included in Diagnostic E-Mail, but may also be collected or examined separately..
4. Debug Logs
   Debug Logs are only created during a system panic under directory /cvol/log. In case a NAS/Gateway appliance panics, the system attempt to save the information to dbglog files. They are very useful in troubleshooting panic situations. There can be total of eleven dbglogs saved on the system named as "dbglog", "dbglog.1" ... "dbglog.10". dbglogs can contain valuable information such as panic stack trace, memory pool information, the current system log, and all currently defined variables.
5. NDMP Logs
   These logs should be collected when there is an issue with backup. Everything that occurs with ndmp backup devices and jobs is logged to this file. The location of the log files is defined by Console/Telenet ndmp command "ndmp set debug.path=<path>". By default ndmp logs are disabled and it can be enabled by CLI command "ndmp set debug.level=full". However, this command would only work if valid data path exists.
6. Performance issues
   NAS includes built-in tools which can be used to collect performance data of Network and Backend storage. The CLI tools are ratewrite and arateread can be used to collect data to check the performance of the backend storage. Check <Document: 1011237.1> for more information on aratewrite and rateread
7. NAS Extractor
   NAS Extractor is a tool available from TSC Storage to collect data from various commands. This provides additional information about the NAS/Gateway appliance and is very helpful in understanding the state of the appliance.
8. Core Dump
   Beginning with OS version 4.21, the NAS has the capability to collect a core dump in the event of a panic or hang condition Check <Document: 1005348.1> for details on how to collect a core dump.
9. Network Packet Capture
   The NAS has a built-in tool that can be used to capture packets from the network and save them to a file. This can be useful for many different types of issues, problems joining a Windows domain, security issues, etc. Check <Document: 1004130.1> for more information on the configuration and usage of Network Packet Capture.

NOTE: With NAS OS Version 4.21 and above, while collecting Diagnostic E-Mail a tar ball file (diag.tar.gz) is created which includes :

1. Diagnostic E-Mail
2. Configuration files /dvol/etc
3. Debug Logs
4. Boot Logs
5. Storage array data (SupportData) if it was previously collected with lsi_menu command. For more details please refer to <Document: 1002481.1>.
6. Syslogs if logging is enabled locally ie if environment variables "syslogd.logtofile=yes" and "syslogd.filename" have a valid path and filename.

Click here to download NAS Extractor. Please read the instructions for help on its usage.

The Knowledge Work Queue for this article is KNO-STO-NAS

This solution has no attachment