Sun Storage 5210 NAS Appliance
 

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

______________________________________________________________________________
PHASE I Code Update preparation - At the NAS head
______________________________________________________________________________
1. Telnet xxx.xxx.xxx.xxx   (i.e. xxx.xxx.xxx.xxx is the IP of the NAS head)
2. At the prompt type admin followed by the enter key
> admin
3. Make the cvol shareable
> set system.export_bootdir yes
> load unixtools
4. Create the specific subdirecties shown below:
> mkdir /cvol/firmware
> mkdir /cvol/firmware/mrc
To confirm directory exists or list files in a directory, type:
ls /cvol/firmware
5. Type menu at the prompt to go into the telnet menu
> menu
6. If using Unix use the telnet menu and select option F - Hosts
from the menu. Enter in the host name and IP number.  Use the
Escape key to go back to the main telnet menu.
7. Select option M - Trusted Hosts and enter the server name. Add the
server to the trusted list by entering the 7 key.
Note: A trusted host will have full rights to all the NAS storage devices
including the cvol and dvol. It is best to disable the share, remove the
IP from the trusted host list, and change the "set system.export_bootdir no"
once completed for the safety of the systems files.
8.  Escape back to the main menu
9.  Select "CIFS/SMB configuration" from the main menu located near the bottom
right corner of the screen. The letter key used will vary depending on how
many other optional loadable modules are resident.
10. Select Option E for Shares
11. Select Option 8 Add a share
12. Key in the share name of "cvol" and press the enter key
13. Type the full path location of the partition located on the NAS head
/cvol
14. Push enter through all other share options which can remain at defaults
or are optional. If ADS is used, make sure to include the container or
organizational unit.
example:  cu=<container name> ou=<organizational name>
15. Select Option 7 Save changes
_______________________________________________________________________
PHASE II Code update client preparation
_______________________________________________________________________
At the Unix or Solaris machine
1. Create a subdirectory and mount the share
# mkdir /SE5210
# mount xxx.xxx.xxx.xxx:/cvol /SE5210
2. Download the firmware file and latest OS Image file from sunsolve
The zipped patch contains both code files.
4. cp /xxxxxxxx.rom /cvol/firmware/mrc
At the Windows machine using the Microsoft GUI
1. Right mouse click on My network places
2. Select Map Network drive
3. Enter in the path //<server>/cvol
server = server name or IP number
4. Drag and drop with the mouse the .rom file to the /cvol/firmware/mrc path.
The .img file will transport to the NAS head when the upgrade process
starts through the NAS head GUI.
Windows Command line
1. net use y: \\192.168.0.8\cvol
2. Download the LSI firmware file and latest OS Image file from sunsolve
The zipped patch contains both code files.
3. xcopy c:\xxxxxx.rom  y:\firmware\mrc.
____________________________________________________________________
Phase III - Update OS Image and firmware using the NAS head GUI
___________________________________________________________________
1. Mouse click on System Operations
2. Mouse Click on Update Software
3. Click on browse and find the file on the local disk drive
4. Click on Update.
5. The activity bar will move from start to finish and a message will appear
prompting to reboot the server.
6. Click on yes.
The system will reboot.  At this time the firmware will upgrade first.
The code has a built-in script which will reboot the machine after upgrade.
When the system boots again the OS image script will begin and upgrade the
Operating system.  The system will now boot up completely.
_______________________________________________________________________
PHASE IV - Viewing upgrade results from the NAS GUI
_______________________________________________________________________
1. Click on System Operations > Update OS
2. Click on RAID > View Controller Information

This solution has no attachment