Patch-ID# 113730-01

NOTE:
***********************************************************************
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
***********************************************************************

Keywords: storedge 3320 se3320 se3000 raid storage firmware safte
Synopsis: SE3320 415G: StorEdge 3320 array controller firmware upgrade
Date: Jun/13/2006


Install Requirements: NA                      
                      
Solaris Release: 8 8_x86 9 9_x86 10 10_x86

SunOS Release: 5.8 5.8_x86 5.9 5.9_x86 5.10 5.10_x86

Unbundled Product: StorEdge 3320 Array Controller Firmware

Unbundled Release: 415G

Xref: 

Topic: 

Relevant Architectures: sparc i386

BugId's fixed with this patch: 6254634 6317661 6330757 6431154

Changes incorporated in this version: 6254634 6317661 6330757 6431154

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

README.113730-01
SUN-STOREDGE-3320-MIB.txt   # SNMP MIB for installation in SNMP Managers
SUN415G-3320.bin       # RAID controller firmware rev 415G
patchinfo
saftefw_3320_1180.bin  # SAF-TE firmware rev 1180

NOTE:
Topics Included in this file:
* Problem Description
* Invoking Sun StorEdge CLI
* Upgrading Controller Firmware
* SAF-TE Firmware Upgrade
* After Upgrading
* Special Install Instructions
====================

Problem Description:

--------------------
 
This patch contains firmware that is installed on the Sun StorEdge 3320
RAID array controller and expansion chassis using Sun StorEdge CLI, rather
than using installpatch or patchadd.  Two types of firmware are included: 
RAID controller firmware that is installed in RAID controller modules, and
SAF-TE firmware that is installed in both RAID controller chassis and
disk expansion chassis.
 
This patch also contains a SNMP MIB for installation in SNMP Managers such
as HP OpenView Network Node Manager. This MIB is specific to the Sun
StorEdge 3320. Refer to Appendix F, "SNMP Management Using HP OpenView," in
the Sun StorEdge 3000 Family RAID User's Guide for information about MIB
installation and use.
 
 
You do not need to install this patch if you have all of the following
firmware revision levels in all of your StorEdge 3320 enclosures:
 
         Controller firmware: 415G
         SAF-TE firmware:     1180
 
You do need to install this patch if you have any of the following:
 
  * controller firmware earlier than revision 415G
 
This patch contains firmware that is installed on the Sun StorEdge 3320
array using Sun StorEdge CLI, rather than using installpatch or patchadd.
 
 
RAID firmware 415G addresses the following issues:
 
6254634 Excessive write policy restore pop up messages
6317661 "No SAFTE devices found" message in sccli with 3 host channels
6330757 3310/3320 allow more than 128 luns to be mapped
6431154 3320: Cable error issues: error handling enhancement

Patch Installation Instructions:
==========================
 
Invoking Sun StorEdge CLI:
 
---------------------------
 
Version 2.3 or greater of the "sccli" CLI utility is required. It is included
in the SUNWsscs package, which may be downloaded from the Sun Download Center
or installed from the optional Sun StorEdge Professional Storage Manager CD.
 
For software installation or upgrading instructions, refer to the "Sun
StorEdge 3000 Family Software Installation Guide." Click the link for your
array on the Sun Documentation Centers Storage web page at:
 
sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/
 
Select the most recent version of software and then download the Software
Installation Guide.
 
The firmware procedures require the user to invoke Sun StorEdge CLI (sccli)
using the appropriate syntax for the type of connection used to manage the 
array.
 
If the array to be upgraded is a standalone SCSI JBOD, invoke sccli with the
name of an SAF-TE device:
 
        sccli /dev/es/ses<n>
 
If the array to be upgraded is a RAID subsystem attached to a SCSI HBA
installed in the local host, type the sccli command with no arguments:
 
        sccli
 
If more than one array is connected to local SCSI HBAs, sccli will display
a list from which the appropriate device may be selected.
 
If the array has an IP address configured, it may be managed remotely using
a network (or "out-of-band") connection.  To specify this mode, type:
 
        sccli [-w <password>] <hostname | ip>
 
where <password> is the password assigned to the controller, and 
<hostname | ip> is the hostname or IP address of the array.  Use single 
quote characters to quote the password if it contains any characters that 
are interpreted specially by the shell.  If no controller password is set, 
the -w option and password argument should be omitted.
 
To verify the version of "sccli" you are running type the following command
at the sccli> prompt:
 
       version
 
============================================
 
Upgrading Controller Firmware
 
--------------------------------------------
 
 1.  Verify the Product and Revision of the array.  Type the following 
     command at the sccli> prompt:
 
        show inquiry
 
    and examine the output.  If the "Product" is "StorEdge 3320 D" and 
    "Device Type: Enclosure" appears, the device is a JBOD chassis and has
    no controller firmware; skip to the "SAF-TE Firmware Upgrade" 
    section.    
 
    If the Product is not "StorEdge 3320," this patch does not apply.  
    Select a different device or discontinue installation of this patch.
 
    If the firmware version reported is 415G, the RAID controller 
    firmware does not need to be upgraded. Otherwise, continue with step 2.
 
 2. Verify single or dual controller.  Type the following command at the
     sccli> prompt:
 
        show redundancy
 
    and examine the output. If the "array redundancy" mode is not
    "Active-Active" AND the "redundancy" status is not "Enabled," skip to
    step 4 and follow the instructions for upgrading a single-controller
    configuration or for non-redundant configurations.
 
 3. ONLY if the "show redundancy" command reports that the Redundancy mode
    is "Active-Active" and that the status is "Enabled" (dual-controller),
    AND you are currently running 4.12E or later should you continue.
 
----
Note:
----
Entering the "download controller-firmware" command below will cause a
controlled reset and failover of both controller modules. During this process
host I/O can be temporarily affected and recoverable errors may be recorded.
This may have an impact of IO performance during the upgrade procedure.
Retryable I/O errors and bus resets can be visible on attached hosts.
 
    Perform the firmware upgrade by typing the following command at the
    sccli> prompt:
 
        download controller-firmware SUN415G-3320.bin
 
    The sccli command will display the following messages:
 
     sccli: Downloading controller firmware...programming flash memory...done
     sccli: Engaging firmware...done
     sccli> 
 
    Wait until the sccli> prompt appears again, which may take 10 minutes or
    more, before proceeding.
 
    If you see an error message containing the text: "please repeat download 
    command" or "controller firmware download ok, but engage operation is 
    not allowed," the controller was unable to perform the firmware 
    upgrade. Repeat the download as follows:
 
    Stop all I/O activity and unmount any filesystems or volumes mounted by
    a volume manager from the array.  Then, type the following command at
    the sccli> prompt:
 
        download controller-firmware -r SUN415G-3320.bin
 
    When download completes, skip to step 5.
 
 4. Single-controller or non-redundant configurations require a reset after
    downloading new firmware. This type of upgrade requires that the
    controller be reset, which in turn causes the controller to stop
    servicing I/O requests for several minutes.
 
    Stop all I/O activity and unmount any filesystems or volumes mounted by
    a volume manager from the array.  Then, type the following command at
    the sccli> prompt:
 
        download controller-firmware -r SUN415G-3320.bin
 
    The sccli command will display the following messages:
 
     sccli: Downloading controller firmware...programming flash memory...done
     sccli: Resetting controller...done
     sccli> 
 
    Wait until the sccli> prompt appears again, which may take 10 minutes or
    more, before proceeding.
 
 5. Verify that the firmware upgrade succeeded by examining the firmware
    revision again. Type the following command at the sccli> prompt:
 
         show inquiry
 
    and verify that the firmware revision is now reported as 415G.
 
 6. If no errors occurred, continue to "SAF-TE Firmware Upgrade."
 
========================
 
SAF-TE Firmware Upgrade:
 
------------------------
 
 1. Verify the SAF-TE firmware version. Type the following command at the
    sccli> prompt:
 
        show safte
 
        sccli> show safte
        Ch  Id  Chassis  Vendor  Product ID        Rev   Package
        ---------------------------------------------------------
         0  14  000187   SUN     StorEdge 3320  A  1180  1180
         2  15  005632   SUN     StorEdge 3320  D  1180  1180
 
    Examine the SAF-TE firmware revision codes displayed in the "Rev"
    column and "Package" column. If all the lines contain a revision code
    of 1180 in the "Rev" field and "Package" field then no SAF-TE firmware
    update is necessary and you should skip to "After Upgrading."  In the
    example above, the "Rev" field and "Package" field is 1180 for both
    devices and therefore NO upgrade is needed.
 
    -----
    Note:
    -----
    Only one line of information may be displayed for a standalone expansion
    (JBOD) chassis, and more than two lines may be displayed if a RAID
    enclosure has expansion chassis connected to it. The Product ID field
    will be "StorEdge 3320 A" for SAF-TE devices internal to the RAID array
    chassis, and "StorEdge 3320 D" for SAF-TE devices internal to the
    expansion chassis.
 
 2. Since the SSCS agent may interfere with the download of SAF-TE code, it
    is necessary to stop any SSCS agent that may be running on a host
    connected to the array controller.  To stop the SSCS agent, issue the
    shell command as "root" user:
 
       /etc/init.d/ssagent stop
 
    If the SSCS agent is running on a Microsoft Windows system connected
    to the array, use the Services application (Start->Run->services.msc)
    to stop the SSCS Agent service.
 
    StorADE, or any other application that monitors the status of the
    enclosure, may also interfere with controller or SAF-TE firmware
    downloads. Stop the StorADE agent software, or any other software that
    monitors the array, following the procedures described in the
    documentation for that application.
 
 4. Perform the upgrade. Type the following command at the sccli> prompt:
 
       download safte-firmware saftefw_3320_1180.bin
 
    -----
    Note:
    -----
    It is not necessary to reset the RAID controller afterwards; however,
    until the next controller reset, the firmware's menu interface may
    continue to display the old SAF-TE firmware revision.
 
 5. Verify that all SAF-TE devices have been upgraded. Type the following
    command at the sccli> prompt:
 
        show safte
 
        sccli> show safte
        Ch  Id  Chassis  Vendor  Product ID        Rev   Package
        ---------------------------------------------------------
         0  14  012345   SUN     StorEdge 3320  A  1180  1180
         2  15  005632   SUN     StorEdge 3320  D  1180  1180
 
 
    The lines should now contain a revision of 1180 as indicated by the
    "Rev" column and the "Package" column.
 
================
 
After Upgrading:
 
----------------
 
 1. If the SSCS agent was stopped, restart it with the command 
    "/etc/init.d/ssagent start" if it is installed on Solaris,
    or using the Services utility (Start->Run->"services.msc") if it
    is installed on Microsoft Windows.
 
 2. If other storage management software such as StorADE was stopped,
    restart it following the procedures in the documentation for that
    software.
 
=============================

Special Install Instructions:
-----------------------------
 
None.

README -- Last modified date:  Tuesday, June 13, 2006

