Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-73-1020430.1
Update Date:2010-09-16
Keywords:

Solution Type  FAB (standard) Sure

Solution  1020430.1 :   FCO A0305-1: Netra T2000 with PCI Tray 371-1959-02 and Netra X4200 M2 with PCI Tray 371-2368-03 do not configure 1x or 4x PCI Express (PCIe) cards.  


Related Items
  • Sun Netra X4200 M2 Server
  •  
  • Sun Netra T2000 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Sun FAB>Hardware Remediation>Reactive
  •  

PreviouslyPublishedAs
258268


Bug Id
<SUNBUG: 6784637>

Product
Sun Netra T2000 Server
Sun Netra X4200 M2 Server

Date of Resolved Release
11-May-2009

Netra T2000 and Netra X4200 M2 with certain PCI Trays do not configure 1x or 4x PCIe cards (see details below).

Affected Parts:

371-2368-03   FRU, 4-Slot PCI Tray
371-1959-02   FRU, 4-Slot PCI Tray
371-1099-08   PCI Board

Impact

Netra T2000 systems with PCI tray 371-1959-02 and Netra X4200 M2 systems with PCI tray 371-2368-03  will not detect or configure 1x or 4x PCI Express cards in the lone PCIe slot.  This may in turn cause applications to not run properly, or prompt unnecessary hardware replacement.

Contributing Factors

This issue can occur on the following platforms...

    * Netra T2000 PCI Tray 371-1959-02 (contains PCIe Board 371-1099-08)
    * Netra X4200 M2 PCI Tray 371-2368-03 (contains PCIe Board 371-1099-08)

...with shipping dates of mid-August 2008 to mid-January 2009.

Note: This issue does not occur with 8x PCI Express cards in either of the above mentioned PCI trays.

Symptoms

Symptoms will vary, but there are no predictable symptoms that would indicate the 1x or 4x PCI Express cards are not being recognized.  One possible indication may be that applications or processes attempting to utilize these cards would fail to start.

Root Cause

A problem was found on the -08 PCI tray used on the Netra T2000 Server and the Netra X4200 M2 Server where PCIe cards less than x8 would not link train.  This problem caused PCIe cards less than x8 to go into what is called compliance mode and to not communicate with the system.  The root cause behind this issue was determined to be a problem with the Pericom 4402D device used on the receive side of the PCI signals.  This device was not allowing PCIe cards less than x8 to go into link training.  Changing to the Pericom 4402 addressed this issue and allows any PCIe card to link train properly.

This issue was addressed in Manufacturing via ECO# WO_40753 approved on February 12, 2009 and in Services via GSAP# 4686 released on February 18, 2009.

Corrective Action

Workaround:

No workaround available - see Resolution section below.

Resolution:

Hot Swappable: No

Upon Failure Only replace as follows:

   371-1959-01 (containing 371-1099-08) with 371-2368-04
   371-2368-03 (containing 371-1099-08) with 371-2368-04

Earlier and later dash levels of the above part numbers are not impacted by this issue.

Identification of Affected Parts (how to):

For the T2000, the ALOM "showfru" command can be used to determine the revision of the PCI tray installed in the system:

FRU_PROM at PCIMEZZ/SEEPROM
SEGMENT: SD
/ManR
/ManR/UNIX_Timestamp32:      THU NOV 30 22:16:46 2008
/ManR/Description:           PCI tray board
...
/ManR/Sun Part No:           3711099    <==
/ManR/Sun Serial No:         0101N7
...
/ManR/Initial HW Dash Level: 08       <==
/ManR/Initial HW Rev Level:  50
/ManR/Shortname:             PCITray
 
The above output indicates that PCI tray 371-1099 version 08 is installed in the system.

Note: Currently, ILOM does not read the "SD" segment and therefore cannot determine the revision of the PCI tray.  For the Netra X4200 M2, visual inspection on the tray is required to determine the part number.

Hardware Remediation and Material Availability Details:

All Regions/Timezones were materially ready at the time of publication of this knowledge asset.

Check with your Logistics Representative or TZ / Country / Area FCO Manager for more information with regard to material availability and the parts ordering process for this FCO.

No FCO seedstock was planned for ANZO due to an estimated small affected installed base in that Region.

References:

  BugID:  6784637
  Sun Alert:  251446
  ECO:  WO_40753
  GSAP:  4686



For information about FAB documents, its release processes, implementation strategies and billing information, go to the following URL:

For Sun Authorized Service Providers go to:

In addition to the above you may email:



Modification History
Modifications made since initial publication.

Date: 01-Jun-2009
  • Clarified affected part numbers in Resolution section.

Internal Contributor/submitter
[email protected]

Internal Eng Responsible Engineer
[email protected] Responsible Manager: [email protected]

Internal Services Knowledge Engineer
[email protected]

Internal Sun Alert & FAB Admin Info
30-Apr-2009: Initial draft sent to FCO Tiger Team for review.
11-May-2009: Materially Ready - sending to publish.


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback