WARNING:Articles moved into the Archived collection were accurate at the "Last Update" date, but are not maintained from that date forward.
As such, Sun disclaims all implied or express warranties with respect to the information contained in such articles.
Document Audience:INTERNAL Archive
Document ID:I0435-1
Title:DLT7000s may exhibit poor performance due to an incorrect st.conf file entry.
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Last Updated Date:1998-11-05

---------------------------------------------------------------------
        - Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                        FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)
FIN #: I0435-1
Synopsis: DLT7000s may exhibit poor performance due to an incorrect st.conf file entry.
Create Date: Oct/16/98
Keywords: 

DLT7000s may exhibit poor performance due to an incorrect st.conf file entry.

Top FIN/FCO Report: No
Products Reference: /kernel/drv/st.conf entry
Product Category: Storage / Tape
Product Affected: 
Mkt_ID   Platform   Model  Description            Serial Number
------   --------   -----  -----------            -------------
Systems Affected
----------------

   -     ANYSYS        -   System Platform Independent     -

X-Options Affected
------------------

SG-XLIBDLT1-280G   -   -   StorEdge L280 280-560GB DLT 7000 Desktop  -
SG-XLIBDLT2-280G   -   -   StorEdge L280 280-560GB DLT 7000 Rackmnt  -
SG-XLIBDLT1-1TB	   -   -   StorEdge L1000 Library Deskside    -	
SG-XLIBDLT4-1TB	   -   -   StorEdge L1000 Library Deskside    -	
SG-XLIBDLT1R-1TB   -   -   StorEdge L1000 Library Rackmount   -
SG-XLIBDLT4R-1TB   -   -   StorEdge L1000 Library Rackmount   -
SG-XTAPDLT1-1TB    -   -   StorEdge DLT 7000 Drive for L1000	
X6073A     -       -       StorEdge L1800 w 2 DLT 7000 drives       -
X6074A     -       -       StorEdge L1800 w 4 DLT 7000 drives       -
X6075A     -       -       StorEdge L3500 w 2 DLT 7000 drives       -
X6076A     -       -       StorEdge L3500 w 7 DLT 7000 drives       -
X6063A     -       -       35-70GB DLT 7000 for L1800 or L3500      -
X6060A     -    -   35-70GB DLT 7000 FlexPack w/68-68pin SCSI cable  -
X6061A     -    -   35-70GB DLT 7000 FlexPack w/50-68pin SCSI cable  -
X6062A     -    -   35-70GB DLT 7000 FlexPack w/68-68pin SCSI cable  -
Parts Affected: 
Part Number   Description   	 Model
-----------   -----------   	 -----
370-2847-0X   DRV,DLT 7000,QNTM    -   

(SCSI Devices)
Type  Vendor  Model   Serial Number(Min) Serial Number(Max) Firmware
----  ------  ------- ------------------ ------------------ --------
Tape  Quantum DLT7000       -                  -               -
References: 
BugId:  4056076    
MANUAL: 805-0648-10  35-70 Gbyte SPARCstorage DLT7000 Tape Drive 
MANUAL: 805-1034-10  Sun Enterprise Tape Library 7/3500 Facilities 
                     Planning and Installation Guide
Issue Description: 
The /kernel/drv/st.conf file entries are incorrect in Solaris 2.5.1 and  
2.6 for the DLT7000 drive.  The use of an incorrect st.conf file entry  
will cause tape format incompatibility and poor device performance.  In
addition, the host system will not recognize the tape device as a DLT-    
7000, but as a generic tape device and will assign improper tape density    
codes and device type to tape drive.  Example shown below:

The incorrect st.conf file entry is as follows:

	"Quantum DLT7000",      "Quantum DLT7000", "DLT7k-data",
DLT7k-data = 	1,0x36,0,0x1D639,4,0x82,0x83,0x84,0x85,2;
Implementation: 
---
        |   |   MANDATORY (Fully Pro-Active)
         ---    
         
  
         ---
        |   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        | X |   REACTIVE (As Required)
         ---
Corrective Action: 
To avoid the potential problems with DLT7000 configuration, as des-
cribed above, verify that the current /kernel/drv/st.conf entry is 
incorrect, if so, make the appropriate modifications as described 
below:

The correct /kernel/drv/st.conf entry:  (QUANTUM in uppercase)
 
	"QUANTUM DLT7000",      "QUANTUM DLT7000", "DLT7k-data";
DLT7k-data = 	1,0x36,0,0x1D639,4,0x82,0x83,0x84,0x85,2;
Comments: 
--------------------------------------------------------------------------
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 sup-   
     port 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://cte.corp/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 "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@cte.Corp

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