test

Solaris 9 9/04 Installation Guide

Appendix I x86: Preparing to Boot From the Solaris Device Configuration Assistant or the Network (Tasks)

This appendix describes the following topics.

x86: Copying the Boot Software to a Diskette

The Solaris Device Configuration Assistant is a program that enables you to perform various hardware configuration and booting tasks. The Solaris Device Configuration Assistant image is found in the Tools directory of either the Solaris x86 Platform Edition DVD or the Solaris Software 2 of 2 x86 Platform Edition CD. Use the following procedure to copy the boot image to a 3.5 diskette.

Note –

You can boot directly from DVD or CD media or by using a net image with PXE. For information on these methods of booting, see x86: Accessing the Solaris 9 Device Configuration Assistant and PXE.

x86: To Copy the Boot Software to a Diskette

Note –

This procedure assumes that the system is running Volume Manager. If you are not using Volume Manager to manage diskettes and discs, refer to System Administration Guide: Devices and File Systems for detailed information about managing removable media without Volume Manager.

  1. Log in as superuser on an x86 system to which a diskette drive is attached.

  2. On the system with the DVD-ROM or CD-ROM drive, insert the Solaris x86 Platform Edition DVD or the Solaris Software 2 of 2 x86 Platform Edition CD in the drive.

    The Volume Manager mounts the disc.

  3. Change to the directory that contains the boot image.

    • For DVD media, type:


      # cd /cdrom/sol_9_x86/s2/Solaris_9/Tools

    • For CD media, type:


      # cd /cdrom/sol_9_x86/Solaris_9/Tools

  4. Insert a blank diskette or a diskette that can be overwritten in the diskette drive.

  5. Notify Volume Manager to check for new media.


    # volcheck

  6. Format the diskette:

    Caution – Caution –

    Formatting erases all data on the diskette.


    # fdformat -d -U

  7. Copy the file to the diskette.


    # dd if=d1_image of=/vol/dev/aliases/floppy0 bs=36k

  8. Eject the diskette by typing eject floppy at the command line, and then manually ejecting the diskette from the drive.

x86: Booting and Installing Over the Network With PXE

This section describes how to set up an x86-based system to install over the network without local boot media. This section describes the following topics.

What is PXE?

PXE network boot is a “direct” network boot. No boot media is required on the client system. With PXE, you can install an x86-based client over the network by using DHCP.

PXE network boot is available only for devices that implement the Intel Preboot Execution Environment specification. To determine if your system supports PXE network boot, see your hardware manufacturer's documentation.

The Solaris boot diskette is still available for systems that do not support PXE. The boot diskette image is available on the Solaris Software 2 of 2 x86 Platform Edition CD.

x86: Guidelines for Booting With PXE

To boot over the network by using PXE, you need the following systems.

When you are preparing to use PXE to install a client over the network, consider the following issues.

Booting With PXE (Task Map)

Perform the following tasks to boot and install your system over the network by using PXE.

Table I–1 x86: Task Map: Booting From the Network By Using PXE

Task 

Description 

Instructions 

Verify that your system supports PXE. 

Confirm that your machine can use PXE to boot without local boot media. 

Check your hardware manufacturer's documentation. 

Choose an installation method. 

The Solaris operating environment provides several methods for installation or upgrade. Choose the installation method that is most appropriate for your environment. 

Chapter 3, Choosing a Solaris Installation Method (Overview)

Gather information about your system. 

Use the checklist and complete the worksheet to collect all of the information that you need to install or upgrade. 

Chapter 6, Gathering Information Before Installation or Upgrade (Planning)

(Optional) Preconfigure system information. 

You can preconfigure system information to avoid being prompted for the information during the installation or upgrade. 

Chapter 7, Preconfiguring System Configuration Information (Tasks)

Create an install server. 

Set up a Solaris server to install the Solaris operating environment from the network.  

x86: Creating an x86 Install Server

Add systems to be installed over the network. 

Use add_install_client -d to add DHCP support to install a class of client (of a certain machine type, for example) or a particular client ID.

x86: Adding Systems to Install Over the Network By Using PXE

Set up a DHCP server. 

Plan for and configure your DHCP service. 

“Planning for DHCP Service (Task)” in System Administration Guide: IP Services.

Create DHCP options for installation parameters and macros that include the options. 

Use DHCP Manager or dhtadm to create the vendor options and macros that are output from the add_install_client -d command.

Creating DHCP Options and Macros for Solaris Installation Parameters

Boot the client. 

Instruct the client BIOS to boot from the network. 

x86: Booting the Client Over the Network By Using PXE

x86: Creating an x86 Install Server

The install server contains the installation image that is needed to install systems from the network. You must create an install server to install the Solaris software on a system from the network.

Note –

If you want use the Solaris DVD media to set up an install server on a system that is running the Solaris 2.6 or 7 operating environment, you must first apply one of the following patches.

To Create an x86 Install Server
Note –

This procedure makes the following assumptions.

  1. On the system that is to become the install server, become superuser.

    The system must include a CD-ROM drive and be part of the site's network and name service. If you use a name service, the system must already be in a name service, such as NIS, NIS+, DNS, or LDAP. If you do not use a name service, you must distribute information about this system by following your site's policies.

  2. Insert the Solaris Software 1 of 2 CD in the system's drive.

  3. Create a directory for the CD image.


    # mkdir -p install_dir_path
    install_dir_path

    Specifies the directory where the CD image is to be copied

  4. Change to the Tools directory on the mounted disc.


    # cd /cdrom/cdrom0/s2/Solaris_9/Tools

    In the previous example, cdrom0 is the path to the drive that contains the Solaris operating environment CD media.

  5. Copy the image in the drive to the install server's hard disk.


    # ./setup_install_server install_dir_path
    install_dir_path

    Specifies the directory where the CD image is to be copied

    Note –

    The setup_install_server command indicates whether you have enough disk space available for the Solaris Software disc images. To determine available disk space, use the df -kl command.

  6. Change directories to root (/).


    # cd /

  7. Eject the Solaris Software 1 of 2 CD.

  8. Insert the Solaris Software 2 of 2 CD in the system's CD-ROM drive.

  9. Change to the Tools directory on the mounted CD:


    # cd /cdrom/cdrom0/Solaris_9/Tools

  10. Copy the CD in the CD-ROM drive to the install server's hard disk.


    # ./add_to_install_server install_dir_path
    install_dir_path

    Specifies the directory where the CD image is to be copied

  11. Change directories to root (/).


    # cd /

  12. Eject the Solaris Software 2 of 2 CD.

  13. Insert the Solaris Languages CD in the system's CD-ROM drive.

  14. Change to the Tools directory on the mounted CD:


    # cd /cdrom/cdrom0/Tools

  15. Copy the CD in the CD-ROM drive to the install server's hard disk.


    # ./add_to_install_server install_dir_path
    install_dir_path

    Specifies the directory where the CD image is to be copied

  16. Change directories to root (/).


    # cd /

  17. If you want to patch the files that are located in the miniroot (/install_dir_path/Solaris_9/Tools/Boot) on the net install image, use the patchadd -C command to patch these files. You might need to patch a file if a boot image has problems.

    Caution – Caution –

    Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.

Example I–1 x86: Creating an x86 Install Server With x86 CD Media

The following example illustrates how to create an install server by copying the following CDs to the install server's /export/home/cdx86 directory.


# mkdir -p /export/home/cdx86
# cd /cdrom/cdrom0/s2/Solaris_9/Tools
# ./setup_install_server /export/home/cdx86
# cd /
# cd /cdrom/cdrom0/Solaris_9/Tools
# ./add_to_install_server /export/home/cdx86
# cd /
# cd /cdrom/cdrom0/Tools
# ./add_to_install_server /export/home/cdx86
# cd /
# cd /cdrom/cdrom0/s2
# ./modify_install_server -p /export/home/cdx86 /cdrom/cdrom0/s2

In this example, each CD is inserted and automatically mounted before each of the commands. After each command, the CD is removed.

x86: Adding Systems to Install Over the Network By Using PXE

After you create an install server, you must set up each system that you want to install from the network. Each system that you want to install needs to find the following:

Use the following add_install_client procedure for set up an x86 client to install from the network by using PXE.

To Add a Client to Install Over the Network With DHCP

  1. On the install server, become superuser.

  2. If you use the NIS, NIS+, DNS, or LDAP name service, verify that the following information about the system to be installed has been added to the name service:

    • Host name

    • IP address

    • Ethernet address

    For more information on name services, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

  3. Change to the Tools directory on the Solaris 9 CD image on the install server:


    # cd /install_dir_path/Solaris_9/Tools
    install_dir_path

    Specifies the path to the Tools directory

  4. Set up the client system to be installed from the network. 


    # ./add_install_client -d [[-s install_server:install_dir_path]] \
[[-c jumpstart_server:jumpstart_dir_path]]   [[-p sysid_server:path]] \
  [[-t boot_image_path]] [[-b "boot-property=value"]] \
[[-e ethernet_address]] client_name platform_group
    -d

    Specifies that the client is to use DHCP to obtain the network install parameters. If you use the -d only, the add_install_client command sets up the installation information for client systems of the same class, for example, all x86 client machines. To set up the installation information for a specific client, use the -d with the -e option.

    For more information about class-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.

    -s install_server:install_dir_path

    Specifies the name and path to the install server.

    • install_server is the host name of the install server

    • install_dir_path is the absolute path to the Solaris 9 CD image

    -c jumpstart_server:jumpstart_dir_path

    Specifies a JumpStart directory for custom JumpStart installations. jumpstart_server is the host name of the server on which the JumpStart directory is located. jumpstart_dir_path is the absolute path to the JumpStart directory.

    -p sysid_server:path

    Specifies the path to the sysidcfg file for preconfiguring system information. sysid_server is either a valid host name or an IP address for the server that contains the file. path is the absolute path to the directory containing the sysidcfg file.

    -t boot_image_path

    Specifies the path to an alternate boot image if you want to use a boot image other than the image in the Tools directory on the Solaris 9 net installation image, CD, or DVD.

    -b “boot-property=value”

    x86 based systems only: Enables you to set a boot property variable that you want to use to boot the client from the network. The -b must be used with the -e option.

    See the eeprom(1M) man page for descriptions of boot properties.

    -e ethernet_address

    Specifies the ethernet address of the client that you want to install. This option enables you to set up the installation information to use for a specific client.

    For more information about client-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.

    client_name

    Is the name of the system to be installed from the network. This name is not the host name of the install server.

    platform_group

    Is the platform group of the system to be installed. A detailed list of platform groups appears in Appendix C, Platform Names and Groups (Reference).

    The previous command outputs the vendor options and macros that you need to add to you DHCP server. See Creating DHCP Options and Macros for Solaris Installation Parameters for instructions about how to define these vendor options and macros in your DHCP server.

Example I–2 x86: Adding an x86 Install Client on an x86 Install Server When Using DHCP and PXE (CDs)

The following example illustrates how to add an x86 install client to an install server when you are using DHCP to set installation parameters on the network. The -d option is used to specify that clients are to use the DHCP protocol for configuration. The DHCP class name SUNW.i86pc indicates that this command applies to all Solaris x86 network boot clients, not just a single client. The -s option is used to specify that the clients are to be installed from the install server that is named rosemary. This server contains a Solaris Software 1 of 2 x86 Platform Edition CD image in /export/home/cdx86.

For more information on how to use DHCP to set installation parameters for network installations, see “Supporting Solaris Network Installation with the DHCP Service (Task Map)” in System Administration Guide: IP Services.


x86_install_server# cd /export/boot/Solaris_9/Tools
x86_install_server# ./add_install_client -d -s rosemary:/export/home/cdx86 \
SUNW.i86pc i86pc
Example I–3 x86: Specifying a Serial Console to Use During a Network Installation (CDs)

The following example illustrates how to add an x86 install client to an install server and specify a serial console to use during the installation. This example sets up the install client in the following manner.


install server# cd /export/boot/Solaris_9/Tools
install server# ./add_install_client -d -e "00:07:e9:04:4a:bf" \
-b "input-device=ttya" -b "output-device=ttya" i86pc

For a complete description of the boot property variables that you can use with the -b option, see the eeprom(1M) man page.

Example I–4 x86: Specifying a Boot Device to Use During a Network Installation (CDs)

The following example illustrates how to add an x86 install client to an install server and specify a boot device to use during the installation. If you specify the boot device when you set up the install client, you are not prompted for this information by the Device Configuration Assistant during the installation.

This example sets up the install client in the following manner.


install server# cd /export/boot/Solaris_9/Tools
install server# ./add_install_client -d -e "00:07:e9:04:4a:bf" \
-b "input-device=ttya" -b "output-device=ttya" \
-b "bootpath=/pci@0,0/pci108e,16a8@8" i86pc

For a complete description of the boot property variables that you can use with the -b option, see the eeprom(1M) man page.

x86: Booting the Client Over the Network By Using PXE

To install the system over the network, you must instruct the client system to boot over the network. Enable PXE network boot on the client system by using the BIOS setup program in the system BIOS, the network adapter BIOS, or both. On some systems, you must also adjust the boot device priority list so that network boot is attempted before booting from other devices. See the manufacturer's documentation for each setup program, or watch for setup program instructions during boot.

During the installation, answer the system configuration questions, if you are prompted.

After the system boots and installs over the network, instruct the system to boot from the disk drive on subsequent boots.

Some PXE-capable network adapters have a feature that enables PXE boot if you type a particular keystroke in response to a brief boot-time prompt. This feature enables you to boot over the network with PXE without modifying the PXE settings. If your adapter does not have this feature, disable PXE in the BIOS setup when the system reboots after installation. The system then boots from the disk drive.