Document Audience:INTERNAL
Document ID:A0163-1
Title:Systems with large quantities of UDWIS/SBus Host Adapters installed may not come up after reboot due to miscommunication between the SCSI host and the target.
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:Fri Mar 31 00:00:00 MST 2000

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

 
FCO #: A0163-1
Status: inactive
Synopsis: Systems with large quantities of UDWIS/SBus Host Adapters installed may not come up after reboot due to miscommunication between the SCSI host and the target.
Date: Mar/31/00
Keywords: 

Systems with large quantities of UDWIS/SBus Host Adapters installed may not come up after reboot due to miscommunication between the SCSI host and the target

Top FIN/FCO Report: Yes
Products Reference: UDWIS/SBus Host Adapter
Product Category: Server / System Board ; Storage / A3000 ; Storage / A3500 ;
                  Storage / A1000 ; Storage / D1000
Product Affected: 
Mkt_ID   Platform   Model  Description         Serial Number
------   --------   -----  -----------         -------------

Systems Affected
------- --------
  -      E10000     ALL    Ultra Enterprise 10000    -
  -      E6500      ALL    Ultra Enterprise 6500     -
  -      E6000      ALL    Ultra Enterprise 6000     -
  -      E5500      ALL    Ultra Enterprise 5500     -
  -      E5000      ALL    Ultra Enterprise 5000     -
  -      E4500      ALL    Ultra Enterprise 4500     -
  -      E4000      ALL    Ultra Enterprise 4000     -
  -      E3500      ALL    Ultra Enterprise 3500     -
  -      E3000      ALL    Ultra Enterprise 3000     -
  -      A14        ALL    Ultra Enterprise 2        -


X-options Affected    
--------- --------
X1065A     -         -     Ultra DWIS/SBus Host Adapter    -

  -      A1000      ALL    StorEdge A1000            -
  -      D1000      ALL    StorEdge D1000            -
  -      A3000      ALL    StorEdge A3000            -
  -      A3500      ALL    StorEdge A3500            -
Parts Affected: 
Part Number   Description                 Model
-----------   -----------                 -----
370-2443-01   UDWIS/SBus SPORT-20D ULTRA    -

(SCSI Devices)
Type    Vendor    Model     SerialNumber(Min)    SerialNumber(Max)    Firmware
----    ------    -------   ------------------   ------------------   --------
N/A
References: 
ECO: WO_16478
   FIN: I0547-1, I0569-1, I0552-1
   LEAP: 1071A
   BugId: 4272400, 4230719, 4279917, 4246784
   Esc: 523110, 522070, 521024, 522036, 522925, 523016, 523175, 522262
Issue Description: 
Systems with large quantities of UDWIS/SBus Host Adapters installed (Sun part
number 370-2443-01) may not come up after reboot due to miscommunication 
between
the SCSI host and the target.  Large configurations with many UDWIS/SBus Host
Adapter cards are more vulnerable due to higher probability of encountering
the reboot problem.

If a system can be rebooted it may fail to communicate correctly with a storage
device connected via a UDWIS/SBus Host Adapter.  This would have different
results depending on the system configuration.

StorEdge A3x00 units on either standalone systems or clusters are particularly
susceptible to this problem.  Cluster or Non-cluster systems with StorEdge
A3x00s may see corrupted SCSI inquiry strings during boot up.

Example of corrupted SCSI inquiry strings;

Nov  1 13:55:49 test unix: sd2044 at QLGC,isp17: target 4 lun 0
Nov  1 13:55:49 test unix: sd2044 is /sbus@5d,0/QLGC,isp@1,10000/sd@4,0
Nov  1 13:55:49 test unix:      Vendor 'SoEG', product '00****7*********', 
(unknown capacity)

Moreover, if a node in a cluster system is running while the other booting
node is experiencing this problem, the running node will eventually be 
affected with some StorEdge A3x00 controllers being failed over by the
booting node.

+ Determining System Affectivity.

  To determine if a system is affected check the isp-fcode value as follows...

  At the ok prompt;

    dev 
    .properties
    device-end

  When .properties executes, examine the value of the property "isp-fcode".
  It should be "1.28 99/11/08" for the 1.28 FCode image.

  One can also get the version at the OS prompt via "prtconf -v", and looking
  at the value for the same property.

  EXAMPLE 1 (The command for an Ultra-2 with old UDWIS at Sbus slot 1 and 
            expected output from the ok prompt using (dev inquiry) would be);

    ok> reset-all
    ok> dev /sbus@1f,0/QLGC,isp@1,10000
    ok> .properties
    scsi-initiator-id   00000007
    clock-frequency     03938700
    differential
    isp-fcode           1.25 96/10/15    [***criteria***]
    device_type         scsi 
    intr                00000003 00000000
    interrupts          00000003
    wide
    fast-20
    reg                 00000001 00010000 00000450
    64-bit-clean
    model               QLGC,ISP1000U 
    name                QLGC,isp
    ok> device-end

  EXAMPLE 2 (Same system running Solaris 8 using prtconf -pv commmand
            produces the following output);

  ....
  Node 0xf007aa94
            scsi-initiator-id:  00000007
            clock-frequency:  03938700
            differential:  00
            isp-fcode:  '1.25 96/10/15'     [***criteria***]
            device_type:  'scsi'
            intr:  00000003.00000000
            interrupts:  00000003
            wide:  00
            fast-20:  00
            reg:  00000001.00010000.00000450
            64-bit-clean:  00
            model:  'QLGC,ISP1000U'
            name:  'QLGC,isp'
  ....

+ End of Determining System Affectivity.

Root cause analysis has determined that the problem is within the Fcode
level 1.25.

Corrective action was made available by the release of new Fcode level 1.28
via ECO# WO_16478 on November 24, 1999 by dash rolling the UDWIS/SBus Host
Adapter from 370-2443-01 to 370-2443-02.  This new Fcode was made available
in Enterprise Services via LEAP 1071A.
Implementation: 
---
  	|   |  	MANDATORY (Fully Pro-Active)
	 ---    

         ---
  	| X | 	CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
	 ---   
			
         ---
  	|   | 	UPON FAILURE
	 ---
Replacement Time Estimate: 
30 minutes
Special Considerations: 
1. This problem is seen more often on systems with CPU module(s) of higher
   clock speeds, and/or in systems with mutliple UDWIS/Sbus Host Adapters
   installed.  Reference FINI0547-1 for additional background information
   on this issue.

2. Proactive implementation is authorized in mission-critical accounts 
   with E10000, E5x00, E6x00, and clusters.  The probability of failure
   is low in most configurations except for those with many UDWIS cards.

3. WARNING!  Systems may experience "invalid command" during probe-scsi-all
   and "invalid command" during "boot -hv" from the StorEdge D1000 with a
   UDWIS card (with fcode 1.28) attached to StorEdge D1000 with the
   following OBP variables set;

     setenv diag-switch? true
     setenv diag-level max
   
   This is not a bug and the messages can be ignored.  Reference FINI0569-1
   for more information.
Corrective Action: 
For Cluster System configurations please follow the recommended procedure
in removing one node from the cluster for maintenance.  Evaluate each 
account to determine if this change applies.  Problem can affect any E10000,
clustered HA, or multi-initiator configurations which can include D1000, 
A1000, A3x00, or A7000 Sun Storage products, as well as SCSI attached
OEM storage products.

Review FINI0552-1 and, if appropriate, implement FIN's corrective action
prior to implementing this FCO.

Upon failure or request in mission-critical accounts with E10000, E5x00,
E6x00 and clusters, replace all 370-2443-01 (UDWIS SPORT-20D SBus card)
with 370-2443-02 (or above).

Upon failure, in all other configurations, replace all 370-2443-01 (UDWIS
SPORT-20D SBus card) with 370-2443-02 (or above).
Billing Type: 
Warranty: Sun will provide parts at no charge under Warranty 
           Service. On-Site Labor Rates are based on how the
           system was initially installed.

 Contract: Sun will provide parts at no charge. On-Site Labor Rates
           are based on the type of service contract.

 Non Contract: Sun will provide parts at no charge. Installation by
               Sun is available based on the On-Site Labor Rates 
               defined in the Price List.

--------------------------------------------------------------------------
Implementation Footnote: 
________________________

i)   In case of Mandatory FCOs, Enterprise Services will attempt to contact
      all known customers to recommend the part upgrade.

ii)  For controlled proactive swap FCOs, Enterprise Services mission critical
     support teams will initiate proactive swap efforts for their respective 
     accounts, as required.

iii) For Replace upon Failure FCOs, Enterprise Services partners will implement 
     the necessary corrective actions as and when they are required.

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

Supporting Documents:
____________________
 
Supporting documents for FIN/FCOs can be found on Edist.  Edist can be 
accessed internally at the following URL: http://edist.Central/.
  
* From there, follow the hyperlink path of "SunService Documentation" and 
  click on "FIN & FCO attachments", then choose the appropriate folder,  
  FIN or FCO.  This will display supporting directories/files for FINs or
  FCOs.
   
Internet Access:
_______________
 
* Access the top level URL of https://infoserver.Sun.COM


--------------------------------------------------------------------------
General:
________

Send questions or comments to finfco-manager@Sun.COM

---------------------------------------------------------------------------
Statusinactive