Document fins/I0646-1
FIN #: I0646-1
SYNOPSIS: SSP 3.4 patch problem on E10K
DATE: May/03/01
KEYWORDS: SSP 3.4 patch problem on E10K
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: SSP 3.4 failover may prevent successful patch installation in a
dual SSP configuration.
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: E10000 with SSP 3.4 Patches
PRODUCT CATEGORY: Server / SW Admin
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- E10000 ALL Ultra Enterprise 10000 -
X-Options Affected
------------------
- - - - -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
- - -
REFERENCES:
PatchId: 
110304: SSP 3.4: autoconfig changes required to support new
ecache srams.
Manual: Sun Enterprise 10000 SSP 3.4 User Guide 806-4870-10
PROBLEM DESCRIPTION:
In a dual System Service Processor (SSP) configuration on an E10000
system, failure to disable the SSP failover capability may prevent
correct installation of SSP 3.4 Patch 110304. Some of the files
that are included in this patch which update the scantool database can
be overwritten by the failover process. It will appear that the patch
has been installed (use 'showrev -p') but some of the affected scantool
files may actually be the original versions.
Here is an example of how the scantool database can be overwritten:
. Install patches on the spare SSP and reboot.
. Force failover on the main SSP so that the spare becomes primary. At
this time data is copied from one SSP (not patched) to the
other which is patched. This will overwrite some of the files which
were included in the patch.
. Bring down the new spare SSP, install the patch(es), and reboot.
. Both SSP's now will show the patches as installed with showrev, but
the files that came with the patches have been overwritten by the
SSP failover process.
In order to identify the overwritten files after the 110304 is installed,
check the file size and cksum for the chip.ids file:
navy-ssp:nimitz% cksum
/var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/board/sysboard/chip.ids
2357333398 7129
/var/opt/SUNWssp/data/Ultra-Enterprise-10000/common/board/sysboard/chip.ids
The following are the most common symptoms:
. The corrupted scantool database failures with post, and or either other
problems.
. Autoconfig failing to recognize new Component ID's.
. Unable to power on a system board.
This problem happens due to the failover mechanism between the two
SSP's. SSP 3.4 provides an automatic failover capability which
switches the main SSP to the spare SSP under certain conditions. Patch
110304 requires a reboot of the SSP and this triggers a failover.
This problem includes all patches that install the scantool database
and configuration files such as ssp_resource. Currently, only Patch ID
110304 is affected. The instructions supplied with this FIN must
be followed when installing all future patches that update the scantool
database or SSP configuration files.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| X | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
An Authorized Enterprise Field Service Representative may avoid the
above mentioned problems by following the recommendations as shown
below.
A. In order to install affected SSP 3.4 patches in a dual SSP configuration,
please perform the following steps.
1. Run the 'setfailover off' command on the main SSP.
2. Install the patches on both the main and spare SSP's.
# patchadd <patchID#>
3. Follow any special instructions in the patch README file.
NOTE: The PatchId# 110304 README file has been updated to include
above instruction.
All new patches that include files that are copied over in the failover
process will include this information in the Special Instructions.
B. If the scantool database has already been affected by this problem, then
perform the following procedure in order to recover from the corruption.
The scantool files should be considered to be overwritten if failover has
occurred during patch installation.
1. Type "showrev -p" to display all the patches that were installed
on
the SSP.
2. Remove affected SSP 3.4 patches (currently only 110304) from
the SSP.
# patchrm <patchID#>
3. Run the 'setfailover off' command on the main SSP.
Reinstall the patches.
# setfailover off
# patchadd <patchID#>
4. Follow any special instructions in the patch README file.
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 finfco-manager@Sun.COM
---------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.