autoconfig(1M)

NAME | SYNOPSIS | CAUTION | DESCRIPTION | OPTIONS | FILES

NAME

autoconfig- scantool/interconnect auto config

SYNOPSIS

autoconfig [board_name]

CAUTION

Only authorized service providers can execute this command. You must be user ssp to run this command.

DESCRIPTION

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:

1. Reads the chip IDs from all rings on the selected board to determine the ID value and the number of chips on a ring.

2. Determines that all chip IDs are valid and that the module type for variable-length rings is recognized.

3. Builds ring signatures for each ring on the selected board.

4. Determines from the board.sigs file which rings need updating in the Scantool database, and adds new ring signatures to the board.sigs file.

5. Selects the correct ring templates for all variable-length rings that need updating in the Scantool database.

6. 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.

7. 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.

OPTIONS

The following options are supported:

board_name

Configure the specified board. Valid board names are sysboardn, where n is an integer 0 to 15, inclusive; or centerplanen, where n is either 0 or 1. Use this option only when a system board is moved from one slot to another, a new system board is added to the system, or the centerplane is replaced.

FILES

The following files in $SSPVAR/data/Ultra-Enterprise/ are supported:

common/board/sysboard/chip.ids

Contains the IDs for all the chips on a system board.

common/board/centerplane/chip.ids

Contains the IDs for all the chips on a centerplane.

common/board/sysboard/board.sigs

Contains all the ring signatures and board revision signatures built so far for the system boards.

common/board/centerplane/board.sigs

Contains all the ring signatures and board revision signatures built so far for the centerplane.

config/platform_name.config

Contains the current revision given to each system board and centerplane.

common/board/sysboard/revn/ringname.chips

revn is a copy of the rev1 directory. autoconfig edits the chips files in this copied directory, as necessary.

common/board/sysboard/revn/template.chips

revn is a copy of the rev1 directory. Variable-length rings require a template containing the correct number of chips, which can be copied over the ringname.chips file.

common/board/centerplane/revn/ringname.chips

revn is a copy of the rev1 directory. autoconfig edits the ringname.chips files for each affected ring.

SSP 3.5  Last Revised 11 July 2000

NAME | SYNOPSIS | CAUTION | DESCRIPTION | OPTIONS | FILES