SE3511 421F: StorEdge 3511 array firmware upgrade |
Status: RELEASED
Patch Id: 113724-11
***********************************************************************
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: SE3511 421F: StorEdge 3511 array firmware upgrade
Date: Sep/27/2007
Installation Requirements:
NA
Solaris Release: 8 8_x86 9 9_x86 10 10_x86
Sun OS Release: 5.8 5.8_x86 5.9 5.9_x86 5.10 5.10_x86
Unbundled Product: StorEdge 3511 Array Controller Firmware
Unbundled Release: 421F
Xref:
Topic:
Relevant Architecture: all
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 5045527 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 6289481 6304482 6314763 6324010 6327242 6358500 6362013 6365622 6365769 6365977 6368784 6374218 6386567 6389969 6390474 6407806 6417555 6445249 6462387 6472074 6473097 6476866 6501088 6511494 6519929 6601231
Changes incorporated in this version:
5045527 6314763 6358500 6362013 6365622 6365769 6365977 6368784 6374218 6386567 6389969 6390474 6407806 6417555 6445249 6462387 6472074 6473097 6476866 6501088 6519929 6601231
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Required Patches:
Obsoleted by:
Files Included in this Patch:
FW_DP0579.dlf # SATA Router firmware rev DP0579
PC_BB42.dat # SATA MUX firmware rev BB42
README.113724-11
SUN-STOREDGE-3511-MIB.txt # SNMP MIB for installation in SNMP Managers
SUN421F-3511.bin # SE3511 Array Controller Firmware rev 421F
patchinfo
sata1100.s3r # SE3511 Enclosure PLD Firmware rev 1100
sesfw_3511_0430.s3r # SE3511 Enclosure SES Firmware rev 0430
NOTE:
Topics Included in this file:
* Problem Description
* Invoking Sun StorEdge CLI
* Upgrading Controller Firmware 4.xx to 4.21
* Mixed 3510 and 3511 Upgrades
* SES Firmware Upgrade
* PLD Firmware Upgrade
* Router Firmware Upgrade
* MUX Firmware Upgrade
* After Upgrading
* Special Install Instructions
====================
Problem Description:
--------------------
This patch contains all five types of firmware updates for the Sun StorEdge
3511 array subsystem: the RAID controller, that processes I/O requests; the
SCSI Enclosure Services (SES) processor, that handles enclosure management
functions; the Programmable Logic Device (PLD) that is responsible for
routing of Fibre Channel traffic within the subsystem; the SATA SR-1216
router, that provides port routing in the SATA unit; and the SATA MUX,
that 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 Sun
StorEdge 3511 SATA Array expansion chassis (JBOD) as well as the RAID
Array chassis.
This patch also contains a SNMP MIB for installation in SNMP Managers such
as HP OpenView Network Node Manager. This MIB is specific to the Sun
StorEdge 3511. 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 3511 enclosures:
Controller firmware: 421F
SES firmware: 0430
PLD firmware: 1100
Router firmware: DP0579
MUX firmware: BB42
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.21. 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.
This patch contains firmware that is installed on the Sun StorEdge 3511
array using Sun StorEdge CLI, rather than using installpatch or patchadd.
RAID firmware 421F addresses the following issue:
5045527 3511: block ability to change mode for channels with logical drives/volumes
6314763 addition of boot error for 3510, 3511, 3310 and JBOD with duplicate target IDs
6358500 multiple media scans on se3511 disks in expansion units
6362013 Upload of mismatched (3.x vs. 4.1x) NVRAM/firmware should be rejected
6365622 SE3510/3511 - Message during partitioning from GUI is not correct
6365769 FTP error reported after incorrect password
6365977 SE3000 array must prevent partiton size changes when other partitions are still mapped
6368784 FW Application allows channel 4 and 5 to be set to 1G
6374218 LD shows hotspare present even if no hotspare configured
6386567 Actual NVRAM on the controller should be seen rather than the one tied with the firmware
6389969 Disk error handling Improvement for SE3xxx arrays
6390474 SE3xxx array should report the reason for hang/reset when unrecoverable condition is met
6407806 Recabling channels 4 & 5 to host channels causes issues with disks
6417555 Firmware 4.x controller password containing upper case "Z" letter hangs telnet session during login.
6445249 Serial Interface won't partition lun of 4TB
6462387 Slackware 2.4.31 losses LUN when connected to SE3511 in a same loop
6472074 Optimization for Random I/O does not work as expected
6473097 Irregular battery charging cycles
6476866 SE3511 performance issue
6501088 Port 1, 4 and 5 never return sense data of REPORTED LUNS DATA CHANGED in SE3511(415F)
6519929 Multiple disk failures, "none used" after reset, dead LD's following proactive drive replacements
6601231 Controller should not fail the drive when parity error(0b/47) is returned by the drive.
(from 113724-10)
RAID firmware 415G addresses the following issue:
6511494 35xx/33xx with huge I/O and Write Cache Enable can lead to filesystem corruption
from 113724-09)
RAID firmware 415F addresses the following issues:
6289481 Telnet fails with message "Telnet in used"
SES firmware 0430 addresses the following issue:
6327242 SE3511 SES device is shoftware bybassed the cause is not logged in the event log
from 113724-08)
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-02)
RAID firmware 411E addresses the following issues:
5070627 sccli 'show battery' command does not report bad battery
5072698 Getting "NVRAM CRC Error! NVRAM must be reinitialized" on SE3510 while reseting
5082717 sccli 1.6.1 - 'show battery' becomes INTERACTIVE when run for first time
5091272 cannot perform parity check on LD assigned to secondary via the cli
(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 3511Revision History:
113724-10 113724-04 113724-01 113724-09 113724-03 113724-08 113724-05
Patch Installation Instructions:
==========================
Invoking Sun StorEdge CLI:
---------------------------
Version 2.4 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.21
--------------------------------------------
The following procedure is used for a minor revision upgrade, such as from
4.11 to 4.21. 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 SUN421F-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 3511F D" and
"Device Type: Enclosure" appears, the device is a JBOD chassis and has
no controller firmware; skip 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 421F, 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 SUN421F-3511.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 SUN421F-3511.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 SUN421F-3511.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 421F.
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 1080 A000 204000C0FF000187
2 60 0066AE SUN StorEdge 3511F D 0430 1100 204000C0FF000187
3 12 000187 SUN StorEdge 3510F A 1080 A000 204000C0FF000187
3 60 0066AE SUN StorEdge 3511F D 0430 1100 204000C0FF000187
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_3510_1080.s3r)
2. SES firmware version 0430 for the 3511 expansion unit
(sesfw_3511_0430.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 DP0579 for 3511 expansion units
(FW_DP0579.dlf)
6. SATA MUX firmware version BB42 for 3511 expansion units (PC_BB42.dat)
To install the necessary 3510 firmware for controller, SES, and PLD, download
patch 113723 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:
---------------------
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 3511F A 0420 1000 204000C0FF000187
3 12 000187 SUN StorEdge 3511F A 0420 1000 204000C0FF000187
Examine the SES firmware revision codes displayed in the "Rev" column.
If all the lines contain a revision code of 0430 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 0420
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 3511F A"
for SES devices internal to the RAID array chassis, and
"StorEdge 3511F D" for SES devices internal to the expansion chassis.
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_3511_0430.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 3511F A 0430 1000 204000C0FF000187
3 12 000187 SUN StorEdge 3511F A 0430 1000 204000C0FF000187
The lines should now contain a revision of 0430 as indicated by the
"Rev" column.
=====================
PLD Firmware Upgrade:
---------------------
-------
Caution:
-------
Performing this PLD firmware upgrade incorrectly, by using a version
of sccli prior to version 2.4 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 3511F A 0413 1000 204000C0FF000187
3 12 000187 SUN StorEdge 3511F A 0413 1000 204000C0FF000187
Examine the PLD firmware revision codes displayed in the "PLD" column.
If all the lines contain a revision code of 1100 in the "PLD" field,
then no PLD firmware update is necessary and you should skip to
"Router Firmware Upgrade." In the example above, the "PLD" field is
1000 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.
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 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.
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 3511F A 0413 1100 204000C0FF000187
3 12 000187 SUN StorEdge 3511F A 0413 1100 204000C0FF000187
The lines should now contain a revision of 1100 as indicated by the
"PLD" column.
=======================
Router Firmware Upgrade:
-----------------------
-------
Caution:
-------
This Router firmware upgrade will interrupt I/O. To avoid any
possibility of application failures or filesystem corruption, ensure
that no host I/O occurs while the router upgrade is taking place.
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 DP0569a 0548 0500 11 0552
0 07EE85 3 lower DP0569a 0548 0500 11 0552
2. Examine the firmware revision code displayed in the "Rev" column.
In the example above, both the upper and lower SATA routers contain
DP0569a firmware, and an update is necessary. If all of the lines
contain a revision code of DP0579 in the Rev column, then no firmware
update is necessary and you should skip to "MUX Firmware Upgrade."
3. Type the following command at the sccli> prompt:
download sata-router-firmware FW_DP0579.dlf
4. If you do not have a redundant configuration, or do have 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.
5. Run the sccli "show sata-router" command again to verify that all
devices have been upgraded to version DP0579, as indicated by the
"Rev" column. In the example below, the Rev column has changed to
"DP0579" 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 DP0579 0548 0500 11 0552
0 07EE85 3 lower DP0579 0548 0500 11 0552
=====================
MUX Firmware Upgrade:
---------------------
-------
Caution:
-------
This MUX firmware upgrade will interrupt I/O. To avoid any possibility
of application failures or filesystem corruption, ensure that no host
I/O occurs while the MUX upgrade is taking place.
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 can
be up to twelve boards for the RAID enclosure and up to twelve for
each expansion chassis. The example 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 skip 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 do have 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.
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. In the example below, the PC150/Rev column
has "BB42" for all MUX boards:
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
================
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.21. 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, September 27, 2007
Sun Contracted Content
Sun Contracted Feature
