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

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

Included with each version of the NAS OA patch 119351-xx for the 5310 and patch 119352-xx for the 5320 are the firmware files for the CSM1 (6130) and CSM2 (6140) backend storage arrays. As part of a NAS OS upgrade, it is necessary to update the backend firmware as well.
Obtain the current NAS OS patch and unzip into a work directory. Once unzipped, the firmware will be in the directory ./<patch_ID>/CSM1_FW  for 6130s and ./<patch_ID>/CSM2_FW for 6410s.
In the example detailed below, the NAS 4.20 patch was downloaded and extracted. It is possible that with different NAS OS releases, the backend firmware files will be different than those listed below.  The CSM1 array firmware files will include the NVSRAM identified by the String N2882_xxx.dlp, the Controller firmware identified by SNAP_xxx.dlp and the JBOD firmware identified by esm...  The CSM2 array firmware files will include the NVSRAM identified by the String N399X_xxx.dlp, the Controller firmware identified by RC_xxx.dlp. and the JBOD firmware identified by the file extension .esm.
The listing below are the firmware files included with the 4.20 NAS os patch.
6130
----
NVSRAM:              N2882-612843-505.dlp
CTLR F/W:            SNAP_288X_06122710.dlp
Fiber Channel JBOD:  esm9631.s3r
SATA JBOD:           esm9726.dl
6140
----
NVSRAM:              N399X-616843-504.dlp
CTLR F/W:            RC_06168110_amethyst2_apollo_399x.dlp
JBOD:                husker9865.esm
The upgrade process consists of placing the firmware files on the
NAS head in the appropriate directory followed by a reboot of the
NAS head.  The steps to do this are below:
1. Telnet to the NAS head and verify that  the appropriate firmware
directories exist.  If the directories are missing, you must manually
create them.
The directories required for a 6130 firmware upgrade are as follows:
5310NAS > ls /cvol/firmware/2882
ctlr            drive           nvsram      jbod
The 6130 firmware files extracted from the NAS OS patch must be ftp'd
to the NAS head and located in the appropriate firmware directory below the directory 2282.
The directories required for a 6140 firmware upgrade are as follows:
5310NAS > ls /cvol/firmware/399x
ctlr            drive           nvsram      jbod
The 6140 firmware files extracted from the NAS os patch must be ftp'd
to the NAS head and located in the appropriate firmware directory below the directory 399x
2. Once the firmware files are located on the NAS head, you
have 2 options for performing the firmware upgrade.  The easiset
method is to reboot the NAS head. As part of the reboot process,
the firmware directories are checked. If firmware files are found, they
are loaded to the backend storage and deleted from the directory.
Alternately, you can telnet to the NAS head and perform the upgrade via commandline. The following details the steps involved in using the raidctl commandline command to perform the upgrade.
1. Following step 1 detailed above, Verifythat the necessary firware directories
exist on the 5310/5320. Locate the firmware files from the patch in these
directories.
2. Telnet to the NAS head, log in as admin and perform the firmware update using
the following command.
5310NAS >raidctl download type=lsi target=all
In the following example, ONLY the controller firmware, snap_288.dlp has been
placed in the /cvol/firmware/2882/ctlr directory prior to the execution of the
raidctl command therefore only the controller firmware will be udpated on the
backend 6130.  Had the other firmware files been transfered to the NAS head,
they too would have been loaded to the 6130 as well.
5310NAS >raidctl download type=lsi target=all
BoardID=<2882>
Checking dir </cvol/firmware/2882/nvsram>
Checking dir </cvol/firmware/2882/ctlr>
*** Found <snap_288.dlp>
Checking dir </cvol/firmware/2882/jbod>
Checking dir </cvol/firmware/2882/drive>
lsi_suspend_io: Suspending I/O on ctlr 0
lsi_wait_sa_quiet: *** isp2 quiet - no pending reqs
lsi_suspend_io: Suspending I/O on ctlr 1
lsi_wait_sa_quiet: *** isp1 quiet - no pending reqs
Flashing RAID Ctlr0: /cvol/firmware/2882/ctlr/snap_288.dlp (5080992)
lsi_download_fw2: image_size=5080992 chunk=32768 iter=156
Firmware Download   5% complete
Firmware Download  10% complete
Firmware Download  15% complete
....
Firmware Download 100% complete
Wait 180 secs for F/W to become ready
Waiting for Ctlr 0 to become ACTIVE
Controller 0 - now ACTIVE <0x2150A>
Waiting for Ctlr 1 to become ACTIVE
Controller 1 - now ACTIVE <0x2150A>
lsi_resume_io: Resuming I/O on ctlr 0
lsi_resume_io: Resuming I/O on ctlr 1
3. To verify that the upgrade had been successful, list the 6130 controller
profile.  In this example, we are expecting a controller version of 06.12.27.10
5310NAS >raidctl get type=lsi target=profile ctlr=0..N
Controller in Tray 0, Slot A
Status: Online
Current Configuration
Firmware version: 06.12.27.10
Appware version: 06.12.27.10
Bootware version: 06.12.27.10
NVSRAM version: N2882-612843-503
Pending Configuration
Firmware version: None
Appware version: Non
Bootware version: None
NVSRAM version: None
Transferred on: None
Board ID: 2882
</cvol/firmware/2882/nvsram>N2882-612843-505.dlp
</cvol/firmware/2882/ctlr>SNAP_288X_06122710.dlp
</cvol/firmware/2882/jbod>
</cvol/firmware/2882/drive>D_ST314680FSUN146G_0407.dlp(d_st3146.dlp)

This solution has no attachment