| |
autoconfig checks, in turn, the chip revisions of
all configured system boards and the two centerplane halves in the Sun Enterprise
10000 system. It then looks at the sysboard/chip.ids file
for system boards or the centerplane/chip.ids file for
centerplane halves in $SSPVAR/data/Ultra-Enterprise-10000/common/board to determine the signature for the selected board. autoconfig then looks at the file board.sigs in the same
directory to determine if and how the selected system board or centerplane
half should be updated in the Scantool database.
Warning: Do not run this command on system boards
that are running the operating system, or on the centerplane if any domain
is running the operating system.
autoconfig executes the following steps:
- Reads the chip IDs from all rings on the selected board to
determine the ID value and the number of chips on a ring.
- Determines that all chip IDs are valid and that the module
type for variable-length rings is recognized.
- Builds ring signatures for each ring on the selected board.
- Determines from the board.sigs file which
rings need updating in the Scantool database, and adds new ring signatures
to the board.sigs file.
- Selects the correct ring templates for all variable-length
rings that need updating in the Scantool database.
- Updates the Scantool database, if necessary, by creating a
new revision for the board. autoconfig then adds new revision
signature to the board.sigs file.
- Updates the platform_name.config file in $SSPVAR/data/Ultra-Enterprise-10000/config with the new revision for the board.
If autoconfig detects an error on a ring, it leaves
the ring unchanged and continues. If it detects errors when accessing the chip.ids or board.sigs files, or in attempting
to edit the Scantool database, autoconfig restores the
files for the selected board, then continues.
On completion, autoconfig prompts you to reboot the
SSP to start the new Scantool database. Do this while logged in as user ssp
so that the shell environment variables are set correctly.
|
