OBSOLETE Patch-ID# 113724-08

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 3511 se3511 se3000 raid storage firmware ses pld
Synopsis: Obsoleted by: 113724-09 SE3511 413C: StorEdge 3511 array firmware upgrade
Date: Jan/13/2006


Install Requirements: NA                      
                      
Solaris Release: 8 9 10

SunOS Release: 5.8 5.9 5.10

Unbundled Product: StorEdge 3511 Array Controller Firmware

Unbundled Release: 1.0

Xref: 

Topic: 

Relevant Architectures: sparc x86
NOTE: 
If you are using 3.27R or earlier controller firmware and do not want to
upgrade to version 4.13, you can download the most recent 3.27R firmware 
patch, 113724-03, from sunsolve.sun.com.
NOTE:
When upgrading from 3.xx to 4.1x on Solaris, Windows, or Linux, you must 
use the upgrade script for 3.xx to 4.xx upgrades. Other platforms require 
the manual upgrade procedure contained in this README file.
*  See the quick_upgrade.pdf file contained in this patch. It is for 
   experienced Sun customers who can use the upgrade script and 
   minimum instructions.  
*  See the script_troubleshooting.pdf file contained in this patch for 
   script troubleshooting information. 
*  For a minor upgrade, see "Upgrading Controller Firmware (4.xx to 4.xx)" 
   in this README file.


BugId's fixed with this patch: 4702532 4714811 4715089 4726561 4743721 4782928 4797299 4806105 4812759 4819218 4819226 4824129 4825806 4847479 4860776 4866684 4876281 4876284 4881105 4881136 4881138 4881139 4888526 4900452 4911841 4937092 4938844 4944252 4950297 4967518 4971693 4988102 4995551 5007650 5013417 5014422 5016303 5022022 5026029 5026182 5034782 5038581 5039653 5045633 5047709 5051226 5054672 5056389 5057239 5059398 5069625 5070627 5072698 5082717 5090335 5091255 5091272 5091334 5091492 5092116 5092128 5092130 5092132 5092135 5094340 5094897 5104938 6179058 6180938 6194855 6194880 6194926 6194975 6202496 6232352 6235263 6241794 6255677 6257852 6274609 6276668 6286138 6304482 6324010

Changes incorporated in this version: 4797299 4819226 4824129 4967518 6232352 6255677 6257852 6274609 6276668 6304482 6324010

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_DP0569a.dlf          # SATA Router firmware rev DP0569a 
PC_BB42.dat             # SATA MUX firmware rev BB42
README.113724-08
SUN413C-3511.bin        # SE3511 Array Controller Firmware rev 413C
patchinfo
quick_upgrade.pdf       # Flowchart procedures for experienced Sun customers
sata1100.s3r            # SE3511 Enclosure PLD Firmware rev 1100
script_troubleshooting.pdf # Troubleshooting information for upgrade script
sesfw_3511_0420.s3r     # SE3511 Enclosure SES Firmware rev 0420

NOTE:
Topics Included in this file:
* Problem Description
* Upgrading Controller Firmware (4.xx to 4.xx)
* Patch Installation Instructions (3.xx to 4.xx)
* Prerequisites for Upgrading Firmware (3.xx to 4.xx)
* To Install or Upgrade Software on Solaris Operating Systems
* To Invoke Sun StorEdge CLI
* Preparing to Upgrade Controller Firmware (3.xx to 4.xx)
* s3kdlres Upgrade Script for 3.xx to 4.xx Only
* Upgrading the Controller Firmware with a Script (3.xx to 4.xx)
* Upgrading the Controller Firmware Manually (3.xx to 4.xx)
* SES Firmware Upgrade
* PLD Firmware Upgrade
* Router Firmware Upgrade
* MUX Firmware Upgrade
* After Upgrading
* Mixed 3510 and 3511 Upgrades
* Special Install Instructions
====================

Problem Description:

--------------------
 
This patch contains all five types of firmware updates for the StorEdge 3511
array subsystem: 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 SR-1216 
router, which provides port routing in the SATA unit; and the SATA MUX, 
which controls the path microcode on the multiplexer (MUX) boards behind
the SATA router.
 
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: 413C
         SES firmware:        0420
         PLD firmware:        1100
         Router firmware:     DP0569a 
         MUX firmware:        BB42
 
This patch contains firmware which is installed on the StorEdge 3511
array using Sun StorEdge CLI, rather than using installpatch or patchadd.
 
 
Router firmware DP0569a addresses the following issue:
 
6324010 Download of SATA-MUX and SATA-Router code fails with timeouts
 
 
RAID firmware 413C addresses the following issues:
 
4797299 Need data checking facility
4819226 Should have percentage complete for adding drives to an LD
4824129 Request for enhancement of messages on controller FW
4967518 Firmware doesn't track drive failure and the drive can scan back ok.
6232352 serial interface goes into different menu than expected
6255677 the media scan does not start back up on the rebuilt drive
6257852 LD_RESCUE support removed from SE3000 family without notification
6274609 SE3510 with Firmware 4.11I has dirty cache that cannot be destaged to disk
6276668 SE3510 F/W 4.11I in cluster config panic with "Unrecoverable Controller Error Encountered !"
6304482 Over Voltage Critical error is displayed when one p/s is turned off
 
SES firmware 0420 addresses the following issue:
 
6286138 Primary & secondary RAID controller batteries fault after 4.11 upgrade
 
(from 113724-04)
 
RAID firmware 411I addresses the following issues:
 
4702532 write cache not automatically disabled when battery is off line
4714811 Partition/Offset/Size screen should have more information
4715089 Out of band error msgs are not persistant across power cycles
4726561 Aborting Parity Check results in "Parity Regeneration Failed" message
4743721 SSCS: no method for identifying disk drives
4782928 Request that SCCLI 'show events' command can use a time argument
4806105 FW 3.25O enhancement to allow multiple simultaneous rebuilds
4812759 Add status information in sccli 'show FRUs' and 'show config' commands
4819218 differences between firmware and sccli events
4825806 BBU warnings should not be as severe
4847479 sccli> show inquiry-data does not show correct Firmware Revision
4860776 create user configurable function to add timeout/disconnect on telnet session
4866684 open tcp/ip ports
4876281 sccli: Add support to view current voltage of 3510 +3.3v, +5v, and +12v.
4876284 sccli: Add support to view current Temperature of 3510 - CPU Board1 and Board2.
4881105 Ability to set Date, Time, and TZ through the External Interface
4881136 Periodic cache flushing feature with user-selectable flush interval
4881138 Write-back caching option with accelerated posting of writes
4881139 Logical drive expansion for RAID 1 logical drives
4888526 Temperature events should contain the sensor number
4900452 Network connectivity through default gateway is unreliable
4911841 SE3510 - unable to send SNMP traps using 'agent.ini' file, as documented
4937092 The SCCLI/GUI does'nt allow us to set scsi-io-timeout > 10
4938844 Repartitoning a logical disk can cause all data on the logical disk to ve lost
4944252 After a disk failure, the drive is no longer displayed by sccli.
4950297 Parity checks run from the GUI always enables auto correction of parity
4971693 controller reset request popup not happeneing when changing scsi timeout value
4988102 Port scanning/security software cause the SE3310 to hang
4995551 Serialnumbers in eventlog are inconsistent or missing
5007650 Controller offlines disk drive with an "Unexpected Sense Received" event
5013417 sccli doesn't accept the controller passwd in out-band connection
5014422 sccli show FRUs return inconsistant result intermittently
5016303 sccli should show removed FRUs  with status "missing"
5022022 DRAM parity errors/SDRAM ECC errors can cause data corruption
5026029 Firmware upgrade/downgrade shown as controller failure detected from sccli.
5026182 Firmware upgrade/downgrade displayes incorrect times stamp via sccli show events
5038581 FI: Fan failure recovery displays different error code for telnet and sccli.
5039653 both controller get hung with sccli show lun-maps
5047709 Reserve Bit Test failed on SE3511
5051226 sscli: show config -x frequently misses FC_JBOD_IOM
5054672 Assignment of Slot ids for Drives does not work properly.
5056389 Temperature sensors go off and bring down controller
5057239 Controller replacement caused drives to fail.
5059398 Data Corruption during IO, with LD rebuild and multiple fault condition
5069625 Cache optimization mode can be incorrectly changed causing Data Integrity issue
5090335 show partitions is not correct
5091255 sccli incorrect error message from check parity when attempting to run multiples
5091334 Restore Factory defaults - completes with error
5091492 unmap partition partition does not work as documented 5092130 sccli 1.6.2 allows 
local spares to be assigned to RAID 0 Logical Drives
5092116 Ability to combine SATA and FC Logical drives in a Logical Volume
5092128 Perpetual clone allows FC to SATA and SATA to FC drive cloning operation
5092132 quick installation allows the mixing of SATA and FC drives in a LD
5092135 All global-spares assigned show up under each individual logical drive
5094340 SSCS - Requires  controller reset when changing baud rate
5094897 ld rebuild only gets to 99%
5104938 The word "replace" is mis-spelled in the abort copy and replace confirmation.
6180938 Verify a media scan is continuosly running on each LD after time of creation.
6194855 Remove duplicate "it" from shutdown controller message text 
6194880 Cache optimization is changable without reset
6194926 "delete LV" inband command fails
6194975 when changing the assignment of a logical volume it asks for reset, but it's not needed
6235263 The released documentation for adding expansion units to 3511 raid is inaccurate.
6241794 3511 enclosure ignores most significant byte of allocation length on Receive Diagnostic Results
 
The 113724.04 README file addresses:
6202496 Synopsis: Incorrect information in patch README
 
(from 113724-03)
 
SES firmware 0413 addresses the following issues:
 
5034782 SCCLI: SES is displayed as software bypassed but unbypass command is not working
5045633 3511 does not support the same level as diagnostics available in 3510
 
(from 113724-01)
 
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:
============================================

Upgrading Controller Firmware (4.xx to 4.xx)

--------------------------------------------

The following procedure is used for a minor upgrade, such as from 4.11 to 
4.13. 

 1. 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, 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 are running sccli version 2.1 or later with the 
    "version" command.

 2. Verify the Product and Revision of the array.  Type the command

        show inquiry

    and examine the output.  If the "Product" is "StorEdge 3511F D" and 
    "Device Type: Enclosure" appears, the device is a JBOD chassis and has
    no controller firmware; proceed to the "SES Firmware Upgrade" 
    section.    

    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 413C or later, the RAID controller 
    firmware does not need to be upgraded. If it is reported as 
    "3511 411I vX.XX" or 411<x>, continue with step 3.

 3. 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"(dual-controller), 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 4 and follow  
    the instructions for upgrading a single-controller configuration.

    If you have a dual-controller configuration running firmware 411I or 
    later, 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 SUN413C-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, 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 a live firmware 
    upgrade. Wait until it is okay to stop I/O to the array, and then 
    follow the instructions in step 4 to do a non-live firmware upgrade.

    If no error messages were displayed, proceed with step 5.

 4. Single-controller configurations, dual-controller configurations
    which are in degraded status, or controllers running firmware 
    earlier than 4.11I 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 SUN413C-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 
    again, which may take 10 minutes or more, before proceeding.
 
 5. 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 "413C".


===============================================

Patch Installation Instructions (3.xx to 4.xx):

-----------------------------------------------

When upgrading from 3.xx to 4.13, you must have a serial connection to
restore settings when the controller firmware upgrade completes, and the
serial connection must be set to 38400.

When upgrading from 3.xx to 4.13 on Solaris, Windows, or Linux, you 
must use the upgrade script. Other platforms require the "Configuring 
the Controller Firmware Manually" instructions contained in this 
README file. 

For experienced Sun customers who can use the upgrade script and 
minimum instructions, use the quick_upgrade.pdf file contained 
in this patch. 

Refer to the script_troubleshooting.pdf file provided in this 
patch if error messages occur when running the upgrade script. 
 

-----------------------------------------------

Prerequisites for Upgrading Firmware (3.xx to 4.xx):
 
-----------------------------------------------

Before installing controller firmware version 4.13, make sure your 
environment can support the prerequisites for installing the new 
firmware including:

 * Version 2.1 software required
 
        Version 2.1 of the "sccli" CLI utility included in the SUNWsscs
        package, which may be installed from the Sun StorEdge Professional
        Storage Manager CD or downloaded from the Sun Download Center.  
 
        If you do not have this package installed, or if you have an 
        earlier version, see "To Install or Upgrade Software on Solaris 
        Operating Systems" later in this document.

 * Upgrade script required (Solaris, Microsoft Windows, Linux)

        The version 2.1 software provides the upgrade script for
        software installations on Solaris, Microsoft Windows and Linux.   
        
        You must use the s3kdlres script to perform the controller firmware
        upgrade if you have the 2.1 software installed on Solaris, Microsoft 
        Windows, or Linux systems. This greatly reduces the probability of 
        error and saves time. 

 *  Manual upgrade procedure required for HP-UX and IBM AIX systems 

        If you have the 2.1 software installed on HP-UX or IBM AIX systems, 
        you must use the procedure provided in "Upgrading Controller Firmware 
        Manually" in this README file. 

        -----
        Note:
        ----
        The manual procedure works on all systems but should not be used
        on systems which have the upgrade script. 

 * The controller firmware script restores the following configuration
   settings:
 
    *   controller-name 
 
    *   controller-id 
 
    *   Logical Drive controller assignment (Primary/Secondary) 
 
    *   host-wwn-name 
 
    *   cache-parameters: write-back, write-through, random, 
        sequential 
 
    *   disk-array: normal-verify, rebuild-verify, init-verify, 
        rebuild-priority 
 
    *   drive-parameters: spin-up, disk-access-delay, 
        scsi-io-timeout, queue-depth, polling-interval, 
        enclosure-polling-interval, auto-detect-swap-interval, 
        smart, auto-global-spare 
 
    *   host-parameters: queue-depth, max-luns-per-id, 
        fibre-connection-mode 
 
    *   channels - This option restores the channel type, 
        (disk or host), and target IDs. 
 
    *   maps - This option restores the LUN mappings. 
 
    All other settings will be set to the 4.13 default settings.
 
 * Ethernet connections required for out-of-band firmware upgrades
 
        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.
 
 * You must stop all I/O to the array before beginning the controller 
   firmware upgrade.
 
 * Unmount all StorEdge 3511 logical drives/LUNs from any Solaris hosts 
   connected to the array, for the duration of the install procedure.  
 
        For example, filesystems mounted from the Sun StorEdge 
        3511 should be unmounted, and databases accessing raw devices on 
        the array should be shut down.
 
 * Do not exceed 32 partitions per logical drive. 
 
        If your configuration has more than 32 partitions per logical drive, 
        you must back up the data on the affected logical drives, 
        reconfigure the partitions per logical drive to less than 32, 
        redistribute the data across the logical drives, and then upgrade 
        the firmware.
 
 * You must reconfigure controller and network parameters after
   upgrading the controller firmware. 
 
        For example, the controller password is not restored if you perform
        a manual upgrade or an inband upgrade using the script. The password 
        is set to null when the upgrade completes. The controller password is
        restored if you perform an out-of-band upgrade using the script. 
 
 * You must have a serial connection to restore the IP address, netmask, and 
   default gateway settings for your array when the upgrade completes. The
   serial connection must be set to 38400. 
 
        Note the IP address, netmask, and default gateway settings for your 
        array before you begin the upgrade.
 
 * Using the RS-232 interface, note the filter map and sector/head/cylinder
   parameters, and record these settings. 
 
      The RS-232 serial interface allows additional filter map and 
      sector/head/cylinder parameters beyond what sccli allows. After the 
      firmware is upgraded, there is no way to recover this information. 
      For details, see step 6 in "Preparing to Upgrade Controller Firmware."
 
 * If you will be using the script to perform the upgrade:
 
   * You must currently have controller firmware version 3.27R or later.
 
   * If performing an in-band upgrade using the script, the controller 
     password is set to null when the upgrade completes. Be sure to 
     specify a more secure controller password. 
 
 * Be aware that 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.
 
 * Due to important data integrity improvements in this release, the 
   performance for RAID1 has been impacted. Random write operations are 
   impacted the most -- performance is reduced by 10-20%. 
 
 * Stop any Sun StorEdge Configuration Service (SSCS) agent that may be 
   running on a host connected to the array controller. 
 
      The SSCS agent may interfere with the download of SES code and the
      script upgrade process.  To stop the SSCS agent, issue the shell 
      command "/etc/init.d/ssagent stop" as root on any system where 
      the SUNWsscs 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.
 
 * Stop the StorADE agent software, or any other software that monitors the 
   array, following the procedures described in the documentation for that 
   application.
 
      StorADE, or any other application which monitors the status of the
      enclosure, may also interfere with controller or SES firmware
      downloads and the controller firmware script upgrade.
 
 * Unpack the patch into any convenient directory (for example, /var/tmp).
 
============================================================
 
To Install or Upgrade Software on Solaris Operating Systems:
 
------------------------------------------------------------ 
 
For installation or upgrading instructions for other operating systems,
refer to "Sun StorEdge 3000 Family Software Installation Guide," which 
is available from:
 
       http://docs.sun.com/app/docs/coll/3511FCarray
 
  1. Go to http://www.sun.com/software/download/index.jsp and click
     the "Storage Management" link under the "Systems Administration"
     heading.
 
  2. Click the link for "StorEdge 3000 Family Storage 
     Products--Related Software".
 
  3. Log in or register as necessary.
 
  4. Download and install the appropriate software files. If you are 
     upgrading, uninstall all earlier versions of Sun StorEdge 
     Configuration Service, Sun StorEdge Diagnostic Reporter, and 
     Sun StorEdge CLI, including the agents. 
 
  5. To uninstall earlier versions of the software, type:
 
         # pkgrm filename
 
    where filename for version 2.x is SUNWsscs

    and filename for version 1.x is:
 
        SUNWscsd      Configuration Service Agent
        SUNWscsu      Configuration Service Console
        SUNWscsa      Diagnostic Reporter Agent
        SUNWscui      Diagnostic Reporter Config Tool
        SUNWsccli     CLI
 
  6. To install the version 2.1 software package, type:
 
         # pkgadd -d . SUNWsscs
 
     The Solaris installation package, SUNWsscs, includes the 
     following components:
           Sun StorEdge Configuration Service agent
           Sun StorEdge Configuration Service console
           Sun StorEdge Diagnostic Reporter agent (daemon)
           Sun StorEdge Diagnostic Reporter Config Tool (UI)
           Sun StorEdge CLI
 
  7. Provide appropriate responses to each of the installation prompts.
 
  8. After the package is installed, a message is displayed, indicating it
     was installed successfully. 
 
     The Sun StorEdge Configuration Service components are installed in the
     following directories:
 
      /opt/SUNWsscs/ssagent
      /opt/SUNWsscs/sscsconsole
 
     The Sun StorEdge Diagnostic Reporter components are installed in the 
     following directories: 
 
      /opt/SUNWsscs/ssdiagreporterd
      /opt/SUNWsscs/ssdiagreporterui
 
     The CLI is installed in /opt/SUNWsscs/sbin/sccli.
 
  9. Verify that the correct CLI version is installed by typing:
 
      /opt/SUNWsscs/sbin/sccli version
 
===========================
 
To Invoke Sun StorEdge CLI:
 
---------------------------
 
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 expansion chassis (JBOD), 
invoke sccli with the name of an SES device:
 
        sccli /dev/es/ses<n>
 
If the array to be upgraded is a RAID subsystem attached to a Fibre Channel
HBA installed in the local host, 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 | 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.  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.   
 
 
========================================================
 
Preparing to Upgrade Controller Firmware (3.xx to 4.xx):
 
--------------------------------------------------------
 
If you are using controller firmware version 4.13C, then no firmware 
upgrade is necessary and you should proceed to "SES Firmware Upgrade."
 
 1. Back up all data.
 
     -------
     Caution:
     -------
     To ensure that the existing array is restored using the currently 
     configured settings, back up all data and configuration parameters
     so you can reference them after the upgrade.
 
     The script upgrade procedure does not restore the following settings.
 
     * Network settings - IP address, net mask, and gateway settings
 
     * Baud rate for the serial port
 
     * Host LUN filter settings - type, access mode, and name

     * Sector/head/cylinder settings
 
     * Channel data rate - If the channel data rate was set to 1 GHz
     or 2 GHz, after the script is run, the channel speed is set to 
     auto (auto-negotiation). Since a FC channel communicates at a 
     rate of either 1 GHz or 2 GHz, the Auto setting uses the best
     rate for communications at the time.
 
     * Non-default RCCOM settings - RCCOM channel settings are recovered 
     for Channels 2 and 3 only.  RCCOM settings for other channels are not
     recovered.  You must record and set this information with the RS-232 
     interface. 
 
     * Certain customized settings - Use the configuration file created
     in step 5 to verify that all parameters have been restored.
 
     See step 5 for details on saving configuration parameters.

     See step 6 for details on recording sector/head/cylinder settings, 
     RCCOM settings, and host filter parameters.
 
 2. Change your working directory to the directory in which the patch
    was unpacked and confirm that the SUN413C-3511.bin file is present
    using the "ls" command.
 
 3. Invoke sccli and verify that you are running sccli version 2.1 with 
    the "version" command.
 
 4. 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 413C, the RAID controller firmware 
    does not need to be upgraded; proceed to "SES Firmware Upgrade."
 
 5. Save the array configuration settings in .txt and .xml formats. These
    files can be referred to later in case it is necessary to restore or 
    troubleshoot the configuration settings.  
 
    -----
    Note:
    -----
    Configuration setting output files are not transferable. You cannot 
    save a configuration for a specific device and use it to perform the
    script upgrade on another device. 
 
    At the "sccli>" command prompt, type:
 
        show configuration filename.txt
 
    and then type:
 
        show configuration --xml filename.xml
 
    These commands may take several minutes to complete.  
 
 6. Use the RS-232 interface, to view host LUN filter parameters,
    sector/head/cylinder parameters, and RCCOM settings. Record 
    these settings. 
 
    After nvram is reset, there is no way to recover this information. 
    The RS-232 serial interface allows additional parameters 
    beyond what sccli allows. These include read-write/read-only, 
    exclude/include, filter masks, and RCCOM settings. sccli does not 
    provide a way to check or record these parameters. 
 
    Record sector/head/cylinder settings by using the RS-232 
    connection and choosing "view and edit Configuration parameters > 
    Host-side Parameters > Host Cylinder/Head/Sector Mapping Configuration"  
    from the Main Menu. 
 
    Use the "view and edit Host luns" command from the Main Menu to view
    host filter parameters. 
 
    Record RCCOM settings by using the RS-232 connection and choosing
    "view and edit channels" from the Main Menu. 
 
    -----
    Note:
    -----
    The 4.13 firmware automatically allows LDs over 253 GB to be seen by 
    Solaris. After upgrading to 4.13 the sector/head/cylinder values will 
    be set to default values and Solaris will see the proper LD size. 
    However, if you have modified the sector/head/cylinder parameters in 
    3.2x firmware,  after upgrading to 4.13 firmware you should change those 
    parameters back to the values you had set in 3.2x; this is in case a 
    relabel on Solaris is performed at a later date.

 7.  Check that the array is healthy by running the CLI "show redundancy" 
     command. The dual-controller array is healthy if the Redundancy mode 
     is "Active-Active" and the status is "Enabled." The single-controller
     array is healthy if the Redundancy mode is "Active-Active" and the 
     status is "Scanning."
 
 8. Perform this step only if you are upgrading the controller firmware
    using the upgrade script. This step is not necessary for the manual
    upgrade.
 
    If channels 4 and 5 are used as drive channels, you must use the default
    PID/SID IDs of 14 and 15. Similarly, you must use PID/SID IDs of 14 and
    15 for channels 2 and 3. Check your drive channel IDs and perform the 
    following steps. Always set the primary controller ID (PID) before you 
    set the secondary controller ID (SID). 
 
    a. Check all channel ID settings with: 
 
       sccli <device> show channels 
 
    b. Set PID/SID IDs to 14 and 15 where needed. Example commands: 
       sccli <device> configure channel 4 Drive pid 14 
       sccli <device> configure channel 4 Drive sid 15 
       sccli <device> configure channel 5 Drive pid 14 
       sccli <device> configure channel 5 Drive sid 15 
 
    c. Reset controller: 
 
       sccli <device> reset controller 
 
    d. Confirm that the IDs have the correct settings: 
 
       sccli <device> show channels 

=============================================
 
s3kdlres Upgrade Script for 3.xx to 4.xx Only
 
---------------------------------------------
 
This s3kdlres script automates the upgrade process from the 3XX code base 
to the 4XX code base. This script saves the controller configuration in XML 
format, upgrades the firmware, resets nvram, and restores the configuration 
with sccli commands based on the XML file. 

    --------
    Caution:
    -------
    DO NOT use the upgrade script if you are performing a minor upgrade, 
    such as 4.11 to 4.13. It must be used only for 3.xx to 4.xx upgrades.  

    ----
    Note: 
    ----
    See the script_troubleshooting.pdf file contained in this patch for 
    script troubleshooting information. 

The upgrade script is provided in the SSCS/CLI 2.1 software package on the 
Sun Download Center or on your Sun StorEdge 3000 Family Professional Manager 
CD. 

    ----
    Note: 
    ----
    It is not possible to recover all configuration information with 
    sccli and the XML configuration file. See the LIMITATIONS section in the 
    s3kdlres man page for details. Before running this script it is 
    recommended that you use sccli to save nvram to the local file system, 
    and save the output from "show configuration" for later reference if 
    necessary.

To reference the s3kdlres man page on Solaris systems type:
 
    man -M /opt/SUNWsscs/man s3kdlres
 
To reference the s3kdlres man page on Linux systems type:
 
    man 1m -M /opt/SUNWsscs/man s3kdlres 

 
=============================================================
 
Upgrading the Controller Firmware with a Script (3.xx to 4.xx):
 
--------------------------------------------------------------

The upgrade script works with Solaris, Microsoft Windows, and Linux 
operating systems only. You must use the upgrade script to upgrade 
from 3.xx to 4.13 when the 2.1 software is installed on these systems. 

   -------
   Caution:
   -------
   Review all procedures and release notes for this major upgrade
   prior to upgrading your array. Downgrading back to the 3.27 
   controller firmware is recommended only for a FRU replacement
   module. All other downgrades risk loss of all data. 
 
   -----
   Note:
   -----
   If you will be upgrading more than one array, take note of the 
   of time it takes to upgrade the first array. Then, you can 
   allot the appropriate amount of time it will take to upgrade
   your other arrays.
 
   -----
   Note:
   -----

   IBM AIX and HP-UX operating systems must use the manual upgrade 
   procedure.

   -----
   Note:
   -----
   Using the script to perform the upgrade saves time. For example, a 
   simple upgrade was completed by an experienced user in 25 minutes 
   using the script. Using the manual procedure took the same user 
   almost 60 minutes to upgrade the same data. 
 
   -------
   Caution:
   -------
   Before you begin the upgrade, read the "Prerequisites for Upgrading
   Firmware" section.
 
 1. If you have not already done so, do the following:
 
       a. Stop all I/O to the array.
 
       b. Unmount all hosts connected to the array.
 
       c. Stop any Sun StorEdge Configuration Service (SSCS) agent that 
          may be running on a host connected to the array controller. 
 
       d. Stop the StorADE agent software, or any other software that 
          monitors the array,
 
    Reference the "Prerequisites for Upgrading Firmware" section
    for more information on the preceding items.
 
 2. For the controller firmware upgrade, you must use the serial port
    interface to restore the IP address and network settings and to 
    monitor the progress of the upgrade. 
 
    Use a null modem serial cable to connect the COM port of the RAID
    array to the serial port on a host workstation. 
 
    Set the serial port parameters on the workstation to 38,400 baud, 
    8 bit, 1 stop bit, no parity. 
 
 3. Prepare to monitor the progress of the installation by using the 
    serial connection.
        -----
        Note:
        -----
        If an upgrade fails resulting in an indeterminate or incomplete 
        status, contact an authorized Sun Service person immediately. Or,
        reference the "Troubleshooting the Script Upgrade" section later
        in this document.
 
 4. To use the s3kdlres script to update the controller firmware, perform 
    the following steps.
 
  a. (Solaris and Linux only) To run the s3kdlres script to update the 
     controller firmware, change your directory to /opt/SUNWsscs/sbin 
     and type:
  
     ./s3kdlres <XML Filename> --device=<device or IP> --password=
          <Controller Password>
  
     XML filename is the name of the file where the array 
     configuration output will be saved.
  
     Device or IP is the device name or IP address of the array.
  
     Password is the controller password, if there is one. If no
     password is set, do not specify the password option.
  
     The following example runs the script and updates the firmware on 
     the specified device, which does not have a password assigned:
  
     # ./s3kdlres /var/tmp/xml_conf.out --device=206.111.111.111 
  
     The executable script is located in: 
  
     /opt/SUNWsscs/sbin
  
     For detailed instructions about the script, see the 
     "s3kdlres Script Man Page" section below.
  
  b. (Microsoft Windows only) To run the s3kdlres script to update 
     the controller firmware, choose Start > Run and type cmd to 
     launch a command-line prompt. Change to the directory 
     containing the s3kdlres script:
  
     C:\Program Files\Sun\sccli
  
     If you installed the software in a location other than the 
     default location listed above, specify that location rather
     than what is listed above.
  
     And then type:
  
     s3kdlres <XML Filename> --device=<device or IP> --password=
          <Controller Password>
  
     XML filename is the name of the file where the array 
     configuration output will be saved.
  
     Device or IP is the device name or IP address of the array.
  
     Password is the controller password, if there is one. If no
     password is set, do not specify the password option.
  
     The following example runs the script and updates the firmware on 
     the specified device, which does not have a password assigned:
  
     # s3kdlres xml_conf.out --device=206.111.111.111 
  
     For detailed instructions about the script on Microsoft Windows 
     systems, double-click the help file, s3kdlres.txt, located in:
  
     C:\Program Files\Sun\sccli
  
  c. When the script prompts you for the firmware file, specify the 
     path where the firmware patch was extracted and the firmware 
     file name, SUN413C-3511.bin. 
  
     For example, in Solaris, if you extract the firmware file to
     the default location, type:
  
     /var/tmp/SUN413C-3511.bin
  
     For example, in Microsoft Windows, if you extract the firmware
     patch to C:\Program Files\Sun\sccli, type:
 
     113724-08\SUN413C-3511.bin
  
 d.  If you encounter an error or exception, refer to the 
     script_troubleshooting.pdf provided in this patch.
 
     -----
     Note:
     -----
     If you have logical drives on the secondary controller on
     channels 4 or 5, the upgrade script stops before the LUN mapping  
     is restored, and an error is displayed. No LUNs will be remapped.
     You must change the logical drive assignments from primary to 
     secondary controller through the RS-232 firmware connection. 
     For details, reference the "Troubleshooting the Script Upgrade" 
     section later in this document.
  
  e. When prompted, restore the IP address, netmask, and gateway using the
     serial interface. If you are using in-band communication, restore 
     channel settings (ID), LUN mapping, and inter-controller links for 
     the same device used during the firmware upgrade.
  
  f. When prompted, type yes to complete the installation.
 
 5. 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 "413C".
 
 6. Reference the 3.27 configuration .xml or .txt file or the RS-232 
    settings recorded in steps 5 and 6 of "Preparing to Upgrade Controller 
    Firmware" to restore any settings that were not reset. 
 
    The upgrade does not restore:
 
    * Network settings - IP address, net mask, and gateway settings
 
    * Baud rate for the serial port
 
    * Host LUN filter settings - type, access mode, and name (See the 
      following step for instructions of restoring these settings.)

    * Sector/head/cylinder settings
 
    * Channel data rate - If the channel data rate was set to 1 GHz
      or 2 GHz, after the script is run, the channel speed is set to 
      auto (auto-negotiation). Since a FC channel communicates at a 
      rate of either 1 GHz or 2 GHz, the Auto setting uses the best
      rate for communications at the time.
 
    * Non-default RCCOM settings - RCCOM channel settings are recovered 
      for Channels 2 and 3 only.  RCCOM settings for other channels are not
      recovered.  You must record and set this information with the RS-232 
      interface. 
 
    * Certain customized settings - Use the configuration file created
      in step 5 to verify that all settings have been restored. Change
      any parameters that were not restored.

    Refer to step 6 in "Preparing to Upgrade Controller Firmware" for 
    the recorded LUN filter parameters, sector/head/cylinder parameters, 
    and RCCOM settings.

    Reconfigure the array with the RS-232 firmware connection or sccli. 
 
 7. To restore your previous LUN host mappings, reference the 3.27 
    configuration file and run the following CLI commands:
 
      a. Restore the logical drive controller assignment using the 
         following command:
                set logical-drive <ld> assignment [primary | secondary] 
 
      b. Restore the channel IDs using the "configure channel" command. 
 
      c. Restore LUN maps using the "map partition" command. 
 
      d. If you use random optimization, restore it with the 
         "set cache-parameter" command.
 
      e. Refer to the sccli man page for more information about these
         commands. 
 
 8. Using the RS-232 interface, restore the parameters based on the 
    settings you recorded in step 6 in the "Preparing to Upgrade 
    Controller Firmware" section. Restore the parameter values as 
    needed for the filter map Mask, Filter type, Access Mode, 
    non-default RCCOM settings, and sector/head/cylinder settings.

==========================================================

Upgrading the Controller Firmware Manually (3.xx to 4.xx): 

----------------------------------------------------------
 
 To use the sccli to do a manual update, perform the following 
 steps. IBM AIX and HP-UX operating systems must use the manual 
 upgrade procedure to upgrade from 3xx to 4.xx. 

   -------
   Caution:
   -------
   Review all procedures and release notes for this major upgrade
   prior to upgrading your array. Downgrading back to the 3.27 
   controller firmware is recommended only for a FRU replacement
   module. All other downgrades risk loss of all data. 

   -----
   Note:
   -----
   If you will be upgrading more than one array, take note of the 
   time it takes to upgrade the first array. Then, you can 
   allot the appropriate amount of time it will take to upgrade
   your other arrays.

   -------
   Caution:
   -------
   Before you begin the upgrade, read the "Prerequisites for Upgrading
   Firmware" section.

   --------
   Warning:
   --------
   Do not restore saved 3.xx NVRAM from disk or any image file
   of 3.xx configuration on a 4.1x controller. This may cause data loss
   or data corruption.


 1. If you have not already done so, do the following:
       
       a. Stop all I/O to the array.

       b. Unmount all hosts connected to the array.

       c. Stop any Sun StorEdge Configuration Service (SSCS) agent that 
          may be running on a host connected to the array controller. 
    
       d. Stop the StorADE agent software, or any other software that 
          monitors the array,

     Reference the "Prerequisites for Upgrading Firmware" section
     for more information on the preceding items.

 2. For the controller firmware upgrade, you must use the serial port
    interface to restore the IP address and network settings and to 
    monitor the progress of the upgrade. 

    Use a null modem serial cable to connect the COM port of the RAID
    array to the serial port on a host workstation. 
 
    Set the serial port parameters on the workstation to 38,400 baud, 
    8 bit, 1 stop bit, no parity. 

 3. You can choose to complete the download in one step. Or, you can 
    complete the upgrade later. You must reset nvram to complete the 
    upgrade.

    --------
    Caution:
    --------
    The download controller-firmware command does not support a
    live upgrade (a hot download operation). The -r option in the
    following step must be used to prevent firmware download failure.
 
    To complete the download in one step and reset nvram, type:
 
     download controller-firmware --reset-nvram -r SUN413C-3511.bin

    To complete the download without resetting nvram, type:
 
     download controller-firmware --dont-reset-nvram -r SUN413C-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, which may take 10 minutes or more, before proceeding.

 4. If you specified the "--dont-reset-nvram" option, run the following 
    command:

        reset nvram

        -----
        Note:
        -----
        With firmware version 4.13, in a redundant-controller 
        configuration, you can run the reset nvram command on both 
        controllers simultaneously. 

 5. To re-establish communication with the array, use the serial 
    connection to restore the IP address, netmask, and gateway. Or,
    remap a partition to LUN0. If you are using in-band communication,
    restore channel settings (ID), LUN mapping, and inter-controller
    links for the same device used during the firmware upgrade.

 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 "413C".

 7. Reconfigure the array with the RS-232 firmware connection or sccli. 
      -----
      Note:
      -----
      The manual upgrade procedure requires extensive configuration 
      because all 4.13 factory defaults have been restored.

    Reference the 3.27 configuration .xml or .txt file or the RS-232 
    settings recorded in steps 5 and 6 of "Preparing to Upgrade 
    Controller Firmware" to reconfigure parameters.

    Using the RS-232 interface, restore the parameters based on the 
    settings you recorded in step 6 in the "Preparing to Upgrade 
    Controller Firmware" section. Restore the parameter values as 
    needed for the filter map Mask, Filter type, Access Mode, 
    non-default RCCOM settings, and sector/head/cylinder settings. 

 8. To configure your previous LUN host mappings, run the following 
    CLI commands:

      a. Restore the logical drive controller assignment using the 
         following command:
         set logical-drive <ld> assignment [primary | secondary] 

      b. Restore the channel IDs using the "configure channel" command. 

      c. Restore LUN maps using the "map partition" command. 

      d. If you use random optimization, restore it with the 
         "set cache-parameter" command.

         Refer to the sccli man page for more information about these
         commands. 
 
=====================
 
SES Firmware Upgrade:
 
---------------------
 
If you are using SES firmware revision 0420, then no SES firmware 
update is necessary and you should proceed to "PLD Firmware Upgrade."
 
    -------
    Caution:
    -------
    SES firmware upgrade will interrupt I/O. To avoid any
    possibility of application failures or filesystem corruption,
    it is necessary to ensure that no host I/O is permitted while
    the SES upgrade is taking place.
 


 1. Invoke sccli and verify that you are running sccli version 2.1.0 or 
    later with the "version" command.
 
 2. Verify the SES firmware version using the sccli "show ses-devices" 
    command:
 
      sccli> show ses-devices
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             ...
        ---------------------------------------------------------------...
         2  12 000187  SUN StorEdge 3511F A 0403 1000 204000C0FF000187 ...
                                                             Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0403 1000 204000C0FF000187 ...
                                                             Topology: ...
 
    In the example above, the information that appears where "..." is
    shown above may not be accurate until after the firmware update is
    completed, and it's not needed for the upgrade, so it won't be shown
    here.

    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.

    -----
    Note:
    -----
    Sun StorEdge 3510 FC RAID devices may be connected to Sun StorEdge 3511 
    SATA expansion units. In which case, "StorEdge 3510F A" and 
    "StorEdge 3511F D" are displayed when the "show ses-devices" command is 
    run. See the "Mixed 3510 and 3511 Upgrades" section for an example.

    To update the Sun StorEdge 3510 FC RAID device, SES firmware 
    version 1080 is required. If you are using SES firmware revision 1080,
    then no SES firmware update is necessary. 

    To install the necessary FC SES and controller firmware files, download 
    patch 113723 from Sunsolve.com. Follow the directions in 
    README.113723 to update the SES firmware to version 1080 and the 
    controller firmware to version 4.13.

 3. Examine the SES firmware revision codes displayed in the "Rev"
    column.  If all the lines contain a revision code of 0420 in the "Rev" 
    field, then no SES firmware update is necessary and you should proceed 
    to "PLD Firmware Upgrade."  In this example, the 
    "Rev" field is 0403 for both devices and therefore an upgrade is needed.
 
 4. 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 SUNWsscs 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.
 
 5. Invoke sccli again.  At the "sccli>" prompt, type the following command:
 
       download ses-firmware sesfw_3511_0420.s3r
 
    Note: 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.
 
 6. Run the sccli "show ses-devices" command again to verify that all SES
    devices have been upgraded to version 0420, as indicated by the
    "Rev" column.  In the example below, the Rev column has changed to
    "0420" for both SES devices:
 
      sccli> show ses-devices
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             ...
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3511F A 0420 1000 204000C0FF000187 ...
                                                             Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0420 1000 204000C0FF000187 ...
                                                             Topology: ...

=====================
 
PLD Firmware Upgrade:
 
---------------------
 
If you are using PLD firmware revision 1100, then no PLD firmware 
update is necessary and you should proceed to "Router Firmware Upgrade."
 
    -------
    Caution:
    -------
    Performing this PLD firmware upgrade incorrectly, by using
    a version of sccli prior to version 2.1 or power-cycling the array
    at the wrong time, could result in the array enclosure being
    rendered unusable.
 
    -----
    Note:
    -----
    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.
 
    -----
    Note:
    -----
    If you upgrade the PLD firmware inband, make sure the host's Fibre
    Channel HBA connections are restored after the PLD firmware download.
 
 1. Invoke sccli and verify that you are running sccli version 2.1 with the
    "version" command.
 
 2. Verify the PLD firmware revision by issuing the sccli "show 
    ses-devices" command:
 
      sccli> show ses-devices
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             ...
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3511F A 0413 1000 204000C0FF000187 ...
                                                             Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0413 1000 204000C0FF000187 ...
                                                             Topology: ...

    -----
    Note:
    -----
    Sun StorEdge 3510 FC RAID devices may be connected to Sun StorEdge 3511 
    SATA expansion units. In which case, "StorEdge 3510F A" and 
    "StorEdge 3511F D" are displayed when the "show ses-devices" command is 
    run. See the "Mixed 3510 and 3511 Upgrades" section for an example.

    To update the Sun StorEdge 3510 FC RAID device, PLD firmware 
    version 1000 is required. If you are using PLD firmware revision 1000,
    then no PLD firmware update is necessary and you should proceed to
    "After Upgrading."

    To install the necessary FC PLD firmware file, pld1r10.s3r, download 
    patch 113723 from Sunsolve.com. Follow the directions in the 
    "PLD Firmware Upgrade" section in README.113723 to update the PLD 
    firmware to version 1000.
 
 3. Examine the PLD firmware revision codes displayed in the "PLD"
    column. If all of the lines contain a revision code of 1100 in the
    PLD column, then no PLD firmware update is necessary and you should
    proceed to "Router Firmware Upgrade."
 
 4. 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.
 
 5. Type the following command at the "sccli>" prompt:
 
         download pld-firmware sata1100.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.
 
 6. 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.
 
 7. Restart sccli and run the "show ses-devices" command again to verify 
    that the PLD firmware revision displayed in the PLD column is 1100 for
    all SES devices shown, as in the example below:
 
      sccli> show ses-devices
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             ...
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3511F A 0413 1100 204000C0FF000187 ...
                                                           Topology: ...
         3  12 000187  SUN StorEdge 3511F A 0413 1100 204000C0FF000187 ...
                                                           Topology: ...
=======================
 
Router Firmware Upgrade:
 
-----------------------
 
If you are using router firmware revision DP0569a, then no router firmware 
update is necessary and you should proceed to "MUX Firmware Upgrade."
 
 1. 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 DP0555a  0548     0500 11     0552
        0       07EE85  3  lower DP0555a  0548     0500 11     0552
 
 2. Examine the firmware revision code displayed in the "Rev" column.
    In this case, both the upper and lower SATA routers contain DP0555a
    firmware, so and update is necessary.  If all of the lines contain a
    revision code of DP0569a in the Rev column, then no firmware update
    is necessary and you should proceed to "MUX Firmware Upgrade."
 
 3. Type the following command at the "sccli>" prompt:
 
         download sata-router-firmware FW_DP0569a.dlf
 
 4. 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.
 
 5. Run the sccli "show sata-router" command again to verify that all
    devices have been upgraded to version DP0569a, as indicated by the
    "Rev" column.  In the example below, the Rev column has changed to
    "DP0569a" 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 DP0569a   0548     0500 11     0552
        0       07EE85  3  lower DP0569a   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 "After Upgrading."
 
 1. 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
 
    -----
    Note:
    -----
    The number of MUX boards is based on the configuration. There
    are twelve boards for the RAID enclosure and twelve for each 
    expansion chassis. The configuration above has one RAID
    enclosure and one expansion chassis. 
 
 2. 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 "After Upgrading."
 
 3. Type the following command at the "sccli>" prompt:
 
         download sata-path-controller-firmware PC_BB42.dat
 
 4. 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.
 
 5. 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:
 
----------------
 
 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.
 
 3. Whenever a controller is reset, continuous media scans begin on
    all physical drives that are active components of logical drives, 
    regardless of their media scan status prior to the controller reset.
 
    If you want to stop the media scan, using the firmware application,
    perform the following steps.
    1. In the firmware application, choose view and edit Logical drives.
    2. Select the logical drive that is currently being scanned.
    3. Choose Media Scan -> Abort Media Scan, and then choose Yes to 
       terminate the media scan.
    4. Perform steps 1-3 for each logical drive on which you want to stop
       media scan.
 
    Or, to stop the media scan using the Sun StorEdge CLI, run:
 
        abort media-check [<disk-list> <ld-index> <ld-id>]

 4.  Use the RS-232 serial interface to confirm that the filter map and
     sector/head/cyclinder parameters are correct for your configuration. 
     Refer to step 6 in "Preparing to Upgrade Controller Firmware." 
 
 5. If you are using Sun StorEdge Configuration Service and Diagnostic
    Reporter to manage and monitor the storage, the following additional
    steps are required.
 
     a. You must set passwords for all Sun StorEdge Configuration 
        Service users.
    -----
    Note:
    -----
    User passwords are deleted when Sun StorEdge Configuration Service
    is uninstalled. If you had a previous configuration, you have to 
    reenter the ssmon, ssadmin, and ssconfig passwords.
 
     b. Before starting the Sun StorEdge Configuration Service Console,
        you must run the following command to specify the web browser 
        to access online help.
 
          /opt/SUNWsscs/sscsconsole/config_sscon
 
     c. The Sun StorEdge Configuration Service agent and the Sun 
        StorEdge Diagnostic Reporter agent (daemon) have been 
        installed but are not configured to start at boot time by
        default. To enable the Sun StorEdge Configuration Service agent
        to start automatically when the system boots, and to start it now,
        Type: 
 
           /etc/init.d/ssagent enable start    
 
     d. To enable the Sun StorEdge Diagnostic Reporter to start 
        automatically when the system boots, and to start it now, type:
 
          /etc/init.d/ssdgrptd enable start


=============================

Mixed 3510 and 3511 Upgrades:

-----------------------------

Sun StorEdge 3510 FC RAID devices may be connected to Sun StorEdge 3511 SATA 
expansion units. In which case, "StorEdge 3511F D" and "StorEdge 3510F A" 
are displayed when the "show ses-devices" command is run. For example:

       sccli> show ses-devices
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             ...
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3510F A 1080 1000 204000C0FF000187 ...
                                                             Topology: ...
         2  60 0066AE  SUN StorEdge 3511F D 0413 1100 204000C0FF000187 ...
                                                             Topology: ...
         3  12 000187  SUN StorEdge 3510F A 1080 1000 204000C0FF000187 ...
                                                             Topology: ...
         3  60 0066AE  SUN StorEdge 3511F D 0413 1100 204000C0FF000187 ...
                                                             Topology: ...

In a mixed 3510 and 3511 environment, the following files are required:

 1. SES firmware version 1080 for the 3510 FC RAID controller and expansion
    units (sesfw_sunfc_1080.s3r)

 2. SES firmware version 0420 for the 3511 expansion unit 
    (sesfw_3511_0420.s3r)

 3. 3510 RAID controller firmware version 413 (SUN413C-3510.bin)

 4. PLD firmware version 1000 for the 3510 FC RAID controller and expansion
    units (pld1r10.s3r)

 5. PLD firmware version 1100 for 3511 expansion units (sata1100.s3r)

 6. SATA router firmware version DP0569a for 3511 expansion units 
    (FW_DP0569a.dlf)

 7. SATA MUX firmware version BB42 for 3511 expansion units (PC_BB42.dat) 

To install the necessary FC SES, controller, and PLD files, download patch 
113723 from http://sunsolve.sun.com. Follow the directions in the 
relevant sections in README.113723 to update the SES, controller, and 
PLD firmware to the required versions.
  
    
=============================

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

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

