Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-73-2269228.1
Update Date:2017-06-08
Keywords:

Solution Type  FAB (standard) Sure

Solution  2269228.1 :   FCO A0379-1:Proactive: SPARC S7-2 servers with affected NVMe cables may experience POST errors during NVMe drive initiation  


Related Items
  • SPARC S7-2
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun FAB
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Internal and Partners

Applies to:

SPARC S7-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
________________________________________

Affected Parts:

7318517 - CBL,PCIE,68P,R/A,HD8i,R/A,2,3-A,SN-1U (SFF-8643 to SFF-8087 Cable, 467mm)
7318496 - CBL,PCIE,68P,R/A,HD8i,R/A,0,1-B,SN-1U (SFF-8643 to SFF-8087 Cable, 555mm)
________________________________________

Symptoms

If the described issue occurs, the failure signature observed is FMA fault ‘SPSUN4V-8000-YE - fault.io.pciex.bus-linkerr’

Impact:

Unable to use the NVMe drive in the system due to NVMe drive initialization errors seen in POST.

Changes

Contributing Factors:

SPARC S7-2 systems with NVMe cable p/n 7318517 and 7318496.

Regional Deployment Managers (RDMs) identified below have the list of affected systems and customers:

NAR: dennis.cairns@oracle.com
EMEA: roberto.donzelli@oracle.com
JAPAC: khee-huat.lim@oracle.com
LAD: sergio.alonso@oracle.com

This FCO is targeted only to systems in the list sent to RDMs.

Cause

 A small number of SPARC S7-2 systems were shipped with NVMe cables that do not fully meet design specification and could lead to POST errors during NVMe drive initialization.

Solution

Target Completion Date: 08-Sep-2017

Hot Swap: No

Workaround:

No workaround available – see Resolution section below.

Resolution:

Regional Deployment Managers (RDMs) identified below have the list of affected systems and customers:

NAR: dennis.cairns@oracle.com
EMEA: roberto.donzelli@oracle.com
JAPAC: khee-huat.lim@oracle.com
LAD: sergio.alonso@oracle.com

This FCO is targeted only to systems in the list sent to RDMs.

Replace both affected NVMe cables (p/n 7318517 and 7318496) with cables of the same part number. The replacement cables are only available as part of a cable kit (p/n 7320894). This kit contains 5 unique part numbers (the two mentioned above, and three others that will be disposed of by the Field Engineer).

Affected/Bad Part Numbers Replacement/Good Part Number

7318517

7318496

7320894 –Cable kit (This kit contains p/n 7318517 and 7318496 along with 3 other cables).

 For information on how to replace SPARC S7-2 internal NVMe cables, please refer to <Document:2154228.1>

SPARC S7-2 Server Service Manual 

An Oracle Legal approved Customer Ready Document is available here.

Identification of Affected Parts (how to):

Visually inspect both cables. The affected cables (p/n 7318517 & 7318496) with gold colored signal wires (see images 1 and 2) will need to be replaced with  cables of the same part numbers. The replacement/good cables will have silver colored signal wires (see images 3 and 4):

Affected/Bad Cables

Image 1:

 Bad Cable 1

 Image 2:

Bad Cable 2

Replacement/Good Cables

Image 3:

Good Cable 1

 Image 4:

Good Cable 2

Hardware Remediation and Material Availability Details:

Up until the estimated Target Completion Date of 08-Sep-2017 proactively remediate as described in the Resolution section above. After the Target Completion Date systems should only be remediated per standard break-fix processes.

References:

SPARC S7-2 Server Service Manual

<Document:2154228.1> How to Replace SPARC S7-2 (1 or 2 Processor) Internal NVMe Cables between the motherboard NVME controller and the Disk Backplane [VCAP]

Contacts:

Contributor/Submitter: nitin.malhotra@oracle.com
Responsible Engineer: chuck.forgues@oracle.com
Responsible Manager: fernando.bonaventura@oracle.com


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback