Sun Storage 5310 NAS Appliance
 
Sun Storage 5320 NAS Appliance
 
Sun Storage 5310 NAS Gateway System
 

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

• Data gathering

    # telnet NAS

2. Check to see if the appropriate output directories exist on the Sun StorEdge 5310 NAS Appliance or StorageTek 5320 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

See note at bottom of page

3. Once the directories have been created, load the runtime lsi module:

    NAS> load lsi_menu

4. 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] 

5. 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] 

6. 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

7. When the data collection has finished, the Support Menu will be redisplayed, select option number 10 "Exit".

8. The Main menu will be redisplayed, select option number 6 "Exit". The NAS command prompt is then displayed.

9. At this point, all of the extracted data is located in either /dvol/support/2882/cltr0 or /dvol/support/399x/cltr0

Transfer these files to the unix workstation via FTP:

   # ftp <ip_address or host_name of NAS>

Log in as admin user providing password if necessary.

Change directory to the appropriate directory:

      cd /dvol/support/2882/ctlr0
== or ==
cd /dvol/support/399x/ctlr0

Set transfer mode to binary:

      bin 

Transfer the files to the unix host:

      mget *
(files will transfer one at a time)

Terminate the FTP session:

      bye

Upon completion of the FTP transfer, the backend data files will be located on the UNIX[R] workstation in the current working directory.

Note:

Sub-directories ctlr0 and ctlr1 will be automatically created when the LSI menu is used.

If the command line option is used to extract support data, the following directories must exist prior to issuance of the command(s):

/dvol/support/2882/ctlr0
/dvol/support/2882/ctlr1

/dvol/support/399x/ctlr0
/dvol/support/399x/ctlr1

Command line examples:

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=1

This solution has no attachment