---------------------------------------------------------
            - Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                        FIELD INFORMATION NOTICE
               (For Authorized Distribution by SunService)

FIN #: I0916-1

Create Date: Dec/23/02

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Sun StorEdge 39x0/69x0 Array

Product Category: Storage / Service

Product Affected: 

Systems Affected:
-----------------  
Mkt_ID     Platform     Model      Description                 Serial Number
------     --------     -----      -----------                 -------------
  -         ANYSYS        -        System Platform Independent       -  


X-Options Affected:
-------------------
Mkt_ID   Platform   Model   Description   		Serial Number
------   --------   -----   -----------   		-------------
  -        3910       -     Sun StorEdge 3910 Array           -
  -        3960       -     Sun StorEdge 3960 Array           -
  -        6910       -     Sun StorEdge 6910 Array           -
  -        6960       -     Sun StorEdge 6960 Array           -

Parts Affected: 

Part Number     Description                            Model
-----------     -----------                            -----
595-5800-xx     X-Opt Python 16-port Dual Switch         -
595-5816-xx     X-Opt Python 8-port Switch               -

References: 

BugId:  4770426 - restoreswitch overwrote sw??.map file when switch had 
                  out of date flash.
        4770435 - Replacing FC-switch ch.13 needs to have step added to 
                  verify Flash on new sw.

MANUAL: 816-5253-10: Sun StorEdge 3900 and 6900 Series 1.1 Reference and  
                     Service.

Issue Description: 

The current FC Switch replacement procedure for Sun StorEdge 3900/6900
Series arrays fails to ensure that the replacement switch is running
the correct firmware prior to completing the replacement.  This can
result in the replacement failing, increased error messaging due to an
unsupported configuration and unnecessary exposure of the customer to a
single point of failure.

This issue affects any Sun StorEdge 3900/6900 Series array which uses
Storage Service Processor (SSP) monitoring where a firmware mismatch
exists between a replacement switch an its counterpart switch.
Frontend switches in 39x0 or 69x0 arrays and backend switches in the
69x0 array are affected.  Frontend switches in the 39x0SL or 69x0SL
(aka Switchless) are not affected by this problem.

This problem can be identified by comparing the firmware versions of
the replacement switch and its counterpart switch.  After powering on
the replacement switch and prior to running any other command from the
SSP:

Note: Use the appropriate switch-name (sw1a, sw1b, sw2a, sw2b)

   # showswitch -s  | grep FLASH
     FLASH:          30351             <---- This should be 30462

   # showswitch -s  | grep FLASH
     FLASH:          30462

When this issue occurs, i.e. a switch firmware mismatch exists, the
customer may see error messages from the SSP like:

   Error(s) found in logfile: /var/adm/messages.t3 on msp0 (id=83133d67):

   Oct 27 07:30:17 t3b0 ISR1[2]: N: u1d4 SVD_PATH_FAILBACK: path_id = 1
   Oct 27 07:30:17 t3b0 ISR1[2]: N: u1d5 SVD_PATH_FAILBACK: path_id = 1
   Oct 27 07:30:17 t3b0 ISR1[2]: N: u1d6 SVD_PATH_FAILBACK: path_id = 1
   Oct 27 07:30:17 t3b0 ISR1[2]: N: u1d7 SVD_PATH_FAILBACK: path_id = 1
   Oct 27 07:30:17 t3b0 ISR1[2]: N: u1d8 SVD_PATH_FAILBACK: path_id = 1
   Oct 27 07:30:17 t3b0 ISR1[2]: N: u1d9 SVD_PATH_FAILBACK: path_id = 1
   Oct 27 07:30:19 t3b0 ISR1[2]: N: u1d5 SVD_CHECK_ERROR: Cmd Aborted (path = 0)
   Oct 27 07:30:19 t3b0 ISR1[2]: N: u1d6 SVD_CHECK_ERROR: Cmd Aborted (path = 0)

OR 

   The state of chassis.temp.status on sw1a (ip=192.168.0.30) changed 
   from 'OK' to '[Undefined]'.

Currently there is only one supported version of switch firmware,
30462, for the 39x0 and 69x0 disk arrays.  However, more than one
version of the firmware exists for FRUs in Sun's spare parts
inventory.  Thus, a replacement FRU switch may not contain the correct
firmware version.

This problem will be addressed by a code fix in the next release of the
SUNWsecfg package (1.5.8).  In the meantime, please use the workaround
procedure provided below.

Implementation: 

---
        |   |   MANDATORY (Fully Proactive)
         ---    
         
  
         ---
        |   |   CONTROLLED PROACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        | X |   REACTIVE (As Required)
         ---

Corrective Action: 

The following recommendation is provided as a guideline for authorized
Sun Services Field Representatives who may encounter the above
mentioned problem.    
    
FC Switch Replacement Procedure for Sun StorEdge 3900/6900 Series Arrays
------------------------------------------------------------------------

Note: This procedure only needs to be done under the following circumstances:

The switch in question is under the control of the SSP.  In other
words, backend switches in a 6910SL, 6910, 6960SL, or 6960 and frontend
switches in a 3910, 3960, 6910 or 6960 are affected.  Frontend switches
in switchless configurations (3910SL,3960SL, 6910SL or 6960SL) are
unaffected.
	   
   1. Reinsert the GBICs into the new switch in the same port numbers
      they occupied on the removed switch.

   2.  Identify the MAC address for the new switch.

   3.  Place the switch in its position in the Sun StorEdge 3900 and
       6900 series system.

   4.  Replace the screws that connect the switch to the Sun StorEdge
       3900 and 6900 series system.

   5.  Reconnect the power cable to the switch.

   6.  Plug in the FC cables into the GBICs.

   7.  Log in to the Storage Service Processor (SSP).

   8.  Edit the /etc/ethers file on the SSP to change the old MAC address 
       to the MAC address of the new switch.  See the ethers(4) man page 
       for details.  For example:

          8:0:20:7d:93:7e 

   9.  Ensure the RARP daemon in.rarpd(1M) is running on the SSP.
       For example:

          msp0# ps -eaf | grep rarpd
             root 317 314 0 sept 28 ? 0:00 /usr/sbin/in.rarpd dmfe 1
          msp0#
        
       If the daemon is not running, start it with the following command:
        
          msp0# /usr/sbin/in.rarpd dmfe 1

   10. Power on the FC switch.

   11. Save a copy of the switch configuration data:

       # cp /opt/SUNWsecfg/etc/.map 
            /opt/SUNWsecfg/etc/.map.keep

       Note: use the appropriate switch-name (sw1a, sw1b, sw2a, sw2b).

   12. Check the switch firmware version of the newly replaced switch and 
       its counterpart in the 39x0 or 69x0:

       # showswitch -s  | grep FLASH
         FLASH:          30351             <---- This should be 30462
       
       # showswitch -s  | grep FLASH
         FLASH:          30462

       Note: sw1a & sw1b are counterparts, as are sw2a & sw2b.

   13. If the switch firmware (FLASH) is the same as the surviving switch,
        go to step 15.  If the switch firmware isn't the same as the surviving
	switch, run the following command:

        # setswitchflash -s 

   14. Confirm that the download was successful:

       # showswitch -s  | grep FLASH
       FLASH:          30462
        
       Note: if the switch firmware is not correct after running 
       setswitchflash, there are other problems beneath the surface that 
       are not addressed by this FIN and it is recommended that you escalate 
       the problem for resolution.

   15. Copy back the switch configuration data:

       # cp /opt/SUNWsecfg/etc/.map.keep 
            /opt/SUNWsecfg/etc/.map

   16. Type:

       # /opt/SUNWsecfg/bin/restoreswitch -s 

   17. Type:

       # /opt/SUNWstade/bin/config_solution -m 

       Note: model-number refers to 3910, 3960, 6910 or 6960.

   18. Bring up the Storage Automated Diagnostic Environment and replace
       the old switch name with the new one.  

       Note: It is important to delete the original switch entry prior to 
       doing a device discovery.  Refer to the Storage Automated Diagnostic
       Environment User's Guide for details.

   19. Log out of the SSP.

   20. Replace the grill that covers the FC switch.

Comments: 

None.

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

Implementation Footnote: 

i)   In case of MANDATORY FINs, Sun Services will attempt to contact   
     all affected customers to recommend implementation of the FIN. 
   
ii)  For CONTROLLED PROACTIVE FINs, Sun Services mission critical    
     support teams will recommend implementation of the FIN  (to their  
     respective accounts), at the convenience of the customer. 

iii) For REACTIVE FINs, Sun Services will implement the FIN as the   
     need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network 
browser as follows:
 
SunWeb Access:
-------------- 
* Access the top level URL of http://sdpsweb.central/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.
 
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Central/

* From there, select the appropriate link to browse the FIN or FCO index.

Internet Access:
----------------
* Access the top level URL of https://spe.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
--------------------------------------------------------------------------