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

FIN #: I0897-1

Create Date: Nov/08/02

SunAlert: No

Top FIN/FCO Report: No

Products Reference: A5200 Disks

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
------   --------    -----     -----------            -------------
  -       A5200       ALL      A5200 Storage Array          -

Parts Affected: 

Part Number      Description         Model
-----------      -----------         -----
     -                -                -

References: 

BugId:   4719559 - Crystal+, photon, and leadville from matrix 
                   3.13 do not work correctly.

ESC:     539130 - disk device name displayed as WWN instead of as 
                  c#t#d# in format.

Issue Description: 

Under specific conditions, addresses for disks in a StorEdge A5200
array may display incorrectly with the 'format' command.  Instead of
appearing as "c#t#d#", a disk address will display as "c#td#".
The targetid (t#) should be an integer between 0 and 127, but instead
shows as the World Wide Name (WWN) of the A5200 disk.  This issue has
no impact on system performance or I/O operations and does not cause
data loss.

This issue can occur with StorEdge A5200 arrays in the following
configuration:

  . A5200 is connected to hosts with SUNW,qlc (ISP2200) chip HBAs
    and running Solaris 8 or later.

  . The host is running SAN drivers (fp/qlc),
      example: device path ..../SUNW,qlc@5/fp@0,0/ssd@w2200002037d9bc85,0.
    
NOTE: This issue has NOT been experienced in the following configurations:

  . A5200 is connected to a SOC+ HBA, and the host is running Solaris 7
    or below.

The issue will most likely be seen when performing a host reboot, or
when servicing an A5200 by recabling, connecting to a new host, or
changing hardware. 

Example of incorrect and correct target ID's shown with 'format':

Incorrect:

  4. c5t2200002037D9BC85d0 
        ^^^^^^^^^^^^^^^^
     /pci@9,600000/pci@2/SUNW,qlc@5/fp@0,0/ssd@w2200002037d9bc85,0

Correct:
 62. c10t64d0 
         ^^
     /pci@8,700000/pci@2/SUNW,qlc@5/fp@0,0/ssd@w2100002037c865c6,0

When this issue occurs, the following may appear in the /var/adm/messages 
file (one message per disk):

   fp: [ID 517869 kern.info] NOTICE: fp(4): NL_Port Identifier 2c doesn't
       match with Hard Address a5, Will use Port WWN 2200002037d9bc85

Note: Once an A5200 configuration is stable, this symptom is not seen.
It is generally seen when the host is rebooted after reconfiguring the
A5200.

This issue occurs when some disks take an incorrect loop address
(AL_PA) causing the fp driver to use the Port WWN of each disk for
target ID.  This causes the Volume Manager or file system to see an
incorrect path.

While Sun has been notified of this issue, our Engineering teams have
not been successful at duplicating it.  If this issue does occur at a
customer site, please use the workarounds 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.

1. Ensure there are not two A5200s with the same box ID on the FC loop.
   If this is the case, the configuration must be changed by assigning
   unique box ID's to each A5200 using the Front Panel.

2. If the above is not the case, apply one of the workarounds listed below:

   A. From the Front Panel Manager (FPM) screen, spin down affected disks
      and then spin them up and then reboot the affected host(s).
      
   OR

   B. Power cycle the A5200 and then reboot the affected host(s).
   
   OR

   C. From a host, run these two commands for each disk:
        
        "luxadm power_off ,[f|r]"
        "luxadm power_on ,[f|r]"

        Definitions:   = A5200 boxname
                     [f|r] = front (f) or rear (r)
                      = Disk slot number between 0 and 10.
                     
        Here are examples:

        Assume there is a Photon enclosure named BOB.
        If front slot 6 has the problem, do:

        #luxadm power_off BOB,f6
        #luxadm power_on BOB,f6

        If a disk in rear slot 0 has the problem, do:

        luxadm power_off BOB,r0
        luxadm power_on BOB,r0
                     
        Reboot the affected host(s).
      
  OR

   D. Download two shell scripts which automatically power off and power on
      the affected disks.  The two scripts are: S01Photonreset and photonreset.
      They may be obtained from the following URL:
      
      http://pts-americas.west/nws/products/A5x00/tools.html                  

     These scripts can be used to make sure that problem is fixed
     automatically.  Every time a host is rebooted, all target ids will be
     checked and corrected automatically.  Place these two scripts in the
     /etc/rc2.d directory.  Placing the scripts in this directory will run
     these scripts during the boot process.  If this issue is detected,
     these disks will be corrected and the host will be rebooted automatically.

     To run these scripts for the first time or to run them manually, type:
     
     # sh /etc/rc2.d/S01Photonreset

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.ebay/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://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------