Sun StorageTek[TM] 5000 Series NAS: How to use the lsi_menu and commands to collect CSM100/CSM200 backend support data

Asset ID:	1-71-1002481.1
Update Date:	2011-11-28
Keywords:

Solution Type Technical Instruction Sure

Solution 1002481.1 : Sun StorageTek[TM] 5000 Series NAS: How to use the lsi_menu and commands to collect CSM100/CSM200 backend support data

Applies to:

Sun Storage 5310 NAS Appliance - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 5320 NAS Appliance - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 5220 NAS Appliance - Version: Not Applicable and later    [Release: N/A and later]
All Platforms

Goal

Included in NAS OS release 4.20 and above, is a new command that allows collection of data from Sun StorageTek[TM] 5000 Series NAS RAID Expansion Unit connected to the Sun StorEdge[TM] 5310 NAS Appliance, Sun StorageTek[TM] 5220 NAS Appliance or Sun StorageTek[TM] 5320 NAS Appliance.

The Sun StorageTek[TM] 5000 Series NAS RAID Expansion Unit is either a modified Sun StorEdge[TM] 6130 Array (CSM100) or a Sun StorageTek[TM] 6140 Array (CSM200) storage array.

This document provides details on the configuration and use of this new command.

Solution

Steps to Follow

Preparation

To successfully collect the data from the Sun StorageTek[TM] 5000 Series NAS Raid Expansion Unit certain folders need to exist on the NAS appliance. If they do not exist they need to be created. This requires to connect to the CLI of the NAS appliance.

All collected data for backend storage goes to following folders, which need to exist or need to be created:

NAS Appliance	Raid Expansion Unit Type	Folder
Sun StorEdge[TM] 5310	Sun StorageTek[TM] 6130	/dvol/support/2882
Sun StorageTek[TM] 5220	Sun StorageTek[TM] 6140	/dvol/support/399x
Sun StorageTek[TM] 5320	Sun StorageTek[TM] 6130	/dvol/support/2882
Sun StorageTek[TM] 5320 RoHS	Sun StorageTek[TM] 6140	/dvol/support/399x

To create or verify the existence of the target folder follow the process outlined below:

Connect to the NAS via command line:
# telnet NAS
Check to see if the appropriate output directories exist on the Sun StorageTek[TM] 5000 NAS Appliance:
NAS> ls /dvol/support 2882 399x
If the directory or directories do not exist, they must be created:
NAS> mkdir /dvol/support/2882 NAS> mkdir /dvol/support/399x

Collecting the Data

Once the directories have been created, load the run time LSI module:
NAS> load lsi_menu
Invoke the program:
NAS> lsi_menu
The following menu will appear:
Found 1 Array ************************************************* * SUN Microsystems * * Engenio Raid Utility * * Version 1.0 * ************************************************* 1. Array Menu 2. VolumeGroup Menu 3. Volume Menu 4. Disk Drive Menu 5. Support Menu 6. Exit Selection: [1 - 6]
Enter option number 5 for "Support Menu"
The following support menu will appear:
********** Support Menu ********** 1. Show Network Configuration 2. Set Network Configuration 3. Enable/Disable Remote Login 4. Extract Support Data 5. View Major Event Log (MEL) 6. Locate Tray 7. Locate Drive 8. Show CRS 9. Fix CRS 10. Exit Selection: [1 - 10]
Enter option number 4 for "Extract Support Data", The Sun StorEdge 5310 NAS Appliance or StorageTek 5320 NAS Appliance will extract support data from the backend storage. Be patient, this is a rather lengthy process.
Various updates will be displayed during the data extraction:
Array Number: 1 Extracting Support Data from Array 1... Gathering state capture data Gathering volume performance statistical data Gathering storage array profile data Gathering NVSRAM data Gathering major event data Total number of events: 8191 [1219, 9410] Logging MEL entries to file: /dvol/support/2882/ctlr0/eall.txt 10% complete 20% complete 30% complete 40% complete 50% complete 60% complete 70% complete 80% complete 90% complete Total events: 8191 are in file /dvol/support/2882/ctlr0/eall.txt Converting binary event entries to readable text Gathering critical event data Total number of events: 8191 [1219, 9410] Logging MEL entries to file: /dvol/support/2882/ctlr0/ecri.txt Total critical events: 91 are in file /dvol/support/2882/ctlr0/ecri.txt Converting binary event entries to readable text Gathering all drive's log data Gathering unreadable sectors data base Zipping all array support files Zipping /dvol/support/2882/ctlr0/stat.txt.gz Zipping /dvol/support/2882/ctlr0/stor.txt.gz Zipping /dvol/support/2882/ctlr0/nram.txt.gz Zipping /dvol/support/2882/ctlr0/perf.txt.gz Zipping /dvol/support/2882/ctlr0/drv.bin.gz Zipping /dvol/support/2882/ctlr0/usec.txt.gz Zipping /dvol/support/2882/ctlr0/eall.txt.gz Zipping /dvol/support/2882/ctlr/ecri.txt.gz
When the data collection has finished, the Support Menu will be redisplayed, select option number 10 "Exit", the number of options might vary from version to version of the program. The Main menu will be displayed again.
Select option number 6 "Exit" to quit the program and to return to the CLI, command prompt is displayed.

At this point, all of the extracted data is located in either /dvol/support/2882/ctlr0 or /dvol/support/399x/ctlr0 and needs to be transferred to your client.

Transfer these files to a client via FTP:

To get the files of the Sun StorageTek[TM] 5000 NAS appliance you could use any ftp client you are familiar with, provide the credentials and change to the appropriate directory. Set the transfer mode to binary, turn off prompt and use mget to transfer the files. A sample is shown below.

$ftp NAS
Connected to rigel.de.oracle.com.
220-Local time is now 13:51 and the system load is 0%.
220 You will be disconnected after 900 seconds of inactivity.
User (NAS:(none)): admin
331 Admin login OK. Password required.
Password:
230-User admin logged in.
230 Current directory is /
ftp> cd /dvol/support/399x/ctlr0
250 Changed to /dvol/support/399x/ctlr0
ftp> bin
200 TYPE is now 8-bit binary
ftp> prompt
Interactive mode Off .
ftp> mget *
200 TYPE is now 8-bit binary
200 PORT command successful
150 Opening data connection with 10.175.13.97:56582
226 Transfer complete.
ftp: 1249 bytes received in 0,00Seconds 1249000,00Kbytes/sec.
200 PORT command successful
150-Opening data connection with 10.175.13.97:56583
150 63K bytes to download
226 Transfer complete.
ftp: 65201 bytes received in 0,48Seconds 136,40Kbytes/sec.
200 PORT command successful
150 Opening data connection with 10.175.13.97:56586
226 Transfer complete.
ftp: 862 bytes received in 0,00Seconds 862000,00Kbytes/sec.
200 PORT command successful
150 Opening data connection with 10.175.13.97:56587
226 Transfer complete.
ftp: 1156 bytes received in 0,00Seconds 1156,00Kbytes/sec.
200 PORT command successful
150 Opening data connection with 10.175.13.97:56588
226 Transfer complete.
ftp: 373 bytes received in 0,00Seconds 373000,00Kbytes/sec.
200 PORT command successful
150-Opening data connection with 10.175.13.97:56592
150 235K bytes to download
226 Transfer complete.
ftp: 241085 bytes received in 1,23Seconds 196,32Kbytes/sec.
200 PORT command successful
150 Opening data connection with 10.175.13.97:56594
226 Transfer complete.
ftp: 3242 bytes received in 0,26Seconds 12,33Kbytes/sec.
200 PORT command successful
150 Opening data connection with 10.175.13.97:56595
226 Transfer complete.
ftp: 20 bytes received in 0,00Seconds 20000,00Kbytes/sec.
ftp> quit
221-Goodbye. You uploaded 0 and downloaded 305K bytes.
221 CPU time spent on you: 0.000 seconds.

$

Upon completion of the FTP transfer, the data files will be located in the current working directory of the client.

Sub-directories ctlr0 and ctlr1 will be automatically created when command line utility lsi_menu is used. If the corresponding command line option for raidctl is used to extract support data, directories for the controller need to preexist, see example below.
For a NAS appliance with two RAID Expansion Units connected directories for ctlr2 and ctlr3 are also needed.
Directories ctlr0 and ctlr1 belong to the first detected array and ctlr2 and ctlr3 belong to second array attached to the NAS head.

Required directories on the NAS head

/dvol/support/2882/ctlr0

/dvol/support/2882/ctlr1
/dvol/support/2882/ctlr2
/dvol/support/2882/ctlr3
/dvol/support/399x/ctlr0

/dvol/support/399x/ctlr1
/dvol/support/399x/ctlr2
/dvol/support/399x/ctlr3

Command line examples for direct collection of support data

san5310a-usan > raidctl get type=lsi target=supportdata ctlr=all

san5310a-usan > raidctl get type=lsi target=supportdata ctlr=0

san5310a-usan > raidctl get type=lsi target=supportdata ctlr=2

Attachments

This solution has no attachment