OBSOLETE Patch-ID# 113724-01
Keywords: storedge 3511 se3511 se3000 raid storage firmware ses pld
Synopsis: Obsoleted by: 113724-03 SE3511: StorEdge 3511 array firmware upgrade
Date: Nov/24/2004


Install Requirements: NA                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: StorEdge 3511 Array Controller Firmware

Unbundled Release: 1.0

Xref: 

Topic: 

Relevant Architectures: sparc

BugId's fixed with this patch: 5051226 5056389 5057239 6179058

Changes incorporated in this version: 5051226 5056389 5057239 6179058

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: 

        FW_DP0555a.dlf          # SATA Router firmware rev DP0555a
        PC_BB42.dat             # SATA MUX firmware rev BB42
        README.113724-01
        patchinfo
        sata1000.s3r            # SE3511 Enclosure PLD Firmware rev 1000
        sesfw_sunsata_0412.s3r  # SE3511 Enclosure SES Firmware rev 0412
SUN327R-3511.bin        # SE3511 Array Controller Firmware rev 327R

Problem Description:

This patch contains all five types of firmware updates for the StorEdge
3511 array subsystem: firmware for the array RAID controllers; firmware for
the SES processors in each enclosure; firmware for the programmable
logic devices (PLDs) that route Fibre Channel data within each enclosure;
firmware for SATA routers; and firmware for SATA MUX boards.
 
The SES, PLD, router, and MUX firmware updates are applicable to the StorEdge
3511 SATA Array expansion chassis (JBOD) as well as the RAID Array chassis.  
 
You do not need to install this patch if you have all of the following
firmware revision levels in all of your StorEdge 3511 enclosures:
 
         Controller firmware: 327R
         SES firmware:        0412
         PLD firmware:        1000
         Router firmware:     DP0555a
         MUX firmware:        BB42
 
If you're not sure how to determine what firmware you currently have
installed, follow the instructions in the Patch Installation
Instructions section.
 
SATA Router firmware DPO555a addresses the following issues:
 
5056389 Temperature sensors go off and bring down controller
5057239 Controller replacement caused drives to fail.
 
SES firmware 0412 addresses the following issues:
 
5051226 sscli: show config -x frequently misses FC_JBOD_IOM
6179058 Unable to use FC port 4 and 5 on 3511

Patch Installation Instructions:
--------------------------------
 
This patch contains firmware which is installed on the StorEdge 3511
array, rather than using installpatch or patchadd.
 
The prerequisites for installing the new firmware are:
 
 * Version 1.6.1 or later of the "sccli" CLI utility included in the 
   SUNWsccli package, which may be installed from the Sun StorEdge 
   Professional Storage Manager CD or downloaded from the Sun Download
   Center.  The sccli command is installed, by default, in 
   /opt/SUNWsscs/sbin on Solaris systems, and a symbolic link is 
   provided in /usr/sbin so that the user may simply type "sccli" to
   invoke it.
 
   If you do not have this package installed, or if you have an older
   version, download and install the latest version from the Sun
   Download Center:
 
    1. Go to http://www.sun.com/software/download/index.jsp and
       click on the link for "Storage Management" under the "Systems
       Administration" heading.
    2. Click on the link for "StorEdge 3000 Family Storage 
       Products--Related Software"
    3. Log in or register as necessary
    4. Download the file VVV_sw_XXX.zip where "VVV" is the software
       version (1.6.1 or later) and "XXX" describes your platform.
    5. Unzip the file and install the package.  For example, on Solaris:
 
            pkgrm SUNWsccli                             # remove old version
            pkgadd -d solaris/`uname -p` SUNWsccli
 
    6. Verify that the correct version is installed by typing
 
            /opt/SUNWsscs/sbin/sccli version
 
   DO NOT ATTEMPT TO USE AN EARLIER VERSION OF SCCLI.
 
 * For RAID controller firmware upgrades, an Ethernet connection (or two
   Ethernet connections for dual-controller configurations) is required
   for out-of-band firmware upgrades, if the array to be upgraded is not
   connected to the host on which the upgrades are to be performed.
 
   In order to use the Ethernet connection(s), the controller must
   have an IP address assigned.
 
 * A Fibre Channel connection to the array is required when no network
   connection to the array is available.
 
Unpack the patch into any convenient directory (for example, /var/tmp),
and refer to the Special Install Instructions below.

Special Install Instructions:
----------------------------- 
 
*** Warning *** Warning *** Warning *** Warning *** Warning ***
 
DO NOT INSTALL THIS PATCH with a version of sccli earlier than version
1.6.1.  If an earlier version is installed, refer to the upgrade
instructions above.
 
*** Warning *** Warning *** Warning *** Warning *** Warning ***
 
If the array controller is power-cycled at the wrong time during
programming of the PLD firmware, the array controller may be rendered
inoperable and require replacement.
 
This procedure upgrades five different firmware files for five
different hardware components: the RAID controller, which processes I/O
requests; the SCSI Enclosure Services (SES) processor, which handles
enclosure management functions; the Programmable Logic Device (PLD)
which is responsible for routing of Fibre Channel traffic within the
subsystem; the SATA router, which provides SR-1216 router firmware to 
all SATA routers in the SATA unit; and the SATA MUX, which controls the 
path microcode on the multiplexer (MUX) boards behind the SATA router.
 
Preparing to Upgrade Firmware:
------------------------------
 
If you are using controller firmware version 3.27R, then no firmware 
upgrade is necessary and you should proceed to step 7.
 
 1. Change your working directory to the directory in which the patch
    was unpacked and confirm that the SUN327R-3511.bin file is present
    using the "ls" command.
 
 2. Invoke sccli, using the appropriate syntax for the type of
    connection used to manage the array:
 
    If the array to be upgraded is a RAID subsystem attached to a Fibre
    Channel HBA installed in the local host, simply type the sccli
    command with no arguments:
 
        sccli
 
    If more than one array is connected to local Fibre Channel 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>
 
    where <password> is the password assigned to the controller, and
    <hostname> 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.  If the hostname for a locally attached array is unknown,
    the "--oob" option may be specified instead of a hostname, and sccli
    will try to determine the IP address of a locally-attached array
    automatically.
 
    Verify that you're running sccli version 1.6.1 or later with the
    "version" command.
 
 3. Verify the Product and Revision of the array.  Type the command
 
        show inquiry
 
    If the Product is not "StorEdge 3511", this patch does not
    apply.  Select a different device or discontinue installation of
    this patch.
 
    If the firmware version reported is 327R or higher, the RAID
    controller firmware does not need to be upgraded; proceed to step 7.
 
 4. If array contains only one controller, or the "show redundancy" command 
    does not report that the array redundancy mode is Active-Active and its
    redundancy status is "Enabled", the controller firmware upgrade will 
    require that the controller be reset, which in turn will cause the
    controller to stop service I/O requests for several minutes.  If one
    of the previous conditions is true, skip to step 5 and follow the
    instructions for on upgrading a single-controller configuration.
 
    If you have a dual controller configuration, and the "show redundancy" 
    command reports that the Redundancy mode is "Active-Active" and that 
    the status is "Enabled", perform a live firmware upgrade by typing the
    following command at the CLI prompt:
 
         download controller-firmware SUN327R-3511.bin
 
    The sccli command will display messages indicating that it is
    downloading the firmware, programming the controller's flash memory,
    and "engaging" the new firmware.  Wait until the "sccli>" prompt
    appears again, or 3-4 minutes, 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 a
    live firmware upgrade.  Wait until it is OK to stop I/O to the
    array, and then follow the instructions in step 5 to do a
    non-live firmware upgrade.
 
    If no error messages were displayed, proceed with step 6.
 
 5. Single controller configurations, or dual controller configurations
    which are in degraded status must be reset after downloading new 
    firmware.
 
    First, stop all I/O activity and unmount any filesystems or volumes
    mounted from the array.  Then, at the "sccli>" prompt, type:
 
        download controller-firmware -r SUN327R-3511.bin
 
    You should see output indicating that the firmware is being
    downloaded and programmed into flash memory, and then a message
    indicating that the controller is being reset.  Wait until the
    "sccli>" prompt appears before proceeding.
 
 6. Verify that the firmware upgrade succeeded by examining the firmware
    revision again. At the "sccli>" prompt, type
 
         show inquiry
 
    and verify that the firmware revision is now reported as "327R".
 
SES Firmware Upgrade:
---------------------
 
If you are using SES firmware revision 0412, then no SES firmware 
update is necessary and you should proceed to step 12.
 
 7. Verify the SES firmware version using the sccli "show ses" command:
 
      sccli> show ses
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWPN             ...
        ---------------------------------------------------------------...
         2  12 000187  SUN StorEdge 3511F A 0403 1000 204000C0FF000187 ...
                                                             Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0403 1000 204000C0FF000187 ...
                                                             Topology: ...
 
    Note that more than two lines may be displayed if a RAID enclosure 
    has expansion chassis connected to it. The Product ID field will be
    "StorEdge 3511F A" for SES devices internal to the RAID array chassis,
    and "StorEdge 3511F D" for SES devices internal to the expansion chassis.
 
 8. Examine the SES firmware revision codes displayed in the "Rev"
    column.  If all of the lines contain a revision code of 0412 in the
    "Rev" field, then no SES firmware update is necessary and you should
    proceed to step 12.  In this example, the "Rev" field is 0403 for
    both devices and therefore an upgrade is needed.
 
 9. Since the SSCS agent may interfere with download of SES 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 "/etc/init.d/ssagent stop" as root on any system
    where the SUNWscsa package is installed.  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 which monitors the status of the
    enclosure, may also interfere with controller or SES 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.
 
10. Invoke sccli again.  At the "sccli>" prompt, type the following command:
 
       download ses-firmware sesfw_sunsata_0412.s3r
 
    sccli performs a "live upgrade" of the SES firmware and it is not
    necessary to restart the RAID controller afterwards; however, until
    the next controller reset, the firmware's telnet/RS232 menu
    interface may continue to display the old SES firmware revision.
 
11. Run the sccli "show ses" command again to verify that all SES
    devices have been upgraded to version 0412, as indicated by the
    "Rev" column.  In the example below, the Rev column has changed to
    "0412" for both SES devices:
 
      sccli> show ses
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWPN             ...
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3511F A 0412 1000 204000C0FF000187 ...
                                                             Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0412 1000 204000C0FF000187 ...
                                                             Topology: ...
 
    Note: While it is not necessary to reset the RAID controller after
    an SES firmware upgrade, the RAID controller's telnet/RS232 menu
    interface may continue to display the old SES revision number until
    after the next time it is reset.
 
PLD Firmware Upgrade:
---------------------
 
If you are using PLD firmware revision 1000, then no PLD firmware 
update is necessary and you should proceed to step 18.
 
    Warning: Performing this PLD firmware upgrade incorrectly, by using
    a version of sccli prior to version 1.6.1 or power-cycling the array
    at the wrong time, could result in the array enclosure being
    rendered unusable.
 
    Upgrading the PLD firmware causes the host's Fibre Channel HBAs to
    be disconnected from the array temporarily, which may prevent
    sccli from completing the procedure properly if sccli is not used
    out-of-band.  sccli must be invoked with the hostname or IP address
    assigned to the array, so that a network connection is used to
    communicate with the array controller (see Step 2).
 
    The PLD firmware upgrade cannot be completed without power-cycling
    the array at the end of the procedure.  Do not proceed if it is not
    possible to power cycle the array at this time.
 
12. Verify the PLD firmware revision by issuing the sccli "show ses"
    command:
 
      sccli> show ses
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWPN             ...
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3511F A 0412 1000 204000C0FF000187 ...
                                                             Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0412 1000 204000C0FF000187 ...
                                                             Topology: ...
 
13. Examine the PLD firmware revision codes displayed in the "PLD"
    column.  If all of the lines contain a revision code of 1000 in the
    PLD column, then no PLD firmware update is necessary and you should
    proceed to step 18.
 
14. Make sure that all host I/O activity has been stopped.  The array
    will be unable to process host I/O activity for up to 10 minutes.
 
15. Type the following command at the "sccli>" prompt:
 
         download pld-firmware sata1000.s3r
 
    sccli will indicate that it is shutting down the controller,
    sending the PLD firmware data, and programming the flash memory.
    All the LEDs on the array will illuminate while the flash
    programming is under way, and sccli will pause for 3 to 5 minutes.
 
    DO NOT POWER CYCLE THE ARRAY YET.  Note the time and wait at least 5
    minutes for the PLD flash programming operation to complete.
 
16. After waiting at least 5 minutes after seeing the message "Please
    wait about 3 minutes until you are notified to power cycle", turn
    off power to the array, wait 10 seconds, and then turn power back
    on.  Be sure to turn off, or unplug, BOTH power supplies, as
    removing power from one power supply does not cause the array to
    lose power.  Allow up to 3 minutes for the controller to restart
    fully.
 
17. Restart sccli and run the "show ses" command again to verify that
    the PLD firmware revision displayed in the PLD column is 1000 for
    all SES devices shown, as in the example below:
 
      sccli> show ses
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWPN             ...
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3511F A 0412 1000 204000C0FF000187 ...
                                                           Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0412 1000 204000C0FF000187 ...
                                                           Topology: ...
 
Router Firmware Upgrade:
-----------------------
 
If you are using router firmware revision DP0555a, then no router firmware 
update is necessary and you should proceed to step 23.
 
18. Verify the router firmware revision by issuing the sccli "show sata-
    router" command:
 
        sccli> show sata-router
        Encl-ID Encl-SN Ch Slot  Rev      Boot-rev CSB  HW-rev ST-rev
        -------------------------------------------------------------
        0       07EE85  2  upper DP0554e  0548     0500 11     0552
        0       07EE85  3  lower DP0554e  0548     0500 11     0552
 
19. Examine the firmware revision code displayed in the "Rev" column.
    In this case, both the upper and lower SATA routers contain DP0554e
    firmware, so and update is necessary.  If all of the lines contain a
    revision code of DP0555a in the Rev column, then no firmware update
    is necessary and you should proceed to step 23.
 
20. Type the following command at the "sccli>" prompt:
 
         download sata-router-firmware FW_DP0555a.dlf
 
21. If you do not have a redundant configuration or in a 
    single-controller environment, sccli prompts you to continue. If you 
    specify Y at the prompt, sccli shuts down the controller, performs the
    download, and then resets the controller. When the controller shuts down,
    the host is prevented from performing I/O for several minutes.
 
22. Run the sccli "show sata-router" command again to verify that all
    devices have been upgraded to version DP0555a, as indicated by the
    "Rev" column.  In the example below, the Rev column has changed to
    "DP0555a" for both routers:
 
      sccli> show sata-router
        Encl-ID Encl-SN Ch Slot  Rev      Boot-rev CSB  HW-rev ST-rev
        -------------------------------------------------------------
        0       07EE85  2  upper DP0555a  0548     0500 11     0552
        0       07EE85  3  lower DP0555a  0548     0500 11     0552
 
MUX Firmware Upgrade:
---------------------
 
If you are using MUX firmware revision BB42, then no MUX firmware 
update is necessary and you should proceed to step 28.
 
23. Verify the MUX firmware revision by issuing the sccli "show sata-
    mux" command:
 
        sccli> show sata-mux
        24 mux boards found
 
        Ch Id  Mux-SN Mux-Type PC150/Rev PC150/Boot
        -------------------------------------------
         2   0 00075D A/A      BB42      0300
         2   1 00075E A/A      BB42      0300
         2   2 00075F A/A      BB42      0300
         2   3 000760 A/A      BB42      0300
         2   4 000761 A/A      BB42      0300
         2   5 000762 A/A      BB42      0300
         2   6 000763 A/A      BB42      0300
         2   7 000764 A/A      BB42      0300
         2   8 000765 A/A      BB42      0300
         2   9 000869 A/A      BB42      0300
         2  10 000767 A/A      BB42      0300
         2  11 000768 A/A      BB42      0300
         2  16 000C9D A/A      BB42      0300
         2  17 000C9E A/A      BB42      0300
         2  18 000C9F A/A      BB42      0300
         2  19 000CA0 A/A      BB42      0300
         2  20 000CA1 A/A      BB42      0300
         2  21 000CA2 A/A      BB42      0300
         2  22 000CA3 A/A      BB42      0300
         2  23 000CA4 A/A      BB42      0300
         2  24 000CA5 A/A      BB42      0300
         2  25 000CA6 A/A      BB42      0300
         2  26 000CA7 A/A      BB42      0300
         2  27 000CA8 A/A      BB42      0300
 
 
24. Examine the firmware revision code displayed in the "PC150/Rev"
    column.  If all of the lines contain a revision code of BB42 in the
    PC150/Rev column, then no firmware update is necessary and you should
    proceed to step 28.
 
25. Type the following command at the "sccli>" prompt:
 
         download sata-path-controller-firmware PC_BB42.dat
 
26. If you do not have a redundant configuration or in a 
    single-controller environment, sccli prompts you to continue. If you 
    specify Y at the prompt, sccli shuts down the controller, performs the
    download, and then resets the controller. When the controller shuts down,
    the host is prevented from performing I/O for several minutes.
 
27. Run the sccli "show sata-mux" command again to verify that all
    devices have been upgraded to version BB42, as indicated by the
    "PC150/Rev" column.  
 
After Upgrading:
----------------
 
28. If the SSCS agent was stopped in step 9, 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.
 
    If other storage management software such as StorADE was stopped,
    restart it following the procedures in the documentation for that
    software.

README -- Last modified date:  Wednesday, April 20, 2005

