Document Audience: | INTERNAL |
Document ID: | I0594-1 |
Title: | Some StorEdge A3500 product shipped with the StorEdge A3000 name tag leading customers to believe the wrong product was delivered. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2000-09-08 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I0594-1
Synopsis: Some StorEdge A3500 product shipped with the StorEdge A3000 name tag leading customers to believe the wrong product was delivered.Create Date: Sep/08/00
Keywords:
Some StorEdge A3500 product shipped with the StorEdge A3000 name tag leading customers to believe the wrong product was delivered.
Top FIN/FCO Report: No
Products Reference: StorEdge A3500 Name Plate
Product Category: Storage / A3500
Product Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- ANYSYS - - -
X-Options Affected
------------------
X6537A A3500 - A3500 SCSI controller -
SG-XARY350A-90G - - A3500 1x5x9GB/7200, min -
SG-XARY350A-545G - - A3500 1x5x9GB/7200, max -
SG-XARY351A-180G - - A3500 1x5x18GB/7200, min -
SG-XARY352A-180G - - A3500 2x7x9GB/7200, min -
SG-XARY352A-763G - - A3500 2x7x9GB/7200, max -
SG-XARY353A-360G - - A3500 2x7x18GB/7200, min -
SG-XARY354A-1635G - - A3500 3x15x9GB/7200, max -
SG-XARY360A-90G - - A3500 1x5x9GB/10K, min (BSD) -
SG-XARY360A-545G - - A3500 1x5x9GB/10K, max -
SG-XARY362A-180G - - A3500 2x7x9GB/10K, min (BSD) -
SG-XARY362A-763G - - A3500 2x7x9GB/10K, max -
SG-XARY364A-1635G - - A3500 3x15x9GB/10K, max -
SG-XARY374A-273G - - A3500 3x15x9GB/10K, min (BSD) -
SG-XARY380A-182G - - A3500 1x5x18GB/10K, min (BSD) -
SG-XARY380A-1092G - - A3500 1x5x18GB/10K, max -
SG-XARY382A-364G - - A3500 2x7x18GB/10K, min (BSD) -
SG-XARY384A-546G - - A3500 3x15x18GB/10, min (BSD) -
SG-XARY381A-364G - - A3500 1x5x36GB/10K, min (BSD) -
SG-XARY381A-1456G - - A3500 1x5x36GB/10K, Max -
SG-XARY383A-728G - - A3500 2x7x36GB/10K, min (BSD) -
SG-XARY385A-1092G - - A3500 3x15x36/10K, min (BSD) -
Parts Affected:
Part Number Description Model
----------- ----------- -----
596-2561-01 Factory A3500 SCSI controller -
References:
ECO: WO_16119
Issue Description:
In the affected customer systems the name tag should be replaced to be
consistent with the product name. This mislabeling does not interfere
with system operation. Installation of the new name tag does not require
any special tools and comes with an adhesive backing.
The controller name tag for the StorEdge A3500 product shows as "StorEdge
A3000" although the product is being sold and shipped as StorEdge A3500.
There have been many customer calls where the customer thought the wrong
product was delivered.
All StorEdge A3500 Array Controllers that mistakenly have the StorEdge A3000
name tag were shipped in 72-Inch rack configurations only, starting in July
1998 through November 30, 1999. It is estimated that approximately 4,000
StorEdge A3500 Array Controllers were shipped with the StorEdge A3000 label.
Corrective action was made available in Sun Manufacturing as of November 30,
1999 via the release of ECO WO_16119 which changes the name tag from StorEdge
A3000 to StorEdge A3500. Corrective action was made available to Enterprise
Services as of September 2000 via a special order purchase of the StorEdge
A3500 Name Tag kit (Sun p/n 263-0942-01).
Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
To be consistent and avoid further confusion and customer calls the name
tag on customer's A3500 controllers should be replaced during the next
customer visit or per customer request.
The Service Engineer should order the name tag part number 263-0942-01
per standard ES Logistics process.
The following are instructions to replace the name tag;
1. Remove the front bezel from the rack.
2. Turn the bezel over and locate a hole behind the name tag.
3. Push through the hole with a pen or a screw driver to pop out
the old name tag.
4. Remove covering over the adhesive backing of the new name tag, carefully
align the name tag to its mounting position, and press firmly.
5. Install the bezel on the rack.
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
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 [email protected]
---------------------------------------------------------------------------