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

FIN #: I0680-1

Create Date: May/31/01

Keywords: 

SDS problem on Netra X1 due to non-unique device ID's

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Netra X1 Non-Unique Disk Device Id's

Product Category: Server / Service

Product Affected: 

Mkt_ID        Platform   Model   Description                Serial Number
------        --------   -----   -----------                -------------
Systems Affected
----------------
  -             N19       ALL    Netra X1 Server                   -

X-Options Affected
------------------
X7095A	         -         -     XOPT 20GB IDE DRIVE (F-J LITE)    -

Parts Affected: 

Part Number     Description                       Model
-----------     -----------                       -----
600-7097-02     Netra X1 400MHz 1GB 2 * 20GB        -     
F600-7097-02    FRU Netra X1 400MHz 1GB 2 * 20GB    -

References: 

BugId: 4430564 - non unique device IDs on the Netra X1 machines.

URL: 4430564http://cleese.uk/PROJECTS/FLAPJACK-LITE/software/-fin-notes.txt
     http://sdpsweb.ebay/FIN_FCO/FIN/FINIOXXX-1_dir/rwdevid.Z

Issue Description: 

Netra X1 systems with two disk drives may encounter a problem when
using Solstice Disksuite (SDS).  A failure occurs when trying to run
Solstice Disksuite on high-end Netra X1 systems shipped from the
factory with 2 disk drives installed (P/N N19-UJE1-9S-102AT1).  SDS
cannot be configured on these systems.  Netra X1 systems using X-option
disk drives will not be affected by this issue.  Netra X1 systems
manufactured prior to May-01-01 with two disk drives are subject to
this problem.

For example, a Netra X1 has two internal IDE disks c0t0d0 and c0t2d0.
These disks are on separate IDE controllers and both of them are
installed as master devices, which is normal.

The disks appear as below:

    prtvtoc -h /dev/dsk/c0t0d0s0
       0      2    00          0  36027936  36027935   /
       1      3    01   36027936   3062304  39090239
       2      5    00          0  39100320  39100319
       7      0    00   39090240     10080  39100319

    prtvtoc -h /dev/dsk/c0t2d0s0
       0      2    00          0  36027936  36027935
       1      3    01   36027936   3062304  39090239
       2      5    00          0  39100320  39100319
       7      0    00   39090240     10080  39100319

  Trying to add meta databases for SDS onto these disks fails with:

    metadb -a -c 3 -f c0t0d0s7
    metadb -a -c 3 c0t2d0s7
    metadb: irc: c0t2d0s7: overlaps with device in metadevice state 
                 database

A similar error occurs with 'metainit', the first disk is OK but SDS
believes the second disk is the same as the first one.

   bash-2.03# metainit -f d1 1 1 c0t0d0s0
   d1: Concat/Stripe is setup
   bash-2.03# metainit d2 1 1 c0t2d0s0
   metainit: irc: c0t2d0s0: overlaps with device in d1

Due to a problem with the disk duplication process in manufacturing,
disk device ID's stored on the disks are not unique.  This causes
problems with mirroring disks under SDS which requires the disk device
ID's to be different.  The device ID value is stored on the disk media
itself and is generated and written to the disk by the IDE disk device
driver the first time the disk is brought up with the system.  Once
generated, the device ID is fixed for the life of the disk.
  
This Netra X1 problem is being resolved by steps taken in Sun
Manufacturing.  For units already deployed in the field, a special
utility called 'rwdevid' has been generated which resets the disk
device ID to a blank value.  When the system is next rebooted the
device ID will be regenerated to a new unique value.

The 'rwdevid' utility is attached to bug report 4430564 and can be
retrieved by clicking on the Attachments' button once the bug has been
selected in Bugtraq.  The utility can also be downloaded from:

   http://sdpsweb.ebay/FIN_FCO/FIN/FINIO680-1_dir/rwdevid.Z

Implementation: 

---
        |   |   MANDATORY (Fully Pro-Active)
         ---    
         
  
         ---
        |   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        | X |   REACTIVE (As Required)
         ---

Corrective Action: 

The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above 
mentioned problem.

To correct the problem on a deployed Netra X1, perform the following 
guideline.

  1. Download the 'rwdevid' utility from bug 4430564 or the given URL.

     The 'rwdevid' utility can be obtained from Bugtraq report number
     4430564.  To download a copy to your local directory, start up
     bugtraq, select bug 4430564, click on the Attachments button and
     select the file rwdevid.Z.

  2. Uncompress the file and set execution permission.
     # uncompress rwdevid.Z
     # chmod 755 rwdevid
  
  3. Read the value of the device id for the 2nd disk.

     # ./rwdevid -d /dev/rdsk/c0t2d0s2

       Device Id on disk is: 696401030c646164080b5be6c391b52230ee25600


  3. Clear the device id by using the -w flag

     #./rwdevid -d /dev/rdsk/c0t2d0s2 -w

     Device Id on disk is: 696401030c646164080b5be6c391b52230ee25600
     Clearing devid.....
     Device Id cleared  

  4. Reboot the system.
  
     # init 6

  5. Continue with the Solstice Disk Suite Installation.

Comments: 

None.

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

Implementation Footnote: 

i)   In case of MANDATORY FINs, Enterprise Services will attempt to    
contact all affected customers to recommend implementation of 
the FIN. 

ii)  For CONTROLLED PROACTIVE FINs, Enterprise 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, Enterprise 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.Corp/

* 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.corp/.

* From there, follow the hyperlink path of "Enterprise Services Documenta- 
tion" 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
---------------------------------------------------------------------------