System Slave Boards - Sun Microsystems SPARCcenter 2000 Service Manual

E
E.3 System Slave Boards
E.3.1 SuperSPARC Modules
E-4
If there is no terminal on the system, remove all system boards except one from
the card cage (slot 0 is recommended) to force OBP to select this board as the
new master (the board must have at least one SPARC module).
System Boards with PROM Revision 2.13 (or Higher)
If all PROMs are revision 2.13 or higher, the auto-master scheme will be used
instead of master-nvram scheme to select the system master board. In this case,
nvram information is automatically propagated to all boards.
If there is no system hardware error, OBP will select the POST master board (or
the lowest board that has a functional CPU) as the system master board.
The auto-master scheme ignores the status of nvram master or slave.
If any system hardware error occurs after power on, then OBP will use the
master-nvram scheme to select a system master. See "System Boards with
PROM Revision 2.11 (or Lower)" on page 3.
The remaining system boards are "slave boards," because the master board
exercises control during portions of boot and other system operations.
For uniformity of configuration and ease of service, install and equip slave
system boards according to the guidelines below. (These guidelines are not
required by system architecture, but are strongly recommended, to maintain
consistency between systems and to simplify service procedures.)
Install slave boards in the lowest card cage slot numbers, following the
system master.
Installing SuperSPARC modules strictly according to the guidelines
presented in Section E.3.1.
Install SIMM devices strictly according to the guidelines presented in
Section E.3.3.
When installing or replacing a SuperSPARC module, use the following
guidelines to verify that you have selected a valid location.
SPARCcenter 2000/2000E Service Manual—June 1996