Document Audience: | INTERNAL
Archive
| 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 ID: | I0468-1 |
Title: | After installing SF+ System Boards in an E10000 System, domains may not reboot. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Last Updated Date: | 2004-01-07 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I0468-1
Synopsis: After installing SF+ System Boards in an E10000 System, domains may not reboot.Create Date: Dec/11/98
Keywords:
After installing SF+ System Boards in an E10000 System, domains may not reboot.
Top FIN/FCO Report: Yes
Products Reference: Failed E10000 boot process
Product Category: Server / System Board
Product Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
E10000 E10000 ALL Ultra Enterprise E10000 Server -
HPC10000 E10000 ALL Sun HPC 10000 Server -
X-Options Affected
------------------
X2761A - - E10000 System Board -
E10000-SW-SSP-3.1 - - SSP SW 3.1, CD DOC LIC -
Parts Affected:
Part Number Description Model
----------- ----------- -----
501-5240-0X E10000 System Board -
501-5278-0X E10000 System Board -
501-5279-0X E10000 System Board -
References:
BugId: 4191552
PatchId: 105683-11
Issue Description:
Sun DHPG engineering has determined that a bug exists in the inter-
action between Enterprise 10000 SSP 3.1 software and the new X2761A
Enterprise 10000 system boards.
This bug will prevent automatic reboots, failure recovery, and
processor monitoring on domains from occurring properly. The bug
will also prevent hostview from updating processor state changes from
those processors that are plugged into the new system boards.
An example of the netcon session:
---
# reboot
Nov 30 14:24:59 hostname reboot: rebooted by root
syslogd: going down on signal 15
Nov 30 14:24:59 rpcbind: rpcbind terminating on signal.
Nov 30 14:24:59 snmpdx: received signal 15
syncing file systems... done
rebooting...
Resetting...
----
Normal reboot flow would include the following:
---
...
rebooting...
Resetting...
The netcon_server disconnected.
trying to connect...
connected.
SUNW,Ultra-Enterprise-10000, using Network Console
OpenBoot 3.2.108, 2560 MB memory installed, Serial #10905627.
Ethernet address 0:0:be:a6:68:1b, Host ID: 80a6681b.
...
---
This problem is due to an incorrect check of the processor resistors
in determining the list of processors which will be monitored. In
particular, the thresholds in cbutil/adc.tcl have not been updated
with the new values which are appropriate for SF+ boards.
Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
In response to the above mentioned problem due to an interaction be-
tween the Enterprise 10000 SSP 3.1 software and the new 2761A E10000
system boards, The following recommendations are provided to resolve
the problem:
1. A temporary workaround to this problem is to initiate the boot
sequence manually by using the "bringup" command.
2. Or install:
Patch-ID# 105683-11
Keywords: Starfire cbe netcon sigbcmd sigb_get IDN flash_boot
Synopsis: SSP 3.1: sigbcmd/cbe/flash_boot patch
Date: Dec/02/98
Solaris Release: 2.5.1
SunOS release: 5.5.1
Unbundled Product: System Service Processor (SSP)
Unbundled Release: 3.1
NOTE: It is critical to follow the first 5 steps in the "Special Install
Instructions:" even if the flashprom has already been updated.
Comments:
This bug does *NOT* affect domains consisting entirely of 2760A system
boards.
This bug does *NOT* affect systems running SSP3.0.
*The revision of the patches (shown above) are subject to change. Refer
to the SunSolve database for the most current version.
--------------------------------------------------------------------------
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 [email protected]
-------------------------------------------------