Obsoleted by: 113723-18 SE3510 415G: StorEdge 3510 array controller firmware upgrade |
Disclaimer:
Please note:
Although OBSOLETED patches are available on SunSolve, Sun recommends using the most recent patches and the most recent revision of those patches. OBSOLETED patches do not include the latest bug fixes and/or product enhancements, and may require the installation of additional patches as a corrective measure.
Status: OBSOLETE
Patch Id: 113723-17
***********************************************************************
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.
***********************************************************************Summary: Obsoleted by: 113723-18 SE3510 415G: StorEdge 3510 array controller firmware upgrade
Date: Mar/16/2007
Installation Requirements:
See Special Install Instructions
Solaris Release: 8 9 10
Sun OS Release: 5.8 5.9 5.10
Unbundled Product: StorEdge 3320 Array Controller Firmware
Unbundled Release: 415G
Xref:
Topic:
Relevant Architecture: sparc x86
BugId's fixed with this patch:
4702532 4714811 4715089 4726561 4739050 4743721 4782928 4784958 4787696 4797299 4799098 4805923 4806105 4806710 4808697 4810830 4812759 4819218 4819226 4824129 4825806 4825913 4826287 4832000 4832464 4833731 4838275 4847479 4847938 4849102 4849745 4859259 4860383 4860776 4862475 4865012 4866684 4867584 4868149 4872004 4875515 4876281 4876284 4876286 4876289 4879120 4880182 4881105 4881127 4881132 4881136 4881138 4881139 4881678 4881785 4883836 4888526 4888608 4889104 4889967 4892830 4893753 4893756 4896313 4900378 4900452 4900579 4903457 4906151 4908244 4908349 4911841 4916011 4921484 4932155 4932175 4937092 4938844 4939014 4942103 4942158 4944252 4950297 4951469 4952788 4952932 4955208 4955390 4956217 4960959 4967518 4971693 4975148 4980144 4988102 4993105 4995551 5000290 5007650 5012640 5013417 5014422 5016303 5019011 5022022 5026029 5026182 5026412 5028458 5029233 5032176 5032470 5034422 5036074 5038581 5038863 5039653 5039901 5040293 5069625 5072698 5090335 5091255 5091334 5091492 5095223 6173949 6180050 6180938 6186372 6194855 6194880 6194882 6194883 6194887 6194893 6194894 6194895 6194899 6194912 6194920 6194926 6194928 6194936 6194938 6194966 6194971 6194974 6194975 6194977 6195000 6201152 6202496 6205633 6209860 6215264 6227316 6235263 6240910 6242752 6244280 6255677 6256792 6257852 6264626 6274609 6276668 6286138 6289481 6291576 6301383 6304482 6304985 6306991 6315439 6318921 6319815 6321239 6323133 6323147 6346306 6347055 6352091 6352109 6355818 6365819 6366838 6384958 6442784 6511494
Changes incorporated in this version:
6442784 6511494
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Required Patches:
Obsoleted by:
Files Included in this Patch:
JBOD_upgrade.txt # Procedures for upgrading standalone FC JBOD
README.113723-17
SUN-STOREDGE-3510-MIB.txt # SNMP MIB for installation in SNMP Managers
SUN415G-3510.bin # SE3510 Array Controller Firmware rev 415G
patchinfo
pld1r10.s3r # SE3510 Enclosure PLD Firmware rev 1000
sesfw_3510_1102.s3r # SE3510 Enclosure SES Firmware rev 1102
NOTE:
Topics included in this file:
* Problem Description
* Invoking Sun StorEdge CLI
* Upgrading Controller Firmware 4.xx to 4.15
* Mixed 3510 and 3511 Upgrades
* SES Firmware Upgrade
* PLD Firmware Upgrade
* After Upgrading
* Special Install Instructions
Problem Description:
--------------------
This patch contains all three types of firmware updates for the Sun StorEdge
3510 array subsystem: firmware for the array RAID controllers; firmware for
the SES processors in each enclosure; and firmware for the programmable
logic devices (PLD), that route Fibre Channel data within each enclosure.
The SES and PLD firmware updates are applicable to the Sun StorEdge 3510 FC
standalone FC JBOD as well as the FC RAID Array chassis. If you are
upgrading firmware in a standalone FC JBOD, you will use a separate
upgrade procedure for SES and PLD firmware upgrades. See the
JBOD_upgrade.txt document contained in this patch.
This patch also contains a SNMP MIB for installation in SNMP Managers such
as HP OpenView Network Node Manager. This MIB is specific to the Sun
StorEdge 3510. Refer to Appendix F, "SNMP Management Using HP OpenView," in
the Sun StorEdge 3000 Family RAID User's Guide for information about MIB
installation and use.
You do not need to install this patch if you have all of the following
firmware revision levels in all of your StorEdge 3510 enclosures:
Controller firmware: 415G
SES firmware: 1102
PLD firmware: 1000
You do need to install this patch if you have any of the following:
* controller firmware earlier than revision 415G, or
* SES firmware A100, 1000, 1040 1046 1080 or
* PLD firmware A000
These README instructions require that RAID controller 4.1x firmware already
be present on any arrays being upgraded. If your array currently has version
3.2x controller firmware installed, do NOT attempt to use the instructions in
this README to upgrade from version 3.2x to version 4.15. Instead, follow the
detailed instructions in the Sun StorEdge 3000 Family RAID Controller
Firmware Migration Guide. This document is part of the Sun StorEdge 3000
Family documentation set and can be downloaded by following the links from
Sun Product Documentation's Workgroup Storage web page:
http://www.sun.com/products-n-
solutions/hardware/docs/Network_Storage_Solutions/Workgroup/
This patch contains firmware that is installed on the Sun StorEdge 3510 array
using SUNWsscs package (sccli), rather than using installpatch or patchadd.
RAID firmware 415G addresses the following issue:
6511494 35xx/33xx with huge I/O and Write Cache Enable can lead to filesystem corruption
SES firmware 1102 addresses the following issue:
6442784 False Power Supply Not Available messages and other SES events and Amber LED's reported
(from 113723-15)
RAID firmware 415F addresses the following issues:
4875515 Add minimal SNMP agent support for automated discovery
5095223 Recovery Behavior of LD needs to be a manual process.
6194899 Cleared SNMP events re-appear after Primary controller failure.
6194912 SNMP: Enterprise ID and sub objects fixed
6194928 SNMP trap reports controller UID in decimal s/b hex
6194938 SNMP: Trap OIDs clashes with other enterprise group OIDs.
6194966 SNMP trap does not indicate which battery (or controller) is in exception state
6194974 SNMP: Standard Objects not supported.
6194977 "BBU Thermal Shutdown" message is ambiguous
6240910 Battery BBU failure/recharge/going to WT produces excessive messages during IO
6256792 Battery charging should not cause the RAID controller to go to "Write Through" mode
6289481 Telnet fails with message "Telnet in used"
6291576 Setting of password prevents the cache policy from been changed in the 4.11 firmware for the 3510
6301383 rfe - minnow needs a FW message to indicate cache was discarded when LD goes "dead" or "Fatal Fail"
6306991 Hitting esc. during "save NVRAM" operation can hang SE3xxx telnet/serial firmware application menu
6318921 VxSF 4.1 (x64) hang with the new 119131-08 patch and the 3510 4.1.1I firmware during hot swap
6319815 SNMP: enterprises.1714 can not be decoded
6321239 ssd panic with Reservation conflict from minnow
6323133 telnet connects but fails to display menu on SE3000 raid controllers at 4.11i f/w
6323147 SE3000 raid controller event log messages for sdram errors are misleading
6346306 "Drive Failure" "Media Scan Failed" "Clone Failed" messages are inadequate for troubleshooting
6347055 SE3510 does not return peripheral qualifier of Inquiry cmd according to the SCSI spec
6352091 Some array firmware settings cause spurious "Drive Failure" messages and mark disks as "bad"
6352109 Controller should log disk drive check conditions with sense key 0x1 & 0xB
6355818 SE3XX0 failed controller can write stale data in cache to disks upon power cycle
6365819 Repartitioning of an unmapped partition causes a cluster to panic with a reservation conflict
6366838 Controller reset from console does not flush cache prior reset, nor does it notify the end user
6384958 Improved disk error handling for SE3xxx
(from 113723-14)
SES firmware 1080 addresses the following issues:
6264626 temperature related battery problems at normal environmental conditions
6286138 Primary & secondary RAID controller batteries fault after 4.11 upgrade
6304985 Erronous battery alert messages on 3510FC
6315439 Under certain conditions ses behavior becomes unexpected, including amber LEDs and invalid events
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.
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
(from 113723-10)
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
4739050 Lun initialization lost if power failure
4743721 SSCS: no method for identifying disk drives
4782928 Request that SCCLI 'show events' command can use a time argument
4799098 NVRAM Restore does not prompt for reboot
4806105 FW 3.25O enhancement to allow multiple simultaneous rebuilds
4806710 Various host lun screens should have top to bottom wrap
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
4847938 sccli inquiry does not show the IP address
4860776 create user configurable function to add timeout/disconnect on telnet session
4866684 open tcp/ip ports
4868149 Drive state inconsistency when aborting clone on 3510
4872004 Time not consistent between primary and secondary controllers during failure
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.
4876286 sccli: Add support to view temperature event thresholds of 3510 - CPU and Boards
4876289 sccli: Add support to view voltage event thresholds of 3510 - +3.3v, +5v & +12v.
4879120 3510 to support scsi read/write buffer as per 'scsibit' use
4881105 Ability to set Date, Time, and TZ through the External Interface
4881127 Duplicate logical drive IDs assigned on same controller
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
4881785 Cluster panics with Logical Volume on Secondary Controller
4883836 sccli: no method for identifying disk drives
4888526 Temperature events should contain the sensor number
4888608 Solaris SES driver receives incorrect response from 3510 RAID in attach
4889967 Time Stamp reported for an event log entry is not constant, it changes over time
4896313 cache data isn't flushed correctly in case of primary battery failure
4900452 Network connectivity through default gateway is unreliable
4903457 Deassert Reset on Failed Controller (reinit failed ctrlr) loses access to disks
4911841 SE3510 - unable to send SNMP traps using 'agent.ini' file, as documented
4921484 3510 and 3310 did not shut down during extended overtemp conditions
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
4951469 3510 sccli should require a password
4952932 SE3510 ethernet interface cannot communicate with Cisco 2948 switch
4955390 Scgdevs cluster command causes array to reset
4956217 Unit waits 3 1/2 hours before rebuilding degraded RAID5 LD
4960959 Controller boot error in maintenace operation test with I/Os
4971693 controller reset request popup not happeneing when changing scsi timeout value
4980144 Dual ported disk can be scanned twice
4988102 Port scanning/security software cause the SE3310 to hang
4993105 Read/Write Failures on SE3510 / SE3511 during 24 hour RSCN fault injection test
4995551 Serialnumbers in eventlog are inconsistent or missing
5000290 Telnet session becomes unresponsive and requires re-telnet
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
5026412 3510 could not be managed via sccli, required reboot.
5028458 In shutdown mode, Ethernet port on secondary controller fails to go-live at fail.
5029233 SE3510/SE3511 presenting unpermissioned LUNs to host
5032176 Unable to use 3510 for more then 2 clusters if No Device Preset is not set
5032470 When bad drive parity encountered 3.27Q , event is not fully logged.
5034422 SE3510/3511 ethernet interface very slow / hangs when running at 100MB half dupl
5036074 README File for Patch 113723-07 download wait time is too short.
5038581 FI: Fan failure recovery displays different error code for telnet and sccli.
5038863 command timeout on 3510 FC array due to no XF_RDY for ~ 90 seconds
5039653 both controller get hung with sccli show lun-maps
5040293 3510: Pull Primary Battery card, SCCLI displays 3 very similar events.
5069625 Cache optimization mode can be incorrectly changed causing Data Integrity issue
5072698 Getting "NVRAM CRC Error! NVRAM must be reinitialized" on SE3510 while reseting
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
6173949 SE3510 ctlr disable when probed with 3rd party network security sw
6180050 sccli does not function on array after 3.27r upgrade
6180938 Verify a media scan is continuosly running on each LD after time of creation.
6186372 sccli device configure partition should provide an appropriate message to existing partition.
6194880 Cache optimization is changable without reset
6194882 show protocol command causes controller network interface to fail
6194883 RAID 1 Parrity regen does not correct data
6194855 Remove duplicate "it" from shutdown controller message text
6194887 Under heavy load and after 100+ failover/failbacks one controller will hang
6194893 Default protocol settings are not correct
6194894 Controller requires 2 resets after restoring defaults
6194895 View peripheral device does not update device status on a 3510.
6194920 EI return "0xFFFF" for no mapped LUNs
6194926 "delete LV" inband command fails
6194936 all events are not reported via the EI
6194971 CLI hangs, when running diagnostic bypass/unbypass device several time on all target
6194975 when changing the assignment of a logical volume it asks for reset, but it's not needed
6195000 events aren't recorded in eventlog after reset
6201152 SCMD_READ_DEFECT_LIST scsi command results in a "Reservation Conflict" panic
6209860 access to 3510 lost from four direct attached nodes during SCATE scsi3:reboot tests
6215264 Meaning of error messages on 3510 boot-up not clear.
6227316 Synopsis: Sun StorEdge 3000 Family Best Practices Manual has errors on page 36
6235263 The released documentation for adding expansion units to 3511 raid is inaccurate.
6242752 Cabling in figure 4.5 and 4.6 does not match table 4.2.
6244280 SE3510 Release notes don't explicitly state support for the SunFire V440.
The 113723-10 README file addresses:
6202496 Synopsis: Incorrect information in patch README
(from 113723-09)
SES Firmware 1046 addresses the following issues:
4975148 SES fw upgrade via cli connects inter-controller-links that were disconnected
6205633 LDs with Fujitsu drives(MAP3147F and MAS3735FC) having format->analyze problem with SE3510.
This README file addresses the following issues:
5019011 incorrect syntax in released 113723-07 README
5036074 README File for Patch 113723-07 download wait time is too short.
5039901 readme for patch 113723-07 mistakenly refers to PLD firmware of 1040
(from 113723-07)
RAID firmware 327R addresses the following issues:
4860383 out of band cli interface hangs during diag channel inquiry after 1 to 4 hours
4867584 missing LUNs on reboot (1024 LUNs, 512 per channel)
4906151 lack of sccli oob functionality follows raid controllers
4916011 Parity check never completes on random LD's in certain configurations.
4932155 P2S2 I/O failure(giving up) due to command timeout on datafailover test
4939014 Controller hang when Controller failed through sccli
4952788 telnet sessions to 3510 hang (DUPLICATE of 4860383)
4955208 Primary controller fault lead to host IO and LUN failure
5012640 Disk side fibre channel CRC link errors may cause the controller to fail
SES Firmware 1040 addresses the following issues:
4880182 FCP response packet sometimes fills in non-zero values in reserved fields
4908349 FRU physical location within 3510 is not available from the SCCLI.
(from 113723-06)
RAID firmware 327Q addresses the following issues:
4893753 FC 3510 continuously returns STATUS_BUSY
4893756 FC 3510 not responding to INQUIRY
4900378 SE3510 failed SSTM 3.1 24-hour Load & Stress (No error injection)
4900579 3510 Cache gets "pinned" at a certain percentage
4908244 the telnet menu shutdown reset hangs when cache is pinned from bug id 4900579
SES Firmware 1030 addresses the following issues:
4881678 Can't recover the FW status from data path failure on expansion cable
This README file addresses the following issues:
4932175 Firmware patch is confusing about upgrading the PLD
4942103 Patch 113723-06, README.113723-06 has embedded control characters.
4942158 3510 - SES upgrade to 1030, README.113723-06 has incorrect SES
Upgrade Step 9.
(from 113723-05)
RAID firmware 327P addresses the following issues:
4859259 telnet connection drops
4865012 Filtered LUN maps persist after Logical Drive is reassigned to other controller.
4881132 Disk status is incorrect when rebuilding after RAID 1 multiple drive failures
4892830 Cntrl F/W does not Retry if Hard Drive issues timeout (62F error)
(from 113723-04)
RAID firmware 327N addresses the following issue in version 327M:
4862475 heavy i/o load can cause unnecessary controller failover
(from 113723-03)
RAID firmware 327M addresses the following issues in version 327K:
4889104 Logical drive initialization phase takes too long
4784958 <Return> key is too sensitive to select at 3.27B FW
4805923 LUNs are inaccessible after Host resets
4808697 out of band sccli interface unavailable after extended operation.
4810830 Spelling error in "view and edit Configuration parameters" menu
4832000 scsi 2 reboot test tc_mhiocstatus failure
4832464 loss of access to LUNs after node reboots
4833731 rebooting a host impacts channel availability
4849102 scsi2 tc_mhiocstatus reboot failure with LUN filtering enabled
4849745 De-assert a failed secondary controller causes data corruption in point to point
PLD firmware version 1000 addresses the following issues:
4833731 rebooting a host impacts channel availability
4838275 Direct connect arrays failing scsi 3 reboot tests
(from 113723-02)
RAID firmware 327K addresses the following issue in version 327I:
4825913 Point to point only mode will check in as loop if more than 1 id is assigned
4805923 LUNs are inaccessible after Host resets
4787696 controller failed persistent reservation tests
(from 113723-01)
4826287 copy and replace disk activity during LD rebuild causes data corruptionRevision History:
113723-11 113723-09 113723-15 113723-02 113723-04 113723-06 113723-01 113723-14 113723-10 113723-03 113723-07 113723-05
Patch Installation Instructions:
==========================
Invoking Sun StorEdge CLI:
---------------------------
Version 2.3 or greater of the "sccli" CLI utility is required. It is included
in the SUNWsscs package, which may be downloaded from the Sun Download Center
or installed from the optional Sun StorEdge Professional Storage Manager CD.
For software installation or upgrading instructions, refer to the "Sun
StorEdge 3000 Family Software Installation Guide." Click the link for your
array on the Sun Documentation Centers Storage web page at:
sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/
Select the most recent version of software and then download the Software
Installation Guide.
The firmware procedures require the user to invoke Sun StorEdge CLI (sccli)
using the appropriate syntax for the type of connection used to manage the
array.
If the array to be upgraded is a 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.
To verify the version of "sccli" you are running type the following command
at the sccli> prompt:
version
============================================
Upgrading Controller Firmware 4.xx to 4.15
--------------------------------------------
The following procedure is used for a minor revision upgrade, such as from
4.11 to 4.15. If you are currently running 3.xx firmware, skip to
"Special Install Instructions" at the end of this README.
-----
Note:
-----
Be sure your working directory is the directory in which the patch was
unpacked and confirm that the SUN415G-3510.bin file is present.
1. Verify the Product and Revision of the array. Type the following
command at the sccli> prompt:
show inquiry
and examine the output. If the "Product" is "StorEdge 3510F D" and
"Device Type: Enclosure" appears, the device is a JBOD chassis and has
no controller firmware; skip to the JBOD_upgrade.txt document contained
in this patch.
If the Product is not "StorEdge 3510," this patch does not apply.
Select a different device or discontinue installation of this patch.
If the firmware version reported is 415G, the RAID controller firmware
does not need to be upgraded; skip to the "Mixed 3510 and 3511
Upgrades." Otherwise, continue with step 2.
2. Verify single or dual controller. Type the following command at the
sccli> prompt:
show redundancy
and examine the output. If the "array redundancy" mode is not
"Active-Active" AND the "redundancy" status is not "Enabled," skip to
step 4 and follow the instructions for upgrading a single-controller
configuration or for non-redundant configurations.
3. ONLY if the "show redundancy" command reports that the Redundancy mode
is "Active-Active" and that the status is "Enabled" (dual-controller),
AND you are currently running 4.11I or later should you continue.
----
Note:
----
Entering the "download controller-firmware" command below will cause a
controlled reset and failover of both controller modules. During this process
host I/O can be temporarily affected and recoverable errors may be recorded.
This may have an impact of IO performance during the upgrade procedure.
Retryable I/O errors and bus resets can be visible on attached hosts.
Perform the firmware upgrade by typing the following command at the
sccli> prompt:
download controller-firmware SUN415G-3510.bin
The sccli command will display the following messages:
sccli: Downloading controller firmware...programming flash memory...done
sccli: Engaging firmware...done
sccli>
Wait until the sccli> prompt appears again, which may take 10 minutes or
more, before proceeding.
If you see an error message containing the text: "please repeat download
command" or "controller firmware download ok, but engage operation is
not allowed," the controller was unable to perform the firmware
upgrade. Repeat the download as follows:
Stop all I/O activity and unmount any filesystems or volumes mounted by
a volume manager from the array. Then, type the following command at
the sccli> prompt:
download controller-firmware -r SUN415G-3510.bin
When download completes, skip to step 5.
4. Single-controller or non-redundant configurations require a reset after
downloading new firmware. This type of upgrade requires that the
controller be reset, which in turn causes the controller to stop
servicing I/O requests for several minutes.
Stop all I/O activity and unmount any filesystems or volumes mounted by
a volume manager from the array. Then, type the following command at
the sccli> prompt:
download controller-firmware -r SUN415G-3510.bin
The sccli command will display the following messages:
sccli: Downloading controller firmware...programming flash memory...done
sccli: Resetting controller...done
sccli>
Wait until the sccli> prompt appears again, which may take 10 minutes or
more, before proceeding.
5. Verify that the firmware upgrade succeeded by examining the firmware
revision again. Type the following command at the sccli> prompt:
show inquiry
and verify that the firmware revision is now reported as 415G.
6. Some customers connect Sun StorEdge 3511 expansion units to Sun StorEdge
3510 RAID controllers. If you are upgrading this mixed configuration,
follow the steps in the next section. Otherwise, skip to the "SES
Firmware Upgrade" section.
=============================
Mixed 3510 and 3511 Upgrades:
-----------------------------
Sun StorEdge 3510 FC RAID devices may be connected to Sun StorEdge 3511 SATA
expansion units. In this 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 1102 A000 204000C0FF000187
2 60 0066AE SUN StorEdge 3511F D 0420 1100 204000C0FF000187
3 12 000187 SUN StorEdge 3510F A 1102 A000 204000C0FF000187
3 60 0066AE SUN StorEdge 3511F D 0420 1100 204000C0FF000187
In a mixed 3510 and 3511 environment, the following minimum level files
are required:
1. SES firmware version 1102 for the 3510 FC RAID controller and expansion
units (sesfw_3510_1102.s3r)
2. SES firmware version 0420 for the 3511 expansion unit
(sesfw_3511_0420.s3r)
3. PLD firmware version 1000 for the 3510 FC RAID controller and expansion
units (pld1r10.s3r)
4. PLD firmware version 1100 for the 3511 expansion unit (sata1100.s3r)
5. SATA router firmware version DP0569a for 3511 expansion units
(FW_DP0569a.dlf)
6. SATA MUX firmware version BB42 for 3511 expansion units (PC_BB42.dat)
To install the necessary 3511 firmware for controller, SES, PLD, router, and
MUX, download the latest patch 113724 from http://sunsolve.sun.com. Follow
the directions in the relevant sections in README.113724 to update the
firmware to the required versions.
=====================
SES Firmware Upgrade:
---------------------
----
Note:
----
Standalone FC JBOD upgrades require using a separate upgrade procedure
for SES and PLD firmware upgrades. See the JBOD_upgrade.txt contained
in this patch.
1. Verify the SES firmware version. Type the following command at the
sccli> prompt:
show ses-devices
sccli> show ses-devices
Ch Id Chassis Vendor/Product ID Rev PLD WWNN
---------------------------------------------------------------
2 12 000187 SUN StorEdge 3510F A 1080 A000 204000C0FF000187
3 12 000187 SUN StorEdge 3510F A 1080 A000 204000C0FF000187
Examine the SES firmware revision codes displayed in the "Rev" column.
If all the lines contain a revision code of 1102 (also compatable with
3.27R) in the "Rev" field, then no SES firmware update is necessary and
you should skip to "PLD Firmware Upgrade." In the example above, the
"Rev" field is 1080 for both devices and therefore an upgrade is needed.
-----
Note:
-----
More than two lines may be displayed if a RAID enclosure has expansion
chassis connected to it. The Product ID field will be "StorEdge 3510F A"
for SES devices internal to the RAID array chassis, and "StorEdge
3510F D" for SES devices internal to the expansion chassis. If all lines
show "3510F D," you have only JBODs and no RAID array, and you should
skip to the JBOD_upgrade.txt document contained in this patch.
Sun StorEdge 3510 FC RAID devices may be connected to Sun StorEdge 3511
SATA expansion units. In this 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.
2. Since the SSCS agent may interfere with the 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 as "root" user:
/etc/init.d/ssagent stop
If the SSCS agent is running on a Microsoft Windows system connected
to the array, use the Services application (Start->Run->services.msc)
to stop the SSCS Agent service.
StorADE, or any other application that monitors the status of the
enclosure, may also interfere with controller or 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.
3. Perform the upgrade. Type the following command at the sccli> prompt:
download ses-firmware sesfw_3510_1102.s3r
-----
Note:
-----
It is not necessary to reset the RAID controller afterwards; however,
until the next controller reset, the firmware's menu interface may
continue to display the old SES firmware revision.
4. Verify that all SES devices have been upgraded. Type the following
command at the sccli> prompt:
show ses-devices
sccli> show ses-devices
Ch Id Chassis Vendor/Product ID Rev PLD WWNN
------------------------------------------------------------------
2 12 000187 SUN StorEdge 3510F A 1102 A000 204000C0FF000187
3 12 000187 SUN StorEdge 3510F A 1102 A000 204000C0FF000187
The lines should now contain a revision of 1102 as indicated by the
"Rev" column.
=====================
PLD Firmware Upgrade:
---------------------
----
Note:
----
Standalone FC JBOD upgrades require using a separate upgrade procedure
for SES and PLD firmware upgrades. See the JBOD_upgrade.txt contained
in this patch.
-------
Caution:
-------
Performing this PLD firmware upgrade incorrectly, by using a version
of sccli prior to version 2.3 or power-cycling the array at the wrong
time, can result in the array enclosure being rendered unusable.
This PLD firmware upgrade will interrupt I/O. Stop all I/O activity
and unmount any filesystems or volumes mounted by a volume manager
from the array.
-----
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.
If you upgrade the PLD firmware inband, make sure the host's Fibre
Channel HBA connections are restored after the PLD firmware download.
1. Verify the PLD firmware version. Type the following command at the
sccli> prompt:
show ses-devices
sccli> show ses-devices
Ch Id Chassis Vendor/Product ID Rev PLD WWNN
---------------------------------------------------------------
2 12 000187 SUN StorEdge 3510F A 1102 A000 204000C0FF000187
3 12 000187 SUN StorEdge 3510F A 1102 A000 204000C0FF000187
Examine the PLD firmware revision codes displayed in the "PLD" column.
If all the lines contain a revision code of 1000 in the "PLD" field,
then no PLD firmware update is necessary and you should skip to
"After Upgrading." In the example above, the "PLD" field is A000 for
both devices and therefore an upgrade is needed.
-----
Note:
-----
More than two lines may be displayed if a RAID enclosure has expansion
chassis connected to it. The Product ID field will be "StorEdge 3510F A"
for PLD devices internal to the RAID array chassis, and "StorEdge
3510F D" for PLD devices internal to the expansion chassis. If all lines
show "3510F D," you have only JBODs and no RAID array, and you should
skip to the JBOD_upgrade.txt document contained in this patch.
Sun StorEdge 3510 FC RAID devices may be connected to Sun StorEdge 3511
SATA expansion units. In this 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.
2. 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. Type
the following command at the sccli> prompt:
download pld-firmware pld1r10.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.
3. Wait at least 5 minutes after seeing the message "Power cycle the
array, including expansion units" Then turn off power to BOTH power
supplies on the array, wait 10 seconds, and then turn power back on.
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.
4. Verify that all PLD devices have been upgraded. Type the following
command at the sccli> prompt:
show ses-devices
sccli> show ses-devices
Ch Id Chassis Vendor/Product ID Rev PLD WWNN
------------------------------------------------------------------
2 12 000187 SUN StorEdge 3510F A 1102 1000 204000C0FF000187
3 12 000187 SUN StorEdge 3510F A 1102 1000 204000C0FF000187
The lines should now contain a revision of 1000 as indicated by the
"PLD" column.
================
After Upgrading:
----------------
1. If the SSCS agent was stopped, restart it with the command
"/etc/init.d/ssagent start" if it is installed on Solaris, or using
the Services utility (Start->Run->services.msc) if it is
installed on Microsoft Windows.
2. If other storage management software such as StorADE was stopped,
restart it following the procedures in the documentation for that
software.
=============================Special Install Instructions:
-----------------------------
These README instructions require that RAID controller 4.1x firmware already
be present on any arrays being upgraded. If your array currently has version
3.2x controller firmware installed, do NOT attempt to use the instructions in
this README to upgrade from version 3.2x to version 4.15. Instead, follow the
detailed instructions in the Sun StorEdge 3000 Family RAID Controller
Firmware Migration Guide. This document is part of the Sun StorEdge 3000
Family documentation set and can be downloaded by following the links from
Sun Product Documentation's Workgroup Storage web page:
http://www.sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/Workgroup/
README -- Last modified date: Thursday, October 4, 2007
|
Subscribe |
Careers |
Contact Us |
Site Maps |
Legal Notices |
Terms of Use |
Your Privacy Rights |
Sun Contracted Content
Sun Contracted Feature
