Patch-ID# 113722-06
Keywords: storedge 3310 se3310 se3000 raid storage firmware safte security
Synopsis: SE3310 325W: StorEdge 3310 array controller firmware upgrade
Date: Jul/01/2004


Install Requirements: None                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: StorEdge 3310 Array Controller Firmware

Unbundled Release: 325W

Xref: 

Topic: 

Relevant Architectures: sparc
NOTE:
This patch requires version 1.5 or later of the "sccli" utility, which
is part of the SUNWsccli package available on CD or from the Sun
Download Center.  For instructions on obtaining the latest release of
sccli, please refer to Patch Installation Instructions section below.
** DO NOT ATTEMPT TO INSTALL THIS PATCH WITH AN EARLIER VERSION OF SCCLI **
NOTE:
If the StorEdge PCI Dual Ultra3 SCSI Host Adapter, x6758A, is used
to connect the 3310 array, the qus driver must also be updated. The
updated qus driver is available in the following patches: 
        Solaris 8 Operating Environment: 112697-04
        Solaris 9 Operating Environment: 112706-03

BugId's fixed with this patch: 4717055 4723464 4764506 4792748 4802207 4809787 4809793 4810830 4826944 4842604 4847052 4865630 4876079 4881109 4881132 4889104 4929829 4956272 4969758 4975612 4986468 4988102 4989809 5036067

Changes incorporated in this version: 4929829 4969758 4986468 4988102 5036067

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: 

	saftefw_sun2u_1159.bin		# SAF-TE firmware rev 1159
        SUN325W-3310.bin		# RAID Controller firmware rev 325W
        patchinfo
README.113722-06

Problem Description:

--------------------
 
RAID firmware 325W addresses the following issues:
 
4929829 Format inquiry returns failed to SE3310 from Ultra320 LVD PCI HBA & Sun Fire V440 on-board
4969758 SE3510 uses wrong MAC address for ICMP echo reply under some circumstances
4986468 Giving up messages on SE3310 RAID array LUNs
4988102 Port scanning/security software cause the SE3310 to hang
 
This file addresses the following issue:
 
5036067 README File for Patch 113722-05 download wait time is too short.
 
(From 113722-05)
 
This file addresses the following issues:
 
4989809 Incorrect information and typo in README.113722-05
 
SAF-TE firmware 1159 addresses the following issues:
 
4865630 sccli hangs and causes I/O timeouts when 'show frus' is executed
4956272 PS LED does not change state above 40C
4975612 SAF-TE firmware upgrade results in gross phase signal errors.
 
(from 113722-03)
 
RAID firmware 325S addresses the following issues:
 
4889104 Logical drive initialization phase takes too long
4881109 Controller hangs upon encountering medium error for Raid 0 or NRAID
4881132 Disk status is incorrect when rebuilding after RAID 1 multiple drive failures
4876079 SE 3310 RAID Array syncs at 80 MBytes/sec on Ultra320 scsi ports
4847052 Silent Data Corruption when ATN line is cut
4842604 SE 3310 controller violates SCSI spec for "receive diagnostic" command
4810830 Spelling error in "view and edit Configuration parameters" menu
 
(from 113722-02)
 
RAID firmware 325Q addresses the following issues:
 
4826944 Copy and Replace function during rebuild causes data corruption
4809793 scsi incomplete retry errors when cache is optimized for Random I/O
4809787 After "defaults restore" fw asks for a controller unique id
4802207 SCSI Bus Reset and daemon.error under heavy load test for 3310
4792748 3310 incomplete read- retrying w VTS
4764506 Enabling secondary RS-232 port causes serial communication failure
 
(from 113722-01)
 
RAID firmware 325O addresses the following issues:
 
4717055 Running heavy I/O & scsi-resets to VxVM volumes on SE3310 LUNs may cause data loss
4723464 Diskomizer w/scsi resets on Minnow causes aio write/read errors and long boots

Patch Installation Instructions:
-------------------------------- 
 
This patch contains firmware which is installed on the StorEdge 3310
array controller and expansion chassis, rather than using installpatch
or patchadd.  Two types of firmware are included: RAID controller
firmware which is installed in RAID controller modules, and SAF-TE
firmware which is installed in both RAID controller chassis and
disk expansion chassis.
 
Prerequisites for installing the new firmware include:
 
 * Version 1.5 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/sccli 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/sys_admin.html
    2. Click on the link for "Sun StorEdge 3310 SCSI Array - Related Software"
    3. Log in or register as necessary
    4. Download the file named 1.5.0_sw_XXX.zip, where "XXX" describes
       your platform, and "1.5.0" may be replaced with "1.6.1" or a
       later version.
    5. Unzip the file and install the package.  For example, on Solaris:
 
		unzip 1.5.0_sw_solaris_sparc.zip
		pkgrm SUNWsccli # remove old version
		pkgadd -d solaris/`uname -p` SUNWsccli
 
    6. Verify that the correct version is installed by typing
 
		sccli version
 
 * For out-of-band (network) upgrades of the RAID controller firmware:
   an Ethernet connection for the StorEdge 3310 (two Ethernet
   connections are required if dual controllers are installed), with an
   IP address assigned, allowing the user to connect to the array via
   telnet. Refer to the Sun StorEdge 3000 Family Installation,
   Operation, and Service Manual for the Sun StorEdge 3310 SCSI Array,
   Appendix B, section B.2 for procedures to connect to the array via
   telnet.
 
 * For in-band upgrades, a SCSI connection to the array that is being
   upgraded.
 
Unpack the patch into any convenient directory such as /var/tmp, and refer
to the Special Install Instructions below.

Special Install Instructions:
----------------------------- 
 
*** Warning *** Warning *** Warning *** Warning *** Warning ***
 
The RAID controller firmware upgrade procedure will prevent StorEdge
3310 arrays from servicing normal I/O requests for one to three minutes.
For this reason, all StorEdge 3310 logical disks should be unmounted
from any Solaris hosts connected to the array for the duration of the
install procedure.  If you are unable to do this, and you have a
redundant controller configuration, refer to the manuals for the live
upgrade procedure.
 
1.  Stop I/O to the StorEdge 3310 array.  Halt applications which may be
    using the array and, if possible, unmount any filesystems,
    metadisks, or volume manager volumes mounted from the array.
 
    Since the SSCS agent may interfere with firmware downloads, it is
    necessary to stop any SSCS agent that may be running on any host
    connected to the array controller.  To stop the SSCS agent, log in
    as root on each host connected to the array and on which the
    SUNWscsa package has been installed, and issue the shell command
    "/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 which 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.
 
2.  Change your working directory, if necessary, to the directory in
    which the patch was unpacked and confirm that the SUN325W-3310.bin
    file is present using the "ls" command.
 
3.  Invoke the "sccli" command.  If only one SE3310 array is
    connected to the host, it will be selected automatically; otherwise,
    select the appropriate array from the menu.  To upgrade the firmware
    using an out-of-band connection, specify the hostname or IP address
    of the array on the sccli command line, or specify the --oob option
    to use an inband connection to determine the IP address.
 
    At the "sccli>" prompt, type "show inquiry" and examine the output.
 
    Verify that the "Product" field begins with "StorEdge 3310"; if
    it does not, this patch does not apply to the selected device.
    Specify an appropriate device or discontinue installation of this patch.
 
    If the "Product" field reports "StorEdge 3310  D" and the "Device
    Type" field is "Enclosure", the selected device is a JBOD enclosure;
    proceed to step 6 to upgrade the SAF-TE firmware.
 
    Check the "Revision" field. If the firmware version reported is
    "325W" or higher, the controller firmware does not need to be
    updated; proceed to step 6 to upgrade the SAF-TE firmware.
 
    If the firmware revision is reported as "0325", check the first 4
    digits of the "NVRAM Defaults" string; if it starts with a 4-digit
    code "325W", the controller firmware does not need to be updated;
    proceed to step 6 to update the SAF-TE firmware.
 
    Otherwise, continue the RAID controller firmare upgrade with step 4.
 
4.  Type the command "show redundancy" at the "sccli>" prompt and
    examine the output.  If the Redundancy mode is not "Active-Active" or the
    status is not "Enabled", or there is a zero in the Secondary
    controler serial number field, your configuration cannot be upgraded
    "live" and you must skip ahead to step 4b.
 
4a. If the "show redundancy" output shows that the Active-Active mode is
    Enabled and displays non-zero serial numbers for both controllers,
    then you can perform a live upgrade.
 
    WARNING: do not power-cycle the subsystem or remove either of the
    conroller FRUs within 10 minutes of performing a controller firmware
    upgrade, or the controller may be rendered inoperable.
 
    Type the command:
 
        download controller-firmware SUN325W-3310.bin
 
    and verify that the controller firmware is programmed and that the
    controller has been upgraded successfully.  If no errors are
    encountered, proceed to step 5.
 
    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 4b to do a
    non-live firmware upgrade.
 
4b. To upgrade the controller firmware into a non-redundant controller
    configuration (a single controller subsystem, or a dual controller
    system where only one controller is active), the controller must be
    reset after programming the new firmware into flash memory, and this
    will cause the array to be offline for several minutes.
 
    WARNING: do not power-cycle the subsystem or remove either of the
    conroller FRUs within 10 minutes of performing a controller firmware
    upgrade, or the controller may be rendered inoperable.
 
    Make sure all I/O activity has been stopped, and unmount any
    filesystems or volumes mounted from the array.  Download the
    controller firmware using the following command at the "sccli>"
    prompt:
 
        download controller-firmware -r SUN325W-3310.bin
 
    and then wait 2-3 minutes until the "sccli>" prompt appears again.
 
5.  At the "sccli>" prompt, verify that the new firmware is 325W by
    typing "show inquiry" and examining the "Revision" field; if the
    Revision field reports "0325", refer to the first 4 digits of the
    NVRAM Defaults field.
 
    Proceed to step 7 to update the SAF-TE firmware in the same RAID
    enclosure chassis.
 
6.  At the "sccli>" prompt, verify the SAF-TE firmware version by
    issuing the "show safte" subcommand:
 
        sccli> show safte
	Ch  Id  Chassis  Vendor  Product ID        Rev   Package
	---------------------------------------------------------
 	 0  14  000187   SUN     StorEdge 3310  A  A000  A000
 	 2  15  005632   SUN     StorEdge 3310  D  1159  1159
 
    The "show safte" command will produce one line of output for each
    enclosure; in the example above, a RAID chassis with serial number
    (000187) has an expanson chassis (005632) attached, but for a
    standalone JBOD chassis or RAID subsystems with no expansion
    chassis attached, only one enclosure will be displayed.
 
    Examine the SAFTE firmware revision codes displayed in the "Rev"
    column, and SAF-TE "Package" revision codes displayed in the
    "Package" column.  
 
    In the example above, the first chassis indicates revision A000 and
    the second indicates revision 1159.  In this case, only the first
    chassis is out of date.
 
    If BOTH the Rev column and the Package column contain "1159" or
    higher for every device reported, AND you are sure that no power
    supply FRUs have been replaced in any of the enclosures listed, no
    SAF-TE firmware upgrade is necessary; skip to step 10.  Otherwise,
    continue with step 7.
 
7.  At the "sccli>" prompt, type the following command:
 
       download safte-firmware saftefw_sun2u_1159.bin
 
    The sccli command will prompt you for confirmation and then proceed
    with a "live" updated of the SAF-TE firmware.  It is not necessary
    to restart the 3310 RAID controller following the SAF-TE firmware
    update, but the 3310 RAID controller's telnet and serial interfaces
    may continue to display the old SAF-TE firmware revision until the
    next controller reset (sccli will display the correct version number).
 
    The SAF-TE firmware download procedure normally takes several
    minutes to complete.  If the selected device is a RAID subsystem
    with one or more expansion chassis attached, all of the attached
    expansion chassis will be upgraded at the same time.
 
8.  If the firmware download operation reports a failure, repeat step 7
    one time, after verifying that no other storage software (such as
    the SSCS agent, StorADE, ESM, etc) is running and possibly
    interfering with the download.
 
9.  When upgrading SAF-TE firmware earlier than revision 1159, it is
    necessary to repeat the firmware download command twice, even if it
    looked like the download operation succeeded the first time.  This
    additional step is required because of a bug in the old firmware
    that may cause a portion of the new firmware not to be loaded
    correctly, in which case the power supplies may not be able to
    report their status correctly.  Enter the same command again at the
    "sccli>" prompt:
 
       download safte-firmware saftefw_sun2u_1159.bin
 
    After this second "download safte-firmware" command has completed,
    run the sccli subcommand "show safte" again to verify that the
    SAF-TE "Rev" column contains version "1159" and the "Package" column
    reports "1159".  For example,
 
        sccli> show safte
	Ch  Id  Chassis  Vendor  Product ID        Rev   Package
	---------------------------------------------------------
 	 0  14  012345   SUN     StorEdge 3310  A  1159  1159
 	 2  15  005632   SUN     StorEdge 3310  D  1159  1159
 
After Upgrading:
----------------
 
10. Repeat steps 3 to 9 for each additional 3310 RAID array subsystem or
    standalone JBOD chassis.
 
11. If the SSCS agent was stopped in step 1, 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 software such as StorADE was stopped, restart it following
    the procedures in the documentation for that software.

README -- Last modified date:  Thursday, July 1, 2004

