Document Audience: | INTERNAL |
Document ID: | I0749-1 |
Title: | OS mapping versus physical location of CPU modules for E420R, E450, U80 and Netra t1400/t1405 systems may lead to incorrect module replacement. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2004-02-23 |
---------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by Enterprise Services)
FIN #: I0749-1
Synopsis: OS mapping versus physical location of CPU modules for E420R, E450, U80 and Netra t1400/t1405 systems may lead to incorrect module replacement.Create Date: Dec/03/01
SunAlert: No
Top FIN/FCO Report: No
Products Reference: E450, E420R, U80, Netra t1400/t1405 CPU
Product Category: Server / Service
Product Affected:
------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- A25 ALL Enterprise 450 -
- A27 ALL Ultra 80 -
- A33 ALL Enterprise 420R -
- N14 ALL Netra-T1405 -
- N15 ALL Netra-T1400 -
- E450 ALL Ultra Enterprise 450 -
X-Options Affected
------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- - - - -
Parts Affected:
Part Number Description Model
----------- ----------- -----
- - -
References:
N/A
Issue Description:
There is a discrepancy between Solaris Operating System mapping and the
installation order of CPU modules for Enterprise 450, Enterprise 420R,
Ultra 80 and Netra t1400/t1405 systems.
The OS refers to CPUs by their Ultra Port Architecture (UPA) ids. Slot
numbers J0101, J0201, J0301 and J0401 in hardware essentially refer to
Ultra Port Architecture Identification Number (UPAID) ids 0, 1, 2 and 3.
The order in which the CPUs are installed in these slots does not
correlate to their UPA ids.
When referring to CPUs by hardware slot number, there is no confusion
about a CPUs location which is given in OS error messages. Note that
slot numbers start from 1, whereas UPA ids start from 0.
The problem arises when referring to CPUs by the order in which they
have been installed. If the OS prints an error message stating that CPU
0x1 is bad, it is referring to the CPU in slot 2 (J0201) and not the
first CPU which was installed, ie; CPU 0x3 in J0401 in an E450 system,
or CPU 0x2 in J0301 in an E420R system. This is a procedural problem
and not a technical one. When an FE replaces a CPU module that is
identified by the OS error messages, it is possible that the wrong CPU
module could be replaced.
The issue is CPU OS mapping versus installation order, which can cause
some confusion when replacing the CPUs.
The OS maps the CPUs as follows:
cpu 0 (labeled CPU-A1 in System Handbook)
cpu 1 (labeled CPU-A2 in System Handbook)
cpu 2 (labeled CPU-B1 in System Handbook)
cpu 3 (labeled CPU-B2 in System Handbook)
Below example shows the labeling inside the chassis on the label attached
to the module cardcage. Starting closest to the edge of the system board,
and ending nearest the I/O slots and Psycho chips, the CPUs are installed
in the following order:
First CPU-B2 (cpu 3)
Second CPU-A2 (cpu 1)
Third CPU-B1 (cpu 2)
Fourth CPU-A1 (cpu 0)
An example of a system message follows, when an ecache failure is reported
on one of the CPU modules. Please note the CPU number called out by the OS:
Oct 31 00:24:11 densgx3 unix: WARNING: [AFT1] WP event on CPU1, errID
0x002663ec.18d72631
Oct 31 00:24:11 densgx3 unix: AFSR 0x00000000.00800200 AFAR
0x00000000.0445b540
Oct 31 00:24:11 densgx3 unix: AFSR.PSYND 0x0200(Score 95) AFSR.ETS
0x00 Fault_PC 0x10072cf8
Oct 31 00:24:11 densgx3 unix: UDBH 0x0000 UDBH.ESYND 0x00 UDBL
0x0000 UDBL.ESYND 0x00
NOTE: This is the first failure on this system.
CPU1 was identified by the OS. It is possible that CPU3 might be
incorrectly replaced because this was the first CPU module installed.
Implementation:
---
| | MANDATORY (Fully Proactive)
---
---
| | CONTROLLED PROACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
An Authorized Enterprise Services Field Representative may avoid the
above mentioned problems by following the recommendations as shown
below.
Please use the following reference tables when identifying and replacing
a failed CPU module in E420R, E450, U80 and Netra t1400/t1405 systems.
For E420R, E450, U80 and Netra t1400/t1405 systems, CPU ids referred to
by the OS will not match the CPU module installation order. The
following table shows the correlation between slot numbers, UPA ids,
and the order of installation.
E420R, U80, Netra t1400/t1405 systems:
--------------------------------------
----------------------------------------------------------------------
| Slot Number | CPU/UPA id | Installation Order | Slot position* |
|=============+============+====================+======================|
| J0401 | 3 | 3rd | closest to mem riser |
| J0301 | 2 | 1st | 2nd from mem riser |
| J0201 | 1 | 2nd | 3rd from mem riser |
| J0101 | 0 | 4th | closest to PCI slots |
----------------------------------------------------------------------
NOTE: * Slot position is with reference to board schematic diagram.
E450 systems:
-------------
----------------------------------------------------------------------
| Slot Number | CPU/UPA id | Installation Order | Slot position** |
|=============+============+====================+======================|
| J0401 | 3 | 1st | B2 - bottom most |
| J0301 | 2 | 3rd | B1 - 2nd from bottom|
| J0201 | 1 | 2nd | A2 - 3rd from bottom|
| J0101 | 0 | 4th | A1 - top |
----------------------------------------------------------------------
NOTE: ** Slot position is with reference to board schematic diagram.
The next table lists CPU ids and their slot positions when you have
1, 2, 3 or 4 CPUs in an E420R, U80 or Netra t1400/t1405 system.
--------------------------------------------------------------
| #of CPUS | UPA id | Slot number | Slot position |
|===========+==========+===============+=======================|
| 1 | 2 | J0301 | 2nd from mem riser |
|-----------+----------+---------------+-----------------------|
| 2 | 2 | J0301 | 2nd from mem riser & |
| | 1 | J0201 | 3rd from mem riser |
|-----------+----------+---------------+-----------------------|
| 3 | 2 | J0301 | 2nd from mem riser |
| | 1 | J0201 | 3rd from mem riser & |
| | 3 | J0401 | closest to mem riser |
|-----------+----------+---------------+-----------------------|
| 4 | 2 | J0301 | 2nd from mem riser & |
| | 1 | J0201 | 3rd from mem riser & |
| | 3 | J0401 | closest to mem riser |
| | 0 | J0101 | closest to PCI slots |
--------------------------------------------------------------
The next table lists CPU ids and their slot positions when you have
1, 2, 3 or 4 CPUs in an E450 system:
--------------------------------------------------------------------
| #of CPUS | UPA id | Slot number | Slot position |
|===========+==========+===============+=============================|
| 1 | 3 | J0401 | B2 - bottom most |
|-----------+----------+---------------+-----------------------------|
| 2 | 3 | J0401 | B2 - bottom most & |
| | 1 | J0201 | A2 - 3rd from bottom |
|-----------+----------+---------------+-----------------------------|
| 3 | 3 | J0401 | B2 - bottom most & |
| | 1 | J0201 | A2 - 3rd from bottom & |
| | 2 | J0301 | B1 - 2nd from bottom |
|-----------+----------+---------------+-----------------------------|
| 4 | 3 | J0401 | B2 - bottom most & |
| | 1 | J0201 | A2 - 3rd from bottom & |
| | 2 | J0301 | B1 - 2nd from bottom & |
| | 0 | J0101 | A1 - top most |
--------------------------------------------------------------------
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
--------------------------------------------------------------------------