A Sun Microsystems, Inc. Business
901 San Antonio Road
Palo Alto, CA 94303-4900 USA
650 960-1300fax 650 969-9131
Part No.: 805-4500-11
Revision A, July 1998
Send comments about this document to: docfeedback@sun.com
Page 2
Copyright 1998 Sun Microsystems,Inc.,901SanAntonioRoad,PaloAlto,CA94303-4900USA.Allrightsreserved.
This productordocumentisprotectedbycopyrightanddistributedunderlicensesrestrictingitsuse,copying,distribution,anddecompilation.
No part of this productordocumentmaybereproducedinanyformbyanymeanswithoutpriorwrittenauthorizationofSunand its licensors,
if any.Third-party software, including font technology,is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registeredtrademark in
the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, the Sun logo, AnswerBook, SunDocs, and Solaris are trademarks, registered trademarks, or service marks of Sun
Microsystems,Inc. in the U.S. and other countries. All SPARCtrademarks are used under license and are trademarks or registeredtrademarks
of SPARC International, Inc. in the U.S. and other countries. Productsbearing SPARCtrademarks are based upon an architecture developed by
Sun Microsystems, Inc.
The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems,Inc. for its users and licensees. Sun acknowledges
the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.Sun
holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN
LOOK GUIs and otherwise comply with Sun’s written license agreements.
RESTRICTEDRIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR52.227-14(g)(2)(6/87) and FAR
52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR227.7202-3(a).
DOCUMENTATION IS PROVIDED“AS IS” ANDALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONSAND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 1998 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303-4900 Etats-Unis. Tousdroits réservés.
Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignentl’utilisation, la copie, la distribution, et la
décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans
l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie
relativeaux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.
Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque
déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, AnswerBook, SunDocs, et Solaris sont des marques de fabrique ou des marques déposées, ou marquesde
service, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutesles marques SPARCsont utilisées sous licence et sont des
marquesde fabrique ou des marques déposéesde SPARCInternational, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les
marquesSPARCsont basés sur une architecture développée par Sun Microsystems, Inc.
L’interfaced’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun
reconnaîtles efforts de pionniers de Xerox pour la rechercheet le développement du concept des interfaces d’utilisation visuelle ou graphique
pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence
couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux
licences écrites de Sun.
CETTE PUBLICATION EST FOURNIE "EN L’ETAT" ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N’EST ACCORDEE, Y
COMPRIS DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDE DE LA PUBLICATION A REPONDRE A UNE
UTILISATION PARTICULIERE, OU LE FAIT QU’ELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE
GARANTIE NE S’APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU.
Page 3
Installing 336-Mhz Processor
Modules into a Enterprise 10000
System
Introduction
This document provides the service provider with the information necessary to
replace 250-Mhz processor modules with 336-Mhz processor modules on a system
board.
Because of processor modules must be the same speed, all domains must be power
off. Additionally, the clock multiplier must be changed via the SSP.
This document contains the following sections to assist you with installing processor
modules on your Enterprise 10000 system.
■ Powering off a system board
■ Removing a system board
■ Processor module removal
■ Processor module installation
■ Installing a system board
■ Powering on a system board
■ Restoring the thermal calibration information using SSP version 3.0
■ Changing the clock multiplier
1
Page 4
Shut Down all Domains
The following procedure is for halting the operating system on a domain.
1. Log in to the SSP as user ssp.
2. When prompted for the SUNW_HOSTNAME, use either the platform name or the
name of an existing domain.
3. Log into the domain as root.
4. Open a netcon session to the domain in another window.
5. Notify users that the system is going down.
6. Halt the system using the appropriate Solaris commands.
The basic command for halting the system should be shutdown(1M). Refer to the
man page for options and other considerations. For example:
# cd /
# shutdown -i0 -g0 -y
7. Wait for the system-halted message and the OBP prompt to be displayed on the
netcon console window.
1. If no processor modules exist on this board, install the modules in the following
order:
1. Processor 0
2. Processor 2
3. Processor 1
4. Processor 3
For increased processor performance, avoid populating processors 0 and 1 together
and processors 2 and 3 together.
2. Verify the new processor module speed is the same as all other processor modules
that are installed or to be installed in the system.
Mixing processors speeds in a system will cause the processors that do not match the
system clock speed to fail. Refer to sys_clock(1M).
3. Verify the new processor module cache size is the same as all other processor
modules that are installed or to be installed on the system board.
Mixing cache sizes on a system board will result in the larger caches sizes being
limited to the size of the smallest. If possible, move dissimilar processor modules to
another system board.
4. Remove the thin blue plastic strip from the processor board thermal pad on the
system board, if present.
This blue plastic strip covers a white thermal pad that provides thermal relief for the
cache on the processor module. When a processor module is installed, it should be
removed permanently.
5. Prior to installing the module, wipe the gold pads of the system board and the
exposed contacts of the compression connector with a lint-free non-abrasive cloth.
6. Align processor module compression connectors to the system board compression
mating backplate.
7. Engage all captive connector screws clockwise using a
#4-40 hex-head driver.
8. Tighten the captive connector screws to a low torque of 0.34 Nm (3.0 inch pounds)
in the pattern noted in
FIGURE 2.
Installing 336-Mhz Processor Modules into a Enterprise 10000 System5
Page 8
3
5
4
2
314
FIGURE 2Tightening Pattern for the Processor Module
152
9. Tighten the captive connector screws to a final torque of 0.68 Nm (6.0 inch pounds)
in the pattern noted in
FIGURE 2.
10. Replace the system board cover and secure with Phillips screws tightening to a
torque of 1.0 Nm (8.9 inch pounds),
11. See “Installing a System Board” on page 7 to confirm the event monitoring
daemon is running prior to installing the system board.
1. To confirm the event monitoring daemon is running, type:
ssp% edd_cmd
The returned message should show State = started-monitoring. If not, it will
be necessary to restart the event monitoring daemon by typing the following:
ssp% edd_cmd -x start
Refer to edd(1M) and edd_cmd(1M) for additional information.
2. To install a system board, firmly grasp the board by the handles and position it
onto the card cage rail.
3. With the handles extended, slide the board into the slot until it begins to mate
with the centerplane connector.
4. Apply firm pressure to the face plate to engage the board with the centerplane
connector.
5. Use the insertion handles to fully seat the board.
6. Lock the handles by sliding the locking levers into position until they are fully
nested with the handles.
Installing 336-Mhz Processor Modules into a Enterprise 10000 System7
Page 10
Powering On a System Board
1. Determine the amount of system power available by typing power.
TABLE 1 to confirm the amount of available power is sufficient for the amount of
3. If using SSP version 3.0, restore the system boards thermal calibration data.
See “Restoring the Thermal Calibration Information Using SSP Version 3.0” on
page 9.”
Restoring the Thermal Calibration
Information Using SSP Version 3.0
This procedure is performed automatically by SSP version 3.1.
The system boards and centerplane contain ASICs which require thermal calibration
data in order for the SSP software to correctly report temperature data. The initial
thermal calibration of the system boards and centerplane is done during the
manufacturing process using the thermcal(1M) command. The resulting thermcal
calibration data is then written to EEPROMs resident on the boards. Once done, the
thermcal(1M) procedure need not be repeated.
The SSP software requires the correct thermal calibration data for each system board
and centerplane resident in the system. A data file containing this information is
created by the thermcal_config(1M) command. In order for this data file to be
correct, thermcal_config(1M) must be executed during SSP software installation
or when system boards or centerplanes are replaced, added, or moved to new slots.
Failure to execute this procedure in these cases will prevent the SSP software from
correctly monitoring the system's temperature.
1. Type:
% edd_cmd -x stop
This stops the edd daemon monitoring scripts.
Installing 336-Mhz Processor Modules into a Enterprise 10000 System9
Page 12
2. Type:
% thermcal_config
The thermcal_config(1M) command requires approximately 10 minutes to
complete on a system containing 16 system boards. The thermcal_config(1M)
command reads thermal data on every system board as well as the centerplane
configured in the system, and creates a file (thermcaldata.tcl).
It is important to note any errors that the thermcal_config(1M) command
encounters when performing this operation. The $SSPVAR/adm/messages contains
additional messages related to problems the thermcal_config(1M) command
encounters. Use the following command (in a separate window) to monitor the
messages file:
% tail -f $SSPVAR/adm/messages
If the thermcal_config(1M) command encounters problems when attempting to
read thermal data, you must repeat Step 2 until no errors occur.
Note – If errors of this type persist (especially for the same board), it is likely that
the board is not thermally calibrated. In this case, contact your service
representative.
This procedure is done when changing to different speed processor modules. To
upgrade from a 250-MHz processor module to a 336-MHz processor modules, the
clock multiplier must change from 3:2 to 2:1. To do this, all domains must be down
and the new processors installed onto the system board.
1. To change the multiplier value, type:
ssp% sys_clock -p two-to-one -s
This will update the ssp_resource file.
Caution – Do not run the sys_clock command with any of its command-line
options on a running system.
2. To check the multiplier value, type:
ssp% sys_clock
Installing 336-Mhz Processor Modules into a Enterprise 10000 System11