test

Trusted Solaris Installation and Configuration

Initial Configuration

Log In

  1. Log in as install, assume the root role, and open a terminal.

    See "Logging In and Launching a Terminal" for details.

SPARC: Protect Machine Hardware

    In the terminal, enter the PROM security mode. 


    # eeprom security-mode=command

Changing PROM password:
	New password: password
	Retype new password: password

    Choose the value command or full. See the eeprom(1M) man page for more details.

    If you are not prompted to enter a PROM password, the system already has a PROM password. To change the PROM password, run the command:


    # eeprom security-password=Return
Changing PROM password:
New password: password
Retype new password: password

    The new PROM security mode and password are in effect immediately, but are most likely to be noticed at the next boot.

    Caution - Caution -

    Do not forget this password. The hardware is unusable without it.

IA: Protect the BIOS

On Intel architecture, the equivalent to protecting the PROM is to protect the BIOS.

    Refer to your machine's manuals for how to protect the BIOS.

Install the Name Service Master's label_encodings File
Caution - Caution -

The label_encodings file on the client machine must be identical to the one on the name service master. If you are sure it is identical, you may skip this step.

  1. In the root role, create an ADMIN_HIGH workspace.

    See "Create an Admin_High Workspace" for details.

  2. In the ADMIN_HIGH workspace, allocate the floppy device, and insert the name service master's ADMIN_HIGH diskette containing the label_encodings file.

    See "Allocate the Appropriate Device" for details.

  3. Double-click the Check Encodings action in the System_Admin folder of the Application Manager and enter the full pathname of the label_encodings file.

  4. Answer yes to install the the name service master's label_encodings file on the client.

  5. Deallocate the floppy drive, and return to a root workspace labeled ADMIN_LOW.

Mount the Diskette With Configuration Files

You made a diskette for the client in "Copy Configuration Files for Distribution to Clients".

  1. In the root role at label ADMIN_LOW, allocate the floppy device, insert the ADMIN_LOW diskette of selected files from the name service master, and mount it.

  2. Leave up the File Manager that shows the diskette's mount point.

Initialize the SMC Server

    In the root role in an ADMIN_LOW workspace, start the SMC server process in the terminal window. 


    # smc
    Note -

    The smc command initializes the SMC server. The first time the server is launched, it performs several registration tasks, which can take a few minutes.

    If toolboxes do not load, see Step 2 in "Initializing the Solaris Management Console" for troubleshooting procedures. If the client was installed with the End User cluster, SMC will not run.