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

Upgrading Standalone FC JBOD:

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

This procedure is for upgrading a Sun StorEdge 3510 standalone JBOD
that is directly attached to a Solaris host.

There are two different procedures, depending on whether two physical
cables are attaching the 3510 to the host system. Follow the
appropriate procedure, depending on your situation.

If there are two cables from the host to the FC JBOD Array, follow the
"Two Cable Connection" procedures. If there is only one physical I/O
module installed in the FC JBOD or if there is only one cable connected
to the host, follow the "Single Cable Connection" procedures.

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

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 CDUpgrading.

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 
JBOD.

Sccli can be invoked with the name of an SES device:

        sccli /dev/es/ses<n>

Sccli can also be invoked by typing the sccli command with no arguments:

        sccli

If more than one JBOD is connected to local Fibre Channel HBAs, sccli will
display a list from which the appropriate device may be selected.

To verify the version of "sccli" you are running, type the following command
at the sccli> prompt:

       version
 
===============================

Two Cable Connection:

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

In this procedure, you must identify two different SES device filenames
for each chassis, and repeat the download for each SES/PLD device.

 1. Upgrading the two SES/PLD devices in the 3510 FC JBOD Array requires
    access to two separate device filenames in /dev/es, one for each
    SES device.

       To identify the SES devices, run the following command:

       for d in /dev/es/*; do sccli --list $d; done | grep 3510F >jbods.txt

    This command may take a few minutes to complete. When it completes,
    jbods.txt will contain two lines for each valid directly-attached JBOD
    chassis.  You can safely ignore any messages referring to non-existent
    devices.

 2. To view the output, run the following command:

       cat ./jbods.txt

       /dev/es/ses3    SUN StorEdge 3510F D SN#000187
       /dev/es/ses9    SUN StorEdge 3510F D SN#000187

    Examine the output. Verify that you see two device filenames for each
    chassis serial number, indicating that you've identified a device
    filename for each of the two SES devices in that chassis. In the example
    above, /dev/es/ses3 and /dev/es/ses9 are two separate SES devices within
    the JBOD expansion chassis with serial number 000187.

----
Note:
----
If a chassis serial number appears only once in the list, and you are sure
that your cable connections are not faulty, either your chassis contains
only one I/O Module FRU or you have only one cable attached to the host
system. In either of these cases, skip to the "Single Cable Connection"
section instead.

 3. Verify the SES firmware version. Type the following command, replacing
    the <n> with the SES device number obtained in step 2 above. 

        sccli /dev/es/ses<n> show ses-devices

        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             
        ---------------------------------------------------------------
         2  12 000187  SUN StorEdge 3510F A 1046 A000 204000C0FF000187 
                                                              

    Examine the SES firmware revision code displayed in the "Rev" column.
    If the line contains a revision code of 1080 in the "Rev" field,
    then no SES firmware update is necessary and you should skip to
    step 7.  In the example above, the "Rev" field is 1046 and therefore
    an upgrade is needed.

 4. 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 JBOD.  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 JBOD, 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 SES firmware downloads.
    Stop the StorADE agent software, or any other software that monitors
    the JBOD, following the procedures described in the documentation for
    that application.
 
 5. Perform the upgrade. Type the following command, replacing the <n> with
    the SES device number obtained in step 2 above.
        
        sccli /dev/es/<n> download ses-firmware sesfw_3510_1080.s3r
        
 6. Verify that the SES device has been upgraded. Type the following
    command, replacing the <n> with the SES device number obtained in step
    2 above.

        sccli /dev/es/ses<n> show ses-devices
 
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3510F A 1080 A000 204000C0FF000187 


    The line should now contain a revision of 1080 as indicated by the
    "Rev" column.

 7. Verify the PLD firmware version with output from step 6 above displayed
    in the "PLD" column. If you are using PLD firmware revision 1000, then
    no PLD firmware update is necessary and you should skip to step 11.
 
    -------
    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 JBOD at the end of the procedure.  Do not proceed if it is not
    possible to power cycle the array at this time.
 
 8. Make sure that all host I/O activity has been stopped.  The JBOD
    will be unable to process host I/O activity for up to 10 minutes. Type
    the following command, replacing the <n> with the SES device number
    obtained in step 2 above.

         sccli /dev/es/ses<n> download pld-firmware pld1r10.s3r 

    sccli will indicate that it is 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 JBOD YET.  Note the time and wait at least 5
    minutes for the PLD flash programming operation to complete.

 9. 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 JBOD, wait 10 seconds, and then turn power back on.
    Removing power from one power supply does not cause the JBOD to lose
    power.

10. Verify that the PLD device has been upgraded. Type the following
    command, replacing the <n> with the SES device number obtained in step
    2 above.

        sccli /dev/es/ses<n> show ses-devices
 
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3510F A 1080 1000 204000C0FF000187 

                                                             
    The line should now contain a revision of 1000 as indicated by the
    "PLD" column.

11. Repeat steps 3-10 for other SES/PLD devices displayed in the output of 
    jbods.txt obtained in step 2.

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

Single Cable Connection:

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

If there is only one I/O module installed in the FC JBOD, no special
preparation is necessary because no firmware revision mismatch can occur.
Skip to and perform only steps 3 through 10 to complete the SES/PLD upgrade.

If there is only one cable connection from the host to the FC JBOD 
but two physical I/O modules installed in the FC JBOD, upgrading
the firmware in both I/O modules requires moving the cable from one
I/O Module to the other.

This SES/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.

 1. Unplug the cable from the I/O module to which it's currently
    connected and plug it in to the other I/O module.

 2. You will need to create a new /dev/es device filename corresponding
    to the second SES device which is now connected to the host. Type the
    following command at the shell command as "root."
        
        devfsadm

    You have now created a new device for the second SES device. The first
    one will no longer be accessible.

 3. Verify the SES firmware version. Type the following command at the
    sccli> prompt:

        show ses-devices

        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             
        ---------------------------------------------------------------
         2  12 000187  SUN StorEdge 3510F A 1046 A000 204000C0FF000187 
                                                              
 
    Examine the SES firmware revision code displayed in the "Rev" column.
    If all the line contains a revision code of 1080 in the "Rev" field,
    then no SES firmware update is necessary and you should skip to
    step 7.  In the example above, the "Rev" field is 1046 and therefore
    an upgrade is needed.

 4. 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 JBOD.  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 SES firmware downloads.
    Stop the StorADE agent software, or any other software that monitors
    the JBOD, following the procedures described in the documentation for
    that application.
 
 5. Perform the upgrade. Type the following command at the sccli> prompt:

        download ses-firmware sesfw_3510_1080.s3r
        
 6. Verify that the SES device has been upgraded. Type the following command
    at the sccli> prompt:

        show ses-devices
 
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3510F A 1080 A000 204000C0FF000187 


    The line should now contain a revision of 1080 as indicated by the
    "Rev" column.

 7. Verify the PLD firmware version with output from step 6 above displayed
    in the "PLD" column. If you are using PLD firmware revision 1000, then
    no PLD firmware update is necessary and you should skip to step 11.
    If you have only one I/O module installed in the FC JBOD and PLD is 
    revision 1000, then the upgrade is complete. 
 
    -------
    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 JBOD at the end of the procedure.  Do not proceed if it is not
    possible to power cycle the array at this time.
 
 8. Make sure that all host I/O activity has been stopped.  The JBOD
    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 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 JBOD YET.  Note the time and wait at least 5
    minutes for the PLD flash programming operation to complete.

 9. 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 JBOD, wait 10 seconds, and then turn power back on.
    Removing power from one power supply does not cause the JBOD to lose
    power.

10. Verify that the PLD device has been upgraded. Type the following
    command at the sccli> prompt:

        show ses-devices
 
        Ch  Id Chassis Vendor/Product ID    Rev  PLD  WWNN             
        ------------------------------------------------------------------
         2  12 000187  SUN StorEdge 3510F A 1080 1000 204000C0FF000187 

                                                             
    The line should now contain a revision of 1000 as indicated by the
    "PLD" column.

11. Move the cable back to the I/O module to which it was originally
    connected.

12. Create a device file for the original SES device. Type the following
    command at the shell command as "root."
        
        devfsadm 

You have now re-created the original device. However the second device file
still exists.
 
13. Remove the device file created for the second SES device above. Type the
    following command at the shell command as "root"
        
        devfsadm -C

14. Follow steps 3 through 10 again to upgrade this first SES/PLD device.

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

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.




