test

Trusted Solaris 8 Installation and Configuration on the Sun Enterprise 10000

Chapter 6 Solaris 8 on an E10000 Domain with a Trusted Solaris SSP

This chapter describes how to install and configure the Solaris 8 operating environment on a Sun E10000 domain with the main SSP running the Trusted Solaris 8 operating environment and the Trusted Solaris SSP 3.3 software. The procedures set up the Trusted Solaris SSP as the net install server for the Solaris domain.

Note –

These procedures are only for setting up the Solaris 8 operating environment on a domain controlled by a Trusted Solaris SSP. Setting up the Trusted Solaris operating environment on a domain is described in Chapter 5, Trusted Solaris 8 on an E10000 Domain.

These procedures assume that the domain already exists with an eeprom.image.domain_name file. When an E10000 is ordered, its domains are specified as part of the order. For each domain, an eeprom.image.domain_name file is usually created at the factory. If the domain does not have an eeprom.image.domain_name file for some reason, follow the instructions in Creating a Domain before starting.

Installing a Solaris 8 Domain Controlled by a Trusted Solaris SSP

Installing Solaris 8 on an E10000 domain controlled by a Trusted Solaris SSP includes the following tasks:

Note –

To be able do all the above procedures during a single login session, you need to log into the main SSP as user ssp.

The administrator makes changes to configuration files on the SSP using the Trusted Solaris Management Console toolbox according to the name service for the site's configuration. The administrator is also responsible for making sure that the nsswitch.conf(4) entries for each of the configuration files are defined so as to enable the SSP to find the changes.

To Configure the Domain Network Information on the SSP

  1. Log in to the Trusted Solaris SSP as user ssp. Assume the admin role.

  2. As admin at label admin_low, open the Application Manager, then the System_Admin folder.

  3. Using the Admin Editor action, make sure that an entry exists in the /etc/hosts file for the domain you are installing.

    This example shows a hosts(4) entry for a domain name of cuba entered as the hostname with an IP address of 129.150.107.102:


    cuba  129.150.107.102

    Caution – Caution –

    If the new domain entry follows any other host or SSP entry, the add_install_client command may not work in Step 7 in To Set Up the Trusted Solaris SSP as a Solaris Net Install Server.

  4. Using the Admin Editor, make sure that an entry exists in the /etc/ethers file with the Ethernet address for the domain you are installing.

    This example shows an ethers(4) entry for the cuba domain:


    0:00:be:a6:60:d1       cuba

  5. As secadmin at the label admin_low, launch the Solaris Management Console action from the Application Manager.

    If you are unfamiliar with logging in to the Solaris Management Console, follow the procedure Using the Solaris Management Console.

  6. Create a new template named unlab_priv in the tnrhtp(4) database. Use the values in Example 6–1 to fill in the template.

    See To Edit the Tnrhdb for the steps.

  7. Make the unlab_priv template active using the tnctl(1M) command with the -t option.


    ssp$ tnctl -t unlab_priv

  8. Bring up a terminal and check the unlab_priv template using the tninfo(1M) command with the -t option.


    ssp$ tninfo -t unlab_priv

    Example 6–1 unlab_priv Template

    This listing shows the correct values for the unlab_priv template. 

       template: unlab_priv
    host_type: UNLABELED
    doi: 0
    def_label: [ADMIN_LOW]
    hex: 0x00000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000[0x00
    000000000000000000000000000000000000000000000000000000000000000000]
    def_cl: ADMIN_LOW
    hex: 0x00000000000000000000000000000000000000000000000000000000000000000
    000
    forced_privs: sys_devices
    For routing only:
    min_sl: ADMIN_LOW
    hex: 0x00000000000000000000000000000000000000000000000000000000000000000
    000
    max_sl: ADMIN_HIGH
    hex: 0x7ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
    fff

  9. Using the Trusted Solaris Management Console Security families — ALL tool, assign the new unlab_priv template to the domain. See To Edit the Tnrhdb for the steps.

    If the domain being installed existed before the start of these procedures and the domain is controlled by the Trusted Solaris SSP, a tnrhdb database entry already exists for the domain either in the local /etc/security/tsol/tnrhdb file or in the tnrhdb name service (NIS or NIS+).

    If a template is already assigned to the domain, replace the template assignment with the new unlab_priv template. If no entry exists for the domain, create an entry as shown in the example. 

       129.150.107.102:unlab_priv

  10. As admin, use the Name Service Switch action from the System_Admin folder to make sure that the nsswitch.conf(4) entries for the modified files have an appropriate entry for your configuration.

    The following example shows the correct /etc/nsswitch.conf entries for an SSP that is a NIS+ client, when the administrator wants the local files to be consulted before the NIS+ maps. 

    hosts:        files nisplus
ethers:       files nisplus
tnrhtp:       files nisplus
tnrhdb:       files nisplus

    Caution – Caution –

    Make sure that the hosts entry does not have dns listed as a name service. If dns is in the hosts entry, add_install_client(1M) fails as described in Step d.

  11. In the admin role, make the changes to the domain's template active using the tnctl(1M) command.


    ssp$ tnctl -h cuba

  12. As secadmin, bring up a new terminal and enter the tninfo(1M) command to check the template assigned to the domain. 

       ssp$ tninfo -h cuba
IP address= 129.150.107.102, port= 0
template = unlab_priv

To Set Up the Trusted Solaris SSP as a Solaris Net Install Server

  1. Log in to the SSP as user ssp. Assume the admin role.

  2. In the admin role, at label admin_low, use the Device Allocation Manager to allocate the CD-ROM drive, then mount CD1 with all privileges.

    If you are unfamiliar with the procedure, see Setting up a CD-ROM.

  3. Verify that the add_install_client(1M) and rm_install_client(1M) are available with all privileges to the admin role by running the profiles(1) command:


    ssp$ profiles -l | grep install_client
/cdrom/cdrom0/s0/Solaris_8/Tools/add_install_client: all
/cdrom/cdrom0/s0/Solaris_8/Tools/rm_install_client: all

  4. If the commands are not available, do the following:

    1. Have the security administrator add them with all privileges to the Custom Admin Role profile.

      If you are unfamiliar with the procedure, see “To Add a Command to a Role's Rights” in Trusted Solaris Installation and Configuration.

    2. Assume the admin role in a new workspace to verify that the add_install_client and rm_install_client commands are available in the CD-ROM directories.

      If you are unfamiliar with the procedure, see “To Verify That a Command is Available to a Role” in Trusted Solaris Installation and Configuration.

  5. As admin, use the Name Service Switch action in the System_Admin folder to make sure the nsswitch.conf(4) entry for the prof_attr database has an appropriate entry for your configuration.

    The following example shows the correct /etc/nsswitch.conf prof_attr entry for an SSP that is a NIS+ client:


    prof_attr:    files nisplus

  6. Change to the Tools directory on the CD.


    ssp# cd /cdrom/cdrom0/s0/Solaris_8/Tools

  7. In the role admin, set up the host domain as an install client.

    1. Run add_install_client(1M).


      ssp$ ./add_install_client domain_name sun4u

      The add_install_client command should share the CD across the net.

    2. Confirm that the add_install_client command shared the file system.


      ssp$ showmount -e
export list for bermuda:
/cdrom/admin-cdrom_0 (everyone)

    3. If the command does not return /cdrom/admin-cdrom_0 (everyone), enter the command to share the directory, and re-confirm with the showmount(1M) command.


      ssp$ share -F nfs -o ro,anon=0 /cdrom/admin-cdrom_0
ssp$ showmount -e

    4. If you receive the warning shown in the following example, you need to remove the DNS entry in the /etc/nsswitch.conf file, to add the domain_name to the ethers map if the name is not already in the map, and to re-run the add_install_client command. 

      Error: domain_name does not exist in the NIS+ ethers map.

      The error occurs when the /etc/nsswitch.conf file lists dns in the hosts entry, as shown here: 

      hosts:     files nisplus dns

      1. Remove dns from the hosts entry in the /etc/nsswitch.conf file.


        hosts:     files nisplus

      2. If the domain_name is not already in the ethers map, add it.

      3. Change to the /cdrom/cdrom0/s0/Solaris_8/Tools directory on the CD-ROM.

      4. Re-run the add_install_client(1M) command.


        ssp$ ./add_install_client domain_name sun4u

  8. Leave the admin role workspace and go back to the user ssp workspace.

  9. Use the domain_status(1M) command to ensure that the OS version is set to the proper value.

    For SSP 3.2 and 3.3, the OS version should be 5.8. If the operating system version is correct, go to step Step 10.

    If the OS version is incorrect, remove and re-create the existing domain by performing the following steps.

    1. Halt and remove the existing domain.


      ssp% domain_remove -d domain_name

      The domain_remove(1M) command prompts you to save the domain directories, as in the following example: 

      domain_remove: The following subdirectories contain domain specific
 		information such as messages files, configuration files,
 		and hpost dump files. You may choose to keep these
			directories if you still need this information.  This
			domain may be created with or without this information
			being saved.

		/var/opt/SUNWssp/adm/xf4-b3
		/var/opt/SUNWssp/etc/allxf4/xf4-b3

Keep directories (y/n)? y
Domain : xf4-b3 is removed !

    2. Answer y (for yes) to keep the directories and save the domain information.

      Note –

      If you answered n (for no), you will need to supply the board numbers and platform name for the new domain.

    3. Create the new domain with the proper OS version number.

      The following example shows the operating system version of 5.8.


      ssp% domain_create -d domain_name -o 5.8

      If you saved the domain information, you do not need to include the -b and -p arguments. The domain_create(1M) command uses the saved domain information along with the information you provide with the command to create the new domain.

  10. Use the domain_switch(1M) command to set SUNW_HOSTNAME to the name of the domain.

    This example shows the command line for the cuba domain.


    ssp% domain_switch cuba

    Note –

    The domain_switch(1M) command must be executed from a C shell. By default, the SSP window is a profile C shell (pfcsh(1)).

  11. Check for blacklisted components.

    If SBus boards have been added to a system board, confirm that the processors on those system boards are not blacklisted. Processors are blacklisted at the factory when a system board does not have SBus cards installed.

    During the bring-up process, observe the list of blacklisted components. Alternatively, for instructions on how to retrieve the blacklist file, refer to the blacklist(4) man page.

    To remove a processor from the blacklist, edit the blacklist file and remove the number of the board from the pc line in the file. By default, the blacklist file resides at $SSPVAR/etc/platform_name/blacklist. However, the location of the blacklist file can be reconfigured so that the location of the blacklist file on your server may be different from the default location.

    You are done setting up the SSP as an install server. You can now bring up the domain, as described in the next section.

To Bring Up the Domain

  1. On the SSP as the user ssp, bring up the domain.

    Enter the bringup command in the SSP window as shown:


    ssp% bringup -A off

    If this is the first domain to be brought up, the system prompts you to confirm the configuration of the centerplane.

  2. Type y to continue if you are sure that no other domains are running. Responding yes resets the entire platform; therefore, you must ensure that no other domains are running. 

        This bringup will configure the Centerplane. Please confirm (y/n)? y

    After a few minutes the ssp prompt displays again.

  3. Review the output of the bringup(1M) command. If errors occurred, correct those errors before you proceed. If no errors occurred, continue to the next step.

  4. In the SSP window, open a netcon(1M) session.


    ssp% netcon -g

    The ok prompt displays after a few minutes. The duration depends on the size of the domain.

    You are done bringing up the domain. You can now set up the OpenBoot PROM, as described in the next section.

To Set Up the OpenBoot PROM Environment

  1. Drop down to the OBP prompt and use the devalias command to check for duplicate devaliases entries in OBP.

    The suninstall utility may not work properly if duplicate devaliases are defined in the OBP. Use the devalias command to check the aliases.

    The following example shows the net alias defined twice:


    ok devalias

    net            /sbus@41,0/qec@0,20000/qe@1,0
ttya           /ssp-serial
ssa_b_example  /sbus@40,0/SUNW,soc@0,0/SUNW,pln@b0000000,XXXXXX/SUNW,ssd@0,0:a
ssa_a_example  /sbus@40,0/SUNW,soc@0,0/SUNW,pln@a0000000,XXXXXX/SUNW,ssd@0,0:a
isp_example    /sbus@40,0/QLGC,isp@0,10000/sd@0,0
net_example    /sbus@40,0/qec@0,20000/qe@0,0
net            /sbus@41,0/qec@0,20000/qe@0,0
ok

  2. If multiple entries exist in the devalias output, remove them.

    The following example removes the last-created net devalias. You may have to issue a second nvunalias command if the second net alias is the incorrect one. Then issue an nvalias command to create the correct net device alias.


    ok nvunalias net

  3. If a net alias does not exist for the network interface that is on the same subnet as the SSP, create one by typing a command similar to the following example:


    ok nvalias net /sbus@41,0/SUNW,hme@0,8c00000

    Where /sbus@41,0 refers to system board 0 and SBus 1. The /SUNW,hme@0 portion of the device name defines a 100BASE-T network interface installed in Slot 0. This information is site-specific; your configuration may vary.

    The following table contains the SBus numbers used in the devalias file.

    Table 6–1 SBus Numbers in the devalias File

    system board 

    sysio 0 

    sysio 1 

     

    system board 

    sysio 0 

    sysio 1 

    0 

    /sbus@40 

    /sbus@41 

     

    8 

    /sbus@60 

    /sbus@61 

    1 

    /sbus@44 

    /sbus@45 

     

    9 

    /sbus@64 

    /sbus@65 

    2 

    /sbus@48 

    /sbus@49 

     

    10 

    /sbus@68 

    /sbus@69 

    3 

    /sbus@4c 

    /sbus@4d 

     

    11 

    /sbus@6c 

    /sbus@6d 

    4 

    /sbus@50 

    /sbus@51 

     

    12 

    /sbus@70 

    /sbus@71 

    5 

    /sbus@54 

    /sbus@55 

     

    13 

    /sbus@74 

    /sbus@75 

    6 

    /sbus@58 

    /sbus@59 

     

    14 

    /sbus@78 

    /sbus@79 

    7 

    /sbus@5c 

    /sbus@5d 

     

    15 

    /sbus@7c 

    /sbus@7d 

    The watch-net-all command (no spaces) displays the functioning network interfaces.

  4. Set the boot-disk alias so that it refers to the device on which you are installing the Solaris operating environment.


    ok nvalias bootdisk_alias device_string

    As in this example, the nvalias command should be entered on a single line.

  5. Use the setenv command to set the default boot-disk alias to the correct device.


    ok setenv boot-device bootdisk_alias

    Where bootdisk_alias corresponds to the user-defined alias you established in Step 4. The device should correspond to the device that you want to use as the boot disk.

    You are done setting up the OBP environment. You can now install the Solaris operating environment, as described in the following section.

To Install the Solaris Operating Environment

You can use these instructions to install the Solaris operating environment without saving any previous files.

Use the suninstall utility following the instructions in this procedure, which are specific to the Enterprise 10000 when the SSP is running the Trusted Solaris environment. If needed, also see the Solaris installation instructions in the Solaris 8 Installation Collection, which is available at http://docs.sun.com and in the Solaris media kit.

Caution – Caution –

The next step starts the suninstall utility. During the installation, you will be asked to specify the device name of the boot disk. Do not begin the installation until you know the device name.

  1. In the domain's netcon(1M) window, boot the system from the network.

    Specify the alias assigned in the OBP for the proper network interface, as described in Step d or enter the device path for the network interface.

    The example shows the net alias.


    ok boot net

    Caution – Caution –

    If you specify an incorrect alias or path, the boot command will fail, and you will have to bring up the domain again, as described in To Bring Up the Domain, and enter boot net again.

    If you install the operating system on a disk other than the one designated as the boot disk, the suninstall utility displays a warning message similar to the following: 

    Warning
You have an invalid disk configuration because of the condition(s) 
displayed in the window below. Errors should be fixed to ensure a 
successful installation. Warnings can be ignored without causing 
the installation to fail.

> To go back and fix errors or warnings, select Cancel.
> To accept the error conditions or warnings and continue with 
> the installation, select Continue.

WARNING: The boot disk is not selected or does not have 
a “/” mount point (c0t3d0)

    You can safely ignore this warning and press F2 to continue.

  2. Provide site and platform-specific information when prompted by suninstall.

    The bootnet command starts the suninstall utility. This utility prompts you to provide site and platform-specific information. Refer to the following table for the platform-specific information you may need to supply. If you have questions about the suninstall utility, refer to the Installation Instructions for Solaris 8 (SPARC Platform Edition) in your media kit.

    If you are using an install server, make sure that nfsd and mountd are running on the server.

    Table 6–2 Platform-Specific Information for the suninstall Utility and CD1

    If you are asked to 

    Do this 

    Type of Terminal 

    If you are using dtterm, select Other and enter dtterm.

    Please enter the hostname of the SSP for domain_name [default_name]

    		Enter the hostname for your SSP. Note that the default value is to append -ssp to the domain name.

    Set the network information 

    Select the appropriate level of information you want to provide. If you select any option other than None, the suninstall utility displays a series of dialogs that request configuration information. Provide that information.

    Solaris Interactive Installation 

    Select Initial for fresh install.

    Select 64 bit 

    Click Select To Include Solaris 64-bit Support to install the 64-bit kernel.

    Select Software 

    Select Entire Distribution plus OEM Support.

    Select Disk(s) 

    Select the disk(s) on which the software is to be installed. 

    If you choose a drive for the root partition other than the one designated as the boot drive, a warning message appears later in the installation process. At that point, you can choose whether or not to continue. 

    Automatically Layout File Systems 

    Select Manual Layout, then select Customize. The suninstall utility enables you to customize the root disk by specifying disk partitions. Refer to Table 6–3 as a guide.

    Mount Remote File System 

    Press F2 if file systems are not to be mounted from a remote file server.

    Reboot After Iinstallation 

    Select automatic reboot and press F2 to begin the installation. This step, which installs the software from CD1, can take approximately 40 minutes to complete. Make sure that the boot disk is the disk you just installed. After the reboot, you are prompted for the root password.

    Root Password 

    After CD1 has been installed, the domain is rebooted, andyou will be prompted for the root password. After you enter the password twice, WebStart Launcher appears. 

    You are done with CD1. Go to To Configure the OBP Variables to continue the installation.

    When you perform a full install of the Solaris 8 operating environment on a domain, the suninstall utility allows you to manually enter the disk partition sizes for your file systems. Do not use disk partitions that are less than the minimum sizes in Table 6–3.

    If two disks are used, root (/) and /usr must be on the device specified in the OBP boot alias.

    Table 6–3 Minimum Partition Sizes

    Partition 

    Minimum Sizes 

    Notes 

    0 

    /

    256 Mbyte 

    Bare minimum size 

    1 

    swap

    1024 Mbyte 

    Bare minimum size 

    2 

    overlap 

     

    Actual total disk size 

    3 

    /var

    512 Mbyte 

     

    4 

     

    3 Mbyte 

    This slice must be reserved for the Alternate Pathing and Solstice™ DiskSuite™ products. Otherwise, subsequent Alternate Pathing installations will overwrite the operating system. 

    5 

    /opt

    512 Mbyte 

    This may be larger depending upon remaining space. 

    6 

    /usr

    1 Gbyte 

    Asian-language users may need more space here. 

    Use the Tab key to move the cursor, and use the keyboard to type the size for each partition. Press F2 when you are done.

    Return to Table 6–2 to continue the suninstall installation.

    Table 6–4 Platform-Specific Information for the suninstall Utility and CD2

    If you are asked to 

    Do this 

    WebStart Launcher 

    Select Network File System. WebStart prompts you for CD2. At this point, in another SSP window, log into the SSP as superuser and unshare CD1. Then, eject CD1, replace it with CD2, and share CD2, as follows:


    ssp# share -F nfs -o ro,anon=0 /cdrom/admin-cdrom_0

    WebStart prompts you for the path to the installation image. Enter the path you used to share the CD, as follows:


    SSP_name: /cdrom/admin-cdrom_0

    Select [1] or [2]

    Select [2] Done after CD2 has been installed. You are done with the Solaris installation and the domain is rebooted. Continue the installation by performing the steps in the next section.

To Configure the OBP Variables

  1. In the netcon window, drop down to the OBP prompt using ~#.

  2. List the devices entry for your boot disk.


    domain_name# ls -l /dev/dsk/root_partition_device

    Where root_partition_device is in the form cxtxdxsx.

  3. Copy the part of the string that begins with either /sbus or /pci.

    Example: /sbus@65,0/SUNW,fas@1,8800000/sd@3,0:a

  4. Assign the device string to an alias; enter the nvalias command on a single line.


    ok nvalias bootdisk_alias device_string

  5. Use the setenv command to set the default boot-device alias to the correct device.


    ok setenv boot-device bootdisk_alias

    Where bootdisk_alias should correspond to the device that you want to use as the boot disk, which may be different than the device on which you just installed the Solaris operating environment.

  6. Exit OBP to return to the domain prompt.

    You are done configuring the OBP variables. You can now bring up the domain, as described in the following section.

To Bring Up the Domain

  1. On the main SSP in the ssp window, change to the Tools directory on the CD-ROM.


    ssp% cd /cdrom/cdrom0/s0/Solaris_8/Tools

  2. Enter rm_install_client(1M) to remove the domain as an install client.


    ssp% ./rm_install_client domain_name

  3. Assume the admin role.

  4. At label admin_low, unshare then unmount the /cdrom/admin-cdrom_0 file system.


    ssp$ cd /
ssp$ unshare /cdrom/admin-cdrom_0
ssp$ umount /cdrom/admin-cdrom_0

  5. Use the Device Allocation Manager to deallocate the CD-ROM drive.

    If you are unfamiliar with the steps, see Deallocating the CD-ROM.

  6. Use the Template Manager to make sure the domain has an appropriate template assigned.

    See Editing the Trusted Network Databases if needed for how to create and assign templates in the Trusted Solaris Management Console.

    Solaris domains are classified with the unlabeled host type because hosts running the Solaris operating environment do not support labels (and domains are administered as hosts) . Because the Trusted Solaris environment communicates with a Solaris domain at a single label, the appropriate single label must be specified in a template in the tnrhtp(4) database and assigned to the host in the tnrhdb(4) database. Therefore, any template assigned to a Solaris domain must have both of the following specified:

    • The unlab host type (in the Host Type= field)

    • The appropriate label for the domain in the def_label= field)

      The Template Manager dialog equivalents are the Unlabeled option from the Host Type: menu and the appropriate label specified in the Label field.

    Caution – Caution –

    Do not leave the unlab_priv template that was assigned to the domain in Step 9. It is essential to replace it with another template with the appropriate single label for the domain.

    The screen shows an example unlab_internal template assigned to the tnrhdb entry for the IP address 129.150.107.102. The example assumes that the unlab_internal template is in the tnrhtp(4) database and assumes that the template assigns a host type of unlabeled and a label of internal as the single label for the Solaris domain.


    129.150.107.102:unlab_internal

  7. Make the change in template for the domain active using the tnctl(1M) command.


    ssp$ tnctl -h cuba

  8. Enter the tninfo(1M) command to check the template assigned to the domain.

    The example shows the unlab_internal template assigned to the cuba domain. 

       ssp$ tninfo -h cuba
      IP address= 129.150.107.102, port= 0
      template = unlab_internal

  9. Leave the admin role and go back to the user ssp.

  10. In the ssp window, switch to the domain and bring it up.


    ssp% domain_switch domain-name
ssp% bringup -A on

To Log Into the Solaris Domain as root

When the Solaris domain has booted, the console login: prompt displays on the netcon(1M) for the domain.

  1. Do one of the following to log into the Solaris domain as the root user.

    • On the Trusted Solaris SSP log in at the console login: prompt on the netcon for the domain.


      console login: root
Password:

    • From the Trusted Solaris SSP or another host, do a remote login to the Solaris domain as a normal user then use the su(1M) command to switch to root.


      ssp% rlogin cuba
cuba%  su root
Password:
ssp#

    For how to enable remote logins, see “Managing Remote Logins” in Trusted Solaris Administrator's Procedures, if needed.

  2. Confirm that you are on the Solaris domain and that you are root by using the uname(1) and id(1M) commands.


    ssp# uname -a
ssp# id -a

    To Make the Domain a NIS+ Client

      If the domain is to be a NIS+ client, assume the domain's admin role to update the hosts entry in the /etc/nsswitch.conf file after running the nisclient command.


      hosts: files nisplus

      Failure to do this will result in the domain communicating in JTAG instead of network mode after a reboot.

To Configure the NTP Packages

  1. Log into the Solaris domain as the root user.

  2. Create the ntp.conf file in your text editor.

  3. Add the following lines to the file. 

       server ssp-name
server 127.127.1.0
fudge 127.127.1.0 stratum 10

    Each domain should use the SSP as its source for time, and the SSP should use at least two other sources, besides its internal clock, to avoid a single point of failure in case the SSP clock fails. Each domain should use the SSP as its source for time, and the SSP should use at least two other sources, besides its internal clock, to avoid a single point of failure in case the SSP's clock fails.

    Note –

    The domain should have a stratum number that is at least one level above the SSP.

    For more information about NTP commands, refer to the ntpdate(1M) man page.

    You are done configuring the NTP packages. You can now finish the domain installation, as described in the following section.

To Finish the Domain Installation

  1. Perform any site-specific configuration tasks on the newly installed environment by editing the configuration files in the /a directory.

    The number and extent of any site-specific configuration task, such as configuring the default router, are highly dependent on the local configuration of the server and the network on which it resides. If you are unsure about what tasks you should perform, contact your service provider, or refer to the System Administration Guide, Volume 1 and the Trusted Solaris Administrator's Procedures.

    1. List the devices entry for your boot disk.


      domain_name# ls -l /dev/dsk/root_partition_device

      where root_partition_device is in the form cxtxdxsx.

    2. Copy the part of the string that begins with either /sbus or /pci.

      Example: /sbus@65,0/SUNW,fas@1,8800000/sd@3,0:a

      Record your device string here:


      /

  2. As root on the domain, check the current operating mode.


    domain_name# isainfo -k

    If the domain is running in 64-bit mode, the screen displays sparcv9.

  3. From the SSP window, use the ps(1) command to ensure that the Event Detector Daemon (EDD) is running the edd_cmd(1M) command to ensure that the EDD is running in the proper mode before you attempt to reboot the domain (see the edd(1M) man page).

  4. Reboot into the desired operating mode, if needed.

    Use the bootdisk_alias from To Configure the OBP Variables.

    1. To change from 64–bit to 32-bit mode, enter the following command.


      domain_name# reboot bootdisk_alias kernel/unix

    2. To change from 32–bit to 64-bit mode, type the following command.


      domain_name# reboot bootdisk_alias kernel/sparcv9/unix
To Install and Configure Alternate Pathing on a Solaris Domain

  1. Do the steps in Chapter 7, Trusted Solaris Alternate Pathing 2.3 on an E10000 Domain, To Install Trusted Solaris AP 2.3, but make the following substitutions:

    • Install the Solaris 8 version; use the Solaris Supplement CD for AP 2.3.

    • Do the steps on the Solaris domain as the root user instead of assuming the admin role.

  2. To configure a Solaris AP, do the steps in Chapter 7, Trusted Solaris Alternate Pathing 2.3 on an E10000 Domain, To Configure a Trusted Solaris AP as the root user instead of assuming the admin role.